COMPUTING

TECHNOLOGICAL FIELD

[0001] Embodiments of the present invention relate generally to facilitating user related information management in mobile edge computing.

BACKGROUND

[0002] During the use of conventional or current systems, some information that may be needed to be made available at the mobile edge computing (MEC) server serving the user/user equipment (UE), e.g. to the MEC platform or trusted or non-trusted applications, is often beyond the reach of the MEC server. That is, there are currently no mechanisms to access the information. Examples of such pieces of information are: the IP address allocated to the UE's IP context, subscriber related classification information, e.g., information about a group or groups the subscriber may belong to, location information of the user/UE.

[0003] Furthermore, while some information may change and require dynamic updating at the MEC server / platform, current system do no provide for the providing of updated information to the MEC server / platform. For example, this information may include: the UE IP address (which may change, for example, when the UE detaches from and later re- attaches to a network, or experiences (e.g., in a forthcoming / 5G network) an inter-GW handover), location information which may changes as the UE moves.

[0004] And still furthermore, because some information, and in particular, some user/UE related information may be released, (i.e. become unbound to the current user/UE), and be reused for/by, and may thus be bound to, another user, the use of current systems provide a risk of mixing confidential and trusted information, even sessions, of different users. An example of such information may be the IP address allocated to a user/UE upon attaching to a network, and released upon detaching from the network, and then later allocated to another user/UE attaching the network.

[0005] And still furthermore, current systems provide the new MEC server with the acquired and possibly outdated user/UE related information, when a UE experiences a handover from the area of a MEC server to the area of another MEC server.

[0006] In this regard, areas for improving known and existing systems have been identified. Through applied effort, ingenuity, and innovation, solutions to improve such systems have been realized and are described in connection with embodiments of the present invention.

BRIEF SUMMARY

[0007] European telecommunications standards institute (ETSI) Industry specification group (ISG) Mobile edge computing (MEC) is standardizing mobile edge computing. Potential standardized features / work items may comprise, for example, radio network information, location service and UE identity. Within each of these features / work items, information may be made available for the MEC server or platform per user or user equipment granularity. Accordingly, various methods, apparatuses and computer program products are therefore provided according to an example embodiment of the present invention for facilitating user related information management in mobile edge computing.

OVERVIEW

[0008] In some embodiments, a method may be provided, the method comprising receiving, at a mobile management entity, at least a first MEC server indication indicating presence of a first MEC server in a MME coverage area, the first MEC server having a first MEC server coverage area, receiving, at the mobile management entity, at least a first eNB indication, indicating presence of a first eNB in the MME coverage, detecting a handover of a user equipment (UE) between the first eNB and a second eNB, and determining whether the handover involves the second eNB being within the MME coverage area and within the first MEC server coverage; within the MME coverage area, outside of the first MEC server coverage area, and within a second MEC server coverage area- thus resulting in the UE being transferred to the second eNB; or outside of the MME coverage area.

[0009] In some embodiments, the method may further comprise, in an instance in which the second eNB is within the MME coverage area and within the first MEC server coverage area, facilitating the UE being transferred to the second eNB and same MEC server. In some embodiments, facilitating the UE being transferred to the second eNB and same MEC server comprises causing transmission of updated information, e.g. UE location information, to the MEC server.

[0010] In some embodiments, the method may further comprise, in an instance in which the second eNB is within the MME coverage area, outside of the first MEC server coverage area, facilitating the UE being transferred to the second eNB. In some embodiments, facilitating the UE being transferred to the second eNB comprises causing transmission of a whole set of information, with updates caused by the handover, to the new MEC server; informing previous or old MEC server about the handover and requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information.

[0011] In some embodiments, the method may further comprise, in an instance in which the second eNB is outside of the MME coverage area, facilitating the UE being transferred to a second MME coverage area. In some embodiments, facilitating the UE being transferred to a second MME coverage area comprises causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server.

[0012] In some embodiments, a plurality of options exist for which entity may transmit the whole set of information, or in some embodiments, portions thereof. That is, in some embodiments, causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server may be performed by the old MME. Additionally or alternatively, in some embodiments, transmission is performed by the new MME, in which case, the method may further comprise, causing transmission, from the old MME to the new MME, of the whole set of information with updates caused by the handover. And in yet other embodiments, transmission of the whole set of information is performed by a third network entity or function, the method may further comprise causing transmission, from the old MME to the third party entity of function, of the whole set of information with updates caused by the handover. And in yet one more embodiment, while transmission of the whole set of information may be, as described above, performed by a third network entity or function, the third party entity or function may receive the information from the old MME, via the new MME. As such, the method may further comprise causing transmission, from the old MME to the new MME or to the third party entity or function via the new MME, of the whole set of information with updates caused by the handover.

[0013] In some embodiments, in which the information is sent by the old MME, wherein when the old MME sends the information to the new MEC server, the configuration or awareness of the old MME shall cover also the new eNB versus a new MEC server relationship.

[0014] In some embodiments, the method may further comprise informing the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information. In some embodiments, the method may further comprise, when a UE detaches from a network, either intentionally or unintentionally, informing the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify, at least a portion of, the user/UE related information.

