WO2018215816A1

WO2018215816A1 - Handover at network edge

Info

Publication number: WO2018215816A1
Application number: PCT/IB2017/053049
Authority: WO
Inventors: John RÄSÄNEN
Original assignee: Nokia Technologies Oy; Nokia Usa Inc.
Priority date: 2017-05-23
Filing date: 2017-05-23
Publication date: 2018-11-29

Abstract

An apparatus, method, and computer program product are provided for facilitating inter-gateway handover at a network edge. The apparatus may identify a mobile device connected to a network via a first gateway, and may cause one or more parameters identifying the mobile device to be stored. The apparatus may detect an application session of the mobile device on a bearer and cause the application session to be bound to the identity of the mobile device. Following a change in connection of the mobile device from a first gateway to a second gateway, the apparatus may cause updated parameters identifying the mobile device to be stored, may detect that the application session of the mobile device is ongoing, and may apply policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

Description

HANDOVER AT NETWORK EDGE

TECHNOLOGICAL FIELD

[0001] An example embodiment relates generally to communications networks and multiaccess edge computing ("MEC") and, more particularly, to maintaining application sessions via inter-gateway handover at a network's edge.

BACKGROUND

[0002] Mobile devices are often utilized by users to access applications hosted by a network. As a mobile device moves between various locations, the mobile device may connect to a central or core network via various gateways and access networks.

However, in current and emerging communication networks, applications hosted by the network often cannot tolerate a change of an internet protocol (IP) address of a mobile device due to a change in the location of the mobile device. For example, an application may identify a mobile device and/or user based upon an IP address of a user or mobile device assigned by a local gateway. If the IP address used to access the core or central network by the mobile device or user is released in conjunction with a change in gateway (inter-gateway handover), the application may not be able to effectively communicate with the mobile device.

[0003] Additionally, a further problem may arise, if/when an IP address is released, due to a change in location of the mobile device, where the former IP address is allocated to another mobile device that connects to the network via the gateway left by the mobile device. In such a circumstance, another mobile device now assigned the former IP address may access the same application(s) accessed by the previous mobile device. This situation may result in a collision or mixing of the two respective application sessions of each mobile device. Traditional methods for avoiding or preventing these problems in current communications networks are complicated and require time/cost intensive changes or increased support by network gateways. Additionally, these traditional methods may increase delay {e.g., via data flowing between multiple gateways) and are not compliant with the European telecommunications standards institute ("ETSI") industry specification group ("ISG") requirements for emerging networks {e.g., 3GPP 5G architecture).

[0004] With reference to FIG. 1 , an example fifth generation ("5G") network architecture for access to two data networks is illustrated. This example 5G network architecture 100 includes mobile device(s) 102 connected with a data network 1 12 via a radio access network 104 and a local user plane function 106. The mobile device(s) are further connected with a data network 1 10 via a central user plane function 108 {e.g., network gateway). The 5G network architecture 100 may further include various functions and features such as an access and mobility management function 1 14 ("AMF"), an authentication server function 1 16 ("AUSF"), an unified data managements 1 18 ("UDM"), a session management function 120 ("SMF"), a policy control function 122 ("PCF"), and/or an application function ("AF") configured to facilitate communication on the network 100.

[0005] With reference to FIG. 2, an example 5G network architecture utilizing a multi- access edge computing device ("MEC Device") or multi-access edge host ("ME Host") 200 is illustrated. This example 5G network architecture 200 includes mobile device(s) 102 connected with a radio access network 104 ("(R)AN"), a local user plane function 106, and a central user plane function 108. Similar to the network of FIG. 1 , the 5G network architecture 200 may utilize an AMF 1 14, a SMF 120, and a policy control function 210 ("PCF") to facilitate various operations of communication on the network 200. As discussed in detail below with reference to FIG. 3, a MEC device 202 may be included in some 5G network architectures. However, the 5G network architectures illustrated in FIGS. 1 and 2 may suffer from application collision or mixing due to network gateway handover.

BRIEF SUMMARY

[0006] An apparatus, method, and computer program product are provided according to an example embodiment in order to maintain an application session via inter-gateway handover at a network's edge. An example embodiment of the disclosure provides an apparatus comprising at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to identify a mobile device connected to a network via a first gateway and cause one or more parameters identifying the mobile device to be stored. The one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway. The apparatus is caused to detect an application session of the mobile device on the bearer, cause the application session to be bound to the identity of the mobile device, and following a change in connection of the mobile device with the network from a first gateway to a second gateway, cause one or more updated parameters identifying the mobile device to be stored. The apparatus is caused to detect that the application session of the mobile device is ongoing, and apply one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

[0007] In one embodiment, the apparatus may be caused to determine if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway. In such an embodiment, the apparatus may be caused to, in response to determining that address translation is necessary, create the one or more policy rules for address translation. In some embodiments, the apparatus may be caused to apply the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application. In some further embodiments, the apparatus may be caused to apply the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application versions.

[0008] In some cases, the apparatus may cause the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and cause the another mobile device to be assigned the first internet protocol address upon connection to the first gateway. In such an embodiment, the apparatus may apply the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

[0009] In any of the above embodiments, the apparatus may limit the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.

