Network slice allocation and network slice rejection
A user equipment (UE) is configured to transmit a first registration request to a network, receive a registration accept message in response to the first registration request comprising a rejected network slice and an indication of a rejection cause corresponding to the rejected network slice and transmit a second registration request to the network comprising a requested network slice, wherein the requested network slice and the rejected network slice are a same network slice.
1. A processor of a user equipment (UE) configured to perform operations comprising:
generating for transmission to an access and mobility function (AMF) of a fifth generation (5G) network, a first registration request;
receiving a registration accept message in response to the first registration request comprising a rejected network slice and an indication of a rejection cause corresponding to the rejected network slice 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
generating, for transmission to the AMF, a second registration request comprising a requested network slice, wherein the requested network slice and the rejected network slice are a same network slice and wherein the UE transmits the second registration request from a second tracking area of the registration area after initiating the MRU.
2. The processor of claim 1 , wherein the UE is deployed within a same registration area when receiving the registration accept message and transmitting the second registration request.
3. The processor of claim 1 , wherein the rejection cause is specific to the first tracking area of the registration area.
4. The processor of claim 3 , wherein the rejection cause is indicated using an extended rejected network slice selection assistance information (NSSAI) information element.
5. The processor of claim 1 , the operations further comprising:
receiving, prior to transmitting the second registration request, an indication of one or more tracking area identities (TAIs) within the registration area that allow the rejected network slice.
6. The processor of claim 1 , wherein the rejection cause is specific to an access and mobility management function (AMF).
7. The processor of claim 1 , the operations further comprising:
receiving, prior to transmitting the second registration request, an indication of network slices allowed by each access and mobility management function (AMF) within an AMF pool.
8. A processor of a network function configured to perform operations comprising:
receiving a first registration request from a user equipment (UE);
generating, for transmission to the UE, a first registration accept message in response to the first registration request comprising a rejected network slice and an indication of a rejection cause corresponding to the rejected network slice 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 updated (MRU) when the UE is in a second tracking area of the registration area, the second registration request comprising a requested network slice, wherein the requested network slice and the rejected network slice are a same network slice; and
generating, for transmission to the UE, a second registration accept message in response to the second registration request.
9. The processor of claim 8 , wherein the UE is deployed within a same registration area when receiving the registration accept message and transmitting the second registration request.
10. The processor of claim 8 , wherein the rejection cause is specific to the first tracking area of the registration area.
11. The processor of claim 10 , wherein the rejection cause is indicated using an extended rejected network slice selection assistance information (NSSAI) information element.
12. The processor of claim 8 , the operations further comprising:
transmitting, prior to receiving the second registration request, an indication of one or more tracking area identities (TAIs) within the registration area that allow the rejected network slice.
13. The processor of claim 8 , wherein the network function is an access and mobility management function (AMF) and the rejection cause is specific to the AMF.
14. The processor of claim 8 , the operations further comprising:
transmitting, prior to receiving the second registration request, an indication of network slices allowed by each access and mobility management function (AMF) within an AMF pool.
15. The processor of claim 8 , the operations further comprising:
initiating, in response to the second registration request, an access and mobility management function (AMF) reallocation procedure to an AMF within an AMF pool.
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 perform operations comprising:
generating for transmission to an access and mobility function (AMF) of a fifth generation (5G) network, a first registration request;
receiving a registration accept message in response to the first registration request comprising a rejected network slice and an indication of a rejection cause corresponding to the rejected network slice 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
generating, for transmission to the AMF, a second registration request comprising a requested network slice, wherein the requested network slice and the rejected network slice are a same network slice.
17. The UE of claim 16 , wherein the UE is deployed within a same registration area when receiving the registration accept message and transmitting the second registration request.
18. The UE of claim 16 , wherein the rejection cause is specific to the first tracking area of the registration area.
19. The UE of claim 18 , wherein the rejection cause is indicated using an extended rejected network slice selection assistance information (NSSAI) information element.
20. The UE of claim 16 , the operations further comprising:
receiving, prior to transmitting the second registration request, an indication of one or more tracking area identities (TAIs) within the registration area that allow the rejected network slice.