IP Library Granted Patent US 12,425,927
Granted Patent B2
US 12,425,927 · App. 17/468,251 · Granted Sep 23, 2025

Network slice information for handover procedure

Inventors: Kyungmin Park (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Alireza Babaei (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA)
Assignee: Peninsula Technologies, LLC
H04W36/0016H04W36/0064H04W36/13H04W36/22H04W76/18H04W8/24H04W28/0268H04W36/00692H04W36/00698
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,425,927
App. No.
17/468,251
Granted
Sep 23, 2025
Kind
B2
Abstract

A first base station determines that session resources for a network slice are not available for a wireless device. The first base station sends to a second base station and based on the determination, a request for a handover of the wireless device. The request comprises: an identifier of the network slice for the handover; and a cause information element indicating that a cause for the handover is that the session resources are not available for the network slice at the first base station. A response to the request is received from the second base station.

Claims (59)

1. A method comprising:

receiving, by a first base station from a core network entity, a first message indicating a request for session resources for a wireless device, wherein the session resources are for a first network slice;

initiating, by the first base station and based on the requested session resources for the first network slice not being available for the wireless device at the first base station, a handover for the wireless device towards a first cell of a second base station;

sending, from the first base station to the second base station and after a determination that the requested session resources for the network slice associated with the first base station are not available for the wireless device, a request for the handover of the wireless device, the request comprising:

a packet flow identifier of a packet flow associated with the first network slice;

a network slice identifier of the network slice for the handover; and

a cause information element indicating that a cause for the handover is that the session resources are not available at the first base station for the network slice associated with the network slice identifier; and

receiving, from the second base station, a response to the request.

2. The method of claim 1 , wherein the second base station determines the response based on at least one of:

the cause information element; or

a traffic load status of one or more cells of the second base station for the network slice.

3. The method of claim 1 , wherein the request further comprises:

a wireless device identifier of the wireless device.

4. The method of claim 3 , wherein the request further comprises a cell identifier of a first cell of the second base station.

5. The method of claim 4 , wherein the response further comprises a rejection cause for rejecting at least one of the request or the packet flow associated with the network slice, the rejection cause indicating that the network slice is not supported by at least one of:

the first cell of the second base station; or

the second base station.

6. The method of claim 1 , wherein the response further comprises at least one of:

an admitted packet flow identifier of an admitted packet flow; or

a non-admitted packet flow identifier of a non-admitted packet flow.

7. The method of claim 1 , wherein the network slice identifier of the network slice comprises

a network slice selection assistance information.

8. The method of claim 1 , wherein the network slice identifier of the network slice comprises a single network slice selection assistance information.

9. The method of claim 1 , wherein the core network entity sends the message based on a session creation request from the wireless device, the session creation request associated with the network slice.

10. The method of claim 1 , wherein the response comprises an acceptance or rejection of the request.

11. A first base station comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the first base station to:

receive, by a first base station from a core network entity, a first message indicating a request for session resources for a wireless device, wherein the session resources are for a first network slice;

initiate, by the first base station and based on the requested session resources for the first network slice not being available for the wireless device at the first base station, a handover for the wireless device towards a first cell of a second base station;

send to the second base station and after a determination that the requested session resources for the network slice associated with the first base station are not available for the wireless device, a request for the handover of the wireless device, the request comprising:

a packet flow identifier of a packet flow associated with the first network slice;

a network slice identifier of a network slice for the handover; and

a cause information element indicating that a cause for the handover is that the session resources are not available at the first base station for the network slice associated with the network slice identifier; and

receive, from the second base station, a response to the request.

12. The first base station of claim 11 , wherein the second base station determines the response based on at least one of:

the cause information element; or

a traffic load status of one or more cells of the second base station for the network slice.

13. The first base station of claim 11 , wherein the request further comprises:

a wireless device identifier of the wireless device.

14. The first base station of claim 13 , wherein the request further comprises a cell identifier of a first cell of the second base station.

15. The first base station of claim 14 , wherein the response further comprises a rejection cause for rejecting at least one of the request or the packet flow associated with the network slice, the rejection cause indicating that the network slice is not supported by at least one of:

the first cell of the second base station; or

the second base station.

16. The first base station of claim 11 , wherein the response further comprises at least one of:

an admitted packet flow identifier of an admitted packet flow; or

a non-admitted packet flow identifier of a non-admitted packet flow.

17. The first base station of claim 11 , wherein the network slice identifier of the network slice comprises

a network slice selection assistance information.

18. The first base station of claim 11 , wherein the network slice identifier of the network slice comprises a single network slice selection assistance information.

19. The first base station of claim 11 , wherein the core network entity sends the message based on a session creation request from the wireless device, the session creation request associated with the network slice.

20. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a device, cause a first base station to perform:

receiving, from a core network entity, a first message indicating a request for session resources for a wireless device, wherein the session resources are for a first network slice;

initiating, based on the requested session resources for the first network slice not being available for the wireless device at the first base station, a handover for the wireless device towards a first cell of a second base station;

sending, to the second base station and after a determination that the requested session resources for the network slice associated with the first base station are not available for the wireless device, a request for the handover of the wireless device, the request comprising:

a packet flow identifier of a packet flow associated with the first network slice;

a network slice identifier of the network slice for the handover; and

a cause information element indicating that a cause for the handover is that the session resources are not available at the first base station for the network slice associated with the network slice identifier; and

receiving, from the second base station, a response to the request.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 8, 2025
From: OFINNO, LLC
To: PENINSULA TECHNOLOGIES, LLC
Reel/Frame 069849/0289 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 22, 2021
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; JEON, HYOUNGSUK
To: OFINNO, LLC
Reel/Frame 058461/0518 →
Continuity (3)
Continuation 15972037 · May 4, 2018
Provisional Application 62501438 · May 4, 2017
Related Publication 20210410019A1 · Dec 30, 2021
References Cited (70)
US 11140544B2 · Yang · 2021 [cited by examiner]
US 20150317434A1 · Kondo · 2015 [cited by examiner]
US 20150327127A1 · Centonza · 2015 [cited by examiner]
US 20150358883A1 · Axelsson et al. · 2015 [cited by applicant]
US 20160277965A1 · Durowoju · 2016 [cited by examiner]
US 20160353350A1 · Engstrom · 2016 [cited by examiner]
US 20170054595A1 · Zhang · 2017 [cited by examiner]
US 20170079059A1 · Li · 2017 [cited by examiner]
US 20170086118A1 · Vrzic · 2017 [cited by examiner]
US 20170164349A1 · Zhu · 2017 [cited by examiner]
US 20170366679A1 · Mohamed · 2017 [cited by examiner]
US 20180041994A1 · Zhang · 2018 [cited by examiner]
US 20180124660A1 · Zhang · 2018 [cited by examiner]
US 20180220344A1 · Shaheen · 2018 [cited by applicant]
US 20180316615A1 · Shaw · 2018 [cited by examiner]
US 20180376364A1 · Keller · 2018 [cited by examiner]
US 20180376384A1 · Youn · 2018 [cited by examiner]
US 20190058997A1 · Futaki et al. · 2019 [cited by applicant]
US 20190098545A1 · Zhang · 2019 [cited by examiner]
US 20190158360A1 · Xu et al. · 2019 [cited by applicant]
US 20190261187A1 · Chen et al. · 2019 [cited by applicant]
US 20190261234A1 · Park et al. · 2019 [cited by applicant]
US 20190327153A1 · Wahlqvist · 2019 [cited by examiner]
US 20200059989A1 · Velev · 2020 [cited by examiner]
US 20200100173A1 · Casati · 2020 [cited by examiner]
US 20200305054A1 · Zee · 2020 [cited by examiner]
R3-171097; 3GPP TSG-RAN WG3 #95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Source: Qualcomm Incorporated; Title: TP for network slicing description. [cited by applicant]
R3-171251; 3GPP TSG-RAN WG3 95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: Huawei; Title: Further Discussion on Slice Re-mapping. [cited by applicant]
R3-171252; 3GPP TSG-RAN WG3 95bis; Spokane, Washington, USA, Apr. 3-7, 2017, Agenda item: 10.3; Source: Huawei; Title: Dual Connectivity for Slicing. [cited by applicant]
3GPP TS 36.300 V14.2.0 (Mar. 2017); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Acc… [cited by applicant]
3GPP TS 36.331 V14.2.2 (Apr. 2017); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol spe… [cited by applicant]
R2-1702529; 3GPP TSG-RAN WG2 #97bis; Spokane, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: Xiaomi; Title: Visibility of Slicing to UE; Document for: Discussion and Decision. [cited by applicant]
R2-1702539; 3GPP TSG-RAN2 #97bis; Spokane, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: OPPO; Title: Discussion on Mobility Issues of Network Slicing; Document for: Discussion and Decision. [cited by applicant]
R2-1702551; 3GPP TSG-RAN WG2 #97bis; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: Ericsson; Title: Signalling aspects of network slicing; Document for: Discussion & Approval. [cited by applicant]
R2-1702552; 3GPP TSG-RAN WG2 #97bis; Spokane, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: Ericsson; Title: Slice availability ; Document for: Discussion, Decision. [cited by applicant]
R2-1702553; 3GPP TSG-RAN WG2 #97bis; Spokane, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: Ericsson; Title: Access Control and Resource Isolation for Slicing; Document for: Discussion, Decision. [cited by applicant]
R2-1702554; 3GPP TSG-RAN WG2 #97bis; Spokane, WA, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: Ericsson; Title: Is UE AS slice agnostic or not?; Document for: Discussion. [cited by applicant]
R2-1702588; 3GPP TSG-RAN WG2#97bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.2.4.2; Source: Huawei, HiSilicon; Title: UE Awareness of Network Slice; Document for: Discussion and Decision. [cited by applicant]
R2-1702589; 3GPP TSG-RAN WG2 #97bis; Spokane, USA, Apr. 3-7, 2017; Source: Huawei, HiSilicon; Title: RRC Support for Network Slicing; Agenda Item: 10.2.4.2; Document for: Discussion and Decision. [cited by applicant]
R2-1702590; 3GPP TSG-RAN WG2 97bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda item: 10.2.4.2; Source: Huawei, HiSilicon; Title: Network Slice Selection Assistance Information over RRC; Document for: Discussion an… [cited by applicant]
R2-1702843; 3GPP TSG-RAN WG2 Meeting #97bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.2.4.2; Source: ZTE, ZTE Microelectronics; Title: Consideration on the NW slice in RAN; Document for: Discussion and Decision. [cited by applicant]
R2-1702969; 3GPP TSG RAN WG2 #97bis; Spokane, USA, Apr. 3-7, 2017; Agenda Item: 10.2.4.2; Source: Coolpad Title: Discussion on UE RRC modeling to support multiple slices per-UE; Document for: Discussion. [cited by applicant]
R2-1703101; 3GPP TSG-RAN WG2 Meeting #97bis; Spokane, USA, Apr. 3-7, 2017; Source: CATT; Title: Slice visibility to UE AS; Agenda item: 10.2.4.2; Document for: Discussion & Decision. [cited by applicant]
R2-1703337; 3GPP TSG-RAN WG2 Meeting 97bis; Spokane, Washington USA, Apr. 3-7, 2017; Agenda item: 10.2.4.2; Source: Samsung; Title: Review on Network Slicing; Document for: Discussion & Decision. [cited by applicant]
R2-1703343; 3GPP TSG-RAN WG2 Meeting 97bis; Spokane, Washington USA, Apr. 3-7, 2017; Agenda item: 10.2.4.2; Source: Samsung; Title: Slice Information in RRC. [cited by applicant]
R2-1703762; 3GPP TSG RAN WG2#97bis; Spokane, USA, Apr. 3-7, 2017; 3GPP TSG-SA WG3 Meeting #86Bis; Tdoc S3-170902; Busan, Korea, Mar. 27-31, 2017; Title: Reply LS on privacy of registration and slice selection informatio… [cited by applicant]
R3-170675; 3GPP TSG-RAN WG3 #95; Athens, Greece, Feb. 13-17, 2017; Agenda Item: 10.4; Source: Ericsson; Title: Clarifications on the use of NSSAI in Network Slicing. [cited by applicant]
R3-170677; 3GPP TSG-RAN WG3 #95; Athens, Greece, Feb. 13-17, 2017; Agenda Item: 10.4; Source: Ericsson; Title: Mobility and Mapping of NW slices. [cited by applicant]
R3-171012; 3GPP TSG-RAN WG3 #95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: CATT; Title: Discussion on Slice-aware mobility. [cited by applicant]
R3-171029; 3GPP TSG RAN WG3 Meeting #95bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: ZTE; Title: NW Slice Availability Handling Approaches during Mobility. [cited by applicant]
R3-171047; 3GPP TSG-RAN WG3 #95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: Samsung; Title: RAN supporting Network Slicing. [cited by applicant]
R3-171115; 3GPP TSG-RAN WG3#95bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Use of slice ID and NSSAI. [cited by applicant]
R3-171116; 3GPP TSG-RAN WG3#95bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Connected mode mobility with slicing. [cited by applicant]
R3-171117; 3GPP TSG RAN WG3 Meeting #95bis; Spokane, USA; Apr. 3-7, 2017; Title: [Draft] LS on slice re-mapping during connected mode mobility. [cited by applicant]
R3-171128; 3GPP TSG-RAN WG3 Meeting #95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: LG Electronics Inc.; Title: Discussion on slice availability during mobility. [cited by applicant]
R3-171129; 3GPP TSG-RAN WG3 Meeting #95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: LG Electronics Inc.; Title: Mobility procedure considering network slice. [cited by applicant]
R3-171139; 3GPP TSG-RAN WG3 #95bis; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: Ericsson; Title: RAN aspects of NW slicing in Stage 2 specifications. [cited by applicant]
R3-171140; 3GPP TSG-RAN WG3 #95bis; R3-171140; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: Ericsson; Title: Stage 2 aspects of CN Instance selection signaling. [cited by applicant]
R3-171141; 3GPP TSG-RAN WG3 #95bis; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: Ericsson; Title: Signalling aspects of network slicing. [cited by applicant]
R3-171142; 3GPP TSG-RAN WG3 #95bis; Spokane, WA, USA, Apr. 3-7, 2017; Title: [Draft] LS regarding RAN support for NW slicing. [cited by applicant]
R3-171143; 3GPP TSG-RAN WG3 #95bis; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: Ericsson; Title: Slice re-mapping or removal during mobility. [cited by applicant]
R3-171144; 3GPP TSG-RAN WG3 #95bis; Spokane WA, USA, Apr. 3-7, 2017; Title: [Draft] LS to SA2 on slices and mobility. [cited by applicant]
R3-171250; 3GPP TSG-RAN WG3 95bis; Spokane, Washington, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: Huawei; Title: Slice Awareness of Availability during Mobility. [cited by applicant]
R3-171351; 3GPP TSG-RAN WG3 Meeting # 95bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: LG Electronics Inc.; Title: TP for exchange of NSSAI in Xn Setup Procedure. [cited by applicant]
R3-171353; 3GPP TSG-RAN WG3 #95bis; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: Ericsson; Title: RAN aspects of NW slicing in Stage 2 specifications. [cited by applicant]
R3-171394; 3GPP TSG-RAN WG3 #95bis; Spokane, WA, USA, Apr. 3-7, 2017; Title: LS regarding RAN support for NW slicing. [cited by applicant]
R3-171395; 3GPP TSG-RAN WG3 #95bis; Spokane WA, USA, Apr. 3-7, 2017; Agenda Item: 10.3; Source: Ericsson; Title: Stage 2 aspects of CN Instance selection signaling. [cited by applicant]
R3-171396; 3GPP TSG RAN WG3 Meeting #95bis; Spokane, USA; Apr. 3-7, 2017; Title: LS on slice re-mapping during connected mode mobility. [cited by applicant]
3GPP TR 38.801 v14.0.0 (Year: 2017); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio access architecture and interfaces (Release 14). [cited by applicant]
R3-171116; 3GPP TSG-RAN WG3#95bis; Spokane, USA, Apr. 3-7, 2017; Agenda item: 10.3; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title:Connected mode mobility with slicing; Document for: Approval. [cited by applicant]