IP Library › Granted Patent US 12,550,094
Granted Patent B2
US 12,550,094 · App. 18/059,188 · Granted Feb 10, 2026

Method and apparatus for controlling network slice in wireless communication system

Inventors: Sangsoo Jeong (Suwon-si, KR); Hoyeon Lee (Suwon-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W60/00H04W48/18
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,550,094
App. No.
18/059,188
Granted
Feb 10, 2026
Kind
B2
Abstract

A method, performed by a user equipment (UE), in a wireless communication system, includes: transmitting, to a network entity, a registration request message including network slice assistance information (NSSAI) corresponding to a slice; receiving a response message including rejection information on a registration for the slice in case that resource allocation has reached an upper limit; and determining to suspend a registration request for the slice, based on the response message, wherein the rejection information on the registration for the slice includes information on a back-off timer or information on a rejection cause.

Claims (55)

1 . 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 including a requested network slice selection assistance information (NSSAI) and information indicating that the UE supports a rejected NSSAI related capability, wherein the requested NSSAI contains at least one single NSSAI (S-NSSAI);

transmitting, to a network function (NF) entity, a request message including information related to a number of UEs registered with the at least one S-NSSAI;

receiving, from the NF entity, a response message including information indicating a maximum number of UEs for the at least one S-NSSAI being reached or not being reached; and

transmitting, to the UE, a registration response message including a rejected NSSAI with a reject cause, based on the registration request message.

2 . The method of claim 1 ,

wherein the information indicating that the UE supports a rejected NSSAI related capability is included in 5G mobility management (5GMM) capability information of the registration request message.

3 . The method of claim 1 ,

wherein the registration response message includes a back-off timer value related to a rejected S-NSSAI included in the rejected NSSAI.

4 . The method of claim 1 ,

wherein the registration response message further includes allowed NSSAI in case that a maximum number of UEs has been reached for one or more S-NSSAIs in the requested NSSAI,

wherein the allowed NSSAI includes at least one allowed S-NSSAI included in the requested NSSAI, and

wherein the registration response message corresponds to a registration accept message.

5 . The method of claim 1 ,

wherein the registration response message further includes allowed NSSAI in case that a maximum number of UEs has been reached for all S-NSSAIs in the requested NSSAI and one or more default S-NSSAIs are allowed to the UE,

wherein the allowed NSSAI includes the one or more default S-NSSAI, and

wherein the registration response message corresponds to a registration accept message.

6 . The method of claim 1 ,

wherein the registration response message includes the rejected NSSAI in case that a maximum number of UEs has been reached for all S-NSSAIs in the requested NSSAI, and

wherein the registration response message corresponds to a registration reject message.

7 . The method of claim 1 ,

wherein the information indicating the maximum number of UEs for the at least one S-NSSAI being reached or not being reached is identified, based on the information related to the number of UEs registered with the at least one S-NSSAI.

8 . The method of claim 1 ,

wherein at least one rejected S-NSSAI is included in the rejected NSSAI, based on the requested NSSAI and the information indicating the maximum number of UEs for the at least one S-NSSAI being reached or not being reached.

9 . The method of claim 1 ,

wherein the reject cause indicates that a S-NSSAI is not available due to maximum number of UEs reached.

10 . An access and mobility management function (AMF) entity in a wireless communication system, the AMF comprising:

a transceiver; and

at least one processor coupled with the transceiver and configured to:

receive, from a user equipment (UE) via the transceiver, a registration request message including a requested network slice selection assistance information (NSSAI) and information indicating that the UE supports a rejected NSSAI related capability, wherein the requested NSSAI contains at least one single NSSAI (S-NSSAI),

transmit, to a network function (NF) entity via the transceiver, a request message including information related to a number of UEs registered with the at least one S-NSSAI,

receive, from the NF entity via the transceiver, a response message including information indicating a maximum number of UEs for the at least one S-NSSAI being reached or not being reached, and

transmit, to the UE via the transceiver, a registration response message including a rejected NSSAI with a reject cause, based on the registration request message.

11 . The AMF entity of claim 10 ,

wherein the information indicating that the UE supports a rejected NSSAI related capability is included in 5G mobility management (5GMM) capability information of the registration request message.

12 . The AMF entity of claim 10 ,

wherein the registration response message includes a back-off timer value related to a rejected S-NSSAI included in the rejected NSSAI.

13 . The AMF entity of claim 10 ,

wherein the registration response message further includes allowed NSSAI in case that a maximum number of UEs has been reached for one or more S-NSSAIs in the requested NSSAI,

wherein the allowed NSSAI includes at least one allowed S-NSSAI included in the requested NSSAI, and

wherein the registration response message corresponds to a registration accept message.

14 . The AMF entity of claim 10 ,

wherein the registration response message further includes allowed NSSAI in case that a maximum number of UEs has been reached for all S-NSSAIs in the requested NSSAI and one or more default S-NSSAIs are allowed to the UE,

wherein the allowed NSSAI includes the one or more default S-NSSAI, and

wherein the registration response message corresponds to a registration accept message.

15 . The AMF entity of claim 10 ,

wherein the registration response message includes the rejected NSSAI in case that a maximum number of UEs has been reached for all S-NSSAIs in the requested NSSAI, and

wherein the registration response message corresponds to a registration reject message.

16 . The AMF entity of claim 10 ,

wherein the information indicating the maximum number of UEs for the at least one S-NSSAI being reached or not being reached is identified, based on the information related to the number of UEs registered with the at least one S-NSSAI.

17 . The AMF entity of claim 10 ,

wherein at least one rejected S-NSSAI is included in the rejected NSSAI, based on the requested NSSAI and the information indicating the maximum number of UEs for the at least one S-NSSAI being reached or not being reached.

18 . The AMF entity of claim 10 ,

wherein the reject cause indicates that a S-NSSAI is not available due to maximum number of UEs reached.

19 . The method of claim 1 , wherein the rejected NSSAI with the reject cause is included in the registration response message, based on the information indicating that the UE supports the rejected NSSAI related capability.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 28, 2022
From: JEONG, SANGSOO; LEE, HOYEON
To: SAMSUNG ELECTRONICS CO., LTD
Reel/Frame 061893/0410 →
Priority Claims (2)
KR 10-2019-0141247 · Nov 6, 2019 · national
KR 10-2020-0061212 · May 21, 2020 · national
Continuity (2)
Continuation 17092088 · Nov 6, 2020
Related Publication 20230091600A1 · Mar 23, 2023
References Cited (28)
US 11388624B2 · Chiba et al. · 2022 [cited by applicant]
US 20130007232A1 · Wang · 2013 [cited by examiner]
US 20180324577A1 · Faccin et al. · 2018 [cited by applicant]
US 20180324663A1 · Park et al. · 2018 [cited by applicant]
US 20190029065A1 · Park et al. · 2019 [cited by applicant]
US 20200162919A1 · Velev et al. · 2020 [cited by applicant]
US 20200177333A1 · Liu · 2020 [cited by examiner]
US 20210029628A1 · Kim · 2021 [cited by examiner]
US 20210204154A1 · Li · 2021 [cited by examiner]
US 20220038897A1 · Liu · 2022 [cited by examiner]
US 20220159605A1 · Li · 2022 [cited by examiner]
US 20220200874A1 · Fendt · 2022 [cited by examiner]
CN 110022581A · 2019 [cited by applicant]
EP 3471464A1 · 2019 [cited by applicant]
EP 3654692A1 · 2020 [cited by applicant]
WO 2019011190A1 · 2019 [cited by applicant]
WO 2019139118A1 · 2019 [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority in connection with International Application No. PCT/KR2020/015469 issued Feb. 10, 2021, 9 pages. [cited by applicant]
Ericsson, “Registration reject due to no available allowed S-NSSAI(s),” C1-195187 (rev of C1-194760, 4494), 3GPP TSG-CT WG1 Meeting #119, Wroclaw, Poland, Aug. 26-30, 2019, 22 pages. [cited by applicant]
Supplementary European Search Report dated Sep. 26, 2022, in connection with European Patent Application No. 20884677.4, 13 pages. [cited by applicant]
Nec, ““S-NSSAI not available in the current PLMN” when non NSSAA supported UE requesting the S-NSSAI subjects to NSSAA,” C1-196756, 3GPP TSG-CT WG1 Meeting #120, Portoroz (Slovenia), Oct. 7-11, 2019, 23 pages. [cited by applicant]
Nec et al., “Need of slice based AMF overload control at NG-RAN,” S2-1906365, 3GPP TSG SA2 #133, May 13-17, 2019, Reno, Nevada, 6 pages. [cited by applicant]
NTT Docomo et al., “New Key Issue on support for network slice quota enforcement in a network slice,” S2-1910749, SA WG2 Meeting #135, Oct. 14-18, 2019, Split, HR, 3 pages. [cited by applicant]
Examination report dated Feb. 10, 2023, in connection with Indian Application No. 202237026136, 5 pages. [cited by applicant]
The First Office Action dated Mar. 30, 2024, in connection with Chinese Application No. 202080077397.8, 15 pages. [cited by applicant]
Hearing Notice dated May 15, 2024, in connection with Indian Application No. 202237026136, 3 pages. [cited by applicant]
Communication under Rule 71(3) EPC dated Aug. 7, 2024, in connection with European Application No. 20884677.4, 49 pages. [cited by applicant]
Notification of the Decision to Grant a Patent Right for Patent for Invention dated Jan. 13, 2025, in connection with Chinese Application No. 202080077397.8, 12 pages. [cited by applicant]