IP Library › Granted Patent US 12,363,595
Granted Patent B2
US 12,363,595 · App. 18/491,142 · Granted Jul 15, 2025

Apparatus and method for supporting session continuity in wireless communication system

Inventors: Hoyeon Lee (Suwon-si, KR); Sangsoo Jeong (Suwon-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W36/0011H04W36/00H04W36/13H04W36/14H04W36/1443
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,363,595
App. No.
18/491,142
Granted
Jul 15, 2025
Kind
B2
Abstract

A method performed by a user equipment (UE) in a wireless communication system is provided. The method includes transmitting, to an access and mobility function (AMF), a registration request message for moving to a first public land mobile network (PLMN) from a second PLMN, receiving, from the AMF, a registration accept message including first single-network slice selection assistance information (S-NSSAI) corresponding to the first PLMN of the AMF, determining whether second S-NSSAI associated with a protocol data unit (PDU) session established for the UE matches to the first S-NSSAI, wherein the second S-NSSAI corresponds to the second PLMN, and locally updating the PDU session based on a result of the determining.

Claims (77)

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

identifying information related to single-network slice selection assistance information (S-NSSAI) of a first public land mobile network (PLMN), wherein the information related to the S-NSSAI of the first PLMN is associated with a protocol data unit (PDU) session, and wherein the information related to the S-NSSAI of the first PLMN includes a first S-NSSAI and a second S-NSSAI mapped to the first S-NSSAI;

transmitting, to an access and mobility management function (AMF) entity, a registration request message for a second PLMN;

receiving, from the AMF entity, a registration accept message including allowed network slice selection assistance information (NSSAI), wherein the allowed NSSAI includes a third S-NSSAI and a fourth S-NSSAI mapped to the third S-NSSAI;

identifying whether the second S-NSSAI associated with the PDU session matches to the fourth S-NSSAI; and

updating the first S-NSSAI associated with the PDU session to the third S-NSSAI in case that the second S-NSSAI matches to the fourth S-NSSAI.

2. The method of claim 1 , further comprising:

identifying the first S-NSSAI associated with the PDU session, based on UE route selection policy (URSP) information; and

establishing the PDU session in the first PLMN.

3. The method of claim 1 ,

wherein the first S-NSSAI includes a first slice/service type (SST),

wherein the second S-NSSAI mapped to the first S-NSSAI includes a second SST,

wherein the third S-NSSAI includes a third SST, and

wherein the fourth S-NSSAI mapped to the third S-NSSAI includes a fourth SST.

4. The method of claim 3 ,

wherein the first S-NSSAI further includes a slice differentiator (SD),

wherein the second S-NSSAI mapped to the first S-NSSAI further includes a second SD,

wherein the third S-NSSAI further includes a third SD, and

wherein the fourth S-NSSAI mapped to the third S-NSSAI further includes a fourth SD.

5. The method of claim 1 , wherein identifying whether the second S-NSSAI associated with the PDU session matches to the fourth S-NSSAI comprises:

identifying whether a second SST included in the second S-NSSAI mapped to the first S-NSSAI is matched to a fourth SST included in the fourth S-NSSAI mapped to the third S-NSSAI.

6. The method of claim 1 , wherein identifying whether the second S-NSSAI associated with the PDU session matches to the fourth S-NSSAI comprises:

identifying whether a second SD included in the second S-NSSAI mapped to the first S-NSSAI is matched to a fourth SD included in the fourth S-NSSAI mapped to the third S-NSSAI.

7. The method of claim 1 ,

wherein the PDU session established in the first PLMN is used in the second PLMN by locally updating the first S-NSSAI to the third S-NSSAI, and

wherein after the UE moves to the second PLMN from the first PLMN the PDU session is used continuously and not released.

8. A method performed by an access and mobility management function (AMF) entity in a wireless communication system, the method comprising:

receiving, from a user equipment (UE), a registration request message for a second public land mobile network (PLMN); and

transmitting, to the UE, a registration accept message including allowed network slice selection assistance information (NSSAI), wherein the allowed NSSAI includes a third single-network slice selection assistance information (S-NSSAI) and a fourth S-NSSAI mapped to the third S-NSSAI;

wherein information related to S-NSSAI of a first PLMN is associated with a protocol data unit (PDU) session,

wherein the information related to the S-NSSAI of the first PLMN includes a first S-NSSAI and a second S-NSSAI mapped to the first S-NSSAI, and

wherein the first S-NSSAI associated with the PDU session is updated to the third S-NSSAI in case that the second S-NSSAI matches to the fourth S-NSSAI.

9. The method of claim 8 ,

wherein the first S-NSSAI associated with the PDU session is based on UE route selection policy (URSP) information, and

wherein the PDU session is established in the first PLMN.

10. The method of claim 8 ,

wherein the first S-NSSAI includes a first slice/service type (SST),

wherein the second S-NSSAI mapped to the first S-NSSAI includes a second SST,

wherein the third S-NSSAI includes a third SST, and

wherein the fourth S-NSSAI mapped to the third S-NSSAI includes a fourth SST.

11. The method of claim 10 ,

wherein the first S-NSSAI further includes a slice differentiator (SD),

wherein the second S-NSSAI mapped to the first S-NSSAI further includes a second SD,

wherein the third S-NSSAI further includes a third SD, and

wherein the fourth S-NSSAI mapped to the third S-NSSAI further includes a fourth SD.

12. The method of claim 8 , wherein the first S-NSSAI associated with the PDU session is updated to the third S-NSSAI in case that a second SST included in the second S-NSSAI mapped to the first S-NSSAI is matched to a fourth SST included in the fourth S-NSSAI mapped to the third S-NSSAI.

13. The method of claim 8 , wherein the first S-NSSAI associated with the PDU session is updated to the third S-NSSAI in case that a second SD included in the second S-NSSAI mapped to the first S-NSSAI is matched to a fourth SD included in the fourth S-NSSAI mapped to the third S-NSSAI.

14. The method of claim 8 ,

wherein the PDU session established in the first PLMN is used in the second PLMN by locally updating the first S-NSSAI to the third S-NSSAI, and

wherein after the UE moves to the second PLMN from the first PLMN the PDU session is used continuously and not released.

15. A user equipment (UE) in a wireless communication system, the UE comprising:

a transceiver; and

at least one processor operably connected with the transceiver, the at least one processor configured to:

identify information related to single-network slice selection assistance information (S-NSSAI) of a first public land mobile network (PLMN), wherein the information related to the S-NSSAI of the first PLMN is associated with a protocol data unit (PDU) session, and wherein the information related to the S-NSSAI of the first PLMN includes a first S-NSSAI and a second S-NSSAI mapped to the first S-NSSAI,

control the transceiver to transmit, to an access and mobility management function (AMF) entity, a registration request message for a second PLMN,

control the transceiver to receive, from the AMF entity, a registration accept message including allowed network slice selection assistance information (NSSAI), wherein the allowed NSSAI includes a third S-NSSAI and a fourth S-NSSAI mapped to the third S-NSSAI,

identify whether the second S-NSSAI associated with the PDU session matches to the fourth S-NSSAI, and

update the first S-NSSAI associated with the PDU session to the third S-NSSAI in case that the second S-NSSAI matches to the fourth S-NSSAI.

16. The UE of claim 15 , wherein the at least one processor is further configured to:

identify the first S-NSSAI associated with the PDU session, based on UE route selection policy (URSP) information, and

establish the PDU session in the first PLMN.

17. The UE of claim 15 ,

wherein the first S-NSSAI includes a first slice/service type (SST),

wherein the second S-NSSAI mapped to the first S-NSSAI includes a second SST,

wherein the third S-NSSAI includes a third SST, and

wherein the fourth S-NSSAI mapped to the third S-NSSAI includes a fourth SST.

18. The UE of claim 17 ,

wherein the first S-NSSAI further includes a slice differentiator (SD),

wherein the second S-NSSAI mapped to the first S-NSSAI further includes a second SD,

wherein the third S-NSSAI further includes a third SD, and

wherein the fourth S-NSSAI mapped to the third S-NSSAI further includes a fourth SD.

19. The UE of claim 15 , wherein the at least one processor is configured to:

identify whether a second SST included in the second S-NSSAI mapped to the first S-NSSAI is matched to a fourth SST included in the fourth S-NSSAI mapped to the third S-NSSAI, and

identify whether a second SD included in the second S-NSSAI mapped to the first S-NSSAI is matched to a fourth SD included in the fourth S-NSSAI mapped to the third S-NSSAI.

20. The UE of claim 15 ,

wherein the PDU session established in the first PLMN is used in the second PLMN by locally updating the first S-NSSAI to the third S-NSSAI, and

wherein after the UE moves to the second PLMN from the first PLMN the PDU session is used continuously and not released.

Priority Claims (1)
KR 10-2019-0053245 · May 7, 2019 · national
Continuity (4)
Continuation 17954881 · Sep 28, 2022
Continuation 16868034 · May 6, 2020
Related Publication 20240137816A1 · Apr 25, 2024
Related Publication 20240236773A9 · Jul 11, 2024
References Cited (23)
US 11470513B2 · Lee et al. · 2022 [cited by applicant]
US 11523465B2 · Yang et al. · 2022 [cited by applicant]
US 20190029065A1 · Park et al. · 2019 [cited by applicant]
US 20190053148A1 · Lee · 2019 [cited by examiner]
US 20190297148A1 · Zong · 2019 [cited by examiner]
WO 2018232570A1 · 2018 [cited by applicant]
WO 2018234085A1 · 2018 [cited by applicant]
WO 2018236819A1 · 2018 [cited by applicant]
WO 2019034249A1 · 2019 [cited by applicant]
Chinese Office Action with English translation dated Feb. 8, 2024; Chinese Appln. No. 202010381374.8. [cited by applicant]
European Communication pursuant to Article 94(3) EPC dated Feb. 22, 2024; European Appln. No. 20 173 406.8-1216. [cited by applicant]
3GPP; 3GPP TS 24.501; V16.0.2; Mar. 29, 2019; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16). [cited by applicant]
Ericsson; Provisioning of Requested NSSAI at mobility update and inter system change to N1 mode; 3GPP TSG CT WG1 Meeting #116; C1-192371; Apr. 8-12, 2019; Xi'an (P.R. of China). [cited by applicant]
Ericsson; Discussion on how to provide only mapped S-NSSAI of HPLMN to VPLMN; 3GPP TSG CT WG1 Meeting #115; C1-191142; XP 51598059 A; Feb. 25-Mar. 1, 2019; Montreal, Canada. [cited by applicant]
Qualcomm Incorporated, et al.; TS 23.501: Applicability of UE slicing configuration in roaming scenarios; SA WG2 Meeting #S2-123; S2-178030, XP 51360647 A; Oct. 23-27, 2017; Ljubljana, Slovenia. [cited by applicant]
International Search Report with Written Opinion dated Aug. 6, 2020; International Appln. No. PCT/KR2020/005966. [cited by applicant]
European Search Report dated Sep. 16, 2020; European Appln. No. 20173406.8-1212. [cited by applicant]
Sharp, “Clarification on configured S-NSSAI not associated with a PLMN_Alt3,” 3GPP TSG-CT WG1 Meeting #112bis C1-186415, Vilnius (Lithuania), Oct. 15-19, 2018. [cited by applicant]
European Office Action dated Apr. 11, 2022, issued in European Application No. 20173406.8. [cited by applicant]
Indian Office Action dated Aug. 4, 2023, issued In Indian Application No. 202137056439. [cited by applicant]
Ericsson; Slice configuration change; SA WG2 Meeting #127-bis; S2-184867; Newport Beach, USA; May 28-Jun. 1, 2018. [cited by applicant]
Korean Office Action with English translation dated Feb. 17, 2025; Korean Appln. No. 10-2019-0053245. [cited by applicant]
European Notice of Allowance dated Jan. 20, 2025; European Appln. No. 20 173 406.8 - 1215. [cited by applicant]