WO2017187011A1 - Gestion d'informations d'utilisateur dans une architecture mobile edge computing - Google Patents

Gestion d'informations d'utilisateur dans une architecture mobile edge computing Download PDF

Info

Publication number
WO2017187011A1
WO2017187011A1 PCT/FI2017/050281 FI2017050281W WO2017187011A1 WO 2017187011 A1 WO2017187011 A1 WO 2017187011A1 FI 2017050281 W FI2017050281 W FI 2017050281W WO 2017187011 A1 WO2017187011 A1 WO 2017187011A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
mec server
information
enb
coverage area
Prior art date
Application number
PCT/FI2017/050281
Other languages
English (en)
Inventor
John RÄSÄNEN
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2017187011A1 publication Critical patent/WO2017187011A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link

Definitions

  • Embodiments of the present invention relate generally to facilitating user related information management in mobile edge computing.
  • MEC mobile edge computing
  • UE user/user equipment
  • 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.
  • 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.
  • ETSI European telecommunications standards institute
  • ISG Industry specification group
  • MEC 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.
  • a 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.
  • UE user equipment
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the configuration or awareness of the old MME shall cover also the new eNB versus a new MEC server relationship.
  • 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.
  • 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.
  • 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 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.
  • UE user equipment
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the configuration or awareness of the old MME shall cover also the new eNB versus a new MEC server relationship.
  • 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.
  • 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.
  • 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.
  • UE user equipment
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the configuration or awareness of the old MME shall cover also the new eNB versus a new MEC server relationship.
  • 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.
  • 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.
  • Figure 1 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention
  • Figure 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present invention.
  • Figure 3 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention.
  • Figures 4-8 are data flow diagrams showing exemplary processes performed in accordance with some example embodiments of the present invention.
  • Figures 9 and 10 are flowcharts showing exemplary methods of operating an example apparatus in accordance with exemplary embodiments of the present invention.
  • Figure 11 is a block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention.
  • 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.
  • circuitry applies to all uses of this term in this application, including in any claims.
  • 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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • 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.
  • W-CDMA wideband code division multiple access
  • CDMA2000 Code Division Multiple Access 2000
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • WiMAX Worldwide Interoperability for Microwave Access
  • UMTS universal mobile telecommunications systems
  • UTRAN Universal mobile telecommunications systems
  • the access points 12 and the stations 10 may communicate via wireline communications, but most commonly communicate via wireless communications.
  • 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.
  • 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.
  • UE user equipment
  • 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.
  • Wi-Fi wireless local area network
  • 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.
  • the station 10 may include or be associated with an apparatus 20 as shown in Figure 2.
  • 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.
  • a processor 22 may include or otherwise be in communication with a processor 22 and a memory device 24.
  • a communication interface 26 may include or otherwise be in communication with a user interface 28.
  • 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.
  • 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.
  • 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.
  • the memory device could be configured to buffer input data for processing by the processor.
  • the memory device could be configured to store instructions for execution by the processor.
  • the apparatus 20 may be embodied by a computing device 10 configured to employ an example embodiment of the present invention.
  • the apparatus may be embodied as a chip or chip set.
  • 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.”
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processor 22 may be embodied in a number of different ways.
  • 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.
  • 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.
  • the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
  • the processor 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processor.
  • the processor may be configured to execute hard coded functionality.
  • 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.
  • the processor 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.
  • the processor 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • DSL digital subscriber line
  • USB universal serial bus
  • 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.
  • 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.
  • 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
  • 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.
  • 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..
  • 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
  • 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)."
  • information is transferred from MME to a MEC server via a third entity or function.
  • 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.
  • 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.
  • MME gets the location information / cell ID from the radio network whenever there is a change.
  • Alternative solutions S/P-GW, PCRF
  • 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.
  • the present disclosure provides a simple interface / application protocol between MME and RNIS / MEC server to, for example, solve the described information exchange problem.
  • 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.
  • 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.
  • 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.
  • FIGS. 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.
  • 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).
  • 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.
  • the operations of Figures 4-10 define an algorithm for configuring a computer or processing to perform an example embodiment.
  • 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.
  • 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.
  • 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.).
  • UE related parameters e.g. UE IP address, UE location, etc.
  • UE 305 sends an attach request to eNB310, the attach request comprising one or more UE related parameters.
  • eNB310 provides the attached request to MME 330 with the UE related parameters.
  • 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.
  • 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.
  • 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.
  • 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.
  • MME 330 may then save the UE IP address, for possible later use, e.g.
  • 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.
  • MEC server may use the received information as per the various embodiments described below.
  • FIG. 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.
  • eNB 310 transmits a path switch request to the MME 330.
  • 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.
  • 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.
  • MEC server 320 may be configured to utilize the received information as described here.
  • FIG. 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.
  • UE 305 may transmit a path switch request to MME 330.
  • MME 330 notes that the new eNB is in the area of another MEC server.
  • 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.
  • 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
  • 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.
  • MME 330 may then transmit message [(IMSI and/or UE IP Address), Location info, Subscription/Group/Classification info, ...] to the new MEC server
  • MEC server 325 may be configured to utilize the received information as described here.
  • MME 330 may transmit message
  • the old MEC server 320 may invalidate/nullify parameters e.g. IP address, of the indicated user/UE.
  • FIG. 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.
  • eNB may provide an indication to MME 330, that a handover is required.
  • MME-old 330 may be configured to identify, transmit and/or forward the relocation request to a new MME, MME-new 330A.
  • MME-old 330 notes that the new eNB is in the area of another MEC server, MEC-new 325.
  • 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.
  • 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.
  • 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.
  • new MME may transmit message [IMSI, UE IP Address), Location info, Subscription/Group/Classification info, ...] to the new MEC server 325.
  • new MEC server 325 may use the received information as per the various embodiments described below.
  • previous MME 330 may transit message [indication of UE leaving the area / request to nullify parameters] to the previous MEC server 320.
  • the previous MEC server 320 may invalidate/nullify parameters e.g. IP address, of the indicated user/UE.
  • FIG. 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.
  • UE 305 transmits detach request [parameters] to MME 330. That is the UE may detach from the network, intentionally or unintentionally.
  • MME 330 transmits a delete session request to P-GW 340.
  • 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.
  • MME 330 prepares to inform the MEC server.
  • MME 330 transmits message [indication of UE detaching/detached / request to nullify parameters].
  • MEC server 320 may invalidate/nullify parameters e.g., IP address, of the indicated user/UE.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • MME may need to send updated information, e.g. UE location information, to the MEC server.
  • updated information e.g. UE location information
  • 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.
  • the MME 330 may be configured to facilitate the UE being transferred to the second eNB.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the MME may be configured for facilitating the UE being transferred to a second MME coverage area.
  • 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.
  • MME may need to send the whole set of information, with updates caused by the handover, to the new MEC server.
  • 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.
  • MME may need to send the whole set of information, with updates caused by the handover, to the new MEC server.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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).
  • a handover message e.g. Forward Relocation Request in 3GPP EPC
  • 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.
  • 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.
  • 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.
  • 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.
  • the third party entity or function may receive the information from the old MME, via the new MME.
  • 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.
  • 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.
  • 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.
  • 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.
  • a user/UE related event e.g. attach, handover, IP context change, etc.
  • other conditions e.g., time, date, weekday, etc.
  • authorized MEC applications may then use the information.
  • one or more applications may be configured to use the location information for targeted advertisement.
  • 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.
  • the user or UE/device information may further help applications in selecting users/UEs (from amongst those at the indicated location).
  • 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).
  • 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.
  • 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).
  • 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.
  • FIG 11 is a block diagram showing a system that may be specifically configured in accordance with an example embodiment of the present invention.
  • Figure 11 shows a block diagram of a 3GPP Architecture for Service Capability Exposure.
  • 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 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.
  • 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.
  • SCEF gets user/UE and/or access related information from many different entities/functions.
  • access network congestion information may be available from RCAF
  • policy control information may be or can be made available via PCRF, etc.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil facilitant la gestion d'informations d'utilisateur dans une architecture Mobile Edge Computing (MEC). Le procédé peut comprendre les étapes consistant à : recevoir, au niveau de l'entité de gestion de mobilité, au moins une première indication d'eNB indiquant la présence d'un premier eNB dans la zone de couverture d'unité MME; détecter un transfert d'un équipement utilisateur (UE) entre le premier eNB et un second eNB; et déterminer si le transfert implique que le second eNB se trouve dans la zone de couverture d'unité MME et dans la première zone de couverture de serveur MEC, à l'intérieur de la zone de couverture d'unité MME, à l'extérieur de la première zone de couverture de serveur MEC, et à l'intérieur d'une seconde zone de couverture de serveur MEC, de sorte que l'UE soit transféré au second eNB ou à l'extérieur de la zone de couverture d'unité MME. Dans certains modes de réalisation, dans un cas où le second eNB se trouve à l'intérieur de la zone de couverture d'unité MME et à l'intérieur de la première zone de couverture de serveur MEC, l'invention facilite le transfert de l'équipement utilisateur au second eNB et au même serveur MEC.
