Patent Application
20250056665
This present disclosure relates to a method of a communication apparatus, a method of a User Equipment (UE), a communication apparatus, a UE, a method for a first core network apparatus, a method for a third core network apparatus and a method for a first network slice control function node.
SA2 #148E endorsed a new Rel-18 study on network slicing (eNS_Ph3) in NPL 2. When the UE performs registration, the UE generates a Requested NSSAI based on the Configured S-NSSAI, Allowed NSSAI and also may take the URSP rules into account. The UE may register S-NSSAIs which are not going to be used (e.g. establish PDU session in the network slice by running applications) at once, and possibly not while registered in this Registration Area (RA). Similar after the applications is terminated, and the PDU session may not be used (e.g. deliver running application traffic via the PDU sessions) by any other applications in the UE. This may be perceived by operator's customers as an issue, for example when Network Slice Admission Control (NSAC) is deployed this will cause additional UE to fail to register this S-NSSAI and request S-NSSAI for PDU session. Another issue is the operator may have Service Level Agreements (SLAs) with customers related to availability of the customer's service. When the network slice is congested and other network slices can serve the SLA better the network may determine that the UE traffic flow is better served by a different network slice.
One outstanding problem with the 3GPP Rel-17 agreed Network Slice Admission Control (NSACF) is whether and how to enhance the system to ensure network-controlled behavior of network slice usage including UE registration and PDU Session establishment. For example, it needs a mechanism to solve a problematic situation that the network slice cannot serve at least one of UE(s) and PDU Session(s) with actual activity when performing the NSAC. For example, it needs a mechanism to solve a problematic situation when the network slice is used by UE(s) or PDU Session (s).
In an aspect of the present disclosure, a method of a communication apparatus includes sending a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a second message in a case where the S-NSSAI is not used for a time period. The second message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for the time period. The time period is associated with the S-NSSAI. The method includes sending a third message to remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI). The third message includes the S-NSSAI and the reject cause.
In an aspect of the present disclosure, a method of a communication apparatus includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The method includes performing Network Slice Admission Control (NSAC) in a case where the timer expires. The method includes sending a second message after performing the NSAC. The second message includes the S-NSSAI and a reject cause indicating expiry of the timer.
In an aspect of the present disclosure, a method of a User Equipment (UE) includes performing a registration for Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a message. The message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for a time period. The time period is associated with the S-NSSAI. The method includes removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) after receiving the message.
In an aspect of the present disclosure, a method of a communication apparatus includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The method includes sending a second message for Network Slice Admission Control (NSAC) and a third message in a case where the timer expires. The second message includes the S-NSSAI. The third message includes the S-NSSAI and a reject cause indicating expiry of the timer.
In an aspect of the present disclosure, a method of a communication apparatus includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The method includes receiving a second message related to establishment of a Protocol Data Unit (PDU) session for the S-NSSAI after starting the timer. The method includes stopping the timer after receiving the second message. The method includes receiving a third message related to release of the PDU session after stopping the timer. The method includes starting the timer after receiving the third message. The method includes sending a fourth message in a case where the timer expires. The fourth message is for removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) or is for deregister the S-NSSAI.
In an aspect of the present disclosure, a method of a communication apparatus includes sending a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The method includes starting a timer after receiving the second message. The method includes sending a third message in a case where there is no user plane activity for the PDU session until the timer expires. The third message indicates that there is no user plane activity for the PDU session. The method includes receiving a fourth message after sending the third message. The method includes performing a procedure to release the PDU session after receiving the fourth message.
In an aspect of the present disclosure, a method of a communication apparatus includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes sending a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The method includes receiving a third message after sending the second message. The third message indicates that there is no user plane activity for the PDU session. The method includes sending a fourth message after receiving the third message. The fourth message is for performing a procedure to release the PDU session.
In an aspect of the present disclosure, a communication apparatus includes means for sending a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The apparatus includes means for receiving a second message in a case where the S-NSSAI is not used for a time period. The second message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for the time period. The time period is associated with the S-NSSAI. The apparatus includes means for sending a third message to remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI). The third message includes the S-NSSAI and the reject cause.
In an aspect of the present disclosure, a communication apparatus includes means for receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The apparatus includes means for starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The apparatus includes means for performing Network Slice Admission Control (NSAC) in a case where the timer expires. The apparatus includes means for sending a second message after performing the NSAC. The second message includes the S-NSSAI and a reject cause indicating expiry of the timer.
In an aspect of the present disclosure, a User Equipment (UE) includes means for performing a registration for Single Network Slice Selection Assistance Information (S-NSSAI). The UE includes means for receiving a message. The message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for a time period. The time period is associated with the S-NSSAI. The UE includes means for removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) after receiving the message.
In an aspect of the present disclosure, a communication apparatus includes means for receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The apparatus includes means for starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The apparatus includes means for sending a second message for Network Slice Admission Control (NSAC) and a third message in a case where the timer expires. The second message includes the S-NSSAI. The third message includes the S-NSSAI and a reject cause indicating expiry of the timer.
In an aspect of the present disclosure, a communication apparatus includes means for receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The apparatus includes means for starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The apparatus includes means for receiving a second message related to establishment of a Protocol Data Unit (PDU) session for the S-NSSAI after starting the timer. The apparatus includes means for stopping the timer after receiving the second message. The apparatus includes means for receiving a third message related to release of the PDU session after stopping the timer. The apparatus includes means for starting the timer after receiving the third message. The apparatus includes means for sending a fourth message in a case where the timer expires. The fourth message is for removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) or is for deregister the S-NSSAI.
In an aspect of the present disclosure, a communication apparatus includes means for sending a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The apparatus includes means for receiving a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The apparatus includes means for starting a timer after receiving the second message. The apparatus includes means for sending a third message in a case where there is no user plane activity for the PDU session until the timer expires. The third message indicates that there is no user plane activity for the PDU session. The apparatus includes means for receiving a fourth message after sending the third message. The apparatus includes means for performing a procedure to release the PDU session after receiving the fourth message.
In an aspect of the present disclosure, a communication apparatus includes means for receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The apparatus includes means for sending a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The apparatus includes means for receiving a third message after sending the second message. The third message indicates that there is no user plane activity for the PDU session. The apparatus includes means for sending a fourth message after receiving the third message. The fourth message is for performing a procedure to release the PDU session.
In an aspect of the present disclosure, a method for a first core network apparatus includes receiving, from a second core network apparatus, a fourth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the fourth message. The method includes detecting the timer is expired. The method includes sending, to the second core network apparatus, a fifth message indicating at least one of the timer is expired or the network slice related to the timer is not used, after the detecting the timer is expired.
In an aspect of the present disclosure, a method for a first core network apparatus includes receiving, from a second core network apparatus, a fourth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the fourth message. The method includes detecting an activity related to the network slice. The method includes stopping the timer after the detecting the activity.
In an aspect of the present disclosure, a method for a third core network apparatus includes receiving, from a first core network apparatus, a sixth message related to management of a network slice. The method includes analysing data related to the network slice based on information receive from other core network apparatus,
In an aspect of the present disclosure, a method for a third core network apparatus includes receiving, from a first core network apparatus, a sixth message related to management of a network slice. The method includes analysing data related to the network slice based on information receive from other core network apparatus. The method includes starting a timer for the network slice after the receiving the sixth message. The method includes detecting an activity related to the network slice. The method includes stopping the timer after the detecting the activity, wherein the first core network apparatus manages network slice admission control.
In an aspect of the present disclosure, a method for a first network slice control function node includes receiving, from a second core network apparatus, an eighth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the eighth message. The method includes detecting the timer is expired. The method includes sending, to the second core network apparatus, a ninth message indicating at least one of the timer is expired or the network slice related to the timer is not used, after the detecting the timer is expired.
In an aspect of the present disclosure, a method for a first network slice control function node includes receiving, from a second core network apparatus, a tenth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the tenth message. The method includes receiving, from a second network slice control function node, eleventh message detecting an activity related to the network slice. The method includes stopping the timer after receiving the eleventh message.
In an aspect of the present disclosure, a method for a third core network apparatus includes sending, to a first core network apparatus, first information related to management of a network slice to initiate a control of a number of session based on a timer. The method includes receiving, from the first core network apparatus, second information indicating the control is initiated. The method includes monitoring user plane activity related to the session after receiving the second information. The method includes sending, to the first core network apparatus, third information indicating the user plane activity is not detected based on the monitoring. The method includes receiving, from the first core network apparatus, fourth information indicating at least one of the timer is expired or the session is not active within a period specified by the timer.
In an aspect of the present disclosure, a method for a first core network apparatus includes receiving, from a third core network apparatus, fifth information related to management of a network slice. The method includes starting a timer for the network slice after receiving the fifth information. The method includes sending, to the third core network apparatus, sixth information indicating the management is initiated to start monitoring user plane activity related to a session. The method includes receiving, from the third core network apparatus, seventh information indicating the user plane activity is not detected based on the monitoring. The method includes sending, to the third core network apparatus, eighth information indicating at least one of the timer is expired or the session is not active within a period specified by the timer.
For the purposes of the present document, the abbreviations given in NPL 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in NPL 1.
For the purposes of the present document, the terms and definitions given in NPL 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in NPL 1.
Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.
For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspect illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.
The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by “comprises . . . a” does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase “in an Aspect”, “in another Aspect” and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.
Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.
In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.
As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.
Each of Aspects and elements included in the each Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.
An example object of this disclosure is to provide a method and apparatus that can solve the above problem.
A method of a communication apparatus according to example aspect of this disclosure includes sending a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a second message in a case where the S-NSSAI is not used for a time period. The second message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for the time period. The time period is associated with the S-NSSAI. The method includes sending a third message to remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI). The third message includes the S-NSSAI and the reject cause.
A method of a communication apparatus according to example aspect of this disclosure includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The method includes performing Network Slice Admission Control (NSAC) in a case where the timer expires. The method includes sending a second message after performing the NSAC. The second message includes the S-NSSAI and a reject cause indicating expiry of the timer.
A method of a User Equipment (UE) according to example aspect of this disclosure includes performing a registration for Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a message. The message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for a time period. The time period is associated with the S-NSSAI. The method includes removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) after receiving the message.
A method of a communication apparatus according to example aspect of this disclosure includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The method includes sending a second message for Network Slice Admission Control (NSAC) and a third message in a case where the timer expires. The second message includes the S-NSSAI. The third message includes the S-NSSAI and a reject cause indicating expiry of the timer.
A method of a communication apparatus according to example aspect of this disclosure includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes starting a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The method includes receiving a second message related to establishment of a Protocol Data Unit (PDU) session for the S-NSSAI after starting the timer. The method includes stopping the timer after receiving the second message. The method includes receiving a third message related to release of the PDU session after stopping the timer. The method includes starting the timer after receiving the third message. The method includes sending a fourth message in a case where the timer expires. The fourth message is for removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) or is for deregister the S-NSSAI.
A method of a communication apparatus according to example aspect of this disclosure includes sending a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The method includes starting a timer after receiving the second message. The method includes sending a third message in a case where there is no user plane activity for the PDU session until the timer expires. The third message indicates that there is no user plane activity for the PDU session. The method includes receiving a fourth message after sending the third message. The method includes performing a procedure to release the PDU session after receiving the fourth message.
A method of a communication apparatus according to example aspect of this disclosure includes receiving a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The method includes sending a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The method includes receiving a third message after sending the second message. The third message indicates that there is no user plane activity for the PDU session. The method includes sending a fourth message after receiving the third message. The fourth message is for performing a procedure to release the PDU session.
A communication apparatus according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to send a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to receive a second message in a case where the S-NSSAI is not used for a time period. The second message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for the time period. The time period is associated with the S-NSSAI. The at least one hardware processor is configured to send a third message to remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI). The third message includes the S-NSSAI and the reject cause.
A communication apparatus according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to start a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The at least one hardware processor is configured to perform Network Slice Admission Control (NSAC) in a case where the timer expires. The at least one hardware processor is configured to send a second message after performing the NSAC. The second message includes the S-NSSAI and a reject cause indicating expiry of the timer.
A User Equipment (UE) according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to perform a registration for Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to receive a message. The message includes the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for a time period. The time period is associated with the S-NSSAI. The at least one hardware processor is configured to remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) after receiving the message.
A communication apparatus according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to start a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The at least one hardware processor is configured to send a second message for Network Slice Admission Control (NSAC) and a third message in a case where the timer expires. The second message includes the S-NSSAI. The third message includes the S-NSSAI and a reject cause indicating expiry of the timer.
A communication apparatus according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to start a timer for the S-NSSAI after receiving the first message. The timer is set to a value associated with the S-NSSAI. The at least one hardware processor is configured to receive a second message related to establishment of a Protocol Data Unit (PDU) session for the S-NSSAI after starting the timer. The at least one hardware processor is configured to stop the timer after receiving the second message. The at least one hardware processor is configured to receive a third message related to release of the PDU session after stopping the timer. The at least one hardware processor is configured to start the timer after receiving the third message. The at least one hardware processor is configured to send a fourth message in a case where the timer expires. The fourth message is for removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) or is for deregister the S-NSSAI.
A communication apparatus according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to send a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to receive a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The at least one hardware processor is configured to start a timer after receiving the second message. The at least one hardware processor is configured to send a third message in a case where there is no user plane activity for the PDU session until the timer expires. The third message indicates that there is no user plane activity for the PDU session. The at least one hardware processor is configured to receive a fourth message after sending the third message. The at least one hardware processor is configured to perform a procedure to release the PDU session after receiving the fourth message.
A communication apparatus according to example aspect of this disclosure includes a memory, and at least one hardware processor coupled to the memory. The at least one hardware processor is configured to receive a first message. The first message includes Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to send a second message. The second message includes identity of a Protocol Data Unit (PDU) session. The at least one hardware processor is configured to receive a third message after sending the second message. The third message indicates that there is no user plane activity for the PDU session. The at least one hardware processor is configured to send a fourth message after receiving the third message. The fourth message is for performing a procedure to release the PDU session.
A method of a first core network apparatus according to example aspect of this disclosure includes receiving, from a second core network apparatus, a fourth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the fourth message. The method includes detecting the timer is expired. The method includes sending, to the second core network apparatus, a fifth message indicating at least one of the timers is expired or the network slice related to the timer is not used, after the detecting the timer is expired.
A method of a first core network apparatus according to example aspect of this disclosure includes receiving, from a second core network apparatus, a fourth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the fourth message. The method includes detecting an activity related to the network slice. The method includes stopping the timer after the detecting the activity.
A method of a third core network apparatus according to example aspect of this disclosure includes receiving, from a first core network apparatus, a sixth message related to management of a network. The method includes analysing data related to the network slice based on information receive from other core network apparatus. The method includes starting a timer for the network slice after receiving the sixth message. The method includes detecting the timer is expired. The method includes sending, to the first core network apparatus, a seventh message indicating at least one of the timers is expired or the network slice related to the timer is not used, after the detecting the timer is expired. The first core network apparatus manages network slice admission control.
A method of a third core network apparatus according to example aspect of this disclosure includes receiving, from a first core network apparatus, a sixth message related to management of a network slice. The method includes analysing data related to the network slice based on information receive from other core network apparatus. The method includes starting a timer for the network slice after the receiving the sixth message. The method includes detecting an activity related to the network slice. The method includes stopping the timer after the detecting the activity. The first core network apparatus manages network slice admission control.
A method of a first network slice control function node according to example aspect of this disclosure includes receiving, from a second core network apparatus, an eighth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the eighth message. The method includes detecting the timer is expired. The method includes sending, to the second core network apparatus, a ninth message indicating at least one of the timer is expired or the network slice related to the timer is not used, after the detecting the timer is expired.
A method of a first network slice control function node according to example aspect of this disclosure includes receiving, from a second core network apparatus, a tenth message related to management of a network slice. The method includes starting a timer for the network slice after receiving the tenth message. The method includes receiving, from a second network slice control function node, eleventh message detecting an activity related to the network slice. The method includes stopping the timer after receiving the eleventh message.
A method of a third core network apparatus node according to example aspect of this disclosure includes sending, to a first core network apparatus, first information related to management of a network slice to initiate a control of a number of sessions based on a timer. The method includes receiving, from the first core network apparatus, second information indicating the control is initiated. The method includes monitoring user plane activity related to the sessions after receiving the second information. The method includes sending, to the first core network apparatus, third information indicating the user plane activity is not detected based on the monitoring. The method includes receiving, from the first core network apparatus, fourth information indicating at least one of the timer is expired or the session is not active within a period specified by the timer.
A method of a third first core network apparatus node according to example aspect of this disclosure includes receiving, from a third core network apparatus, fifth information related to management of a network slice. The method includes starting a timer for the network slice after receiving the fifth information. The method includes sending, to the third core network apparatus, sixth information indicating the management is initiated to start monitoring user plane activity related to a session. The method includes receiving, from the third core network apparatus, seventh information indicating the user plane activity is not detected based on the monitoring. The method includes sending, to the third core network apparatus, eighth information indicating at least one of the timer is expired or the session is not active within a period specified by the timer.
The First Aspect discloses a mechanism which enables the network to deregister the UE from a network slice if the network slice is not used for a long time. For example, the First Aspect discloses a mechanism which enables the network to deregister the UE from a network slice if there is no PDU sessions established by the UE on the network slice for a duration of time defined by the network operator. For example, the First Aspect discloses a mechanism which enables the network to deregister the UE from a network slice if the number of UE registrations with the network slice has reached a certain threshold, e.g. the maximum number of UEs registered with the network slice. For example, the First Aspect discloses a mechanism which enables the network to deregister the UE from a network slice if the network slice is overloaded.
For example, the First Aspect can solve the problem whether and how to enhance the system to ensure network-controlled behavior of network slice usage including UE registration and PDU Session establishment.
For example, the First Aspect can solve the problematic situation that the network slice cannot serve at least one of UE(s) and PDU Session(s) with actual activity when performing the NSAC.
For example, the First Aspect can solve the problematic situation when the network slice is used by UE(s) or PDU Session (s).
The First Example of the First Aspect in
If the requested network slices which are identified by S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 and which are requested by the UE 3 are subject to NSAC, the AMF 70 registers the UE 3 for these network slices by sending an Nnsacf_NSAC_NumOfUEsUpdate_Request message to the NSACF 77. The AMF 70 includes in the message the UE 3's identity (e.g. UE-Id), S-NSSAI-1, S-NSSAI-2, S-NSSAI-3 which identify the requested network slices and a parameter called ‘usage control’ set to ON or ‘inactivity control’ set to ON or any other notation for a parameter in order to indicate to the NSACF 77 that the network slice(s) is subject to usage control or subject to inactivity control. The ‘usage control’ set to ON or the ‘inactivity control’ set to ON may indicate that the UE 3 is to be deregistered from the network slice if the network slice is not used by the UE 3 for certain time. “identity” may be expressed as “identifier” in this disclosure.
The ‘usage control’ or the ‘inactivity control’ or any other notation for a parameter in order to indicate to the NSACF 77 that the network slice(s) is subject to usage control or subject to inactivity control may be collectively expressed as ‘usage control’ or ‘usage control’ parameter.
For example, the ‘usage control’ may be related to S-NSSAI(s) that the UE 3 registers. For example, the ‘usage control’ set to ON may be related to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
The AMF 70 may also include, in the Nnsacf_NSAC_NumOfUEsUpdate_Request message, ‘usage control timer’ parameter or ‘inactivity control timer’ parameter or any other notation for a parameter in order to define a time or time period for which if the network slice(s) is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice(s), the UE 3 is to be deregistered from the network slice(s).
The ‘usage control timer’ parameter or the ‘inactivity control timer’ parameter or any other notation for a parameter in order to define a time or time period for which if the network slice(s) is not used by the UE 3, the UE 3 is to be deregistered from the network slice(s) may be collectively expressed as ‘usage control timer’ or ‘usage control timer’ parameter.
For example, the AMF 70 may configure the ‘usage control timer’ parameter based on a local configuration in the AMF 70 or network operator policy within the AMF 70. Alternatively, the ‘usage control timer’ parameter could be configured in the NSACF 77 or the ‘usage control timer’ parameter is based on network operator policy within the NSACF 77. For example, the AMF 70 or the NSACF 77 may determine value of the ‘usage control timer’ parameter.
For example, the ‘usage control timer’ parameter may be related to S-NSSAI(s) that the UE 3 registers. For example, the ‘usage control timer’ may be related to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. Value of the ‘usage control timer’ parameter may be same to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 or be different for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. Value of the ‘usage control timer’ parameter may be expressed as a value associated with S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
For example, the AMF 70 may send the Nnsacf_NSAC_NumOfUEsUpdate_Request message during a registration procedure for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. For example, the AMF 70 may send, to the NSACF 77, a message related to a network slice. For example, the AMF 70 may send, to the NSACF 77, a message related to management of a network slice. For example, the AMF 70 may send, to the NSACF 77, a message related to management of a number of UE(s) registered with a network slice.
The Nnsacf_NSAC_NumOfUEsUpdate_Request message may be sent for the NSAC.
For example, the NSACF 77 may not start the usage control timer for network slice(s) (e.g. S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3) in a case where the number of registered UEs on the network slice(s) exceeds the maximum number of the UEs allowed to register with that network slice(s) or a threshold number defined by the operator. In this case, the NSACF 77 may send, to the AMF 70, information indicating that the UE identified by the UE-Id cannot be registered to the network slice(s).
If the network slice for which the UE 3 registers for is subject to usage or inactivity control, e.g. the ‘usage control’ parameter from the AMF 70 is set ON, the NSACF 77 starts a timer which measures the time for which a network slice has not been used by the UE 3, e.g. for which no service is requested or no PDU session is established by the UE 3 on that network slice or no data was exchanged on an established PDU session. The timer may be called as, for example, ‘usage control timer’ or ‘inactivity control timer’ or any other notation for a timer. The ‘usage control timer’ or the ‘inactivity control timer’ or any other notation for a timer may be collectively expressed as ‘usage control timer’.
The ‘usage control timer’ or the ‘inactivity control timer’ may be set to a value configured in the NSACF 77 by the operator. The ‘usage control timer’ or ‘the ‘inactivity control timer’ may be set to a value indicated by the AMF 70 in the ‘usage control timer’ parameter or the ‘inactivity control timer’ parameter.
The NSACF 77 runs the ‘usage control timer’ for each network slice which is subject to usage control, e.g. a network slice for which the ‘usage control’ parameter is set to ON. For example, the NSACF 77 runs the ‘usage control timers’ for at least one of S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. The ‘usage control timer’ may be controlled per UE in this disclosure. For example, the NSACF 77 may control the ‘usage control timer’ per UE identified by the UE-Id. For example, the NSACF 77 may run the ‘usage control timers’ regarding at least one of S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 for the UE 3.
When the UE 3 stops using network slices identified by S-NSSAI-1 and S-NSSAI-2, i.e. the UE 3 releases the PDU session(s) on S-NSSAI-1 and S-NSSAI-2, the NSACF 77 re-starts the usage control timers for S-NSSAI-1 and S-NSSAI-2. For example, in a case where the NSACF 77 receives release notification for the PDU session(s) on S-NSSAI-1 and S-NSSAI-2 from the SMF 71, the NSACF 77 may re-start the usage control timers for S-NSSAI-1 and S-NSSAI-2.
The NSACF 77 also updates the number of the UEs registered with S-NSSAI-3 by decreasing the number of the registered UEs with S-NSSAI-3 by 1 and also the NSACF 77 removes the UE 3's identity, e.g. the UE-Id from a list of the UEs registered with S-NSSAI-3.
For example, in a case where the NSACF 77 updates the number of the UEs registered with S-NSSAI-3, the NSACF 77 may perform quota control (e.g. NSAC) for the registered UEs as per clause 4.2.11 of NPL 3.
For example, the NSACF 77 may send the Nnsacf_NSAC_DeregistrationNotification message in a case where the ‘usage control timer’ for S-NSSAI-3 for the UE 3 expires.
For example, the NSAC (e.g. decrement or decreasing the number of the registered UEs with S-NSSAI-3 by 1) by the NSACF 77 may be performed in a case where the ‘usage control timer’ for S-NSSAI-3 for the UE 3 expires.
For example, the NSAC (e.g. decrement or decreasing the number of the registered UEs with S-NSSAI-3 by 1) by the NSACF 77 may be performed in a case where time period indicated by the ‘usage control timer’ parameter lapses.
The AMF 70 also includes, in the UCU message, a reject cause for S-NSSAI-3, e.g. reject cause which is set to ‘usage control timer expired’ or ‘inactivity control timer expired’ or any other notation for a reject cause in order to indicate that the rejection is due to a network slice not being used by the UE 3 until the expiry of the usage control timer for the UE 3 for that network slice. The reject cause may be same to one in the Nnsacf_NSAC_DeregistrationNotification message. The reject cause may indicate same one in the Nnsacf_NSAC_DeregistrationNotification message.
Alternatively, the AMF 70 may use existing UE deregistration procedure by sending Deregistration Request message to the UE 3 in which the AMF 70 includes the network slice, e.g. S-NSSAI-3 for which the UE 3 is rejected from registration and a reject cause which is set to ‘usage control timer expired’.
Upon receiving the Nnsacf_NSAC_DeregistrationNotification message, if the UE 3 is in idle mode, the AMF 70 either:
The AMF 70 may store information indicating whether the UE 3 is in connected mode or is in idle mode. The AMF 70 may receive information indicating whether the UE 3 is in connected mode or is in idle mode from other network node. The AMF 70 may determine whether the UE 3 is in connected mode or is in idle mode based on the information indicating whether the UE 3 is in connected mode or is in idle mode. The UCU message or the Deregistration Request message may be sent for at least one of removing S-NSSAI-3 from the Allowed NSSAI and adding S-NSSAI-3 to the Rejected NSSAI.
For example, a communication apparatus corresponding to the AMF 70 may send a first message. The first message may include Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus may receive a second message in a case where the S-NSSAI is not used for a time period. The second message may include the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for the time period. The time period may be associated with the S-NSSAI. The communication apparatus may send a third message to remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI). The third message may include the S-NSSAI and the reject cause.
For example, a communication apparatus corresponding to the NSACF 77 may receive a first message. The first message may include Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus may start a timer for the S-NSSAI after receiving the first message. The timer may be set to a value associated with the S-NSSAI. The communication apparatus may perform Network Slice Admission Control (NSAC) in a case where the timer expires. The communication apparatus may send a second message after performing the NSAC. The second message may include the S-NSSAI and a reject cause indicating expiry of the timer.
For example, a User Equipment (UE) corresponding to the UE 3 may perform a registration for Single Network Slice Selection Assistance Information (S-NSSAI). The UE may receive a message. The message may include the S-NSSAI and a reject cause indicating that the S-NSSAI is not used for a time period. The time period may be associated with the S-NSSAI. The UE may remove the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) after receiving the message.
For example, a first core network apparatus corresponding to the NSACF 77 may receive, from a second core network apparatus corresponding to the AMF 70, a message related to management of a network slice. The first core network apparatus may start a timer for the network slice after receiving the message. The first core network apparatus may detect the timer is expired. The first core network apparatus may send, to the second core network apparatus, a message indicating at least one of the timer is expired or the network slice related to the timer is not used, after detecting the timer is expired.
For example, a first core network apparatus corresponding to the NSACF 77 may receive, from a second core network apparatus corresponding to the AMF 70, a message related to management of a network slice. The first core network apparatus may start a timer for the network slice after receiving the message. The first core network apparatus may detect an activity related to the network slice. The first core network apparatus may stop the timer after detecting the activity
According to the above, the above problem such as whether and how to enhance the system to ensure network-controlled behavior of network slice usage including UE registration and PDU Session establishment can be solved.
In step 8 of
The NSACF 77 may trigger the Nnsacf_NSAC_DeregistrationNotification message to AMF 70 when the number of UEs registered with S-NSSAI-3 has reached a threshold value, e.g. maximum number of UEs registered with S-NSSAI-3. The case where the number of UEs registered with S-NSSAI-3 has reached a threshold value, e.g. maximum number of UEs registered with S-NSSAI-3 may mean the network slice identified by S-NSSAI-3 is overloaded. In this case the rejection cause in the Nnsacf_NSAC_DeregistrationNotification message indicates that the maximum number of UEs registered with a network slice, e.g. S-NSSAI-3 has been reached. The AMF 70 delivers the rejected S-NSSAI-3 and the new reject cause which is set to ‘maximum number of UEs registered with a network slice has been reached’ to the UE 3 in step 9 and the UE 3 removes the rejected network slice, e.g. S-NSSAI-3 from the Allowed NSSAI. The reject cause which is set ‘maximum number of UEs registered with a network slice has been reached’ to may indicate that the maximum number of UEs registered with a network slice, e.g. S-NSSAI-3 has been reached. In addition, the Nnsacf_NSAC_DeregistrationNotification message may include a back-off timer parameter for the rejected network slice, e.g. S-NSSAI-3. The back-off timer parameter may be included in the UCU message or the Deregistration Request message. If the back-off timer parameter is included in the UCU message or the Deregistration Request message by the AMF 70, the UE 3 starts a timer with the value provided in the back-off timer parameter and the UE 3 does not attempt another registration for the rejected network slice, e.g. S-NSSAI-3 while the timer is still running. The UE 3 may attempt another registration for the rejected network slice, e.g. S-NSSAI-3 in a case where the timer expires.
In step 9 of
When UE 3 releases the PDU session(s) on S-NSSAI-1 and S-NSSAI-2 that is established in step 4, the SMF 71 contacts to the NSACF 77 for PDU sessions quota control. For example, the SMF 71 may contact to the NSACF 77 for PDU sessions quota control in a case where the SMF 71 receives, from other nodes (e.g. the UE 3), notification regarding releasing the PDU session(s) on S-NSSAI-1 and S-NSSAI-2.
In this case, the NSACF 77 re-starts the usage control timers for S-NSSAI-1 and S-NSSAI-2 for the UE 3 as associated PDU session(s) are released.
In step 2, the Nnsacf_NSAC_NumOfUEsUpdate_Request message may not include the usage control parameter.
For example, the NSACF 77 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfUEsUpdate_Request message is subject to usage control or subject to inactivity control based on inclusion of the S-NSSAI(s) and the usage control timer parameter.
In a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter in step 2, the NSACF 77 may start the usage control timers for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 in step 3 and the subsequent processes may be performed in accordance with the First Example of the First Aspect.
In step 2, the Nnsacf_NSAC_NumOfUEsUpdate_Request message may not include the usage control parameter and the usage control timer parameter.
For example, the NSACF 77 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfUEsUpdate_Request message is subject to usage control or subject to inactivity control based on reception of the Nnsacf_NSAC_NumOfUEsUpdate_Request message.
In a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter and the usage control timer parameter in step 2, the NSACF 77 may start the usage control timers for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 in step 3 and the subsequent processes may be performed in accordance with the First Example of the First Aspect. In this case, the NSACF 77 may configure value of the usage control timer(s) based on local configuration of the NSACF 77 or operator's policy stored in the NSACF 77.
The Second Example of the First Aspect in
If the requested network slices which are identified by S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 and which are requested by the UE 3 are subject to NSAC, the AMF 70 registers the UE 3 for these network slices by sending an Nnsacf_NSAC_NumOfUEsUpdate_Request message to the NSACF 77. The AMF 70 includes in the message the UE 3's identity (e.g. UE-Id), S-NSSAI-1, S-NSSAI-2, S-NSSAI-3 which identify the requested network slices and a parameter called ‘usage control’ set to ON or ‘inactivity control’ set to ON or any other notation for a parameter in order to indicate to the NSACF 77 that the network slice(s) is subject to usage control or inactivity control. The ‘usage control’ set to ON or the ‘inactivity control’ set to ON may indicate that the UE 3 is to be deregistered from the network slice if the network slice is not used by the UE 3 for certain time.
The ‘usage control’ or the ‘inactivity control’ or any other notation for a parameter in order to indicate to the NSACF 77 that the network slice(s) is subject to usage control or subject to inactivity control may be collectively expressed as ‘usage control’ or ‘usage control’ parameter.
For example, the ‘usage control’ may be related to S-NSSAI(s) that the UE 3 registers. For example, the ‘usage control’ set to ON may be related to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
The AMF 70 may also include, in the Nnsacf_NSAC_NumOfUEsUpdate_Request message, ‘usage control timer’ parameter or ‘inactivity control timer’ parameter or any other notation for a parameter in order to define a time or time period for which if the network slice(s) is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice(s), the UE 3 is to be deregistered from the network slice(s).
The ‘usage control timer’ parameter or the ‘inactivity control timer’ parameter or any other notation for a parameter in order to define a time or time period for which if the network slice(s) is not used by the UE 3, the UE 3 is to be deregistered from the network slice(s) may be collectively expressed as ‘usage control timer’ or ‘usage control timer’ parameter.
For example, the AMF 70 may configure the ‘usage control timer’ parameter based on a local configuration in the AMF 70 or network operator policy within the AMF 70. Alternatively, the ‘usage control timer’ parameter could be configured in the NSACF 77 or the ‘usage control timer’ parameter is based on network operator policy within the NSACF 77. For example, the AMF 70 or the NSACF 77 may determine value of the ‘usage control timer’ parameter.
For example, the ‘usage control timer’ parameter may be related to S-NSSAI(s) that the UE 3 registers. For example, the ‘usage control timer’ may be related to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. Value of the ‘usage control timer’ parameter may be same to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 or be different for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. Value of the ‘usage control timer’ parameter may be expressed as a value associated with S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
For example, the AMF 70 may send the Nnsacf_NSAC_NumOfUEsUpdate_Request message during a registration procedure for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
The NSACF 77 may start the quota control for the network slices provided by the AMF 70, e.g. S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. For example, the NSACF 77 may start control for the maximum number of the registered UEs for these network slices as per clause 4.2.11 in NPL 3. If the provided network slices, e.g. S-NSSAI-1, S-NSSAI-2, S-NSSAI-3 by the AMF 70 are subject to usage control, e.g. indicated by the AMF 70 via ‘usage control’ parameter set to ON or indicated by a configuration in the NSACF 77 (e.g. if the NSACF 77 receives the ‘usage control’ parameter set to ON or indicated by a configuration in the NSACF 77), the NSACF 77 sends an Nnwdaf_SliceUsageControl message including UE_Id, S-NSSAI-1, S-NSSAI-2, S-NSSAI-3, usage control which is set to ON and usage control timer to the NWDAF 76. For example, the NWDAF 76 analyzes the usage of the network slices per UE, e.g. UE 3 or per multiple UEs based on inputs from one or multiple NSACFs and other network functions as AMF, e.g. AMF 70 and SMF, e.g. SMF 71, for example. For example, the NWDAF 76 analyzes data related to a network based on other factors to the network slice, for example, network slice congestion. The NSACF 77 may include in the Nnwdaf_SliceUsageControl message parameters mentioned below:
For example, the NSACF 77 may send, to the NWDAF 76, a message related to a network slice. For example, the NSACF 77 may send, to the NWDAF 76, a message related to management of a network slice. For example, the NSACF 77 may send, to the NWDAF 76, a message related to management of a number of UE(s) registered with a network slice.
If the network slice for which the UE 3 registers for is subject to usage or inactivity control, e.g. if the ‘usage control’ parameter from the NSACF 77 in the Nnwdaf_SliceUsageControl message is set to ON, the NWDAF 76 starts a timer which measures time for which a network slice has not been used by the UE 3, e.g. for which no service is requested or no PDU session is established by the UE 3 on that network slice or no data was exchanged on an established PDU session. The timer may be called as, for example, ‘usage control timer’ or ‘inactivity control timer’ or any other notation for a timer. The ‘usage control timer’ or the ‘inactivity control timer’ or any other notation for a timer may be collectively expressed as ‘usage control timer’.
The ‘usage control timer’ or ‘the ‘inactivity control timer’ may be set to a value configured in the NWDAF 76 by the operator. The ‘usage control timer’ may be configured within the NWDAF 76 or be based on the operator policy in the NWDAF 76. For example, the NWDAF 76 may determine value of the ‘usage control timer’ timer based on the operator policy or local configuration in the NWDAF 76. The ‘usage control timer’ or ‘the ‘inactivity control timer’ may be set to a value indicated by the AMF 70 in the ‘usage control timer’ parameter or ‘inactivity control timer’ parameter. The ‘usage control timer’ or ‘the ‘inactivity control timer’ may be set to a value indicated by the NSACF 77 in the usage control timer. The NWDAF 76 runs the ‘usage control timer’ for each network slice which is subject to usage control, e.g. a network slice for which the ‘usage control’ parameter is set to ON. For example, the NWDAF 76 runs the ‘usage control timers’ for at least one of S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. The ‘usage control timer’ may be controlled per UE by the NWDAF 76. For example, the NWDAF 76 may control the ‘usage control timer’ per UE identified by the UE-Id. For example, the NWDAF 76 may run the ‘usage control timers’ regarding at least one of S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 for the UE 3.
For example, the NSACF 77 may send, to the NWDAF 76, a message related to a network slice. For example, the NSACF 77 may send, to the NWDAF 76, a message related to management of a network slice. For example, the NSACF 77 may send, to the NWDAF 76, a message related to management of a number of UE(s) registered with a network slice. For example, the NSACF 77 may send, to the NWDAF 76, a message related to PDU session(s). For example, the NSACF 77 may send, to the NWDAF 76, a message indicating PDU session(s) has been established. For example, the NSACF 77 may send, to the NWDAF 76, a message indicating PDU session(s) related to at least one of the S-NSSAI-1 and S-NSSAI-2 has been established. For example, the NWDAF 76 detects an activity related to a network slice (e.g. an activity related to a network slice identified by S-NSSAI-1 or S-NSSAI-2).
When the UE 3 stops using network slices identified by S-NSSAI-1 and S-NSSAI-2, i.e. the UE 3 releases the PDU session(s) on S-NSSAI-1 and S-NSSAI-2, the NWDAF 76 re-starts the usage control timers for S-NSSAI-1 and S-NSSAI-2. For example, in a case where the NSACF 77 receives release notification for the PDU session(s) on S-NSSAI-1 and S-NSSAI-2 from the SMF 71, the NSACF 77 may send the release notification to the NWDAF 76. In a case where the NWDAF 76 receives the release notification, the NWDAF 76 may re-start the usage control timers for S-NSSAI-1 and S-NSSAI-2. The release notification may be an Nnwdaf_SliceUsageControl message. The Nnwdaf_SliceUsageControl message in case of informing the release of the PDU session(s) may include UE-Id (e.g. identity of the UE 3), one or more network slices parameter and “PDU session released” parameter. The one or more network slices parameter may indicate that network slice(s) that PDU session(s) has been released (e.g. network slice identity related to released PDU session(s). e.g. S-NSSAI-1 and S-NSSAI-2). The “PDU session released” parameter may indicate that PDU session(s) that is related to the associated network slice(s) (e.g. network slices identified by S-NSSAI-1 and S-NSSAI-2) has been released. The PDU session released parameter may indicate that PDU session(s) related to S-NSSAI-1 and S-NSSAI-2 has been established.
The Nnwdaf_DeregistrationRequest message may be sent for the NSACD 77.
The AMF 70 also includes, in the UCU message, a reject cause for S-NSSAI-3, e.g. reject cause which is set to ‘usage control timer expired’ or ‘inactivity control timer expired’ or any other notation for a reject cause in order to indicate that the rejection is due to a network slice not being used by the UE 3 until the expiry of the usage control timer for the UE 3 for that network slice.
Alternatively, the AMF 70 may use existing UE deregistration procedure by sending Deregistration Request to the UE 3 in which the AMF 70 includes the network slice, e.g. S-NSSAI-3 for which the UE 3 is rejected from registration and a reject cause which is set to ‘usage control timer expired’.
Upon receiving the Nnwdaf_DeregistrationNotification message, if the UE 3 is in idle mode, the AMF 70 either:
The AMF 70 may store information indicating whether the UE 3 is in connected mode or is in idle mode. The AMF 70 may receive information indicating whether the UE 3 is in connected mode or is in idle mode from other network node. The AMF 70 may determine whether the UE 3 is in connected mode or is in idle mode based on the information indicating whether the UE 3 is in connected mode or is in idle mode.
For example, a communication apparatus corresponding to the NWDAF 76 may receive a first message. The first message may include Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus may start a timer for the S-NSSAI after receiving the first message. The timer may be set to a value associated with the S-NSSAI. The communication apparatus may send a second message for Network Slice Admission Control (NSAC) and a third message in a case where the timer expires. The second message may include the S-NSSAI. The third message may include the S-NSSAI and a reject cause indicating expiry of the timer.
For example, a first core network apparatus corresponding to the NWDAF 76 may receive, from a second core network apparatus corresponding to NSACF 77, a message related to management of a network slice. The first core network apparatus may analyse data related to the network slice based on information from other core network apparatus corresponding to at least one of the second core network apparatus, the AMF 70 and the SMF 71. The first core network apparatus may start a timer for the network slice after receiving the message. The first core network apparatus may detect the timer is expired. The first core network apparatus may send, to the second core network apparatus, a message indicating at least one of the timer is expired or the network slice related to the timer is not used, after the detecting the timer is expired. The second core network apparatus may manage network slice admission control.
For example, a first core network apparatus corresponding to the NWDAF 76 may receive, from a second core network apparatus corresponding to NSACF 77, a message related to management of a network slice. The first core network apparatus may analyse data related to the network slice based on information from other network apparatus corresponding to at least one of the second core network apparatus, the AMF 70 and the SMF 71. The first core network apparatus may start a timer for the network slice after receiving the message. The first core network apparatus may detect an activity related to the network slice. The first core network apparatus may stop the timer after detecting the activity. The second core network apparatus may manage network slice admission control.
According to the above, the above problem such as whether and how to enhance the system to ensure network-controlled behavior of network slice usage including UE registration and PDU Session establishment can be solved.
In step 11 of
The NWDAF 76 may trigger the Nnwdaf_NSAC_DeregistrationNotification message to AMF 70 when the number of UEs registered with S-NSSAI-3 has reached a threshold value, e.g. maximum number of UEs registered with S-NSSAI-3. The case where the number of UEs registered with S-NSSAI-3 has reached a threshold value, e.g. maximum number of UEs registered with S-NSSAI-3 may mean the network slice identified by S-NSSAI-3 is overloaded. For example, this may be indicated to the NWDAF 76 from the NSACF 77 via an Nnsacf_MaxRegisteredUEs message including S-NSSAI-3 or any other notation for a message from the NSACF 77 to the NWDAF 76 with a purpose to indicate that the number of the registered UEs with a network slice, e.g. S-NSSAI-3, has reached its maximum. In this case the rejection cause in the Nnwdaf_NSAC_DeregistrationNotification message indicates that the maximum number of UEs registered with a network slice, e.g. S-NSSAI-3 has been reached. The AMF 70 delivers the rejected S-NSSAI-3 and the new reject cause which is set to ‘maximum number of UEs registered with a network slice has been reached’ to the UE 3 in step 12 and the UE 3 removes the rejected network slice, e.g. S-NSSAI-3 from the Allowed NSSAI. The reject cause which is set ‘maximum number of UEs registered with a network slice has been reached’ to may indicate that the maximum number of UEs registered with a network slice, e.g. S-NSSAI-3 has been reached. In addition, the Nnwdaf_NSAC_DeregistrationNotification message may include a back-off timer parameter for the rejected network slice, e.g. S-NSSAI-3. If the back-off timer parameter is included in the UCU message or the Deregistration Request message by the AMF 70, the UE 3 starts a timer with the value provided in the back-off timer parameter and the UE 3 does not attempt another registration for the rejected network slice, e.g. S-NSSAI-3 while the timer is still running. The UE 3 may attempt another registration for the rejected network slice, e.g. S-NSSAI-3 in a case where the timer expires.
In step 12 of
When UE 3 releases the PDU session(s) on S-NSSAI-1 and S-NSSAI-2 that is established in step 5, the SMF 71 contacts to the NWDAF 76 for Slice Usage Notification. For example, the SMF 71 may contact to the NWDAF 76 for Slice Usage Notification in a case where the SMF 71 receives, from other nodes (e.g. the UE 3), notification regarding releasing the PDU session(s) on S-NSSAI-1 and S-NSSAI-2.
In this case, the NWDAF 76 re-starts the usage control timers for S-NSSAI-1 and S-NSSAI-2 for the UE 3 as associated PDU session(s) are released.
In step 2, the Nnsacf_NSAC_NumOfUEsUpdate_Request message may not include the usage control parameter.
For example, the NSACF 77 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfUEsUpdate_Request message is subject to usage control or subject to inactivity control based on inclusion of the S-NSSAI(s) and the usage control timer parameter.
In a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter in step 2, the NSACF 77 may send, to the NWDAF 76, the Nnwdaf_SliceUsageControl message without the usage control parameter in step 3. Then the NWDAF 76 may start the usage control timers for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 in step 4 and the subsequent processes may be performed in accordance with the Second Example of the First Aspect.
In step 2, the Nnsacf_NSAC_NumOfUEsUpdate_Request message may not include the usage control parameter and the usage control timer parameter.
For example, the NSACF 77 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfUEsUpdate_Request message is subject to usage control or subject to inactivity control based on reception of the Nnsacf_NSAC_NumOfUEsUpdate_Request message.
For example, the NWDAF 76 may understand that network slice(s) identified by S-NSSAI(s) in the Nnwdaf_SliceUsageControl message is subject to usage control or subject to inactivity control based on reception of the Nnwdaf_SliceUsageControl message.
In a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter and the usage control timer parameter in step 2, the NSACF 77 may send, to the NWDAF 76, the Nnwdaf_SliceUsageControl message without the usage control parameter and the usage control timer parameter in step 3. Then the NWDAF 76 may start the usage control timers for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 in step 4 and the subsequent processes may be performed in accordance with the Second Example of the First Aspect. In this case, the NWDAF 76 may configure value of the usage control timer(s) based on local configuration of the NWDAF 76 or operator's policy stored in the NWDAF 76.
In another example, in a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter and the usage control timer parameter in step 2, the NSACF 77 may configure value of the usage control timer(s) based on local configuration of the NSACF 77 or operator's policy stored in the NSACF 77 and send the Nnwdaf_SliceUsageControl message including the value of the usage control timer(s) to the NWDAF 76.
The NWDAF 76 may send two messages, the Nnwdaf_NSAC_DeregistrationRequest message (or the Nnwdaf_DeregistrationRequest message) and the Nnwdaf_NSAC_DeregistrationNotification message to the NSACF 77 and AMF 70 respectively, when the NWDAF 76 detects that S-NSSAI becomes congested (e.g. in a case where the number of UEs registered with the S-NSSAI which identifies a congested network slice has reached a threshold value, e.g. maximum number of UEs registered with the S-NSSAI). The S-NSSAI which identifies the congested network slice may be expressed as congested S-NSSAI. In this case, the NWDAF 76 sends multiple two messages to multiple NSACFs 77 including the congested S-NSSAI and registered UE IDs to the congested S-NSSAI and reject cause indicating that network slice congested.
Once the NSACF 77 (e.g. each of NSACFs 77) receives the Nnwdaf_NSAC_DeregistrationRequest message that includes multiple UE IDs, then the NSACF 77 may deregister all indicated UEs for indicated network slice by the congested S-NSSAI and may reduce the number of UEs registered with the congested S-NSSAI by the number of the indicated UEs for the congested S-NSSAI.
Once the AMF 70 receives the Nnwdaf_NSAC_DeregistrationNotification message that includes multiple UE IDs, then the AMF 70 performs the UE Configuration Update procedure as described in step 12 for all UEs included in the received Nnwdaf_NSAC_DeregistrationNotification message with reject cause indicating that network slice congested.
The NWDAF 76 may not send the Nnwdaf_NSAC_DeregistrationNotification message (or the Nnwdaf_DeregistrationRequest message) to AMF 70 as described in step 11. In this case, upon reception of the Nnwdaf_NSAC_DeregistrationRequest message (or the Nnwdaf_DeregistrationRequest message) in the NSACF 77, the NSACF 77 sends the Nnsacf_NSAC_DeregistrationNotification message to associated AMF(s) as described in the step 8 in the first Example of the First Aspect for all UEs included in the received Nnwdaf_NSAC_DeregistrationRequest message (or the Nnwdaf_DeregistrationRequest message) with reject cause indicating that network slice congested or usage control timer expired.
The NWDAF 76 may be another NSACF from the NSACF 77. Another NSACF may reside in the PLMN or another HPLMN. In this case the following message name changes apply:
The Third Example of the First Aspect in
If the requested network slices which are identified by S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 and which are requested by the UE 3 are subject to NSAC, the AMF 70 registers the UE 3 for these network slices by sending an Nnsacf_NSAC_NumOfUEsUpdate_Request message to the NSACF 7701. The AMF 70 includes in the message the UE 3's identity (e.g. UE-Id), S-NSSAI-1, S-NSSAI-2, S-NSSAI-3 which identify the requested network slices and a parameter called ‘usage control’ set to ON or ‘inactivity control’ set to ON or any other notation for a parameter in order to indicate to the NSACF 7701 that the network slice(s) is subject to usage control or inactivity control. The ‘usage control’ set to ON or the ‘inactivity control’ set to ON may indicate that the UE 3 is to be deregistered from the network slice if the network slice is not used by the UE 3 for certain time.
The ‘usage control’ or the ‘inactivity control’ or any other notation for a parameter in order to indicate to the NSACF 77 that the network slice(s) is subject to usage control or subject to inactivity control may be collectively expressed as ‘usage control’ or ‘usage control’ parameter.
For example, the ‘usage control’ may be related to S-NSSAI(s) that the UE 3 registers. For example, the ‘usage control’ set to ON may be related to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
The AMF 70 may also include, in the Nnsacf_NSAC_NumOfUEsUpdate_Request message, ‘usage control timer’ parameter or ‘inactivity control timer’ parameter or any other notation for a parameter in order to define a time or time period for which if the network slice(s) is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice(s), the UE 3 is to be deregistered from the network slice(s).
The ‘usage control timer’ parameter or the ‘inactivity control timer’ parameter or any other notation for a parameter in order to define a time or time period for which if the network slice(s) is not used by the UE 3, the UE 3 is to be deregistered from the network slice(s) may be collectively expressed as ‘usage control timer’ or ‘usage control timer’ parameter.
For example, the AMF 70 may configure the ‘usage control timer’ parameter based on a local configuration in the AMF 70 or network operator policy within the AMF 70. Alternatively, the ‘usage control timer’ parameter could be configured in the NSACF 7701 or the ‘usage control timer’ parameter is based on network operator policy within the NSACF 7701. For example, the AMF 70 or the NSACF 7701 may determine value of the ‘usage control timer’ parameter.
For example, the ‘usage control timer’ parameter may be related to S-NSSAI(s) that the UE 3 registers. For example, the ‘usage control timer’ may be related to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. Value of the ‘usage control timer’ parameter may be same to S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 or be different for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. Value of the ‘usage control timer’ parameter may be expressed as a value associated with S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3.
For example, the AMF 70 may send the Nnsacf_NSAC_NumOfUEsUpdate_Request message during a registration procedure for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. For example, the AMF 70 may send, to the NSACF 7701, a message related to a network slice. For example, the AMF 70 may send, to NSACF 7701, a message related to management of a network slice. For example, the AMF 70 may send, to the NSACF 7701, a message related to management of a number of UE(s) registered with a network slice.
If the network slice for which the UE 3 registers for is subject to usage control or inactivity control, e.g. the ‘usage control’ parameter from the AMF 70 is set to ON, the NSACF 7701 starts a timer which measures time for which a network slice has not been used by the UE 3, e.g. for which no service is requested or no PDU session is established by the UE 3 on that network slice or no data was exchanged on an established PDU session. The timer may be called as, for example, ‘usage control timer’ or ‘inactivity control timer’ or any other notation for a timer. The ‘usage control timer’ or the ‘inactivity control timer’ or any other notation for a timer may be collectively expressed as ‘usage control timer’.
The ‘usage control timer’ or ‘the ‘inactivity control timer’ may be set to a value configured in the NSACF 7701 by the operator. The ‘usage control timer’ or ‘the ‘inactivity control timer’ may be set to a value indicated by the AMF 70 in the ‘usage control timer’ parameter or the ‘inactivity control timer’ parameter.
The NSACF 7701 runs a the ‘usage control timer’ for each network slice which is subject to usage control, e.g. a network slice for which the ‘usage control’ parameter is set to ON. For example, the NSACF 7701 runs the ‘usage control timers’ for at least one of S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. The ‘usage control timer’ may be controlled per UE by the NSACF 7701. For example, the NSACF 7701 may control the ‘usage control timer’ per UE identified by the UE-Id. For example, the NSACF 7701 may run the ‘usage control timers’ regarding at least one of S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 for the UE 3.
For example, the UE-Id may be UE 3's identity.
For example, the PDU-Id may be identity of an active PDU session on a network slice.
The identity of an active PDU session may be expressed as an active PDU session identity.
For example, the PDU-Id may be active PDU session identity on a network slice.
For example, the PDU-Id may be active PDU session identity on a network slice identified by the network slice identity.
For example, the PDU-Id may be active PDU session identity on a network slice identified by S-NSSAI-3.
For example, the PDU-Id with value which is set to ON may mean that a PDU session identified by the PDU-Id is active on a network slice identified by the network slice identity.
For example, the PDU-Id with value which is set to ON may mean that a PDU session identified by the PDU-Id is active on a network slice identified by S-NSSAI-3.
For example, the network slice identity on which there is an active PDU session may be S-NSSAI-3. For example, in a case where the NSACF 7702 receives a message indicating an activity related to the network slice identified by S-NSSAI-3, the NSACF 7702 may send, to the NSACF 7701, a message indicating detection of an activity related to the network slice identified by S-NSSAI-3.
“the PDU-Id with value which is set to ON” may be expressed as “PDU-Id=ON”.
The Nnsacf_SliceUsageNotify message may be expressed as a message related to establishment of PDU session(s) for S-NSSAI-3.
For example, the UE-Id may be UE 3's identity.
For example, the PDU-Id may be identity of a released PDU session on a network slice.
The identity of a released PDU session may be expressed as released PDU session identity.
For example, the PDU-Id may be released PDU session identity on a network slice.
For example, the PDU-Id may be released PDU session identity on a network slice identified by the network slice identity.
For example, the PDU-Id may be released PDU session identity on a network slice identified by S-NSSAI-3.
For example, the PDU-Id with value which is set to OFF may mean that a PDU session identified by the PDU-Id is released on a network slice identified by the network slice identity.
For example, the PDU-Id with value which is set to OFF may mean that a PDU session identified by the PDU-Id is released on a network slice identified by S-NSSAI-3.
For example, the network slice identity regarding the released PDU session may be network slice identity of a network slice that there was the active PDU session.
For example, the network slice identity regarding the released PDU session may be S-NSSAI-3.
“the PDU-Id with value which is set to OFF” may be expressed as “PDU-Id=OFF”.
The Nnsacf_SliceUsageNotify message in step 8 may be expressed as a message related to release of PDU session(s) for S-NSSAI-3.
For example, after the step 10, the NSACF 7701 may send, to the AMF 70, a message indicating a network slice (e.g. a network slice identified by S-NSSAI-3) is not used.
The AMF 70 may deregister the UE 3 from the network slice which the UE 3 has not used for some time, e.g. S-NSSAI-3 by removing S-NSSAI-3 from the Allowed NSSAI for the UE 3 and adding S-NSSAI-3 to the Rejected NSSAI as described in steps 11 and 12 of the Second Example of the First Aspect.
The AMF 70 may keep the UE 3 registered with the network slice that was reported as inactive or not used e.g. S-NSSAI-3 and mark the network slice identified by S-NSSAI-3 as inactive or not used in the UE 3's context within the AMF 70. The AMF 70 may deregister that network slice, e.g. S-NSSAI-3 from the NSACF 7701 as per clause 4.2.11 of NPL 3 so that S-NSAAI-3 is not counted for the quota control purposes as S-NSSAI-3 is not active or not being used for certain time. As soon as the inactive network slice, e.g. S-NSSAI-3 is used again by the UE 3, e.g. a PDU session is established on S-NSSAI-3, the AMF 70 registers back that network slice with the NSACF 7701 for the purposes of the quota control. For example, in a case where the AMF 70 may determine that the inactive network slice, e.g. S-NSSAI-3 is used again by the UE 3, the AMF 70 may instruct the NSACF 7701 to count the UE 3 for the quota control. For example, the AMF 70 may determine that the inactive network slice, e.g. S-NSSAI-3 is used again by the UE 3 in a case where the AMF 70 receives, from other network node (e.g. the SMF 71 or the UE 3) information indicating that the inactive network slice, e.g. S-NSSAI-3 is used again by the UE 3.
The Nnsacf_SliceUsageNotification message may be expressed as a message for removing S-NSSAI-3 from the Allowed NSSAI. The Nnsacf_SliceUsageNotification message may be expressed as a message for adding S-NSSAI-3 to the Rejected NSSAI. The Nnsacf_SliceUsageNotification message may be expressed as a message for deregister S-NSSAI-3.
For example, a communication apparatus corresponding to the NSACF 7701 may receive a first message. The first message may include Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus may start a timer for the S-NSSAI after receiving the first message. The timer may be set to a value associated with the S-NSSAI. The communication apparatus may receive a second message related to establishment of a Protocol Data Unit (PDU) session for the S-NSSAI after starting the timer. The communication apparatus may stop the timer after receiving the second message. The communication apparatus may receive a third message related to release of the PDU session after stopping the timer. The communication apparatus may start the timer after receiving the third message. The communication apparatus may send a fourth message in a case where the timer expires. The fourth message may be for removing the S-NSSAI from an Allowed Network Slice Selection Assistance Information (NSSAI) or may be for deregister the S-NSSAI.
For example, a first network slice control function node corresponding to the NSACF 7701 may receive, from a core network apparatus corresponding to the AMF 70, a message related to management of a network slice. The first network slice control function node may start a timer for the network slice after receiving the message. The first network slice control function node may detect the timer is expired. The first network slice control function node may send, to the core network apparatus, a message indicating at least one of the time is expired or the network slice related to the timer is not used, after the detecting the timer is expired.
For example, a first network slice control function node corresponding to the NSACF 7701 may receive, from a core network apparatus corresponding to the AMF 70, a message related to management of a network slice. The first network slice control function node may start a timer for the network slice after receiving the message. The first network slice control function node may receive, from a second network slice control function node corresponding to the NSACF 7702, a message detecting an activity related to the network slice. The first network slice control function node may stop the timer after receiving the message.
According to the above, the above problem such as whether and how to enhance the system to ensure network-controlled behavior of network slice usage including UE registration and PDU Session establishment can be solved.
In step 2, the Nnsacf_NSAC_NumOfUEsUpdate_Request message may not include the usage control parameter.
For example, the NSACF 7701 may understand that network slice(s) identified by S-NSSAT(s) in the Nnsacf_NSAC_NumOfUEsUpdate_Request message is subject to usage control or subject to inactivity control based on inclusion of the S-NSSAI(s) and the usage control timer parameter.
In a case where the NSACF 7701 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter in step 2, the NSACF 7701 may start the usage control timers for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 in step 3 and the subsequent processes may be performed in accordance with the Third Example of the First Aspect.
In step 2, the Nnsacf_NSAC_NumOfUEsUpdate_Request message may not include the usage control parameter and the usage control timer parameter.
For example, the NSACF 7701 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfUEsUpdate_Request message is subject to usage control or subject to inactivity control based on reception of the Nnsacf_NSAC_NumOfUEsUpdate_Request message.
In a case where the NSACF 7701 receives the Nnsacf_NSAC_NumOfUEsUpdate_Request message without the usage control parameter and the usage control timer parameter in step 2, the NSACF 7701 may start the usage control timers for S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 in step 3 and the subsequent processes may be performed in accordance with the Third Example of the First Aspect. In this case, the NSACF 7701 may configure value of the usage control timer(s) based on local configuration of the NSACF 7701 or operator's policy stored in the NSACF 7701.
The Fourth Example of the First Aspect in
The UE-Id may be identity of the UE 3.
The usage control which is set ON may indicate to the NSACF 77 that the network slice(s) is subject to usage control or subject to inactivity control. In this case, the usage control which is set ON may indicate to the NSACF 77 that S-NSSAI-1 (or a network slice identified by S-NSSAI-1) is subject to usage control or subject to inactivity control. “usage control which is set ON” may be expressed as “usage control=ON”. The usage control may be expressed as a usage control parameter.
The usage session control timer may define a time or time period for which if the network slice(s) is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice(s), the UE 3 is to be deregistered from the network slice. In this case, the usage session control timer may define a time or time period for which if a network slice identified by S-NSSAI-1 is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice, the UE 3 is to be deregistered from the network slice.
For example, the SMF 71 may configure the usage session control timer based on a local configuration in the SMF 71 or network operator policy within the SMF 71.
The usage session control timer may be expressed as a usage session control timer parameter. For example, the SMF 71 may send to the NSACF 77, a message related to management of a network slice to initiate control of a number of sessions (e.g. PDU sessions) by the NSACF 77 based on the usage session control timer.
The UE-Id may be identity of the UE 3.
The PDU session ID may be identity of a PDU session. The PDU session ID may be identity of a PDU session established on a network slice identified by S-NSSAI-1.
The PDU session ID may be same to one received in the step 3.
The Event ID may identify type of event being subscribed to.
The Event ID which is set to Usage session timer may indicate that network slice(s) is subject to usage control or subject to inactivity control. In this case, the Event ID which is set to Usage session timer may indicate that S-NSSAI-1 (or a network slice identified by S-NSSAI-1) is subject to usage control or subject to inactivity control.
For example, the Event ID which is set to Usage session timer may indicate that the UE 3 is to be deregistered from network slice(s) if the network slice(s) is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice(s). In this case, the Event ID which is set to Usage session timer may indicate that the UE 3 is to be deregistered from a network slice identified by S-NSSAI-1 if the network slice is not used by the UE 3, e.g. if no service request or no PDU session is established by the UE 3 on the network slice.
“Event ID which is set to Usage session timer” may be expressed as “Event ID=Usage session timer”.
The timer value may be configured by the NSACF 77 based on local configuration in the NSACF 77 or may be same to value of the usage session control timer that is received in the Nnsacf_NSAC_NumOfPDUsUpdate_Request message in step 3. The timer value may be associated with the PDU session ID. For example, the NSACF 77 sends, to the SMF 71, a message indicating the control of a number of sessions (e.g. PDU sessions) by the NSACF 77 based on the usage session control timer is initiating or initiated.
For example, in a case where the SMF 71 detects that there is no user plane activity within time period specified by the timer value regarding the PDU session identified by the PDU session ID, the SMF 71 may send the Nsmf_EventExposure_Notify message to the NSACF 77 indicating that the user inactivity in the PDU session has been detected.
The Nsmf_EventExposure_Notify message may include UE-Id and PDU session ID.
The UE-Id may be identity of the UE 3. The UE-Id may be same to one received in step 5.
The PDU session ID may be identity of a PDU session. The PDU session ID may be identity of a PDU session established on a network slice identified by S-NSSAI-1. The PDU session ID may be same to one received in step 5.
For example, the SMF 71 may send the Nsmf_EventExposure_Notify message in a case where there is no user plane activity for the PDU session until the timer of the SMF 71 expires.
The Nsmf_EventExposure_Notify message may indicate that there is no user plane activity for the PDU session.
The Nsmf_EventExposure_Notify message may include information indicating that there is no user plane activity for the PDU session. The information may be expressed as information indicating “User plane inactivity detected”. For example, the SMF 71 sends, to the NSACF 77, a message indicating the user plane activity is not detected based on the monitoring or the result of the monitoring in step 6.
The UE-Id may be identity of the UE 3. The UE-Id may be same to one received in step 7.
The Nsmf_EventExposure_Notify message may include network slice identity that identifies network slice(s) on which there is no user plane activity within time period specified by the timer value. In this case, the Nsmf_EventExposure_Notify message may include S-NSSAI-1.
The Release cause may indicate reason why PDU session(s) established on network slice(s) is released.
For example, in a case where the NSACF 77 receives the Nsmf_EventExposure_Notify message indicating that the user inactivity in the specified PDU session has been detected, the NSACF 77 may set the Release cause to usage session control timer expired. The Release cause which is set to usage session control timer expired may mean that PDU session(s) established on network slice(s) is released as there is no user plane activity within time period specified by the timer value.
For example, in a case where the NSACF 77 receives the Nsmf_EventExposure_Notify message indicating that the user inactivity in the PDU session on a network slice identified by S-NSSAI-1 has been detected, the NSACF 77 may set the Release cause for the S-NSSAI-1 to usage session control timer expired.
The Release cause may be associated with the PDU session ID received in step 7.
“Release cause which is set to usage session control timer expired” may be expressed as “Release cause=usage session control timer expired”. For example, the SMF 71 may receive, from the NSACF 77, a message indicating at least one of the usage session control timer expired and the PDU session is not active state.
For example, in step 9, the SMF 71 may initiate the network requested PDU Session Release procedure for S-NSSAI-1.
For example, in step 9, the SMF 71 may initiate the network requested PDU Session Release procedure for a PDU session identified by the PDU session ID sent in step 7.
For example, in a case where the Nnsacf_NSAC_ReleaseNotification message includes the Release cause with a PDU session ID, the SMF 71 may initiate the network requested PDU Session Release procedure for a PDU session identified by the PDU session ID.
Upon reception of the Nsmf_EventExposure_Notify message in step 7, the NSACF 77 may decrease the number of PDU session established on network slice(s) for quota control of PDU session(s). In this case, the NSACF 77 may decrease, by 1, the number of PDU session established on a network slice identified by S-NSSAI-1.
The Nnsacf_NSAC_ReleaseNotification message may be expressed as a message for performing the network requested PDU Session Release procedure.
The Nnsacf_NSAC_ReleaseNotification message may be expressed as a message for performing a procedure to release the PDU session.
For example, a communication apparatus corresponding to the SMF 71 may send a first message. The first message may include Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus may receive a second message. The second message may include identity of a Protocol Data Unit (PDU) session. The communication apparatus may start a timer after receiving the second message. The communication apparatus may send a third message in a case where there is no user plane activity for the PDU session until the timer expires. The third message may indicate that there is no user plane activity for the PDU session. The communication apparatus may receive a fourth message after sending the third message. The communication apparatus may perform a procedure to release the PDU session after receiving the fourth message.
For example, a communication apparatus corresponding to the NSACF 77 may receive a first message. The first message may include Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus may send a second message. The second message may include identity of a Protocol Data Unit (PDU) session. The communication apparatus may receive a third message after sending the second message. The third message may indicate that there is no user plane activity for the PDU session. The communication apparatus may send a fourth message after receiving the third message. The fourth message may be for performing a procedure to release the PDU session.
For example, a first core network apparatus corresponding to the SMF 71 may send, to a second core network apparatus corresponding to the NSACF 77, first information related to management of a network slice to initiate a control of a number of sessions based on a timer. The first core network apparatus may receive, from the second core network apparatus, second information indicating the control is initiated. The first core network apparatus may monitor user plane activity related to the sessions after receiving the second information. The first core network apparatus may send, to the second core network apparatus, third information indicating the user plane activity is not detected based on the monitoring. The first core network apparatus may receive, from the second core network apparatus, forth information indicating at least one of the timer is expired or the session is not active within the period specified by the timer.
For example, a first core network apparatus corresponding to the NSACF may receive, from a second core network apparatus corresponding to the SMF 71, first information related to management of a network slice. The first core network apparatus may start a timer for the network slice after receiving the first information. The first core network apparatus may send, to the second core network apparatus, second information indicating the management is initiated to start monitoring user plane activity related to a session. The first core network apparatus may receive, from the second core network apparatus, third information indicating the user plane activity is not detected based on the monitoring. The first core network apparatus may send to the second core network apparatus, fourth information indicating at least one of the timer is expired or the session is not active within the period specified by the timer.
According to the above, the above problem such as whether and how to enhance the system to ensure network-controlled behavior of network slice usage including UE registration and PDU Session establishment can be solved.
In a case where the SMF 71 solely performs the usage session control timer handling, step 5, step 7 and step 8 does not take place. The timer value that is used in step 6 may be set based on local configuration in the SMF 71 or based on operator's policy in the SMF 71.
When the SMF 71 detects that there is no user plane activity in specified time period by the timer value, step 9 takes place to release the PDU session that is associated with S-NSSAI 1.
For example, in a case where the SMF 71 detects that there is no user plane activity within specified time period by the timer value, the SMF 71 performs the procedure to release the PDU session that is associated with the PDU session ID sent in step 3.
In step 3, the Nnsacf_NSAC_NumOfPDUsUpdate_Request message may not include the usage control parameter.
For example, the NSACF 77 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfPDUsUpdate_Request message is subject to usage control or subject to inactivity control based on inclusion of the S-NSSAI(s) and the usage session control timer parameter.
In a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfPDUsUpdate_Request message without the usage control parameter in step 3, the NSACF 77 may perform the process in step 4 and send, to the SMF 71, the Nsmf_EventExposure_Subscribe Request message with or without the Event ID in step 5.
Then the SMF 71 may perform the process in step 6 and the subsequent processes may be performed in accordance with the Fourth Example of the First Aspect.
In step 3, the Nnsacf_NSAC_NumOfPDUsUpdate_Request message may not include the usage control parameter and the usage session control timer parameter.
For example, the NSACF 77 may understand that network slice(s) identified by S-NSSAI(s) in the Nnsacf_NSAC_NumOfPDUsUpdate_Request message is subject to usage control or subject to inactivity control based on reception of the Nnsacf_NSAC_NumOfPDUsUpdate_Request message.
In a case where the NSACF 77 receives the Nnsacf_NSAC_NumOfPDUsUpdate_Request message without the usage control parameter and the usage session control timer parameter in step 3, the NSACF 77 may perform the process in step 4 and send, to the SMF 71, the Nsmf_EventExposure_Subscribe Request message with or without the Event ID in step 5.
In a case where the Nnsacf_NSAC_NumOfPDUsUpdate_Request message does not include the usage session control timer parameter, the NSACF 77 may configure the timer value based on local configuration of the NSACF 77 or operator's policy stored in the NSACF 77, and send the timer value by the Nsmf_EventExposure_Subscribe Request message.
Then the SMF 71 may perform the process in step 6 and the subsequent processes may be performed in accordance with the Fourth Example of the First Aspect.
In another example, in a case where the Nnsacf_NSAC_NumOfPDUsUpdate_Request message does not include the usage session control timer parameter, the NSACF 77 may not include the timer value in the Nsmf_EventExposure_Subscribe Request message. In this case, the SMF 71 may configure the timer value based on local configuration of the SMF 71 or operator's policy stored in the SMF 71. Then the SMF 71 may perform the process in step 6 and the subsequent processes may be performed in accordance with the Fourth Example of the First Aspect.
The telecommunication system 1 represents a system overview in which an end to end communication is possible. For example, UE 3 (or user equipment, ‘mobile device’ 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.
The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).
The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.
The (R)AN node 5 may be split into control plane function and user plane function. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane functions are aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called as ‘dual connectivity’ or ‘Multi connectivity’.
The (R)AN node 5 can also support a communication using the satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access.
In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN).
The core network 7 may include logical nodes (or ‘functions’) for supporting a communication in the telecommunication system 1. For example, the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in logical nodes can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).
A Network Function can be deployed as distributed, redundant, stateless, and scalable that provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).
The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
As is well known, a UE 3 may enter and leave the areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.
The core network 7 also includes, amongst others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, an Authentication Server Function (AUSF) 74, a Unified Data Management (UDM) 75, a Network Data Analytics Function (NWDAF) 76 and a Network Slice Admission Control Function (NSACF) 77. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, and PCF 73 for the roaming-out UE 3.
The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called “Uu” interface and/or the like). Neighboring (R)AN node 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called “Xn” interface and/or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called “N2”/“N3” interface(s) and/or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In case that the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type.
The “Uu” interface may include a Control plane of Uu interface and User plane of Uu interface.
The User plane of Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection.
The Control plane of Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.
For example, the following messages are communicated over the RRC layer to support AS signaling.
The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and/or the like). The N1 interface is responsible to provide a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface.
The UE 3 may, for example, support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The UE 3 may, for example, be an item of equipment for production or manufacture and/or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and/or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and/or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and/or related machinery; paper converting machinery; chemical machinery; mining and/or construction machinery and/or related equipment; machinery and/or implements for agriculture, forestry and/or fisheries; safety and/or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and/or application systems for any of the previously mentioned equipment or machinery etc.).
The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).
The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).
The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and/or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).
The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).
The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and/or system, a weapon, an item of cutlery, a hand tool, or the like.
The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).
The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to “internet of things (IoT)”, using a variety of wired and/or wireless communication technologies.
Internet of Things devices (or “things”) may be equipped with appropriate electronics, software, sensors, network connectivity, and/or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and/or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored/tracked.
It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.
The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device).
The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).
<(R)AN node>
The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.
The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
The (R)AN node 5 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit, the DU 61 can be integrated/combined with the CU 62 as another integrated/combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated/combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called “E1” interface and/or the like).
The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called “Uu” interface and/or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called “Front haul”, “Open Front haul”, “F1” interface and/or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called “Mid haul”, “Open Mid haul”, “E2” interface and/or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called “Back haul”, “Open Back haul”, “N2”/“N3” interface(s) and/or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes 7 via an appropriate interface (such as the so-called “N3” interface(s) and/or the like).
Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide functionalities to communicate with a UE 3 over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.
The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating/sending/receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer.
The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and/or moving trajectory estimation.
The RU 60 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
As described above, the RU 60 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated/combined unit above.
The DU 61 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
As described above, the RU 60 can be integrated/combined with the DU 61 or CU 62 as an integrated/combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated/combined unit above.
The CU 62 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
As described above, the CU 62 can be integrated/combined with the DU 61 as an integrated/combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated/combined unit above.
The AMF 70 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The UPF 72 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The PCF 73 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The AUSF 74 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The UDM 75 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The NWDAF 76 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).
The NSACF 77 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NSACF 7701 and the NSACF 7702 may have same components to the NSACF 77.
The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following.
The number of UEs per network slice availability check and update procedure is to update (i.e. increase or decrease) the number of UEs registered with a S-NSSAI which is subject to NSAC. The AMF is configured with the information indicating which network slice is subject to NSAC.
NOTE 1: Depending on the deployment, there may be different NSACF for different S-NSSAI subject to NSAC, and hence, during the registration, AMF triggers the Number of UEs per network slice availability check and update procedure to multiple NSACFs.
If this is the first time to perform NSAC procedure for the S-NSSAI towards the NSACF, the AMF includes notification endpoint for EAC Notification to implicitly subscribe the EAC notification for the S-NSSAI from the NSACF.
If the update flag parameter from the AMF indicates increase, the following applies:
NOTE 2: The use case of having two or more entries in the NSACF for the same UE can happen during (a) inter-AMF mobility when the new AMF request update to the NSACF before the old AMF sends request to deregister the UE; or (b) PDN connections establishment in the EPC when multiple SMF+PGW-Cs (i.e. used for different PDN Connections associated with the same S-NSSAI) send update requests for maximum number of UEs to the NSACF.
If the update flag parameter from the AMF indicates decrease and if there is only one entry associated with the UE ID, the NSACF removes the UE ID from the list of UEs registered with the network slice for each of the S-NSSAI(s) indicated in the request from the AMF and also the NSACF decreases the number of UEs per network slice that is maintained by the NSACF for each of these network slices. If there are multiple entries associated with the UE ID, the NSACF removes the entry associated with the NF ID but the UE ID is kept in the list of UEs registered with the S-NSSAI.
The NSACF takes access type into account for increasing and decreasing the number of UEs per network slice as described in clause 5.15.11.1 of TS 23.501 [2].
The NSACF stores the notification endpoint for EAC Notification associated with the S-NSSAI if it is received from the AMF. The NSACF can use this AMF notification endpoint to update the EAC mode as described in clause 4.2.11.3.
NOTE 3: This enables the NSACF to maintain up-to-date information about the AMFs serving the S-NSSAIs.
If the AMF included usage control parameter set to ON for one or more network slices for the UE and an usage control timer value, the NSACF starts usage control timers for these network slice for the UE with the timer value provided by the AMF. Alternatively, the usage control timer value could be a configured value in the NSACF. The usage control timer for a certain network slice for a UE is stop when a PDU session is established on that network slice by the UE and it is re-started as soon as the PDU Session is released.
If a usage control timer for a network slice expires for the UE, e.g. the network slice has not been used by the UE for the duration of the usage control timer, the NSACF deregisters the UE from the network slice, i.e. the NSACF decreases the UE count for the network slice and removes the UE identity from the list of the UEs registered with the network slice. Then the NSACF returns Nnsacf_NSAC_DeregistrationNotification message to the AMF in which the NSACF includes the UE Identity, the network slice identity and a reject cause set to ‘usage control timer expired’.
At UE Registration procedure, if only some of the S-NSSAIs reached the maximum number of UEs per S-NSSAI, the AMF sends a Registration Accept message to the UE in which the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI list for which the NSACF has indicated that the maximum number of UEs per network slice has been reached, and for each rejected S-NSSAI the AMF includes a reject cause set to ‘maximum number of UEs per network slice reached’ and optionally a back-off timer.
When for all the Requested S-NSSAI(s) provided in step 2 the NSACF returned the maximum number of UEs per network slice has been reached and if one or more subscribed S-NSSAIs are marked as default in the subscription data and not subject to Network Slice Admission Control, the AMF can decide to include these Default Subscribed S-NSSAIs in the Allowed NSSAI. Otherwise, the AMF rejects the UE request for registration. In the Registration Reject message the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI parameter, and for each rejected S-NSSAI the AMF includes a reject cause to indicate that the maximum number of UEs per network slice has been reached and optionally a back-off timer.
NOTE 4: If the use case requires the UE to remain reachable at all times with at least one slice, it is recommended that at least one of the Subscribed S-NSSAIs is marked as the default S-NSSAI which is not subject to Network Slice Admission Control. This will ensure the UE is able to access to services even when maximum number of UEs per network slice has been reached.
<4.2.11.4 Number of PDU Sessions per network slice availability check and update procedure>
The number of PDU Sessions per network slice availability check and update procedure is to update (i.e. increase or decrease) the number of PDU Sessions established on S-NSSAI which is subject to NSAC. The SMF is configured with the information indicating which network slice is subject to NSAC.
NOTE 1: EAC mode is not applicable for Number of PDU Sessions per network slice availability check and update procedure.
NOTE 2: SMFs handling PDU sessions associated with UE Request Type “Existing PDU Session” for handover purposes do not interact with the NSACF.
NOTE 3: For SSC mode 3 PDU session, the SMF of the new PDU Session invokes the NSACF to increase the number of PDU Session and adds the new PDU session ID in the NSACF. When the old PDU session is released the SMF of the old PDU session invokes the NSACF to decrease the number of PDU Session and remove the old PDU session ID in the NSACF.
NOTE 4: An SMF anchoring an IPv6 Multi-homed PDU session does not invoke NSACF for an S-NSSAI subject to NSAC when the PDU session replaces an existing anchor according to clause 4.3.5.3.
If the update flag parameter from the SMF anchoring the PDU session indicates increase and the maximum number of PDU Sessions established on the S-NSSAI has already been reached, then the NSACF returns a result parameter indicating that the maximum number of PDU Sessions per network slice has been reached. If the maximum number of PDU Sessions established on the S-NSSAI has not been reached, the NSACF checks the UE ID. If the UE ID is located, the NSACF, stores the PDU Session ID, and increases the number of PDU Sessions for that S-NSSAI. If the NSACF did not locate the UE ID, it creates an entry for the UE ID, stores the PDU Session ID, and increases the number of PDU Sessions for that S-NSSAI.
If the update flag parameter from the SMF anchoring the PDU session indicates decrease the current number of PDU Sessions per S-NSSAI, the NSACF locates the UE ID, and decreases the number of PDU Sessions for that S-NSSAI and its related PDU Session ID. If the UE ID has no more PDU sessions, after the decrease, the NSACF removes the UE ID entry.
The NSACF takes access type into account for increasing and decreasing the number of PDU Sessions per S-NSSAI as described in clause 5.15.11.2 of TS 23.501 [2].
If the NSACF has active usage control timer running for a network slice for the UE, the NSACF stops the usage control timer if the update flag for the network slice is set to increase, i.e. a new PDU session is established by the UE on the network slice. The NSACF re-starts the usage control timer for the network slice if the update flag for the network slice is set to decrease, i.e. an active PDU session on the network slice has been released by the UE.
In the case of a PDU Session Establishment failure, the anchor SMF triggers another request to the NSACF with the update flag parameter equal to decrease in order to re-adjust back the PDU Session counter in the NSACF.
Description: Updates the number of UEs registered with a network slice (e.g. increase or decrease) when the UE registration status for a network slice subject to NSAC has changed. Also, if the number of the UEs registered with the network slice is to be increased and the Early Availability Check (EAC) mode in the NSACF is activated for that network slice (see Nnsacf_NSAC_EACNotify service operation), the NSACF first checks whether the number of UEs registered with the network slice has reached the maximum number of UEs per network slice threshold. If the maximum number of UEs registered with the network slice has already been reached, the UE registration for that network slice is rejected. If the EAC is not activated, the NSACF increases or decreases the number of UEs per network slice as per the input parameters below.
Inputs, Required: S-NSSAI(s), UE ID (SUPI), NF ID, access type, update flag.
Inputs, Conditional: Notification endpoint for EAC Notification for the S-NSSAI.
The S-NSSAI(s) parameter is a list of one or more network slices for which the number of UEs registered with a network slice is to be updated and checked if the maximum number of UEs per network slice threshold has already been reached.
The UE ID is used by the NSACF to maintain a list of UE IDs registered with the network slice. The NSACF also takes access type into account for increasing and decreasing the number of UEs per network slice as described in clause 5.15.11.1 of TS 23.501 [2].
The NF ID parameter is the NF instance ID of the NF (e.g. AMF or SMF+PGW-C) sending the request to the NSACF.
The update flag input parameter indicates whether the number of UEs registered with a network slice is to be:
If this is the first time to perform NSAC procedure for the S-NSSAI towards the NSACF, the AMF includes notification endpoint for EAC Notification to implicitly subscribe the EAC notification for the S-NSSAI from the NSACF.
Inputs, Optional: usage control, usage control timer
The usage control timer per a network slice for a UE is included if the network slice is subject to usage control, i.e. the UE is to be deregistered from the network slice by the NSACF if the network slice is not used by the UE for certain duration of time.
The usage control timer may be included if the network slice(s) are subject to usage control.
The NSACF may optionally return the current status of the network slice availability (e.g. a percentage out of the maximum number of UEs registered with a network slice) in the availability status parameter. This information may be used for NSACF signalling and load balancing in case multiple NSACFs are serving the same network slice.
Editor's note: It is FFS how to support in case multi NSACF is supported, e.g. discover the same NSACF, coordination of the local maximum number among NSACF.
Outputs, Required: maximum number of UEs per network slice reached, availability status.
Description: Notifies for a network slice for which the UE was deregistered from by the NSACF due to the usage control timer expiry for that network slice for the UE.
Inputs, Required: UE_ID, S-NSSAI, reject cause.
The UE_ID parameter is the UE identity which is deregistered from the network slice due to the usage control timer expiry
The S-NSSAI parameter is the network slice identity which the UE has not used for the duration of the usage control timer
The reject cause parameter is set to ‘usage control timer expired’ if the UE has not used the S-NSSAI for the duration of the usage control timer.
Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.
In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.
Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories/caches (program and/or data); processing registers; communication buses (e.g. control, data and/or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and/or timers; and/or the like.
In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.
In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.
Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/tablet computers, web browsers, e-book readers and/or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called ‘Internet of Things’ (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.
As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.
It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.
The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).
The whole or part of the example embodiments disclosed above can be described as, but not limited to, the following supplementary notes.
While the invention has been particularly shown and described with reference to example embodiments thereof, the invention is not limited to these embodiments. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the claims.
This application is based upon and claims the benefit of priority from Indian pro-visional patent application No. 202111060026, filed on Dec. 22, 2021, the disclosure of which is incorporated herein in its entirety by reference.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202111060026 | Dec 2021 | IN | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2022/043677 | 11/28/2022 | WO |
