IP Library › Granted Patent US 12,294,896
Granted Patent B2
US 12,294,896 · App. 18/225,421 · Granted May 6, 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
H04W36/0033H04W36/13H04W36/1443H04W36/0038H04W92/20
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,294,896
App. No.
18/225,421
Granted
May 6, 2025
Kind
B2
Abstract

In response to receiving from a source RAN node ( 2 ), on a direct interface ( 101 ), a message requesting a handover of a radio terminal ( 1 ) from a first network to a second network, a target RAN node ( 3 ) receives at least one of slice information and flow information from a core network ( 5 ), and controls communication of the radio terminal ( 1 ) based on at least one of the slice information and the flow information. The slice information relates to a network slice in the second network. The flow information relates to at least one session to be established in the second network, serving as a bearer-less network, in order to transfer at least one packet flow of the radio terminal ( 1 ). It is thus possible, for example, to provide an Inter-RAT handover procedure involving transfer of handover signaling messages on a direct inter-base-station interface.

Claims (58)

1. A target radio access network (RAN) node connected to a Fifth Generation Core (5G Core) 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:

receive, from a source RAN node, a Handover Request message on an interface between the target RAN node and the source RAN node connected to the 5G Core network; and

transmit, to the source RAN node, a Handover Request Acknowledge message including a transparent container that contains radio resource configuration information which is transferred to a radio terminal via the source RAN node,

wherein the Handover Request message includes: slice information, list information of a Protocol Data Unit (PDU) Session, and flow list information indicating at least one flow to be setup,

wherein the slice information identifies a network slice, the network slice being a logical network,

wherein the list information of the PDU Session includes a PDU Session ID corresponding to a PDU Session,

wherein the at least one flow indicated in the flow list information is configured within the PDU session, and

wherein the flow list information includes:

a flow identifier identifying the at least one flow within the PDU session; and

a flow QoS parameter corresponding to the flow identified by the flow identifier.

2. The target RAN node according to claim 1 , wherein the source RAN node and the target RAN node are 5G base stations.

3. The target RAN node according to claim 1 , wherein the radio resource configuration information is created using the Handover Request message.

4. The target RAN node according to claim 1 , wherein the radio resource configuration information is created using at least one of the flow list information and the slice information.

5. A source radio access network (RAN) node connected to a Fifth Generation Core (5G Core) network, the source RAN comprising:

at least one memory; and

at least one processor coupled to the at least one memory and configured to:

transmit, to a target RAN node, a Handover Request message on an interface between the target RAN node and the source RAN node, the target RAN node being connected to the 5G Core network;

receive from the target RAN node, on the interface between the target RAN node and the source RAN node, a Handover Request Acknowledge message including a transparent container that contains radio resource configuration information; and

transmit the radio resource configuration information to a radio terminal,

wherein the Handover Request message includes: slice information, list information of a Protocol Data Unit (PDU) Session, and flow list information indicating at least one flow to be setup,

wherein the slice information identifies a network slice, the network slice being a logical network,

wherein the list information of the PDU Session includes a PDU Session ID corresponding to a PDU Session,

wherein the at least one flow indicated in the flow list information is configured within the PDU session, and

wherein the flow list information includes:

a flow identifier identifying the at least one flow within the PDU session; and

a flow QoS parameter corresponding to the flow identified by the flow identifier.

6. The source RAN node according to claim 5 , wherein the source RAN node and the target RAN node are 5G base stations.

7. The source RAN node according to claim 5 , wherein the radio resource configuration information is created using the Handover Request message.

8. The source RAN node according to claim 5 , wherein the radio resource configuration information is created using at least one of the flow list information and the slice information.

9. A method of a target radio access network (RAN) node connected to a Fifth Generation Core (5G Core) network, the method comprising:

receiving, a source RAN node, a Handover Request message on an interface between the target RAN node and the source RAN node connected to the 5G Core network; and

transmitting, to the source RAN node, a Handover Request Acknowledge message including a transparent container that contains radio resource configuration information which is transferred to a radio terminal via the source RAN node,

