CN-115866712-B - Network slice allocation and network slice rejection

Abstract

The present disclosure relates to network slice allocation and network slice rejection. A User Equipment (UE) configured to transmit a first registration request to a network, receive a registration accept message in response to the first registration request, the registration accept message including a rejected network slice and an indication of a reject reason corresponding to the rejected network slice, and transmit a second registration request to the network including the requested network slice, wherein the requested network slice and the rejected network slice are the same network slice.

Inventors

• S.T. Ramapa
• A. R.V. Kumar
• K. Keith
• N. Koshta
• S. Prakasham

Assignees

• 苹果公司

Dates

Publication Date

20260512

Application Date

20220915

Priority Date

20210924

Claims (20)

1. 1. A method performed by a user equipment, UE, the method comprising: transmitting a first registration request to a mobility management function AMF of a fifth generation 5G network; receiving a registration accept message in response to the first registration request, the registration accept message including a rejected network slice and an indication of a reject cause corresponding to the rejected network slice, the indication indicating that the rejected network slice is not allowed in a first tracking area of a registration area; Initiating a mobility registration update, MRU, based on the registration accept message, and After initiating the MRU, a second registration request including the requested network slice is transmitted from a second tracking area of the registration area to the AMF, wherein the requested network slice and the rejected network slice are the same network slice.
2. 2. The method of claim 1, wherein the UE is deployed within a same registration area upon receiving the registration accept message and transmitting the second registration request.
3. 3. The method of claim 1, wherein the reject cause is specific to the first tracking area of the registration area.
4. 4. The method of claim 3, wherein the reject cause is indicated using an extended rejected network slice selection assistance information NSSAI information element.
5. 5. The method of claim 1, further comprising: an indication of one or more tracking area identities TAIs within the registration area that allow the rejected network slice is received before transmitting the second registration request.
6. 6. The method of claim 1, wherein the reject cause is specific to an access and mobility management function, AMF.
7. 7. The method of claim 1, further comprising: An indication of network slices allowed by each AMF within the pool of access and mobility management functions AMFs is received before transmitting the second registration request.
8. 8. A method performed by a network function, the method comprising: receiving a first registration request from a user equipment UE; Transmitting a first registration accept message responsive to the first registration request, the first registration accept message including a rejected network slice and an indication of a reject cause corresponding to the rejected network slice, the indication indicating that the rejected network slice is not allowed in a first tracking area of a registration area; Receiving a second registration request from the UE as part of a UE-initiated mobility registration update, MRU, while the UE is in a second tracking area of the registration area, the second registration request including a requested network slice, wherein the requested network slice and the rejected network slice are the same network slice, and A second registration accept message is transmitted in response to the second registration request.
9. 9. The method of claim 8, wherein the UE is deployed within a same registration area upon receiving the registration accept message and transmitting the second registration request.
10. 10. The method of claim 8, wherein the reject cause is specific to the first tracking area of the registration area.
11. 11. The method of claim 10, wherein the reject cause is indicated using an extended rejected network slice selection assistance information NSSAI information element.
12. 12. The method of claim 8, further comprising: An indication of one or more tracking area identities TAIs within the registration area that allow the rejected network slice is transmitted before the second registration request is received.
13. 13. The method of claim 8, wherein the network function is an access and mobility management function, AMF, and the reject cause is specific to the AMF.
14. 14. The method of claim 8, further comprising: An indication of network slices allowed by each AMF within the pool of access and mobility management functions AMFs is transmitted before receiving the second registration request.
15. 15. The method of claim 8, further comprising: In response to the second registration request, an AMF reassignment procedure to an AMF within the pool of access and mobility management functions AMFs is initiated.
16. 16. A user equipment, UE, comprising: a transceiver configured to communicate with a network, and A processor communicatively coupled to the transceiver and configured to: generating a first registration request for transmission to a mobility management function AMF of a fifth generation 5G network; receiving a registration accept message in response to the first registration request, the registration accept message including a rejected network slice and an indication of a reject cause corresponding to the rejected network slice, the indication indicating that the rejected network slice is not allowed in a first tracking area of a registration area; Initiating a mobility registration update, MRU, based on the registration accept message, and A second registration request including the requested network slice is generated for transmission to the AMF, wherein the requested network slice and the rejected network slice are the same network slice.
17. 17. The UE of claim 16, wherein the UE is disposed within a same registration area upon receiving the registration accept message and transmitting the second registration request.
18. 18. The UE of claim 16, wherein the reject cause is specific to the first tracking area of the registration area.
19. 19. The UE of claim 18, wherein the reject cause is indicated using an extended rejected network slice selection assistance information NSSAI information element.
20. 20. The UE of claim 16, the operations further comprising: an indication of one or more tracking area identities TAIs within the registration area that allow the rejected network slice is received before transmitting the second registration request.

