METHOD FOR REGISTERING TERMINAL IN WIRELESS COMMUNICATION SYSTEM AND APPARATUS THEREFOR

• US 20200137552A1
• Filed: 12/26/2019
• Published: 04/30/2020
• Est. Priority Date: 06/17/2017
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: PARK, Sangmin, RYU, Jinsook, KIM, Hyunsook, YOUN, Myungjune
• Granted Patent: US 11,224,084 B2
• Time in Patent Office: Days
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 16/18 Network planning tools
• CPC Class Codes: H04W 4/16 Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 48/02 Access restriction performed under specific conditions
• CPC Class Codes: H04W 48/18 Selecting a network or a communication service
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 60/06 De-registration or detaching
• CPC Class Codes: H04W 76/18 Management of setup rejection or failure
• CPC Class Codes: H04W 76/27 Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 8/02 Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/08 Mobility data transfer
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 80/08 Upper layer protocols network arrangements or communication protocols for networked applications H04L67/00
• CPC Class Codes: H04W 84/042 Public Land Mobile systems, e.g. cellular systems

Abstract

A registration method of a user equipment (UE) in a wireless communication system is disclosed. The registration method includes transmitting a registration request message to an access and mobility management function (AMF), wherein the registration request message includes requested network slice selection assistance information (NSSAI) including single (S)-NSSAI corresponding to a network slice to which the UE intends to register with; and receiving, from the AMF, a registration accept message as a response to the registration request message, wherein if at least one of the S-NSSAI included in the requested NSSAI is rejected by the AMF, the registration accept message includes the rejected S-NSSAI and a reason for refusal for the rejected S-NSSAI.

Claims

1. A method of registering a user equipment (UE) in a wireless communication system, the method comprising:

transmitting a registration request message to an access and mobility management function (AMF), wherein the registration request message comprises a requested network slice selection assistance information (NSSAI), and wherein the requested NSSAI comprises at least one single NSSAI (S-NSSAI) corresponding to a network slice with which the UE requests to register; and

receiving, from the AMF, a registration accept message in response to the registration request message,

wherein based on the AMF rejecting an S-NSSAI among the at least one S-NSSAI in the requested NSSAI;

the registration accept message comprises (i) information regarding the rejected S-NSSAI, and (ii) a rejection cause for the rejected S-NSSAI, and

the method further comprises;

storing the rejected S-NSSAI in a rejected NSSAI based on the rejection cause; and

attempting to use the stored rejected S-NSSAI based on (i) the rejection cause being that the stored rejected S-NSSAI is not available in a current registration area, and (ii) the UE leaving the current registration area.

2. The method of claim 1, wherein attempting to use the stored rejected S-NSSAI comprises:

transmitting, to the AMF, a second registration request message comprising the stored rejected S-NSSAI.

3. The method of claim 1, wherein the rejection cause is based on at least one of (i) whether the stored rejected S-NSSAI corresponds to at least one Preferred List of Mobile Network (PLMN), or (ii) whether the stored rejected S-NSSAI is not available in the current registration area.

4. The method of claim 3, wherein the at least one PLMN corresponds to either (i) a current PLMN of the UE, or (ii) all PLMNs of the UE.

5. The method of claim 3, further comprising:

attempting to use the stored rejected S-NSSAI based on (i) the rejection cause being that the stored rejected S-NSSAI is not valid in the at least one PLMN, and (ii) the stored rejected S-NSSAI being deleted from the rejected NSSAI.

6. The method of claim 3, wherein based on the AMF allowing an S-NSSAI other than the rejected S-NSSAI among the least one S-NSSAI in the requested NSSAI:

the registration accept message further comprises an allowed NSSAI comprising the allowed S-NSSAI.

7. The method of claim 6, wherein based on the allowed NSSAI not having already been stored by the UE, a configuration for the PLMN comprises the allowed NSSAI or a subset of S-NSSAIs in the allowed NSSAI.

