IP Library › Granted Patent US 12,432,568
Granted Patent B2
US 12,432,568 · App. 17/376,920 · Granted Sep 30, 2025

Radio access network node, radio terminal, core network node, and method therefor

Inventors: Hisashi Futaki (Tokyo, JP); Sadafuku Hayashi (Tokyo, JP)
Assignee: NEC CORPORATION
H04W16/02H04W36/0072H04W36/1443H04W36/26H04W76/27
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,432,568
App. No.
17/376,920
Granted
Sep 30, 2025
Kind
B2
Abstract

During handover of a radio terminal ( 1 ) from a first network to a second network, a target RAN node ( 3 ) is operates to: receive, from a core network ( 5 ), slice information about a network slice which is included in the second network and to which the radio terminal ( 1 ) is to be connected; create, upon receiving the slice information, radio resource configuration information that is to be used by the radio terminal ( 1 ) after the handover in the second network; and transmit this radio resource configuration information through the first network to the radio terminal ( 1 ). It is possible to contribute to appropriately configuring an AS layer or NAS layer of a target RAT in inter-RAT handover.

Claims (42)

1. A target radio access network (RAN) node associated with a second network, the target RAN node comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configured to, during handover of a radio terminal from a first network to the second network:

receive, from a core network, slice information about a network slice which is included in the second network and to which the radio terminal is to be connected, the network slice including network functions of the core network, the network slice being a logical network providing specific network capabilities, the slice information including identification information identifying the network slice, the slice information further including at least one of a mobility class and a session class that are supported by the network slice selected for the radio terminal;

create, based on the received slice information, radio resource configuration information to be used by the radio terminal after the handover in the second network; and

transmit the radio resource configuration information through the first network to the radio terminal.

2. The target RAN node according to claim 1 , wherein the at least one processor is configured to:

receive, from the core network, a handover request message requesting the handover of the radio terminal from the first network to the second network and including the slice information about the network slice, which is included in the second network and to which the radio terminal is to be connected; and

transmit to the core network, in response to the handover request message, a handover request acknowledge message containing a Target to Source Transparent Container,

wherein the Target to Source Transparent Container contains the radio resource configuration information derived from the slice information and is to be forwarded through the core network to a source RAN node associated with the first network.

3. The target RAN node according to claim 1 , wherein the identification information included in the slice information includes: type information of the network slice selected for the radio terminal.

4. The target RAN node according to claim 1 , wherein the at least one processor is configured to determine based on the slice information whether to accept a bearer or a flow for each beater or each flow of the radio terminal.

5. The target RAN node according to claim 1 , wherein the at least one processor is configured to determine, based on the slice information, whether it is possible to accept each network slice.

6. The target RAN node according to claim 1 , wherein the first network does not support network slicing, and the second network supports the network slicing.

7. A source radio access network (RAN) node associated with a first network, the source RAN node comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configured to, during handover of a radio terminal from the first network to a second network:

receive, from a core network, a handover-related message, the handover-related message containing at least one of slice information about a network slice which is included in the second network and to which the radio terminal is to be connected, and radio resource configuration information based on the network slice in the second network, the network slice including network functions of the core network, the network slice being a logical network providing specific network capabilities, the slice information including identification information identifying the network slice, the slice information further including at least one of a mobility class and a session class that are supported by the network slice selected for the radio terminal; and

transmit the handover-related message to the radio terminal.

8. The source RAN node according to claim 7 , wherein the at least one processor is configured to:

transmit, to the core network, a handover required message for starting the handover of the radio terminal from the first network to the second network;

receive a handover command message containing a Target to Source Transparent Container from the core network, the Target to Source Transparent Container containing radio resource configuration information created by a target RAN node associated with the second network, the radio resource configuration information being necessary for the radio terminal to establish a radio connection associated with the network slice, which is included in the second network and to which the radio terminal is to be connected; and