Description

Network slice allocation and network slice rejection Technical Field Embodiments of the present disclosure generally relate to a method for communication. Background A User Equipment (UE) may be connected to a network that deploys a plurality of network slices. Generally, network fragmentation refers to an end-to-end logical network configured to provide a particular service and/or have particular network characteristics. Each network slice may be isolated from each other but run on a shared network infrastructure. Thus, each network slice may share network resources, but facilitate different functions. During operation, a scenario may occur in which the UE cannot access the desired network slice. This may have a negative impact on the user experience associated with the UE and/or the applications running on the UE. Thus, there is a need for mechanisms that enable a UE to access its desired network slice. Disclosure of Invention Some example embodiments relate to a processor of a User Equipment (UE) configured to perform operations. The operations include transmitting a first registration request to a network, receiving a registration acceptance message including a rejected network slice and an indication of a rejection reason corresponding to the rejected network slice in response to the first registration request, and transmitting a second registration request to the network including the requested network slice, wherein the requested network slice and the rejected network slice are the same network slice. Other exemplary embodiments relate to a processor of a network function configured to perform operations. The operations include receiving a first registration request from a User Equipment (UE), transmitting a first registration accept message including a rejected network slice and an indication of a reject cause corresponding to the rejected network slice in response to the first registration request, receiving a second registration request including the requested network slice from the UE, wherein the requested network slice and the rejected network slice are the same network slice, and transmitting a second registration accept message in response to the second registration request. Still further exemplary embodiments relate to a processor of a User Equipment (UE) configured to perform operations. The operations include establishing a Packet Data Unit (PDU) session on a first network slice, determining that a PDU session transfer from the first network slice to a second, different network slice is to be performed, and continuing the PDU session on the second, different network slice. Drawings Fig. 1 illustrates an exemplary network arrangement according to various exemplary embodiments. Fig. 2 illustrates an exemplary network architecture according to various exemplary embodiments. Fig. 3 illustrates an exemplary User Equipment (UE) in accordance with various exemplary embodiments. Fig. 4 illustrates an exemplary base station in accordance with various exemplary embodiments. Fig. 5 illustrates an example of a Registration Area (RA) including a plurality of tracking areas according to various exemplary embodiments. Fig. 6 shows a signaling diagram including an example of network slice rejection at the tracking area level. Fig. 7 shows a table comprising cause values and corresponding reject causes for rejected Network Slice Selection Assistance Information (NSSAI). Fig. 8 shows a signaling diagram including an example of network slice rejection at the access and mobility management function (AMF) level. Fig. 9 shows a table comprising cause values for the rejected NSSAI and corresponding reject causes. Fig. 10 illustrates a method for transferring an existing Packet Data Unit (PDU) session from a first network slice to a second, different network slice, in accordance with various exemplary embodiments. Fig. 11 illustrates a signaling diagram for UE-initiated PDU session modification in accordance with various exemplary embodiments. Fig. 12 illustrates a signaling diagram for UE-initiated PDU session establishment with handover in accordance with various exemplary embodiments. Fig. 13 illustrates a signaling diagram for a network initiated PDU session modification procedure in accordance with various exemplary embodiments. Fig. 14 illustrates a signaling diagram for a network initiated PDU session modification procedure in accordance with various exemplary embodiments. Detailed Description The exemplary embodiments may be further understood with reference to the following description and the appended drawings, wherein like elements have the same reference numerals. The exemplary embodiments introduce enhancements to network fragmentation. In one aspect, exemplary embodiments relate to network slice rejection. In another aspect, the exemplary embodiments relate to network slice allocation and include a mechanism for transferring an existing Packet Data Unit (PDU) session from a first network slice to a