IP Library › Granted Patent US 12,550,206
Granted Patent B2
US 12,550,206 · App. 17/370,932 · Granted Feb 10, 2026

User plane function selection for isolated network slice

Inventors: Peyman Talebi Fard (Sterling, VA); Esmael Dinan (McLean, VA); Kyungmin Park (Vienna, VA); Weihua Qiao (Herndon, VA)
Assignee: Comcast Cable Communications, LLC
H04W76/11H04W8/18H04W24/02H04W48/00H04W72/04
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,206
App. No.
17/370,932
Granted
Feb 10, 2026
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A first message indicating a request to select a user plane function (UPF) device may comprise a network slice isolation information parameter and a network slice identifier associated with a wireless device. A second message comprising an identifier of a UPF device may be received.

Claims (90)

1 . A method comprising:

sending, by an access and mobility management function (AMF) to a session management function (SMF), a first message for establishing a session, the first message comprising:

an indication of a request for a user plane resource, for the session, for sending data associated with a wireless device; and

an indication of a network slice restriction to be used in selecting a user plane resource for the request; and

receiving, by the AMF and from the SMF, a second message comprising an indication of a user plane resource that satisfies the network slice restriction.

2 . The method of claim 1 , wherein:

the first message comprises a network slice identifier associated with the wireless device, and

the indicated user plane resource is associated with the network slice identifier.

3 . The method of claim 1 , wherein the indicated user plane resource comprises a user plane resource of a user plane function (UPF) device.

4 . The method of claim 1 , wherein the first message comprises a packet data unit (PDU) session establishment request.

5 . The method of claim 1 , further comprising receiving, from the wireless device, a request to establish a session for sending the data associated with the wireless device, wherein the request to establish the session comprises the indication of the network slice restriction.

6 . The method of claim 1 , further comprising receiving, from the wireless device, a non-access stratum (NAS) message comprising the indication of the network slice restriction.

7 . The method of claim 1 , wherein the network slice restriction comprises at least one of:

a network slice isolation type descriptor; or

a degree of network slice isolation.

8 . The method of claim 1 , wherein the user plane resource that satisfies the network slice restriction is selected by a network repository function (NRF) device based on the network slice restriction.

9 . The method of claim 1 , further comprising:

causing, via the indicated user plane resource, establishment of a communication session with the wireless device.

10 . The method of claim 1 , further comprising:

sending, based on the indicated user plane resource, a third message indicating a request to establish a session for sending the data.

11 . The method of claim 1 , wherein the network slice restriction indicates that a first network slice and a second network slice do not coexist.

12 . A method comprising:

receiving, by a session management function (SMF) from an access and mobility management function (AMF), a first message comprising a network slice restriction for selection of user plane resources of a plurality of network slices;

selecting, by the SMF and based on the network slice restriction, a user plane resource of one of the plurality of network slices; and

sending, by the SMF to the AMF, a second message comprising an indication of the selected user plane resource.

13 . The method of claim 12 , wherein the selected user plane resource comprises a user plane resource of a user plane function (UPF) device.

14 . The method of claim 12 , wherein:

the first message comprises a network slice identifier associated with a wireless device, and

the selected user plane resource is associated with the network slice identifier.

15 . The method of claim 12 , wherein the first message further comprises

a user plane function (UPF) selection rule.

16 . The method of claim 12 , further comprising sending, by the SMF to the AMF, a third message indicating a change in at least one of:

the network slice restriction, or

a user plane function (UPF) selection rule.

17 . The method of claim 12 , wherein the network slice restriction comprises at least one of:

a network slice isolation type descriptor; or

a degree of network slice isolation.

18 . The method of claim 12 , wherein the selecting comprises sending, by the SMF to a unified data management (UDM) device, the network slice restriction for selection of user plane resources of a plurality of network slices.

19 . The method of claim 12 , further comprising:

causing, via the selected user plane resource, establishment of a communication session with a wireless device.