transmit, to the radio terminal, a mobility command message containing the radio resource configuration information and indicating the handover to the second network.

9. The source RAN node according to claim 7 , wherein the first network does not support network slicing, and the second network supports the network slicing.

10. A core network node comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configured to, during handover of a radio terminal from a first network to a second network, send, to a target radio access network (RAN) node associated with the second network, slice information about a network slice which is included in the second network and to which the radio terminal is to be connected, the network slice including network functions of the core network, the network slice being a logical network providing specific network capabilities, the slice information including identification information identifying the network slice, the slice information further including at least one of a mobility class and a session class that are supported by the network slice selected for the radio terminal,

wherein the slice information causes the target RAN node to create, based on the received slice information, radio resource configuration information to be used by the radio terminal after the handover in the second network.

11. The core network node according to claim 10 , wherein the at least one processor is configured to:

receive, from a source RAN node associated with the first network, a handover required message for starting the handover of the radio terminal from the first network to the second network; and

send to the target RAN node, in response to the handover required message, a handover request message including the slice information and requesting the handover of the radio terminal from the first network to the second network.

12. The core network node according to claim 11 , wherein the at least one processor is further configured to:

receive a handover request acknowledge message containing a Target to Source Transparent Container from the target RAN node, the Target to Source Transparent Container containing radio resource configuration information derived from the slice information; and

send a Handover Command message containing the Target to Source Transparent Container to the source RAN node.

13. The core network node according to claim 10 , wherein the identification information included in the slice information includes: type information of the network slice selected for the radio terminal.

14. The core network node according to claim 10 , wherein the first network does not support network slicing, and the second network supports the network slicing.

15. A method in a target radio access network (RAN) node associated with a second network, the method comprising:

during handover of a radio terminal from a first network to the second network,

receiving, from a core network, slice information about a network slice which is included in the second network and to which the radio terminal is to be connected, the network slice including network functions of the core network, the network slice being a logical network providing specific network capabilities, the slice information including identification information identifying the network slice, the slice information further including at least one of a mobility class and a session class that are supported by the network slice selected for the radio terminal;

creating, based on the received slice information, radio resource configuration information to be used by the radio terminal after the handover in the second network; and

transmitting the radio resource configuration information through the first network to the radio terminal.

16. The method according to claim 15 , wherein the first network does not support network slicing, and the second network supports the network slicing.