[0010] A method is provided in accordance with another embodiment in which the method includes identifying a mobile device connected to a network via a first gateway and causing one or more parameters identifying the mobile device to be stored. The one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway. The method includes detecting an application session of the mobile device on the bearer, causing the application session to be bound to the identity of the mobile device, and following a change in connection of the mobile device with the network from a first gateway to a second gateway, causing one or more updated parameters identifying the mobile device to be stored. The method includes detecting that the application session of the mobile device is ongoing, and applying one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

[0011] In one embodiment, the method may include determining if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway. In such an embodiment, in response to determining that address translation is necessary, the method may include creating the one or more policy rules for address translation. In some embodiments, the method may include applying the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application. In some further embodiments, the method may include applying the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application versions.

[0012] In some cases, the method may include causing the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and cause the another mobile device to be assigned the first internet protocol address upon connection to the first gateway. In such an embodiment, method may apply the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

[0013] In any of the above embodiments, the method may include limiting the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.

[0014] In a further embodiment, a computer program is provided that includes at least one non-transitory computer-readable storage medium having computer-executable program code stored therein with the computer-executable program code including program code instructions configured to identify a mobile device connected to a network via a first gateway and cause one or more parameters identifying the mobile device to be stored, wherein the one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway. The computer executable program code may also include program code instructions configured to detect an application session of the mobile device on the bearer, cause the application session to be bound to the identity of the mobile device, and following a change in connection of the mobile device with the network from a first gateway to a second gateway, cause one or more updated parameters identifying the mobile device to be stored. The computer executable program code may also include program code instructions configured to detect that the application session of the mobile device is ongoing, and apply one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

[0015] In one embodiment, the computer executable program code may also include program code instructions configured to determine if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway. In such an embodiment, the computer executable program code may also include program code instructions configured to, in response to determining that address translation is necessary, create the one or more policy rules for address translation. In some embodiments, the computer executable program code may also include program code instructions configured to apply the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application. In some further embodiments, the computer executable program code may also include program code instructions configured to apply the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application versions.

[0016] In some cases, the computer executable program code may also include program code instructions configured to cause the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and cause the another mobile device to be assigned the first internet protocol address upon connection to the first gateway. In such an embodiment, the computer executable program code may also include program code instructions configured to apply the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

[0017] In any of the above embodiments, the computer executable program code may also include program code instructions configured to limit the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.

[0018] In yet another embodiment, an apparatus is provided that includes means for identifying a mobile device connected to a network via a first gateway and means for causing one or more parameters identifying the mobile device to be stored. The one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway. The apparatus further include means for detecting an application session of the mobile device on the bearer, means for causing the application session to be bound to the identity of the mobile device, and means for, following a change in connection of the mobile device with the network from a first gateway to a second gateway, causing one or more updated parameters identifying the mobile device to be stored. The apparatus includes means for detecting that the application session of the mobile device is ongoing, and means for applying one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

[0019] In one embodiment, the apparatus may include means for determining if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway. In such an embodiment, in response to determining that address translation is necessary, the apparatus may include means for creating the one or more policy rules for address translation. In some embodiments, the apparatus may include means for applying the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application. In some further embodiments, the apparatus may include means for applying the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application versions.

[0020] In some cases, the apparatus may include means for causing the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and means for causing the another mobile device to be assigned the first internet protocol address upon connection to the first gateway. In such an embodiment, apparatus may include means for applying the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

[0021] In any of the above embodiments, the apparatus may include means for limiting the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover. BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0022] Having thus described certain embodiments of the disclosure in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0023] FIG. 1 shows an example block diagram of a 5G network architecture for concurrent access to two data networks;

[0024] FIG. 2 shows an example block diagram of a 5G network architecture utilizing a MEC Host;

[0025] FIG. 3 shows an example block diagram of a network architecture that may be specifically configured, according to an example embodiment of the present disclosure;

[0026] FIG. 4 shows a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present disclosure;

[0027] FIG. 5 shows a flowchart illustrating operations performed, such as by the apparatus of FIG. 4, in accordance with an example embodiment of the present disclosure; and

[0028] FIG. 6 shows a data flow diagram showing an example process performed in accordance with some example embodiments of the present disclosure. DETAILED DESCRIPTION OF THE DRAWINGS

[0029] Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the description may refer to an "apparatus." However, elements of the apparatus described herein may be equally applicable to the claimed method and computer program product. In any embodiment of the present disclosure, a "gateway" or "network gateway" may equally encompass a "user plane function" and may be used interchangeably to describe a piece of networking equipment configured to connect or otherwise interface, directly or indirectly, a mobile device {e.g., user equipment) with a network (e.g., core network, data network, or the like). Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention. Definition of Terms

[0030] Certain terms used in connection with embodiments described herein are defined below.

[0031] As used herein, the terms "data," "content," "services," "information," and similar terms may be used interchangeably to refer to information capable of being transmitted, received, and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention. Further, where a computing device/server is described herein to receive data from another computing device/server, it will be appreciated that the data may be received directly from the another computing device, or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like, sometimes referred to herein as a "network." Similarly, where a computing device/server is described herein to send data to another computing device/server, it will be appreciated that the data may be sent directly to the another computing device or may be sent indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like.

[0032] As used herein, the terms "application," "mobile application," "mobile

