WO2018154355A1 - Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès - Google Patents

Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès Download PDF

Info

Publication number
WO2018154355A1
WO2018154355A1 PCT/IB2017/051049 IB2017051049W WO2018154355A1 WO 2018154355 A1 WO2018154355 A1 WO 2018154355A1 IB 2017051049 W IB2017051049 W IB 2017051049W WO 2018154355 A1 WO2018154355 A1 WO 2018154355A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
user equipment
control plane
mec
mec server
Prior art date
Application number
PCT/IB2017/051049
Other languages
English (en)
Inventor
John RASANEN
Original Assignee
Nokia Technologies Oy
Nokia Usa Inc.
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, Nokia Usa Inc. filed Critical Nokia Technologies Oy
Priority to PCT/IB2017/051049 priority Critical patent/WO2018154355A1/fr
Publication of WO2018154355A1 publication Critical patent/WO2018154355A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • 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
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy

Definitions

  • An example embodiment relates generally to multi-access edge computing (MEC) and, more particularly, to the capture and provision of one or more parameters related to a user or user equipment served by one or more MEC servers.
  • MEC multi-access edge computing
  • Multi-access edge computing also known as mobile-edge computing
  • MEC provides for content to be rapidly processed at the edge of a mobile network.
  • application developers, content providers and others can enjoy cloud-computing capabilities with ultra-low latency and high bandwidth as well as real time access to radio network information that may be leveraged by various MEC applications.
  • MEC may be utilized by a variety of applications including video analytic applications, location service applications, Internet of Things (IoT) applications, augmented reality applications, optimized local content distribution applications and data caching applications.
  • IoT Internet of Things
  • a MEC platform includes one or more MEC servers for serving user equipment.
  • MEC servers In order to provide the various services to the user equipment, MEC servers sometimes require information, such as radio network information or information relating to the user or the user equipment including the identity of the user or user equipment, the location of the user or the user equipment and the like.
  • MEC servers may not always have access to the required information and, as such, may not be able to provide the desired services in a timely manner.
  • information relating to the user or the user equipment that is required by the MEC server but that may not always be available includes the Internet Protocol (IP) address allocated to the IP context of the user equipment, subscriber related classification information, e.g., information regarding a group or groups to which the subscriber belongs, location information of the user or user equipment, etc.
  • IP Internet Protocol
  • subscriber related classification information e.g., information regarding a group or groups to which the subscriber belongs
  • location information of the user or user equipment etc.
  • the MEC server is limited in its ability to obtain this information relating to the user or user equipment from the radio network, such as via the MEC radio network information service (RNIS), since the control plane via which such information would be transferred is ciphered between the user equipment and the core network.
  • RIS MEC radio network information service
  • An additional difficulty with respect to the MEC server obtaining and maintaining information regarding the user or the user equipment served by the MEC server is that some of the information may change over the course of time and may need to be dynamically updated.
  • the IP address of the user equipment may change, such as in an instance in which the user equipment detaches from and thereafter reattaches to the network or in which the user equipment experiences an inter-gateway handover.
  • the location information associated with the user equipment changes as the user equipment moves.
  • some of the information related to the user or the user equipment may be released, that is, may become unbound from the user or the user equipment.
  • the unbound information may thereafter be reused by and may even be bound to another user or user equipment, thereby introducing a risk of mixing confidential and trusted information, including sessions, of different users if the information regarding the user and user equipment is not updated by the MEC server.
  • the IP address allocated to a user or user equipment upon attaching to a network may be unbound from the user or user equipment when the user or user equipment detaches from the network and may thereafter be allocated to a different user or user equipment attaching to the network.
  • Handovers may create additional issues with respect to the accuracy of the information relating to the user or user equipment that is maintained by a MEC server.
  • a MEC server may not necessarily detect a handover condition in an instance in which a user equipment is handed over from an area served by a first MEC server to an area served by a second MEC server.
  • the second MEC server may not receive the information related to the user or user equipment that is now being served by the second MEC server following the handover.
  • the MEC server may not be able to support the various applications that rely upon the information associated with the user or the user equipment, at least not in a timely manner.
  • a method, apparatus and computer program product are provided in accordance with an example embodiment in order to capture one or more parameters related to a user or user equipment and to cause those parameters to be provided to a respective MEC server.
  • the method, apparatus and computer program product of an example embodiment arms the MEC server with the information required by applications that are reliant upon the information relating to the user or the user equipment such that the MEC server may support execution of these applications in a timely manner.
  • the method, apparatus and computer program product of an example embodiment capture the information relating to the user or the user equipment in such a manner as to identify instances in which the information relating to the user or the user equipment changes and the parameter(s) stored by a respective MEC server must be dynamically updated, as well as instances in which the information is released or unbound from the user or user equipment and parameter(s) stored by the respective MEC server must again be updated. Further, the method, apparatus and computer program product of an example embodiment facilitate handover from a first MEC server to a second MEC server with the second MEC server being provided with information regarding the user or user equipment now being served by the second MEC server following the handover, thereby increasing the reliability and reducing the latency associated with such a handover.
  • a method in an example embodiment, includes determining whether a control plane message references an access point associated with one or more multi-access edge computing (MEC) servers. In an instance in which the control plane message references an access point associated with one or more MEC servers, the method captures one or more parameters related to a user or user equipment associated with the control plane message. The method further includes causing the one or more parameters related to the user or user equipment to be provided to a respective MEC server.
  • MEC multi-access edge computing
  • the method of an example embodiment also includes identifying a first parameter that is common to the control plane messages in a current context of the user or user equipment to serve as a control plane key.
  • the method of this example embodiment also includes binding a subsequent control plane message having the first parameter that serves as a control plane key to the one or more parameters related to the user or user equipment.
  • the method of this example embodiment further includes updating the one or more parameters related to the user or user equipment based upon the subsequent control plane message.
  • the method of an example embodiment also includes identifying a second parameter that is common to the control plane messages and to user plane traffic involving the access point to serve as a user plane fetch key.
  • the method also includes receiving a request for the one or more parameters related to the user or user equipment.
  • the request is associated with the user plane fetch key.
  • the method further includes causing the one or more parameters related to the user or user equipment to be provided in response to the request associated with the user plane fetch key.
  • the method of an example embodiment determines whether a control plane message references an access point associated with one or more MEC servers by monitoring both request messages and response messages to determine whether the request and response messages reference the access point associated with one or more MEC servers.
  • the method of an example embodiment also includes determining, in response to a handover message, whether the MEC server serving the user equipment will change upon handover. In an instance in which the MEC server will change, the method of this example embodiment causes a message to be provided to the one or more MEC servers providing contact information for the respective MEC server serving the user equipment prior to the handover and for a second MEC server that will serve the user equipment following the handover.
  • the method of another example embodiment also includes receiving a control plane message from the respective MEC server and for causing a control plane message to be transmitted in response to the control plane message from the respective MEC server in order to trigger paging of one or more user equipment.
  • an apparatus in another example embodiment, includes at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the processor, cause the apparatus at least to determine whether a control plane message references an access point associated with one or more multi-access edge computing (MEC) servers.
  • MEC multi-access edge computing
  • the at least one memory and the computer program code are also configured to, with at least one processor, cause the apparatus to capture one or more parameters related to the user or user equipment associated with the control plane message and cause the one or more parameters related to the user or user equipment to be provided to a respective MEC server.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to identify a first parameter that is common to the control plane messages in the current context of the user or user equipment to serve as a control plane key.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of this example embodiment to bind the subsequent control plane message having the first parameter that serves as the control plane key to the one or more parameters related to the user or user equipment and to update the one or more parameters related to the user or user equipment based upon the subsequent control plane message.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of an example embodiment to identify a second parameter that is common to the control plane messages and to user plane traffic involving the access point to serve as a user plane fetch key.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of this example embodiment to receive a request for the one or more parameters related to the user or user equipment. The request is associated with the user plane fetch key.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of this example embodiment to cause the one or more parameters related to the user or user equipment to be provided in response to the request associated with user plane fetch key.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to determine whether a control plane message references an access point associated with one or more MEC servers by monitoring both request messages and response messages to determine whether the request and response messages reference the access point associated with one or more MEC servers.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to determine, in response to a handover message, whether the MEC server serving the user equipment will change upon handover.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus of this example embodiment to cause a message to be provided to the one or more MEC servers providing contact information for the respective MEC servers serving the user equipment prior to the handover and for a second MEC server that will serve the user equipment following the handover.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to receive a control plane message from the respective MEC server and to cause a control plane message to be transmitted in response to the control plane message from the respective MEC server in order to trigger paging of one or more user equipment.
  • an apparatus in a further example embodiment, includes means for determining whether a control plane message references an access point associated with one or more multi-access edge computing (MEC) servers.
  • the apparatus of this embodiment also includes means, in an instance in which the control plane message references an access point associated with one or more MEC servers, for capturing one or more parameters related to a user or user equipment associated with the control plane message.
  • the apparatus of this embodiment further includes means for causing the one or more parameters related to the user or user equipment to be provided to a respective MEC server.
  • the apparatus of an example embodiment also includes means for identifying the first parameter that is common to the control plane messages in the current context of the user or user equipment to serve as a control plane key.
  • the apparatus of this example embodiment also includes means for binding a subsequent control plane message having the first parameter that serves as the control plane key to the one or more parameters related to the user or user equipment.
  • the apparatus of this example embodiment further includes means for updating the one or more parameters related to the user or user equipment based upon the subsequent control plane message.
  • the apparatus of another example embodiment also includes means for identifying a second parameter that is common to the control plane messages and to user plane traffic involving the access point to serve as a user plane fetch key.
  • the apparatus of this example embodiment also includes means for receiving a request for the one or more parameters related to the user or user equipment. The request is associated with the user plane fetch key.
  • the apparatus of this example embodiment further includes means for causing the one or more parameters related to the user or user equipment to be provided in response to the request associated with the user plane fetch key.
  • the means for determining whether a control plane message references an access point associated with one or more MEC servers includes means for monitoring both request messages and response messages to determine whether the request and response messages reference the access point associated with one or more MEC servers.
  • the apparatus of another example embodiment further includes means, in response to a handover message, for determining whether the MEC server serving the user equipment will change upon handover and means, in an instance in which the MEC server will change, for causing a message to be provided to the one or more MEC servers providing contact information for the respective MEC server serving the user equipment prior to the handover and for a second MEC server that will serve the user equipment following the handover.
  • the apparatus of another example embodiment also includes means for receiving a control plane message from the respective MEC server and means for causing a control plane message to be transmitted in response to the control plane message from the respective MEC server in order to trigger paging of one or more user equipment.
  • a computer program product includes at least one non-transitory computer-readable storage medium having computer-executable program code stored therein with the computer-executable program code including program code instructions configured to determine whether a control plane message references an access point associated with one or more multi-access edge computer (MEC) servers.
  • the computer-executable program code also includes program code instructions configured to capture one or more parameters related to a user or user equipment associated with the control plane message.
  • the computer-executable program code further includes program code instructions configured to cause the one or more parameters related to the user or user equipment to be provided to a respective MEC server.
  • the computer-executable program code of another example embodiment further includes program code instructions configured to identify a first parameter that is common to the control plane messages in a current context of the user or user equipment to serve as a control plane key.
  • the computer-executable program code of this example embodiment also includes program code instructions configured to bind the subsequent control plane message having the first parameter that serves as the control plane key to the one or more parameters related to the user or user equipment.
  • the computer-executable program code of this example embodiment further includes program code instructions configured to update the one or more parameters related to the user or user equipment based upon the subsequent control plane message.
  • the computer-executable program code of another example embodiment also includes program code instructions configured to identify a second parameter that is common to the control plane messages and to user plane traffic involving the access point to serve as a user plane fetch key.
  • the computer-executable program code of this example embodiment also includes the program code instructions configured to receive a request for the one or more parameters related to the user or user equipment. The request is associated with the user plane fetch key.
  • the computer-executable program code of this example embodiment further includes program code instructions configured to cause the one or more parameters related to the user or user equipment to be provided in response to the request associated with the user plane fetch key.
  • the program code instructions configured to determine whether a control plane message references an access point associated with one or more MEC servers may include program control code instructions configured to monitor both request messages and response messages to determine whether the request and response messages reference the access point associated with one or more MEC servers.
  • the computer-executable program code of another example embodiment also includes program code instructions configured to determine, in response to a handover message, whether the MEC server serving the use equipment will change upon handover and, in an instance in which the MEC server will change, to cause a message to be provided to the one or MEC servers providing contact information for the respective MEC server serving the user equipment prior to the handover and for a second MEC server that will serve the user equipment following the handover.
  • the computer-executable program code of another example embodiment also includes program code instructions configured to receive a control plane message from the respective MEC server and to cause a control plane message to be transmitted in response to the control plane message from the respective MEC server in order to trigger paging of one or more user equipment.
  • FIG. 1 is a system diagram utilizing a 3 rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) network architecture with multi-access edge computing (MEC) servers on the Sl-U interface and a monitoring and control function in accordance with an example embodiment of the present disclosure on the S 11 interface;
  • 3GPP 3 rd Generation Partnership Project
  • LTE Long Term Evolution
  • MEC multi-access edge computing
  • Figure 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present disclosure to perform the monitoring and control function;
  • Figure 3 is a flowchart illustrating operations performed, such as by the apparatus of Figure 2, in accordance with an example embodiment of the present disclosure
  • Figure 4 is a signal flow diagram depicting the capture of one or more parameters related to a user or user equipment in conjunction with the attachment of the user equipment to a network in accordance with an example embodiment of the present disclosure
  • Figure 5 is a signal flow diagram illustrating the updating of one or more parameters related to the user or user equipment in accordance with an example embodiment of the present disclosure in response to the performance of an update action by the user equipment;
  • FIG. 6 is a signal flow diagram illustrating the provision of contact information to the multi-access edge computing (MEC) server involved in the handover in accordance with an example embodiment of the present disclosure
  • FIG. 7 is a signal flow diagram illustrating the fetching of one or more parameters related to a user or user equipment by a multi-access edge computing (MEC) server in accordance with an example embodiment of the present disclosure.
  • MEC multi-access edge computing
  • Figure 8 is a signal flow diagram illustrating the MEC server obtaining the location of the user equipment, such as for paging in accordance with an example embodiment of the present disclosure.
  • circuitry refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present.
  • the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.
  • a "computer-readable storage medium,” which refers to a non- transitory physical storage medium (e.g., volatile or non-volatile memory device), can be
  • a method, apparatus and computer program product are provided in accordance with an example embodiment in order to provide one or more parameters related to a user or user equipment to a respective multi-access edge computing (MEC) server that is serving the user or user equipment.
  • MEC multi-access edge computing
  • the MEC server may support applications that rely upon the one or more parameters related to the user or user equipment in an efficient manner with low latency. These applications may include location service applications or applications that otherwise depend upon the identity of the user equipment.
  • the one or more parameters associated with the user or user equipment may be provided in conjunction with a handover from a first MEC server to a second MEC server, thereby facilitating the seamless handover of the user equipment.
  • the one or more parameters related to the user or user equipment may also be updated such as in instances in which a parameter changes over the course of time or in instances in which the parameters are unbound from the user or user equipment, thereby insuring that the respective MEC server has up-to-date information for use with the applications executed by the respective MEC server.
  • FIG. 1 a system 10 utilizing a 3GPP LTE network architecture and including a plurality of MEC servers 12 is depicted. While shown in Figure 1 and described below in conjunction with a 3GPP LTE network architecture, the MEC servers and the apparatus providing the monitoring and control function in accordance with an example embodiment to the present disclosure may be employed in conjunction with other network architectures and access types other than a 3GPP radio access, such as a wireless local area network (WLAN) access or a fixed access. As such, the 3GPP LTE network architecture of Figure 1 is provided by way of example and not of limitation.
  • WLAN wireless local area network
  • the user equipment 14 such as a mobile terminal, e.g., a portable digital assistant (PDA), mobile telephone, smartphone, pager, mobile television, gaming device, laptop computer, camera, tablet computer, touch surface, video recorder, radio, electronic book, positioning device (e.g., global positioning system (GPS) device), or any combination of the aforementioned, and other types of voice and text communications systems, or a fixed computing device, such as a personal computer, a computer workstation, a server or the like, is connected via an access point 16, such as an evolved node B (eNB), a node B, a base station or the like, to a network, such as a mobile network.
  • a mobile terminal e.g., a portable digital assistant (PDA), mobile telephone, smartphone, pager, mobile television, gaming device, laptop computer, camera, tablet computer, touch surface, video recorder, radio, electronic book, positioning device (e.g., global positioning system (GPS) device), or any combination of the aforementioned, and other types of voice and
  • the user equipment may be connected to any one of a plurality of access nodes via an interface, such as an LTE-Uu interface.
  • an interface such as an LTE-Uu interface.
  • the user equipment and the access node may be connected both in the user/data plane and in the control plane with the solid line representing a connection in the user/data plane and the thinly-dashed line representing a connection in the control plane.
  • the access point such as eNB in the illustrated embodiment, is then connected both to a mobility management entity (MME) 18 and to one or more MEC servers 12, designated MEC servers 1, . .n.
  • MME mobility management entity
  • connection between the access node and the MME is in the control plane, such as via an SI -MME interface, while the connection between the access node and the MEC servers is in the user plane, such as via an Sl-U interface. Conversely, the connection between the access node and the one or more MEC servers is in the user plane, such as via an Sl-U interface.
  • the MEC servers 12 are, in turn, connected via the user plane to a serving gateway 20 (S- GW), such as via an Sl-U interface.
  • S-GW serving gateway 20
  • the S-GW is connected in both the user plane (UP) and the control plane (CP) to a packet data network gateway 22 (P-GW) which, in turn, provides a connection to a packet network, such as via an SGi interface.
  • P-GW packet data network gateway 22
  • the S-GW is also connected in the control plane, such as via an S 11 interface, to the MME.
  • an apparatus embodying a monitoring and control function 24 is associated with the one or more MEC servers 12, such as via an interface, e.g., an M-MCF interface.
  • the apparatus embodying the monitoring and control function is also configured to monitor the control plane traffic between the MME 18 and the S-GW 20, such as by monitoring the SI 1 interface in the control plane between the MME and the S-GW.
  • the control plane between user equipment 14 and the MME bypasses the MEC servers 12, while the user plane between the user equipment and the S-GW passes through a respective MEC server.
  • the apparatus that embodies the monitoring and control function is positioned in a trusted area within the network such that the control plane signaling monitored by the apparatus embodying the MCF, such as the control plane signaling between the MME and the S-GW, is not ciphered.
  • the apparatus embodying the monitoring and control function 24 may be embodied by one or more of the MEC servers 12 or by another network entity embodied by or independent of the other elements of the system 10 depicted in Figure 1. Regardless of the manner in which the apparatus embodying the monitoring and control function is embodied, however, the apparatus embodying the monitoring and control function may be transparent to the other core network entities, such as the MME 18, the S-GW 20, etc. and, as such, need not impact the mobile and/or core network specifications or implementations other than routing the control plane traffic through the apparatus embodying the monitoring and control function.
  • the apparatus embodying the monitoring and control function may be transparent to the other core network entities, such as the MME 18, the S-GW 20, etc. and, as such, need not impact the mobile and/or core network specifications or implementations other than routing the control plane traffic through the apparatus embodying the monitoring and control function.
  • the MEC servers 12 may be embodied in different manners, the MEC servers of the example embodiment depicted in Figure 1 include one or more applications 26, such as may be stored by a memory device of the MEC servers, and a multi-access edge platform 28 such as one or more processors, configured to execute the one or more applications.
  • the MEC servers also include a data/forwarding plane 30, such as a processor and/or communication interface as described below, for forwarding or routing the user plane traffic between the access node 16 and/or applications 26 and/or the S-GW via the SI -U interfaces.
  • access network types other than the 3GPP radio network access may also include one or more MEC servers 12 as well as an apparatus embodying a monitoring and control function 24 in accordance with the example embodiment of the present disclosure.
  • the apparatus embodying the monitoring and control function may monitor an interface different than the Sl l interface.
  • the apparatus embodying the monitoring and control function of another example embodiment may be configured to monitor reference point S2b between the evolved packet data gateway (ePDG) and the P-GW in a home public land mobile network or reference point S2a between a trusted wireless local area network (WLAN) access network and a P-GW.
  • ePDG evolved packet data gateway
  • WLAN trusted wireless local area network
  • the apparatus 40 embodying the monitoring and control function 24 may be configured in a variety of manners, but in one example embodiment may be configured as shown in Figure 2 so as to include, be associated with or otherwise be in communication with one or more processors 42, one or more memory devices 44 and a communication interface 46.
  • the processor and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor
  • the memory device may be non-transitory and may include, for example, one or more volatile and/or nonvolatile 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 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. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.
  • the apparatus 40 may be embodied by a computing device, such as one or more of the MEC servers 12 or another network entity.
  • 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 42 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 42 may be configured to execute instructions stored in the memory device 44 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 disclosure 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., an audio/video player, an audio/video mixer, a radio or a mobile terminal) 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.
  • ALU arithmetic logic unit
  • the apparatus 40 may also include the communication interface 46.
  • the communication interface 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 from/to a network and/or any other device or module in communication with the apparatus.
  • the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network.
  • 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).
  • the communication interface may alternatively or also support wired communication.
  • 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.
  • the apparatus embodying the monitoring and control function monitors control plane signaling in a trusted area of the network in which the control plane signaling is not ciphered.
  • the apparatus of an example embodiment includes means, such as the processor 42, the communication interface 46 or the like, for receiving a control plane message. See block 50 of Figure 3.
  • the apparatus is configured to receive a control plane message via the SI 1 interface between the MME 18 and the S-GW 20.
  • the apparatus 40 embodying the monitoring and control function also includes means, such as the processor 42 or the like, for determining, for a respective control plane message, whether the control plane message references an access point associated with one or more MEC servers 12. See block 52 of Figure 3.
  • the apparatus of an example embodiment includes, such as in memory 44, or has access to, such as via the communication interface 46, information that defines the MEC servers served by the apparatus as well as the access nodes, such as the eNBs 16 served by the one or more MEC servers.
  • the information defining the MEC servers served by the apparatus embodying the monitoring and control function and, in turn, the access nodes served by the MEC servers may be defined by information provided by the network regarding the configuration of the network and/or information associated with network typology management.
  • a single apparatus embodying the monitoring and control function may serve a plurality of MEC servers, such as all MEC servers connected to the access nodes, such as the eNBs, within the realm of an MME 18 with which the apparatus embodying the monitoring and control function is associated, such as a result of the monitoring of the control plane signals on the SI 1 interface between the MME and the S- GW 20 in the example embodiment of Figure 1.
  • the apparatus 40 such as the processor 42, embodying the monitoring and control function may determine whether a control plane message references an access point, e.g., an eNB 18, associated with one or more MEC servers 12 in various manners.
  • the apparatus such as the processor, is configured to identify the access point or cell identification (ID) within the control plane message.
  • the apparatus such as the processor, is configured to determine whether the access point or cell ID within the control plane message references an access point associated with one or more of the MEC servers with which the apparatus is associated.
  • the apparatus 40 such as the processor 42, embodying the monitoring and control function is configured to further evaluate the control plane message after having determined that the control plane message references an access point associated with one or more MEC servers with which the apparatus is associated.
  • the apparatus such as the processor, may be configured to further review the control plane message to determine whether the use of a MEC application is possible and/or is allowed.
  • the apparatus such as the processor, may be configured to determine whether the use of a MEC application is possible and/or allowed in various manners.
  • the apparatus such as the processor, is configured to identify the access point, e.g., the eNB 16, the connection type, the user's rights or indicated preferences, etc.
  • the apparatus may be configured to determine whether the use of a MEC application is possible and/or allowed, such as by comparing these additionally identified parameters with predefined requirements, such as may be maintained by memory 44, for the use of a MEC application.
  • the operations performed by the apparatus may be configured to proceed as shown in Figure 3 and as described hereinafter.
  • the apparatus such as the processor, may be configured to halt further analysis of the control plane message and to take no further action with respect to the particular control plane message.
  • the apparatus 40 embodying the monitoring and control function in accordance with an example embodiment also includes means, such as the processor 42, the memory 44 or the like, for capturing one or more parameters from the control plane message, such as a tracking area update (TAU) message, that are related to a user or user equipment associated with the control plane message.
  • the apparatus such as the processor, may be configured to capture a variety of parameters related to the user or user equipment, such as the access point or cell ID, the international mobile subscriber identity (IMSI), the user equipment identifier (e.g.
  • the apparatus embodying the monitoring and control function may be configured or instructed to monitor and capture power saving mode related information from control plane messages between the user equipment and the core network.
  • the captured information of this example embodiment may contain wake -up periods or information to indicate when the user equipment is available for, that is. is able to receive possible downlink data or control plane messages.
  • the apparatus embodying the monitoring and control function may further be configured or instructed to send the user equipment-availability or wake -up information to the relevant MEC server to enable an application or applications to determine the availability of the user equipment.
  • the one or more parameters captured relating to the user or user equipment associated with the control plane message may be stored, such as within memory.
  • the apparatus 40 embodying the monitoring and control function of an example embodiment includes means, such as the processor 42 or the like, for identifying a second parameter that is common to (utilized by both or included within both) the control plane message and to user plane traffic involving the access point, such as user plane traffic between the access point, e.g., eNB 16, and the S-GW 20 via the data forwarding plane 30 of one or more MEC servers in the example embodiment of Figure 1. See block 56 of Figure 3.
  • the parameter that is common to the control plane message and to the user plane traffic that is identified serves as a user plane fetch key and, as such, may be stored, such as by memory 44, and may be associated with the one or more parameters related to the user or user equipment that were captured from the control plane message in conjunction with block 54.
  • a request may thereafter be received, such as from a MEC server, for the one or more parameters related to the user or the user equipment that were captured.
  • This subsequent request for parameter(s) related to the user or the user equipment may identify the requested parameter(s) by the user plane fetch key associated with the parameter(s).
  • Various parameters may be utilized as the user plane fetch key. In an example embodiment, however, the user plane TEID is identified and is utilized as the user plane fetch key.
  • the apparatus 40 embodying the monitoring and control function in accordance with an example embodiment also includes means, such as the processor 42 or the like, for identifying a first parameter that is common to (utilized by both or included within both) the control plane messages in a current context of the user or user equipment.
  • This first parameter may then serve as a control plane key.
  • the apparatus, such as the processor, of this example embodiment is configured to identify a parameter that is common to the control plane messages in the particular packet data protocol (PDP) context of the user or user equipment. While various parameters may be utilized as a control plane key, the control plane TEID may be identified to be common to the control plane messages and may serve as the control plane key.
  • PDP packet data protocol
  • the parameter that is in common to the control plane messages in the current context of the user or user equipment that serves as the control plane key may be associated with the one or more parameters related to the user or user equipment, such as by storing the control plane key in memory 44 in conjunction with the one or more parameters related to the user or user equipment.
  • the apparatus 40 also includes means, such as the processor 42, the memory 44 or the like, for binding a subsequent control plane message having the same parameter that serves as the control plane key to the one or more parameters that were previously captured in conjunction with block 54 in relation to the user or the user equipment.
  • the apparatus upon receipt of a subsequent control plane message (that is, subsequent to the control plane message from which the parameters related to the user or user equipment were captured), the apparatus, such as the processor, may be configured to determine whether the subsequent control plane message has the same parameter that serves as the control plane key and, if so, to thereafter associate the subsequent control plane message with the one or more parameters related to the user or user equipment that were captured from the prior control plane message.
  • the binding provided by the apparatus, such as the processor, in this example embodiment based upon the parameter that serves as the control plane key is based upon a recognition that the subsequent control plane message relates to the same user or user equipment in the same context as that for which the one or more parameters related to the user or user equipment were previously captured.
  • the one or more parameters related to the user or user equipment may also be relevant to the subsequent control plane message.
  • the apparatus 40 of this example embodiment does, however, take into account the possibility that the subsequent control plane message may modify or change the parameter(s) related to the user or user equipment that were previously captured from a prior control plane message as described above in conjunction with block 54.
  • the parameter(s) related to the user or user equipment may change over the course of time or may be unbound from the user or user equipment in some situations.
  • the apparatus of this example embodiment also includes means, such as the processor 42, the memory 44 or the like, for updating the one or more parameters related to the user or user equipment based upon the subsequent control plane message. See block 62 of Figure 3.
  • the apparatus such as the processor, is configured to identify one or more parameters related to the user or the user equipment from the subsequent control plane message and to compare those parameter(s) to the one or more parameters related to the user or user equipment that were captured from the prior control plane message. In instances in which this comparison reveals that one or more of the parameters related to the user or the user equipment have changed or been unbound from the user or user equipment, the apparatus, such as the processor, is configured to update the parameter(s) related to the user or user equipment by modifying the parameter(s) related to the user or user equipment to be the parameter(s) identified from the subsequent control plane message since the subsequent control plane message is more recent than the prior control plane message from which the parameter(s) were captured.
  • the updated parameter(s) related to the user and user equipment may, in turn, be stored, such as in memory.
  • the apparatus 40 embodying the monitoring and control function in accordance with an example embodiment also includes means, such as the processor 42, the communication interface 46 or the like, for causing the one or more parameters related to the user or user equipment to be provided to a respective MEC server 12.
  • the one or more parameters related to the user or user equipment may be pushed to the respective MEC server following capture by the apparatus and without a request for the parameters from the respective MEC server.
  • the apparatus such as the processor, memory 44 or the like, may store the one or more parameters related to the user or user equipment and may provide the one or more parameters related to the user or user equipment in response to a request from a respective MEC server.
  • the request by the respective MEC server may be made in response to the execution of an application by the MEC server that requires the one or more parameter related to the user or user equipment.
  • the respective MEC server may then utilize the one or more parameters related to the user or user equipment in conjunction with the execution of the MEC application that requires the parameter(s), such as for the provision of location services, presence services, or other user or user equipment specific services.
  • Figure 4 depicts a signal flow diagram in an instance in which the user equipment attaches to a network, such as shown in Figure 1.
  • the user equipment 14 may issue an attach request including one or more parameters associated with the attach request and/or the user equipment.
  • the MME 18 receives the attach request and creates a session request that is directed to the S-GW 20.
  • this session request may be provided via the SI 1 interface between the MME and the S- GW and, as such, may be provided as control plane signaling within the trusted part of the network so as not to be ciphered.
  • the apparatus 40 embodying the monitoring and control function, such as the processor 42, the communication interface 46 or the like, monitors the control plane signaling between the MME and the S-GW and determines whether the control plane message references an access point, e.g., an eNB 16, associated with one or more of the MEC servers 12 served by the apparatus.
  • an access point e.g., an eNB 16
  • the apparatus such as the processor, the memory 44 or the like, captures one or more parameters related to the user or user equipment, such as the access point or cell ID, the IMSI, the user equipment ID, the connection ID, the TEID, location information or the like, as shown in operation 3 of Figure 4.
  • the apparatus embodying the monitoring and control function such as the processor, the communication interface or the like, may also identify a first parameter that is common to the control plane messages in the current context of the user or user equipment so as to serve as the control plane key.
  • the one or more parameters related to the user or user equipment as well as the control plane key may be stored, such as in memory.
  • the S-GW 20 of this example embodiment may issue a request for an IP address for the new IP context of the user equipment 14 from a packet data network gateway (P-GW) 22 and may, in turn, receive a response providing the IP address.
  • P-GW packet data network gateway
  • the S-GW may create and provide a session response directed to the MME 18.
  • the session response may be provided via the SI 1 interface as control plane signaling.
  • the apparatus 40 embodying the monitoring and control function, such as the processor 42, may again monitor the control plane signaling and, in particular, the session response.
  • the apparatus may capture any additional parameters relating to the user or user equipment, such as the IP address, and may correspondingly store the additional parameter(s) relating to the user and/or user equipment.
  • the apparatus is also configured to identify a second parameter that is common to the message exchange between the MME and the S-GW as well as to the user plane traffic between the access point and the S-GW with the second parameter then being stored in association with the parameters relating the user or user equipment so as to serve as a user plane fetch key.
  • FIG. 5 another example of the operations performed by the apparatus 40 embodying the monitoring and control function is provided in conjunction with the performance of an update action by the user equipment 14, such as a context update, e.g., a PDP context update or a tracking area update.
  • a context update e.g., a PDP context update or a tracking area update.
  • the user equipment may issue a request including one or more parameters for an update action to the MME 18.
  • the MME may, in turn, issue an action request to the S-GW 20 providing, for example, the user connection ID and one or more additional parameters. See signal 2 of Figure 5.
  • the action request is a form of control plane signaling and is monitored by the apparatus, such as the processor 42.
  • the apparatus such as the processor, is configured to determine whether the access point referenced by the control plane message is associated with a MEC server 12 served by the apparatus and, if so, evaluates the control plane message to identify whether one or more parameters related to the user or user equipment have been updated relative to the corresponding parameter(s) captured and stored previously, such as described above in conjunction with block 54 of Figure 3.
  • the updated parameter(s) are also captured and stored, such as in memory 44, thereby effectively updating the one or more parameters related to the user or user equipment.
  • the S-GW of this example embodiment may then communicate via a request and a response with the P-GW 22 in order to obtain updated or new parameters and may then provide an action response as shown by signal 5 via control plane signaling to the MME.
  • the action response may include the user and/or connection ID and one or more parameters, such as the updated or new parameters obtained by the S-GW.
  • the apparatus 40 embodying the monitoring and control function may again determine whether the control plane message references an access point associated with one or more MEC servers 12 served by the apparatus and, if so, determine whether the one or more parameters related to the user or user equipment 14 have changed relative to the corresponding parameter(s) that were previously captured and stored. If one or more parameters related to the user or user equipment have changed, the updated version of the parameter(s) may be captured and stored.
  • the apparatus such as the processor 42, of this example embodiment identifies if the user plane fetch key that is common to the control plane messages and to the user plane traffic involving the access point has changed relative to the user plane fetch key that was previously stored.
  • the apparatus such as the processor, of this example embodiment is configured to identify the parameter that is now common to the control plane messages and to the user plane traffic involving the access point and to save this parameter as the updated version of the user plane fetch key.
  • the apparatus 40 such as the processor 42, of an example embodiment is configured to determine whether a control plane message references an access point associated with one or more MEC servers 12 by monitoring both request messages and response messages to determine whether the request and response messages reference the access point associated with one or more MEC servers.
  • both the request and response messages are forms of control plane signaling occurring within the trusted portion of the network and, as such, are not ciphered. This control plane signaling may therefore be monitored by the apparatus in order to capture and update one or more parameters related to the user or user equipment 14, as described above.
  • the apparatus 40 of an example embodiment may include means, such as the processor 42, the communication interface 46 or the like, for receiving a request for the one or more parameters related to the user or user equipment 14 with the request being associated with the user plane fetch key.
  • a MEC server 12 that is executing an application requiring the one or more parameters related to the user or user equipment may issue a request to the apparatus for the one or more parameters relating to user or user equipment along with the user plane fetch key.
  • the apparatus such as the processor, the memory 44 or the like, may identify the one or more parameters related to user or user equipment as being those parameters associated with user plane fetch key and may provide means, such as the processor, the communication interface or the like, for causing the one or more parameters related to the user or the user equipment to be provided in response to the request associated with user plane fetch key. Thereafter, the MEC server may utilize the one or more parameters related to the user or user equipment in conjunction with an application executed by the MEC server.
  • handover message may be provided by an access point, e.g., eNB 16, including one or more parameters.
  • the MME 18 of this example embodiment may receive the handover message and, may, in turn, issue an action request as represented by signal 2 including the user and/or connection ID and one or more parameters via control plane signaling to the S-GW 20.
  • the apparatus 40 embodying the monitoring and control function monitors the control plane signaling between the MME and the S-GW and, as shown by operation 3 of Figure 6, determines whether the access point referenced by the control plane message, such as the access point that issued the handover message, is associated with, that is, served by one or more MEC servers served by the apparatus.
  • the apparatus such as the processor 42, determines in operation 3 whether the control plane signaling includes one or more parameters related to the user or user equipment that have been updated or otherwise changed relative to the corresponding parameter(s) previously captured and stored relating to the user or the user equipment.
  • the apparatus such as the processor, is configured to update the corresponding parameter (s) related to the user or user equipment so as to represent the changed version of the parameter.
  • the apparatus 40 of this example embodiment also includes means, such as the processor 42 or the like, for determining, in response to the handover message, whether the MEC server 12 serving the user equipment 14 will change upon handover.
  • the apparatus such as the processor, may be configured to determine based upon the access node or cell ID included within the handover message whether the MEC server that serves the user equipment will change upon the handover.
  • the handover message may identify the access node to which the user equipment is being handed over and the apparatus, such as the processor, of this example embodiment may be configured to identify the MEC server that serves the access node to which the user equipment is being handed over and to thereafter determine whether the MEC server that will serve the user equipment following the handover is the same MEC server as that which currently serves the user equipment or is a different MEC server.
  • the apparatus determines that the MEC server that will serve the user equipment will change upon handover
  • the apparatus collects the contact information of the MEC server that currently serves the user equipment and/or the MEC server that will serve the user equipment following the handover, such as based upon contact information for the plurality of MEC servers stored, for example, in memory 44.
  • the apparatus 40 of this example embodiment also includes means, such as the processor 42, the communication interface 46 or the like, for causing a message to be provided, such as in an instance in which the MEC server 12 will change upon handover, to the one or more MEC servers 12 providing contact information.
  • the apparatus such as the processor, may be configured to provide contact information for the respective MEC server serving user equipment prior to handover and/or for the second MEC server that will serve the user equipment following the handover.
  • the apparatus such as the processor, may be configured to provide the respective MEC server that serves the user equipment prior to handover with contact information for the second MEC server that will serve the user equipment following the handover and/or may be configured to provide the second MEC server that will serve the user equipment following the handover with contact information of the respective MEC server that currently serves the user equipment prior to the handover.
  • the apparatus such as the processor, may be configured to provide one or more parameters related to the user or user equipment. As shown in operation 5 of Figure 6, in an instance in which the MEC server that will serve the user equipment will change upon handover, the respective MEC server and the second MEC server may commence preparations for session mobility and/or session continuation.
  • the S-GW 20 may communicate with the P-GW 22, such as via a request and response in order to obtain updated or new parameters related to the user or the user equipment 14. As represented by signal 7, the S-GW may then provide an action response to the MME 18 including the user and/or connection ID and one or more parameters.
  • the apparatus 40 embodying the monitoring and control function may again determine whether the control plane message references an access point associated with one or more MEC servers 12 served by the apparatus and, if so, determine whether the one or more parameters related to the user or user equipment 14 have changed relative to the corresponding parameter(s) that were previously captured and stored.
  • the updated version of the parameter(s) may be captured and stored.
  • the apparatus, such as the processor 42, of this example embodiment identifies if the user plane fetch key that is common to the control plane messages and to the user plane traffic involving the access point has changed relative to the user plane fetch key that was previously stored. In an instance in which the user plane fetch key has changed, the apparatus, such as the processor, of this example embodiment is configured to identify the parameter that is now common to the control plane messages and to the user plane traffic involving the access point and to save this parameter as the updated version of the user plane fetch key.
  • the apparatus 40 such as the processor 42, the communications interface 46 or the like, may be configured to provide an additional message (see signal 9 of Figure 6) to the one or more MEC servers 12, such as the second MEC server that will serve the user equipment 14 following the handover, providing or more parameters relating to the user or user equipment, particularly in instances in which the one or more parameters relating the user or user equipment have been updated or otherwise modified.
  • the message provided by the apparatus such as the processor, may include the user and/or connection ID and/or the user plane fetch key.
  • the MEC server such as the second MEC server that will serve the user equipment following the handover, may then utilize the information provided the apparatus, such as in support of the applications executed thereby.
  • the signal flow diagram illustrates the setup of a session by the user equipment 14 that is routed to and/or via an application executed by a MEC server 12.
  • the MEC server may fetch the one or more parameters related to the user or user equivalent for use in the application session.
  • the user equipment may provide an application data packet/flow to a respective MEC server.
  • the user equipment may establish an application session that is routed to and/or via an application executed by the respective MEC server.
  • the respective MEC server detects that the application needs one or more parameters related to the user or user equipment, such as the IP address, the user equipment ID, etc.
  • the respective MEC server is configured to identify the user plane fetch key, such as the user plane TEID from the user plane protocol frame/packet, and to utilize the user plane fetch key as a key to obtain the one or more parameters related to the user or user equipment from the apparatus of an example embodiment, as shown by operation 2 of Figure 7.
  • the respective MEC server may request from the apparatus embodying the monitoring and control function all parameters related to the user or user equipment
  • the respective MEC server of an example embodiment may also identify the particular parameters related to the user or user equipment that are requested.
  • the apparatus embodying the monitoring and control function may receive a request from the respective MEC server including, for example, the user plane fetch key and optionally identifying information for one or more parameters related to the user or user equipment.
  • the apparatus 40 such as the processor 42, may then obtain the one or more parameters related to the user or user equipment 14, such as the one or more particular parameters related to the user or user equipment identified by the respective MEC server 12 from memory 44 based upon the association of the parameter related to the user or user equipment with the user plane fetch key, as shown by operation 4 of Figure 7.
  • the apparatus such as the processor, the communication interface 46 or the like, of this example embodiment may then provide a message as represented by signal 5 to the respective MEC server that provides the one or more parameters related to the user or user equipment, such as the IMSI, the IP address of the user equipment, location information associated with the user equipment, the UE ID, etc.
  • the respective MEC server will then utilize the one or more parameters related to the user or user equipment during execution of the application.
  • the respective MEC server may provide one or more parameters related to the user or user equipment to the application or may map a network confidential parameter to a non-confidential and/or public parameter for provision to the application based upon the one or more parameters related to the user or user equipment.
  • the apparatus 40 embodying the monitoring and control function may be utilized, such as by a MEC server 12, to send a control plane message to the MME 18, the radio network and/or the user equipment 14.
  • a MEC server 12 may be utilized, such as by a MEC server 12, to send a control plane message to the MME 18, the radio network and/or the user equipment 14.
  • problems associated with the control plane messaging being encrypted between the MME and the radio network and/or the user equipment may be effectively circumvented.
  • the MEC server may be unable to effectively communicate utilizing control plane messaging that is encrypted.
  • the respective MEC server and, in turn, the apparatus embodying the monitoring and control function utilize the trusted portion of the network that allows for unencrypted control plane messaging to the MME which, in turn, sends an encrypted version of the control plane messaging to the radio network and/or the user equipment.
  • the use of the apparatus embodying the monitoring and control function by the MEC server to send control plane messages to the MME, the radio network and/or the user equipment may serve various purposes.
  • the apparatus 40 embodying the monitoring and control function 24 includes the means, such as the processor 42, the communications interface 46 or the like, for receiving a control plane message from the respective MEC server 12.
  • the apparatus may receive various control plane messages.
  • the respective MEC server utilizes the apparatus embodying the monitoring and control function in order to trigger the MME 18 to send and/or activate paging for one or more user equipment 14.
  • the apparatus of this example embodiment also includes means, such as the processor, the
  • control plane message from the respective MEC server may be transmitted within the trusted portion of the network so as to be an unencrypted form of control plane signaling.
  • the control plane message that is transmitted by the apparatus embodying the monitoring and control function may be directed, for example, to the MME 18, such as via a downloading data notification message to the MME, which, in turn, causes control plane signaling to the radio network and/or to one or more user equipment, such as in an encrypted form in order to trigger paging of the user equipment.
  • the paging of one or more user equipment may be instigated by the respective MEC server for various reasons including, for example, as required by an application executed by the respective MEC server.
  • the paging of the user equipment may be the only technique to obtain the location information for the user equipment that is required in conjunction with a location service application executed by the respective MEC application.
  • the MEC server 12 may detect a need to get or determine the location of the user equipment 14 and/or the state of the user equipment. In instances in which the user equipment is within the paged area, but is in the idle state, the location of the user equipment may then be acquired by paging the user equipment. As shown by operation 1 of Figure 8, the MEC server may identify a requirement to obtain the location of the user equipment. The requirement to obtain the location of the user equipment may be identified in various manners, for example such as a request or subscription from an application.
  • the MEC server of an example embodiment may have verified that the P-GW 22/S-GW 20 has requested that changes to the location of the user equipment be reported (from the MME 18) to the packet core network, such as to the P-GW, or the MEC server may itself have sent a request, such as via the apparatus 40 embodying the monitoring and control function 24, and, as such may cause a request to be sent via the apparatus embodying the monitoring and control function to the MME to report changes to the location of the user equipment (from the MME) to the packet core network, such as to the P-GW.
  • the MEC server may send a request to the apparatus embodying the monitoring and control function along with the identity of the user and/or user equipment and one or more other parameters as represented by signal 2.
  • the apparatus 40 embodying the monitoring and control function 24 and the MME 18 may exchange a downlink data notification including one or more parameters and a downlink data notification acknowledgement (ACK).
  • the MME may then page and/or send a paging request to the access node, such as the eNB 16, which, in turn, pages the user equipment. See signals 5 and 6 of Figure 8.
  • a radio bearer may then be established between the user equipment and the access node and a message indicating that the initial context setup is complete may be issued by the access node, such as the eNB, to the MME. See signals 7 and 8 of Figure 8.
  • This message may include the location of the user equipment and one or more parameters.
  • the MME and the apparatus embodying the monitoring and control function may then exchange a modify bearer request including the location of the user equipment and one or more parameters and a modify bearer response, as indicated by signals 9 and 10.
  • the apparatus embodying the monitoring and control function may then issue a response including the location of the user equipment and one or more parameters to the MEC server, thereby providing the MEC server with the location of the user equipment.
  • the user equipment may be determined to be within the paged area based upon the paging of signal 6 and the parameters provided with the response may indicate the current state of the user equipment, such as the idle state.
  • a method, apparatus 40 and computer program product are therefore provided in accordance with an example embodiment in order to capture one or more parameters related to a user or user equipment 14 and to cause those parameters to be provided to a respective MEC server 12.
  • the method, apparatus and computer program product of an example embodiment arms the MEC server with the information required by applications that are reliant upon the information relating to the user or the user equipment.
  • the method, apparatus and computer program product of an example embodiment capture the information relating to the user or the user equipment in such a manner as to identify instances in which the information relating to the user or the user equipment changes and the parameter(s) stored by a respective MEC server must be dynamically updated, as well as instances in which the information is released or unbound from the user or user equipment and parameter(s) stored by the respective MEC server must again be updated. Further, the method, apparatus and computer program product of an example embodiment facilitate handover from a first MEC server to a second MEC server with the second MEC server being provided information regarding the user or user equipment now being served by the second MEC server following the handover, thereby increasing the reliability and reducing the latency associated with such a handover.
  • Figure 3 illustrates a flowchart of an apparatus 40, method, and computer program product according to example embodiments of the disclosure. It will be understood that each block of the flowchart, and combinations of blocks in the flowchart, may be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by the memory device 44 of an apparatus employing an embodiment of the present invention and executed by the processor 42 of 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 implements the functions specified in the flowchart blocks.
  • These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer -readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
  • blocks of the flowchart support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by special purpose hardware -based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

Abstract

L'invention concerne un procédé, un appareil et un produit de programme informatique destinés à capturer un ou plusieurs paramètres associés à un utilisateur ou à un équipement utilisateur et à amener lesdits paramètres à être fournis à un serveur d'informatique de périphérie de réseau multi-accès (MEC) respectif de façon à prendre en charge, par exemple, l'exécution d'applications, lesquelles sont basées sur les informations associées à l'utilisateur ou à l'équipement utilisateur. Selon un procédé, des messages de plan de commande sont surveillés et il est déterminé si un message de plan de commande référence un point d'accès associé à un serveur MEC. Dans une instance dans laquelle le message de plan de commande référence un point d'accès associé à un serveur MEC, le procédé capture un ou plusieurs paramètres associés à un utilisateur ou à un équipement utilisateur associé au message de plan de commande. Le procédé consiste en outre à amener le ou les paramètres associés à l'utilisateur ou à l'équipement utilisateur à être fournis à un serveur MEC respectif.
PCT/IB2017/051049 2017-02-23 2017-02-23 Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès WO2018154355A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2017/051049 WO2018154355A1 (fr) 2017-02-23 2017-02-23 Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2017/051049 WO2018154355A1 (fr) 2017-02-23 2017-02-23 Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès

Publications (1)

Publication Number Publication Date
WO2018154355A1 true WO2018154355A1 (fr) 2018-08-30

Family

ID=63253154

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2017/051049 WO2018154355A1 (fr) 2017-02-23 2017-02-23 Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès

Country Status (1)

Country Link
WO (1) WO2018154355A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109347739A (zh) * 2018-11-14 2019-02-15 电子科技大学 为多接入边缘计算提供资源配置和接入点选择策略的方法
US10819434B1 (en) 2019-04-10 2020-10-27 At&T Intellectual Property I, L.P. Hybrid fiber coaxial fed 5G small cell surveillance with hybrid fiber coaxial hosted mobile edge computing
CN111970369A (zh) * 2020-08-25 2020-11-20 浙江大华技术股份有限公司 无接触的设备控制方法及装置
US10848988B1 (en) 2019-05-24 2020-11-24 At&T Intellectual Property I, L.P. Dynamic cloudlet fog node deployment architecture
CN112954736A (zh) * 2019-12-10 2021-06-11 深圳先进技术研究院 基于策略的无线携能物联网设备的计算卸载
CN114980033A (zh) * 2021-02-26 2022-08-30 维沃移动通信有限公司 原生算力业务实现方法、装置、网络设备及终端

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2159964A1 (fr) * 2008-09-02 2010-03-03 Icom Incorporated Réseau de communication sans fil apte à considérer la localisation des utilisateurs
WO2016134772A1 (fr) * 2015-02-26 2016-09-01 Nokia Solutions And Networks Oy Facturation et commande de services périphériques
WO2017012674A1 (fr) * 2015-07-23 2017-01-26 Nokia Solutions And Networks Oy Commande de fonction d'accélération dans un réseau
US20170048876A1 (en) * 2015-08-14 2017-02-16 Nec Laboratories America, Inc. Enabling high-bandwidth, responsive mobile applications in lte networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2159964A1 (fr) * 2008-09-02 2010-03-03 Icom Incorporated Réseau de communication sans fil apte à considérer la localisation des utilisateurs
WO2016134772A1 (fr) * 2015-02-26 2016-09-01 Nokia Solutions And Networks Oy Facturation et commande de services périphériques
WO2017012674A1 (fr) * 2015-07-23 2017-01-26 Nokia Solutions And Networks Oy Commande de fonction d'accélération dans un réseau
US20170048876A1 (en) * 2015-08-14 2017-02-16 Nec Laboratories America, Inc. Enabling high-bandwidth, responsive mobile applications in lte networks

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109347739A (zh) * 2018-11-14 2019-02-15 电子科技大学 为多接入边缘计算提供资源配置和接入点选择策略的方法
CN109347739B (zh) * 2018-11-14 2021-06-22 电子科技大学 为多接入边缘计算提供资源配置和接入点选择策略的方法
US10819434B1 (en) 2019-04-10 2020-10-27 At&T Intellectual Property I, L.P. Hybrid fiber coaxial fed 5G small cell surveillance with hybrid fiber coaxial hosted mobile edge computing
US11146333B2 (en) 2019-04-10 2021-10-12 At&T Intellectual Property I, L.P. Hybrid fiber coaxial fed 5G small cell surveillance with hybrid fiber coaxial hosted mobile edge computing
US11558116B2 (en) 2019-04-10 2023-01-17 At&T Intellectual Property I, L.P. Hybrid fiber coaxial fed 5G small cell surveillance with hybrid fiber coaxial hosted mobile edge computing
US10848988B1 (en) 2019-05-24 2020-11-24 At&T Intellectual Property I, L.P. Dynamic cloudlet fog node deployment architecture
US11503480B2 (en) 2019-05-24 2022-11-15 At&T Intellectual Property I, L.P. Dynamic cloudlet fog node deployment architecture
US11974147B2 (en) 2019-05-24 2024-04-30 At&T Intellectual Property I, L.P. Dynamic cloudlet fog node deployment architecture
CN112954736A (zh) * 2019-12-10 2021-06-11 深圳先进技术研究院 基于策略的无线携能物联网设备的计算卸载
CN111970369A (zh) * 2020-08-25 2020-11-20 浙江大华技术股份有限公司 无接触的设备控制方法及装置
CN114980033A (zh) * 2021-02-26 2022-08-30 维沃移动通信有限公司 原生算力业务实现方法、装置、网络设备及终端

Similar Documents

Publication Publication Date Title
JP6409871B2 (ja) モバイルネットワークにおける複数のパケットサービスの再開
WO2018154355A1 (fr) Procédé et appareil de capture de paramètres d'utilisateur ou d'équipement utilisateur dans un système informatique de périphérie de réseau multi-accès
US8665716B2 (en) Enabling circuit-switched services during mobility management congestion control
US20210112483A1 (en) Processing method, terminal, and network element
WO2018112897A1 (fr) Procédé et dispositif d'activation de session, et système
US20230209328A1 (en) Method and device for establishing session
US9794874B2 (en) Electronic device and method for signal transmission and reception
US20120207011A1 (en) Method and apparatus for responding to an unrecoverable error
KR102055198B1 (ko) 영상 통화 중 증강 현실 컨텐츠 제공 방법을 위한 프로그램을 기록한 컴퓨터 판독 가능한 기록매체 및 이를 위한 장치
EP3531619B1 (fr) Procédé, dispositif et système de programmation de fonction
US10631199B2 (en) Method for allowing user equipment to detach from network entity
US11082893B2 (en) Session migration method and device applied to a UE tracking area update
WO2018166328A1 (fr) Procédé de traitement d'informations, appareil, support d'informations lisible par ordinateur et dispositif électronique
WO2022007484A1 (fr) Procédé de redirection, dispositif de réseau, dispositif terminal et support de stockage lisible
EP2850912B1 (fr) Distribution efficace de messages de signalisation dans une passerelle d'accès de mobilité ou un dispositif d'ancrage de mobilité locale
WO2020034802A1 (fr) Procédé et dispositif d'activation de session pdu
CN110913505A (zh) 一种下行数据缓存方法、网络设备及upf实体
WO2017035723A1 (fr) Procédé et appareil de radiomessagerie pour passerelle répartie
US20210243657A1 (en) Communication method, core network device, access network device, terminal device, and communication system
JP2020536399A (ja) データ伝送方法及びネットワークデバイス
US20190387397A1 (en) Lawful Interception Method, Apparatus, And System
GB2511540A (en) Wireless communication system and method
WO2012156943A1 (fr) Procédés et appareil d'activation de services à commutation de circuits
US20150334196A1 (en) Method and apparatus for preserving packet switched (ps) signaling connection
GB2490948A (en) Indicating in mobility management rejection messages that circuit-switched services are permitted during congestion

Legal Events

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

Ref document number: 17898178

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17898178

Country of ref document: EP

Kind code of ref document: A1