Method for registering terminal in wireless communication system and apparatus therefor

Patent metadata

Field	Value
Publication number	US-11224084-B2
Application number	US-201916727365-A
Country	US
Kind code	B2
Filing date	Dec 26, 2019
Priority date	Jun 17, 2017
Publication date	Jan 11, 2022
Grant date	Jan 11, 2022

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.

First claim

The invention claimed is:

1. A method performed by a user equipment (UE) operating 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 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 comprising (i) information regarding the rejected S-NSSAI, and (ii) a rejection cause for the rejected S-NSSAI, the rejection cause is at least one of (i) the rejected S-NSSAI not being available in a current public land mobile network (PLMN) or (ii) the rejected S-NSSAI not being available in a current registration area, and
the method further comprises:
storing the rejected S-NSSAI in a rejected NSSAI based on the rejection cause;
deleting the stored rejected S-NSSAI from a list of NSSAI for the current PLMN
based on the rejection cause being that the stored rejected S-NSSAI is not available in the current PLMN; 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 the current registration area, and (ii) the UE leaving the current registration area;
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.

2. The method of claim 1 , 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 available in the current PLMN, and (ii) the stored rejected S-NSSAI being deleted from the rejected NSSAI.

3. The method of claim 1 , wherein based on the AMF allowing an S-NSSAI other than the rejected S-NSSAI among the at least one S-NSSAI in the requested NSSAI:
the registration accept message further comprises an allowed NSSAI comprising the allowed S-NSSAI.

4. The method of claim 3 , 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.

5. The method of claim 3 , 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.

6. 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 the method further comprises:
removing the stored rejected S-NSSAI from the rejected NSSAI.

7. 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.

8. 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.

9. A user equipment (UE) configured to operate 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 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 comprising (i) the rejected S-NSSAI, and (ii) a rejection cause for the rejected S-NSSAI,
the rejection cause is at least one of (i) the rejected S-NSSAI not being available in a current public land mobile network (PLMN) or (ii) the rejected S-NSSAI not being available in a current registration area, and
the operations further comprise:
storing the rejected S-NSSAI in a rejected NSSAI based on the rejection cause;
deleting the stored rejected S-NSSAI from a list of NSSAI for the current PLMN
based on the rejection cause being that the stored rejected S-NSSAI is not available in the current PLMN; 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 the current registration area, and (ii) the UE leaving the current registration area;
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.

10. The UE of claim 9 , 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 available in the current PLMN, and (ii) the stored rejected S-NSSAI being deleted from the rejected NSSAI.

11. The UE of claim 9 , wherein based on the AMf allowing an S-NSSAI other than the rejected S-NSSAI among the at least one S-NSSAI in the requested NSSAI:
the registration accept message further comprises an allowed NSSAI comprising the allowed S-NSSAI.

12. The UE of claim 11 , 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.

13. The UE of claim 11 , 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.

14. The UE of claim 9 , 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, the operations further comprise:
removing the stored rejected S-NSSAI from the rejected NSSAI.

15. The UE of claim 9 , 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.

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

17. A user equipment (UE) configured to operate in a wireless communication system, the UE comprising:
at least one processor; and
at least one computer memory operably connectable to the at least one processor,
wherein the at least one processor is configured to perform operations comprising:
generating a registration request message,
wherein the registration request message comprises requested network slice selection assistance information (NSSAI), and
w

Assignees

• Lg Electronics Inc

Inventors

• Park Sangmin
• Ryu Jinsook
• Kim Hyunsook
• Youn Myungjune

Classifications

• H04W60/00 Primary

  Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration · CPC title

• H04W8/22

  Processing or transfer of terminal data, e.g. status or physical capabilities · CPC title

• H04W4/16

  Communication-related supplementary services, e.g. call-transfer or call-hold · CPC title

• H04W8/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 title

• H04W80/08

  Upper layer protocols {(network arrangements or communication protocols for networked applications H04L67/00)} · CPC title