PCT/FI2017/050281 2016-04-27 2017-04-13 Gestion d'informations d'utilisateur dans une architecture mobile edge computing WO2017187011A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662328037P 2016-04-27 2016-04-27
US62/328,037 2016-04-27

Publications (1)

Publication Number Publication Date
WO2017187011A1 true WO2017187011A1 (fr) 2017-11-02

Family

ID=60160162

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2017/050281 WO2017187011A1 (fr) 2016-04-27 2017-04-13 Gestion d'informations d'utilisateur dans une architecture mobile edge computing

Country Status (1)

Country Link
WO (1) WO2017187011A1 (fr)

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282801A (zh) * 2018-01-26 2018-07-13 重庆邮电大学 一种基于移动边缘计算的切换管理方法
CN108712761A (zh) * 2018-03-20 2018-10-26 中国科学院计算机网络信息中心 移动终端跨区保持mec边缘tcp业务服务方法及系统
CN109362100A (zh) * 2018-12-26 2019-02-19 中国联合网络通信集团有限公司 一种基于通信信令的基站评估方法和系统
US10230605B1 (en) 2018-09-04 2019-03-12 Cisco Technology, Inc. Scalable distributed end-to-end performance delay measurement for segment routing policies
US10235226B1 (en) 2018-07-24 2019-03-19 Cisco Technology, Inc. System and method for message management across a network
US10285155B1 (en) 2018-09-24 2019-05-07 Cisco Technology, Inc. Providing user equipment location information indication on user plane
US10284429B1 (en) 2018-08-08 2019-05-07 Cisco Technology, Inc. System and method for sharing subscriber resources in a network environment
CN109756903A (zh) * 2017-11-03 2019-05-14 南宁富桂精密工业有限公司 优化移动边缘计算系统的方法和相关设备
US10299128B1 (en) 2018-06-08 2019-05-21 Cisco Technology, Inc. Securing communications for roaming user equipment (UE) using a native blockchain platform
CN109788514A (zh) * 2017-11-13 2019-05-21 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及边缘计算平台
CN109788513A (zh) * 2017-11-13 2019-05-21 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及控制器
CN109818868A (zh) * 2017-11-20 2019-05-28 中兴通讯股份有限公司 一种实现边缘网络能力开放的方法、装置、设备及存储介质
EP3509349A1 (fr) * 2018-01-09 2019-07-10 Saguna Networks Ltd. Réseau de communication de données mobiles facilitant un calcul informatisé en périphérie (edge-computing)
TWI667933B (zh) * 2017-12-29 2019-08-01 財團法人工業技術研究院 行動邊緣平台伺服器及其車聯網服務之裝置與訊息管理方法
US10374749B1 (en) 2018-08-22 2019-08-06 Cisco Technology, Inc. Proactive interference avoidance for access points
CN110233815A (zh) * 2018-03-05 2019-09-13 大唐移动通信设备有限公司 一种寻呼方法和装置
US10491376B1 (en) 2018-06-08 2019-11-26 Cisco Technology, Inc. Systems, devices, and techniques for managing data sessions in a wireless network using a native blockchain platform
US10499304B1 (en) 2018-06-18 2019-12-03 Google Llc Fifth generation new radio edge computing mobility management
CN110839233A (zh) * 2018-08-17 2020-02-25 中国电信股份有限公司 流量统计方法、装置及计算机可读存储介质
US10601724B1 (en) 2018-11-01 2020-03-24 Cisco Technology, Inc. Scalable network slice based queuing using segment routing flexible algorithm
US10652152B2 (en) 2018-09-04 2020-05-12 Cisco Technology, Inc. Mobile core dynamic tunnel end-point processing
US10779188B2 (en) 2018-09-06 2020-09-15 Cisco Technology, Inc. Uplink bandwidth estimation over broadband cellular networks
EP3783863A1 (fr) * 2019-08-20 2021-02-24 TMRW Foundation IP & Holding S.A.R.L. Système et procédé de réseau d'accès radio virtuel pour des services d'informatique en nuage, de rendu, de suivi et de communication dans un espace tridimensionnel à travers un réseau de centres informatiques distribués
US10949557B2 (en) 2018-08-20 2021-03-16 Cisco Technology, Inc. Blockchain-based auditing, instantiation and maintenance of 5G network slices
CN112788089A (zh) * 2019-11-11 2021-05-11 财团法人工业技术研究院 多边缘云的网络通讯控制方法及边缘运算装置与系统
TWI727496B (zh) * 2019-11-11 2021-05-11 財團法人工業技術研究院 多邊緣雲之網路通訊控制方法及邊緣運算系統
EP3780497A4 (fr) * 2018-05-16 2021-06-02 Huawei Technologies Co., Ltd. Procédé informatique de bord mobile et dispositif
CN113891411A (zh) * 2021-10-18 2022-01-04 中国联合网络通信集团有限公司 一种mec切换方法、装置和电子设备
US11558288B2 (en) 2018-09-21 2023-01-17 Cisco Technology, Inc. Scalable and programmable mechanism for targeted in-situ OAM implementation in segment routing networks
US11606421B2 (en) 2017-12-12 2023-03-14 Sony Group Corporation Edge computing relocation

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120303818A1 (en) * 2010-04-07 2012-11-29 Limelight Networks, Inc. Edge-based resource spin-up for cloud computing
US20150245160A1 (en) * 2014-02-24 2015-08-27 International Business Machines Corporation Techniques for Mobility-Aware Dynamic Service Placement in Mobile Clouds

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120303818A1 (en) * 2010-04-07 2012-11-29 Limelight Networks, Inc. Edge-based resource spin-up for cloud computing
US20150245160A1 (en) * 2014-02-24 2015-08-27 International Business Machines Corporation Techniques for Mobility-Aware Dynamic Service Placement in Mobile Clouds

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Mobile-Edge Computing - Introductory Technical White Paper", EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI, 16 December 2014 (2014-12-16), 650, route des Lucioles ; F-06921 Sophia-Antipolis ; France, pages 1 - 36 *
GIUST, F.: "NEC EUROPE LTD MEC MOBILITY MANAGEMENT", EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI, 14 July 2015 (2015-07-14), 650, route des Lucioles ; F-06921 Sophia-Antipolis ; France *