[0015] In some embodiments, an apparatus may be provided, the 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 processor, cause the apparatus to receiving, at a mobile management entity, at least a first MEC server indication indicating presence of a first MEC server in a MME coverage area, the first MEC server having a first MEC server coverage area, receiving, at the mobile management entity, at least a first eNB indication, indicating presence of a first eNB in the MME coverage, and detecting a handover of a user equipment (UE) between the first eNB and a second eNB, determining whether the handover involves the second eNB being within the MME coverage area and within the first MEC server coverage; within the MME coverage area, outside of the first MEC server coverage area, and within a second MEC server coverage area- thus resulting in the UE being transferred to the second eNB, or outside of the MME coverage area.

[0016] In some embodiments, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to, in an instance in which the second eNB is within the MME coverage area and within the first MEC server coverage area, facilitating the UE being transferred to the second eNB and same MEC server. In some embodiments, facilitating the UE being transferred to the second eNB and same MEC server comprises causing transmission of updated information, e.g. UE location information, to the MEC server.

[0017] In some embodiments, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to, in an instance in which the second eNB is within the MME coverage area and outside of the first MEC server coverage area, facilitate the UE being transferred to the second eNB. In some embodiments, facilitating the UE being transferred to the second eNB may comprise causing transmission of a whole set of information, with updates caused by the handover, to the new MEC server; informing previous or old MEC server about the handover and requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information

[0018] In some embodiments, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to, in an instance in which the second eNB is outside of the MME coverage area, facilitate the UE being transferred to a second MME coverage area. In some embodiments, facilitating the UE being transferred to a second MME coverage area comprises causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server.

[0019] In some embodiments, a plurality of options exist for which entity may transmit the whole set of information, or in some embodiments, portions thereof. That is, in some embodiments, causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server may be performed by the old MME. Additionally or alternatively, in some embodiments, transmission is performed by the new MME, in which case, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to transmit, from the old MME to the new MME, of the whole set of information with updates caused by the handover. And in yet other embodiments, transmission of the whole set of information is performed by a third network entity or function, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to transmit, from the old MME to the third party entity of function, of the whole set of information with updates caused by the handover. And in yet one more embodiment, while transmission of the whole set of information may be, as described above, performed by a third network entity or function, the third party entity or function may receive the information from the old MME, via the new MME. As such, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to transmit, from the old MME to the new MME or to the third party entity or function via the new MME, of the whole set of information with updates caused by the handover.

[0020] In some embodiments, in which the information is sent by the old MME, wherein when the old MME sends the information to the new MEC server, the configuration or awareness of the old MME shall cover also the new eNB versus a new MEC server relationship.

[0021] In some embodiments, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to inform the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information. In some embodiments, the apparatus may further comprise computer program code configured to, with the processor, cause the apparatus to, when a UE detaches from a network, either intentionally or unintentionally, inform the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify, at least a portion of, the user/UE related information. [0022] A computer program product comprising at least one non-transitory computer- readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for receiving, at a mobile management entity, at least a first MEC server indication indicating presence of a first MEC server in a MME coverage area, the first MEC server having a first MEC server coverage area, receiving, at the mobile management entity, at least a first eNB indication, indicating presence of a first eNB in the MME coverage, and detecting a handover of a user equipment (UE) between the first eNB and a second eNB, determining whether the handover involves the second eNB being within the MME coverage area and within the first MEC server coverage; within the MME coverage area, outside of the first MEC server coverage area, and within a second MEC server coverage area- thus resulting in the UE being transferred to the second eNB, or outside of the MME coverage area.

[0023] In some embodiments, the computer-executable program code instructions further comprise program code instructions for, in an instance in which the second eNB is within the MME coverage area and within the first MEC server coverage area, facilitating the UE being transferred to the second eNB and same MEC server. In some embodiments, facilitating the UE being transferred to the second eNB and same MEC server comprises causing transmission of updated information, e.g. UE location information, to the MEC server.

[0024] In some embodiments, the computer-executable program code instructions further comprise program code instructions for, in an instance in which the second eNB is within the MME coverage area, outside of the first MEC server coverage area, facilitating the UE being transferred to the second eNB. In some embodiments, facilitating the UE being transferred to the second eNB comprises causing transmission of a whole set of information, with updates caused by the handover, to the new MEC server; informing previous or old MEC server about the handover and requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information

[0025] In some embodiments, the computer-executable program code instructions further comprise program code instructions for, in an instance in which the second eNB is outside of the MME coverage area, facilitating the UE being transferred to a second MME coverage area. In some embodiments, facilitating the UE being transferred to a second MME coverage area comprises causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server. [0026] In some embodiments, a plurality of options exist for which entity may transmit the whole set of information, or in some embodiments, portions thereof. That is, in some embodiments, causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server may be performed by the old MME. Additionally or alternatively, in some embodiments, transmission is performed by the new MME, in which case, the computer-executable program code instructions further comprise program code instructions for causing transmission, from the old MME to the new MME, of the whole set of information with updates caused by the handover. And in yet other embodiments, transmission of the whole set of information is performed by a third network entity or function, the computer-executable program code instructions further comprise program code instructions for causing transmission, from the old MME to the third party entity of function, of the whole set of information with updates caused by the handover. And in yet one more embodiment, while transmission of the whole set of information may be, as described above, performed by a third network entity or function, the third party entity or function may receive the information from the old MME, via the new MME. As such, the computer-executable program code instructions further comprise program code instructions for causing transmission, from the old MME to the new MME or to the third party entity or function via the new MME, of the whole set of information with updates caused by the handover.

