Patent Application
20250193824
The present disclosure relates to a method of a user equipment (UE), a UE, a method of a communication apparatus and a communication apparatus.
The NSSRG (Network Slice Simultaneous Registration Group) is introduced to the 5GS in release 17. The NSSRG feature provides 3GPP operators a mechanism for limiting a combination of network slices to be registered at the same time.
However, there are many ambiguous descriptions in 3GPP specification(s) how to handle the NSSRG feature.
For example, this disclosure provides solution for this problem.
In an aspect of the present disclosure, a method of a user equipment (UE) includes communicating with a communication apparatus and sending a Registration Request message. The Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI). The Requested NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and second S-NSSAI in Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.
In an aspect of the present disclosure, a user equipment (UE) includes means for communicating with a communication apparatus and means for sending a Registration Request message. The Registration Request message includes Requested Network Slice Selection Assistance Information (NSSAI). The Requested NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and second S-NSSAI in Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.
In an aspect of the present disclosure, a method of a communication apparatus includes communicating with a user equipment (UE). The method includes sending a message. The message includes Allowed Network Slice Selection Assistance Information (NSSAI). The Allowed NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and second S-NSSAI in Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.
In an aspect of the present disclosure, a communication apparatus includes means for communicating with a user equipment (UE). The communication apparatus includes means for sending a message. The message includes Allowed Network Slice Selection Assistance Information (NSSAI). The Allowed NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The first S-NSSAI and second S-NSSAI in Pending NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value.
In an aspect of the present disclosure, a method of a communication apparatus includes sending a first message including Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a registration request message including Requested NSSAI. The Requested NSSAI includes second S-NSSAI. The method includes checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The method includes sending a second message including Configured NSSAI in case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
In an aspect of the present disclosure, a communication apparatus includes means for sending a first message including Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The communication apparatus includes means for receiving a registration request message including Requested NSSAI. The Requested NSSAI includes second S-NSSAI. The communication apparatus includes means for checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The communication apparatus includes means for sending a second message including Configured NSSAI in case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
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 may 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 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 user equipment (UE) according to example aspect of this disclosure includes receiving a message including Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The method includes checking whether the first S-NSSAI and second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value in a case where registration procedure using the second S-NSSAI is triggered. The method includes sending a registration request message including the second S-NSSAI in a case where the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value.
A method of a communication apparatus according to example aspect of this disclosure includes sending a first message including Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The method includes receiving a registration request message including Requested NSSAI. The Requested NSSAI includes second S-NSSAI. The method includes checking whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The method includes sending a second message including Configured NSSAI in case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
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 receive a message including Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to check whether the first S-NSSAI and second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value in a case where registration procedure using the second S-NSSAI is triggered. The at least one hardware processor is configured to send a registration request message including the second S-NSSAI in a case where the first S-NSSAI and the second S-NSSAI are associated with the at least one common NSSRG value.
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 including Pending Network Slice Selection Assistance Information (NSSAI). The Pending NSSAI includes first Single Network Slice Selection Assistance Information (S-NSSAI). The at least one hardware processor is configured to receive a registration request message including Requested NSSAI. The Requested NSSAI includes second S-NSSAI. The at least one hardware processor is configured to check whether the first S-NSSAI and the second S-NSSAI are associated with at least one common Network Slice Simultaneous Registration Group (NSSRG) value. The at least one hardware processor is configured to send a second message including Configured NSSAI in case where the first S-NSSAI and the second S-NSSAI are not associated with the at least one common NSSRG value.
The NSSRG (Network Slice Simultaneous Registration Group) is introduced to the 5GS in release 17. The NSSRG feature provides 3GPP operator(s) mechanism for limiting a combination of network slices to be registered to the end user at the same time. According to current 3GPP specification(s), the NSSRG information (e.g. information indicating NSSRG or information related to NSSRG) is provided to a UE from 5GC, and the UE chooses the network slice(s) based on the NSSRG information. However, it is not clear in 3GPP specification(s) what the 5GC is supposed to do if the UE holds an old Configured network slice(s) (e.g. old Configured NSSAI) and/or old NSSRG information. In this case, the NSSRG feature does not work properly.
For example, this aspect focuses on an issue when an AMF 70 detects, based on the NSSRG information, that S-NSSAI(s) in Requested NSSAI in a Registration Request message from a UE 3 includes S-NSSAI(s) that is not compatible with S-NSSAI(s) in Pending NSSAI in the AMF 70. For example, this aspect provides solution for this issue.
For example, as the S-NSSAI(s) in the Requested NSSAI and the S-NSSAI(s) in the Pending NSSAI cannot be allowed to be registered at the same time, the AMF 70 detects that at least one of Configured NSSAI and NSSRG information in the UE 3 are not the latest ones. For example, the AMF 70 detects that at least one of the Configured NSSAI and the NSSRG information in the UE 3 are out of date. In this case, the AMF 70 provides at least one of Configured NSSAI and NSSRG information to the UE 3 to refresh data in the UE 3.
For example, this aspect also discloses a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message does not belong to or does not share any common NSSRG value with S-NSSAI(s) in the Pending NSSAI.
For example, this aspect also discloses a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message belongs to or shares at least one common NSSRG value with S-NSSAI(s) in the Pending NSSAI.
A First example of the First Aspect discloses a method where the UE 3 checks whether S-NSSAI(s) in Pending NSSAI and Requested NSSAI in a Registration Request message belong to or share at least one common NSSRG value.
The detailed processes of the First example of the First Aspect are described below, with reference to
The AMF 70 may know that the UE 3 has the Pending NSSAI including the S-NSSAI 1.
For example, in a case where the S-NSSAI 1 is associated with NSSRG 1 (or NSSRG value 1) and the S-NSSAI 2 is associated with NSSRG 1 (or NSSRG value 1), the UE 3 determines that the S-NSSAI 1 and the S-NSSAI 2 belong to or share or are associated with the common NSSRG (or the common NSSRG value), and initiates the registration procedure by sending the Registration Request message including the Requested NSSAI which includes the S-NSSAI 2.
If the S-NSSAI 1 in the Pending NSSAI in the UE 3 and the S-NSSAI 2 do not belong to a common NSSRG value (e.g. if the S-NSSAI 1 and the S-NSSAI 2 do not belong to a common NSSRG or if the S-NSSAI 1 and the S-NSSAI 2 do not share a common NSSRG value or if the S-NSSAI 1 and the S-NSSAI 2 do not share a common NSSRG or if the S-NSSAI 1 and the S-NSSAI 2 are not associated with any common NSSRG value), then the UE 3 has a few options to take.
For example, in a case where the S-NSSAI 1 is associated with NSSRG 1 (or NSSRG value 1) and the S-NSSAI 2 is associated with to NSSRG 2 (or NSSRG value 2), the UE 3 determines that the S-NSSAI 1 and the S-NSSAI 2 do not belong to or do not share or are not associated with the common NSSRG (or the common NSSRG value), and may perform one of the options below.
See below for the options that the UE 3 takes:
In a case where the UE 3 initiates the registration procedure by sending the Registration Request message including the Requested NSSAI set with the S-NSSAI 2 in step 7, the registration procedure may continue from the step 4 in section 4.2.2.2.2 of NPL 3.
In a case where the UE 3 initiates the registration procedure by sending the Registration Request message including the Requested NSSAI set with the another S-NSSAI that belongs to a common NSSRG value with the S-NSSAI 1 in step 7, the registration procedure may continue from the step 4 in section 4.2.2.2.2 of NPL 3.
In a case where the UE 3 initiates the registration procedure by sending the Registration Request message including the Requested NSSAI set with the S-NSSAI 2 after completion of the aborting the NSSAA procedure for the S-NSSAI 1 in step 7, the registration procedure may continue from the step 4 in section 4.2.2.2.2 of NPL 3.
In a case where the UE 3 initiates the registration procedure by sending the Registration Request message including the Requested NSSAI set with the S-NSSAI 2 after completion of NSSAA procedure for the S-NSSAI 1 in step 7, the registration procedure may continue from the step 4 in section 4.2.2.2.2 of NPL 3.
For example, in a case where the S-NSSAI 1 and the S-NSSAI 2 are not associated with any common NSSRG value, the UE 3 may detect or determine that at least one of the Configured NSSAI and the NSSRG information in the UE 3 are not latest ones. In this case, the UE 3 may request at least one of latest Configured NSSAI and latest NSSRG information to the 5GC, and receive the at least one of latest Configured NSSAI and latest NSSRG information.
According to the First example of the First Aspect, for example, it can provide solution for ambiguous descriptions in 3GPP specification(s) how to handle the NSSRG.
According to the First example of the First Aspect, for example, it can provide a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message does not belong to or does not share any common NSSRG value with S-NSSAI(s) in the Pending NSSAI.
According to the First example of the First Aspect, for example, it can provide a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message belongs to or shares at least one common NSSRG value with S-NSSAI(s) in the Pending NSSAI.
In one example, in step 1, the UE 3 sends only S-NSSAI 1 in the Registration Request message. In this case the UE 3 and the AMF 70 have S-NSSAI 1 in Pending NSSAI. In step 6 the UE 3 receives trigger to register to S-NSSAI 2 and may perform processes in step 6. For example, the UE 3 may select S-NSSAI(s) from Configured NSSAI, and include the selected S-NSSAI(s) in the Requested NSSAI in the Registration Request message. For example, subset of the Configured NSSAI may be provided in the Requested NSSAI. For example, subset of the Configured NSSAI may be the Requested NSSAI. Variant 1 of First example of the First Aspect may be applied to Second example of the First Aspect below. For example, in a case where the UE 3 has the Pending NSSAI, the subset of Configured NSSAI provided in the Requested NSSAI and the Pending NSSAI may be associated with at least one common NSSRG value.
For example, in a case where the UE 3 initiates registration procedure (e.g. in step 6), the UE 3 may determine or check whether the UE 3 has Pending NSSAI. In a case where the UE 3 determines or checks that UE 3 has the Pending NSSAI and the UE 3 initiates registration procedure using the Requested NSSAI (e.g. the UE 3 initiates the registration procedure by sending a Registration Request message including the Requested NSSAI), the UE 3 may determine or check whether the subset of Configured NSSAI provided in the Requested NSSAI and the Pending NSSAI are associated with at least one common NSSRG value.
In a case where the UE 3 determines or checks that the subset of Configured NSSAI provided in the Requested NSSAI and the Pending NSSAI are associated with at least one common NSSRG value (e.g. in step 6), the UE 3 may perform the registration procedure using the Requested NSSAI (e.g. the UE 3 may send the Registration Request message including the Requested NSSAI. This process may be performed in step 7). The following processes (or subsequent processes) may be same as step 8 of
A Second example of the First Aspect discloses a method where the AMF 70 checks whether the S-NSSAI(s) in the Pending NSSAI and the S-NSSAI(s) in the Requested NSSAI in the Registration Request message share at least one common NSSRG value or not. In a case where the S-NSSAI(s) in the Pending NSSAI and the S-NSSAI(s) in the Requested NSSAI don't share any common NSSRG value, then the AMF 70 provides Configured NSSAI and the NSSRG to a UE 3 to refresh configuration data in the UE 3.
The detailed processes of the Second example of the First Aspect are described below, with reference to
The AMF 70 may store the NSSRG information. For example, the AMF 70 can understand based on the NSSRG information which network slice (e.g. S-NSSAI) belongs to which NSSRG value or NSSRG. For example, the AMF 70 can understand based on the NSSRG information which network slice(s) (e.g. S-NSSAI(s)) share to NSSRG value or NSSRG. For example, the AMF 70 can understand based on the NSSRG information which network slice (e.g. S-NSSAI) is associated with which NSSRG value or NSSRG.
The AMF 70 may store the NSSRG information in advance or may receive the NSSRG information from other network node or may create the NSSRG information based on local configuration in the AMF 70 or operator's policy or information received from other network node.
The AMF 70 may know that the UE 3 has the Pending NSSAI including the S-NSSAI 1.
The UE 3 keeps the S-NSSAI 1 in the Pending NSSAI during the NSSAA procedure. The steps 6 to 9 may be performed during the NSSAA procedure for the S-NSSAI 1.
Depending on an outcome of the checking in step 7, one of steps 8a, 8b, 8c and 8d takes place.
The UE 3 may store the Allowed NSSAI and the Pending NSSAI. For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
Upon reception of the Registration Accept message from the AMF 70 including the S-NSSAI 1 in the Rejected NSSAI, as the S-NSSAI 1 is in the Pending NSSAI stored in the UE 3, the UE 3 removes the S-NSSAI 1 from the Pending NSSAI and stores the S-NSSAI 1 to the Rejected NSSAI. In addition, the UE 3 may initiate an abort process to ongoing NSSAA procedure for the S-NSSAI 1. The UE 3 may store the S-NSSAI 2 in the Allowed NSSAI. For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
For example, the UE 3 may keep the ongoing NSSAA procedure for the S-NSSAI 1. In this case, if the UE 3 receives Allowed NSSAI including the S-NSSAI 1 after completion of the NSSAA procedure for the S-NSSAI 1, the UE 3 may not update Allowed NSSAI in the UE 3 based on the received Allowed NSSAI including the S-NSSAI 1. In this case, the UE 3 may discard the received Allowed NSSAI and keep the S-NSSAI 1 in the Rejected NSSAI.
Upon reception of the Registration Accept message from the AMF 70 including the S-NSSAI 2 in the Rejected NSSAI, as the S-NSSAI 2 is in the Allowed NSSAI stored in the UE 3, the UE 3 removes the S-NSSAI 2 from the Allowed NSSAI and stores the S-NSSAI 2 to the Rejected NSSAI. The UE 3 may store the S-NSSAI 1 in the Pending NSSAI. For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
Upon reception of the Registration Reject message from the AMF 70 including the S-NSSAI 1 and the S-NSSAI 2 in the Rejected NSSAI, as the S-NSSAI 1 is in the Pending NSSAI in the UE 3 and the S-NSSAI 2 is in the Allowed NSSAI in the UE 3, the UE 3 removes the S-NSSAI 1 from the Pending NSSAI, and removes the S-NSSAI 2 from the Allowed NSSAI, and stores the S-NSSAI 1 and S-NSSAI 2 to the Rejected NSSAI. In addition, the UE 3 initiates an abort process to ongoing NSSAA procedure for S-NSSAI 1. For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
For example, the UE 3 may keep the ongoing NSSAA procedure for the S-NSSAI 1. In this case, if the UE 3 receives Allowed NSSAI including the S-NSSAI 1 after completion of the NSSAA procedure for the S-NSSAI 1, the UE 3 may not update Allowed NSSAI in the UE 3 based on the received Allowed NSSAI including the S-NSSAI 1. In this case, the UE 3 may discard the received Allowed NSSAI and keep the S-NSSAI 1 in the Rejected NSSAI.
For example, in a case where the AMF 70 determines that the S-NSSAI 1 and the S-NSSAI 2 are not associated with any common NSSRG value, the AMF 70 may detect or determine that at least one of the Configured NSSAI and the NSSRG information in the UE 3 are not latest ones. In this case, the AMF 70 may send the Registration Accept message or the Registration Reject message as mentioned in step 8b, 8c or 8d.
The Configured NSSAI sent in step 8a, 8b 8c or 8d may be same to the Configured NSSAI sent in step 2.
The Configured NSSAI sent in step 8a, 8b 8c or 8d may be different the Configured NSSAI sent in step 2. In this case, the AMF 70 may create new Configured NSSAI or update the Configured NSSAI sent in step 2 based on local configuration in the AMF 70 or operator's policy or information received from other network node, and may send the new Configured NSSAI or the updated Configured NSSAI in step 8a, 8b 8c or 8d. The AMF 70 may request the new Configured NSSAI or the updated Configured NSSAI to other network node and may receive the new Configured NSSAI or the updated Configured NSSAI from the other network node. Then the AMF 70 may send the new Configured NSSAI or the updated Configured NSSAI in step 8a, 8b 8c or 8d.
The NSSRG information sent in step 8a, 8b 8c or 8d may be same to the NSSRG information sent in step 2.
The NSSRG information sent in step 8a, 8b 8c or 8d may be different the NSSRG information sent in step 2. In this case, the AMF 70 may create new NSSRG information or update the NSSRG information sent in step 2 based on local configuration in the AMF 70 or operator's policy or information received from other network node, and may send the new NSSRG information or the updated NSSRG information in step 8a, 8b 8c or 8d.
The AMF 70 may request the new NSSRG information or the updated NSSRG information to other network node and may receive the new NSSRG information or the updated NSSRG information from the other network node. Then the AMF 70 may send the new NSSRG information or the updated NSSRG information in step 8a, 8b 8c or 8d.
For example, in a case where the UE 3 has the Pending NSSAI and the S-NSSAI 2 of the Requested NSSAI in the Registration Request message and the Pending NSSAI (e.g. S-NSSAI 1 in the Pending NSSAI) are not associated with any common NSSRG value, the AMF 70 may send the new Configured NSSAI by using the Registration Reject message or the Registration Accept message (or the AMF 70 may include the new Configured NSSAI in the Registration Reject message or the Registration Accept message).
For example, in a case where the AMF 70 has the Pending NSSAI and the S-NSSAI 2 of the Requested NSSAI in the Registration Request message and the Pending NSSAI (e.g. S-NSSAI 1 in the Pending NSSAI) are not associated with any common NSSRG value, the AMF 70 may send the new Configured NSSAI by using the Registration Reject message or the Registration Accept message (or the AMF 70 may include the new Configured NSSAI in the Registration Reject message or the Registration Accept message).
According to the Second example of the First Aspect, for example, it can provide solution for ambiguous descriptions in 3GPP specification(s) how to handle the NSSRG.
According to the Second example of the First Aspect, for example, it can provide a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message does not belong to or does not share any common NSSRG value with S-NSSAI(s) in the Pending NSSAI.
According to the Second example of the First Aspect, for example, it can provide a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message belongs to or shares at least one common NSSRG value with S-NSSAI(s) in the Pending NSSAI.
For example, in a case where the S-NSSAI 1 and the S-NSSAI 2 does not share at least one common NSSRG value, there is possibility that at least one of the Configured NSSAI and the NSSRG information stored in the UE 3 are not latest ones. By checking whether the S-NSSAI 1 and the S-NSSAI 2 share at least one common NSSRG value, the AMF 70 can detect or determine whether at least one of the Configured NSSAI and the NSSRG information in the UE 3 may not be the latest ones (or may be old ones). In a case where the AMF 70 determines that the S-NSSAI 1 and the S-NSSAI 2 do not share at least one common NSSRG value (e.g. the AMF 70 detects or determines that at least one of the Configured NSSAI and the NSSRG information in the UE 3 may not be the latest ones), the AMF 70 sends at least one of the Configured NSSAI and the NSSRG information to refresh or update at least one of the Configured NSSAI and the NSSRG information stored in the UE 3. According to the Second example of the First Aspect, for example, the latest information (e.g. the Configured NSSAI and the NSSRG information) for performing the NSSRG feature is provide from the AMF 70 to the UE 3 in a case where the S-NSSAI 1 and the S-NSSAI 2 do not share at least one common NSSRG value and the NSSRG feature can work properly.
In steps 8b and 8d, the AMF 70 may initiate the AMF triggered Slice-Specific Authorization Revocation procedure. The AMF triggered Slice-Specific Authorization Revocation procedure may be one of outlined procedures below:
For example, the AMF 70 may know that contents of Configured NSSAI for the UE 3 or that the UE 3 has the Configured NSSAI. For example, in a case where the AMF 70 receives, from the UE 3, a Registration Request message including Requested NSSAI (e.g. in step 6), the AMF 70 may determine or check whether subset of Configured NSSAI provided in the Requested NSSAI and Pending NSSAI (e.g. Pending NSSAI for UE 3) are associated with at least one common NSSRG value (e.g. in step 7). Depending on the determination or the checking, the AMF 70 may perform one of steps 8a to 8d. For example, in a case where the AMF 70 determines that the subset of Configured NSSAI provided in the Requested NSSAI and the Pending NSSAI are associated with at least one common NSSRG value, the AMF 70 may perform the process in step 8a (e.g. the AMF 70 may send the Registration Accept message in step 8a). For example, in a case where the AMF 70 determines that the subset of Configured NSSAI provided in the Requested NSSAI and the Pending NSSAI are not associated with at least one common NSSRG value, the AMF 70 may perform the process in one of steps 8b to 8d (e.g. the AMF 70 may send the Registration Accept message in step 8b or the AMF 70 may send the Registration Accept message in step 8c or the AMF 70 may send the Registration Reject message in step 8d).
The NSSRG (Network Slice Simultaneous Registration Group) is introduced to the 5GS in release 17. The NSSRG feature provides 3GPP operator(s) mechanism for limiting a combination of network slices to be registered to the end user at the same time. According to current 3GPP specification(s), the NSSRG information (e.g. information indicating NSSRG or information related to NSSRG) is provided to a UE from 5GC, and the UE chooses the network slice(s) based on the NSSRG information. However, it is not clear in 3GPP specification(s) what the 5GC is supposed to do if the UE holds an old Configured network slice(s) (e.g. old Configured NSSAI) and/or old NSSRG information. In this case, the NSSRG feature does not work properly.
For example, this aspect focuses on an issue when an AMF 70 detects, based on the NSSRG information, that S-NSSAI(s) in Requested NSSAI in a Registration Request message from a UE 3 includes S-NSSAI(s) that is not compatible with S-NSSAI(s) in the Allowed NSSAI for another access type in the AMF 70. For example, this aspect provides solution for this issue.
For example, as the S-NSSAI(s) in the Requested NSSAI and the S-NSSAI(s) in the Allowed NSSAI for another access type cannot be allowed to be registered at the same time, the AMF 70 detects that at least one of Configured NSSAI and NSSRG information in the UE 3 are not the latest ones. For example, the AMF 70 detects that at least one of the Configured NSSAI and the NSSRG information in the UE 3 are out of date. In this case, the AMF 70 provides Configured NSSAI information and NSSRG information to the UE 3 to refresh data in the UE 3.
For example, this aspect also discloses a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message does not belong to or does not share any common NSSRG value with S-NSSAI(s) in Allowed NSSAI for another access type.
A First example of the Second Aspect discloses a method where the AMF 70 checks whether S-NSSAI(s) in Allowed NSSAI over one access type and the Requested NSSAI(s) in the Registration Request message over another access type share at least one common NSSRG value. In a case where the S-NSSAI(s) in the Allowed NSSAI over one access and S-NSSAI(s) in the Requested NSSAI(s) over another access don't share a common NSSRG value then the AMF 70 sends a Registration Accept message to the UE 3 containing Configured NSSAI and NSSRG information to refresh configuration data in the UE 3.
The detailed processes of the First example of the Second Aspect are described below, with reference to
The AMF 70 may store the NSSRG information in advance or may receive the NSSRG information from other network node or may create the NSSRG information based on local configuration in the AMF 70 or operator's policy or information received from other network node.
For example, the AMF 70 can understand based on the NSSRG information which network slice (e.g. S-NSSAI) belongs to which NSSRG value or NSSRG. For example, the AMF 70 can understand based on the NSSRG information which network slice(s) (e.g. S-NSSAI(s)) share to NSSRG value or NSSRG. For example, the AMF 70 can understand based on the NSSRG information which network slice (e.g. S-NSSAI) is associated with which NSSRG value or NSSRG.
Depending on an outcome of the checking, there are two options to take.
This is an option that the AMF 70 rejects the Registration Request message due to no common NSSRG value between S-NSSAI 1 in the Requested NSSAI and S-NSSAI 2 in the Allowed NSSAI over 3GPP access.
Upon reception of the Registration Reject message, the UE 3 stores at least one of the Configured NSSAI, the NSSRG information and the S-NSSAI 2 set to the Rejected NSSAI. For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
This is an option that the AMF 70 accepts the Registration Request with the S-NSSAI 2. As S-NSSAI 2 is accepted, the AMF 70 updates the S-NSSAI 1 over the non-3GPP access to be rejected as there is no common NSSRG value between the S-NSSAI 1 and the S-NSSAI 2.
Upon reception of the Registration Accept message, the UE 3 stores at least one of the Configured NSSAI, the NSSRG information and the S-NSSAI 2 set to the Allowed NSSAI. For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
Upon reception of the UE Configuration Update Command message, the UE 3 stores at least one of the Configured NSSAI, the NSSRG information and the S-NSSAI 1 set to the Rejected NSSAI for the 3GPP access.
For example, the UE 3 may delete the S-NSSAI 1 from the Allowed NSSAI for the 3GPP access, and store the Rejected NSSAI including the S-NSSAI 1 for the 3GPP access.
For example, the UE 3 may use at least one of the received Configured NSSAI and the received NSSRG information to refresh or update data in the UE 3 (e.g. the Configured NSSAI and the NSSRG information which are previously stored in the UE 3).
The AMF 70 may create new Configured NSSAI or update the Configured NSSAI sent to the UE 3 previously based on local configuration in the AMF 70 or operator's policy or information received from other network node, and may send the new Configured NSSAI or the updated Configured NSSAI in step 5a, 5b or 7b.
The AMF 70 may request the new Configured NSSAI or the updated Configured NSSAI to other network node and may receive the new Configured NSSAI or the updated Configured NSSAI from the other network node. Then the AMF 70 may send the new Configured NSSAI or the updated Configured NSSAI in step 5a, 5b or 7b.
For example, the Configured NSSAI in step 5a or step 5b may be configured for the non-3GPP access. For example, the Configured NSSAI in step 5b and step 7b may be configured so as to be common to the 3GPP access and the non-3GPP access. For example, the Configured NSSAI in step 5a and step 7b may be configured so as to be different between the 3GPP access and the non-3GPP access. For example, the Configured NSSAI in steps 5a and 5b may be for the non-3GPP access, and the Configured NSSAI in steps 7b may be for the 3GPP access.
The AMF 70 may create new NSSRG information or update the NSSRG information sent to the UE 3 previously based on local configuration in the AMF 70 or operator's policy or information received from other network node, and may send the new NSSRG information or the updated NSSRG information in step 5a, 5b or 7b.
The AMF 70 may request the new NSSRG information or the updated NSSRG information to other network node and may receive the new NSSRG information or the updated NSSRG information from the other network node. Then the AMF 70 may send the new NSSRG information or the updated NSSRG information in step 5a, 5b or 7b.
For example, the NSSRG information in step 5a or step 5b may be configured for the non-3GPP access. For example, the NSSRG information in step 5b and step 7b may be configured so as to be common to the 3GPP access and the non-3GPP access. For example, the NSSRG information in step 5a and step 7b may be configured so as to be different between the 3GPP access and the non-3GPP access. For example, the NSSRG information in steps 5a and 5b may be for the non-3GPP access, and the NSSRG information in steps 7b may be for the 3GPP access
For example, in a case where the AMF 70 determines that the S-NSSAI 1 and the S-NSSAI 2 belong to common NSSRG value in step 4, the AMF 70 may send, to the UE 3, a Registration Accept message including Allowed NSSAI for the non-3GPP access which includes the S-NSSAI 2.
For example, in a case where the UE 3 has already the Allowed NSSAI for the 3GPP access and the S-NSSAI 2 of the Requested NSSAI in the Registration Request message and the Allowed NSSAI (e.g. S-NSSAI 1 in the Allowed NSSAI) are not associated with any common NSSRG value, the AMF 70 may send the new Configured NSSAI by using the Registration Reject message or the Registration Accept message (or the AMF 70 may include the new Configured NSSAI in the Registration Reject message or the Registration Accept message).
For example, in a case where the AMF 70 has already the Allowed NSSAI for the 3GPP access and the S-NSSAI 2 of the Requested NSSAI in the Registration Request message and the Allowed NSSAI (e.g. S-NSSAI 1 in the Allowed NSSAI) are not associated with any common NSSRG value, the AMF 70 may send the new Configured NSSAI by using the Registration Reject message or the Registration Accept message (or the AMF 70 may include the new Configured NSSAI in the Registration Reject message or the Registration Accept message).
For example, in a case where the AMF 70 has already the Allowed NSSAI for the 3GPP access and the S-NSSAI 2 of the Requested NSSAI in the Registration Request message over the non-3GPP access and the Allowed NSSAI (e.g. S-NSSAI 1 in the Allowed NSSAI) for the 3GPP access are not associated with any common NSSRG value, the AMF 70 may send the new Configured NSSAI by using the Registration Reject message or the Registration Accept message (or the AMF 70 may include the new Configured NSSAI in the Registration Reject message or the Registration Accept message).
For example, in a case where the UE 3 (or the AMF 70) has already the Allowed NSSAI for the other access and the S-NSSAI 2 of the Requested NSSAI in the Registration Request message over the current access and the Allowed NSSAI (e.g. S-NSSAI 1 in the Allowed NSSAI) for the other access are not associated with any common NSSRG value, the AMF 70 may send the new Configured NSSAI by using the Registration Reject message or the Registration Accept message (or the AMF 70 may include the new Configured NSSAI in the Registration Reject message or the Registration Accept message).
The Registration Accept message in step 5b may include information indicating that the UE Configuration Update Command message will be sent. In a case where the UE 3 receives the information, the UE 3 may not send, over the 3GPP access, a Registration Request message including Requested NSSAI which includes the S-NSSAI 1 or other NAS message related to the S-NSSAI 1 until the UE 3 receives the UE Configuration Update Command message.
According to the First example of the Second Aspect, for example, it can provide solution for ambiguous descriptions in 3GPP specification(s) how to handle the NSSRG.
According to the First example of the Second Aspect, for example, it can provide a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message over one access does not belong to or does not share any common NSSRG value with S-NSSAI(s) in the Allowed NSSAI for another access.
According to the First example of the Second Aspect, for example, it can provide a method of handling registration procedure in a case where S-NSSAI(s) of the Requested NSSAI in the Registration Request message over one access belongs to or shares at least one common NSSRG value with S-NSSAI(s) in the Allowed NSSAI for another access.
For example, in a case where the S-NSSAI 1 and the S-NSSAI 2 does not share at least one common NSSRG value, there is possibility that at least one of the Configured NSSAI and the NSSRG information stored in the UE 3 are not latest ones. By checking whether the S-NSSAI 1 and the S-NSSAI 2 share at least one common NSSRG value, the AMF 70 can detect or determine whether at least one of the Configured NSSAI and the NSSRG information in the UE 3 may not be the latest ones (or may be old ones). In a case where the AMF 70 determines that the S-NSSAI 1 and the S-NSSAI 2 does not share at least one common NSSRG value (e.g. the AMF 70 detects or determines that at least one of the Configured NSSAI and the NSSRG information in the UE 3 may not be the latest ones), the AMF 70 sends at least one of the Configured NSSAI and the NSSRG information to refresh or update at least one of the Configured NSSAI and the NSSRG information stored in the UE 3. According to the First example of the Second Aspect, for example, the latest information (e.g. the Configured NSSAI and the NSSRG information) for performing the NSSRG feature is provide from the AMF 70 to the UE 3 in a case where the S-NSSAI 1 and the S-NSSAI 2 does not share at least one common NSSRG value and the NSSRG feature can work properly.
Although this example explains a situation where the UE 3 sends the Registration Request message to the AMF 70 over the non-3GPP access while the UE 3 has the Allowed NSSAI over the 3GPP access, the First example of the Second Aspect is equally effective to a situation where the UE 3 sends the Registration Request message to the AMF 70 over 3GPP access while the UE 3 has the Allowed NSSAI over the non-3GPP access.
The steps 7b and 8b can takes place before steps 5b and 6b. Step 7b may be performed after step 5b. Step 5b may be performed after step 7b.
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 (PN1-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, and a Network Slice-Specific Authentication and Authorization Function (NSSAAF) 76. 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 (PN1-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).
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 estimates 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 (PN1-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 estimates 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 (PN1-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 (PN1-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 (PN1-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 (PN1-NPN). An AMF 7001 and an AMF 7002 may have same components to the AMF 70.
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 (PN1-NPN). A PCF 7301 and a PCF 7302 may have same components to the PCF 73.
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 (PN1-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 (PN1-NPN).
The NSSAAF 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 (PN1-NPN).
The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following.
The subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to the current PLMN, if the S-NSSAI is neither in the rejected NSSAI f nor associated to the S-NSSAI(s) in the rejected NSSAI. In addition, if the NSSRG information is available, the subset of configured NSSAI provided in the requested NSSAI shall be associated with at least one common NSSRG value. If the UE has pending NSSAI, the subset of configured NSSAI provided in the requested NSSAI and pending NSSAI shall be associated with at least one common NSSRG value. If the UE has already an allowed NSSAI for the other access, all the S-NSSAI(s) in the requested NSSAI for the current access shall share at least an NSSRG value common to all the S-NSSAI(s) of the allowed NSSAI for the other access. If the UE is simultaneously performing the registration procedure on the other access, the UE shall include S-NSSAIs that share at least a common NSSRG value across all access types.
The AMF may include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message if:
The subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to this PLMN, if the S-NSSAI is neither in the rejected NSSAI nor associated to the S-NSSAI(s) in the rejected NSSAI. In addition, if the NSSRG information is available, the subset of configured NSSAI provided in the requested NSSAI shall be associated with at least one common NSSRG value. If the UE has pending NSSAI, the subset of configured NSSAI provided in the requested NSSAI and pending NSSAI shall be associated with at least one common NSSRG value. If the UE has already an allowed NSSAI for the other access, all the S-NSSAI(s) in the requested NSSAI for the current access shall share at least an NSSRG value common to all the S-NSSAI(s) of the allowed NSSAI for the other access. If the UE is simultaneously performing the registration procedure on the other access, the UE shall include S-NSSAIs that share at least a common NSSRG value across all access types.
The AMF may include a new configured NSSAI for the current PLMN in the REGISTRATION ACCEPT message if:
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 Aspects disclosed above can be described as, but not limited to, the following supplementary notes.
supplementary note 1. A method of a user equipment (UE), the method comprising:
supplementary note 2. A method of a communication apparatus, the method comprising:
supplementary note 3. A user equipment (UE) comprising:
supplementary note 4. A communication apparatus comprising:
supplementary note 5. A method of a communication apparatus, the method comprising:
supplementary note 6. A method of a user equipment (UE), the method comprising:
supplementary note 7. A communication apparatus comprising:
supplementary note 8. A user equipment (UE) comprising:
supplementary note 1. A method of a user equipment (UE), the method comprising:
supplementary note 2. The method according to supplementary note 1, further comprising:
supplementary note 3. A user equipment (UE) comprising:
supplementary note 4. The UE according to supplementary note 3, further comprising:
A method of a communication apparatus, the method comprising:
The method according to supplementary note 5,
The method according to supplementary note 5 or 6,
A communication apparatus comprising:
The communication apparatus according to supplementary note 8,
The communication apparatus according to supplementary note 8 or 9,
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 provisional patent application No. 202211016659, filed on Mar. 24, 2022, the disclosure of which is incorporated herein in its entirety by reference.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202211016659 | Mar 2022 | IN | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2023/010547 | 3/17/2023 | WO |