Priority Claims (1)
JP 2016-158280 · Aug 10, 2016 · national
Continuity (2)
Continuation 16080392
Related Publication 20210345119A1 · Nov 4, 2021
References Cited (195)
US 8553643B2 · Flore et al. · 2013 [cited by applicant]
US 10028128B2 · Salkintzis · 2018 [cited by applicant]
US 10644955B2 · Zhang et al. · 2020 [cited by applicant]
US 11356854B2 · Futaki · 2022 [cited by examiner]
US 20020191556A1 · Krishnarajah et al. · 2002 [cited by applicant]
US 20040057400A1 · Walsh et al. · 2004 [cited by applicant]
US 20070021120A1 · Flore et al. · 2007 [cited by applicant]
US 20070281697A1 · Davis · 2007 [cited by applicant]
US 20080049677A1 · Hayashi · 2008 [cited by applicant]
US 20080267128A1 · Bennett et al. · 2008 [cited by applicant]
US 20090016259A1 · Zhang et al. · 2009 [cited by applicant]
US 20120207129A1 · Sun · 2012 [cited by applicant]
US 20130010611A1 · Wiemann et al. · 2013 [cited by applicant]
US 20130017826A1 · Bergquist et al. · 2013 [cited by applicant]
US 20130128866A1 · Zhang et al. · 2013 [cited by applicant]
US 20140051443A1 · Diachina et al. · 2014 [cited by applicant]
US 20140301370A1 · Sivavakeesar · 2014 [cited by applicant]
US 20150139195A1 · Xiao et al. · 2015 [cited by applicant]
US 20150215822A1 · Won et al. · 2015 [cited by applicant]
US 20150229491A1 · Solovyev · 2015 [cited by applicant]
US 20150264609A1 · Zhang et al. · 2015 [cited by applicant]
US 20150282021A1 · Pao et al. · 2015 [cited by applicant]
US 20160057783A1 · Rosa et al. · 2016 [cited by applicant]
US 20160205578A1 · Lee et al. · 2016 [cited by applicant]
US 20160227459A1 · Fujishiro et al. · 2016 [cited by applicant]
US 20160353465A1 · Vrzic et al. · 2016 [cited by applicant]
US 20170034749A1 · Chandramouli et al. · 2017 [cited by applicant]
US 20170079059A1 · Li et al. · 2017 [cited by applicant]
US 20170086118A1 · Vrzic · 2017 [cited by applicant]
US 20170164349A1 · Zhu et al. · 2017 [cited by applicant]
US 20170195935A1 · Xu et al. · 2017 [cited by applicant]
US 20170288972A1 · Li et al. · 2017 [cited by applicant]
US 20170289019A1 · Faccin et al. · 2017 [cited by applicant]
US 20170289046A1 · Faccin et al. · 2017 [cited by applicant]
US 20170332295A1 · Sunay · 2017 [cited by applicant]
US 20170339609A1 · Youn · 2017 [cited by examiner]
US 20170359768A1 · Byun et al. · 2017 [cited by applicant]
US 20170367110A1 · Li et al. · 2017 [cited by applicant]
US 20180014224A1 · Cheng et al. · 2018 [cited by applicant]
US 20180020382A1 · Kim · 2018 [cited by examiner]
US 20180035339A1 · Mitsui et al. · 2018 [cited by applicant]
US 20180124660A1 · Zhang et al. · 2018 [cited by applicant]
US 20180242304A1 · Rong et al. · 2018 [cited by applicant]
US 20180288654A1 · Shih · 2018 [cited by examiner]
US 20180368140A1 · Centonza et al. · 2018 [cited by applicant]
US 20190021043A1 · Youn et al. · 2019 [cited by applicant]
US 20190029000A1 · Vikberg et al. · 2019 [cited by applicant]
US 20190098544A1 · Han et al. · 2019 [cited by applicant]
US 20190150219A1 · Wang et al. · 2019 [cited by applicant]
US 20190158360A1 · Xu · 2019 [cited by examiner]
US 20190159027A1 · Kuge et al. · 2019 [cited by applicant]
US 20190174368A1 · Decarreau et al. · 2019 [cited by applicant]
US 20190174377A1 · Decarreau et al. · 2019 [cited by applicant]
US 20190182733A1 · Shimojou et al. · 2019 [cited by applicant]
US 20190182737A1 · Futaki et al. · 2019 [cited by applicant]
US 20190253944A1 · Kim · 2019 [cited by examiner]
US 20190261233A1 · Duan · 2019 [cited by examiner]
US 20190306761A1 · Jin · 2019 [cited by examiner]
US 20190357131A1 · Sivavakeesar · 2019 [cited by examiner]
US 20200059989A1 · Velev · 2020 [cited by examiner]
US 20200305054A1 · Zee et al. · 2020 [cited by applicant]
US 20210266820A1 · Lou · 2021 [cited by examiner]
CN 1543109A · 2004 [cited by applicant]
CN 101052208A · 2007 [cited by applicant]
CN 101237677A · 2008 [cited by applicant]
CN 101291537A · 2008 [cited by applicant]
CN 101600238A · 2009 [cited by applicant]
CN 101682532A · 2010 [cited by applicant]
CN 101801055A · 2010 [cited by applicant]
CN 101808374A · 2010 [cited by applicant]
CN 101841824A · 2010 [cited by applicant]
CN 102104927A · 2011 [cited by applicant]
CN 102215537A · 2011 [cited by applicant]
CN 102223669A · 2011 [cited by applicant]
CN 102771158A · 2012 [cited by applicant]
CN 103067864A · 2013 [cited by applicant]
CN 103548387A · 2014 [cited by applicant]
CN 104025639A · 2014 [cited by applicant]
CN 104053200A · 2014 [cited by applicant]
CN 104221405A · 2014 [cited by applicant]
CN 104936237A · 2015 [cited by applicant]
CN 105376811A · 2016 [cited by applicant]
CN 105432135A · 2016 [cited by applicant]
CN 105516312A · 2016 [cited by applicant]
CN 105637905A · 2016 [cited by applicant]
CN 105813195A · 2016 [cited by applicant]
CN 109526252A · 2019 [cited by applicant]
CN 109565732A · 2019 [cited by applicant]
EP 2870795 · 2015 [cited by applicant]
JP 2007214704A · 2007 [cited by applicant]
JP 201028816A · 2010 [cited by applicant]
JP 2011151828A · 2011 [cited by applicant]
JP 2012186865A · 2012 [cited by applicant]
JP 2014171128A · 2014 [cited by applicant]
JP 2015527846A · 2015 [cited by applicant]
JP 2015192453A · 2015 [cited by applicant]
JP 202039182A · 2020 [cited by applicant]
WO 2011020487A1 · 2011 [cited by applicant]
WO 2011021876A2 · 2011 [cited by applicant]
WO 2012055446A1 · 2012 [cited by applicant]
WO 2013033883A1 · 2013 [cited by applicant]
WO 2014005653A1 · 2014 [cited by applicant]
WO 2015160329A1 · 2014 [cited by applicant]
WO 2014158084A1 · 2014 [cited by applicant]
WO 2014161161A1 · 2014 [cited by applicant]
WO 2015115761A1 · 2015 [cited by applicant]
WO 2015119547A1 · 2015 [cited by applicant]
WO 2015139763A1 · 2015 [cited by applicant]
WO 2015162088A1 · 2015 [cited by applicant]
WO 2015168918A1 · 2015 [cited by applicant]
WO 2015169387A1 · 2015 [cited by applicant]
WO WO2018028342A1 · 2018 [cited by examiner]
Japanese Office Action for JP Application No. 2021-025225 mailed on Feb. 22, 2022 with English Translation. [cited by applicant]
Ericsson, Update of QoS Interim agreements, 3GPP TSG-SA WG2#116, S2-163337, Jul. 11-15, 2016. [cited by applicant]
US Office Action for U.S. Appl. No. 17/385,428, mailed on Jul. 12, 2023. [cited by applicant]
US Office Action for U.S. Appl. No. 16/321,998, mailed on Jul. 26, 2023. [cited by applicant]
US Office Action and PTO-892 for U.S. Appl. No. 16/321,998 mailed on Mar. 15, 2022. [cited by applicant]
Communication dated Apr. 4, 2023 issued by the Japanese Intellectual Property Office in counterpart Japanese Application No. 2022-092163. [cited by applicant]
Chinese Office Communication for CN Application No. 201780048078.2 mailed on Aug. 2, 2021 with English Translation. [cited by applicant]
Yang Xiao-Long et al., Spectrum handoff model based on preemptive queuing theory in cognitive radio networks, Acta Phys. Sin. vol. 64, No. 10, Apr. 19, 2015. [cited by applicant]
Zhao Su et al., A Handover Algorithm Based on Prediction of Adjustable Threshold Hysteresis Margin in Ultra Dense Network, Journal of Electronics & Information Technology, vol. 38, No. 3, Mar. 15, 2016. [cited by applicant]
Samsung, “Assignment of CP and UP network functions during an MM procedure”, 3GPP SA WG2 Meeting #116, S2-164041, Jul. 15, 2016, Austria, p. 1-7. [cited by applicant]
International Search Report for PCT Application No. PCT/JP2017/018323, mailed on Jun. 20, 2017. [cited by applicant]
JP Office Action for JP Application No. 2022-167447, mailed on Jul. 4, 2023 with English Translation. [cited by applicant]
Huawei, Clean up of remaining FFS on Security, 3GPP TSG RAN #100 R3-183388, May 28, 2018, pp. 1-15. [cited by applicant]
Nokia (rapporteur), TS 38.413—latest agreed version (V0.1.0), 3GPP TSG RAN WG3 adhoc_R3_AH_NR_1706 R3-172260, Jun. 20, 2017, pp. 1-82. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 13)”, 3GPP TS 36.423 V13.4.0… [cited by applicant]
ETRI, “Update the solution 6.2.1.1: Relation between PDU Flow and Service Data Flow”, SA WG2 Meeting #116, S2-163520, Jul. 2016, 4 pages total. [cited by applicant]
Huawei, “NR RAN functions”, 3GPP TSG-RAN3 Meeting #92, R3-161129, May 2016, 4 pages total. [cited by applicant]
3GPP TR 23.799 V0.7.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)”, Aug. 2016, 322 pages total. [cited by applicant]
Huawei, “Slice impact on mobility”, 3GPP TSG-RAN WG3 95bis R3-171789, Hangzhou, China, May 15-19, 2017, 3 pages total. [cited by applicant]
The Extended European Search Report dated Apr. 12, 2019 in issued by the European Patent Office in counterpart application No. 17839005.0. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Access Architecture and Interfaces (Release 14)” 3GPP TR 38.801 V0.2.0, Jun. 2016, pp.… [cited by applicant]
ETRI et al. “NextGen Core Architecture solution for Network Slice Instance Selection”, S2-162551, SA WG2 Meeting #115, May 23-27, 2016, pp. 1-5. [cited by applicant]
ZTE, “Consideration on RAN Side Network Slicing”, R3-160821, 3GPP TSG RAN WG3 Meeting#91bis, Apr. 11-15, 2016, pp. 1-9. [cited by applicant]
NEC, “RAN architecture impact due to Network Slicing”, R2-162891, 3GPP TSG RAN2#93bis, Apr. 11-15, 2016, pp. 1-6. [cited by applicant]
Communication issued Jun. 10, 2020 by the China National Intellectual Property Administration in application No. 201780014285.6. [cited by applicant]
International Search Report for PCT/JP2017/018224 dated Jun. 6, 2017 [PCT/ISA/210]. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System, (Release 14)”, 3GPP TR 23.799, V0.6.0, Jul. 2016, pp. 1-320. [cited by applicant]
“Solution: Mobility Options”, Nokia, Apr. 11-15, 2016, SA WG2 Meeting #S2-114, S2-161625. pp. 1-5, Sophia Antipolis, FR. [cited by applicant]
Huawei et al., “Network slicing considerations”, 3GPP TSG-RAN WG2, Meeting #93bis R2-162664, Apr. 11-15, 2016 (3 pages total). [cited by applicant]
ZTE: “Network Slice Selection Procedure”, 3GPP TSG RAN WG3 Meeting #92, R3-161107, Nanjing, China, May 23-27, 2016 (4 pages total). [cited by applicant]
ETRI, “High-level Functional Architecture for the Network Slicing”, SA WG2 Meeting #114, S2-161833, Apr. 11-15, 2016, Sophia Antipolis, France (4 pages total). [cited by applicant]
China Mobile et al., “Network Slicing Architecture and High-Level Function Definition,” SA WG2 Meeting #115, S2-162365, May 23-27, 2016, Nanjing, China (5 pages total). [cited by applicant]
CATT, “Control plane for support of NR standalone operation”, 3GPP TSG RAN WG2 Meeting #94, R2-163468, May 23-27, 2016, Nanjing, China (5 pages total). [cited by applicant]
Samsung, “Assignment of CP and UP network functions during an MM procedure” SA WG2 Meeting #116, S2-163297, Jul. 11-15, 2016, Vienna, Austria (6 pages total). [cited by applicant]
Ericsson, “Lossless Inter-RAT handover with 5GC”, 3GPP TSG-RAN WG2 #97, Tdoc R2-1700877, Athens, Greece, Feb. 13-17, 2017 (4 pages total). [cited by applicant]
3GPP TS 33.401; V13.3.0; 3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 13), Jun. 2016 (148 pages… [cited by applicant]
Nokia, Alcatel-Lucent Shanghai Bell, “Interface consideration for tight LTE/NR interworking anchored to NextGen Core”, 3GPP TSG-RAN WG2 Meeting #93bis, R2-162421, Dubrovnik, Croatia, Apr. 11-15, 2016 (2 pages total). [cited by applicant]
3GPP TS 36.300; V13.4.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network… [cited by applicant]
Samsung, “RAN-CN interface aspects”, 3GPP TSG-RAN WG3 Meeting #92, R3-161061, Nanjing, P.R., China, May 23-27, 2016 (4 pages total). [cited by applicant]
Huawei, “Requirements and functionalities of the interface between LTE and NR”, 3GPP TSG-RAN3 Meeting #92, R3-161138, Nanjing, China, May 23-27, 2016 (5 pages total). [cited by applicant]
Huawei et al., “Update of Solution #1 for Key issue #1”, 3GPP SA WG2 Meeting #114, S2-161503, Apr. 11-15, 2016, Sophia Antipolis, France (5 pages total). [cited by applicant]
Nokia et al., “Update to Solution 2.3: Content Aware QoS Framework”, SA WG2 Meeting #115 S2-162706, May 23-27, 2016, Nanjing, P.R. China (7 pages total). [cited by applicant]
NTT Docomo, “Update of Network Slicing Solution 1.3”, SA WG2 Meeting #116, S2-163446, Jul. 11-15, 2016, Vienna, AT (8 pages total). [cited by applicant]
Samsung, “Inter-RAT handover with LTE”, 3GPP TSG-RAN WG3 Meeting #92, R3-161486, Nanjing, P.R. China, May 23-27, 2016 (1 page). [cited by applicant]
3GPP TS 29.280; V14.0.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC (Release 14) … [cited by applicant]
3GPP TS 38.300; V0.2.1; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15) May 2017 (48 pages total). [cited by applicant]
Huawei et al., “Considerations on 5G RAN QoS framework”, 3GPP TSG-RAN2 Meeting #94, R2-164267, Nanjing, China, May 23-27, 2016 (2 pages total). [cited by applicant]
Intel, “Solution for interworking and migration”, SA WG2 Meeting #116, S2-164247, Jul. 11-15, 2016, Vienna, AT (3 pages total). [cited by applicant]
3GPP TR 23.799; V0.6.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14) Jul. 2016 (320 pages total). [cited by applicant]
Huawei, “Inter-RAT handover”, 3GPP TSG-RAN3 Meeting #92, R3-161140, Nanjing, China, May 23-27, 2016 (4 pages total). [cited by applicant]
CATT, “Inter-RAT mobility in NR”, 3GPP TSG RAN WG2#94, R2-163472, Nanjing, China, May 23-27, 2016 (4 pages total). [cited by applicant]
3GPP TS 43.129; V13.0.0; 3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Packet-switched handover for GERAN A/GB mode; Stage 2 (Release 13) Dec. 2015 (95 pages total). [cited by applicant]
3GPP TS 25.413; V13.2.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling (Release 13) Jun. 2016 (451 pa… [cited by applicant]
3GPP TR 23.799; V0.7.0 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14) Aug. 2018 (322 pages total). [cited by applicant]
3GPP TS 36.413; V13.3.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 13) … [cited by applicant]
3GPP TS 48.018; V13.2.0; 3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; General Packet Radio Service (GPRS); Base Station System (BSS)—Serving GPRS Support Node (SGSN); … [cited by applicant]
3GPP TS 23.401; V14.0.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Net… [cited by applicant]
3GPP TR 23.799; V0.4.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14) Apr. 2016 (96 pages total). [cited by applicant]
Extended European Search Report for EP Application No. 20204727.0 dated on Jan. 18, 2021. [cited by applicant]
NTT Docomo, “Solution to support a UE with simultaneous connections to multiple Network Slices”, 3GPP Draft; S2-161043, SA WG2 Meeting #113AH, Sophia Antipolis, France, Feb. 23, 2016-Feb. 26, 2016 Retrieved from the Int… [cited by applicant]
US Office Action and PTO-892 for U.S. Appl. No. 16/321,864 mailed on Nov. 29, 2021. [cited by applicant]
JP Office Action for JP Application No. 2022-130339, mailed on Jun. 27, 2023 with English Translation. [cited by applicant]
Qualcomm Incorporated, NR Mobility, 3GPP TSG-RAN WG3#92, R3-161343, May 27, 2016. [cited by applicant]
US Office Action for U.S. Appl. No. 16/321,877 mailed on Aug. 9, 2021. [cited by applicant]
US Office Action for U.S. Appl. No. 17/385,428 mailed on Oct. 4, 2022. [cited by applicant]
US Office Action for U.S. Appl. No. 16/321,998, mailed on Sep. 29, 2022. [cited by applicant]
CN Office Action for CN Application No. 202111018745.7, mailed on Jan. 1, 2024 with English Translation. [cited by applicant]
Huawei, “Network slicing considerations”, 3GPP TSG-RAN WG3 Meeting #91bis R3-160833, Apr. 15, 2016, pp. 1-pp. 3. [cited by applicant]
CN Office Action for CN Application No. 202110653734.X, mailed on Jan. 2, 2024 with English Translation. [cited by applicant]
CN Office Action for Chinese Patent Application No. 202111018747.6, mailed on Oct. 28, 2023 with English Translation. [cited by applicant]
Chinise Office Action for CN Application No. 202111203306.3 dated on Nov. 13, 2023 with English Translation. [cited by applicant]
CN Office Action for CN Application No. 202111018747.6, mailed on Oct. 28, 2023 with English Translation. [cited by applicant]
US Office Action for U.S. Appl. No. 18/225,421, mailed on Mar. 14, 2024. [cited by applicant]
CN Office Action for CN Application No. 202110655351.6, mailed on Jan. 1, 2024 with English Translation. [cited by applicant]
CN Office Action for CN Application No. 202111018747.6, mailed on Aug. 1, 2024 with English Translation. [cited by applicant]
CN Office Action for CN Application No. 202110324177.7, mailed on Sep. 26, 2024 with English Translation. [cited by applicant]
JP Office Action for JP Application No. 2023-119539, mailed on Jun. 4, 2024 with English Translation. [cited by applicant]
Nokia, Alcatel-Lucent Shanghai Bell, “Context Aware QoS Framework for GBR services”, 3GPP TSG-SA WG2#116 S2-163799, Jul. 17, 2016, p. 1-pp. 10. [cited by applicant]
US Office Action for U.S. Appl. No. 18/397,296, mailed on Jul. 15, 2024. [cited by applicant]
CN Official Communication for CN Application No. 202110326994.6, mailed on Sep. 2, 2024 with English Translation. [cited by applicant]
Huawei, “Network slice selection”, RAN WG3 Meeting #92 R3-161134, May 27, 2016. [cited by applicant]
CN Office Action for CN Application No. 202111018745.7, mailed on Dec. 5, 2024 with English Translation. [cited by applicant]
CN Notice of Allowance for CN Application No. 202111202452.4, mailed on Nov. 29, 2024 with English Translation. [cited by applicant]