Cited By (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109756903B (zh) * 2017-11-03 2022-03-29 南宁富桂精密工业有限公司 优化移动边缘计算系统的方法和相关设备
TWI669007B (zh) * 2017-11-03 2019-08-11 鴻海精密工業股份有限公司 優化移動邊緣計算系統的方法和相關設備
US10660003B2 (en) 2017-11-03 2020-05-19 Hon Hai Precision Industry Co., Ltd. Methods and related devices for optimizing a mobile edge computing (MEC) system
CN109756903A (zh) * 2017-11-03 2019-05-14 南宁富桂精密工业有限公司 优化移动边缘计算系统的方法和相关设备
CN109788513A (zh) * 2017-11-13 2019-05-21 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及控制器
CN109788514B (zh) * 2017-11-13 2021-03-23 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及边缘计算平台
CN109788513B (zh) * 2017-11-13 2021-03-23 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及控制器
CN109788514A (zh) * 2017-11-13 2019-05-21 中国电信股份有限公司 边缘计算应用的数据同步方法、系统及边缘计算平台
US11425225B2 (en) 2017-11-20 2022-08-23 Zte Corporation Method, apparatus, and equipment for exposing edge network capability, and storage medium
CN109818868B (zh) * 2017-11-20 2021-06-22 中兴通讯股份有限公司 一种实现边缘网络能力开放的方法、装置、设备及存储介质
CN109818868A (zh) * 2017-11-20 2019-05-28 中兴通讯股份有限公司 一种实现边缘网络能力开放的方法、装置、设备及存储介质
US11606421B2 (en) 2017-12-12 2023-03-14 Sony Group Corporation Edge computing relocation
TWI667933B (zh) * 2017-12-29 2019-08-01 財團法人工業技術研究院 行動邊緣平台伺服器及其車聯網服務之裝置與訊息管理方法
EP3509349A1 (fr) * 2018-01-09 2019-07-10 Saguna Networks Ltd. Réseau de communication de données mobiles facilitant un calcul informatisé en périphérie (edge-computing)
CN108282801A (zh) * 2018-01-26 2018-07-13 重庆邮电大学 一种基于移动边缘计算的切换管理方法
CN110233815A (zh) * 2018-03-05 2019-09-13 大唐移动通信设备有限公司 一种寻呼方法和装置
CN110233815B (zh) * 2018-03-05 2020-07-03 大唐移动通信设备有限公司 一种寻呼方法和装置
CN108712761A (zh) * 2018-03-20 2018-10-26 中国科学院计算机网络信息中心 移动终端跨区保持mec边缘tcp业务服务方法及系统
CN108712761B (zh) * 2018-03-20 2021-02-09 中国科学院计算机网络信息中心 移动终端跨区保持mec边缘tcp业务服务方法及系统
EP3780497A4 (fr) * 2018-05-16 2021-06-02 Huawei Technologies Co., Ltd. Procédé informatique de bord mobile et dispositif
US11803409B2 (en) 2018-05-16 2023-10-31 Huawei Technologies Co., Ltd. Mobile edge computing method and apparatus
US10742396B2 (en) 2018-06-08 2020-08-11 Cisco Technology, Inc. Securing communications for roaming user equipment (UE) using a native blockchain platform
US10491376B1 (en) 2018-06-08 2019-11-26 Cisco Technology, Inc. Systems, devices, and techniques for managing data sessions in a wireless network using a native blockchain platform
US10299128B1 (en) 2018-06-08 2019-05-21 Cisco Technology, Inc. Securing communications for roaming user equipment (UE) using a native blockchain platform
US10361843B1 (en) 2018-06-08 2019-07-23 Cisco Technology, Inc. Native blockchain platform for improving workload mobility in telecommunication networks
US10505718B1 (en) 2018-06-08 2019-12-10 Cisco Technology, Inc. Systems, devices, and techniques for registering user equipment (UE) in wireless networks using a native blockchain platform
US10673618B2 (en) 2018-06-08 2020-06-02 Cisco Technology, Inc. Provisioning network resources in a wireless network using a native blockchain platform
US10499304B1 (en) 2018-06-18 2019-12-03 Google Llc Fifth generation new radio edge computing mobility management
US10235226B1 (en) 2018-07-24 2019-03-19 Cisco Technology, Inc. System and method for message management across a network
US10284429B1 (en) 2018-08-08 2019-05-07 Cisco Technology, Inc. System and method for sharing subscriber resources in a network environment
CN110839233A (zh) * 2018-08-17 2020-02-25 中国电信股份有限公司 流量统计方法、装置及计算机可读存储介质
CN110839233B (zh) * 2018-08-17 2022-06-17 中国电信股份有限公司 流量统计方法、装置及计算机可读存储介质
US10949557B2 (en) 2018-08-20 2021-03-16 Cisco Technology, Inc. Blockchain-based auditing, instantiation and maintenance of 5G network slices
US10374749B1 (en) 2018-08-22 2019-08-06 Cisco Technology, Inc. Proactive interference avoidance for access points
US11606298B2 (en) 2018-09-04 2023-03-14 Cisco Technology, Inc. Mobile core dynamic tunnel end-point processing
US10230605B1 (en) 2018-09-04 2019-03-12 Cisco Technology, Inc. Scalable distributed end-to-end performance delay measurement for segment routing policies
US11201823B2 (en) 2018-09-04 2021-12-14 Cisco Technology, Inc. Mobile core dynamic tunnel end-point processing
US10652152B2 (en) 2018-09-04 2020-05-12 Cisco Technology, Inc. Mobile core dynamic tunnel end-point processing
US10779188B2 (en) 2018-09-06 2020-09-15 Cisco Technology, Inc. Uplink bandwidth estimation over broadband cellular networks
US11864020B2 (en) 2018-09-06 2024-01-02 Cisco Technology, Inc. Uplink bandwidth estimation over broadband cellular networks
US11558288B2 (en) 2018-09-21 2023-01-17 Cisco Technology, Inc. Scalable and programmable mechanism for targeted in-situ OAM implementation in segment routing networks
US10285155B1 (en) 2018-09-24 2019-05-07 Cisco Technology, Inc. Providing user equipment location information indication on user plane
US10660061B2 (en) 2018-09-24 2020-05-19 Cisco Technology, Inc. Providing user equipment location information indication on user plane
US10601724B1 (en) 2018-11-01 2020-03-24 Cisco Technology, Inc. Scalable network slice based queuing using segment routing flexible algorithm
US11627094B2 (en) 2018-11-01 2023-04-11 Cisco Technology, Inc. Scalable network slice based queuing using segment routing flexible algorithm
CN109362100B (zh) * 2018-12-26 2021-08-03 中国联合网络通信集团有限公司 一种基于通信信令的基站评估方法和系统
CN109362100A (zh) * 2018-12-26 2019-02-19 中国联合网络通信集团有限公司 一种基于通信信令的基站评估方法和系统
CN112422311A (zh) * 2019-08-20 2021-02-26 明日基金知识产权控股有限公司 通过分布式计算中心网络在三维空间中优化实时响应的连续的基于位置的服务的系统和方法
KR102443913B1 (ko) * 2019-08-20 2022-09-16 티엠알더블유 파운데이션 아이피 앤드 홀딩 에스에이알엘 분산 컴퓨팅 센터 네트워크를 통한 3 차원 공간에서의 최적화된 실시간 응답 연속 위치 기반 클라우드 컴퓨팅, 렌더링, 추적 및 통신 서비스를 위한 가상 무선 액세스 네트워크 시스템 및 방법
US11076004B2 (en) 2019-08-20 2021-07-27 The Calany Holding S.Á R.L. Virtual radio access network system and method for optimized real-time responsive continuous location-based cloud computing, rendering, tracking, and communication services in three-dimensional space through a distributed computing center network
EP3783863A1 (fr) * 2019-08-20 2021-02-24 TMRW Foundation IP & Holding S.A.R.L. Système et procédé de réseau d'accès radio virtuel pour des services d'informatique en nuage, de rendu, de suivi et de communication dans un espace tridimensionnel à travers un réseau de centres informatiques distribués
KR20210023705A (ko) * 2019-08-20 2021-03-04 티엠알더블유 파운데이션 아이피 앤드 홀딩 에스에이알엘 분산 컴퓨팅 센터 네트워크를 통한 3 차원 공간에서의 최적화된 실시간 응답 연속 위치 기반 클라우드 컴퓨팅, 렌더링, 추적 및 통신 서비스를 위한 가상 무선 액세스 네트워크 시스템 및 방법
CN112422311B (zh) * 2019-08-20 2023-09-05 卡兰控股有限公司 通过分布式计算中心网络在三维空间中优化实时响应的连续的基于位置的服务的系统和方法
CN112788089A (zh) * 2019-11-11 2021-05-11 财团法人工业技术研究院 多边缘云的网络通讯控制方法及边缘运算装置与系统
CN112788089B (zh) * 2019-11-11 2023-11-07 财团法人工业技术研究院 多边缘云的网络通讯控制方法及边缘运算装置与系统
TWI727496B (zh) * 2019-11-11 2021-05-11 財團法人工業技術研究院 多邊緣雲之網路通訊控制方法及邊緣運算系統
CN113891411A (zh) * 2021-10-18 2022-01-04 中国联合网络通信集团有限公司 一种mec切换方法、装置和电子设备
CN113891411B (zh) * 2021-10-18 2023-07-18 中国联合网络通信集团有限公司 一种mec切换方法、装置和电子设备

Similar Documents

Publication Publication Date Title
WO2017187011A1 (fr) Gestion d'informations d'utilisateur dans une architecture mobile edge computing
AU2020239707B2 (en) Inter-communications-system handover method, device, and system
US10264439B2 (en) Method and apparatus for discovering devices and application users
WO2018206844A1 (fr) Gestion de routage et de politique au niveau d'une périphérie de réseau
EP3713258B1 (fr) Procédé et dispositif de rapport d'informations de localisation
US20120202492A1 (en) Method and apparatus for enabling identification of a rejecting network in connection with registration area updating
US20140355444A1 (en) Method and Apparatus for Providing Routing
JP6777451B2 (ja) 基地局
JP7362723B2 (ja) Ｐｄｕセッションの常時接続属性を提供するため、及び常時接続ｐｄｕセッションに関してインターワーキングの側面を提供するための方法及び装置
US10212093B2 (en) Method and apparatus for U-plane sub-service flow mapping
US10075414B2 (en) Method and apparatus for providng push service in communication system
US11546765B2 (en) Master gNodeBs and method of operating master gNodeB
US20230269631A1 (en) Wireless communication handovers for non-third generation partnership project (non-3gpp) access nodes
JP2015525518A (ja) ３ｇｐｐ及びｅｔｓｉのマシン・ツー・マシン（ｍ２ｍ）相互接続のためのｍ２ｍデバイス及び方法
EP4080911A1 (fr) Procédé et appareil de suivi de topologie de zone
WO2018174790A1 (fr) Équipement utilisateur, nœud de réseau central, nœud de réseau radio et procédés pour traiter des mesures de couche d'application
JP7100645B2 (ja) 位置算出装置、無線基地局、位置算出方法、および測位制御方法
US10674564B2 (en) Base station, management apparatus and connection method
WO2018002438A1 (fr) Procédé et appareil facilitant le comportement de ppr renforcé de sw
US20240107288A1 (en) Roaming for UE of a NPN

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17788876

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17788876

Country of ref document: EP

Kind code of ref document: A1