[0027] In some embodiments, in which the information is sent by the old MME, wherein when the old MME sends the information to the new MEC server, the configuration or awareness of the old MME shall cover also the new eNB versus a new MEC server relationship.

[0028]

[0029] In some embodiments, the computer-executable program code instructions further comprise program code instructions for informing the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information. In some embodiments, the computer- executable program code instructions further comprise program code instructions for, when a UE detaches from a network, either intentionally or unintentionally, informing the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify, at least a portion of, the user/UE related information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0031] Figure 1 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention;

[0032] Figure 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present invention;

[0033] Figure 3 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention;

[0034] Figures 4-8 are data flow diagrams showing exemplary processes performed in accordance with some example embodiments of the present invention;

[0035] Figures 9 and 10 are flowcharts showing exemplary methods of operating an example apparatus in accordance with exemplary embodiments of the present invention; and

[0036] Figure 11 is a block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention.

DETAILED DESCRIPTION

[0037] Some example embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments are shown. Indeed, the example embodiments may take 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. The terms "data," "content," "information," and similar terms may be used interchangeably, according to some example embodiments, to refer to data capable of being transmitted, received, operated on, and/or stored. Moreover, the term "exemplary", as may be used herein, is not provided to convey any qualitative assessment, but instead merely to convey an illustration of an example. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

[0038] As used herein, the term "circuitry" refers to all of the following: (a) hardware- only circuit implementations (such as implementations in only analog and/or digital circuitry); (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) to circuits, such as 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.

[0039] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term 'circuitry' would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or application specific integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or other network device.

System Architecture

[0040] Referring now to Figure 1, which illustrates an example system that supports communications between a plurality of stations 10 and one or more access points 12 (e.g., a high density system scenario where a plurality of access points may be deployed to a geographical area and may be operating on the same frequency channel), each access point may communicate with one or more stations and, in one embodiment, may communicate with a large number of stations, such as 6,000 or more stations. The access points may, in turn, communicate with a network 14. While the access points may communicate via an Long Term Evolution (LTE) or LTE-Advanced (LTE-A) network, other networks may support communications between the access points including those configured in accordance with wideband code division multiple access (W-CDMA), CDMA2000, global system for mobile communications (GSM), general packet radio service (GPRS), the IEEE 802.11 standard including, for example, the IEEE 802.11 ah or 802.1 lac standard or other newer amendments of the standard, wireless local access network (WLAN), Worldwide Interoperability for Microwave Access (WiMAX) protocols, universal mobile telecommunications systems (UMTS) terrestrial radio access network (UTRAN) and/or the like.

[0041] The access points 12 and the stations 10 may communicate via wireline communications, but most commonly communicate via wireless communications. For example, the access points and the stations may communicate in a sub 1 GHz band as defined by IEEE 802.11 ah standard or in a 5GHz band, which may be defined by, for example, IEEE 802.1 lac standard. The access point may be embodied by any of a variety of network entities, such as an access point, a base station, a Node B, an evolved Node B (eNB), a radio network controller (RNC), a mobile device / a station (e.g., mobile telephones, smart phones, portable digital assistants (PDAs), pagers, laptop computers, tablet computers or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof), or the like. The stations may also be embodied by a variety of devices, such as sensors, meters or the like. The sensors and meters may be deployed in a variety of different applications including in utility applications to serve as a gas meter, a water meter, a power meter or the like, in environmental and/or agricultural monitoring applications, in industrial process automation applications, in healthcare and fitness applications, in building automation and control applications and/or in temperature sensing applications. Stations that are embodied by sensors or meters may be utilized in some embodiments to backhaul sensor and meter data. Alternatively, the stations may be embodied by mobile terminals or user equipment(s) (UE), such as mobile communication devices, e.g., mobile telephones, smart phones, portable digital assistants (PDAs), pagers, laptop computers, tablet computers or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof. In an embodiment in which the station is embodied by a mobile terminal, the communication between an access point and the station may serve to extend the range of Wi-Fi or another wireless local area network (WLAN), such as by extending the range of a hotspot, and to offload traffic that otherwise would be carried by a cellular or other network.

[0042] The access point 12 and/or the station 10 may be embodied as or otherwise include an apparatus 20 that is specifically configured to perform the functions of the respective device, as generically represented by the block diagram of Figure 2. While the apparatus may be employed, for example, by an access point or a station, it should be noted that the components, devices or elements described below may not be mandatory and thus some may be omitted in certain embodiments. Additionally, some embodiments may include further or different components, devices or elements beyond those shown and described herein.

Apparatus Architecture

[0043] Regardless of the type of device that embodies the station 10, the station 10 may include or be associated with an apparatus 20 as shown in Figure 2. In this regard, the apparatus may include or otherwise be in communication with a processor 22, a memory device 24, a communication interface 26 and a user interface 28. 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.