8. The method of claim 6, wherein based on the allowed NSSAI having already been stored by the UE, the requested NSSAI comprises the allowed NSSAI or a subset of S-NSSAIs in the allowed NSSAI.

9. The method of claim 1, wherein based on (i) the rejection cause being that the stored rejected S-NSSAI is not available in the current registration area, and (ii) the rejection cause for the stored rejected S-NSSAI having been alleviated due to the UE leaving the current registration area:

removing the stored rejected S-NSSAI from the rejected NSSAI.

10. The method of claim 1, wherein storing the rejected S-NSSAI in the rejected NSSAI comprises:

storing the rejected S-NSSAI in a list of stored rejected S-NSSAIs in the rejected NSSAI.

11. The method of claim 1, wherein the UE does not attempt to use the stored rejected S-NSSAI until the UE leaves the current registration area.

12. A user equipment (UE) configured to perform a registration procedure in a wireless communication system, the UE comprising:

a transceiver;

at least one processor; and

at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations comprising;

transmitting a registration request message through the transceiver to an access and mobility management function (AMF), wherein the registration request message comprises a requested network slice selection assistance information (NSSAI), and wherein the requested NSSAI comprises at least one single NSSAI (S-NSSAI) corresponding to a network slice with which the UE requests to register; and

receiving, from the AMF through the transceiver, a registration accept message in response to the registration request message,

wherein based on the AMF rejecting an S-NSSAI among the at least one S-NSSAI in the requested NSSAI;

the registration accept message comprises (i) information regarding the rejected S-NSSAI, and (ii) a rejection cause for the rejected S-NSSAI, and

the operations further comprise;

storing the rejected S-NSSAI in a rejected NSSAI based on the rejection cause; and

attempting to use the stored rejected S-NSSAI based on (i) the rejection cause being that the stored rejected S-NSSAI is not available in a current registration area, and (ii) the UE leaving the current registration area.

13. The UE of claim 12, wherein attempting to use the stored rejected S-NSSAI comprises:

transmitting, to the AMF, a second registration request message comprising the stored rejected S-NSSAI.

14. The UE of claim 12, wherein the rejection cause is based on at least one of (i) whether the stored rejected S-NSSAI corresponds to at least one Preferred List of Mobile Network (PLMN), or (ii) whether the stored rejected S-NSSAI is not available in the current registration area.

15. The UE of claim 14, wherein the at least one PLMN corresponds to either (i) a current PLMN of the UE, or (ii) all PLMNs of the UE.

16. The UE of claim 14, wherein the operations further comprise:

attempting to use the stored rejected S-NSSAI based on (i) the rejection cause being that the stored rejected S-NSSAI is not valid in the at least one PLMN, and (ii) the stored rejected S-NSSAI being deleted from the rejected NSSAI.

17. The UE of claim 14, wherein based on the AMF allowing an S-NSSAI other than the rejected S-NSSAI among the least one S-NSSAI in the requested NSSAI:

the registration accept message further comprises an allowed NSSAI comprising the allowed S-NSSAI.

18. The UE of claim 17, wherein based on the allowed NSSAI not having already been stored by the UE, a configuration for the PLMN comprises the allowed NSSAI or a subset of S-NSSAIs in the allowed NSSAI.

19. The UE of claim 17, wherein based on the allowed NSSAI having already been stored by the UE, the requested NSSAI comprises the allowed NSSAI or a subset of S-NSSAIs in the allowed NSSAI.

20. The UE of claim 12, wherein based on (i) the rejection cause being that the stored rejected S-NSSAI is not available in the current registration area, and (ii) the rejection cause for the stored rejected S-NSSAI having been alleviated due to the UE leaving the current registration area:

removing the stored rejected S-NSSAI from the rejected NSSAI.

21. The UE of claim 12, wherein storing the rejected S-NSSAI in the rejected NSSAI comprises:

storing the rejected S-NSSAI in a list of stored rejected S-NSSAIs in the rejected NSSAI.

22. The UE of claim 12, wherein the UE does not attempt to use the stored rejected S-NSSAI until the UE leaves the current registration area.