wherein the Handover Request message includes: slice information, list information of a Protocol Data Unit (PDU) Session, and flow list information indicating at least one flow to be setup,

wherein the slice information identifies a network slice, the network slice being a logical network,

wherein the list information of the PDU Session includes a PDU Session ID corresponding to a PDU Session,

wherein the at least one flow indicated in the flow list information is configured within the PDU session, and

wherein the flow list information includes:

a flow identifier identifying the at least one flow within the PDU session; and

a flow QoS parameter corresponding to the flow identified by the flow identifier.

10. The method according to claim 9 , wherein the source RAN node and the target RAN node are 5G base stations.

11. The method according to claim 9 , wherein the radio resource configuration information is created using the Handover Request message.

12. The method according to claim 9 , wherein the radio resource configuration information is created using at least one of the flow list information and the slice information.

13. A method of a source radio access network (RAN) node connected to a Fifth Generation Core (5G Core) network, the method comprising:

transmitting, to a target RAN node, a Handover Request message on an interface between the target RAN node and the source RAN node, the target RAN node being connected to the 5G Core network;

receiving from the target RAN node, on the interface between the target RAN node and the source RAN node, a Handover Request Acknowledge message including a transparent container that contains radio resource configuration information; and

transmitting the radio resource configuration information to the radio terminal,

wherein the Handover Request message includes: slice information, list information of a Protocol Data Unit (PDU) Session, and flow list information indicating at least one flow to be setup,

wherein the slice information identifies a network slice, the network slice being a logical network,

wherein the list information of the PDU Session includes a PDU Session ID corresponding to a PDU Session,

wherein the at least one flow indicated in the flow list information is configured within the PDU session, and

wherein the flow list information includes:

a flow identifier identifying the at least one a flow within the PDU session; and

a flow QoS parameter corresponding to the flow identified by the flow identifier.

14. The method according to claim 13 , wherein the source RAN node and the target RAN node are 5G base stations.

15. The method according to claim 13 , wherein the radio resource configuration information is created using the Handover Request message.

16. The method according to claim 13 , wherein the radio resource configuration information is created using at least one of the flow list information and the slice information.

