IP Library › Granted Patent US 12,641,505
Granted Patent B2
US 12,641,505 · App. 16/072,901 · Granted May 26, 2026

Method and apparatus for implementing mobile edge application session connectivity and mobility

Inventors: John Juha Antero Rasanen (Espoo, FI); Pekka Kuure (Espoo, FI)
Assignee: NOKIA SOLUTIONS AND NETWORKS OY
H04W36/12H04W36/0016H04W36/36H04W88/16
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,641,505
App. No.
16/072,901
Granted
May 26, 2026
Kind
B2
Abstract

A method and apparatus may include detecting a handover that is requested by a user equipment. The user equipment moves from a first area of a first mobile-edge-computing server to a second area of a second mobile-edge-computing server. The method may also include determining whether the user equipment has an ongoing application session with the first mobile-edge-computing server. The method may also include determining whether the ongoing application session should be moved from the first mobile-edge-computing server to the second mobile-edge-computing server, if the user equipment has been determined to have an ongoing application session. The method may also include moving the ongoing application session from the first mobile-edge-computing server to the second mobile-edge-computing server, if the application session has been determined to be moved.

Claims (60)

1 . A first mobile-edge-computing server, comprising:

at least one processor; and

at least one memory including computer program code,

the computer program code, when executed by the at least one processor, is configured to cause the first mobile-edge-computing server to perform:

detecting a handover of a user equipment, which has an ongoing application session with an application hosted on the first mobile-edge-computing server, from an evolved Node B of the first mobile-edge-computing server to an evolved Node B of a second mobile-edge-computing server, wherein the detecting the handover is based on at least one of signaling related to the handover, information from a radio network information service, control plane signaling between the evolved Node B of the first mobile-edge-computing server and the evolved Node B of the second mobile-edge-computing server, signaling between the evolved Node B of the first mobile-edge-computing server and a mobility management entity, or information about the handover;

determining to maintain the ongoing application session of the user equipment with the application hosted on the first mobile-edge-computing server;

in response to the determining, transmitting, to the second mobile-edge-computing server, a request to route traffic identified by a traffic flow template that originates from the user equipment and is related to the ongoing application session to the first mobile-edge-computing server, and to route traffic that originates from the application hosted on the first mobile-edge-computing server and is related to the ongoing application session to the user equipment, wherein said request comprises an Internet Protocol address of the first mobile-edge-computing server; and

maintaining the ongoing application session of the user equipment with the application hosted on the first mobile-edge-computing server.

2 . The first mobile-edge-computing server according to claim 1 , wherein

the computer program code, when executed by the at least one processor, is configured to cause the first mobile-edge-computing server to perform:

identifying the application of the ongoing application session.

3 . The first mobile-edge-computing server according to claim 2 , wherein, the identifying the application comprises:

identifying a unique internet protocol address of the application.

4 . The first mobile-edge-computing server according to claim 3 , wherein

said unique internet protocol address of said application is unique in a network comprising said first mobile-edge-computing server.

5 . The first mobile-edge-computing server according to claim 1 , wherein

the computer program code, when executed by the at least one processor, is configured to cause the apparatus to perform:

deducing, from application-specific information, whether the ongoing application session can be moved to the second mobile-edge-computing server, wherein the application-specific information indicative of whether said application can tolerate or survive a change of an internet protocol address of said application during the ongoing application session is moved to the second mobile-edge-computing server, or is indicative of uniqueness of said internet protocol address of said application.

6 . The first mobile-edge-computing server according to claim 1 , wherein the computer program code, when executed by the at least one processor, is configured to cause the first mobile-edge-computing server to perform:

identifying a topology of a network based on the information from a radio network information service, the network comprising the first mobile-edge-computing server, the second mobile-edge-computing server, the evolved Node B of the first mobile-edge-computing server and the evolved Node B of the second mobile-edge-computing server,

determining a probability of said handover, and

initiating, based on said topology, procedures to optimize a handover performance by sending at least one request to instantiate an application corresponding to applications hosted on said first mobile-edge-computing server on said second mobile-edge-computing server in said network.

7 . The first mobile-edge-computing server according to claim 1 , wherein the computer program code, when executed by the at least one processor, is configured to cause the apparatus to perform:

identifying said second mobile-edge-computing server based on information on the evolved Node B connected to said second mobile-edge-computing server.

8 . The first mobile-edge-computing server according to claim 1 , wherein the computer program code, when executed by the at least one processor, is configured to cause the first mobile-edge-computing server to perform:

initiating session continuity coordination procedures with the second mobile-edge-computing server.

9 . The first mobile-edge-computing server according to claim 8 , wherein the computer program code, when executed by the at least one processor, is configured to cause the first mobile-edge-computing server to perform:

informing, as part of said session continuity coordination procedures, said second mobile-edge-computing server about the handover, or