app," "software application," and "application session" refer to computer-executable application software programmed to or capable of running on a processing unit of a server, computing device mobile device, or the like. Example software applications may include word processors, email, calendars, shared workspaces, issue tracking, software development tools, enterprise wiki collaboration, project management, code hosting, service desks, status monitoring pages, internet browsers, collaborative spaces, text/voice/video chat, sign on identity, bug reporting, and the like. An application session may, in particular, refer to a semi-permanent interactive information exchange or dialogue between two devices {e.g., a mobile device and a network).

[0033] As used herein, the term "user profile," "device profile," and "profile" refer to a collection of preferences, settings, configurations, mobile device identifiers, data, and information associated with a specific user equipment or mobile device. A user profile refers therefore to the explicit digital representation of a mobile device's identity and other data or information associated with the mobile device. A user profile configured in accordance with the present disclosure is accessible by one or more of the software applications that are supported by the mobile device or server, and, thus, may include application-specific preferences, settings, configurations, data, and information. [0034] As used herein, the terms "mobile computing device," "mobile device," and "user equipment ("UE")" (which may be used interchangeably) refer to computer hardware and/or software that is configured to access a service made available by a server and, among various other functions, is configured to communicate or otherwise request data from the server. Example mobile devices may include a smartphone, a tablet computer, a laptop computer, a wearable device, and the like. In other embodiments, a mobile device may include a "smart device" that is equipped with chip of other electronic device that is configured to communicate with the server via Bluetooth, near field communication (NFC), Wi-Fi, third generation (3G), fourth generation (4G), fifth generation (5G), radio frequency identification (RFID) protocols, and the like. In one example, a mobile device may include an object that is equipped with a Wi-Fi radio that is configured to

communicate with a Wi-Fi access point that is communicably connected with a server.

[0035] As defined herein, a "computer-readable storage medium," which refers to a non- transitory physical storage medium (e.g., volatile or non-volatile memory device), can be differentiated from a "computer-readable transmission medium," which refers to an electromagnetic signal.

[0036] Additionally, as used herein, the term 'circuitry' refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. This definition of 'circuitry' applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.

An Example System Architecture