[0044] In some embodiments, the processor 22 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 24 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 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus 20 to carry out various functions in accordance with an example embodiment of the present invention. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.

[0045] As noted above, the apparatus 20 may be embodied by a computing device 10 configured to employ 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 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 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.

[0046] The processor 22 may be embodied in a number of different ways. For example, the processor 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 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 may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.

[0047] In an example embodiment, the processor 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 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 is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device (e.g., a head mounted display) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor. In one embodiment, the processor may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface 28.

[0048] Meanwhile, the communication interface 26 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 the computing device 10 and a server 12.

In this regard, the communication interface 26 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 communications interface may be configured to communicate wirelessly with the head mounted displays 10, 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 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 may be configured to communicate via wired communication with other components of the computing device.

[0049] The user interface 28 may be in communication with the processor 22, such as 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 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. In some embodiments, a display may refer to display on a screen, on a wall, on glasses (e.g., near-eye-display), in the air, etc. The user interface may also be in communication with the memory 24 and/or the communication interface 26, such as via a bus. Architecture

[0050] Figure 3 is a block diagram of a system (e.g., an exemplary high level architecture 300) that may be specifically configured in accordance with an example embodiment of the present invention. Figure 3 shows an architecture with MEC servers 320 and 325 between eNBs 310 and 315 and MME/S/P-GW 330, 335, and 340. In some embodiments, MEC servers 320, 325 may reside behind the SGi interface 340. That is, the MME 330, S-GW 335 and P-GW 340 may reside between the eNBs 310, 315 and MEC server(s) 320, 325..

[0051] In some embodiments, use of MME 330 as a, for example, source of user/UE related information to be sent to a MEC server (e.g., one of 320 and/or 325) may provide one or more advantages. For example, MME 330 may be the first entity (seen from the UE towards the core network) that has access to the user/UE related information (IMSI vs. UE

IP address, location, subscription info and device info). The radio network / eNB may not be used as a source of such information, because, for example, some portion of required information per/versus IMSI may not be available at an eNB. That is, the MEC server /

RNIS at the MEC server shall get the information from somewhere else, e.g., from the core network. This is supported also by the MEC requirements specification, an excerpt from ETSI GS MEC 002 v.0.5.1 / A.17: "this information needs to be provided by an external source (e.g. in the core network)."

[0052] In some embodiments, information is transferred from MME to a MEC server via a third entity or function. An example of such an entity/function is SCEF (Service capability exposure function) in figure 11 , wherein an application represents a MEC server or a part of or a module in a MEC server.

[0053] Another advantage that may be provided by the system of Figure 3 and one or more operations described below is that the path of the information flow (measured in the number of entities on the path) may be the shortest compared to the paths with the alternative entities S/P-GW and PCRF that have access to the same information.

[0054] Another advantage that may be provided by the system of Figure 3 and one or more operations described below is that MME gets the location information / cell ID from the radio network whenever there is a change. Alternative solutions (S/P-GW, PCRF) have to subscribe to the location information from MME, and the provisioning of the subscribed location information causes extra message exchanges in the packet core network increasing message loading on the entities.

[0055] Another advantage that may be provided by the system of Figure 3 and one or more operations described below is that 3GPP has recently (in Rel-13) standardized "the procedures and the Nq and Nq' Application Protocol (Nq-AP) messages used on the Nq/Nq' interfaces between the RAN Congestion Awareness Function (RCAF) and the Mobility Management Entity (MME)", refer to 3GPP TS 29.405. In a similar way simple procedures and application protocol can be specified between MME and MEC server / RNIS for the MEC server / RNIS to get the required user/UE related information from the core network.

[0056] As such, the present disclosure provides a simple interface / application protocol between MME and RNIS / MEC server to, for example, solve the described information exchange problem. However, in the event that there may be an interface / application protocol between the core network PCRF and a (policy) control entity in the MEC server, the same interface could/should be considered for use in providing the MEC server with the user/UE related information, which may, for example, keep the number of new interfaces as low as possible. And further, instead of a direct interface, there may even be an intermediate element/entity between MME and the MEC server, or between MME, PCRF, P-GW, etc. and the MEC server, collecting information from MME and possible other entities and sends the information or part of it to the MEC server. [0057] Exemplary use case may comprise, for example, one or more of the three MEC features / work items currently under work in ETSI MEC standardization: Radio network information, Location service and UE identity, and the use case A.17 ("Mobile edge platform consuming information from operator trusted mobile edge application") in ETSI GS MEC 002 v.0.5.1 requirements specification.

Operation

[0058] In an example embodiment of the present invention, an apparatus or computer program product may be provided to implement or execute a method, process, or algorithm for facilitating user related information management at mobile edge.

[0059] Figures 4-10 show flowcharts of the exemplary operations performed by a method, apparatus and computer program product in accordance with an embodiment of the present invention. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device 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 26 of an apparatus employing an embodiment of the present invention and executed by a processor 24 in 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 provides for implementation of the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer-readable storage 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 storage memory produce an article of manufacture, the execution of which implements the function specified in the flowchart block(s). 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 block(s). As such, the operations of Figures 4-10 when executed, convert a computer or processing circuitry into a particular machine configured to perform an example embodiment of the present invention. Accordingly, the operations of Figures 4-10 define an algorithm for configuring a computer or processing to perform an example embodiment. In some cases, a general purpose computer may be provided with an instance of the processor which performs the algorithms of Figures 4-10 to transform the general purpose computer into a particular machine configured to perform an example embodiment.