20 . The method of claim 12 , wherein the selecting comprises:

selecting, by the SMF and based on a user plane resource selection rule, the selected user plane resource.

21 . An access and mobility management function (AMF) device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, configure the AMF device to:

send, to a session management function (SMF) device, a first message for establishing a session, the first message comprising:

an indication of a request for a user plane resource, for the session, for sending data associated with a wireless device; and

an indication of a network slice restriction to be used in selecting a user plane resource for the request; and

receive, from the SMF device, a second message comprising an indication of a user plane resource that satisfies the network slice restriction.

22 . The AMF device of claim 21 , wherein:

the first message comprises a network slice identifier associated with the wireless device, and

the indicated user plane resource is associated with the network slice identifier.

23 . The AMF device of claim 21 , wherein the indicated user plane resource comprises a user plane resource of a user plane function (UPF) device.

24 . The AMF device of claim 21 , wherein the first message comprises a packet data unit (PDU) session establishment request.

25 . The AMF device of claim 21 , wherein the instructions, when executed by the one or more processors, configure the AMF device to:

receive, from the wireless device, a request to establish a session for sending the data associated with the wireless device, wherein the request to establish the session comprises the network slice restriction.

26 . The AMF device of claim 21 , wherein the instructions, when executed by the one or more processors, configure the AMF device to:

receive a non-access stratum (NAS) message comprising the network slice restriction.

27 . The AMF device of claim 21 , wherein the network slice restriction comprises at least one of:

a network slice isolation type descriptor; or

a degree of network slice isolation.

28 . The AMF device of claim 21 , wherein the user plane resource that satisfies the network slice restriction is selected by a network repository function (NRF) device based on the network slice restriction.

29 . The AMF device of claim 21 , wherein the instructions, when executed by the one or more processors, configure the AMF device to:

cause, via the indicated user plane resource, establishment of a communication session with the wireless device.

30 . The AMF device of claim 21 , wherein the instructions, when executed by the one or more processors, configure the AMF device to:

send, based on the indicated user plane resource, a third message indicating a request to establish a session for sending the data.

31 . A session management function (SMF) device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, configure the SMF device to:

receive, from an access and mobility management function (AMF) device, a first message comprising a network slice restriction for selection of user plane resources of a plurality of network slices;

select, based on the network slice restriction, a user plane resource of one of the plurality of network slices; and

send to the AMF device, a second message comprising an indication of the selected user plane resource.

32 . The SMF device of claim 31 , wherein the selected user plane resource comprises a user plane resource of a user plane function (UPF) device.

33 . The SMF device of claim 31 , wherein:

the first message comprises a network slice identifier associated with a wireless device, and

the selected user plane resource is associated with the network slice identifier.

34 . The SMF device of claim 31 , wherein the first message further comprises

a user plane function (UPF) selection rule.

35 . The SMF device of claim 31 , wherein the instructions, when executed by the one or more processors, configure the SMF device to:

send, to the AMF device, a third message indicating a change in at least one of:

the network slice restriction, or

a user plane function (UPF) selection rule.

36 . The SMF device of claim 31 , wherein the network slice restriction comprises at least one of:

a network slice isolation type descriptor; or

a degree of network slice isolation.

37 . The SMF device of claim 31 , wherein the instructions, when executed by the one or more processors, configure the SMF device to send, to a unified data management (UDM) device, the network slice restriction for selection of user plane resources of a plurality of network slices.

38 . The SMF device of claim 31 , wherein the instructions, when executed by the one or more processors, configure the SMF device to:

cause, via the selected user plane resource, establishment of a communication session with a wireless device.

39 . The SMF device of claim 31 , wherein the instructions, when executed by the one or more processors, configure the SMF device to:

select the selected user plane resource based on a user plane resource selection rule.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2022
From: FARD, PEYMAN TALEBI; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; QIAO, WEIHUA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 061458/0868 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2022
From: FARD, PEYMAN TALEBI; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; QIAO, WEIHUA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 061458/0878 →
Continuity (4)
Continuation 16796582 · Feb 20, 2020
Continuation 16213092 · Dec 7, 2018
Provisional Application 62596237 · Dec 8, 2017
Related Publication 20220039177A1 · Feb 3, 2022
References Cited (214)
US 10129894B2 · Farmanbar et al. · 2018 [cited by examiner]
US 10161934B2 · Laury-Kleintop et al. · 2018 [cited by applicant]
US 10616934B2 · Talebi Fard et al. · 2020 [cited by examiner]
US 11102828B2 · Talebi Fard et al. · 2021 [cited by examiner]
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 examiner]
US 20170054595A1 · Zhang et al. · 2017 [cited by applicant]
US 20170086118A1 · Vrzic · 2017 [cited by examiner]
US 20170142591A1 · Vrzic · 2017 [cited by examiner]
US 20170164349A1 · Zhu et al. · 2017 [cited by applicant]
US 20170208634A1 · Bharatia et al. · 2017 [cited by examiner]
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 examiner]
US 20170353490A1 · Kraus et al. · 2017 [cited by examiner]
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 20180199279A1 · Baek · 2018 [cited by examiner]
US 20180199398A1 · Pao et al. · 2018 [cited by applicant]
US 20180227871A1 · Singh 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 20180317163A1 · Lee · 2018 [cited by examiner]
US 20180324646A1 · Lee et al. · 2018 [cited by applicant]
US 20180332441A1 · Shaw · 2018 [cited by examiner]
US 20180332523A1 · Faccin et al. · 2018 [cited by applicant]
US 20180368061A1 · Yu 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 20190098569A1 · Hou · 2019 [cited by examiner]
US 20190124572A1 · Park et al. · 2019 [cited by applicant]
US 20190150081A1 · Qiao et al. · 2019 [cited by examiner]
US 20190158364A1 · Zhang et al. · 2019 [cited by applicant]
US 20190159107A1 · Kim et al. · 2019 [cited by applicant]
US 20190159117A1 · Kuge · 2019 [cited by examiner]
US 20190174561A1 · Sivavakeesar · 2019 [cited by applicant]
US 20190182752A1 · Lou · 2019 [cited by examiner]
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 20190230004A1 · Zhou · 2019 [cited by examiner]
US 20190238425A1 · Mladin et al. · 2019 [cited by applicant]
US 20190254089A1 · Huang-Fu · 2019 [cited by examiner]
US 20190289528A1 · Lou · 2019 [cited by examiner]
US 20190312782A1 · Vaishnavi · 2019 [cited by examiner]
US 20190364496A1 · Jin · 2019 [cited by applicant]
US 20190394651A1 · Wifvesson · 2019 [cited by examiner]
US 20200015127A1 · Zhu et al. · 2020 [cited by applicant]
US 20200107173A1 · Breuer · 2020 [cited by examiner]
US 20200163134A1 · Ying et al. · 2020 [cited by applicant]
US 20200196130A1 · Tamura · 2020 [cited by examiner]
US 20200205176A1 · Yu · 2020 [cited by examiner]
US 20200305054A1 · Zee et al. · 2020 [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 WO2017173404A1 · 2017 [cited by examiner]
WO WO2017178921A1 · 2017 [cited by examiner]
WO 2018017132A1 · 2018 [cited by applicant]
WO 2018058579A1 · 2018 [cited by applicant]
WO WO2018059689A1 · 2018 [cited by examiner]
WO 2018093168A1 · 2018 [cited by applicant]
WO 2018121880A1 · 2018 [cited by applicant]
WO 2019011794A1 · 2019 [cited by applicant]
Method Of Establishing User Plane; CN 101137203 A (Year: 2008). [cited by examiner]
Method for Transmitting/Receiving Location Registration-Related Message in Wireless Communication System and Apparatus for Same; WO 2017142362 A1 (Year: 2017). [cited by examiner]
SDN-Based Methods and Apparatuses for Providing TDD Radio Access Network Services; WO 2017168112 A1 (Year: 2017). [cited by examiner]
Method for Managing Network Slice and Management Unit; WO 2018058579 A1 (Year: 2018). [cited by examiner]
Terminal Device, Base Station Device, MME (Mobile Management Entity) and Communication Control Method; WO 2017175715 A1 (Year: 2017). [cited by examiner]
Communication Method and Device; WO 2018176425 A1 (Year: 2018). [cited by examiner]
Qiao et al.: Communication Method, User Equipment, and Core Network Control Plane Apparatus; WO 2018148962 A1. (Year: 2018). [cited by examiner]
Lu et al.: Method And System For Performing Network Slicing In A Wireless Access Network; KR 20180090882 A. (Year: 2018). [cited by examiner]
Tu et al.: Method And Device For The Separation Of One Management Data For Network Slicing Sub-network Instance; CN 109429244 A. (Year: 2019). [cited by examiner]
Subin et al.: Network Operation Rule; WO 2015142372 A1. (Year: 2015). [cited by examiner]
WO 2018058579 A1, published to Zhou et al. discloses—Method for Managing Network Slice and Management Unit (see title' abstract). (Year: 2018). [cited by examiner]
(WO 2018059546 A1), published to Lou et al., discloses >>>> Communication Methods and Devices (see title). Also discloses >>> user plane, slice identifier and slice control (see description). (Year: 2018). [cited by examiner]
(CN 109429244 A), discloses >>> Method And Device For The Separation Of One Management Data For Network Slicing Sub-network Instance (see title). (Year: 2019). [cited by examiner]
Li et al. (WO 2017166148 A1) >>> Data Transmission Method and Related Device (see title and Description) (Year: 2017). [cited by examiner]
Hu et al. (WO 2018176425 A1) >>> Communication Method and Device (see title) (Year: 2018). [cited by examiner]
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 Systeml 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]
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: Huawi, 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]
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]
Oct. 15, 2020, European Office Action, EP 18211009.8. [cited by applicant]
3GPP TS 23.501 V1.6.0—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-178836 SA WG2 Meeting #124, Nov. 27-Dec. 1, 2017 Reno, U.S.; Huawei, HiSilicon, “Ol#4f: Support of isolated slice usage in the UE”. [cited by applicant]
S2-177297 SA WG2 Meeting #123, Oct. 23-27, 2017 Ljubljana, Slovenia; Huawei, HiSilicon, TS 23.501: “Support of isolated slice usage in the UE”. [cited by applicant]
S2-175766 SA WG2 Meeting #122bis, Aug. 21-25, 2017, Sophia Antipolis, France; Qualcomm Incorporated, “TS 23.501: Network Triggered charge of slices for UE”. [cited by applicant]
3GPP TS 23.501 V1.5.0; 3rd Generation Partnership Project; Technical Specification Group and System Aspects; System Architecture for teh 5G System; Stage 2 (Release 15). [cited by applicant]
Feb. 22, 2022—European Search Report—EP 21204548.8. [cited by applicant]
3GPP TS 23.502 V0.5.0 (Jul. 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]
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]
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]
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: Ol#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-174808, SA WG2 Meeting #122; San Jose Del Cabo, Mexico, Jun. 26-30, 2017; Source: Ericsson; Title: RRC Inactive state—new procedures in TS 23.502. [cited by applicant]
S2-173106, SA WG2 Meeting #121; Hangzhou, P.R. China, May 15-19, 2017; Source: Qualcomm Incorporated; TS 23.502: handling of PDU session at slice unavailability. [cited by applicant]
3GPP TS 23.502 V1.2.0 (Sep. 2017), 3rd Generaton Partnership Project; Technical Specification Group Services and Systems Aspects; Procedures for the 5G System; Stage 2 (Release 15). [cited by applicant]
Dec. 17, 2025—European Search Report—EP App. 25193458.4. [cited by applicant]