[0037] An apparatus, method, and computer program product are provided to facilitate application sessions during inter-gateway handover at a network edge. Multi-access edge computing ("MEC), also known as mobile-edge computing, provides for content to be rapidly processed at the edge of a mobile network. As such, application developers, content providers and others can enjoy cloud-computing capabilities with ultra-low latency and high bandwidth as well as real time access to radio network information that may be leveraged by various MEC applications. MEC may be utilized by a variety of applications including video analytic applications, location service applications, Internet of Things (loT) applications, augmented reality applications, optimized local content distribution applications and data caching applications. A MEC device, as described herein, may provide lower latency, dynamic service/application offering, and higher performance to a communications network. Additionally, the utilization of a MEC device, as described in conjunction with the processes and method discussed herein, may facilitate maintaining application sessions during a gateway handover process. Further, at least certain embodiments described herein may be configured for preventing "UE IP address change" issues as described in GR MEC-0018 (an excerpt from MEC-0018) provided by the ETSI ISG requirements for 3GPP 5G architecture.

[0038] With reference to FIG. 3, an example communication network 300 is illustrated which may be used to perform some or all of the methods, processes, etc. as described herein for facilitating application sessions due to handover at a network edge. Although the network may be configured in different manners, the network 300 of an example embodiment comprises a multi-access edge computing ("MEC") device 202 (e.g., a MEC server), a mobile device 301 , a first access network 302, a first gateway ("GW-1 ") 304, a second access network 308, a second gateway ("GW-2") 310, and a network 306. The MEC device 202 may, in some embodiments, comprise a forwarding plane 206, one or more applications ("Appl") 208, and a multi-access edge ("ME") platform 204. In describing the processes, methods, and the like which are configured facilitate application sessions during handover (e.g., between GW-1 and GW-2 for example) at a network edge, the present disclosure may describe these processes, methods, and the like with reference to the MEC device 202 as the apparatus (e.g., apparatus 400 in FIG. 4) performing some or all of the operations herein. However, the present disclosure contemplates that this functionality may equally be performed in whole or part by the mobile device 301 , access networks (e.g., first access network 302 or second access network 308), and/or gateways (e.g., first gateway 304 or second gateway 31 0).

[0039] The MEC device 202 may include circuitry, networked processors, or the like (e.g., as seen in FIG. 4) configured to perform some or all of processes described herein, and may be any suitable network server and/or other type of processing device. In some embodiments, MEC device 202 may function as a "cloud" with respect to the network 1 00. In that sense, the MEC device 202 may include several servers performing interconnected and/or distributed functions. To avoid unnecessarily overcomplicating the disclosure, the MEC device 202 is shown and described herein as a single server. In some embodiments, the MEC device 202 may further define one or more applications 208 and a ME platform 204 hosted and/or stored by the MEC device 202. As described below in detail, the one or more applications 208 and the ME platform 204 may correspond to services, applications, and/or data requested by one or more mobile devices 301 communicably connected with the MEC device 202. Although described herein as a "server," the present disclosure contemplates that the MEC device 202 may be broadly encompassed by any computing device.

[0040] The network 100 may be configured in some embodiments, as seen in FIG. 3, such that mobile device 301 may be communicably connected with the MEC device 202 and network 306 via a first access network 302 and a GW-1 304. The first access network 302 may include one or more wired and/or wireless communication networks including, for example, a wired or wireless local area network (LAN), personal area network (PAN), metropolitan area network (MAN), wide area network (WAN), or the like, as well as any hardware, software and/or firmware for implementing the one or more networks {e.g., network routers, switches, hubs, etc.). For example, the first access network 302 may include a cellular telephone, mobile broadband, long term evolution (LTE), a global system for mobile communications (GSM)/enhanced data GSM environment (EDGE), a universal mobile telecommunications system (UMTS)/a highspeed packet access (HSPA), Institute of Electrical and Electronics Engineers (IEEE) 802.1 1 , IEEE 802.16, IEEE 802.20, Wi-Fi, dial-up, and/or a world interoperability for microwave access (WiMAX) network. Furthermore, the first access network 302 may include a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to transmission control protocol (TCP)/internet protocol (IP) based networking protocols.

[0041] The first gateway ("GW-1 ") 304 {e.g., a user plane function, "UPF," or the like) may be configured to connect the mobile device 301 with the MEC Device 202 and network 306 {e.g., core network, central network, or the like). The GW-1 may operate to route, switch, monitor, or otherwise facilitate communication between the first access network 302 and a network 306. Additionally, the GW-1 304 may be associated with a particular coverage area, node, beacon, or the like. By way of example, the GW-1 304 may be configured to facilitate connection of a mobile device located within a certain proximity or coverage area of the GW-1 304. As would be understood by one of ordinary skill in the art in light of the present disclosure, a network architecture {e.g., network 300 in FIG. 3) may include any number of access networks, gateways, beacons, nodes, or the like which may be configured to facilitate connection of a mobile device with a network. Furthermore, this plurality of access networks, gateways, beacons, nodes, or the like may be configured such that each gateway, for example, may be assigned a particular coverage area or configured to be communicably connected with only mobile devices located within its coverage area. Still further, when a mobile device leaves a coverage area defined by a first gateway {e.g., GW-1 304 in FIG. 3) and enters a coverage area defined by a second gateway {e.g., GW-2 310 in FIG. 3) the network may be configured to maintain a connection between the mobile device 301 and the network 306 or the MEC device 202 via an handover process at a network gateway {e.g., inter-gateway handover).

[0042] Similar to the GW-1 304 and first access network 302 described above, the second access network 308 and second gateway (GW-2) 310 may be configured to connect the mobile device 301 with the MEC Device 202 and network 306 {e.g., core network, central network, or the like). The GW-2 310 may operate to route, switch, monitor, or otherwise facilitate communication between the second access network 308 and a network 306. Additionally, the GW-2 310 may be associated with a particular coverage area, node, beacon, or the like, which may be distinct from the coverage area of GW-1 302 or may coincide with portions of the coverage area of GW-1 302.

[0043] In some embodiments, a mobile device 301 may be associated with a user profile. Although described in reference to a single mobile device 301 , the present disclosure contemplates that any number of mobile devices may be associated with various other user profiles or identifying information {e.g., IMS I). Additionally, the present disclosure contemplates that the MEC device 102 {e.g., and network 300) may be communicably connected to any number of mobile devices located within or proximate the coverage area of the network 300.

[0044] In some embodiments, the MEC device 202 may include a forwarding plane 206 {e.g., data plane ("DP"), etc.). In such an embodiment, the forwarding plane 206 may be communicably connected with the GW-1 304 and GW-2 310. The forwarding plane 206 may be configured to monitor a data flow transmitted over the network 300. By way of example, the forwarding plane 206 may receive data {e.g., a request for services, applications, and/or data) from the mobile device 104 and may determine that the MEC device 202 cannot serve or otherwise fulfil the request and, as such, may forward the request.

[0045] A network 306 {e.g., core network, central network, etc.) may comprise the highly functional communication facilities that interconnect primary nodes of access networks. The network 306 may further be configured to route or exchange data among various sub-networks. The network 306 may be any suitable core network structure such as an evolved packet core (EPC) network, a general packet radio system (GPRS) core network, or the like. The core network gateway 306 may further be configured to receive a request for services, applications, and/or data from the MEC device 202. In such an embodiment, the MEC Device 202 may be communicably connected directly with the network 306.

[0046] Regardless of the type of device that embodies the MEC device 202, the MEC 202 may include or be associated with an apparatus 400 as shown in FIG. 4. In this regard, the apparatus 400 may include or otherwise be in communication with a processor 402, a memory device 404, a communication interface 406, and/or a user interface 408. As such, in some embodiments, although devices or elements are shown as being in communication with each other, hereinafter such devices or elements should be considered to be capable of being embodied within the same device or element and thus, devices or elements shown in communication should be understood to alternatively be portions of the same device or element. Furthermore, the apparatus 400 may be encompassed, in whole or in part, by any of the elements of network 300 as shown in FIG. 3.

[0047] In some embodiments, the processor 402 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 404 via a bus for passing information among components of the apparatus. The memory device may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor). The memory device 404 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus 400 to carry out various functions in accordance with an example embodiment of the present invention. In this regard, the memory device 404 may store the applications 208 in FIG. 3. For example, the memory device 404 could be configured to buffer input data for processing by the processor 402. Additionally or alternatively, the memory device 404 could be configured to store instructions for execution by the processor 402.