Priority Claims (1)
JP 2016-158282 · Aug 10, 2016 · national
Continuity (3)
Continuation 17385428 · Jul 26, 2021
Continuation 16321998
Related Publication 20230370928A1 · Nov 16, 2023
References Cited (212)
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 20020191556A1 · Krishnarajah et al. · 2002 [cited by applicant]
US 20030016259A1 · Otokita et al. · 2003 [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 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 20150139195A1 · Xiao · 2015 [cited by applicant]
US 20150215822A1 · Won et al. · 2015 [cited by applicant]
US 20150229491A1 · Solovyev et al. · 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 · 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 · 2017 [cited by applicant]
US 20170288972A1 · Li · 2017 [cited by examiner]
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 et al. · 2017 [cited by applicant]
US 20170359768A1 · Byun · 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 et al. · 2018 [cited by applicant]
US 20180035339A1 · Mitsui · 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 et al. · 2018 [cited by applicant]
US 20180368140A1 · Centonza · 2018 [cited by examiner]
US 20190007899A1 · Vrzic · 2019 [cited by applicant]
US 20190021043A1 · Youn et al. · 2019 [cited by applicant]
US 20190029000A1 · Vikberg · 2019 [cited by applicant]
US 20190098544A1 · Han et al. · 2019 [cited by applicant]
US 20190150219A1 · Wang · 2019 [cited by applicant]
US 20190158360A1 · Xu et al. · 2019 [cited by applicant]
US 20190159027A1 · Kuge et al. · 2019 [cited by applicant]
US 20190174368A1 · Decarreau · 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 applicant]
US 20190261233A1 · Duan et al. · 2019 [cited by applicant]
US 20190306761A1 · Jin et al. · 2019 [cited by applicant]
US 20190357131A1 · Sivavakeesar et al. · 2019 [cited by applicant]
US 20190387393A1 · Xu · 2019 [cited by applicant]
US 20200059989A1 · Velev et al. · 2020 [cited by applicant]
US 20200305054A1 · Zee et al. · 2020 [cited by applicant]
US 20210266820A1 · Lou et al. · 2021 [cited by applicant]
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 2870795A · 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 2015192453A1 · 2015 [cited by applicant]
JP 2020039182A · 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 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 2015160329A1 · 2015 [cited by applicant]
WO 2015162088A1 · 2015 [cited by applicant]
WO 2015168918A1 · 2015 [cited by applicant]
WO 2015169387A1 · 2015 [cited by applicant]
WO 2018028342A1 · 2018 [cited by applicant]
CN Office Action for CN Application No. 202111018747.6, mailed on Oct. 28, 2023 with English Translation. [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, 5 pgs., Nanjing, China. [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]
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 (20 p… [cited by applicant]
Ericsson, “Lossless Inter-RAT handover with 5GC”, 3GPP TSG-RAN WG2 #97, Tdoc R2-1700877, Athens, Greece, Feb. 13-17, 2017, pp. 1-4 (4 pages total). [cited by applicant]
Communication dated Aug. 20, 2020, from the State Intellectual Property Office in application No. 201780048078.2. [cited by applicant]
Communication dated Sep. 23, 2020, from the Japanese Patent Office in application No. 2019224261. [cited by applicant]
CATT, “Control plane for support of NR standalone operation”, 3GPP TSG RAN WG2 Meeting #94, R2- 163468, May 23-27, 2016, 5 pgs., Nanjing, China. [cited by applicant]
Communication dated Jul. 17, 2019, from the European Patent Office in counterpart European Application No. 17839006.8. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall descr… [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]
Huawei et al., “Update of Solution #1 for Key issue #1”, 3GPP SA WG2 Meeting #114, S2-161503, Apr. 11-15, 2016, total 5 pages. [cited by applicant]
“Update of Network Slicing Solution 1.3”, NTT Docomo, SA WG2 Meeting #116, S2-163446, Jul. 11-15, 2016, ( 8 pages total). [cited by applicant]
3GPP TS 23.401 VI 4.0.0 (Jun. 2016), Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (R… [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, 320 pgs. [cited by applicant]
ETRI, “High-level Functional Architecture for the Network Slicing”, SA WG2 Meeting #114, S2-161833, Apr. 11-15, 2016, 4 pgs. Sophia Antipolis, France. [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]
Nokia, Alcatel-Lucent Shanghai Bell, Interface consideration for tight LTE/NR interworking anchored to NextGen Core, 3GPP TSG-RAB WG2 Meeting #93bis, R2-162421, Dubrovnik, Croatia, Apr. 11-15, 2016 (2 pages total). [cited by applicant]
3GPP TS36.413 V 13.3.0 (Jun. 2016), Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 13), pp. 1-331. [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, 6 pgs., Vienna, Austria. [cited by applicant]
International Search Report for PCT/JP2017/018227 dated, Jul. 4, 2017 (PCT/ISA/210). [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]
3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 13), 3GPP TS 33.401 V13.3.0, Jun. 2016 (148 pages … [cited by applicant]
Nokia et al., “Update to Solution 2.3: Content Aware QoS Framework”, 3GPP, SA WG2 Meeting #115, S2-162706, May 23-27, 2016, pp. 1-7. [cited by applicant]
Communication dated Sep. 24, 2019 from Japanese Patent Office in counterpart JP Application No. 2018-533427. [cited by applicant]
3GPP TR23.799 V0.70 (Mar. 2016), Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14), pp. 1-322. [cited by applicant]
3GPP TS25.413 V13.2.0 (Jun. 2016), Technical Specification Group Radio Access Network: UTRAN lu interface Radio Access Network Application Part (RANAP) signaling (Release 13), pp. 1-451. [cited by applicant]
Huawei et al: “Considerations on 5G Kan QoS framework”, 3GPP TSG-RAN2 Meeting #94, R2-164267, May 22, 2018, China. [cited by applicant]
Etri et al., “NextGen Core Architecture solution for Network Slice Instance Selection”, 3GPP SA WG2 Meeting #115, S2-162551.May 23-27, 2016. China, pp. 1-5. [cited by applicant]
NTT Docomo, “Solution to support a UE with simultaneous connections to multiple Network Slices”, 3GPP Draft, SA WG2 Meeting #113AH, S2-161043, Feb. 18, 2016, France, pp. 1-4. [cited by applicant]
Huawei, HiSilicon, “Update of Solution #1 for Key issue #1”, 3GPP TSG SA WG2#114, S2-161503. Apr. 2018, France. [cited by applicant]
Extended European Search Report for EP Application No. 20205291.6 dated on Feb. 18, 2021. [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]
Intel, “Solution for interworking and migration”, SA WG2 Meeting #116, S2-164247, Jul. 11-15, 2016, pp. 1-3. [cited by applicant]
3GPP TR 38.801 V0.2.0 (Jun. 2016), Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Access Architecture and Interfaces (Release 14), pp. 1-20. [cited by applicant]
Nokia, “Solution: Mobility Options”, Apr. 11-15, 2016, SA WG2 Meeting # S2-114, S2-161625, France, pp. 1-5. [cited by applicant]
Nokia, Alcatel Lucent Shanghai Bell, “Update to Solution 2.3: Content Aware QoS Framework”, 3GPP TSG SA WG2#115, S2-162706, 2016.05, China, pp. 1-7. [cited by applicant]
3GPP TR 23.799 V0.4.0, Technical Specification Group Services and System Aspects; Study on Architecture For Next Generation System (Release 14), pp. 1-96. [cited by applicant]
3GPP TS 48.018 V13.2.0 (Aug. 2016), Technical Specification Group GSM/EDGE Radio Access Network; General Packet Radio Service (GPRS); Base Station System (BSS)—Serving GPRS Support Node (Sgsn); 3SS GPRS Protocol (3SSGP)… [cited by applicant]
3GPP TS43.129 V13.0.0 (Dec. 2015), Technical Specification Group GSM/EDGE Radio Access Net-work; Packet switched handover for GERAN A/GB mode; Stage 2 (Release 13), pp. 1-95. [cited by applicant]
3GPP TS 38.300 V0.2.1, Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15), May 10, 2017, pp. 1-48. [cited by applicant]
ZTE, “Consideration on RAN Side Network Slicing”, 3GPP TSG RAN WG3 Meeting #91 bis, R3-160821, Apr. 11-15, 2016. India. [cited by applicant]
Samsung, “Inter-RAT handover with LTE”. 3GPP TSG-RAN WG3#92, R3-161486, May 27. 2016, China. [cited by applicant]
ZTE, “Network Slice Selection Procedure”, 3GPP Draft, TSG RAN WG3 Meeting #92, R3-161107, May 22, 2016 China. [cited by applicant]
Chinese Office Action for CN Application No. 201780048078.2 dated on Feb. 10, 2021 with English Translation. [cited by applicant]
Huawei, “NR RAN functions”, 3GPP TSG-RAN3 Meeting #92, R3-161129, May 2016, 4 pages total. [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]
CATT, “inter-RAT mobility in NR”, R2-163472, RANWG2 Meeting #94, China, May 23-27, 2015, pp. 1-4. [cited by applicant]
3GPP TS 29.280 V 14.0.0. 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), Mar. 22, 2017, pp. 1-23. [cited by applicant]
NEC, “RAN architecture impact due to Network Slicing”, 3GPP TSG RAN2 #93bis, R2-162891, Apr. 11-15, 2016, Croatia. [cited by applicant]
NTT Docomo, “Update of Network Slicing Solution 1.3”, 3GPP TSG-SA WG2#116, S2-163446, Jul. 5, 2016, pp. 1-8. [cited by applicant]
Huawei, HiSilicon, “Network slicing considerations”, 3GPP TSG-RAN WG2 Meeting #93bis R2-162664, Apr. 1, 2016, Croatia. [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]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Oct. 6, 2020. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Mar. 26, 2021. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Sep. 29, 2022. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Oct. 12, 2021. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Mar. 15, 2022. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Feb. 28, 2023. [cited by applicant]
Advisory Action for U.S. Appl. No. 16/321,998, mailed on May 16, 2023. [cited by applicant]
Chinese Office Communication for CM 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 Rhys. 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]
U.S. Office Action for U.S. Appl. No. 17/385,428, mailed on Oct. 4, 2022. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 17/385,428, mailed on Mar. 9, 2023. [cited by applicant]
JP Office Action for JP Application No. 2022-130339, mailed on Jun. 27, 2023 with English Translation. [cited by applicant]
JP Office Communication for JP Application No. 2022-167447, mailed on Jul. 4, 2023 with English Translation. [cited by applicant]
Qualcomm Incorporated, NR Mobility, 3GPP TSG-RAN WG3#92, R3-161343, May 27, 2016. [cited by applicant]
Huawei, Clean up of remaining FFS on Security, 3GPP TSG RAN WG3 #100, R3-183388, May 28, 2018. [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. [cited by applicant]
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. 5, 2016. [cited by applicant]
U.S. Office Action and PTO-892 for U.S. Appl. No. 16/321,864 mailed on Nov. 29, 2021. [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, pp. 1-7. [cited by applicant]
International Search Report for PCT Application No. PCT/JP2017/018323, mailed on Jun. 20, 2017. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 16/321,877 mailed on Aug. 9, 2021. [cited by applicant]
U.S. Notice of Allowance for U.S. Appl. No. 16/321,998, mailed on Jul. 26, 2023. [cited by applicant]
CN Office Action for CN Application No. 202110655351.6, mailed on Jan. 1, 2024 with English Translation. [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 TS36.413 V i 3.3.0 (Jun. 2018), Technical Specification Group Radio Access Network; t-voived Universal Terrestrial Radio Access Network (E-UTRAN); SI Application Protocol (S1AP) (Release 13), pp. 1-331. [cited by applicant]
3GPP TS25.413 V13.2.0 (Jun. 2018), Technical Specification Group Radio Access Network: UTRAN lu interface Radio Access Network Application Part (RANAP) signaling (Release 13), pp. 1-451. [cited by applicant]
Nokia, Alcatel Lucent Shanghai Bell, “Update to Solution 2.3: Content Aware QoS Framework”, 3GPP TSG SA WG2#115, S2-162706, May 2016, China, pp. 1-7. [cited by applicant]
3GPP TS 4S.018 V13.2.0 (Aug. 2016), Technical Specification Group GSM/EDGE Radio Access Network; General Packet Radio Service (GPRS); Base Station System (BSS)—Serving GPRS Support Node (SGSN); 3SS GPRS Protocol (3SSGP)… [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]
U.S. Office Action for U.S. Appl. No. 16/321,998, mailed on Jul. 26, 2023. [cited by applicant]
CN Office Action for Chinese Patent Application No. 202111203306.3, mailed on Nov. 13, 2023 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]
CN Office Action for CN Application No. 202111018747.6, mailed on Aug. 1, 2024 with English Translation. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 18/397,296, mailed on Jul. 15, 2024. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 17/376,920, mailed on Jun. 20, 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. 202110324177.7, mailed on Sep. 26, 2024 with English Translation. [cited by applicant]
U.S. Office Action for U.S. Appl. No. 17/376,920 mailed on Dec. 3, 2024. [cited by applicant]
Chinese Office Communication for CN Application No. 202111202452.4 mailed on Nov. 29, 2024 with English Translation. [cited by applicant]
Chinese Office Action for CN Application No. 202111018745.7 mailed on Dec. 5, 2024 with English Translation. [cited by applicant]