IP Library › Granted Patent US 12,587,825
Granted Patent B2
US 12,587,825 · App. 18/151,983 · Granted Mar 24, 2026

Inter-system mobility in integrated wireless networks

Inventors: John L. Tomici (Southold, NY); Michael F. Starsinic (Newtown, PA); Qing Li (Princeton Junction, NJ)
Assignee: InterDigital Patent Holdings, Inc.
H04W8/06H04W12/08H04W76/12H04W36/1446H04W88/06H04W88/16H04W92/24
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,587,825
App. No.
18/151,983
Granted
Mar 24, 2026
Kind
B2
Abstract

A system is disclosed for providing inter-system mobility in integrated LTE and WiFi systems. A control plane interface, referred to as the S1a-C interface, is defined between a trusted WLAN access network (TWAN) and a mobility management entity (MME) comprised in an LTE wireless access network. A user plane interface, referred to as the S1a-U interface, is defined between the TWAN and a server gateway (SGW) in the LTE wireless access network. The MME operates as a common control plane entity for both LTE and TWAN access, while the SGW operates as a user plane gateway for both LTE and TWAN. The integrated MME and SGW allow for user equipment (UE) to access the capabilities of a packet data network (PDN) through either the LTE access network or TWAN.

Claims (28)

1 . A method, comprising:

receiving, by a mobility management entity, via a non-cellular communication network, a first request to access a connection to a user plane gateway, wherein the first request indicates maintaining of the connection to the user plane gateway simultaneously over a cellular communication network and the non-cellular communication network for access to a first data service, wherein the connection is configured to allow a User Equipment (UE) to transmit packets associated with the first data service from the UE via the cellular communication network and is also configured to allow the UE to transmit packets associated with the first data service from the UE via the non-cellular communication network;

transmitting, by the mobility management entity, a second request to access the connection for the first data service to the user plane gateway, wherein the second request also indicates the maintaining of the connection to the user plane gateway simultaneously over the cellular communication network and the non-cellular communication network;

receiving, by the mobility management entity, a first message that includes tunnel information corresponding to the connection for the first data service to the user plane gateway; and

transmitting, by the mobility management entity, to the non-cellular communication network, a second message that includes the tunnel information corresponding to the connection for the first data service to the user plane gateway.

2 . The method of claim 1 , wherein the non-cellular communication network is a Wireless Fidelity (WiFi) network.

3 . The method of claim 1 , wherein the tunnel information relates to an existing communication path.

4 . The method of claim 3 , wherein the existing communication path is initially established to service access through the cellular communication network.

5 . The method of claim 1 , wherein at least one of the first message or the second message further includes bearer parameters.

6 . The method of claim 1 , wherein at least one of the first message or the second message further includes an Internet Protocol (IP) address.

7 . The method of claim 1 , wherein at least one of the first data service or a second service are associated with an Access Point Name (APN).

8 . The method of claim 1 , wherein at least one of the first request or the second request includes a Radio Access Technology (RAT) type.

9 . The method of claim 1 , wherein at least one of the first request or the second request includes at least one of a Basic Service Set Identifier (BSSID) or a Service Set Identifier (SSID).

10 . The method of claim 1 , wherein the first request and the second request include multi-connection indicators that indicate the maintaining of the connection to the user plane gateway simultaneously over the cellular communication network and the non-cellular communication network.

11 . A network entity comprising one or more processors and one or more memories, the network entity configured to perform operations comprising:

receiving, via a non-cellular communication network, a first request to access a connection to a user plane gateway, wherein the first request indicates maintaining of the connection to the user plane gateway simultaneously over a cellular communication network and the non-cellular communication network for access to a first data service, wherein the connection is configured to allow a User Equipment (UE) to transmit packets associated with the first data service from the UE via the cellular communication network and is also configured to allow the UE to transmit packets associated with the first data service from the UE via the non-cellular communication network;