[0048] As noted above, the apparatus 400 may be embodied by a MEC device 202 configured to be utilized in an example embodiment of the present invention. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus 400 may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a

baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus 400 may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single "system on a chip." As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein. As described above, although reference is made herein to a MEC device 202 which performs some or all of the steps of the present disclosure, the present disclosure contemplates that this functionality may equally be performed in whole or part by the mobile device 301 , access networks {e.g., first access network 302 or second access network 308), and/or gateways {e.g., first gateway 304 or second gateway 310).

[0049] The processor 402 may be embodied in a number of different ways. For example, the processor 402 may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an ASIC

(application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor 402 may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor 402 may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.

[0050] In an example embodiment, the processor 402 may be configured to execute instructions stored in the memory device 404 or otherwise accessible to the processor 402. Alternatively or additionally, the processor 402 may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 402 may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly. Thus, for example, when the processor 402 is embodied as an ASIC, FPGA or the like, the processor 402 may be specifically configured hardware for conducting the operations described herein.

Alternatively, as another example, when the processor 402 is embodied as an executor of software instructions, the instructions may specifically configure the processor 402 to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor 402 may be a processor 402 of a specific device (e.g., a MEC device, such as the ME platform 204, and/or the forwarding plane 206 as shown in FIG. 3) configured to be employed by an embodiment of the present invention by further configuration of the processor 402 by instructions for performing the algorithms and/or operations described herein. The processor 402 may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.

[0051] Meanwhile, the communication interface 406 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data between computing devices and/or servers {e.g., the MEC device 202 and first gateway 304 in FIG. 3 and, more particularly, the forwarding plane 206). In this regard, the communication interface 406 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications wirelessly. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause

transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). For example, the communication interface 406 may be configured to communicate wirelessly with the one or more mobile devices, such as via Wi-Fi,

Bluetooth or other wireless communications techniques. In some instances, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface 406 may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. For example, the communication interface 406 may be configured to communicate via wired

communication with other components of the computing device.

[0052] In some embodiments, the apparatus 400 may optionally include a user interface 408 in communication with the processor 402, such as by the user interface circuitry, to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. As such, the user interface 408 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms. The user interface may also be in communication with the memory 404 and/or the communication interface 406, such as via a bus.

[0053] The method, apparatus 400, and computer program product of an example embodiment will now be described in conjunction with the operations illustrated in FIGS. 5-6. With reference to FIG. 5, a flowchart is provided that illustrates a method 500 for facilitating handover at a network edge for use with some embodiments, described herein. The method 500 may include identifying a mobile device connected to a network via a first gateway at Block 502. As described above with reference to FIG. 3, the apparatus 400 may include means, such as the processor 402, the communications interface 406 or the like, for identifying a mobile device 301 connected to a network. By way of example, a mobile device 301 may be assigned various parameters such as a user identity ("IMS I"), a bearer (e.g., tunnel) identify ("TEID-1 "), and/or an IP address ("IP Addr-1 ") when connected to a first access network 302 and GW-1 304. These parameters, and any dependencies, may identify the mobile device 301 to the network 306 or the MEC device 202.

[0054] Following identifying the mobile device 301 , the apparatus 400 may include means, such as the processor 402, the memory 404 or the like, for causing one or more parameters identifying the mobile device 301 to be stored. The one or more parameters include an identity {e.g., IMSI or IP Addr-1 ) of the mobile device 301 and an identity of a bearer (e.g., TEID-1 ) supported by the first gateway 304 at Block 504. By way of example, the apparatus 400 (e.g., MEC device 202 in FIG. 3) may identify that a mobile device 301 has connected to the network 306 or the MEC device 202 via the first access network 302 and GW-1 304. This identification may be made due to a request by the mobile device to access an application (e.g., application(s) 208 in FIG. 3). This identification of the mobile device 301 may include causing one or more parameters identifying the mobile device to be stored such that the apparatus 400 may, specifically at a later point in time, identify the mobile device 301 .

[0055] Upon storage of the one or more parameters identifying the mobile device at Block 504, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for detecting an application session of the mobile device 301 on the bearer at Block 506 and causing the application session to be bound to the identity of the mobile device 301 at Block 508. By way of example, the apparatus 400 may detect that the mobile device 301 has requested an application or application session hosted by the network 306 or MEC device 202. The apparatus 400 may associate or otherwise bind the previously stored one or more parameters identifying the mobile device 301 (e.g., at Block 504) with the application session of the mobile device 301 . In some embodiments, the apparatus 400 may not detect an application session of the mobile device 301 by an active request of the mobile device 301 , but may instead detect an ongoing application session of the mobile device 301 . By way of example, a mobile device 301 may be accessing an application or communicating with a network 306 via an application session when the mobile device 301 enters a coverage area of the GW-1 304. The GW-1 304 may detect this application session, and may, upon identifying and storing one or more parameters of the mobile device 301 at Blocks 502, 504, bind the application session with the IP Addr-1 and/or IMSI-1 of the mobile device 301 . [0056] Following a change in connection of the mobile device with the network from a first gateway to a second gateway, the apparatus 400 may include means, such as the processor 402, the memory 404, or the like, for causing one or more updated parameters identifying the mobile device to be stored at Block 510. By way of example, the mobile device 301 may change its connection with the network 306 or the MEC device 202 from the GW-1 304 to GW-2 31 0. By way of example, the mobile device 301 may be connected with the network 306 or the MEC device 202 via the first access network 302 and the GW-1 304 while located in a coverage region of the GW-1 304. In an instance in which the mobile device 301 is no longer located within the coverage region(s) of GW-1 304 (e.g., the context between mobile device 301 and GW-1 304 is terminated), or that the network (e.g., via MEC device 202 or any other computing device) determines that the mobile device 301 may be more properly connected with the network 306 or the MEC device 202 via a new gateway, the mobile device 301 may change connection from the GW-1 304 to the GW-2 31 0. In some embodiments, the change of connection of the mobile device 301 with the network 306 or the MEC device 202 via the GW-2 31 0, and associated second access network 308, may result in updated parameters identifying the mobile device. By way of example, a mobile device 301 may be assigned various updated parameters such as a bearer (e.g., tunnel) identify ("TEID-2"), and/or an IP address ("IP Addr-2") when connected to a second access network 308 and GW-2 31 0.