[0060] Accordingly, blocks of the flowchart 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 flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware- based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

[0061] In some embodiments, certain ones of the operations herein may be modified or further amplified as described below. It should be appreciated that each of the modifications, optional additions or amplifications below may be included with the operations above either alone or in combination with any others among the features described herein.

[0062] Figure 4 shows a data flow diagram showing an exemplary process for facilitating a process, for example, when a UE attaches to a network and a MEC server is made aware of UE related parameters (e.g. UE IP address, UE location, etc.)..

[0063] At operation 405, UE 305 sends an attach request to eNB310, the attach request comprising one or more UE related parameters. At operation 410, eNB310 provides the attached request to MME 330 with the UE related parameters. At operation 415, MME 330 notes a target eNB and/or any other UE related information, and at operation 420, provides IMSI towards S/P-GW 335, 340. At operation 425, MME 330 may receive subscription information from HSS, and subsequently, at operation 430, transmit a create session request including, for example, IMSI to P-GW 340.

[0064] At operation 435, P-GW 340 may allocate an IP address to the new IP context of the UE 305, and at operation 440, provide a create session response, comprising, for example, IMSI, UE IP address, to MME 330. At operation 445, MME 330 may prepare to send and/or subsequently send UE/IMSI related parameters, e.g., IMSI, UE IP address, location information (e.g. cell ID) and/or subscription / group / classification info, to a MEC server to which the current eNB of the UE is connected. At operation 450, MME 330 may then save the UE IP address, for possible later use, e.g. upon handovers to update the new (to-be-handed-over-to) MEC server. [0065] At operation 455, MME 330 may provide or otherwise transmit a message to MEC server, comprising for example, IMSI, UE IP Address, Location info, Subscription/Group/Classification info, etc. At operation 460, MEC server may use the received information as per the various embodiments described below.

[0066] Figure 5 shows a data flow diagram showing an exemplary process for facilitating a hand over process between eNBs within the area of a MEC server. At operation 505, eNB 310 transmits a path switch request to the MME 330. At operation 510, MME 330 prepares to send UE related parameters, e.g., location information (e.g., cell ID) and/or user group identification information and/or user/UE classification information, to update the MEC server 320. At operation 515, MME 330 may transmit a message comprising, for example, [IMSI and/or UE IP Address), Location info, Subscription/Group/Classification info, ... ] to MEC server 320. At operation 520, MEC server 320 may be configured to utilize the received information as described here.

[0067] Figure 6 shows a data flow diagram showing an exemplary process for facilitating a hand over process between eNBs within the areas of different MEC servers. At operation 605, UE 305 may transmit a path switch request to MME 330. At operation 610, MME 330 notes that the new eNB is in the area of another MEC server. As shown in operation 615, MME 330 may then prepare to send and/or send UE related parameters (e.g., IMSI, UE IP address, location information (e.g., cell ID) and/or user group identification information and/or user/UE classification information), to the new MEC server. At operation 620, MME 330 may prepare to inform and/or inform the old MEC server about the UE leaving the area, e.g., to enable the MEC server to invalidate/nullify UE related information, e.g., the UE IP address.

[0068] At operation 625, MME 330 may then transmit message [(IMSI and/or UE IP Address), Location info, Subscription/Group/Classification info, ...] to the new MEC server

325. At operation 630, MEC server 325 may be configured to utilize the received information as described here. At operation 635, MME 330 may transmit message

[indication of UE leaving the area / request to nullify parameters] to the old MEC server 320.

At operation 640, the old MEC server 320 may invalidate/nullify parameters e.g. IP address, of the indicated user/UE.

[0069] Figure 7 shows a data flow diagram showing an exemplary process for facilitating a hand over process between eNBs where both the MEC server and MME change. At operation 705, eNB may provide an indication to MME 330, that a handover is required. In an instance in which it is determined that, for example, the UE is relocating to a coverage area of a second eNB covered by a new MEC server and new MME, as shown at operation 710, MME-old 330 may be configured to identify, transmit and/or forward the relocation request to a new MME, MME-new 330A. At operation 715, MME-old 330 notes that the new eNB is in the area of another MEC server, MEC-new 325. At operation 720, MME-old 330 prepares to inform the old MEC server 320 about the UE leaving the area, e.g. to enable the MEC server to invalidate/nullify UE related information, e.g. the UE IP address.

[0070] At operation 725, MME-new 330A may prepare to send UE related parameters, e.g. IMSI, UE IP address, location information (e.g. cell ID) and/or user group identification information and/or user/UE classification information, to the new MEC server 325.

[0071] At operation 730, new MME may transmit message [IMSI, UE IP Address), Location info, Subscription/Group/Classification info, ...] to the new MEC server 325. At operation 735, new MEC server 325 may use the received information as per the various embodiments described below. At operation 740, previous MME 330 may transit message [indication of UE leaving the area / request to nullify parameters] to the previous MEC server 320. At operation 745, the previous MEC server 320 may invalidate/nullify parameters e.g. IP address, of the indicated user/UE.

