WO2019001174A1 - 一种应用实例地址的转换方法和装置 - Google Patents

一种应用实例地址的转换方法和装置 Download PDF

Info

Publication number
WO2019001174A1
WO2019001174A1 PCT/CN2018/087860 CN2018087860W WO2019001174A1 WO 2019001174 A1 WO2019001174 A1 WO 2019001174A1 CN 2018087860 W CN2018087860 W CN 2018087860W WO 2019001174 A1 WO2019001174 A1 WO 2019001174A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
target
instance
application service
application
Prior art date
Application number
PCT/CN2018/087860
Other languages
English (en)
French (fr)
Inventor
金爱进
张丰裕
王岩
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21168289.3A priority Critical patent/EP3920595A1/en
Priority to EP18823492.6A priority patent/EP3627897B1/en
Publication of WO2019001174A1 publication Critical patent/WO2019001174A1/zh
Priority to US16/710,449 priority patent/US11140665B2/en
Priority to US17/493,580 priority patent/US11696290B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/087Mobility data transfer for preserving data network PoA address despite hand-offs
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2521Translation architectures other than single NAT servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0069Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node

Definitions

  • the present application relates to the field of communications, and in particular, to a method and apparatus for converting an application instance address.
  • the current network (commercial wireless network 2G/3G/Long Term Evolution (English term: LTE)) is a converged network.
  • the service has a low latency requirement, and the terminal accesses the service through a centralized deployment gateway.
  • the access delay of the terminal to the service is about 100ms.
  • the future mobile network will deploy a micro cloud platform at the edge of the network (for example, close to the base station), that is, mobile edge computing/mobile edge cloud (English full name: Mobile Edge Computing/Cloud , English abbreviation: MEC) platform.
  • Each application instance of the service provides services for terminals within a certain range.
  • the terminal moves from one service area to another service area of the application instance of the service, the terminal needs to access an application instance corresponding to another service area.
  • the application state relocation of the application instance needs to be performed when accessing the application instance of another service area
  • the application state migration includes: application layer user state migration, network connection (socket) migration, and IP (English full name Internet Protocol) address and transmission path mobility (English abbreviation: IP Mobility) processing.
  • IP Mobility International Mobile Mobility
  • the existing migration technology is: after the application instance is changed, the user device needs to send the service device corresponding to the source application instance to the service device corresponding to the source application instance, and the service corresponding to the source application instance.
  • the device performs destination address translation (English name: Destination Network Address Translation, English abbreviation: DNAT), and then the service device corresponding to the source application instance forwards the packet to the service device corresponding to the destination application instance, and finally forwards it to the destination application.
  • destination address translation English name: Destination Network Address Translation, English abbreviation: DNAT
  • the problem of this technology is that the uplink path is detoured.
  • the uplink packet needs to be sent to the first serving device and then forwarded to the destination service device, thus causing network delay during the terminal migration process. Higher, affecting the user experience.
  • the present application provides a method and apparatus for converting an application instance address, which is used to reduce network delay of a terminal during a mobile process.
  • the application provides a method for converting an application instance address, including:
  • the control plane device sends the information of the application service accessed by the terminal and the location of the terminal to the mobile edge cloud MEC control device through the collaborative request. After acquiring the address of the target instance according to the information of the application service and the location information of the terminal, the MEC control device sends the address of the target instance to the control plane device by using a response message.
  • the control plane device generates an address translation policy according to the address of the target instance, and sends the policy to the first user equipment, where the policy is used to indicate the first user plane device: the uplink message sent by the terminal to obtain the application service.
  • the destination forwarding address is set to the address of the target instance.
  • the terminal After the terminal moves from one service area to another, although the application instance of the accessed application service changes, the terminal does not perceive.
  • the terminal can still send the uplink packet by using the address of the application instance that is connected to the application service.
  • the network side can forward the uplink packet sent by the terminal to the new application instance. In this way, the terminal can send packets without establishing a connection with the new application instance, which reduces network delay.
  • the foregoing method may further include:
  • the control plane device obtains an initial instance address when the terminal accesses the application service according to the address of the application instance that the terminal currently communicates with.
  • the control plane device generates an address translation policy for the downlink packet according to the obtained initial instance address, and sends the policy to the first user equipment, where the policy is a downlink packet indicating that the first user equipment sends the target instance to the terminal.
  • the source address is set to the initial instance address.
  • the terminal may not be able to identify the source address of the downlink packet for the downlink packet sent by the new application instance.
  • the network side needs to set the source address of the downlink packet as the initial instance address when the terminal accesses the application service. In this way, in the process of the terminal accessing the application service, the terminal can not only identify the downlink packet sent by the new application instance, but also does not perceive that the network side has replaced the new application instance, so that the terminal does not need to establish a connection with the new application instance. , reducing network latency.
  • the foregoing method may further include:
  • the control plane device receives a handover request sent by the original access network AN or the target AN, and the handover request is used to request to switch the terminal from the original AN to the target AN;
  • the control plane device queries the user plane device corresponding to the target AN. If there are multiple user plane devices corresponding to the target AN, the control plane device selects at least one user plane device, and selects at least one user plane device. The information is sent to the MEC control device through a collaborative request. The MEC control device determines which of the at least one user plane can be used, and determines which one corresponds to the MEC platform served by the target AN, thereby determining the first user plane device.
  • the MEC Ctl then sends the determined information of the first user plane device to the control plane device through a response message.
  • the control plane device creates a session between the terminal and the first user plane device.
  • the first user plane device is determined by the control plane device and the MEC control device, which reduces the situation that the determined user plane device cannot be used because the user plane device is determined by a single network element.
  • the application provides a method for converting an application instance address, including:
  • the mobile edge cloud MEC control device receives a collaboration request sent by the control plane device, where the cooperation request includes location information of the terminal and information of the application service accessed by the terminal.
  • the MEC control device determines the MEC platform according to the location information of the terminal, determines the target instance according to the information of the application service, and obtains the address of the target instance.
  • the MEC control device sends the obtained address of the target instance to the control plane device through the response message, so that the control plane device formulates an address translation policy according to the target instance, and instructs the first user plane device to send the target instance to the terminal.
  • the source address is set to the initial instance address.
  • the location information of the terminal includes information of the target AN accessed by the terminal;
  • the MEC control device determines that the target instance can be based on the location information of the terminal and the information of the application service:
  • the MEC control device determines which MEC platforms the target AN serves, and then determines which MEC platform of the MEC platform deploys the application instance of the application service, thereby determining the first MEC platform and the target deployed on the first MEC platform.
  • the application provides a method for converting an application instance address, including:
  • the control plane device sends the information of the application service accessed by the terminal and the location of the terminal to the mobile edge cloud MEC control device through the collaborative request. After determining the first MEC platform according to the information of the application service and the location information of the terminal, the MEC control device sends the identifier of the first MEC platform to the control plane device by using a response message.
  • the control plane device After receiving the identifier of the first MEC platform, the control plane device sends a packet forwarding indication to the first user plane device, and instructs the first user plane device to send the packet that the terminal accesses the application service to the first MEC platform, to The first MEC platform is caused to perform address translation on the packet.
  • the MEC platform has the function of address translation, and the MEC platform can formulate corresponding address translation strategies and perform corresponding address translation operations, thereby reducing the load on the control plane device and the user plane device.
  • the response message further includes service flow feature information
  • the service flow feature information is created by the MEC control device according to the address of the terminal and the service address and the instance address of the application service.
  • the control plane device further instructs the first user plane device to: determine the target message according to the service flow characteristic information.
  • the application provides a method for converting an application instance address, including:
  • the mobile edge cloud MEC control device receives a collaboration request sent by the control plane device, where the cooperation request includes location information of the terminal and information of the application service accessed by the terminal.
  • the MEC control device determines the first mobile edge cloud MEC platform that provides the application service according to the location information of the terminal.
  • the MEC control device sends the determined identifier of the first MEC platform to the control plane device by using a response message, and instructs the control plane unit to: control the first user plane device to send the packet of the terminal accessing the application service to the first MEC platform,
  • the first MEC platform is caused to perform address translation on the packet.
  • the foregoing method may further include:
  • the MEC control device acquires the service address of the application service and the target instance address, and creates service flow feature information.
  • the MEC control device sends the created service flow feature information to the control plane device through the response message, and instructs the control plane device to: control the first user plane device to determine the target packet according to the service flow feature information.
  • the application provides a method for converting an application instance address, including:
  • the mobile edge cloud MEC platform receives the packet of the application service accessed by the terminal accessed by the first user plane device.
  • the MEC platform determines that the packet is an uplink packet or a downlink packet. If the packet is an uplink packet, the MEC platform sets the destination forwarding address of the packet to the address of the application instance deployed by the application service in the MEC platform. If the packet is a downlink packet, the MEC platform sets the source address of the packet to the service address of the target application service.
  • the obtained access address is the service address of the application service. Therefore, in any serving cell, the terminal accesses the uplink packet of the application service through address translation to be sent to the corresponding application instance, and all downlink packets need to undergo address translation before being sent to the terminal, so that the terminal can enable the terminal to Identify it.
  • the operation of address translation is performed by the MEC platform. If the application instance of the application service is deployed on the MEC platform, the MEC platform must be able to know the service address of the application service and the address of the application instance. In this way, the MEC platform does not need to obtain the address that needs to be converted from other sources, and can directly perform address translation through the local address, which reduces the process of signaling interaction and improves the speed of terminal access.
  • the MEC platform receives the packet of the application service accessed by the terminal accessed by the first user plane device, and the packet may be:
  • the MEC platform receives, by the data plane device, the packet sent by the first user plane device to access the accessed application service, that is, the packet sent by the first user plane device to the MEC platform can be forwarded by the data plane device.
  • the message sent by the MEC platform to the first user plane device can also be forwarded through the data plane device.
  • the method may further include:
  • the MEC platform generates a routing rule according to the configured terminal address network segment, the service address of the application service, and the address of the target instance, and sends the routing rule to the data plane device, indicating that the data plane device: accesses the terminal access according to the routing rule.
  • the application service message is sent to the MEC platform for address translation.
  • the terminal address network segment is used by the data plane device to identify whether the received packet is sent by the terminal or is sent to the terminal. Since the packets sent by other devices to the MEC platform generally do not need address translation, in this way, the occurrence of the foregoing situation is reduced.
  • the application provides a device for converting an application instance address, including:
  • a sending unit configured to send a collaboration request to the mobile edge cloud MEC control device, where the cooperation request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • a receiving unit configured to receive response information from the MEC control device, where the response information includes an address of the target instance, and an address of the target instance is associated with location information of the terminal and information of the application service;
  • the sending unit is further configured to: send, according to the address of the target instance, the address of the target instance to the first user plane device corresponding to the target instance;
  • the processing unit is configured to indicate the first user plane device: set a forwarding address of the uplink packet sent by the terminal for acquiring the application service as an address of the target instance.
  • the application provides an apparatus for converting an application instance address, including:
  • a receiving unit configured to receive a collaborative request from the control plane device, where the collaborative request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • a determining unit configured to determine a target instance of the application service according to the collaborative request
  • An obtaining unit configured to obtain an address of the target instance, where the target instance is an application instance that provides an application service and the service location range includes a location of the terminal;
  • a sending unit configured to send a response message to the control plane device, where the response information includes an address of the target instance, and the address of the target instance is used for address translation of the packet.
  • the application provides an apparatus for converting an application instance address, including:
  • a sending unit configured to send a collaboration request to the mobile edge cloud MEC control device, where the cooperation request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • a receiving unit configured to receive response information from the MEC control device, where the response information includes an identifier of the first mobile edge cloud MEC platform, where the first MEC platform is an MEC platform that provides application services, the identifier of the first MEC platform, and location information of the terminal Information association of application services;
  • the sending unit is further configured to: send the identifier of the first MEC platform to the first user plane device, and instruct the first user plane device to: send the target packet to the first MEC platform, where the target packet is the packet that the terminal accesses the application service. ;
  • a processing unit configured to control a step of the sending unit performing the sending, and controlling the receiving unit to perform the receiving.
  • the application provides an apparatus for converting an application instance address, including:
  • a receiving unit configured to receive a collaborative request from the control plane device, where the collaborative request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • a determining unit configured to determine, according to the collaborative request, an identifier of the first mobile edge cloud MEC platform; wherein the first MEC platform is an MEC platform that provides an application service;
  • a sending unit configured to send, to the control plane device, an identifier of the first MEC platform
  • the processing unit is configured to instruct the control plane unit to: control the first user plane device to send the target packet to the first MEC platform, and the target packet is the packet that the terminal accesses the application service.
  • the application provides an apparatus for converting an application instance address, including:
  • a receiving unit configured to receive a target packet from the first user plane device, where the target packet is a packet that the terminal accesses the application service, and the application service is an application service accessed by the terminal;
  • the setting unit is configured to: if the target packet is an uplink packet, set the forwarding address of the target packet to the address of the target instance, and the address of the target instance is an address of the application instance deployed by the application service in the MEC platform;
  • the setting unit is further configured to: if the target packet is a downlink packet, set a source address of the target packet to a service address of the target application service.
  • the present application provides an apparatus for converting an application instance address, including: a processor, a memory, a transceiver, a processor, a memory, and a transceiver connected by a bus, the memory storing computer instructions, and the processor executing the computer
  • the instructions are for implementing the method as described in the first aspect or the second aspect or the third aspect or the fourth aspect or the aspect.
  • the present application provides a storage medium storing computer instructions for implementing the method as described in the first aspect or the second aspect or the third aspect or the fourth aspect or the aspect .
  • the present application provides a computer program product comprising computer software instructions executable by a processor to implement the first aspect or the second aspect or the third aspect or A process in any of the methods described in any of the four aspects or the first aspect.
  • the present application provides a chip system including a processor, and a conversion device for supporting an application instance address implements functions involved in the above aspects, for example, generating or processing the method involved in the above method. information.
  • the chip system further includes a memory for holding program instructions and data necessary for the conversion device supporting the application instance address.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application has the following advantages:
  • the terminal device When the terminal sends an uplink packet, the terminal device only needs to send the packet according to the original instance address. When the uplink packet reaches the user plane device, the user plane device forwards the uplink packet to the target instance of the application service. In this way, after the terminal moves across the access point service area, the terminal can directly perform message interaction without re-creating the service connection with the new application instance, thereby reducing network delay.
  • FIG. 1 is a schematic diagram of a system architecture applied to a method for converting an application instance address according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of another system applied to a method for converting an application instance address according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of an embodiment of a method for converting an application instance address according to an embodiment of the present application
  • FIG. 4 is a schematic structural diagram of another system applied to a method for converting an application instance address according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of another embodiment of a method for converting an application instance address according to an embodiment of the present application
  • FIG. 6 is a schematic structural diagram of another system applied to a method for converting an application instance address according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of an embodiment of an apparatus for converting an application instance address according to an embodiment of the present application
  • FIG. 8 is a schematic diagram of another embodiment of an apparatus for converting an application instance address according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another embodiment of an apparatus for converting an application instance address according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another embodiment of an apparatus for converting an application instance address according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another embodiment of an apparatus for converting an application instance address according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of another embodiment of an apparatus for converting an application instance address according to an embodiment of the present application.
  • the embodiment of the present application provides a method and an apparatus for converting an application instance address, which are used to reduce network delay of a terminal during a mobile process.
  • FIG. 1 is a schematic diagram of a system architecture applied to a method for converting an application instance address according to an embodiment of the present application.
  • the system architecture includes the terminal (English name: User Equipment, English abbreviation: UE), at least two access points (English full name: Access Node, English abbreviation: AN), control surface (English full name: Control Plane, English abbreviation) :CP) Equipment, MEC centralized control management (English full name: Mobile Edge Computing/Cloud Control, English abbreviation: MEC Ctl) equipment.
  • the system architecture also includes at least two mobile edge hosts (English: Mobile Edge host), and the mobile edge host is also called MEC host.
  • the MEC host is a mobile edge infrastructure.
  • the network structure formed by the network architecture is used to provide a service platform for the application instance.
  • Each MEC host corresponds to a user plane (English name: User Plane, English abbreviation: UP) device.
  • the service device described in the background art may be the user plane device.
  • a separate mobile edge platform (English: Mobile Edge platform) is also installed in each MEC host, and the mobile edge platform is also called MEC platform.
  • At least one application instance is deployed in the MEC platform, and an application instance is represented by an APP (Application) instance in FIG. This application example is used to provide application services for the UE.
  • an application service refers to a service provided by a terminal through various types of applications, such as a video application service operated by a certain developer.
  • the application instance refers to the specific application of the same application service deployed on different MEC platforms. Therefore, one application service can correspond to multiple application instances.
  • the AN is used to access the network when the UE accesses the network service, and receives the measurement report sent by the UE in real time, and is used to detect the signal strength between the UE and other AN points.
  • the AN connected to the UE detects the signal strength between the UE and other ANs and the signal strength between the AN and the UE reaches a mobility threshold, the AN decides to handover the UE to the target AN.
  • the original AN indicates the AN used when the UE first accesses the network
  • the target AN indicates the newly accessed AN after the UE moves.
  • one AN can be connected to one MEC host, or multiple ANs can be connected to one MEC host. In the example of FIG.
  • the AN involved in the present application may be a base station, such as a long term evolution (LTE) evolved base station (English: evolved Node B, abbreviation: eNB), enterprise LTE (English: enterprise LTE, abbreviation: eLTE eNB, new radio access base station (English: new radio gNB, abbreviation: NR gNB), etc., are not limited in this application.
  • LTE long term evolution
  • eNB evolved Node B
  • enterprise LTE English: enterprise LTE, abbreviation: eLTE eNB
  • new radio access base station English: new radio gNB, abbreviation: NR gNB
  • the CP is the core network element, which is used to formulate the packet forwarding policy and control the UP to forward packets according to the packet forwarding policy.
  • the CP is connected to the MEC Ctl, the plurality of ANs, and the UPs on the plurality of MEC hosts.
  • the CP obtains the request information and the service information from the AN and the MEC Ctl, respectively, and formulates the forwarding policy, and sends the forwarding policy to the UP, instructing the UP to forward the packet according to the forwarding policy.
  • the CP receives the handover request sent by the original AN to switch the network connection of the UE to the target AN, and the CP obtains the original instance address and the destination instance address of the application service used by the UE from the MEC Ctl, and the CP according to the original instance.
  • the address and destination instance address are used to formulate a packet forwarding policy.
  • the CP cooperates with the MEC Ctl to determine the target UP, and the CP sends the forwarded policy to the target UP, so that the target UP forwards the packet according to the forwarding policy.
  • the UP is configured to receive the uplink packet sent by the UE, forward the packet to the application instance in the corresponding MEC platform according to the forwarding policy, and forward the downlink packet to the UE according to the forwarding policy when receiving the downlink packet.
  • the MEC Ctl is connected to the MEC platform in multiple MEC hosts, and the MEC Ctl is used to manage and control multiple MEC platforms.
  • a service mobility control (English: Service Mobility Control, shorthand: SM Ctl) device may be set in the MEC C11.
  • MEC Ctl is connected to application instances deployed in multiple MEC platforms through SM Ctl.
  • SM Ctl is used to manage and control application instances on multiple MEC platforms.
  • the SM Ctl stores the application instance deployment information, which includes information about application instances deployed in the MEC platform to which the SM Ctl is connected, and mapping service relationship information between different MEC platforms and different ANs.
  • the MEC Ctl may query, according to the information of the AN, the information of the at least one MEC platform served by the determined AN by using the SM C1.
  • the SM Ctl may also be independent of the MEC Ctl, and the SM Ctl and the MEC Ctl may be connected through an air interface or a wired connection, and the SM Ctl obtains information about the application instance deployed on multiple MEC platforms from the MEC Ctl. .
  • An embodiment of the present application is to set an address translation function on the UP according to the foregoing system architecture.
  • the specific system architecture is as shown in FIG. 2, and the UP translates the destination address of the uplink packet according to the address translation indication established by the CP, and converts the downlink. The original address of the message.
  • the UE After the UE is moved, the UE does not need to be aware of the application instance that has been switched to the new MEC platform, and can perform service access with the new application instance, thereby reducing network delay.
  • the following is a detailed description:
  • an embodiment of a method for converting an application instance address in the embodiment of the present application includes:
  • the original AN or the target AN sends a handover request to the CP.
  • the CP receives a handover request for requesting handover of the UE's network connection from the original AN to the target AN.
  • the UE is connected to the original AN, and accesses the target application instance in the MEC platform through the MEC platform served by the original AN, for example, accessing a video service.
  • the UE moves, the UE switches from the original AN to the target AN, and the original AN/or the target AN sends a handover request to the CP, where the handover request carries the location information of the UE.
  • a handover request may be sent from the original AN to the target AN, and after the target AN feeds back the confirmation information required for the handover, the target AN sends a path switch request preparation message to the CP. That is, the handover request may be a path handover request preparation message sent by the target AN.
  • the original AN sends a handover request to the CP in the handover preparation phase, and the CP sends a handover request message to the target AN, and the target
  • the AN replies with a confirmation message to the handover request message of the CP, and the CP can confirm the handover to the target AN at this time. That is, the above handover request may be a handover request sent by the original AN.
  • the CP reselects the UP according to the location information of the UE and/or the service-related attribute information.
  • the location information of the UE is network location information of the UE, such as: information of the target AN, tracking area information; or the location information of the UE is geographic location information of the UE.
  • the tracking area information is the area information of the UE at the time when the UE reports the location change.
  • the service-related attribute information may be locally configured by the CP, or may be obtained by the CP from the MEC Ctl.
  • the service-related attribute information may refer to attributes of session and service continuity (SSC). The CP judges whether it is possible to reselect UP through the SSC.
  • the CP When the CP determines that the UE needs to perform handover to the target AN, the CP not only needs to cooperate with the MEC Ctl to perform application layer user state migration of the application service, but also needs to perform network connection (Socket) migration.
  • the application service is a video service
  • the user state transition includes: migration of information such as the duration of playing of a video played on the UE and the authentication information of the UE.
  • the migration of the network connection includes: extracting the corresponding session context content of the Socket from the source side device (the source side device includes the original AN and the MEC platform), transmitting to the destination service layer, and installing.
  • the CP also needs to cooperate with the MEC Ctl to migrate the instance address of the application service. This will be further described in connection with step 103.
  • the CP sends a coordination request to the MEC Ctl.
  • the MEC Ctl receives the coordinated request sent by the CP.
  • the CP sends the coordinated request to the MEC Ctl.
  • the location information of the UE needs to be carried, so that the MEC C11 determines whether the service migration needs to be performed according to the location information of the UE. If the migration is required, the corresponding MEC platform is further determined to determine the address of the target application instance in the MEC platform.
  • the location information of the UE included in the cooperation request may include the foregoing location information, or the location information of the UE may also be target UP information or target MEC host information/target MEC platform information.
  • the target UP information is information of the UP selected by the CP, such as the ID of the target UP.
  • the CP searches for the corresponding MEC host or MEC platform according to the target UP, and determines that the MEC host or the MEC platform is the target MEC host or the target MEC platform.
  • the CP can directly select and determine the target UP. For example, the case of serving an AN with an UP.
  • an AN may serve multiple UPs, and when the CP decides to reselect UP, if the UP served by the target AN contains multiple, the CP selects multiple UPs at this time.
  • the CP can request the MEC Ctl to cooperatively determine a unique target UP.
  • the CP may further include information about multiple UPs selected by the CP in the cooperation request sent by the MEC C1.
  • the MEC C1 determines information about the target instance of the target application service according to the location information of the UE, and obtains an address of the target instance.
  • the MEC C11 can be connected to the application instance deployed in each MEC platform through the SM C11, and the information about the application instance deployed in the connected MEC platform is saved in the SM Ctl (application instance deployment information), SM Ctl also stores mapping service relationship information between different MEC platforms and different ANs. Therefore, the MEC Ctl may query the MEC served by the target AN from the application instance deployment information according to the location information of the UE (the location information of the UE may be any one or more of the network location information of the UE described in step 102). platform.
  • the MEC Ctl directly determines the target MEC platform according to the information of the target AN; if the location information of the UE includes the tracking area information, the MEC Ctl may first determine which AN service is available. The area contains the tracking area to determine the target AN, thereby determining the target MEC platform. After determining the target MEC platform, the MEC Ctl may determine the target application instance deployed on the target MEC platform according to the information of the target application service (for example, the identifier of the target application service), thereby obtaining the address of the target application instance.
  • the target application service for example, the identifier of the target application service
  • the CP receives the response information sent by the MEC Ctl.
  • the response information includes an original instance address of the target application service and an address of the target instance, such that the CP sends a request/indication to perform address translation to the target UP according to the response message.
  • the MEC Ctl needs to send the original instance address and the address of the target instance to the CP, so that the CP formulates an address translation policy according to the original instance address and the address of the target instance, thereby instructing the target UP to perform address translation.
  • the CP needs to request the MEC C1 to obtain the address of the application instance of the MEC platform corresponding to the original AN.
  • the original instance address of the application service can be reserved in the MEC Ctl. After obtaining the address of the target instance of the target application service, the MEC Ctl sends the address of the target instance to the CP together with the original instance address.
  • the MEC Ctl may also only send the target instance address of the target service, and does not need to send the original instance address.
  • the UE has already learned the original instance address of the target service when the UE accesses the original application instance of the target service. If the CP saves the original instance address, the MEC Ctl may not send the original instance address to the CP.
  • the CP may select at least one UP according to the UP corresponding to the target AN in the resource pool, and pass the selected information of the at least one UP through the foregoing coordinated request. Sended to the MEC Ctl, the MEC Ctl information of the target UP determined from the information of at least one UP.
  • a resource pool contains service mapping relationships for individual ANs and individual UPs. It should be noted that, since multiple ANs may serve one UP at the same time, if the original AN and the UP served by the target AN are the same UP, the CP does not need to reselect the new UP.
  • the first mode is: the MEC C11 determines the target MEC platform according to the location information of the UE, and then determines the UP corresponding to the target MEC platform. Since the UP and the MEC platform have a one-to-one correspondence, the UP corresponding to the target MEC platform can be determined as the target UP.
  • the second mode is: the MEC C1 determines the MEC platform corresponding to the multiple UPs according to the multiple UPs sent by the CP, and determines which MEC platform of the MEC platform deploys the application instance of the target application service according to the identifier of the target service. Therefore, the MEC platform in which the application instance of the target application service is deployed is determined as the target MEC platform, and then the UP corresponding to the target MEC platform is determined to be the target UP.
  • the information of the target UP is sent to the CP through a response message. That is, the response message sent by the MEC C11 to the CP may further include information of the target UP determined by the MEC Ctl.
  • the CP creates a user session with the target UP.
  • the UE Since the CP does not perform the packet forwarding work, and the UP is used to forward the packet, the UE needs to use the target UP to send the packet after the target is accessed after the mobile, so the CP needs to be determined with the target UP.
  • a user session is created to send information such as a packet forwarding policy and an address translation indication to the target UP.
  • the CP sends an address translation indication to the target UP.
  • the target UP receives an address translation indication sent by the CP, the address translation indication including the original instance address of the target application service and the address of the target instance.
  • the target UP sets the forwarding address of the target application service and the uplink packet of the UE to the address of the target instance according to the address translation indication, and the source of the downlink application of the target application service and the UE.
  • the address is set to the original instance address.
  • the CP formulates an address translation policy, which is: setting the forwarding address of the target application service and the uplink packet of the UE to the address of the target instance. And setting the source address of the target application service and the downlink message of the UE to the original instance address.
  • a network address translation (English name: Network abbreviation: NAT) function is set on the target UP. After receiving the address translation indication, the target UP performs address translation according to the address translation policy. In this way, the UE side does not know that the connected target application service has been replaced with the application instance, and the UE side only needs to send according to the original instance address when sending the uplink message.
  • the target UP forwards the uplink packet to the target instance of the target application service.
  • the target application instance of the target application service sends a downlink packet
  • the target UP translates the source address of the downlink packet to the original instance address. In this way, the UE side does not perceive that the message is sent by a new instance of the target application service, so that the downlink message can be identified.
  • the UE can directly perform packet interaction without re-establishing a service connection with a new instance of the target application service, thereby reducing network delay.
  • the UE has performed at least one regional mobility before moving to the target AN service range, and then may cause the UE to communicate the application before switching to the target instance of the target application service.
  • the instance is not an initial application instance. Therefore, the original instance address obtained by the CP from the MEC Ctl is not the address of the initial instance.
  • the UE starts to access a video service through the first AN, and the instance address of the service that is connected to the UE is the first instance address of the first MEC platform corresponding to the first AN. After the UE moves, the UE accesses the second AN.
  • the UE After the address translation, the UE actually communicates with the UE by using an application instance on the second MEC platform corresponding to the second AN, and the application instance corresponds to the second.
  • the acquired address is not the original first instance address, but the current second converted by the UE after one movement. Instance address.
  • the original instance address of the target application service acquired by the CP is the current instance address used by the target application service and the UE service access, and not the initial instance address used by the target application service to perform service access with the UE. That is, the UE initially accesses the instance address of the target application service. In order to enable the UE to perceive the application instance of the connected target application service to be changed, the network side needs to set the forwarding address of the downlink packet to be the UE accessing the target application service. The initial instance address. Therefore, after obtaining the original instance address, the CP can also query whether the original instance address is the same as the initial instance address when the target application service performs service access with the UE. Since the address translation indication after each transfer is made by the CP, the CP only needs to perform comparison and query according to the previously stored mapping conditions, and can determine the initial instance address of the target application service and the terminal to access the connection.
  • the embodiment of the present application may further include the following steps:
  • the CP obtains an initial instance address when the UE accesses the target application service according to the current instance address;
  • the CP formulates an address translation policy according to the initial instance address and the address of the target instance.
  • the policy may be used to indicate that the target UP sets the forwarding address of the target application service and the uplink message of the UE to the address of the target instance, and the target application service and the downlink message of the UE
  • the source address is set to the initial instance address.
  • the NAT function is set on the UP, the address translation policy of the application instance is formulated by the CP, and the address translation of the application instance is performed by the UP.
  • the NAT function may also be set on the MEC platform, and the MEC platform is used to formulate an address translation policy of the application instance, and the MEC platform performs address translation of the application instance.
  • the specific system framework is shown in Figure 4.
  • the MEC platform receives the registration application sent by the target application service, where the registration application includes a service address of the application service and a network address translation NAT service request identifier, where the NAT service request identifier is used to request the UE and the target application.
  • the service data stream of the service performs address translation on the MEC platform.
  • the service address of the application service is used to mark the application service in the form of an Internet Protocol (IP) address.
  • IP Internet Protocol
  • the service address used by the same application service on all MEC platforms is the same.
  • the UE obtains the service address of the application service corresponding to the application instance, not the instance address of the application instance.
  • the NAT function is set on the MEC platform.
  • the MEC platform may formulate an address translation policy for the target application service.
  • the policy may be: setting the forwarding address of the uplink packet of the UE and the target application service to the address of the local application instance, and setting the source address of the downlink packet sent by the local application instance to the UE as the service of the target application service. address.
  • FIG. 5 describes a process for implementing a new service establishment by the UE through the system architecture shown in FIG. 4.
  • Another embodiment of the method for converting an application instance address in the embodiment of the present application includes:
  • the CP sends a coordination request to the MEC C11.
  • the MEC C11 receives a collaborative request sent by the CP, where the collaborative request includes location information of the UE and an identifier of the target application service.
  • the service request is initiated.
  • the CP sends a cooperation request to the MEC C1, so that the UE can establish a session connection with the target application.
  • the UE sends a service flow message to the target application service through the UP, and the UP detects the message as a new service flow message, and reports the service request to the CP.
  • the CP initiates a cooperation request to the MEC C1, where the cooperation request carries the location information of the UE and the identifier of the target application service, so that the MEC C1 determines the application instance of the MEC platform that the UE needs to access according to the location information of the UE and the identifier of the target application service. .
  • the MEC C11 creates service flow feature information of the target application service according to the location information of the UE and the identifier of the target application service.
  • the MEC C1 needs to determine the connection between the UE and the application instance on the MEC platform. Therefore, the MEC C11 can determine the MEC platform according to the location information of the UE. For example, the location information of the UE is the information of the AN connected to the UE, and the service of the AN is determined. The MEC platform is the MEC platform that the UE needs to access. The MEC Ctl then finds the service address and the instance address of the target application service from the MEC platform according to the identifier of the target application service, and then creates the service flow characteristic information of the target application service.
  • the service flow characteristic information may be quintuple information, including the IP of the source end, the port number of the source end, and the network communication protocol used (Transmission Control Protocol/User Datagram Protocol, English: Transmission Control Protocol/User Datagram Protocol, abbreviated TCP /UDP protocol), destination IP, port number of the destination.
  • the service flow feature information includes uplink service flow feature information and downlink service flow feature information.
  • the IP address of the destination end of the uplink service flow feature information is a service address of the target application service
  • the IP address of the source end of the downlink service flow feature information is an instance address of the target application service.
  • the MEC Ctl sends a response message to the CP.
  • the CP receives the response message sent by the MEC C1, where the response message includes the service flow feature information of the target application service.
  • the formulation of the address translation policy of the application instance and the specific conversion operation are all performed on the MEC platform. Therefore, the MEC Ctl can also carry the indication information in the response message.
  • the indication information is used to instruct the CP to control the UP to forward the message that the UE interacts with the target application service to the MEC platform for address translation.
  • the traffic flow feature information can be created by the CP.
  • the MEC Ctl After the CP sends a coordination request to the MEC Ctl, the MEC Ctl only needs to return to the CP the necessary factors for creating the service flow feature information: the service address of the target application service and the determined instance address on the MEC platform. Therefore, the step 202 may be replaced by: the MEC C11 determines the service address of the target application service and the instance address on the corresponding MEC platform according to the location information of the UE and the identifier of the target application service.
  • Step 203 may be replaced by: MEC C11 sends a response message to the CP, where the response message includes the service address and an instance address. The CP creates service flow feature information according to the service address and the instance address.
  • the CP creates a user session with the UP.
  • the UP is the UP corresponding to the MEC platform determined by the MEC Ctl.
  • the CP sends a packet forwarding indication to the UP.
  • the packet exchanged by the UE with the target application service is sent to the MEC platform for address translation.
  • the CP does not perform an address translation policy.
  • the CP controls the UP to forward the message exchanged by the UE and the target application service to the MEC platform for address translation according to the indication in the response message. For example, the CP generates a corresponding packet forwarding indication and sends the packet forwarding indication to the UP.
  • the UP After receiving the uplink packet sent by the UE, the UP determines, by using the service flow feature information, that the uplink packet is an interaction packet between the UE and the target application service. The UP sends the uplink packet to the corresponding MEC platform for address translation. When receiving the downlink packet sent by the application instance, the UP also needs to send the downlink packet to the MEC platform for address translation.
  • the UP sends the target packet to the MEC platform.
  • the MEC platform receives the target message sent by the UP.
  • the target packet is an interaction packet between the UE and the target application service, including an uplink packet and a downlink packet.
  • the UP After receiving the uplink packet or the downlink packet, the UP first determines that the uplink packet or the downlink packet is the target packet according to the service flow characteristic information. The UP then sends the target message to the MEC platform according to the message forwarding indication.
  • the MEC platform performs address translation on the target packet according to an address translation policy.
  • the MEC platform modifies the forwarding address or source address of the target packet according to the pre-defined address translation policy. For example, if the target packet is an uplink packet, the MEC platform sets the forwarding address of the uplink packet to the address of the application instance deployed by the target application service on the MEC platform, that is, the local on the MEC platform. The instance address; if the target packet is a downlink packet, the MEC platform sets the source address of the downlink packet to the service address of the target application service.
  • the CP does not formulate an address translation policy, and the UP does not perform address translation.
  • the CP only needs to send a packet forwarding indication to the UP according to the packet forwarding requirement of the MEC platform.
  • the UP After receiving the uplink packet sent by the UE, the UP only needs to send the uplink data to the MEC platform for address translation, and the MEC platform will uplink.
  • the packet After the packet is translated, the packet is sent to UP, and the UP is forwarded to the target application instance.
  • the UP also needs to send the downlink packet to the MEC platform for address translation.
  • the MEC platform sends the downlink packet after the address translation to the UP, and the UP forwards the downlink data to the UE.
  • the target application service is deployed on each MEC platform to use the same service address.
  • the UE side only needs to use the service address.
  • Each MEC platform has an address translation policy, that is, the forwarding address of the uplink packet of the UE is set to the address of the local application instance, and the source address of the downlink packet of the application instance is set as the service address.
  • the MEC platform that needs to perform address translation does not need to dynamically obtain the address of the application instance on other MEC platforms (for example, the UE accesses the initial instance address of the target application service), which reduces signaling interaction and reduces network delay.
  • the embodiment of FIG. 5 describes a process for a UE to perform a new service setup.
  • the solution described in the embodiment of FIG. 5 is also applicable to a packet that is accessed by a terminal to a target application service after the UE moves to a service area of another AN.
  • the scene of address translation When the solution is applicable to the scenario in which the network side performs geological transformation on the network after the UE moves, the MEC platform is the new MEC platform corresponding to the UE access target AN determined by the MEC Ctl, and the new MEC platform is also the same. With address translation.
  • the UP is the target UP of the new MEC platform that is determined by the CP and the MEC Ctl.
  • the target UP forwards the target packet to the new MEC platform according to the packet forwarding indication sent by the CP.
  • the description of the embodiment of FIG. 5 can be referred to, and details are not described herein.
  • the above embodiment describes the address translation policy and the address translation operation performed by the MEC platform.
  • the address translation policy of the application instance is still determined by the MEC platform, but the operation of forwarding the packet to the MEC platform for address translation according to the indication may be performed by
  • the data plane (English full name: Data Plane, English abbreviation: DP) device is executed without being executed by UP.
  • the DP is also set in the MEC host.
  • the DP is connected to the UP and MEC platforms respectively.
  • the DP is also connected to the application instance on the MEC platform.
  • the DP is used to forward and control packets.
  • the MEC platform can send a corresponding routing rule to the DP, and the DP sends the target packet to the MEC platform for address translation according to the routing rule.
  • the specific implementation is similar to the method described in the embodiment of FIG. 5, and the difference steps are as follows:
  • the conversion method further includes:
  • the MEC platform sends the routing rule to the DP according to the configured routing rule generated by the configured UE address network segment, the service address of the target application, and the local instance address. After receiving the target packet sent by the UP, the DP sends the target packet to the MEC platform for address translation processing according to the routing rule.
  • the UP sends packets to and from the MEC platform, and needs to be forwarded through the DP.
  • the MEC platform does not need to perform address translation for the interaction between the application instance and the application instance.
  • the packet data between the UE and the application service after the service migration needs to be translated.
  • the network segment of the UE can be distinguished.
  • the address pool (network segment) of the network planning UE is 10.141.0.0/16.
  • the DP resolves the source address of the packet. If the source address belongs to the network segment of the UE, Then, it is determined that the packet belongs to the packet sent by the UE, and therefore needs to be sent to the MEC platform for address translation processing.
  • the routing rules defined by the MEC platform are used not only to determine whether the target packet is a packet sent by the UE or a packet sent to the UE, but also whether the target packet needs to be sent to the MEC platform for address translation.
  • the routing rule includes an uplink routing rule and a downlink routing rule, where the uplink routing rule includes a mapping between the network segment address of the UE and the service address of the target application service, and the downlink routing rule includes the network segment address of the UE and the local instance address of the target application service. The mapping between the two.
  • the DP determines whether the source address of the uplink packet is an address in the network segment of the UE according to the uplink routing rule, and determines whether the destination forwarding address of the uplink packet is the same as the service address of the target application service. When both of the judgments are yes, the DP sends the uplink packet to the MEC platform for address translation. For the downlink packet, the DP determines whether the source address of the downlink packet is the same as the local instance address of the target application service, and determines whether the destination forwarding address of the downlink packet is an address in the UE network segment. When the judgment result of both is yes, the DP sends the downlink packet to the target UP to forward the packet.
  • the MEC platform performs the address translation strategy.
  • the address conversion policy can be formulated by the path rule control unit (English name: Traffic Rule Control, English abbreviation: TRC) on the MEC platform.
  • the MEC platform also configures routing rules and sends the routing rules to the DP.
  • the DP performs specific packet forwarding operations.
  • an embodiment of a device for converting an application instance address in the embodiment of the present application includes:
  • the sending unit 301 is configured to send a collaboration request to the mobile edge cloud MEC control device, where the cooperation request includes location information of the terminal and information of an application service, where the application service is an application service accessed by the terminal;
  • the receiving unit 302 is configured to receive response information from the MEC control device, where the response information includes an address of the target instance, where an address of the target instance is associated with location information of the terminal and information of the application service;
  • the sending unit 301 is further configured to: send, according to an address of the target instance, an address of the target instance to a first user plane device corresponding to the target instance;
  • the processing unit 303 is configured to instruct the first user plane device to set a forwarding address of the uplink packet sent by the terminal to obtain the application service as an address of the target instance.
  • the device further includes:
  • the obtaining unit 304 is configured to obtain an initial instance address when the terminal accesses the application service according to an address of an application instance that the terminal currently communicates with;
  • the processing unit 303 is further configured to: instruct the first user plane device to: set a source address of a downlink packet sent by the target instance to the terminal as the initial instance address.
  • the receiving unit 302 is further configured to:
  • the handover request is used to request to switch the terminal from the original access network AN to the target AN;
  • the device also includes:
  • the selecting unit 305 is configured to select, according to the target AN, at least one user plane device corresponding to the target AN, where the cooperation request includes information of the at least one user plane device, and the response message includes the first User face device information;
  • the creating unit 306 is configured to create a session between the terminal and the first user plane device.
  • the various units described in the embodiment of FIG. 7 can also perform the steps performed by the CP in the embodiment of FIG. 3 during the operation. For details, refer to the embodiment of FIG. 3, and details are not described herein.
  • another embodiment of the apparatus for converting an application instance address in the embodiment of the present application includes:
  • the receiving unit 401 is configured to receive a collaboration request from the control plane device, where the collaboration request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • a determining unit 402 configured to determine, according to the collaborative request, a target instance of the application service
  • An obtaining unit 403, configured to acquire an address of the target instance, where the target instance is an application instance that provides the application service and the service location range includes a location of the terminal;
  • the sending unit 404 is configured to send, to the control plane device, response information, where the response information includes an address of the target instance, and an address of the target instance is used for address translation of a packet.
  • the location information of the terminal includes information about the target access network AN accessed by the terminal;
  • the determining unit 403 is specifically configured to:
  • the first MEC platform Determining, according to the information of the application service, the first MEC platform from the at least one MEC platform, and determining an application instance of the application service deployed in the first MEC platform, where the first MEC platform is a provider The MEC platform for application services.
  • the various units described in the embodiment of FIG. 8 can also perform the steps performed by the MEC C1 in the embodiment of FIG. 3 during the operation. For details, refer to the embodiment of FIG. 3, and details are not described herein.
  • another embodiment of the apparatus for converting an application instance address in the embodiment of the present application includes:
  • the sending unit 501 is configured to send a collaboration request to the mobile edge cloud MEC control device, where the cooperation request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • the receiving unit 502 is configured to receive response information from the MEC control device, where the response information includes an identifier of a first mobile edge cloud MEC platform, where the first MEC platform is an MEC platform that provides the application service, where An identifier of an MEC platform is associated with location information of the terminal and information of the application service;
  • the sending unit 501 is further configured to: send the identifier of the first MEC platform to the first user plane device, and instruct the first user plane device to: send the target packet to the first MEC platform,
  • the target packet is a packet that the terminal accesses the application service;
  • the processing unit 503 is configured to control the step of the sending unit 501 to perform transmission, and the step of controlling the receiving unit 502 to perform receiving.
  • the response message further includes service flow feature information, where the service flow feature information is associated with the terminal and the information of the application service;
  • the processing unit 503 is further configured to:
  • the various units described in the embodiment of FIG. 9 can also perform the steps performed by the CP in the embodiment of FIG. 5 during the operation. For details, refer to the embodiment of FIG. 5, and details are not described herein.
  • another embodiment of the apparatus for converting an application instance address in the embodiment of the present application includes:
  • the receiving unit 601 is configured to receive a collaboration request from the control plane device, where the collaboration request includes location information of the terminal and information of the application service, where the application service is an application service accessed by the terminal;
  • a determining unit 602 configured to determine, according to the collaborative request, an identifier of a first mobile edge cloud MEC platform, where the first MEC platform is an MEC platform that provides the application service;
  • a sending unit 603, configured to send, to the control plane device, an identifier of the first MEC platform
  • the processing unit 604 is configured to instruct the control plane unit to: control the first user plane device to send the target message to the first MEC platform, where the target message is the message that the terminal accesses the application service.
  • the device further includes:
  • the obtaining unit 605 is configured to obtain a service address of the application service and a target instance address, where the target instance is an application instance that is deployed by the application service in the first MEC platform;
  • a creating unit 606 configured to create service flow feature information according to the service address and the target instance address;
  • the sending unit 603 is further configured to send the service flow feature information to the control plane device;
  • the processing unit 604 is further configured to: instruct the control plane device to: control the first user plane device to determine a target packet according to the service flow feature information.
  • the various units described in the embodiment of FIG. 10 can also perform the steps performed by the MEC C1 in the embodiment of FIG. 5 during the operation. For details, refer to the embodiment of FIG. 5, and details are not described herein.
  • another embodiment of the apparatus for converting an application instance address in the embodiment of the present application includes:
  • the receiving unit 701 is configured to receive, by the first user plane device, a target packet, where the target packet is a packet that the terminal accesses the application service, where the application service is an application service accessed by the terminal;
  • the setting unit 702 is configured to: if the target packet is an uplink packet, set a forwarding address of the target packet to an address of a target instance, where an address of the target instance is the application service in the MEC platform The address of the deployed application instance;
  • the setting unit 702 is further configured to: if the target packet is a downlink packet, set a source address of the target packet to a service address of the target application service.
  • the receiving unit 701 is specifically configured to:
  • the device also includes:
  • the generating unit 703 is configured to generate, according to the configured terminal address network segment, the service address of the service of the application, and the address of the target instance, before the receiving unit 701 receives the target packet from the first user plane device by using the data plane device. Routing rules;
  • the sending unit 704 is configured to send the routing rule to the data plane device, and instruct the data plane device to: send the target packet to the MEC platform according to the routing rule.
  • the various units described in the embodiment of FIG. 11 can also perform the steps performed by the MEC platform in the embodiment of FIG. 5 during the operation. For details, refer to the embodiment of FIG. 5, and details are not described herein.
  • the apparatus of the embodiment of the present invention has another form of embodiment.
  • the apparatus includes: a processor 801, a memory 802, a transceiver 803, the processor 801, the memory 802, and
  • the transceiver 803 is connected by a bus 804, which may include a transmitter and a receiver, the memory 802 storing computer instructions, and the processor 801 is implemented by implementing the computer instructions for implementing FIG. 3 or FIG.
  • the specific implementation may adopt various flexible design manners, and the corresponding functions of the respective devices may be further referred to the foregoing method embodiments, and the application is not limited.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • wire eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了一种应用实例地址的转换方法,包括:控制面设备向移动边缘云MEC控制设备发送协同请求,所述协同请求包含所述终端的位置信息以及应用服务的信息,控制面设备从所述MEC控制设备接收响应信息,应信息包含目标实例的地址,控制面设备根据目标实例的地址,向目标实例对应的第一用户面设备发送目标实例的地址,并指示第一用户面设备:将终端为获取应用服务发送的上行报文的转发地址设置为目标实例的地址。这样,终端在进行跨接入点服务区域的移动后,无需与新的应用实例重新创建业务连接就能够直接进行报文交互,减少了网络时延。

Description

一种应用实例地址的转换方法和装置
本申请要求于2017年6月30日提交中国专利局、申请号为201710530099.X、发明名称为“一种应用实例地址的转换方法和装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域,尤其涉及一种应用实例地址的转换方法和装置。
背景技术
当前网络(商用无线网络2G/3G/长期演进(英文全称:Long Term Evolution,英文缩写:LTE))是一种聚合型的网络。在当前网络下,业务对时延的要求并不高,终端访问业务时都经过集中部署的网关。例如,终端对业务的访问时延大概为100ms左右。随着虚拟化技术和分布式云技术的发展,未来移动网络会在网络边缘(比如,靠近基站的位置)部署微云平台,即移动边缘计算/移动边缘云(英文全称:Mobile Edge Computing/Cloud,英文缩写:MEC)平台。为了满足未来业务低时延的需求,降低网络带宽资源消耗,业务的多个应用实例会分别分布式部署在多个MEC平台上,业务的每个应用实例为一定范围内的终端提供服务。当终端从该业务的应用实例的一个服务区域移动到另一个服务区域,终端需要接入另一个服务区域所对应的应用实例。
终端移动后,接入另一个服务区域的应用实例时需要进行的该应用实例的应用状态迁移(Application state relocation),该应用状态迁移包括:应用层用户状态迁移、网络连接(socket)迁移、以及IP(英文全称Internet Protocol)地址和传输路径的移动性(英文缩写:IP Mobility)处理。关于IP Mobility的处理,现有的迁移技术是:用户上行报文在应用实例变换后需要经过目的应用实例所对应的服务设备发送到源应用实例对应的服务设备,由源应用实例所对应的服务设备做目的地址转换(英文全称:Destination Network Address Translation,英文缩写:DNAT),再由该源应用实例所对应的服务设备将报文转发给目的应用实例所对应的服务设备,最后转发给目的应用实例。
这种技术的问题是上行路径迂回,尤其是当应用实例发生连续切换后,上行报文需先发送到最开始的服务设备,再转发至目的服务设备,从而造成了终端迁移过程中网络时延比较高,影响用户的使用体验。
发明内容
本申请提供了一种应用实例地址的转换方法和装置,用于减少终端在移动过程中的网络时延。
第一方面,本申请提供了一种应用实例地址的转换方法,包括:
控制面设备将终端所接入的应用服务的信息以及终端的位置通过协同请求发送给移动边缘云MEC控制设备。MEC控制设备在根据应用服务的信息以及终端的位置信息获取到目标实例的地址后,通过响应消息将该目标实例的地址发送给控制面设备。
控制面设备根据该目标实例的地址制定地址转换策略,并将该策略发送给第一用户设备,该策略用于指示第一用户面设备:将终端为获取该应用服务而发送的上行报文的目的转发地址设置为该目标实例的地址。
终端在从一个服务区移动到另一个服务区后,虽然所接入的应用服务的应用实例发生改变,但是终端并未感知。终端仍可通过初始接入该应用服务时所连接的应用实例的地址发送上行报文,网络侧可通过上述的地址转换方法将终端发送的上行报文转发至新的应用实例。这样,终端无需与新的应用实例建立连接则可进行报文发送,减少了网络时延。
一种可能的实现方式中,上述方法还可以包括:
控制面设备根据终端当前通信的应用实例的地址,获取终端接入应用服务时的初始实例地址。控制面设备根据所获取到的初始实例地址制定针对下行报文的地址转换策略,并将该策略发送给第一用户设备,该策略为指示第一用户设备将目标实例发送至终端的下行报文的来源地址设置为该初始实例地址。
由于网络侧已经更换了新的应用实例,对于新的应用实例发送的下行报文,终端可能无法识别该下行报文的来源地址。网络侧需将该下行报文的来源地址设置为终端接入该应用服务时的初始实例地址。这样,在终端访问该应用服务的过程中,终端不仅能够识别新的应用实例发送的下行报文,且始终不会感知网络侧已经更换了新的应用实例,从而无需与新的应用实例建立连接,减少了网络时延。
另一种可能的实现方式中,上述方法还可以包括:
控制面设备接收原接入网AN或目标AN发送的切换请求,该切换请求用于请求将终端从原AN切换至目标AN;
控制面设备查询与该目标AN对应的用户面设备,若该目标AN对应的用户面设备有多个,控制面设备则选择其中至少一个用户面设备,并将所选择的至少一个用户面设备的信息通过协同请求发送给MEC控制设备。MEC控制设备则判断这至少一个用户面中哪个能使用,以及判断哪个与目标AN所服务的MEC平台对应,进而确定出第一用户面设备。
MEC Ctl再将所确定的第一用户面设备的信息通过响应消息发送给控制面设备。控制面设备则创建终端与第一用户面设备之间的会话。
这样,经过控制面设备与MEC控制设备来协同确定第一用户面设备,减少了由单独某个网元确定用户面设备而造成所确定的用户面设备无法使用的情况。
第二方面,本申请提供了一种应用实例地址的转换方法,包括:
移动边缘云MEC控制设备接收控制面设备发送的协同请求,该协同请求包含终端的位置信息以及终端所接入的应用服务的信息。
MEC控制设备根据终端的位置信息确定MEC平台,再根据应用服务的信息确定目标实例,并获取该目标实例的地址。
MEC控制设备将获取到的目标实例的地址通过响应消息发送给控制面设备,以使得控制面设备根据该目标实例制定地址转换策略,指示第一用户面设备将目标实例发送至终端的下行报文的来源地址设置为该初始实例地址。
一种可能的实现方式中,终端的位置信息包括终端接入的目标AN的信息;
MEC控制设备根据终端的位置信息以及应用服务的信息确定目标实例可以为:
MEC控制设备判断该目标AN服务哪几个MEC平台,再判断这些MEC平台中哪个MEC平台部署有该应用服务的应用实例,从而确定出第一MEC平台以及该第一MEC平台上所部署的目标实例。
第三方面,本申请提供了应用实例地址的转换方法,包括:
控制面设备将终端所接入的应用服务的信息以及终端的位置通过协同请求发送给移动边缘云MEC控制设备。MEC控制设备再根据应用服务的信息以及终端的位置信息确定第一MEC平台后,通过响应消息将该第一MEC平台的标识发送给控制面设备。
控制面设备接收到第一MEC平台的标识后,向第一用户面设备发送报文转发指示,指示第一用户面设备将终端访问该应用服务的报文均发送至该第一MEC平台,以使得第一MEC平台对该报文进行地址转换。
在上述方法中,MEC平台具备了地址转换的功能,MEC平台可以制定相应的地址转换策略,以及执行相应的地址转换操作,减轻了控制面设备以及用户面设备的负荷。
一种可能的实现方式中,响应消息还包括业务流特征信息,业务流特征信息为MEC控制设备根据终端的地址以及应用服务的服务地址和实例地址所创建的。
控制面设备还指示第一用户面设备:根据该业务流特征信息确定目标报文。
第四方面,本申请提供了一种应用实例地址的转换方法,包括:
移动边缘云MEC控制设备接收控制面设备发送的协同请求,该协同请求包含终端的位置信息以及终端所接入的应用服务的信息。
MEC控制设备根据终端的位置信息确定提供该应用服务的第一移动边缘云MEC平台。
MEC控制设备将所确定的第一MEC平台的标识通过响应消息发送给控制面设备,并指示控制面单元:控制第一用户面设备将终端访问应用服务的报文发送至第一MEC平台,以使得第一MEC平台对该报文进行地址转换。
一种可能的实现方式中,上述方法还可以包括:
MEC控制设备获取应用服务的服务地址以及目标实例地址,并创建业务流特征信息。
MEC控制设备将所创建的业务流特征信息发送通过响应消息发送给控制面设备,并指示控制面设备:控制第一用户面设备根据业务流特征信息确定目标报文。
第五方面,本申请提供了一种应用实例地址的转换方法,包括:
移动边缘云MEC平台接收第一用户面设备发送的终端访问所接入的应用服务的报文。
MEC平台判断该报文为上行报文或者为下行报文,若为上行报文,MEC平台则将该报文的目的转发地址设置为该应用服务在该MEC平台中部署的应用实例的地址;若该报文为下行报文,MEC平台则将该报文的来源地址设置为目标应用服务的服务地址。
终端在接入应用服务时,所获取到的访问地址为该应用服务的服务地址。因此,终端无论在哪个服务小区内,访问该应用服务的上行报文都需经地址转换才能发送到相应的应用实例上,以及所有下行报文都需经过地址转换才能发送给终端,让终端能够识别出来。在上述方法中,由MEC平台执行地址转换的操作。若MEC平台部署有该应用服务的应用实例,则该MEC平台必然能够知道该应用服务的服务地址以及应用实例的地址。这样,MEC 平台则无需从其它获取到需要转换的地址,直接可通过本地的地址进行地址转换,减少了信令交互的过程,提高了终端访问的速度。
一种可能的实现方式中,MEC平台接收第一用户面设备发送的终端访问所接入的应用服务的报文可以为:
MEC平台通过数据面设备接收第一用户面设备发送的终端访问所接入的应用服务的报文,即第一用户面设备发送给MEC平台的报文可以经过数据面设备进行转发。相应的,MEC平台发送给第一用户面设备的报文,也可以经过数据面设备进行转发。
在MEC平台通过数据面设备接收第一用户面设备发送的终端访问所接入的应用服务的报文之前,该方法还可以包括:
MEC平台根据配置的终端地址网段、应用的服务的服务地址以及目标实例的地址生成路由规则,并将该路由规则发送给数据面设备,指示数据面设备:根据路由规则将终端访问所接入的应用服务的报文发送至MEC平台进行地址转换。
终端地址网段用于数据面设备识别所接收到的报文是否是终端发送的,或者是需发送给终端的。由于其它设备发送给MEC平台的报文一般不需进行地址转换,因此,通过这种方式,减少了前述情况的发生。
第六方面,本申请提供了一种应用实例地址的转换装置,包括:
发送单元,用于向移动边缘云MEC控制设备发送协同请求,协同请求包含终端的位置信息以及应用服务的信息,其中,应用服务为终端接入的应用服务;
接收单元,用于从MEC控制设备接收响应信息,响应信息包含目标实例的地址,目标实例的地址与终端的位置信息和应用服务的信息关联;
发送单元还用于,根据目标实例的地址,向目标实例对应的第一用户面设备发送目标实例的地址;
处理单元,用于指示第一用户面设备:将终端为获取应用服务发送的上行报文的转发地址设置为目标实例的地址。
第七方面,本申请提供了一种应用实例地址的转换装置,包括:
接收单元,用于从控制面设备接收协同请求,协同请求包含终端的位置信息以及应用服务的信息,其中,应用服务为终端接入的应用服务;
确定单元,用于根据协同请求,确定应用服务的目标实例;
获取单元,用于获取目标实例的地址;其中,目标实例为提供应用服务的且服务位置范围包含终端的位置的应用实例;
发送单元,用于向控制面设备发送响应信息,响应信息包含目标实例的地址,目标实例的地址用于报文的地址转换。
第八方面,本申请提供了一种应用实例地址的转换装置,包括:
发送单元,用于向移动边缘云MEC控制设备发送协同请求,协同请求包含终端的位置信息以及应用服务的信息,其中,应用服务为终端接入的应用服务;
接收单元,用于从MEC控制设备接收响应信息,响应信息包含第一移动边缘云MEC平台的标识,第一MEC平台为提供应用服务的MEC平台,第一MEC平台的标识与终端的位置 信息和应用服务的信息关联;
发送单元还用于,向第一用户面设备发送第一MEC平台的标识,并指示第一用户面设备:将目标报文发送至第一MEC平台,目标报文为终端访问应用服务的报文;
处理单元,用于控制发送单元执行发送的步骤,以及控制接收单元执行接收的步骤。
第九方面,本申请提供了一种应用实例地址的转换装置,包括:
接收单元,用于从控制面设备接收协同请求,协同请求包含终端的位置信息以及应用服务的信息,其中,应用服务为终端接入的应用服务;
确定单元,用于根据协同请求,确定第一移动边缘云MEC平台的标识;其中,第一MEC平台为提供应用服务的MEC平台;
发送单元,用于向控制面设备发送第一MEC平台的标识;
处理单元,用于指示控制面单元:控制第一用户面设备将目标报文发送至第一MEC平台,目标报文为终端访问应用服务的报文。
第十方面,本申请提供了一种应用实例地址的转换装置,包括:
接收单元,用于从第一用户面设备接收目标报文,目标报文为终端访问应用服务的报文,应用服务为终端接入的应用服务;
设置单元,用于若目标报文为上行报文,将目标报文的转发地址设置为目标实例的地址,目标实例的地址为应用服务在MEC平台中部署的应用实例的地址;
设置单元还用于,若目标报文为下行报文,将目标报文的来源地址设置为目标应用服务的服务地址。
第十一方面,本申请提供了一种应用实例地址的转换装置,包括:处理器、存储器、收发器,处理器、存储器以及收发器通过总线连接,存储器存储有计算机指令,处理器通过执行计算机指令用于实现如第一方面或第二方面或第三方面或第四方面或第方面任意一种所描述的方法。
第十二方面,本申请提供了一种存储介质,该存储介质存储有用于实现如第一方面或第二方面或第三方面或第四方面或第方面任意一种所描述的方法的计算机指令。
第十三方面,本申请提供了一种计算机程序产品,该计算机程序产品包括计算机软件指令,该计算机软件指令可通过处理器进行加载来实现如第一方面或第二方面或第三方面或第四方面或第方面任意一种所描述的方法中的流程。
第十四方面,本申请提供了一种芯片系统,该芯片系统包括处理器,用于支持应用实例地址的转换装置实现上述方面中所涉及的功能,例如,生成或处理上述方法中所涉及的信息。在一种可能的设计中,芯片系统还包括存储器,该存储器,用于保存支持应用实例地址的转换装置必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件。
从以上技术方案可以看出,本申请具有以下优点:
终端侧在发送上行报文时,只需按照原实例地址进行发送,该上行报文到达用户面设备时,用户面设备则会将该上行报文转发至应用服务的目标实例上。这样,终端在进行跨接入点服务区域的移动后,无需与新的应用实例重新创建业务连接就能够直接进行报文交 互,减少了网络时延。
附图说明
图1为本申请实施例中应用实例地址的转换方法所应用的一个系统架构示意图;
图2为本申请实施例中应用实例地址的转换方法所应用的另一系统架构示意图;
图3为本申请实施例中应用实例地址的转换方法的一个实施例示意图;
图4为本申请实施例中应用实例地址的转换方法所应用的另一系统架构示意图;
图5为本申请实施例中应用实例地址的转换方法的另一实施例示意图;
图6为本申请实施例中应用实例地址的转换方法所应用的另一系统架构示意图;
图7为本申请实施例中应用实例地址的转换装置的一个实施例示意图;
图8为本申请实施例中应用实例地址的转换装置的另一实施例示意图;
图9为本申请实施例中应用实例地址的转换装置的另一实施例示意图;
图10为本申请实施例中应用实例地址的转换装置的另一实施例示意图;
图11为本申请实施例中应用实例地址的转换装置的另一实施例示意图;
图12为本申请实施例中应用实例地址的转换装置的另一实施例示意图。
具体实施方式
本申请实施例提供了一种应用实例地址的转换方法和装置,用于减少终端在移动过程中的网络时延。
参照图1所示,图1为本申请实施例中应用实例地址的转换方法所应用的系统架构示意图。该系统架构中,包括终端(英文全称:User Equipment,英文缩写:UE),至少两个接入点(英文全称:Access Node,英文缩写:AN),控制面(英文全称:Control Plane,英文缩写:CP)设备,MEC集中控制管理(英文全称:Mobile Edge Computing/Cloud Control,英文缩写:MEC Ctl)设备。该系统架构中还包括至少两个移动边缘主机(英文:Mobile Edge host),移动边缘主机又称MEC主机。MEC主机是一种移动边缘的基础设施,例如,可以由一个或多个服务器与其它网络设备组成,所组成的网络架构形成的网络资源用于给应用实例提供服务平台。每个MEC主机都对应有用户面(英文全称:User Plane,英文缩写:UP)设备。背景技术中所描述的服务设备可以为该用户面设备。每个MEC主机中还设置有单独的移动边缘平台(英文:Mobile Edge platform),移动边缘平台又称MEC平台。MEC平台中部署有至少一个应用实例,图1中以APP(Application)实例表示一个应用实例。该应用实例用于为UE提供应用服务。在本申请实施例中,应用服务指:通过各个类型的应用为终端提供的服务,比如某个开发商所运营的视频应用服务。而应用实例指的是同一个应用服务部署在不同的MEC平台上的具体的应用。因此,一个应用服务可以对应多个应用实例。
AN用于UE进行网络业务访问时接入网络,并且实时接收UE发送的测量报告,用于检测UE与其它AN点之间的信号强度。当与UE连接的AN检测到UE与其它AN之间的信号强度和该AN与UE之间的信号强度达到移动阈值时,该AN决策将UE切换到目标AN。在图1中,原AN表示UE最开始接入网络时所使用的AN,目标AN表示UE移动后新接入的AN。在 本申请中,一个AN可以连接一台MEC主机,也可能是多个AN连接一台MEC主机。在图1示例中,原AN和目标AN各自连接有一台MEC主机。本申请所涉及的AN可以为基站,如长期演进(英文:long term evolution,缩写:LTE)演进型基站(英文:evolved Node B,缩写:eNB)、企业LTE(英文:enterprise LTE,缩写:eLTE)eNB、新无线接入基站(英文:new radio gNB,缩写:NR gNB)等,本申请中不做限定。
CP为核心网网元,用于进行报文转发策略的制定,以及控制UP按照报文转发策略进行报文转发。CP与MEC Ctl、多个AN以及多个MEC主机上的UP分别连接。CP分别从AN和MEC Ctl从获取请求信息和业务信息,从而制定转发策略,并将转发策略发送至UP,指示UP按照该转发策略进行报文转发。比如,CP接收到原AN发送的将UE的网络连接切换至目标AN的切换请求,CP则从MEC Ctl中获取到UE所使用的应用服务的原实例地址和目的实例地址,CP根据该原实例地址和目的实例地址制定报文转发策略。CP与MEC Ctl协同确定目标UP,CP再将所制定的转发策略发送至目标UP,从而使得目标UP根据该转发策略进行报文的转发。
UP用于接收UE发送的上行报文,根据转发策略将该报文转发至相应的MEC平台中的应用实例上,并在接收到下行报文时,根据转发策略将下行报文转发给UE。
MEC Ctl与多个MEC主机中的MEC平台连接,MEC Ctl用于对多个MEC平台进行管理和控制。在一种可能的实现方式中,MEC Ctl中可以设置有业务移动性控制(英文:Service Mobility Control,简写:SM Ctl)设备。MEC Ctl通过SM Ctl与多个MEC平台中所部署的应用实例连接,SM Ctl用于对多个MEC平台上的应用实例进行管理和控制。SM Ctl保存有应用实例部署信息,该信息中包括SM Ctl所连接的MEC平台中部署的应用实例的信息,以及有不同的MEC平台与不同的AN的映射服务关系信息。即,MEC Ctl可以通过SM Ctl根据AN的信息查询出该确定的AN所服务的至少一个MEC平台的信息。在另一种可能的实现方式中,SM Ctl也可以独立于MEC Ctl,SM Ctl与MEC Ctl可以通过空口或者有线连接,SM Ctl从MEC Ctl中获取多个MEC平台上所部署的应用实例的信息。
本申请的一个实施例是根据上述系统架构,将地址转换功能设置在UP上,具体系统架构参照图2所示,UP根据CP所制定的地址转换指示转换上行报文的目的地址,以及转换下行报文的原地址。使得UE在移动后,在UE侧无需感知已切换至新的MEC平台上的应用实例,则能够与新的应用实例进行业务访问,减少了网络时延。下面进行具体描述:
参照图3所示,本申请实施例中应用实例地址的转换方法的一个实施例包括:
101、原AN或目标AN向CP发送切换请求。CP接收到切换请求,所述切换请求用于请求将UE的网络连接从所述原AN切换至目标AN。
UE与原AN进行网络连接,并通过该原AN所服务的MEC平台访问该MEC平台中的目标应用实例,比如访问一个视频业务。当UE移动时,UE从原AN切换到目标AN,原AN/或者目标AN则向CP发送切换请求,该切换请求中携带有UE的位置信息。
例如,在空口切换准备阶段,可以由原AN向目标AN发送切换要求(handover required),目标AN反馈切换要求的确认信息之后,目标AN向CP发送路径切换请求准备(path switch request preparation)消息。即,上述切换请求可以是目标AN发送的路 径切换请求准备消息。另一种实现方式中,对于S1切换(AN之间没有直接接口),原AN在切换准备阶段向CP发送切换要求(handover required),由CP向目标AN发送切换请求(handover request)消息,目标AN对CP的切换请求消息回复确认消息,CP这时候可以确认向目标AN进行切换。即,上述切换请求可以是原AN发送的切换要求。
102、CP根据UE的位置信息和/或业务相关属性信息重选UP。
例如,UE的位置信息为UE的网络位置信息,比如:目标AN的信息,跟踪区信息;或者,UE的位置信息为UE的地理位置信息。跟踪区信息为UE在发生位置变换后所上报的此时UE所在区域信息。
业务相关属性信息可以为CP本地配置的,也可以由CP从MEC Ctl中获取的。业务相关属性信息可以是指业务和会话连续性(session and service continuity,简写:SSC)的属性。CP通过SSC判断是否可以重选UP。
CP在确定UE需要进行切换到目标AN时,CP不仅需要协同MEC Ctl进行该应用服务的应用层用户状态迁移,还需要进行网络连接(Socket)迁移。比如,该应用服务为一个视频服务,那么用户状态迁移包括:在UE上所播放的一个视频已播放的时长以及UE的鉴权信息等信息的迁移。网络连接的迁移包括:将Socket相应的会话上下文内容从源侧设备(源侧设备包括原AN和MEC平台)提取出来,传输到目的服务层,并安装。此外,因为不同的AN所服务的MEC平台可能不同,从而导致UE接入到目标AN后,当前为UE提供应用服务的应用实例已切换为目标AN所服务的MEC平台中的应用实例。因此,CP还需要协同MEC Ctl对应用服务的实例地址进行迁移。这将结合步骤103做进一步描述。
103、CP向MEC Ctl发送协同请求。相应的,MEC Ctl接收CP发送的协同请求。
由于MEC Ctl中保存有各个MEC平台与网络服务范围(比如:各MEC平台服务的AN列表,或者各MEC平台对应的UP,等)的映射服务关系,因此CP向MEC Ctl所发送的协同请求中需携带UE的位置信息,以便MEC Ctl根据UE的位置信息决策是否需要进行业务迁移,如果需要迁移的话,进一步确定所对应的MEC平台,从而确定该MEC平台中的该目标应用实例的地址。
例如,所述协同请求中包含的UE的位置信息可以包括上述位置信息,或者,UE的位置信息还可以是目标UP信息或目标MEC主机信息/目标MEC平台信息。目标UP信息为CP所重选的UP的信息,比如目标UP的ID。CP根据该目标UP查找所对应的MEC主机或MEC平台,并确定该MEC主机或MEC平台为目标MEC主机或目标MEC平台。
在一种可能的实现方式中,CP可以直接选择并确定目标UP。比如,为一个AN服务一个UP的情况。
在另一种可能的实现方式中,一个AN可能服务多个UP,那么CP在决定重选UP时,若目标AN所服务的UP包含多个时,CP此时所选择的UP为多个。在这种情况下,CP可以请求MEC Ctl协同确定出唯一一个目标UP。可选的,CP在向MEC Ctl所发送的协同请求中,还可以包含CP所选择的多个UP的信息。
104、MEC Ctl根据UE的位置信息确定目标应用服务的目标实例的信息,并获取所述目标实例的地址。
在图1实例中描述了MEC Ctl可以通过SM Ctl连接各个MEC平台中所部署的应用实例,且SM Ctl中保存有所连接的MEC平台中部署的应用实例的信息(应用实例部署信息),SM Ctl还保存有不同的MEC平台与不同的AN的映射服务关系信息。因此,MEC Ctl则可以根据UE的位置信息(UE的位置信息可以为步骤102所述的UE的网络位置信息的任意一种或多种)从应用实例部署信息中查询出目标AN所服务的MEC平台。
比如,若UE的位置信息包含目标AN的信息,MEC Ctl则直接根据该目标AN的信息确定目标MEC平台;若UE的位置信息包含跟踪区信息,则MEC Ctl则可以先确定是哪个AN的服务区域包含该跟踪区,从而确定目标AN,进而确定目标MEC平台。MEC Ctl在确定目标MEC平台后,则可以根据目标应用服务的信息(比如,该目标应用服务的标识)确定部署在该目标MEC平台上的目标应用实例,进而获取目标应用实例的地址。
105、MEC Ctl向CP发送的响应信息。CP接收MEC Ctl发送的响应信息。所述响应信息包含所述目标应用服务的原实例地址和目标实例的地址,以使得CP根据所述响应消息向目标UP发送进行地址转换的请求/指示。
MEC Ctl需要将原实例地址和目标实例的地址发送至CP,以便CP根据原实例地址和目标实例的地址制定地址转换策略,从而指示目标UP进行地址转换。由于UE在接入原AN所对应的MEC平台上该目标应用服务的应用实例时,CP需请求MEC Ctl协同获取原AN所对应的MEC平台的应用实例的地址。MEC Ctl中可以保留该应用服务的原实例地址。MEC Ctl在获取到该目标应用服务的目标实例的地址后,则将目标实例的地址和原实例地址一起发送至CP。另一种可能的实现方式中,MEC Ctl也可以只发送该目标服务的目标实例地址,无需发送原实例地址。因为UE在接入该目标服务的原应用实例时,CP已经获知了该目标服务的原实例地址,若CP保存了该原实例地址,MEC Ctl可以不发送原实例地址给CP。
可选的,若目标AN所服务的UP包含多个时,CP可以根据资源池中所述目标AN所对应的UP选择至少一个UP,将所选择的所述至少一个UP的信息通过上述协同请求发送至所述MEC Ctl,MEC Ctl从至少一个UP的信息中所确定的目标UP的信息。例如,资源池包含有各个AN和各个UP的服务映射关系。需要说明的是,由于多个AN可能同时服务一个UP,若原AN与目标AN所服务的UP为同一UP,则CP无需重选新的UP。
MEC Ctl确定目标UP的方式包括两种:
第一种方式为:MEC Ctl根据UE的位置信息确定目标MEC平台,再确定与该目标MEC平台所对应的UP。由于UP与MEC平台是一一对应关系,所以该目标MEC平台所对应的UP则可以确定为目标UP。
第二种方式为:MEC Ctl根据CP所发送的多个UP确定多个UP分别所对应的MEC平台,再根据目标服务的标识确定这些MEC平台中哪个MEC平台部署有该目标应用服务的应用实例,从而确定部署有该目标应用服务的应用实例的MEC平台为目标MEC平台,进而确定与该目标MEC平台所对应的UP为目标UP。
MEC Ctl选择目标UP后,并将目标UP的信息通过响应消息发送至CP。即,MEC Ctl向CP发送的响应消息中还可以包含MEC Ctl所确定的目标UP的信息。
106、CP与目标UP创建用户会话。
由于CP不做报文转发的工作,而UP是用于对报文进行转发的,UE在移动后接入目标AN后,需要使用目标UP进行报文发送,因此CP需要与所确定的目标UP创建用户会话,从而向目标UP发送报文转发策略以及地址转换指示等信息。
107、CP向目标UP发送地址转换指示。目标UP接收CP发送的地址转换指示,所述地址转换指示包含目标应用服务的原实例地址和目标实例的地址。
108、目标UP根据所述地址转换指示将所述目标应用服务与UE的上行报文的转发地址设置为所述目标实例的地址,将所述目标应用服务与所述UE的下行报文的来源地址设置为所述原实例地址。
CP在获取到目标应用服务的原实例地址和目标实例的地址后,则制定地址转换策略,该地址转换策略为:将目标应用服务与UE的上行报文的转发地址设置为该目标实例的地址,将目标应用服务与UE的下行报文的来源地址设置为该原实例地址。如图2所示,在目标UP上设置有网络地址转换(英文全称:Network Address Translation,英文缩写:NAT)功能,目标UP在接收到该地址转换指示后,则按照地址转换策略进行地址转换。这样,UE侧不会感知所连接的目标应用服务已经更换了应用实例,UE侧在发送上行报文时,只需按照原实例地址进行发送。该上行报文到达目标UP时,目标UP则会将该上行报文转发至目标应用服务的目标实例。当目标应用服务的目标应用实例发送下行报文时,目标UP则会将下行报文的来源地址转换为原实例地址。这样,UE侧则不会感知该报文是由目标应用服务的新的实例发送下来的,从而能够识别该下行报文。经过上述应用实例的地址转换方式,UE在移动后,无需与目标应用服务的新实例重新创建业务连接就能够直接进行报文交互,减少了网络时延。
一种可能的实现方式中,UE在移动到该目标AN服务范围内之前,已经进行过至少一次的区域移动,那么有可能造成UE在转换到目标应用服务的目标实例之前,当前所通信的应用实例并非初始应用实例。从而造成CP从MEC Ctl中所获取到的原实例地址并非初始实例的地址。比如,UE开始是通过第一AN接入了某视频业务,UE所连接的该业务的实例地址为第一AN所对应的第一MEC平台的第一实例地址。UE经过一次移动后,接入第二AN,经过地址转换后,实际上与该UE通信的是第二AN所对应的第二MEC平台上的应用实例,该应用实例所对应的则为第二MEC平台上的第二实例地址。UE再次移动后,接入第三AN,CP此时再确定第三MEC平台之前,所获取到的地址并非原始的第一实例地址,而是UE经过一次移动后所转换后的当前的第二实例地址。
在这种情况下,CP获取到的目标应用服务的原实例地址是目标应用服务与UE业务访问所使用的当前实例地址,而非目标应用服务与UE进行业务访问所使用的初始实例地址。即,UE初始接入该目标应用服务所的实例地址。为了实现无论UE进行多少次AN服务区域的转移,都不能让UE感知所连接的目标应用服务的应用实例有变换,网络侧需要将下行报文的转发地址始终设置为UE接入该目标应用服务时的初始实例地址。因此,CP在获取到原实例地址后,还可以查询该原实例地址是否与目标应用服务与UE进行业务访问时的初始实例地址相同。由于每次转移后的地址转换指示都是由CP来制定,因此CP只需根据之前所存储的映射情况进行比对和查询,则能够确定出目标应用服务与终端进行访问连接的初 始实例地址。
基于上述描述的可能的情况,当原实例地址为当前实例地址,而并非初始实例地址时,本申请实施例还可以包括如下步骤:
CP根据所述当前实例地址获取UE接入所述目标应用服务时的初始实例地址;
所述CP根据该初始实例地址和目标实例的地址制定地址转换策略。该策略可用于指示所述目标UP将所述目标应用服务与所述UE的上行报文的转发地址设置为所述目标实例的地址,将所述目标应用服务与所述UE的下行报文的来源地址设置为所述初始实例地址。
上述所描述的实施例中,是将NAT功能设置在UP上,由CP来制定应用实例的地址转换策略,由UP来执行应用实例的地址转换。在另一种实现方式中,NAT功能也可以设置在MEC平台上,由MEC平台来制定应用实例的地址转换策略,并由MEC平台执行应用实例的地址转换。具体系统框架参照图4所示。
在图4架构中,当有应用服务部署在MEC平台上时,都需要向MEC平台发送注册申请。相应的,MEC平台接收目标应用服务发送的注册申请,所述注册申请中包括应用服务的服务地址以及网络地址转换NAT服务请求标识,所述NAT服务请求标识用于请求将UE与所述目标应用服务的业务数据流在所述MEC平台上进行地址转换。需要说明的是,应用服务的服务地址用于通过网络协议(Internet Protocol,简写:IP)地址的形式标记该应用服务。同一个应用服务在所有MEC平台上所使用的服务地址是相同的。在本申请实施例中,无论UE所接入的是哪个应用实例,UE所获取的都是该应用实例所对应的应用服务的服务地址,而非该应用实例的实例地址。
在本申请实施例中,将NAT功能设置在MEC平台上。MEC平台在获取到目标应用服务的服务地址以及NAT服务请求标识后,则可以对该目标应用服务制定地址转换策略。该策略可以为:UE与该目标应用服务的上行报文的转发地址设置为本地应用实例的地址,将本地应用实例所下发给UE的下行报文的来源地址设置为该目标应用服务的服务地址。
参照图5所示,图5实施例描述的是通过图4所示的系统架构实现UE进行新业务建立的流程,本申请实施例中应用实例地址的转换方法的另一实施例包括:
201、当UE发起目标应用服务的服务请求时,CP向MEC Ctl发送协同请求。MEC Ctl接收CP发送的协同请求,所述协同请求包括所述UE的位置信息以及所述目标应用服务的标识。
当UE需要接入目标应用服务业务时,则需要发起服务请求,CP收到服务请求后,向MEC Ctl发送协同请求,以使得UE能够与该目标应用建立会话连接。比如,UE通过UP向该目标应用服务发送业务流报文,UP检测到报文为新的业务流报文,则将服务请求上报给CP。CP则向MEC Ctl发起协同请求,该协同请求携带有UE的位置信息和目标应用服务的标识,以便MEC Ctl根据UE的位置信息和目标应用服务的标识确定UE需要接入的MEC平台的应用实例。
202、MEC Ctl根据所述UE的位置信息以及所述目标应用服务的标识创建所述目标应用服务的业务流特征信息。
MEC Ctl需要先确定UE与哪个MEC平台上的应用实例建立连接,所以MEC Ctl可以根 据UE的位置信息确定MEC平台,比如,UE的位置信息为UE所连接的AN的信息,确定该AN所服务的MEC平台为该UE需要接入的MEC平台。MEC Ctl再根据目标应用服务的标识从该MEC平台中查找到该目标应用服务的服务地址以及实例地址,进而创建该目标应用服务的业务流特征信息。该业务流特征信息可以为五元组信息,包括源端的IP,源端的端口号,所使用的网络通讯协议(传输控制协议/用户数据报协议,英文:Transmission Control Protocol/User Datagram Protocol,简写TCP/UDP协议),目的端的IP,目的端的端口号。该业务流特征信息包括上行业务流特征信息以及下行业务流特征信息。其中,上行业务流特征信息的目的端的IP为所述目标应用服务的服务地址,下行业务流特征信息的源端的IP为所述目标应用服务的实例地址。
203、MEC Ctl向CP发送响应消息。CP接收MEC Ctl发送的响应消息,所述响应消息中包含所述目标应用服务的业务流特征信息。
在本申请实施例中,应用实例的地址转换的策略的制定和具体的转换操作都在MEC平台上执行。因此,MEC Ctl在响应消息中还可以携带指示信息。该指示信息用于指示CP控制UP将该UE与该目标应用服务交互的报文转发至MEC平台上进行地址转换。
需要说明的是,步骤202和203为可选步骤。在另一种实现方式中,业务流特征信息可以由CP来创建。CP在向MEC Ctl发送协同请求后,MEC Ctl只需向CP返回创建业务流特征信息的必要因素:该目标应用服务的服务地址以及所确定的MEC平台上的实例地址。因此,步骤202可以替换为:MEC Ctl根据UE的位置信息以及目标应用服务的标识确定该目标应用服务的服务地址以及所对应的MEC平台上的实例地址。步骤203可以替换为:MEC Ctl向CP发送响应消息,该响应消息中包含所述服务地址以及实例地址。CP根据所述服务地址以及实例地址创建业务流特征信息。
204、CP与UP创建用户会话。
该UP为MEC Ctl所确定的MEC平台所对应的UP。
205、CP向所述UP发送报文转发指示。UP接收CP发送的报文转发指示,所述报文转发指示包含所述目标应用服务的业务流特征信息,所述报文转发指示用于指示UP根据所述目标应用服务的业务流特征信息将UE与所述目标应用服务交互的报文发送至MEC平台进行地址转换。
在本申请实施例中,CP不做地址转换策略。CP在接收到MEC Ctl发送的响应消息后,根据该响应消息中的指示控制UP将该UE与该目标应用服务交互的报文转发至MEC平台上进行地址转换。例如,CP生成相应的报文转发指示,并将该报文转发指示发送至UP。
UP在接收到UE发送的上行报文后,通过所述业务流特征信息确定该上行报文为UE与所述目标应用服务的交互报文。UP则将该上行报文发送至所对应的MEC平台上进行地址转换。UP在接收到应用实例发送的下行报文时,也需将该下行报文发送至MEC平台进行地址转换。
206、UP将目标报文发送至MEC平台。相应的,MEC平台接收所述UP发送的目标报文。
目标报文为UE与所述目标应用服务的交互报文,包括上行报文和下行报文。UP在接收到上行报文或下行报文后,首先根据业务流特征信息确定该上行报文或下行报文为目标 报文。UP再根据报文转发指示将该目标报文发送至MEC平台。
207、MEC平台根据地址转换策略将所述目标报文进行地址转换。
MEC平台在接收到目标报文后,则根据预先制定的地址转换策略修改目标报文的转发地址或者来源地址。比如,若该目标报文为上行报文,MEC平台则将该上行报文的转发地址设置为该目标应用服务在该MEC平台上所部署的应用实例的地址,即,该MEC平台上的本地实例地址;若该目标报文为下行报文,MEC平台则将该下行报文的来源地址设置为该目标应用服务的服务地址。
在本申请实施例中,CP不制定地址转换策略,UP不进行地址转换的执行。CP只需根据MEC平台的报文转发要求向UP下发报文转发指示,UP在接收到UE发送的上行报文后,只需将该上行数据发送至MEC平台进行地址转换,MEC平台将上行报文进行地址转换后发送至UP,UP再转发给目标应用实例。UP在接收到目标应用实例发送的下行报文后,也需将该下行报文发送至MEC平台进行地址转换。MEC平台将进行地址转换后的下行报文发送至UP,UP再将下行数据转发给UE。
本申请实施例中,目标应用服务部署在每个MEC平台使用相同的服务地址,UE在与任一个MEC平台上的应用实例进行报文交互时,UE侧只需使用该服务地址。每个MEC平台都制定有地址转换策略,即,将UE的上行报文的转发地址设置为本地的应用实例的地址,将应用实例的下行报文的来源地址设置为服务地址。这样,需要做地址转换的MEC平台无需动态获取其它MEC平台上应用实例的地址(比如,UE接入该目标应用服务的初始实例地址),减少了信令交互,减少了网络时延。
图5实施例描述了UE进行新业务建立的流程,图5实施例所描述的方案同样适用于当UE移动到另一个AN的服务区域后,网络侧具体为终端访问目标应用服务的报文进行地址转换的场景。当该方案适用于UE移动后,网络侧对报文进行地质转换的场景时,其中的MEC平台为MEC Ctl所确定的UE接入目标AN所对应的新的MEC平台,该新的MEC平台同样具备地址转换的功能。UP为CP与MEC Ctl协同确定的对应该新的MEC平台的目标UP,目标UP根据CP下发的报文转发指示将目标报文转发至新的MEC平台。可参照图5实施例的描述内容,此处不做赘述。
上述实施例描述的是由MEC平台制定地址转换策略和执行地址转换操作。而在如图6所示的本申请实施例的另一种系统架构中,应用实例的地址转换策略依然由MEC平台制定,但是将报文按照指示转发至MEC平台进行地址转换的操作的可以由数据面(英文全称:Data Plane,英文缩写:DP)设备来执行,而不由UP来执行。在图6系统架构中,MEC主机中还设置有DP。DP分别连接UP和MEC平台,DP还与MEC平台上的应用实例连接,DP用于对报文进行转发以及控制等操作。在该架构中,UP与MEC平台之间进行报文交互需要通过DP转发实现。因此,MEC平台在制定好地址转换策略后,可以向DP发送相应的路由规则,由DP根据该路由规则将目标报文发送至MEC平台进行地址转换。具体的实现方式与图5实施例所描述的方式类似,其区别步骤如下:
结合图5实施例,在所述MEC平台接收UP发送的目标报文之前,所述转换方法还包括:
所述MEC平台根据配置的UE地址网段、所述目标应用的服务的服务地址和本地实例地 址生成的路由规则,并将所述路由规则发送至DP。所述DP在接收到UP所发送的所述目标报文后,按照所述路由规则将所述目标报文发送至所述MEC平台进行地址转换处理。
另外,对于UP发送报文至MEC平台和从MEC平台接收报文,均需要通过DP进行转发。
由于MEC平台对应用实例与应用实例之间的报文数据的交互是不需要进行地址转换的,但是对于业务迁移后的UE与应用服务之间的报文数据需要进行地址转换。为了区分这两种报文数据的类型,可以根据UE的网段进行区分。比如网络系统规划UE的地址池(网段)为10.141.0.0/16,DP在通过目标UP接收到一个报文后,解析该报文的源地址,若该源地址属于UE的网段内,那么则确定该报文属于为UE所发送的报文,因此需要发送到MEC平台进行地址转换处理。
MEC平台所制定的路由规则,不仅用于DP确定目标报文是否为UE发送的报文或者发送至UE的报文,还需确定该目标报文是否需要发送至MEC平台进行地址转换。路由规则包括上行路由规则和下行路由规则,上行路由规则包括UE的网段地址和目标应用服务的服务地址之间的映射,下行路由规则包括UE的网段地址和目标应用服务的本地实例地址之间的映射。对于上行报文,DP根据上行路由规则判断该上行报文的来源地址是否为UE网段内的地址,并判断该上行报文的目的转发地址是否与该目标应用服务的服务地址相同。当两者判断结果均为是时,DP则将该上行报文发送至MEC平台进行地址转换。对于下行报文,DP根据下行路由规则判断该下行报文的来源地址是否与目标应用服务的本地实例地址相同,并判断该下行报文的目的转发地址是否为UE网段内的地址。当两者判断结果均为是时,DP则将该下行报文发送至目标UP进行报文转发。
在本实施例中,MEC平台进行地址转换策略的制定。例如,可以由MEC平台上的路径规则控制单元(英文全称:Traffic Rule Control,英文缩写:TRC)来制定地址转换策略。MEC平台还配置路由规则,并将该路由规则发送至DP,由DP来执行具体的报文转发的操作。
参照图7所示,本申请实施例中应用实例地址的转换装置的一个实施例包括:
发送单元301,用于向移动边缘云MEC控制设备发送协同请求,所述协同请求包含所述终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
接收单元302,用于从所述MEC控制设备接收响应信息,所述响应信息包含目标实例的地址,所述目标实例的地址与所述终端的位置信息和所述应用服务的信息关联;
所述发送单元301还用于,根据所述目标实例的地址,向所述目标实例对应的第一用户面设备发送所述目标实例的地址;
处理单元303,用于指示所述第一用户面设备:将所述终端为获取所述应用服务发送的上行报文的转发地址设置为所述目标实例的地址。
可选的,所述装置还包括:
获取单元304,用于根据所述终端当前通信的应用实例的地址,获取所述终端接入所述应用服务时的初始实例地址;
所述处理单元303还用于,指示所述第一用户面设备:将所述目标实例发送至所述终端的下行报文的来源地址设置为所述初始实例地址。
可选的,所述接收单元302还用于:
接收切换请求,所述切换请求用于请求将所述终端从原接入网AN切换至目标AN;
所述装置还包括:
选择单元305,用于根据所述目标AN,选择与所述目标AN对应的至少一个用户面设备,所述协同请求包含所述至少一个用户面设备的信息,所述响应消息包含所述第一用户面设备的信息;
创建单元306,用于创建所述终端与所述第一用户面设备之间的会话。
图7实施例所描述的各个单元在运行时还可以执行图3实施例中CP所执行的步骤,详细内容可参照图3实施例,此处不做赘述。
参照图8所示,本申请实施例中应用实例地址的转换装置的另一实施例包括:
接收单元401,用于从控制面设备接收协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
确定单元402,用于根据所述协同请求,确定所述应用服务的目标实例;
获取单元403,用于获取所述目标实例的地址;其中,所述目标实例为提供所述应用服务的且服务位置范围包含所述终端的位置的应用实例;
发送单元404,用于向所述控制面设备发送响应信息,所述响应信息包含所述目标实例的地址,所述目标实例的地址用于报文的地址转换。
可选的,所述终端的位置信息包括所述终端接入的目标接入网AN的信息;
所述确定单元403具体用于:
根据所述目标AN的信息,确定所述目标AN对应的至少一个移动边缘云MEC平台;
根据所述应用服务的信息从所述至少一个MEC平台确定第一MEC平台,并确定所述第一MEC平台中部署的所述应用服务的应用实例,其中,所述第一MEC平台为提供所述应用服务的MEC平台。
图8实施例所描述的各个单元在运行时还可以执行图3实施例中MEC Ctl所执行的步骤,详细内容可参照图3实施例,此处不做赘述。
参照图9所示,本申请实施例中应用实例地址的转换装置的另一实施例包括:
发送单元501,用于向移动边缘云MEC控制设备发送协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
接收单元502,用于从所述MEC控制设备接收响应信息,所述响应信息包含第一移动边缘云MEC平台的标识,所述第一MEC平台为提供所述应用服务的MEC平台,所述第一MEC平台的标识与所述终端的位置信息和所述应用服务的信息关联;
所述发送单元501还用于,向第一用户面设备发送所述第一MEC平台的标识,并指示所述第一用户面设备:将目标报文发送至所述第一MEC平台,所述目标报文为所述终端访问所述应用服务的报文;
处理单元503,用于控制所述发送单元501执行发送的步骤,以及控制所述接收单元502执行接收的步骤。
可选的,所述响应消息还包括业务流特征信息,所述业务流特征信息与所述终端以及所述应用服务的信息关联;
所述处理单元503还用于:
指示所述第一用户面设备:根据所述业务流特征信息确定目标报文。
图9实施例所描述的各个单元在运行时还可以执行图5实施例中CP所执行的步骤,详细内容可参照图5实施例,此处不做赘述。
参照图10所示,本申请实施例中应用实例地址的转换装置的另一实施例包括:
接收单元601,用于从控制面设备接收协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
确定单元602,用于根据所述协同请求,确定第一移动边缘云MEC平台的标识;其中,所述第一MEC平台为提供所述应用服务的MEC平台;
发送单元603,用于向所述控制面设备发送所述第一MEC平台的标识;
处理单元604,用于指示所述控制面单元:控制第一用户面设备将目标报文发送至第一MEC平台,所述目标报文为所述终端访问所述应用服务的报文。
可选的,所述装置还包括:
获取单元605,用于获取所述应用服务的服务地址以及目标实例地址,所述目标实例为所述应用服务部署在所述第一MEC平台中的应用实例;
创建单元606,用于根据所述服务地址以及所述目标实例地址创建业务流特征信息;
所述发送单元603还用于,向所述控制面设备发送所述业务流特征信息;
所述处理单元604还用于,指示所述控制面设备:控制所述第一用户面设备根据所述业务流特征信息确定目标报文。
图10实施例所描述的各个单元在运行时还可以执行图5实施例中MEC Ctl所执行的步骤,详细内容可参照图5实施例,此处不做赘述。
参照图11所示,本申请实施例中应用实例地址的转换装置的另一实施例包括:
接收单元701,用于从第一用户面设备接收目标报文,所述目标报文为终端访问应用服务的报文,所述应用服务为所述终端接入的应用服务;
设置单元702,用于若所述目标报文为上行报文,将所述目标报文的转发地址设置为目标实例的地址,所述目标实例的地址为所述应用服务在所述MEC平台中部署的应用实例的地址;
所述设置单元702还用于,若所述目标报文为下行报文,将所述目标报文的来源地址设置为所述目标应用服务的服务地址。
可选的,所述接收单元701具体用于:
通过数据面设备从所述第一用户面设备接收所述目标报文;
所述装置还包括:
生成单元703,用于在所述接收单元701通过数据面设备从第一用户面设备接收目标报文之前,根据配置的终端地址网段、所述应用的服务的服务地址以及目标实例的地址生成路由规则;
发送单元704,用于将所述路由规则发送至数据面设备,并指示所述数据面设备:根据所述路由规则将所述目标报文发送至所述MEC平台。
图11实施例所描述的各个单元在运行时还可以执行图5实施例中MEC平台所执行的步骤,详细内容可参照图5实施例,此处不做赘述。
图7-图11实施例所述的装置还有另一个形式的实施例,参照图12所示,包括:处理器801、存储器802、收发器803,所述处理器801、所述存储器802以及所述收发器803通过总线804连接,收发器803可以包括发送器与接收器,所述存储器802存储有计算机指令,所述处理器801通过执行所述计算机指令用于实现图3或图5实施例中应用实例地址的转换方法的功能。具体的实现可以采用各类灵活的设计方式,各个器件相应的功能可以进一步的参考上述方法实施例,本申请不做限制。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部 分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (24)

  1. 一种应用实例地址的转换方法,其特征在于,所述方法包括:
    控制面设备向移动边缘云MEC控制设备发送协同请求,所述协同请求包含所述终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    所述控制面设备从所述MEC控制设备接收响应信息,所述响应信息包含目标实例的地址,所述目标实例的地址与所述终端的位置信息和所述应用服务的信息关联;
    所述控制面设备根据所述目标实例的地址,向所述目标实例对应的第一用户面设备发送所述目标实例的地址,并指示所述第一用户面设备:将所述终端为获取所述应用服务发送的上行报文的转发地址设置为所述目标实例的地址。
  2. 根据权利要求1所述的方法,其特征在于,所述方法还包括:
    所述控制面设备根据所述终端当前通信的应用实例的地址,获取所述终端接入所述应用服务时的初始实例地址;
    所述控制面设备指示所述第一用户面设备:将所述目标实例发送至所述终端的下行报文的来源地址设置为所述初始实例地址。
  3. 根据权利要求1或2所述的方法,其特征在于,所述方法还包括:
    所述控制面设备接收切换请求,所述切换请求用于请求将所述终端从原接入网AN切换至目标AN;
    所述控制面设备根据所述目标AN,选择与所述目标AN对应的至少一个用户面设备,所述协同请求包含所述至少一个用户面设备的信息,所述响应消息包含所述第一用户面设备的信息;
    所述控制面设备创建所述终端与所述第一用户面设备之间的会话。
  4. 一种应用实例地址的转换方法,其特征在于,所述方法包括:
    移动边缘云MEC控制设备从控制面设备接收协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    所述MEC控制设备根据所述协同请求,确定所述应用服务的目标实例,并获取所述目标实例的地址;其中,所述目标实例为提供所述应用服务的且服务位置范围包含所述终端的位置的应用实例;
    所述MEC控制设备向所述控制面设备发送响应信息,所述响应信息包含所述目标实例的地址,所述目标实例的地址用于报文的地址转换。
  5. 根据权利要求4所述的方法,其特征在于,所述终端的位置信息包括所述终端接入的目标接入网AN的信息;
    所述MEC控制设备根据所述协同请求确定所述应用服务的目标实例,包括:
    所述MEC控制设备根据所述目标AN的信息,确定所述目标AN对应的至少一个移动边缘云MEC平台;
    所述MEC控制设备根据所述应用服务的信息从所述至少一个MEC平台确定第一MEC平台,并确定所述第一MEC平台中部署的所述应用服务的应用实例,其中,所述第一MEC平台为提供所述应用服务的MEC平台。
  6. 一种应用实例地址的转换方法,其特征在于,所述方法包括:
    控制面设备向移动边缘云MEC控制设备发送协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    所述控制面设备从所述MEC控制设备接收响应信息,所述响应信息包含第一移动边缘云MEC平台的标识,所述第一MEC平台为提供所述应用服务的MEC平台,所述第一MEC平台的标识与所述终端的位置信息和所述应用服务的信息关联;
    所述控制面设备向第一用户面设备发送所述第一MEC平台的标识,并指示所述第一用户面设备:将目标报文发送至所述第一MEC平台,所述目标报文为所述终端访问所述应用服务的报文。
  7. 根据权利要求6所述的方法,其特征在于,所述响应消息还包括业务流特征信息,所述业务流特征信息与所述终端以及所述应用服务的信息关联;
    所述方法还包括:
    所述控制面设备指示所述第一用户面设备:根据所述业务流特征信息确定目标报文。
  8. 一种应用实例地址的转换方法,其特征在于,所述方法包括:
    移动边缘云MEC控制设备从控制面设备接收协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    所述MEC控制设备根据所述协同请求,确定第一移动边缘云MEC平台的标识;其中,所述第一MEC平台为提供所述应用服务的MEC平台;
    所述MEC控制设备向所述控制面设备发送所述第一MEC平台的标识,并指示所述控制面单元:控制第一用户面设备将目标报文发送至第一MEC平台,所述目标报文为所述终端访问所述应用服务的报文。
  9. 根据权利要求8所述的方法,其特征在于,所述方法还包括:
    所述MEC控制设备获取所述应用服务的服务地址以及目标实例地址,所述目标实例为所述应用服务部署在所述第一MEC平台中的应用实例;
    所述MEC控制设备根据所述服务地址以及所述目标实例地址创建业务流特征信息;
    所述MEC控制设备向所述控制面设备发送所述业务流特征信息,并指示所述控制面设备:控制所述第一用户面设备根据所述业务流特征信息确定目标报文。
  10. 一种应用实例地址的转换方法,其特征在于,所述方法包括:
    移动边缘云MEC平台从第一用户面设备接收目标报文,所述目标报文为终端访问应用服务的报文,所述应用服务为所述终端接入的应用服务;
    若所述目标报文为上行报文,所述MEC平台将所述目标报文的转发地址设置为目标实例的地址,所述目标实例的地址为所述应用服务在所述MEC平台中部署的应用实例的地址;
    若所述目标报文为下行报文,所述MEC平台将所述目标报文的来源地址设置为所述目标应用服务的服务地址。
  11. 根据权利要求10所述的方法,其特征在于,所述MEC平台从第一用户面设备接收目标报文,包括:
    所述MEC平台通过数据面设备从所述第一用户面设备接收所述目标报文;
    在所述MEC平台通过数据面设备从第一用户面设备接收目标报文之前,所述方法还包括:
    所述MEC平台根据配置的终端地址网段、所述应用的服务的服务地址以及目标实例的地址生成路由规则;
    所述MEC平台将所述路由规则发送至数据面设备,并指示所述数据面设备:根据所述路由规则将所述目标报文发送至所述MEC平台。
  12. 一种应用实例地址的转换装置,其特征在于,所述装置包括:
    发送单元,用于向移动边缘云MEC控制设备发送协同请求,所述协同请求包含所述终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    接收单元,用于从所述MEC控制设备接收响应信息,所述响应信息包含目标实例的地址,所述目标实例的地址与所述终端的位置信息和所述应用服务的信息关联;
    所述发送单元还用于,根据所述目标实例的地址,向所述目标实例对应的第一用户面设备发送所述目标实例的地址;
    处理单元,用于指示所述第一用户面设备:将所述终端为获取所述应用服务发送的上行报文的转发地址设置为所述目标实例的地址。
  13. 根据权利要求12所述的装置,其特征在于,所述装置还包括:
    获取单元,用于根据所述终端当前通信的应用实例的地址,获取所述终端接入所述应用服务时的初始实例地址;
    所述处理单元还用于,指示所述第一用户面设备:将所述目标实例发送至所述终端的下行报文的来源地址设置为所述初始实例地址。
  14. 根据权利要求12或13所述的装置,其特征在于,所述接收单元还用于:
    接收切换请求,所述切换请求用于请求将所述终端从原接入网AN切换至目标AN;
    所述装置还包括:
    选择单元,用于根据所述目标AN,选择与所述目标AN对应的至少一个用户面设备,所述协同请求包含所述至少一个用户面设备的信息,所述响应消息包含所述第一用户面设备的信息;
    创建单元,用于创建所述终端与所述第一用户面设备之间的会话。
  15. 一种应用实例地址的转换装置,其特征在于,所述装置包括:
    接收单元,用于从控制面设备接收协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    确定单元,用于根据所述协同请求,确定所述应用服务的目标实例;
    获取单元,用于获取所述目标实例的地址;其中,所述目标实例为提供所述应用服务的且服务位置范围包含所述终端的位置的应用实例;
    发送单元,用于向所述控制面设备发送响应信息,所述响应信息包含所述目标实例的地址,所述目标实例的地址用于报文的地址转换。
  16. 根据权利要求15所述的装置,其特征在于,所述终端的位置信息包括所述终端接入的目标接入网AN的信息;
    所述确定单元具体用于:
    根据所述目标AN的信息,确定所述目标AN对应的至少一个移动边缘云MEC平台;
    根据所述应用服务的信息从所述至少一个MEC平台确定第一MEC平台,并确定所述第一MEC平台中部署的所述应用服务的应用实例,其中,所述第一MEC平台为提供所述应用服务的MEC平台。
  17. 一种应用实例地址的转换装置,其特征在于,所述装置包括:
    发送单元,用于向移动边缘云MEC控制设备发送协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    接收单元,用于从所述MEC控制设备接收响应信息,所述响应信息包含第一移动边缘云MEC平台的标识,所述第一MEC平台为提供所述应用服务的MEC平台,所述第一MEC平台的标识与所述终端的位置信息和所述应用服务的信息关联;
    所述发送单元还用于,向第一用户面设备发送所述第一MEC平台的标识,并指示所述第一用户面设备:将目标报文发送至所述第一MEC平台,所述目标报文为所述终端访问所述应用服务的报文;
    处理单元,用于控制所述发送单元执行发送的步骤,以及控制所述接收单元执行接收的步骤。
  18. 根据权利要求17所述的装置,其特征在于,所述响应消息还包括业务流特征信息,所述业务流特征信息与所述终端以及所述应用服务的信息关联;
    所述处理单元还用于:
    指示所述第一用户面设备:根据所述业务流特征信息确定目标报文。
  19. 一种应用实例地址的转换装置,其特征在于,所述装置包括:
    接收单元,用于从控制面设备接收协同请求,所述协同请求包含终端的位置信息以及应用服务的信息,其中,所述应用服务为所述终端接入的应用服务;
    确定单元,用于根据所述协同请求,确定第一移动边缘云MEC平台的标识;其中,所述第一MEC平台为提供所述应用服务的MEC平台;
    发送单元,用于向所述控制面设备发送所述第一MEC平台的标识;
    处理单元,用于指示所述控制面单元:控制第一用户面设备将目标报文发送至第一MEC平台,所述目标报文为所述终端访问所述应用服务的报文。
  20. 根据权利要求19所述的装置,其特征在于,所述装置还包括:
    获取单元,用于获取所述应用服务的服务地址以及目标实例地址,所述目标实例为所述应用服务部署在所述第一MEC平台中的应用实例;
    创建单元,用于根据所述服务地址以及所述目标实例地址创建业务流特征信息;
    所述发送单元还用于,向所述控制面设备发送所述业务流特征信息;
    所述处理单元还用于,指示所述控制面设备:控制所述第一用户面设备根据所述业务流特征信息确定目标报文。
  21. 一种应用实例地址的转换装置,其特征在于,所述装置包括:
    接收单元,用于从第一用户面设备接收目标报文,所述目标报文为终端访问应用服务 的报文,所述应用服务为所述终端接入的应用服务;
    设置单元,用于若所述目标报文为上行报文,将所述目标报文的转发地址设置为目标实例的地址,所述目标实例的地址为所述应用服务在所述MEC平台中部署的应用实例的地址;
    所述设置单元还用于,若所述目标报文为下行报文,将所述目标报文的来源地址设置为所述目标应用服务的服务地址。
  22. 根据权利要求21所述的装置,其特征在于,所述接收单元具体用于:
    通过数据面设备从所述第一用户面设备接收所述目标报文;
    所述装置还包括:
    生成单元,用于在所述接收单元通过数据面设备从第一用户面设备接收目标报文之前,根据配置的终端地址网段、所述应用的服务的服务地址以及目标实例的地址生成路由规则;
    发送单元,用于将所述路由规则发送至数据面设备,并指示所述数据面设备:根据所述路由规则将所述目标报文发送至所述MEC平台。
  23. 一种计算机可读存储介质,包括指令,当其在计算机上运行时,使得计算机执行如权利要求1-3或4-5或6-7或8-9或10-11任意一项所述的方法。
  24. 一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行如权利要求1-3或4-5或6-7或8-9或10-11任意一项所述的方法。
PCT/CN2018/087860 2017-06-30 2018-05-22 一种应用实例地址的转换方法和装置 WO2019001174A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21168289.3A EP3920595A1 (en) 2017-06-30 2018-05-22 Application instance address translation method and apparatus
EP18823492.6A EP3627897B1 (en) 2017-06-30 2018-05-22 Application instance address translation method and apparatus
US16/710,449 US11140665B2 (en) 2017-06-30 2019-12-11 Application instance address translation method and apparatus
US17/493,580 US11696290B2 (en) 2017-06-30 2021-10-04 Application instance address translation method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710530099.XA CN109218455B (zh) 2017-06-30 2017-06-30 一种应用实例地址的转换方法和装置
CN201710530099.X 2017-06-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/710,449 Continuation US11140665B2 (en) 2017-06-30 2019-12-11 Application instance address translation method and apparatus

Publications (1)

Publication Number Publication Date
WO2019001174A1 true WO2019001174A1 (zh) 2019-01-03

Family

ID=64740338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087860 WO2019001174A1 (zh) 2017-06-30 2018-05-22 一种应用实例地址的转换方法和装置

Country Status (4)

Country Link
US (2) US11140665B2 (zh)
EP (2) EP3920595A1 (zh)
CN (2) CN109218455B (zh)
WO (1) WO2019001174A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021009166A1 (en) * 2019-07-16 2021-01-21 Telefonaktiebolaget Lm Ericsson (Publ) Enabling nat for user plane traffic
CN114270789A (zh) * 2019-08-20 2022-04-01 华为技术有限公司 一种获取信息的方法及装置
EP3979700A4 (en) * 2019-06-24 2022-08-31 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR TRANSMITTING A SERVICE MESSAGE

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11310107B2 (en) * 2018-06-20 2022-04-19 NEC Laboratories Europe GmbH Multi-access edge computing, MEC, system and method for operating the same
US11290561B2 (en) * 2019-02-07 2022-03-29 Verizon Patent And Licensing Inc. Methods and systems for managing applications of a multi-access edge computing environment
US11552900B2 (en) * 2019-03-18 2023-01-10 Sony Group Corporation Management for managing resource allocation in an edge computing system
CN111800282B (zh) * 2019-04-08 2023-03-28 阿里巴巴集团控股有限公司 网络系统、实例管控方法、设备及存储介质
CN110290506B (zh) * 2019-04-17 2020-08-14 中国联合网络通信集团有限公司 一种边缘云移动性管理方法及设备
CN110290140B (zh) * 2019-06-28 2021-09-24 腾讯科技(深圳)有限公司 多媒体数据处理方法及装置、存储介质、电子设备
CN112217856B (zh) * 2019-07-11 2024-06-18 华为技术有限公司 应用实例的地址获取方法、装置、设备及存储介质
CN110896411B (zh) * 2019-07-15 2021-07-27 腾讯科技(深圳)有限公司 一种业务处理方法及相关设备
CN110912835B (zh) * 2019-11-08 2023-04-07 腾讯科技(深圳)有限公司 业务分流方法、装置及系统
CN112953992B (zh) * 2019-12-11 2023-06-23 阿里巴巴集团控股有限公司 网络系统、通信与组网方法、设备及存储介质
TWI739237B (zh) * 2019-12-13 2021-09-11 中華電信股份有限公司 用於行動邊緣運算設備之訊務繞送系統與方法
CN113055426A (zh) * 2019-12-28 2021-06-29 中移(成都)信息通信科技有限公司 业务访问方法、装置、设备和介质
WO2021135663A1 (zh) * 2019-12-31 2021-07-08 华为技术有限公司 应用实例确定的方法、装置及系统
CN113259260A (zh) * 2020-02-11 2021-08-13 华为技术有限公司 部署应用实例和调度应用实例的方法和装置
CN113382032B (zh) * 2020-03-10 2022-12-09 阿里巴巴集团控股有限公司 云节点变更、网络扩展、服务提供方法、设备及介质
CN114124817B (zh) 2020-03-15 2023-03-14 腾讯科技(深圳)有限公司 基于边缘计算的通信方法、装置、介质及电子设备
CN111447652B (zh) * 2020-03-20 2022-07-01 中移雄安信息通信科技有限公司 移动终端的移动边缘运算主机的切换方法、装置及设备
CN113949705B (zh) * 2020-06-29 2023-07-11 华为技术有限公司 通信方法和通信装置
CN114095562A (zh) * 2020-07-31 2022-02-25 中国电信股份有限公司 边缘应用发现方法、系统以及增强防火墙
CN114079649A (zh) * 2020-08-19 2022-02-22 华为技术有限公司 地址分配方法、设备及系统
CN113014630A (zh) * 2021-02-10 2021-06-22 腾讯科技(深圳)有限公司 实现通信连续性的方法及相关设备
CN113364684B (zh) * 2021-05-07 2023-01-17 联想(北京)有限公司 一种信息处理方法、边缘计算平台及存储介质
US11689982B2 (en) * 2021-08-24 2023-06-27 Verizon Patent And Licensing Inc. Weighted MEC selection for application-based MEC traffic steering

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102170667A (zh) * 2010-02-25 2011-08-31 中兴通讯股份有限公司 一种实现基站间切换的方法、系统及基站装置
CN106304228A (zh) * 2016-09-05 2017-01-04 广东工业大学 一种pgw切换控制方法、系统及服务器
WO2017070895A1 (zh) * 2015-10-29 2017-05-04 华为技术有限公司 移动边缘平台确定承载的方法及装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20150110103A (ko) * 2014-03-24 2015-10-02 삼성전자주식회사 전송 경로 최적화를 위한 컨텐츠 서버 간 핸드오버 방법 및 장치
WO2016203798A1 (ja) * 2015-06-19 2016-12-22 ソニー株式会社 装置及び方法
CN106470449B (zh) * 2015-08-14 2020-04-10 电信科学技术研究院 一种数据收发、中继方法、装置及通信系统
US10004019B2 (en) * 2015-09-08 2018-06-19 Parallel Wireless, Inc. RAN for multimedia delivery
WO2017066945A1 (zh) 2015-10-21 2017-04-27 华为技术有限公司 Mec平台的切换方法、装置及系统
CN106900031A (zh) * 2015-12-17 2017-06-27 中国电信股份有限公司 Cu分离场景下用户面网关重选的方法、装置和系统
CN105656992B (zh) * 2015-12-25 2019-04-16 厦门大学 一种面向次等移动内容的分发系统的内容分发装置及其方法
US20190058767A1 (en) * 2016-01-22 2019-02-21 Nokia Solutions And Networks Oy Application relocation between clouds
CN106231607A (zh) * 2016-09-21 2016-12-14 北京佰才邦技术有限公司 一种资源分配的方法及基站
US20190380028A1 (en) * 2016-11-22 2019-12-12 Nokia Technologies Oy User equipment identity implementation in mobile edge scenarios
US10326766B2 (en) * 2017-07-13 2019-06-18 Dell Products, Lp Method and apparatus for optimizing mobile edge computing for nomadic computing capabilities as a service
EP3732932A4 (en) * 2017-12-30 2022-05-11 INTEL Corporation WIRELESS COMMUNICATION METHODS AND DEVICES

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102170667A (zh) * 2010-02-25 2011-08-31 中兴通讯股份有限公司 一种实现基站间切换的方法、系统及基站装置
WO2017070895A1 (zh) * 2015-10-29 2017-05-04 华为技术有限公司 移动边缘平台确定承载的方法及装置
CN106304228A (zh) * 2016-09-05 2017-01-04 广东工业大学 一种pgw切换控制方法、系统及服务器

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ETSI: "Mobile Edge Computing (MEC) Framework and Reference Architecture", ETSI GS MEC 003, 31 March 2016 (2016-03-31), pages 7 - 18, XP055568743 *
See also references of EP3627897A4

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3979700A4 (en) * 2019-06-24 2022-08-31 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR TRANSMITTING A SERVICE MESSAGE
WO2021009166A1 (en) * 2019-07-16 2021-01-21 Telefonaktiebolaget Lm Ericsson (Publ) Enabling nat for user plane traffic
US20220377043A1 (en) * 2019-07-16 2022-11-24 Telefonaktiebolaget Lm Ericsson (Publ) Enabling nat for user plane traffic
CN114270789A (zh) * 2019-08-20 2022-04-01 华为技术有限公司 一种获取信息的方法及装置
CN114270789B (zh) * 2019-08-20 2023-09-01 华为技术有限公司 一种获取信息的方法及装置

Also Published As

Publication number Publication date
EP3627897A1 (en) 2020-03-25
CN113194157B (zh) 2022-10-28
EP3920595A1 (en) 2021-12-08
US20220030585A1 (en) 2022-01-27
EP3627897B1 (en) 2021-07-07
CN109218455A (zh) 2019-01-15
CN109218455B (zh) 2021-04-09
US20200120665A1 (en) 2020-04-16
CN113194157A (zh) 2021-07-30
EP3627897A4 (en) 2020-05-20
US11696290B2 (en) 2023-07-04
US11140665B2 (en) 2021-10-05

Similar Documents

Publication Publication Date Title
US11696290B2 (en) Application instance address translation method and apparatus
US11381961B2 (en) Method, apparatus, network device, and system for releasing IP address
US11924922B2 (en) Application mobility mechanism for edge computing
WO2019042000A1 (zh) 实例切换方法及相关装置
WO2019196811A1 (zh) 通信方法和相关装置
WO2017066945A1 (zh) Mec平台的切换方法、装置及系统
US20210120620A1 (en) Communication Method and Apparatus
WO2017201722A1 (zh) 一种通信控制的方法及相关网元
US11647452B2 (en) Application-driven user slice selection for mobile networks
JP2019511177A (ja) モバイル協働型コミュニケーション方法及び装置
CN111837371A (zh) 基于增强mptcp的应用移动性
WO2020200242A1 (zh) 会话处理的方法、通信装置及通信系统
US10412640B2 (en) Switching control method, apparatus, and wireless communications network
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
CN110138885A (zh) 地址分配方法及装置
AU2021247720B2 (en) Communication method and apparatus
US20170013512A1 (en) Method for selecting shunt gateway and controller
WO2013053133A1 (zh) 业务数据传输处理方法、设备以及通信系统
WO2018129665A1 (zh) 通信方法、网络开放功能网元和控制面网元
WO2018188728A1 (en) Handover with no or limited mme involvement
Choi et al. Support for edge computing in the 5G network
WO2013097747A1 (zh) 一种报文转发的方法与小基站
WO2018076234A1 (zh) 一种通信方法和设备
WO2017091986A1 (zh) 业务流转发功能部署方法、装置及系统
US20200137726A1 (en) Communications device and communication method

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: 18823492

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018823492

Country of ref document: EP

Effective date: 20191219