[0057] Upon storage of the one or more updated parameters identifying the mobile device at Block 510, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for detecting that the application session of the mobile device 301 is ongoing at Block 512. As above at Block 506, the apparatus 400 may detect that the mobile device 301 is currently accessing an application session or that an application session is ongoing when the mobile device 301 connects to the network 306 or the MEC device 202 via the GW-2 310. By way of example, the mobile device 31 0 may, in some circumstances, be traveling in a vehicle such that the mobile device periodically transitions from a current gateway's coverage area to a subsequent gateway's coverage area. However, the mobile device 301 may, throughout this change in location, continually access an application or maintain an application session hosted by the network 306 or the MEC device 202. Upon this change in connection of the mobile device 301 with the network 306 or the MEC device 202, the apparatus 400 may, upon detecting the ongoing application session of the mobile device at Block 51 2, identify the one or more parameters (e.g., TEID-1 and IP Addr-1 ) stored at Block 504 which are bound to the application session (e.g., at Block 508). The apparatus 400 may further identify that the stored one or more parameters identifying the mobile device 301 and the one or more updated parameters identifying the mobile device 301 do not match. By way of a more particular example, the mobile device 301 may have a first IP address when utilizing the GW-1 304 to connect with the network 306 or the MEC device 202, and may have a second IP address when utilizing the GW-2 310 to connect with the network 306 or the MEC device 202.

[0058] In some embodiments, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for determining if address translation is necessary to maintain the application session of the mobile device 301 following connection to the second gateway (GW-2 310). This determination may, in some embodiments, occur in an instance in which the apparatus 400 identifies multiple IP addresses utilized by the mobile device 301 to access an application session (e.g., IP Addr-1 and IP Addr-2). In response to determining that address translation is necessary, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for creating one or more policy rules for address translation. By way of example, the apparatus 400 may apply a network address translation ("NAT") method in order to remap the IP address associated with the first gateway (IP Addr-1 ) to the subsequent IP address associated with the second gateway (IP Addr-2). Such a NAT method may modify network address information in IP address data packets while traveling between elements of the network 300. Although described in reference to a NAT method, the present disclosure contemplates that any suitable translation protocol or method for IP addresses may be utilized in the embodiments described herein.

[0059] As would be understood by one of ordinary skill in the art in light of the present disclosure, in some instances, such as when the context between the mobile device 301 and GW-1 304 is terminated {e.g., via a change in location of the mobile device 301 or the like), the network may assign the previously used IP address of the mobile device 301 (IP Addr-1 ) to another mobile device connected to the network via the GW-1 304. In some instances, the another mobile device (or any number of additional mobile devices) may access the same application as the mobile device (now connected to the network 306 or the MEC device 202 via GW-2 310). This situation may result in collision or mixing of respective application sessions of the mobile device 301 and the another mobile device.

[0060] Subsequently, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for applying one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway at Block 514. As discussed below in further detail, the one or more policy rules instituted by the apparatus 400 may {e.g., MEC device 202) may include application manipulation, routing changes, and the like, to avoid or prevent this collision and/or mixing of application sessions.

[0061] In some embodiments, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for applying the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application. By way of example, the apparatus 400 may determine that, when the mobile device 301 is accessing an ongoing application session via GW-2 310, another mobile device attempts to access the same application. In such an embodiment, the apparatus 400 may recognize this second instance of the application session and may route the second application session of the another mobile device to a separate instance of the application or to a separate entity of an application. Such a policy rule may facilitate the mobile device's 301 uninterrupted application session.

[0062] In some other embodiments, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for applying the one or more policy rules by separating the application session of the mobile device 301 from an application session of the another mobile device based upon one or more parameters identifying the respective application versions. As described in detail above at Blocks 504, 510, the apparatus 400 may store one or more parameters and updated parameters identifying the mobile device 301 . Upon identifying another mobile device accessing the same application and utilizing IP Addr-1 , the apparatus 400 may utilize the stored parameter(s) identifying the mobile device 301 {e.g., collected via connection to the network 306 or the MEC device 202 by GW-1 304 and GW-2 310) to separate the ongoing application session of the mobile device 301 from the application session of the another mobile device. In some embodiments, session identifiers and/or user identifiers may be used to facilitate identification of each respective application session and the associated mobile device. Further, any parameter of the application session(s) and/or mobile device(s) known by the apparatus 400 may be used for separating respective application sessions.