[0072] Figure 8 shows a data flow diagram showing an exemplary process in which UE detaches from a network and a MEC server is made aware of the event. At operation 805, UE 305 transmits detach request [parameters] to MME 330. That is the UE may detach from the network, intentionally or unintentionally. At operation 810, MME 330 transmits a delete session request to P-GW 340. At operation 815, MME 330 notes that a UE within the area of a MEC server is detaching / has detached from the network, meaning that at least some of the user/UE related parameters may become obsolete or invalid, such as for example, the IP address, which may be allocated to another UE later attaching the network. At operation 820, MME 330 prepares to inform the MEC server. At operation 825, MME 330 transmits message [indication of UE detaching/detached / request to nullify parameters]. At operation 830, MEC server 320 may invalidate/nullify parameters e.g., IP address, of the indicated user/UE.

Exemplary Operations

[0073] In some example embodiments, a method, apparatus and computer program product may be configured for handling user-related information at mobile edges when, for example, facilitating a handover of a UE from a first eNB to a second eNB. Figure 9 is a flowchart showing an exemplary method of operating an example apparatus in accordance with an embodiment of the present invention. Specifically, Figure 9 shows an exemplary embodiment of a process for facilitating a handover to a second eNB, and in particular, determining whether the handover involves the second eNB being (i) within the MME coverage area and within the first MEC server coverage area, (ii) within the MME coverage area, outside of the first MEC server coverage area, and within a second MEC server coverage area, or (iii) outside of the MME coverage area.

[0074] An MME is made aware (e.g. by the network management and/or through configurations) of MEC servers in its coverage area, and of eNBs in the coverage area of each MEC server. Consequently, the MME is able to detect, for example, if a handover of a UE takes place between eNBs in the area of the same MEC server (i.e. the MEC server serving the UE does not change upon the handover) or between eNBs that belong to the areas of different MEC servers (i.e. the MEC server serving the UE changes upon the handover). Accordingly, as shown in block 905 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to receive, at a mobile management entity, at least a first MEC server indication indicating presence of a first MEC server in a MME coverage area, the first MEC server having a first MEC server coverage area. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for receiving, at a mobile management entity, at least a first MEC server indication indicating presence of a first MEC server in a MME coverage area, the first MEC server having a first MEC server coverage area. And, as shown in block 910 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to receive, at the mobile management entity, at least a first eNB indication, indicating presence of a first eNB in the MME coverage area. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for receiving, at the mobile management entity, at least a first eNB indication, indicating presence of a first eNB in the MME coverage area.

[0075] Additionally, in some embodiments, the apparatus may be configured to receive, for example, a second MEC server indication indicating presence of a second MEC server in the MME coverage area, the second MEC server having a second MEC server coverage area, wherein the first MEC server coverage area and the second MEC server coverage area are within the MME coverage area. And in some embodiments, the apparatus may be configured to receive, a second eNB indication indicating presence of a second eNB in the MME coverage area. [0076] When a UE attaches the network, the MME may be configured to store any of user related information and/or user related parameters and/or UE related information and/or UE related parameters, for example, that may be required by a MEC server or application. Parameters may comprise any of, for example, the IP address allocated to the UE (e.g., by P-GW), the user location of the UE (e.g., in form of a cell ID), subscriber/subscription related information (which is available for MME e.g. from HSS) which may, for example, for privacy reasons be further classified or filtered. As such, as shown in block 915 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to detect a handover of a user equipment (UE) between the first eNB and a second eNB. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for detecting a handover of a user equipment (UE) between the first eNB and a second eNB.

[0077] Because the handover may include a second eNB, in for example, in a different coverage area, the MME 330 may be configured to determine whether the handover involves the second eNB being within the MME coverage area and within the first MEC server coverage area, resulting in, for example, the UE being transferred to the second eNB but remaining with same MEC server. The MME 330 may further be configured for determining whether the handover involves the second eNB being within the MME coverage area, but outside of the first MEC server coverage area and within a second MEC server coverage area, resulting in the UE being transferred to the second eNB and a second MEC server. The MME 330 may further be configured for determining whether the handover involves the second eNB being outside of the MME coverage area, resulting in, for example, the UE being transferred to a different MME.

[0078] As such, as shown in block 920 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to determine, for example, a hand over condition, the hand over condition being any of an indication of whether the handover involves the second eNB being (i) within the MME coverage area and within the first MEC server coverage area, (ii) within the MME coverage area, outside of the first MEC server coverage area, and within a second MEC server coverage area, or (iii) outside of the MME coverage area. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for determining whether the handover involves the second eNB being (i) within the MME coverage area and within the first MEC server coverage area, (ii) within the MME coverage area, outside of the first MEC server coverage area, and within a second MEC server coverage area, or (iii) outside of the MME coverage area.

[0079] In an instance in which the second eNB is within the MME coverage area and within the first MEC server coverage area, as shown in block 925 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to facilitate the UE being transferred to the second eNB. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for, in an instance in which the second eNB is within the MME coverage area and within the first MEC server coverage area, facilitating the UE being transferred to the second eNB and same MEC server.

