IP Library › Granted Patent US 12,414,025
Granted Patent B2
US 12,414,025 · App. 18/538,544 · Granted Sep 9, 2025

Handover procedure using resource status information

Inventors: Kyungmin Park (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Alireza Babaei (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA)
Assignee: Comcast Cable Communications, LLC
H04W36/38H04W36/00698H04W36/0083H04W36/00837H04W36/13H04W36/22H04W16/02H04W36/087H04W88/085H04W92/12
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,414,025
App. No.
18/538,544
Granted
Sep 9, 2025
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A base station may receive resource status information. The base station may use the resource status information for initiating a handover procedure.

Claims (143)

1. A method comprising:

receiving, from a first base station by a second base station, a resource status request message associated with the second base station;

sending, by the second base station to the first base station based on the resource status request message, a resource status message indicating available capacity associated with a network slice; and

receiving a handover request message indicating the network slice.

2. The method of claim 1 , wherein the receiving the handover request message comprises receiving the handover request message based on the available capacity associated with the network slice.

3. The method of claim 1 , wherein the resource status request message comprises at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

reporting periodicity information that indicates a time duration for the second base station to wait before sending the resource status message.

4. The method of claim 1 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of a wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

5. The method of claim 1 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

6. The method of claim 1 , further comprising sending, by the second base station to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

7. The method of claim 1 , further comprising:

after a handover, communicating, by the second base station, with a wireless device via the network slice.

8. A method comprising:

sending, to a first base station by a second base station, a resource status message indicating available capacity associated with a network slice;

receiving a handover request message indicating the network slice; and

after a handover, communicating, by the second base station, with a wireless device via the network slice.

9. The method of claim 8 , wherein the receiving the handover request message comprises receiving the handover request message based on the available capacity associated with the network slice.

10. The method of claim 8 , further comprising:

receiving, by the second base station from the first base station, a resource status request message associated with the second base station,

wherein the sending the resource status message comprises sending the resource status message based on the resource status request message.

11. The method of claim 8 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of the wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

12. The method of claim 8 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

13. The method of claim 8 , further comprising sending, by the second base station to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

14. A second base station comprising:

one or more processors; and

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

receive, from a first base station, a resource status request message associated with the second base station;

send, to the first base station based on the resource status request message, a resource status message indicating available capacity associated with a network slice; and

receive a handover request message indicating the network slice.

15. The second base station of claim 14 , wherein the instructions, when executed by the one or more processors, configure the second base station to receive the handover request message by receiving the handover request message based on the available capacity associated with the network slice.

16. The second base station of claim 14 , wherein the resource status request message comprises at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

reporting periodicity information that indicates a time duration for the second base station to wait before sending the resource status message.

17. The second base station of claim 14 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of a wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

18. The second base station of claim 14 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

19. The second base station of claim 14 , wherein the instructions, when executed by the one or more processors, further configure the second base station to send, to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

20. The second base station of claim 14 , wherein the instructions, when executed by the one or more processors, further configure the second base station to:

after a handover, communicate with a wireless device via the network slice.

21. A second base station comprising:

one or more processors; and

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

send, to a first base station, a resource status message indicating available capacity associated with a network slice;

receive a handover request message indicating the network slice; and

after a handover, communicate with a wireless device via the network slice.

22. The second base station of claim 21 , wherein the instructions, when executed by the one or more processors, configure the second base station to receive the handover request message by receiving the handover request message based on the available capacity associated with the network slice.

23. The second base station of claim 21 , wherein the instructions, when executed by the one or more processors, further configure the second base station to:

receive, from the first base station, a resource status request message associated with the second base station,

wherein the instructions, when executed by the one or more processors, configure the second base station to send the resource status message by sending the resource status message based on the resource status request message.

24. The second base station of claim 21 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of the wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

25. The second base station of claim 21 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

26. The second base station of claim 21 , wherein the instructions, when executed by the one or more processors, further configure the second base station to send, to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

27. A non-transitory computer-readable medium storing instructions that, when executed, cause:

receiving, from a first base station by a second base station, a resource status request message associated with the second base station;

sending, by the second base station to the first base station based on the resource status request message, a resource status message indicating available capacity associated with a network slice; and

receiving a handover request message indicating the network slice.

28. The non-transitory computer-readable medium of claim 27 , wherein the resource status request message comprises at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

reporting periodicity information that indicates a time duration for the second base station to wait before sending the resource status message.

29. The non-transitory computer-readable medium of claim 27 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of a wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

30. The non-transitory computer-readable medium of claim 27 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

31. The non-transitory computer-readable medium of claim 27 , wherein the instructions, when executed, further cause sending, to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

32. The non-transitory computer-readable medium of claim 27 , wherein the instructions, when executed, further cause:

after a handover, communicating, by the second base station, with a wireless device via the network slice.

33. A non-transitory computer-readable medium storing instructions that, when executed, cause:

sending, to a first base station by a second base station, a resource status message indicating available capacity associated with a network slice;

receiving a handover request message indicating the network slice; and

after a handover, communicating, by the second base station, with a wireless device via the network slice.

34. The non-transitory computer-readable medium of claim 33 , wherein the instructions, when executed, further cause:

receiving, from the first base station, a resource status request message associated with the second base station,

wherein the instructions, when executed, cause the sending the resource status message by sending the resource status message based on the resource status request message.

35. The non-transitory computer-readable medium of claim 33 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of the wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

36. The non-transitory computer-readable medium of claim 33 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

37. The non-transitory computer-readable medium of claim 33 , wherein the instructions, when executed, further cause sending, to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

38. A system comprising:

a first base station; and

a second base station,

wherein the first base station is configured to:

send, to the second base station, a resource status request message associated with the second base station; and

send, to the second base station, a handover request message indicating a network slice, and

wherein the second base station is configured to:

send, to the first base station based on the resource status request message, a resource status message indicating available capacity associated with the network slice.

39. The system of claim 38 , wherein the resource status request message comprises at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

reporting periodicity information that indicates a time duration for the second base station to wait before sending the resource status message.

40. The system of claim 38 , wherein the handover request message comprises at least one of:

a cell identifier of a cell of the second base station;

a wireless device identifier of a wireless device;

a network slice identifier of the network slice; or

one or more packet flow identifiers of one or more packet flows associated with the network slice.

41. The system of claim 38 , wherein the resource status message further indicates at least one of:

a cell identifier of a cell of the second base station;

a network slice identifier of the network slice, wherein the network slice is associated with the cell; or

a resource status information element.

42. The system of claim 38 , wherein the second base station is further configured to send, to the first base station, a resource status response message indicating that a resource status measurement has been initiated.

43. The system of claim 38 , wherein the second base station is further configured to:

after a handover, communicate with a wireless device via the network slice.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; JEON, HYOUNGSUK
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 068749/0050 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; JEON, HYOUNGSUK
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068749/0069 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2024
From: OFINNO TECHNOLOGIES, LLC
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068749/0073 →
Continuity (5)
Continuation 17410807 · Aug 24, 2021
Continuation 16752005 · Jan 24, 2020
Continuation 15971815 · May 4, 2018
Provisional Application 62501478 · May 4, 2017
Related Publication 20240114413A1 · Apr 4, 2024
References Cited (159)
US 20020131372A1 · Rinchiuso · 2002 [cited by applicant]
US 20030139186A1 · Igarashi et al. · 2003 [cited by applicant]
US 20110202635A1 · Yeung et al. · 2011 [cited by applicant]
US 20140086177A1 · Adjakple et al. · 2014 [cited by applicant]
US 20160352645A1 · Senarath et al. · 2016 [cited by applicant]
US 20160353268A1 · Senarath et al. · 2016 [cited by applicant]
US 20160353367A1 · Vrzic et al. · 2016 [cited by applicant]
US 20160353465A1 · Vrzic et al. · 2016 [cited by applicant]
US 20170054595A1 · Zhang et al. · 2017 [cited by applicant]
US 20170086118A1 · Vrzic · 2017 [cited by applicant]
US 20170164349A1 · Zhu et al. · 2017 [cited by applicant]
US 20170289270A1 · Li et al. · 2017 [cited by applicant]
US 20170311304A1 · Lu · 2017 [cited by applicant]
US 20170317894A1 · Dao et al. · 2017 [cited by applicant]
US 20170324652A1 · Lee et al. · 2017 [cited by applicant]
US 20170332421A1 · Sternberg et al. · 2017 [cited by applicant]
US 20170359749A1 · Dao · 2017 [cited by applicant]
US 20180006954A1 · Arora et al. · 2018 [cited by applicant]
US 20180124661A1 · Tsai · 2018 [cited by applicant]
US 20180139107A1 · Senarath et al. · 2018 [cited by applicant]
US 20180184415A1 · Rong et al. · 2018 [cited by applicant]
US 20180199398A1 · Dao et al. · 2018 [cited by applicant]
US 20180227873A1 · Vrzic et al. · 2018 [cited by applicant]
US 20180262924A1 · Dao et al. · 2018 [cited by applicant]
US 20180270712A1 · Faccin et al. · 2018 [cited by applicant]
US 20180270744A1 · Griot et al. · 2018 [cited by applicant]
US 20180324646A1 · Lee et al. · 2018 [cited by applicant]
US 20180332523A1 · Faccin et al. · 2018 [cited by applicant]
US 20190045351A1 · Zee et al. · 2019 [cited by applicant]
US 20190052580A1 · Peng et al. · 2019 [cited by applicant]
US 20190075552A1 · Yu et al. · 2019 [cited by applicant]
US 20190158364A1 · Zhang et al. · 2019 [cited by applicant]
US 20190159107A1 · Kim et al. · 2019 [cited by applicant]
US 20190174561A1 · Sivavakeesar · 2019 [cited by applicant]
US 20190191348A1 · Futaki et al. · 2019 [cited by applicant]
US 20190208573A1 · Yang et al. · 2019 [cited by applicant]
US 20190223093A1 · Watfa et al. · 2019 [cited by applicant]
US 20190238425A1 · Mladin et al. · 2019 [cited by applicant]
CN 107846275A · 2018 [cited by applicant]
WO 2015184708A1 · 2015 [cited by applicant]
WO 2016201999A1 · 2016 [cited by applicant]
WO 2017074486A1 · 2017 [cited by applicant]
WO 2017113109A1 · 2017 [cited by applicant]
WO 2017171598A1 · 2017 [cited by applicant]
WO 2017173259A1 · 2017 [cited by applicant]
WO 2018017132A1 · 2018 [cited by applicant]
WO 2018058579A1 · 2018 [cited by applicant]
WO 2018093168A1 · 2018 [cited by applicant]
WO 2018121880A1 · 2018 [cited by applicant]
WO 2019011794A1 · 2019 [cited by applicant]
S2-174202, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Ericsson; Title: NSSF and Slice selection during the Registration procedures (revision of S2-17xxxx). [cited by applicant]
S2-174246, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: ZTE, Telecom Italia, Oracle; Title: 23.501—Clarifications on Allowed NSSAI/S-NSSAI. [cited by applicant]
S2-174247, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: ZTE, Oracle, China Telecom; Title: 23.501—NSIs compatibility support via organization of NSSAI. [cited by applicant]
S2-174253, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Telecom Italia, Nokia, Alcatel-Lucent Shanghai Bell, ZTE; Title: Network Slicing Support for Roaming. [cited by applicant]
S2-174262, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Motorola Mobility, Lenovo; Title: Application Function influence on slice selection (revision of S2-17xxxx). [cited by applicant]
S2-174263, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Motorola Mobility, Lenovo; Title: Application Function influence on slice selection (revision of S2-17xxxx). [cited by applicant]
S2-174339, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: Allowed NSSAI. [cited by applicant]
S2-174340, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: TS 23.501—Routing NSSAI to perform AMF selection by (R)AN (revision of S2-17xxxx). [cited by applicant]
S2-174433, 3GPP TSG SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: TS 23.501—Use Application Data Repository for AF to provide policy requirements that apply to future PDU ses… [cited by applicant]
S2-174481, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: PCF Discovery and Selection. [cited by applicant]
S2-174485, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Qualcomm Incorporated; Title: TS 23.501—Network Triggered change of slices for UE. [cited by applicant]
S2-174486, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Qualcomm Incorporated; Title: TS 23.502—Network Triggered change of slices for UE. [cited by applicant]
S2-174538; San Jose, Mexico, Jun. 26-30, 2017; Source: Nokia, Alcatel-Lucent Shanghai Bell, Sprint, T-Mobile USA, NEC; Title: Network Slice Instance selection. [cited by applicant]
S2-174653, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: NTT Docomo; Title: TS 23.502—Clarification of NSSAI stored in the UE's subscription data. [cited by applicant]
S2-174709, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: ITRI; Title: Removal of FFS in Section 5.15.1 of TS 23.501 (revision of S2-17xxxx). [cited by applicant]
S2-174842, 3GPP TSG SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: TS 23.501—Use Application Data Repository for AF to provide policy requirements that apply to future PDU ses… [cited by applicant]
S2-174902, 3GPP TSG SA Wg2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: TS 23.501—Use Application Data Repository for AF to provide policy requirements that apply to future PDU ses… [cited by applicant]
S2-175051, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Motorola Mobility, Lenovo, Samsung, SK Telecom; Title: Allowed NSSAI mapping information. [cited by applicant]
S2-175216, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Ericsson; Title: NSSF and Slice selection during the Registration procedures (revision of S2-174992). [cited by applicant]
S2-175217, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon; Title: On Multiple Network Slice instances. [cited by applicant]
S2-175218, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Motorola Mobility, Lenovo; Title: PDU Session maintenance during change of the set of Network Slice(s) (revision of S2-174996, S2-174713). [cited by applicant]
S2-175219, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Motorola Mobility, Lenovo, Samsung, SK Telecom, Telecom Italia; Title: Allowed NSSAI mapping information (revision of S2-175051, S2-174579). [cited by applicant]
S2-175271, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Ericsson; Title: Slice co-existence (merge of S2-174201+4535+4649+4442). [cited by applicant]
S2-175296, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Huawei, HiSilicon, ZTE, China Mobile, Telecom Italia, Oracle, Ericsson, ITRI, China Telecom, InterDigital, KDDI, ETRI, CATT, China Unicom, Deut… [cited by applicant]
S2-175336, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Packet #92 Doc 109; LS reply to SA2 on Next Generation Roaming (revision of S2-174728). [cited by applicant]
Apr. 2, 2019—Extended European Search Report—EP 18211009.8. [cited by applicant]
Huawei et al.—Oct. 17, 2017—“TS 23.501: Support of isolated slice usage in the UE”. [cited by applicant]
Huawei et al.—Nov. 21, 2017—“Ol#4f: Support of isolated slice usage in the UE”. [cited by applicant]
Nov. 13, 2017—3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System Stage 2 (Release 15). [cited by applicant]
S2-175766, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Qualcomm Incorporated; Title: TS 23.501: Network Triggered change of slices for UE. [cited by applicant]
3GPP TS 23.501 V1.5.0 (Nov. 2017), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15). [cited by applicant]
3GPP TS 23.502 V1.3.0 (Nov. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15). [cited by applicant]
S2-175581, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Samsung; Title: Pushing Slice Coexistence Information to the UE. [cited by applicant]
S2-175601, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Telecom Italia, KDDI, ZTE; Title: 23.501: Network Slice Isolation. [cited by applicant]
S2-175630, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Telecom Italia, ZTE; Title: Network Slice Coexistence. [cited by applicant]
S2-175675, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Ericsson; Title: Network Slice Co-Existence Considerations. [cited by applicant]
S2-175678, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: On Coexistence Rules. [cited by applicant]
S2-175757, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Qualcomm Incorporated; Title: TS 23.501: Support for Slice Co-Existence. [cited by applicant]
S2-175911, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: Huawei, HiSilicon; Title: Simple Slice Coexistence. [cited by applicant]
S2-175915, SA WG2 Meeting #122bis; Sophia Antipolis, France, Aug. 21-25, 2017; Source: ZTE, Oracle; Title: 23.501: Network Slicing Clause 5.15.5—Early vs. Late Binding of UE with the Associated NSI Corresponding to Allo… [cited by applicant]
S2-177081, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Telecom Italia; Title: Ol#4a: Network Slice Isolation (23.501). [cited by applicant]
S2-177297, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Huawei, HiSilicon; Title: TS 23.501: Support of Isolated Slice Usage in the UE. [cited by applicant]
S2-177414, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Ntt Docomo; Title: TS 23.501: OI#18: Update of SMF and UPF Selection Principle. [cited by applicant]
S2-177543, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Nokia, Nokia Shanghai Bell; Title: 23.501 §6.3.3: NRF for UPF. [cited by applicant]
S2-177565, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Huawei, HiSilicon; Title: Ol#18 TS 23.501: Interaction between SMF and UPF on N4 Reference Point. [cited by applicant]
S2-177566, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Huawei, HiSilicon; Title: TS 23.501: UPF Selection based on SMF Local Information. [cited by applicant]
S2-178097, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Huawei, HiSilicon, Samsung, SK Telecom; Title: Ol#18 TS 23.501: Interaction between SMF and UPF on N4 Reference Point. [cited by applicant]
S2-178112, SA WG2 Meeting #123; Ljubljana, Slovenia, Oct. 23-27, 2017; Source: Nokia, Nokia Shanghai Bell, Cisco; Title: 23.501 §6.3.3: NRF for UPF. [cited by applicant]
S2-178256, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Nokia, Nokia Shanghai Bell, Verizon, Cisco, Deutsche Telecom; Title: Ol#19: 23.501 §6.3.3: NRF for UPF discovery. [cited by applicant]
S2-178468, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Huawei, HiSilicon; Title: TS23.502 Clarification on UPF selection in PDU session establishment. [cited by applicant]
S2-178509, Sa WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Nokia, Nokia Shanghai Bell, Verizon, Cisco, Deutsche Telecom; Title: Ol#19: 23.502 §4.17.x: NRF for UPF discovery. [cited by applicant]
S2-178541, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Nokia, Nokia Shanghai Bell, Telecom Italia; Title: TS 23.501 Ol:4f Coexistence and isolation among network slices. [cited by applicant]
S2-179779, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Nokia, Nokia Shanghai Bell; Title: 23.501/§ 6.3.3: location data SMF needs for UPF selection. [cited by applicant]
S2-178922, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Huawei, HiSilicon; Title: Ol#19 TS 23.501 Proposal on Using UPF Topology for UPF Selection by SMF. [cited by applicant]
S2-179121 rev1, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Samsung, Deutsche Telekom; Title: TS 23.502: Clarification on NF Service Discovery. [cited by applicant]
S2-179325 rev4, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Nokia, Nokia Shanghai Bell, Verizon, Cisco, Deutsche Telecom; Title: Ol#19: 23.502 §4.17.x: NRF for UPF discovery. [cited by applicant]
S2-179325 rev5, SA WG2 Meeting #124; Reno, USA, Nov. 27-Dec. 1, 2017; Source: Nokia, Nokia Shanghai Bell, Verizon, Cisco, Deutsche Telecom; Title: Ol#19: 23.502 §4.17.x: NRF for UPF discovery. [cited by applicant]
SP-170743, SA WG2 Meeting #1223GPP; Sapporo, Japan, Sep. 13-15, 2017; Source: SA WG2; Title: New SID on Enhancing Topology of SMF and UPF in 5G Networks. [cited by applicant]
Qualcomm Incorporated—Aug. 15, 2017—“TS 23. 501: Network Triggered change of slices for UE”. [cited by applicant]
Qian (Clara) Li et al., “An end-to-end network slicing framework for 5G wireless communication systems”, Aug. 2016, Intel Corporation, USA. [cited by applicant]
3GPP TS 23.501 V0.4.0 (Apr. 2017), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15). [cited by applicant]
R2-1702529 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Xiaomi, Title: Visibility of Slicing to UE. [cited by applicant]
R2-1702539 3GPP TSG-RAN2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: OPPO, Title: Discussion on Mobility Issues of Network Slicing. [cited by applicant]
R2-1702551 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Signalling aspects of network slicing. [cited by applicant]
R2-1702552 Tdoc 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Slice availability. [cited by applicant]
R2-1702553 Tdoc 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Access Control and Resource Isolation for Slicing. [cited by applicant]
R2-1702554 Tdoc 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Is UE As slice agnostic or not? [cited by applicant]
R2-1702588 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: UE Awareness of Network Slice. [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. [cited by applicant]
R2-1702590 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: Network Slice Selection Assistance Information over RRC. [cited by applicant]
R2-1702843 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: ZTE, ZTE Microelectronics, Title: Consideration on the NW slice in RAN. [cited by applicant]
R2-1702969 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Coolpad, Title: Discussion on UE RRC modeling to support multiple slices per-UE. [cited by applicant]
R2-1703101 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: CATT, Title: Slice visibility to UE As. [cited by applicant]
R2-1703337 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Samsung, Title: Review on Network Slicing. [cited by applicant]
R2-1703343 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: Samsung, Title: Slice Information in RRC. [cited by applicant]
R2-1703762 3GPP TSG-RAN WG2 #97bis, Spokane, USA, Apr. 3-7, 2017, Source: SA3, Title: Reply LS on privacy of registration and slice selection information (revision of Tdoc S3170902 in Busan, Korea from Mar. 27-31, 2017). [cited by applicant]
R3-170675 3GPP TSG-RAN WG3 #95, Athens, Greece, Feb. 13-17, 2017, 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, Source: Ericsson, Title: Mobility and Mapping of NW Slices. [cited by applicant]
R3-171012 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: CATT, Title: Discussion on Slice-aware mobility. [cited by applicant]
R3-171029 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: ZTE, Title: NW Slice Availability Handling Approaches during Mobility. [cited by applicant]
R3-171047 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Samsung, Title: RAN supporting Network Slicing. [cited by applicant]
R3-171097 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Qualcomm Incorporated, Title: TP for network slicing description. [cited by applicant]
R3-171115 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, 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, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Connected mode mobility with slicing. [cited by applicant]
R3-171117 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Nokia, Title: LS on slice re-mapping during connected mode mobility. [cited by applicant]
R3-171128 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: LG Electronics Inc., Title: Discussion on slice availability during mobility. [cited by applicant]
R3-171129 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: LG Electronics Inc., Title: Mobility procedure considering network slice. [cited by applicant]
R3-171139 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: RAN aspects of NW slicing in Stage 2 specifications. [cited by applicant]
R3-171140 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Stage 2 aspects of CN Instance selection signalling. [cited by applicant]
R3-171141 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Signalling aspects of networking slicing. [cited by applicant]
R3-171142 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: LS regarding RAN support for NW slicing. [cited by applicant]
R3-171143 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Slice re-mapping or removal during mobility. [cited by applicant]
R3-171144 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: LS to SA2 on slices and mobility. [cited by applicant]
R3-171250 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, Title: Slice Awareness of Availability during Mobility. [cited by applicant]
R3-171251 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, Title: Further Discussion on Slice Re-mapping. [cited by applicant]
R3-171252 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, Title: Dual Connectivity for Slicing. [cited by applicant]
R3-171351 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, 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, USA, Apr. 3-7, 2017, Source: Ericsson, Title: RAN aspects of NW slicing in Stage 2 specifications. [cited by applicant]
R3-171394 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: RAN3, Title: LS regarding RAN support for NW slicing. [cited by applicant]
R3-171395 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Stage 2 aspects of CN Instance selection signalling. [cited by applicant]
R3-171396 3GPP TSG-RAN WG3 #95bis, Spokane, USA, Apr. 3-7, 2017, Source: Ran WG3, Title: LS on slice re-mapping during connected mode mobility. [cited by applicant]
3GPP TS 36.423 V14.2.0 (Mar. 2017); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-Utran); X2 application protocol (X2AP) (R… [cited by applicant]
3GPP TS 22.261 V15.1.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service Requirements for the 5G System; Stage 1 (Release 15). [cited by applicant]
3GPP TS 23.501 V1.2.0 (Jul. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15). [cited by applicant]
3GPP TS 23.502 V0.5.0 (Jul. 2017-07); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15). [cited by applicant]
3GPP TR 23.799 V14.0.0 (Dec. 2016); Technical Report; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for the Next Generation System (Release 14). [cited by applicant]
R2-11Xxxx, 3GPP TSG-RAN WG2 #73, Taipei, Taiwan, Feb. 21-25, 2011, Source: InterDigital Communications, Title: Report of Email discussion #26 on Scell Activation in LTE CA. [cited by applicant]
5G White Paper by Next Generation Mobile Networks (NGMN) Alliance, Version 1.0, Feb. 17, 2015. [cited by applicant]
S2-174201, SA WG2 Meeting #122; San Jose, Mexico, Jun. 26-30, 2017; Source: Ericsson; Title: Slice co-existence. [cited by applicant]