[0063] In some further embodiments, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for applying the one or more policy rules by preventing use of the first internet protocol address by the first gateway 304 with another mobile device until the application session of the mobile device 301 is terminated. By way of example, the apparatus 400 may identify and store one or more parameters identifying the mobile device 301 at Blocks 502, 504, including a first IP address (IP Addr-1 ). The apparatus 400 may be configured in some embodiments to hold, reserve, or otherwise prevent IP Addr-1 from being utilized by another mobile device that connects to the network 306 or the MEC device 202 via the GW-1 304. In such an embodiment, the apparatus may prevent collision or mixing of application sessions as only the mobile device 301 will be assigned the IP Addr-1 while the application session is ongoing.

[0064] In any of the embodiments described herein, the apparatus 400 may include means, such as the processor 402, the communication interface 406, or the like, for limiting the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover. By way of example, the apparatus 400 may be configured, via administrative configuration or via automatic detection, to recognize that multiple gateways and/or user plane functions are present in the network 306. In such an embodiment, the apparatus 400 may further be configured to limit, via the MEC device 202 or forwarding plane 206 {e.g., data plane), any of the methods or processes described above only to connections to the network 306 or the MEC device 202 made via gateways and/or user plane functions capable of performing the methods described herein.

[0065] As described above, the apparatus of an example embodiment therefore facilitates the efficient and timely provision of services, applications or data to a user of a mobile device, and is configured to prevent collision or mixing of application sessions between various mobile devices. In this regard, the apparatus is configured to apply policy rules such that when the mobile device that was previously served by a prior gateway connects with a subsequent gateway, connection of another mobile device to the prior gateway does not interrupt the application session of the mobile device. Thus, users and mobiles devices may experience enhanced application service, particularly when located at a network edge, and network utilization and overall service are correspondingly improved.

[0066] With reference to FIG. 6, a data flow diagram is provided that illustrates an example process performed in accordance with some example embodiments of the present disclosure. At operation 602, UE 301 {e.g., mobile device 301 in FIG. 3) sends an attach request to GW-1 304. The attach request comprises one or more UE 301 related parameters. At operation 604, GW-1 304 provides the attached request to MEC, particularly DP 206 {e.g., data plane or forwarding plane 206 in FIG. 3) with the UE 301 related parameters {e.g., IP Addr-1 , IMS I, TEID-1 ). At operation 606, DP 206 stores the one or more parameters and their dependencies, and at operation 608, UE 301 starts an application session.

[0067] At operation 610, DP 206 detects the start of an application session upon the bearer of GW-1 304 (TEID-1 ). Based on the TEID-1 , DP 206 is able to bind the session to a given IMS I and UE 301 . The DP 206 then determines whether there is already a session with the same application and IP Addr-1 but different IMSI, and, if yes, applies measures, such as described above, to avoid a collision or mixing of the two sessions. DP 206 may then store the application session status. At operation 612, the context between the UE 301 and GW-1 304 is terminated (e.g., when UE 301 is moving from the area of GW-1 304 to the area of GW-2 310). In some embodiments, operation 612 may occur following operation 614 described below.

[0068] At operation 614, UE 301 {e.g., mobile device 301 in FIG. 3) sends an attach request to GW-2 310. The attach request comprises one or more UE 301 related parameters. At operation 604, GW-2 310 provides the attach request to MEC, particularly DP 206 {e.g., data plane or forwarding plane 206 in FIG. 3) with the UE 301 related parameters {e.g., IP Addr-2, IMSI, TEID-2). At operation 616, DP 206 DP stores the one or more parameters and their dependencies and detects an ongoing application session bound to the IMSI. At operation 618, DP 206 determines if address translation is necessary for the application session due to the change in IP address (e.g., from IP Addr- 1 to IP Addr-2). The DP 206 creates one or more policy rules. At operation 620, the DP 206 applies the one or more policy rules to the data packets of the application.

[0069] As described above, FIGS. 5-6 illustrate a flowchart and a data flow diagram, respectively, of an apparatus 400, method, and computer program product according to example embodiments of the disclosure. It will be understood that each block of the flowchart and data flow diagram, and combinations of blocks in the flowchart and data flow diagram, may be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory 404 of an apparatus 400 employing an embodiment of the present invention and executed by a processor 402 of the apparatus. As will be appreciated, any such computer program instructions may be loaded onto a computer or other

programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer- readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart and data flow diagram blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart and data flow diagram blocks.

[0070] Accordingly, blocks of the flowchart and data flow diagram support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowchart and data flow diagram, and combinations of blocks in the flowchart and data flow diagram, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions. In some embodiments, certain ones of the operations above may be modified or further amplified. Furthermore, in some

embodiments, additional optional operations may be included. Modifications, additions, or amplifications to the operations above may be performed in any order and in any combination.

[0071] Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

THAT WHICH IS CLAIMED:

1 . An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:

identify a mobile device connected to a network via a first gateway;

cause one or more parameters identifying the mobile device to be stored, wherein the one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway;

detect an application session of the mobile device on the bearer;