[0080] Because the MEC server remains the same, only updated information may be required to be transferred. That is, in a handover between eNBs within the area of the same MEC server, MME may need to send updated information, e.g. UE location information, to the MEC server. As such, as shown in block 930 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission of updated information. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for, in an instance in which the second eNB is within the MME coverage area and within the first MEC server coverage area causing transmission of updated information to, for example, the first MEC server.

[0081] In an instance in which the second eNB is within the MME coverage area, and outside of the first MEC server coverage area, the MME 330 may be configured to facilitate the UE being transferred to the second eNB. As such, as shown in block 935 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to facilitate the UE being transferred to the second eNB. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for facilitating the UE being transferred to the second eNB.

[0082] Specifically, in a handover between eNBs within the areas of different MEC servers, MME 330 may need to send the whole set of information, with updates caused by the handover, to the new MEC server. MME may also inform the old MEC server about the handover/event and/or may request the old MEC server to invalidate/nullify (at least part of) the user/UE related information. As such, as shown in block 940 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission of a whole set of information, including any updated information or updates caused by the handover, to the new MEC server; informing previous or old MEC server about the handover. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for causing transmission of a whole set of information, including any updated information or updates caused by the handover, to the new MEC server; informing previous or old MEC server about the handover.

[0083] The MME 330 may also be configured for requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information. As such, as shown in block 950 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information. Similarly, when a UE detaches from a network, either intentionally or unintentionally, MME may be configured to inform the relevant MEC server about the event and/or may request the MEC server to invalidate/nullify (at least part of) the user/UE related information.

[0084] In an instance in which the second eNB is outside of the MME coverage area, the MME may be configured for facilitating the UE being transferred to a second MME coverage area. As such, as shown in block 955 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to facilitate the UE being transferred to a second MME coverage area. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for, in an instance in which the second eNB is outside of the MME coverage area, facilitating the UE being transferred to a second MME coverage area.

[0085] In a handover where both the MEC server and the MME change, MME may need to send the whole set of information, with updates caused by the handover, to the new MEC server. As such, as shown in block 960 of Figure 9, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission of the whole set of information, with updates caused by the handover, to the new MEC server. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server.

[0086] As described above, in a handover where both the MEC server and the MME change, MME may need to send the whole set of information, with updates caused by the handover, to the new MEC server. To do this, the information may be sent either by, for example, the new MME, the old MME, or in some embodiments, by a third party entity or function. In an instance in which the new MME sends the information to the new MEC server, the old MME may be configured to send, or have sent, the information to the new MME, for example, upon a handover message (e.g., Forward Relocation Request in 3GPP EPC).

[0087] If the old MME sends the information to the new MEC server, the configuration or awareness of the old MME shall cover also the new eNB vs. new MEC server relationship. MME may also inform the old MEC server about the handover/event and/or may request the old MEC server to invalidate/nullify (at least part of) the user/UE related information.

[0088] Figure 10 is a flowchart showing an exemplary method of operating an example apparatus in accordance with an embodiment of the present invention and, in particular shows an exemplary process for facilitating handover where information may be sent either by the new MME, the old MME, or a third party entity or function.

[0089] That is, in some embodiments, a plurality of options exist for which entity may transmit the whole set of information, or in some embodiments, portions thereof. That is, in some embodiments, causing transmission of the whole set of information, with updates caused by the handover, to the new MEC server may be performed by the old MME. Additionally or alternatively, in some embodiments, transmission may be performed by the new MME. And in yet other embodiments, transmission of the whole set of information is performed by a third network entity or function. As shown in block 1005 of Figure 10, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to determine whether information is and/or should be send by new MME, the old MME, or by a third party entity or function. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for determining whether information is and/or should be send by new MME, the old MME or by a third party entity or function.

[0090] In an instance in which it is determined that the old MME sends, will send, or should send the information to the new MEC server, the old MME may be configured to send the information to the new MME e.g. upon a handover message (e.g. Forward Relocation Request in 3GPP EPC). As such, as shown in block 1010 of Figure 10, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission of the whole set of information to the new MME, for example, before the new

MME sends or can send the information to the new MEC server. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for causing transmission of the whole set of information to the new MME, for example, before the new MME sends or can send the information to the new MEC server.

[0091] Furthermore, in an instance in which it is determined that the old MME sends, will send, or should send the information to the new MEC server, the configuration or awareness of the old MME shall cover also the new eNB vs. new MEC server relationship. As such, as shown in block 1015 of Figure 10, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to apply or utilize the configuration or awareness of the old MME to cover the new eNB - new MEC server relationship. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for applying or utilizing the configuration or awareness of the old MME to cover the new eNB - new MEC server relationship.

[0092] In an instance in which it is determined that transmission is performed by the new MME, as shown in block 1020 of Figure 10, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission, from the old MME to the new MME, of the whole set of information with updates caused by the handover. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for causing transmission, from the old MME to the new MME, of the whole set of information with updates caused by the handover.