transmitting a second request to access the connection for the first data service to the user plane gateway, wherein the second request also indicates the maintaining of the connection to the user plane gateway simultaneously over the cellular communication network and the non-cellular communication network;

receiving a first message that includes tunnel information corresponding to the connection for the first data service to the user plane gateway; and

transmitting, to the non-cellular communication network, a second message that includes the tunnel information corresponding to the connection for the first data service to the user plane gateway.

12 . The network entity of claim 11 , wherein the non-cellular communication network is a Wireless Fidelity (WiFi) network.

13 . The network entity of claim 11 , wherein the tunnel information relates to an existing communication path.

14 . The network entity of claim 13 , wherein the existing communication path is initially established to service access through the cellular communication network.

15 . The network entity of claim 11 , wherein at least one of the first message or the second message further includes bearer parameters.

16 . The network entity of claim 11 , wherein at least one of the first message or the second message further includes an Internet Protocol (IP) address.

17 . The network entity of claim 11 , wherein at least one of the first data service or a second service are associated with an Access Point Name (APN).

18 . The network entity of claim 11 , wherein at least one of the first request or the second request includes a Radio Access Technology (RAT) type.

19 . The network entity of claim 11 , wherein at least one of the first request or the second request includes at least one of a Basic Service Set Identifier (BSSID) or a Service Set Identifier (SSID).

20 . The network entity of claim 11 , wherein the first request and the second request include multi-connection indicators that indicate the maintaining of the connection to the user plane gateway simultaneously over the cellular communication network and the non-cellular communication network.