cause the application session to be bound to the identity of the mobile device; following a change in connection of the mobile device with the network from a first gateway to a second gateway, cause one or more updated parameters identifying the mobile device to be stored;

detect that the application session of the mobile device is ongoing; and

apply one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

2. An apparatus according to Claim 1 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to determine if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway.

3. An apparatus according to Claim 2, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to, in response to determining that address translation is necessary, create the one or more policy rules for address translation.

4. An apparatus according to any one of Claims 1 to 3, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to apply the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application.

5. An apparatus according to any one of Claims 1 to 3, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to apply the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application sessions.

6. An apparatus according to any one of Claims 1 to 3, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to cause the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and cause the another mobile device to be assigned the first internet protocol address upon connection to the first gateway.

7. An apparatus according to Claim 6, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to apply the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

8. An apparatus according to any one of Claims 1 to 6, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to limit the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.

9. A method comprising:

identifying a mobile device connected to a network via a first gateway;

causing one or more parameters identifying the mobile device to be stored, wherein the one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway;

detecting an application session of the mobile device on the bearer;

causing the application session to be bound to the identity of the mobile device; following a change in connection of the mobile device with the network from a first gateway to a second gateway, causing one or more updated parameters identifying the mobile device to be stored;

detecting that the application session of the mobile device is ongoing; and applying one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

10. A method according to Claim 9, further comprising determining if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway.

1 1 . A method according to Claim 10, further comprising, in response to determining that address translation is necessary, creating the one or more policy rules for address translation.

12. A method according to any one of Claims 9 to 1 1 , further comprising applying the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application.

13. A method according to any one of Claims 9 to 1 1 , further comprising applying the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application sessions.

14. A method according to any one of Claims 9 to 1 1 , further comprising causing the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and causing the another mobile device to be assigned the first internet protocol address upon connection to the first gateway.

15. A method according to Claim 14, further comprising applying the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

16. A method according to any one of Claims 9 to 15, further comprising limiting the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.

17. A computer program product computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code stored therein, the computer-executable program code comprising program code instructions configured to:

identify a mobile device connected to a network via a first gateway;

detect an application session of the mobile device on the bearer;

detect that the application session of the mobile device is ongoing; and

18. A computer program product according to Claim 17, wherein the computer- executable program code further comprises program code instructions configured to determine if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway.

19. A computer program product according to Claim 18, wherein the computer- executable program code further comprises program code instructions configured to, in response to determining that address translation is necessary, create the one or more policy rules for address translation.

20. A computer program product according to any one of Claims 17 to 19, wherein the program code instructions configured to apply the one or more policy rules comprise program code instructions configured to route an application session of the another mobile device to a separate instance or entity of an application.

21 . A computer program product according to any one of Claims 17 to 19, wherein the program code instructions configured to apply the one or more policy rules comprise program code instructions configured to separate the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application sessions.

22. A computer program product according to any one of Claims 17 to 19, wherein the computer-executable program code further comprises program code instructions configured to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and cause the another mobile device to be assigned the first internet protocol address upon connection to the first gateway.

23. A computer program product according to Claim 22, wherein the program code instructions configured to apply the one or more policy rules comprise program code instructions configured to prevent use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

24. A computer program product according to any one of Claims 17-23, wherein the computer-executable program code further comprises program code instructions configured to limit the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.

25. An apparatus comprising at least:

means for identifying a mobile device connected to a network via a first gateway; means for causing one or more parameters identifying the mobile device to be stored, wherein the one or more parameters include an identity of the mobile device and an identity of a bearer supported by the first gateway;

means for detecting an application session of the mobile device on the bearer; means for causing the application session to be bound to the identity of the mobile device;

means for following a change in connection of the mobile device with the network from a first gateway to a second gateway, causing one or more updated parameters identifying the mobile device to be stored;

means for detecting that the application session of the mobile device is ongoing; and

means for applying one or more policy rules during the application session to avoid a collision or mixing of the application session with another mobile device that subsequently connects to the first gateway.

26. An apparatus according to Claim 25, further comprising means for determining if address translation is necessary to maintain the application session of the mobile device following connection to the second gateway.

27. An apparatus according to Claim 26, further comprising, in response to determining that address translation is necessary, means for creating the one or more policy rules for address translation.

28. An apparatus according to any one of Claims 25 to 27, further comprising means for applying the one or more policy rules by routing an application session of the another mobile device to a separate instance or entity of an application.

29. An apparatus according to any one of Claims 25 to 28, further comprising means for applying the one or more policy rules by separating the application session of the mobile device from an application session of the another mobile device based upon one or more parameters identifying the respective application sessions.

30. An apparatus according to any one of Claims 25 to 28, further comprising means for causing the mobile device to have a first internet protocol address while connected to the network via the first gateway, and a second internet protocol address while connected to the network via the second gateway and causing the another mobile device to be assigned the first internet protocol address upon connection to the first gateway.

31 . An apparatus according Claim 30, further comprising means for applying the one or more policy rules by preventing use of the first internet protocol address by the first gateway with the another mobile device until the application session of the mobile device is terminated.

32. An apparatus according to any one of Claims 25 to 31 , further comprising means for limiting the application of the one or more policy rules to application sessions established via a gateway that is known to support an inter-gateway handover.