providing, as part of said session continuity coordination procedures, to said second mobile-edge-computing server, information on the ongoing application session that is handed over, wherein

said information on the ongoing application session that is handed over includes an identifier of the application, an internet protocol addresses of the user equipment, or the internet protocol addresses of the first mobile-edge-computing server.

10 . A method comprising:

detecting, by a first mobile-edge-computing server, a handover of a user equipment, which has an ongoing application session with an application hosted on the first mobile-edge-computing server, from an evolved Node B of the first mobile-edge-computing server and an evolved Node B of a second mobile-edge-computing server, wherein detecting the handover is based on at least one of signaling related to the handover, information from a radio network information service, control plane signaling between the evolved Node B of the first mobile-edge-computing server and the evolved Node B of the second mobile-edge-computing server, signaling between the evolved Node B of the first mobile-edge-computing server and a mobility management entity, or information about the handover;

determining, by the first mobile-edge-computing server, to maintain the ongoing application session of the user equipment with the application hosted on the first mobile-edge-computing server;

in response to the determining, transmitting, by the first mobile-edge-computing server, to the second mobile-edge-computing server, a request to route traffic identified by a traffic flow template that originates from the user equipment and is related to the ongoing application session to the first mobile-edge-computing server, and to route traffic that originates from the application hosted on the first mobile-edge-computing server and is related to the ongoing application session to the user equipment, wherein said request comprises an Internet Protocol address of the first mobile-edge-computing server; and

maintaining, by the first mobile-edge-computing server, the ongoing application session of the user equipment with the application hosted on the first mobile-edge-computing server.

11 . The method according to claim 10 , further comprising:

identifying, by the first mobile-edge-computing server, the application of the ongoing application session.

12 . The method according to claim 11 , wherein the identifying the application comprises:

identifying a unique internet protocol address of the application.

13 . The method according to claim 12 , wherein

said unique internet protocol address of said application is unique in a network comprising the first mobile-edge-computing server.

14 . The method according to claim 10 , further comprising:

deducing, by the first mobile-edge-computing server, from application-specific information, whether the ongoing application session can be moved to the second mobile-edge-computing server, wherein the application-specific information indicative of whether said application can tolerate or survive a change of an internet protocol address of said application during the ongoing application session moved to the second mobile-edge-computing server, or is indicative of uniqueness of said internet protocol address of said application.

15 . The method according to claim 10 , further comprising:

identifying, by the first mobile-edge-computing server, a topology of a network based on the information from a radio network information service, the network comprising the first mobile-edge-computing server, the second mobile-edge-computing server, the evolved Node B of the first mobile-edge-computing server and the evolved Node B of the second mobile-edge-computing server;

determining, by the first mobile-edge-computing server, a probability of said handover from said first mobile-edge-computing server to said second mobile-edge-computing server; and

initiating, by the first mobile-edge-computing server based on said topology, procedures to optimize a handover performance by sending at least one request to instantiate an application corresponding to applications hosted on said first mobile-edge-computing server on said second mobile-edge-computing server in said network.

16 . The method according to claim 10 , further comprising:

identifying, by the first mobile-edge-computing server, said second mobile-edge-computing server based on information on the evolved Node B connected to said second mobile-edge-computing server.

17 . The method according to claim 10 , further comprising:

initiating, by the first mobile-edge-computing server, session continuity coordination procedures with the second mobile-edge-computing server.

18 . The method according to claim 17 , further comprising:

informing, by the first mobile-edge-computing server as part of said session continuity coordination procedures, said second mobile-edge-computing server about the handover; or

providing, as part of said session continuity coordination procedures, to said second mobile-edge-computing server, information on the ongoing application session that is handed over, wherein

said information on the ongoing application session that is handed over includes an identifier of the application, an internet protocol addresses of the user equipment, or the internet protocol addresses of the first mobile-edge-computing server.

19 . A non-transitory computer-readable medium comprising instructions which, when executed by a processor of a first mobile-edge-computing server, causes the processor to perform:

detecting a handover of a user equipment, which has an ongoing application session with an application hosted on the first mobile-edge-computing server, from an evolved Node B of the first mobile-edge-computing server to an evolved Node B of a second mobile-edge-computing server, wherein detecting the handover is based on at least one of signaling related to the handover, information from a radio network information service, control plane signaling between the evolved Node B of the first mobile-edge-computing server and the evolved Node B of the second mobile-edge-computing server, signaling between the evolved Node B of the first mobile-edge-computing server and a mobility management entity, or information about the handover;

determining to maintain the ongoing application session of the user equipment with the application hosted on the first mobile-edge-computing server;