Continuity (4)
Continuation 16801783 · Feb 26, 2020
Continuation 15321365
Provisional Application 62015763 · Jun 23, 2014
Related Publication 20230164653A1 · May 25, 2023
References Cited (120)
US 7539175B2 · White et al. · 2009 [cited by applicant]
US 7650143B2 · Jagadeesan et al. · 2010 [cited by applicant]
US 8014367B2 · Carlton et al. · 2011 [cited by applicant]
US 8174994B2 · Forssell et al. · 2012 [cited by applicant]
US 8224303B2 · White · 2012 [cited by applicant]
US 8289954B2 · Tenny et al. · 2012 [cited by applicant]
US 9042373B2 · Lu et al. · 2015 [cited by applicant]
US 9510256B2 · Krishna et al. · 2016 [cited by applicant]
US 9622121B2 · Lu et al. · 2017 [cited by applicant]
US 10009802B2 · Lu et al. · 2018 [cited by applicant]
US 20020184510A1 · Shieh · 2002 [cited by applicant]
US 20060002344A1 · Ono et al. · 2006 [cited by applicant]
US 20060256751A1 · Jagadeesan et al. · 2006 [cited by applicant]
US 20060259951A1 · Forssell et al. · 2006 [cited by applicant]
US 20070041350A1 · Famolari · 2007 [cited by applicant]
US 20070064660A1 · Qi et al. · 2007 [cited by applicant]
US 20070291685A1 · Fiat · 2007 [cited by applicant]
US 20080107119A1 · Chen et al. · 2008 [cited by applicant]
US 20080159232A1 · Thalanany et al. · 2008 [cited by applicant]
US 20080273524A1 · Tenny et al. · 2008 [cited by applicant]
US 20090201881A1 · Chun et al. · 2009 [cited by applicant]
US 20090207812A1 · Gupta et al. · 2009 [cited by applicant]
US 20090287764A1 · Pazhyannur et al. · 2009 [cited by applicant]
US 20100208698A1 · Lu et al. · 2010 [cited by applicant]
US 20100323700A1 · Bachmann et al. · 2010 [cited by applicant]
US 20110141884A1 · Olsson · 2011 [cited by examiner]
US 20110310876A1 · Carlton et al. · 2011 [cited by applicant]
US 20120140743A1 · Pelletier et al. · 2012 [cited by applicant]
US 20130005332A1 · Sedlacek et al. · 2013 [cited by applicant]
US 20130077482A1 · Krishna · 2013 [cited by examiner]
US 20130157659A1 · Ikeda et al. · 2013 [cited by applicant]
US 20130294409A1 · Shuai et al. · 2013 [cited by applicant]
US 20130308513A1 · Jheng · 2013 [cited by examiner]
US 20140036807A1 · Huang · 2014 [cited by examiner]
US 20140185603A1 · Kaippallimalil · 2014 [cited by examiner]
US 20150103804A1 · Gao · 2015 [cited by examiner]
US 20150282026A1 · Gupta · 2015 [cited by applicant]
US 20160112896A1 · Karampatsis et al. · 2016 [cited by applicant]
US 20220264573A1 · Marinier et al. · 2022 [cited by applicant]
CN 101022450A · 2007 [cited by applicant]
CN 101090573A · 2007 [cited by applicant]
CN 101431780A · 2009 [cited by applicant]
CN 102752830A · 2012 [cited by applicant]
CN 103369502A · 2013 [cited by applicant]
CN 103517264A · 2014 [cited by applicant]
CN 103687071A · 2014 [cited by applicant]
CN 103716770A · 2014 [cited by applicant]
EP 1538861A2 · 2005 [cited by applicant]
JP 2005057551A · 2005 [cited by applicant]
JP 2008278512A · 2008 [cited by applicant]
JP 2011509615A · 2011 [cited by applicant]
JP 2013131793A · 2013 [cited by applicant]
KR 1020060113727A · 2006 [cited by applicant]
KR 1020080009131A · 2008 [cited by applicant]
KR 1020140006329A · 2014 [cited by applicant]
KR 1020140038703A · 2014 [cited by applicant]
KR 1020170019466A · 2017 [cited by applicant]
TW 200822617A · 2008 [cited by applicant]
TW 200901799A · 2009 [cited by applicant]
WO 2004105272A1 · 2004 [cited by applicant]
WO 2006130058A1 · 2006 [cited by applicant]
WO 2007063901A1 · 2007 [cited by applicant]
WO 2007144225A1 · 2007 [cited by applicant]
WO 2013019501A1 · 2013 [cited by applicant]
WO 2014107358A1 · 2014 [cited by applicant]
WO 2016059109A2 · 2016 [cited by applicant]
U.S. Appl. No. 16/801,783, filed Feb. 26, 2020. [cited by applicant]
U.S. Appl. No. 15/321,365, filed Dec. 22, 2018. [cited by applicant]
3GPP TS 23402 V12.4.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for non-3GPP Accesses (Release 12), Mar. 2014. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses”, TS 23.402 Release 12, V12.1.0, Jun. 2013, 254 pages. [cited by applicant]
3rd Generation Partnership Project (3GPP); TSG-SA WG2#79 S2-102299, Cisco, ATT, Nokia, NSN, Ericsson, Prefix Delegation: Use Cases and Solution Discussion, 3GPP, May 2010, 11 pages. [cited by applicant]
3rd Generation Partnership Project (3GPP); TSG-SA WG2#94 S2-124315, Huawei, Hisilicon, Proposal for SaMOG Solution with Simple IPSec Tunnel, 3GPP, Nov. 2012, 14 pages. [cited by applicant]
3rd Generation Partnership Project (3GPP); TSG-SA WG2-#95 S2-130535, ZTE, China Unicom, Broadcom Corporation, Merged Stateful DHCP-Based Solution, 3GPP, Jan. 2013, 22 pages. [cited by applicant]
3rd Generation Partnership Project; (3GPP) TR 23.852 V12.0.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on S2a Mobility based on GPRS Tunnelling Protocol (GTP) … [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 22.234 V11.0.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Requirements on 3GPP system to Wireless Local Area Network (WL… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 23.234 V11.0.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP system to Wireless Local Area Network (WLAN) interworking… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 23.401 V12.3.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved U… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 23.402 V12.3.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture Enhancements for Non-3GPP Accesses (Release 12), … [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 24.008 V12.4.0, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile radio interface Layer 3 specification; Core network prot… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 24.244 V1.0.0, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Wireless LAN control plane protocol for trusted WLAN access to E… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 29.273 V12.2.0, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); 3GPP EPS AAA interfaces (Release 1… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 29.274 V12.3.0, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio … [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 29.281 V11.6.0, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; General Packet Radio System (GPRS) Tunnelling Protocol User Pla… [cited by applicant]
3rd Generation Partnership Project; (3GPP) TS 43.318 V11.0.0, 3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Generic Access Network (GAN); Stage 2 (Release 11), Sep. 201… [cited by applicant]
Ericsson: Initial attach and handover attach call flows for single-connection, sA WG2 Meeting #100 S2-134261, 2013, 3-15. [cited by applicant]
Ferrus et al, “Interworking in Heterogeneous Wireless Networks: Comprehensive Framework and Future Trends”, IEEE Wireless Communications, Apr. 2010, 22-31. [cited by applicant]
International Patent Application No. PCT/US2015/037186: International Search Report and The Written Opinion dated Oct. 2, 2015, 12 pages. [cited by applicant]
Korean Patent Application No. 10-2017-7001904: Preliminary Rejection dated Jul. 17, 2017, 10 pages. [cited by applicant]
Ramon Ferrus et al: “Interworking in heterogeneous wireless networks: Comprehensive framework and future trends”, IEEE Wireless Communications, IEEE Service Center, Piscataway, NJ, US, vo I. 17, No. 2, Apr. 1, 2010, pp.… [cited by applicant]
Sankaran, C.B., “Data Offloading Techniqures in 3GPP Rel-10 Networks: A Tutorial”, IEEE Communications Magazine, Jun. 2012, 46-53. [cited by applicant]
SANKARAN: “Data offloading techniques in 3GPP Rel-10 networks: A tutorial”, IEEE Communications Magazine, IEEE Service Center, Piscataway, US, vol. 50, No. 6, Jun. 1, 2012, pp. 46-53. [cited by applicant]
Tomici et al, “Integrated Small Cell and Wi-Fi Networks” 2015 IEEE Wireless Communications and Networking Conference (WCNC):—Track 3: Mobile and Wireless Networks, 2015 1261-1266. [cited by applicant]
Takechi et al., “Network Selection and Route Management for the Mobile Networks”, The Transactions of the Institute of Electronics, Information and Communication Engineers B, vol. J89-B, No. 2, Feb. 1, 2006, 12 pages (1… [cited by applicant]
3rd Generation Partnership Project (3GPP), S2-082105, “ANDSF-Initiated Transactions”, Motorola, InterDigital, AT&T, Intel, 3GPP TSG-SA WG2 Meeting #64, Jeju, South Korea, Apr. 7-11, 2008, 5 pages. [cited by applicant]
3rd Generation Partnership Project (3GPP), TD S1-084182, “Use Cases for MAPIM”, 3GPP TSG-SA WG1, Meeting #43, Miami, Flordia, Nov. 17-21, 2008, 4 pages. [cited by applicant]
3rd Generation Partnership Project (3GPP), TD S2-086386, “Multi Access PDN Connectivity and IP Flow Mobility-WID”, China Mobile, Marvell, Orange, Panasonic, Qualcomm Europe, Samsung, Telecom Italia, TeliaSonera, 3GPP TS… [cited by applicant]
3rd Generation Partnership Project (3GPP), TR 23.861 V1.2.0, “Technical Specification Group Services and System Aspects, Multi Access PDN Connectivity and IP Flow Mobility (Release 9)”, May 2009, pp. 1-48. [cited by applicant]
3rd Generation Partnership Project (3GPP), TR 23.xxx V0.1.0, “Technical Specification Group Services and System Aspects, Multi Access PDN Connectivity and IP Flow Mobility (Release 9)”, Nov. 2008, pp. 1-14. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.060 V8.3.0, “Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS), Service Description, Stage 2 (Release 8)”, Dec. 2008, pp. 1-2… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.060 V8.7.0, “Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS), Service Description, Stage 2 (Release 8)”, Dec. 2009, pp. 1-2… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.060 V9.3.0, “Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS), Service Description, Stage 2 (Release 9)”, Dec. 2009, pp. 1-2… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.203 V8.4.0, “Technical Specification Group Services and System Aspects, Policy and Charging Control Architecture (Release 8)”, Dec. 2008, pp. 1-111. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.203 V8.8.0, “Technical Specification Group Services and System Aspects, Policy and Charging Control Architecture (Release 8)”, Dec. 2009, pp. 1-115. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.203 V9.3.0, “Technical Specification Group Services and System Aspects, Policy and Charging Control Architecture (Release 9)”, Dec. 2009, pp. 1-123. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.327 V8.2.0, “Technical Specification Group Services and System Aspects, Mobility between 3GPP-Wireless Local Area Network (WLAN) Interworking and 3GPP Systems (Release 8)… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.327 V9.0.0, “Technical Specification Group Services and System Aspects, Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP Systems (Release 9)… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.401 V8.4.1, “Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Ne… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.401 V8.8.0, “Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Ne… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.401 V9.3.0, “Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Ne… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.402 V8.4.0, “Technical Specification Group Services and System Aspects, Architecture Enhancements for Non-3GPP Accesses (Release 8)”, Dec. 2008, pp. 1-190. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.402 V8.8.0, “Technical Specification Group Services and System Aspects, Architecture Enhancements for Non-3GPP Accesses (Release 8)”, Dec. 2009, pp. 1-199. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.402 V9.3.0, “Technical Specification Group Services and System Aspects, Architecture Enhancements for Non-3GPP Accesses (Release 9)”, Dec. 2009, pp. 1-198. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 24.302 V8.0.0, Technical Specification Group Core Network and Terminals, Access to the 3GPP Evolved Packet Core (EPC) Via Non-3GPP Access Networks, Stage 3, (Release 8), Dec… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 24.302 V8.4.1, “Technical Specification Group Core Network and Terminals, Access to the 3GPP Evolved Packet Core (EPC) Via Non-3GPP Access Networks, Stage 3 (Release 8)”, De… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 24.302 V9.1.1, “Technical Specification Group Core Network and Terminals, Access to the 3GPP Evolved Packet Core (EPC) Via Non-3GPP Access Networks, Stage 3, (Release 9)”, D… [cited by applicant]
3rd Generation Partnership Project, TR 23.861 V1.0.0, “Technical Specification Group Services and System Aspects, Multi Access PDN Connectivity and IP Flow Mobility (Release 9)”, Mar. 2009, 34 pages. [cited by applicant]
Melia et al., “IEEE 802.21 Mobility Services Framework Design (MSFD)”, Network Working Group, Request for Comments: 5677, Category: Standards Track, Dec. 2009, pp. 1-25. [cited by applicant]
Soliman et al., “Flow Bindings in Mobile IPv6 and NEMO Basic Support”, IETF MEXT Working Group, Internet-Draft, Intended Status: Standards Track, Intended Status: Standards Track, Feb. 13, 2009, pp. 1-32. [cited by applicant]
Soliman et al., “Flow movement in Mobile IPv6”, , Jun. 2003, pp. 1-8. [cited by applicant]
3rd Generation Partnership Project (3GPP), TR 23.xxx V0.1.0, “Technical Specification Group Services and System Aspects, Multi Access PDN Connectivity and IP Flow Mobility (Release 9)”, Nov. 2008, pp. 1-14. (this refere… [cited by applicant]