[0093] In an instance in which it is determined that transmission is performed by the third party entity or function, as shown in block 1025 of Figure 10, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission, from the old MME to the third party entity of function, of the whole set of information with updates caused by the handover. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for causing transmission, from the old MME to the third party entity of function, of the whole set of information with updates caused by the handover. In some embodiments, while transmission of the whole set of information may be, as described above, performed by the third network entity or function, the third party entity or function may receive the information from the old MME, via the new MME. As such, the apparatus, such as apparatus 20 embodied by the MME 330, may be configured to cause transmission, from the old MME to the new MME or to the third party entity or function via the new MME, of the whole set of information with updates caused by the handover. [0094] As shown in block 1030 of Figure 10, an apparatus, such as apparatus 20 embodied by the MME 330, may be configured to inform the old MEC server about the handover/event and/or request the old MEC server to invalidate/nullify (at least part of) the user/UE related information. The apparatus embodied by MME 330 may therefore include means, such as the processor 22, the communication interface 26 or the like, for informing the old MEC server about the handover/event and/or requesting or enabling the old MEC server to invalidate/nullify (at least part of) the user/UE related information.

[0095] In some embodiments, MME 330 may be configured to provide a MEC server with the user/UE location information, and may identify the user/UE with an identity known in the mobile network, e.g. IMSI or IMEI. In some embodiments, MME 330 may also be configured to provide the MEC server with the current IP address of the UE and/or subscriber/subscription related information and/or UE/device specific information. Some of the information may be classified or filtered e.g. for privacy reasons.

[0096] The MEC server may request the information from MME 330, or in some embodiments, MME 330 may be configured to send specific information to specific MEC servers, for example, when a user/UE related event (e.g. attach, handover, IP context change, etc.) is detected and additionally or alternatively, other conditions (e.g., time, date, weekday, etc.) are met.

[0097] In some embodiments, authorized MEC applications may then use the information. For example, one or more applications may be configured to use the location information for targeted advertisement. In this embodiment, a functionality may be complemented with a mechanism to get/receive/access the location information, and further, access or transmit the IP addresses of one or more UEs to the application thus enabling, for example, a quick and simple addressing of the targeted users/UEs, and further, provide (possibly classified or filtered) user and/or UE/device information. In some embodiments, the user or UE/device information may further help applications in selecting users/UEs (from amongst those at the indicated location).

[0098] In a further embodiment. MME 330 may provide a MEC server, i.e. a trusted application at the MEC server (or the MEC platform), with the mobile network user/UE ID and the IP address of the related UE. The trusted application may also be provided with an external user ID (e.g. from the realm of an enterprise LAN) of the same user. The trusted application may then use the mobile network user/UE ID plus the UE IP address pair and the mobile network user/UE ID plus the external user ID pair to bind the current IP address of the UE to the external user ID, and may, in some embodiments, be further configured to create a routing rule for user data flows using the IP address and the external user ID. The routing rule may, for example, direct such user data flows, detected on the MEC server's user plane, to the external realm/entity (e.g., enterprise LAN).

[0099] In some embodiments, the network entity providing the information to MEC servers may be a different entity than MME, such as, for example, S/P-GW or PCRF. In particular, this embodiment may be preferred, for example, in a network where the MEC servers reside behind the SGi interface (for SGi, refer e.g. to figure 3 or to the current 3GPP EPC architecture), i.e. the MME, S-GW and P-GW reside between the eNBs and MEC server(s). However, even in this network/architectural solution, the MME may still be configured to provide the information, with the same benefits of less network entities on the path of the information from the source to the destination as with the network architecture solution in Figure 3.

[00100] Figure 11 is a block diagram showing a system that may be specifically configured in accordance with an example embodiment of the present invention. In particular, Figure 11 shows a block diagram of a 3GPP Architecture for Service Capability Exposure. In this SCEF embodiment, the MEC server, or more specifically the MEC Platform or an application inside the MEC server, may act as the Application that requests or is provided with user and/or access related information available at SCEF. The operations as described above with regard to Figures 4-8 may be configured to apply to the SCEF embodiment. Seen from the MEC server, the interface between the MEC server and MME is replaced with the API/interface between the MEC server and SCEF. Seen from MME, the interface between MME and the MEC server is replaced with an interface between MME and SCEF. Consequently, information sent to the MEC server may still originate from MME, as per figures 4-8. The information is just first sent from MME to SCEF and then, as such or filtered or combined with information from other sources, sent to the MEC server.

[00101] The benefits of this embodiment are, for example, (1) that there is no need to define a dedicated interface between the MEC server and MME, and (2) that more information may be available from SCEF than from MME, because, for example, SCEF gets user/UE and/or access related information from many different entities/functions. For example, access network congestion information may be available from RCAF, policy control information may be or can be made available via PCRF, etc.

[00102] Using SCEF as a source of the user/UE related information to be sent to a MEC server may provide several advantages. For example, there may be no need to define a dedicated interface between the MEC server and MME. Instead, for example, one or some of already available APIs may be used. Second, more information may be available from SCEF than from MME, because, for example, SCEF gets user/UE and/or access related information from many different entities/functions. For example, access network congestion information is available from RCAF, policy control information is or can be made available via PCRF, etc. Finally, even though the SCEF based solution as a whole may look heavier to implement, it may be better (than the MME, P-GW or PCRF based) solution in the long run, because it may be more general and extensible. The SCEF architecture may also support information transfer, if needed, in roaming conditions with an interface between the home network SCEF and visited network SCEF.

[00103] 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.