in response to the determining, transmitting, to the second mobile-edge-computing server, a request to route traffic identified by a traffic flow template that originates from the user equipment and is related to the ongoing application session to the first mobile-edge-computing server, and to route traffic that originates from the application hosted on the first mobile-edge-computing server and is related to the ongoing application session of the user equipment, wherein said request comprises an Internet Protocol address of the first mobile-edge-computing server; and

maintaining the ongoing application session of the user equipment with the application hosted on the first mobile-edge-computing server.

Continuity (2)
Provisional Application 62287747 · Jan 27, 2016
Related Publication 20190045409A1 · Feb 7, 2019
References Cited (52)
US 7957287B2 · Venkatachalam · 2011 [cited by examiner]
US 20030058874A1 · Sahaya et al. · 2003 [cited by applicant]
US 20040233866A1 · Bossoli · 2004 [cited by examiner]
US 20060234744A1 · Sung · 2006 [cited by examiner]
US 20070189220A1 · Oberle · 2007 [cited by examiner]
US 20080263219A1 · Bacchi · 2008 [cited by examiner]
US 20100284369A1 · Chu · 2010 [cited by examiner]
US 20110058520A1 · Keller · 2011 [cited by examiner]
US 20110223885A1 · Salkintzis · 2011 [cited by examiner]
US 20120063420A1 · Long · 2012 [cited by examiner]
US 20120164979A1 · Bachmann et al. · 2012 [cited by applicant]
US 20130301466A1 · Nenner · 2013 [cited by examiner]
US 20140022985A1 · Kalmbach · 2014 [cited by examiner]
US 20140050103A1 · Niu · 2014 [cited by examiner]
US 20140064249A1 · Lee · 2014 [cited by examiner]
US 20140113637A1 · Guan · 2014 [cited by examiner]
US 20140177590A1 · Sirotkin · 2014 [cited by examiner]
US 20140194111A1 · Aso · 2014 [cited by examiner]
US 20140256323A1 · Edge · 2014 [cited by examiner]
US 20140307708A1 · Son · 2014 [cited by examiner]
US 20140379901A1 · Tseitlin · 2014 [cited by examiner]
US 20150016420A1 · Balabhadruni · 2015 [cited by examiner]
US 20150058406A1 · Rezvani · 2015 [cited by examiner]
US 20150200802A1 · Sawal · 2015 [cited by examiner]
US 20150201394A1 · Qu · 2015 [cited by examiner]
US 20150208306A1 · Kotecha · 2015 [cited by examiner]
US 20150373149A1 · Lyons · 2015 [cited by examiner]
US 20160088114A1 · Kim · 2016 [cited by examiner]
US 20160094467A1 · Hong · 2016 [cited by examiner]
US 20160134932A1 · Karp · 2016 [cited by examiner]
US 20160170773A1 · Franck · 2016 [cited by examiner]
US 20160183144A1 · Vallabhu · 2016 [cited by examiner]
US 20160205028A1 · Luna · 2016 [cited by examiner]
US 20160212666A1 · Zalzalah · 2016 [cited by examiner]
US 20160219476A1 · Onishi · 2016 [cited by examiner]
US 20160225403A1 · Hostetter · 2016 [cited by examiner]
US 20160344690A1 · Keis · 2016 [cited by examiner]
US 20170093700A1 · Gilley · 2017 [cited by examiner]
US 20170244593A1 · Rangasamy · 2017 [cited by examiner]
US 20170257257A1 · Dawes · 2017 [cited by examiner]
US 20170265057A1 · Zhang · 2017 [cited by examiner]
US 20180242204A1 · Zhu · 2018 [cited by examiner]
US 20190028934A1 · Rasanen et al. · 2019 [cited by applicant]
CN 108886718A · 2018 [cited by applicant]
WO WO2007038947A1 · 2007 [cited by applicant]
International Search Report & Written Opinion dated Jun. 21, 2017 corresponding to International Patent Application No. PCT/EP2017/051765. [cited by applicant]
Intel: “Discussion Paper on ETSI Mobile-Edge Computing (MEC) and its Relevance to 3GPP Multimedia Services,” 3GPP Draft; S4-150757, 3GPP TSG-SA4 Meeting #84, Rennes, France, Jul. 6-10, 2015, XP050987072. [cited by applicant]
ETSI Mobile-Edge Computing—Introductory Technical White Paper; 2014; Huawei et al. [cited by applicant]
3GPP 3GPP TS 23.401 V13.5.0 (Dec. 2015); 2015; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terres… [cited by applicant]
Chinese Office Action issued in corresponding Chinese Patent Application No. 201780020426.5 on Jun. 28, 2020. [cited by applicant]
MEC Mobility Management, Fabio Giust: NEC Europe Ltd, ETSI, Jul. 14, 2015; 10 pages, Jul. 14, 2015. [cited by applicant]
Indian Office Action issued in corresponding Indian Patent Application No. 201817026650 on Jul. 27, 2020. [cited by applicant]