CN108737271B - Message routing method, device and system - Google Patents
Message routing method, device and system Download PDFInfo
- Publication number
- CN108737271B CN108737271B CN201710245998.5A CN201710245998A CN108737271B CN 108737271 B CN108737271 B CN 108737271B CN 201710245998 A CN201710245998 A CN 201710245998A CN 108737271 B CN108737271 B CN 108737271B
- Authority
- CN
- China
- Prior art keywords
- mobile edge
- application
- address
- edge host
- terminal
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/20—Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a message routing method, a device and a system, comprising a mobile edge host receiving a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, the mobile edge host is provided with an application example of the application, and the application example has the IP address; and the mobile edge host converts the IP address into the IP address of the application example and routes the message to the application example. Before a mobile edge host receives a terminal message, a mobile edge management system deploys an application instance of the application in the mobile edge host in advance; or when the mobile edge host receives the terminal message, the mobile edge management system requests the mobile edge host to deploy the application instance of the application. By the invention, the terminal can access the application nearby after moving, and the service experience of the terminal user is improved.
Description
Technical Field
The present application relates to the field of network application technologies, and in particular, to a method, an apparatus, and a system for routing a packet.
Background
Mobile edge computing is the ability to provide cloud-based computing to a user on the wireless network side near the mobile user, which the user can employ to deploy applications at the edge of the network. The mobile edge computing may also provide real-time wireless network information (e.g., user location, base station loading, etc.) that users may develop differentiated applications. After the cloud computing capability is deployed to the edge of the network, a carrier-class service environment with high performance, low delay and high bandwidth can be created, distribution and downloading of various contents, services and applications in the network are accelerated, and consumers can enjoy high-quality network experience.
Ultra-low latency traffic is sensitive to delay, and both the transmission path and the forwarding node increase latency. The mobile edge calculation makes the content and the service deployed close to the user, and the transmission path is short, and the number of forwarding nodes is small, so the mobile edge calculation is a necessary condition for realizing the ultra-low service. Typical scenario car networking, industrial control, telemedicine, virtual reality/augmented reality, etc.
For the service with super-large bandwidth, the super-large bandwidth flow is processed nearby by mobile edge calculation and nearby deployment, and the impact of the large bandwidth on a backbone network can be greatly reduced. Typical scenes such as stadium events live, concert live, mobile content distribution, etc.
As shown in fig. 1, suppose an application creates application instances on different mobile edge hosts, respectively, and creates application instance 1 on mobile edge host 1, where the IP address is IP 1; an application instance 2 is created on the mobile edge host 2 with an IP address of IP 2. Application example 1 and application example 2 are the results of the same piece of application code running on host 1 and host 2, respectively. The deployer of the application may decide to deploy the application instance on all mobile edge hosts, or on a specified area of mobile edge hosts. The application instance can be deployed on a designated mobile edge host in advance, or can be dynamically created by the mobile edge management system when needed.
In the initial state, a terminal (such as a smart phone, a vehicle-mounted communication device, and the like) communicates with an application instance 1 located on a mobile edge host 1 through a wireless access device 1, and a destination IP address in a message sent by the terminal is IP 1.
The terminal moves from wireless access apparatus 1 to wireless access apparatus 2 while the session is in progress. At this time, the terminal still accesses IP1, and the access path of the message is that the terminal accesses the IP address IP1 of the application instance 1 located on the mobile edge host 1 via the mobile edge host 2.
Because the terminal cannot access the application nearby after moving, the service experience of the terminal user is influenced, network resources are wasted, and the communication efficiency is low.
Disclosure of Invention
In order to solve the problems in the prior art and realize that the terminal can access the application nearby after moving, the embodiment of the invention provides a message routing method, which comprises the following steps:
a mobile edge host receives a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, an application instance of the application is deployed on the mobile edge host, and the application instance has the IP address;
and the mobile edge host converts the IP address into the IP address of the application example and routes the message to the application example.
Optionally, before the mobile edge host receives the terminal packet, the mobile edge management system deploys the application instance of the application in advance on the mobile edge host, or when the mobile edge host receives the terminal packet, the mobile edge management system requests the mobile edge host to deploy the application instance of the application.
When the terminal is switched to the coverage area of the adjacent mobile edge host, the adjacent mobile edge host receives the message of the terminal, and the message carries the IP address:
when the adjacent mobile edge host is deployed with the application instance of the application in advance, the adjacent mobile edge host converts the IP address into the IP address of the application instance deployed on the adjacent mobile edge host, and routes the message to the application instance of the application deployed on the adjacent mobile edge host; or
And when the adjacent mobile edge host does not deploy the application instance of the application in advance, the mobile edge management system requests the adjacent mobile edge host to deploy the application instance of the application, wherein the application instance requested to be deployed at the adjacent mobile edge host and the application instance deployed at the mobile edge host have different IP addresses.
And the adjacent mobile edge host converts the IP address into the IP address of the application instance deployed on the adjacent mobile edge host, and routes the message to the application instance of the application deployed on the adjacent mobile edge host.
Optionally, the mobile edge host and the adjacent mobile edge host are provided with a network address translation rule, where the rule includes a mapping relationship between an IP address of an application accessed by the terminal and an IP address of an application instance deployed on the mobile edge host serving the terminal or the adjacent mobile edge host; and the mobile edge host and the adjacent mobile edge host carry out address translation according to the network address translation rule.
By the method, the terminal can access the application instance of the application nearby, the service experience of the terminal user is improved, and network resources are saved.
The embodiment of the invention also provides a mobile edge host, which comprises
The mobile edge host is used for receiving a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, an application instance of the application is deployed on the mobile edge host, and the application instance has the IP address;
address translation means for translating the IP address to an IP address of the application instance;
and the routing device is used for routing the message to the corresponding application example according to the converted IP address.
Embodiments of the present invention also provide a mobile edge communication system, comprising a mobile edge host and one or more neighboring mobile edge hosts,
the mobile edge host is used for receiving a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, an application instance of the application is deployed on the mobile edge host, and the application instance has the IP address; the mobile edge host converts the IP address into the IP address of the application example and routes the message to the application example;
and the adjacent mobile edge host is used for receiving the message of the terminal when the terminal is switched to the coverage area of the terminal, wherein the message carries the IP address, converting the IP address into the IP address of the application instance deployed on the adjacent mobile edge host, and routing the message to the application instance of the application deployed on the adjacent mobile edge host.
Wherein the application instance deployed by the mobile edge host and the application instance deployed by the adjacent mobile edge host have different IP addresses.
Optionally, the mobile edge management system is configured to deploy, before a mobile edge host receives a terminal packet, an application instance of the application in advance on the mobile edge host; or when the mobile edge host receives the terminal message, requesting the mobile edge host to deploy the application instance of the application.
Optionally, when the terminal switches to the coverage of the adjacent mobile edge host and the adjacent mobile edge host does not deploy the application instance of the application, the mobile edge management system requests the adjacent mobile edge host to deploy the application instance of the application.
An embodiment of the present invention further provides a mobile edge host, which may include: a processor, a communication interface, a bus, and a memory. The memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and the processor executes the computer execution instructions stored by the memory so as to enable the mobile edge host or the adjacent mobile edge host to execute all or part of the steps.
An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores an executable program, where the executable program may be a program for implementing all or part of steps executed by a mobile edge host or an adjacent mobile edge host in the message routing method.
Embodiments of the present invention also provide a computer program product for performing the above-mentioned methods when the computer program product is executed.
By the method, the device and the system of the embodiment, the terminal can access the application instance on the mobile edge host nearby, the service experience of a terminal user is improved, and network resources are saved.
Drawings
FIG. 1 is a schematic diagram of prior art terminal message routing;
FIG. 2 is a reference architecture for moving edge computation according to an embodiment of the present invention;
FIG. 3a is a flowchart of a mobile edge management system configuring a virtual IP address for an application and creating an application instance according to an embodiment of the present invention;
FIG. 3b is a flowchart of a mobile edge management system configuring an IP address for an application and creating an application instance according to an embodiment of the present invention;
fig. 4 is a schematic diagram of terminal message routing according to an embodiment of the present invention;
fig. 5 is a flowchart of message address translation and routing during terminal switching according to an embodiment of the present invention.
FIG. 6 is a block diagram of a mobile edge host according to an embodiment of the present invention;
FIG. 7 is a location diagram of an address translation device or function according to an embodiment of the invention;
FIG. 8 is a diagram of a mobile edge communication system according to an embodiment of the present invention
Fig. 9 is a hardware configuration diagram of a mobile edge host according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The european telecommunications standardization organization (ETSI) defines in its specification ETSI GS MEC 003 the reference architecture for mobile edge computing, which, as shown in fig. 2, is mainly composed of two parts: a Mobile Edge Host (Mobile Edge Host) and a Mobile Edge Management System (Mobile Edge Management System). The Mobile Edge host comprises a Mobile Edge platform and a virtualization infrastructure, wherein the virtualization infrastructure provides virtualized computing, storage and network resources for a Mobile Edge application (Mobile Edge App), and the Mobile Edge application is deployed on the Mobile Edge host in the form of a virtual machine or a container. The virtualization infrastructure contains a data plane that implements flow rules from the mobile edge platform and performs routing functions for the messages. Each mobile edge host is also deployed with a mobile edge platform, which includes some common services, such as terminal location service, wireless network information service, DNS (domain Name system) server or DNS proxy service, etc., which can be used by the mobile edge application. The Service registration function of the Mobile Edge platform provides the Mobile Edge application with the capability to discover and use the Mobile Edge Service (Mobile Edge Service). The flow rule service receives flow rules from the mobile edge management system and issues the flow rules to the data plane. The DNS service receives mapping rules for domain names and IP addresses from the mobile edge management system. The Mobile Edge management system includes a Mobile Edge organizer (Mobile Edge editor), a Mobile Edge Platform Manager (Mobile Edge Platform Manager), a virtualization Infrastructure Manager (virtualization Infrastructure Manager), and the like. The mobile edge orchestrator maintains an overall view of all mobile edge hosts, available resources, available mobile edge services in the mobile edge system, triggering instantiation and termination of applications. The mobile edge platform manager is used for managing the mobile edge platform, managing the life cycle of the mobile edge application, and managing the flow rules and DNS rules of the application. The virtualization infrastructure manager manages the virtualized resources needed for the mobile edge application.
The mobile edge management system receives a request message for creating a certain application, wherein the request may come from an operation support system or other systems of an operator; the mobile edge management system allocates an IP address for the application and sends a request message for configuring a DNS rule to the mobile edge host, wherein the DNS rule is the mapping between the domain name of the application and the allocated IP address. The IP address may be a virtual IP address or a real IP address, and it should be noted that the "IP address" described in various embodiments of the present invention refers to a real IP address, that is, an internet protocol address capable of identifying a real application instance or other entity, and is different from the "virtual IP address" described above. The "virtual IP address" described in various embodiments of the present invention is not a real IP address, but is only used to identify an application, for example, a terminal obtains the virtual IP address through a DNS and uses the virtual IP address when accessing an application instance of the application, and the virtual IP address may be in an IP address format, but cannot represent a real IP address of an application instance. Further, the mobile edge management system interacts with one or more mobile edge hosts, allocates resources such as computation, storage, network, etc. on the mobile edge hosts, and deploys application instances of the application on the mobile edge hosts, the application instances are created based on image files of the application, and the application instances may run in virtual machines or containers. The terminal uses or accesses a certain application, the specific form is to use or access an application instance deployed on the mobile edge host, the program contents of a plurality of different application instances corresponding to one application are the same, and only the recorded terminal running states may be different. In addition, a plurality of application instances corresponding to a certain application have independent and different IP addresses. Fig. 3a is a flowchart of the mobile edge management system configuring a virtual IP address for an application and creating an application instance, and the steps are as follows:
301. the mobile edge management system receives a request message to create an application, which may come from the operator's operational support system or other system.
302. The mobile edge management system allocates a virtual IP address IP _ A to the application, and the terminal accesses the application through the IP address.
303. The mobile edge management system interacts with the mobile edge host 1, allocates resources such as computation, storage, network, etc. on the mobile edge host 1, and deploys application instances thereon. The IP address assigned to the application instance in this step is IP 1.
304. The mobile edge management system sends a request message for configuring a Network Address Translation (NAT) rule for translating the destination virtual IP Address IP _ a to IP1 to the mobile edge host 1.
305. And the mobile edge host 1 answers after finishing the NAT rule configuration.
306. The mobile edge management system sends a request message to the mobile edge host 1 to configure a DNS rule, which is a mapping of the domain name and IP address IP _ a of the application.
307. The mobile edge host 1 replies after completing DNS rule configuration.
The flows of the mobile edge management system for allocating resources on other mobile edge hosts, deploying applications, configuring NAT rules, configuring DNS rules are similar to the flow on the mobile edge host 1, except that the IP address allocated to each application instance is different, and further the IP address in the NAT rule is different, for example, the IP address of the application instance 2 deployed on the mobile edge host 2 is IP2, and the NAT rule configured is to convert the destination virtual IP address IP _ a into IP 2. After completing the creation and configuration of the application instance on each mobile edge host, the mobile edge management system sends a create application reply message to the requestor.
Fig. 3b is a flowchart of the mobile edge management system configuring a real IP address for an application and creating an application instance, and the steps are as follows:
401. the mobile edge management system receives a request message to create an application, which may come from the operator's operational support system or other system.
402. The mobile edge management system interacts with the mobile edge host 1, allocates resources such as computation, storage, network, etc. on the mobile edge host 1, and deploys application instances thereon. The real IP address assigned to the application instance in this step is IP 1.
403. The mobile edge management system sends a request message to mobile edge host 1 to configure DNS rules, which are a mapping of the domain name and IP address IP1 of the application.
404. The mobile edge host 1 replies after completing DNS rule configuration.
405. The mobile edge management system interacts with the mobile edge host 2, allocates resources such as computation, storage, network, etc. on the mobile edge host 1, and deploys application instances thereon. The real IP address assigned to the application instance in this step is IP 2.
406. The mobile edge management system sends a configure network address translation rule request message to the mobile edge host 2, the rule being to translate the destination IP address IP1 to IP 2.
407. The mobile edge host 2 answers after completing the NAT rule configuration.
408. The mobile edge management system sends a request message to mobile edge host 2 to configure DNS rules, which are a mapping of the domain name and IP address IP2 of the application.
409. The mobile edge host 2 replies after completing DNS rule configuration.
410. The mobile edge management system sends a configure network address translation rule request message to mobile edge host 1, the rule being to translate the destination IP address IP2 to IP 1.
411. The mobile edge management system replies to the operator's operator support system or other systems.
In the above flow, when the IP address of the application cached by the terminal is IP2, an application access request is initiated at the mobile edge host 1. The terminal now accesses the application via IP 2. Mobile edge host 1 translates IP2 to the address of local instance IP 1.
In the above flow, when the IP address of the application cached by the terminal is IP1, an application access request is initiated at the mobile edge host 2. The terminal now accesses the application via IP 1. Mobile edge host 2 translates IP1 to the address of local instance IP 2.
As described above, the mobile edge management system allocates an IP address to the application, where the IP address may be a virtual IP address, and specifically, the mobile edge management system sends a message configuring a DNS rule to the mobile edge host, where the DNS rule is a mapping between a domain name of the application and the virtual IP address; in addition, the IP address may also be an IP address of an application instance of the application, specifically, the mobile edge management system sends a message configuring a DNS rule to the mobile edge host, where the DNS rule is a mapping between a domain name of the application and an IP address of an application instance deployed on the mobile edge host. The terminal can acquire the IP address of the accessed application from the DNS of the mobile edge host through a domain name resolution process.
And the terminal accesses the application through the allocated virtual or real IP address, and specifically sends a message carrying the IP address to the terminal. A mobile edge host that covers and serves the terminal receives a message sent by the terminal through a wireless access device (e.g., a base station) and performs Network Address Translation (NAT), translating a destination IP address of the message to an IP address of an application instance deployed on the mobile edge host and routing the message to the application instance. The terminal accesses the application nearby through the conversion between the IP address of the application and the real IP address of the application instance corresponding to the application. If the terminal accesses through the allocated virtual IP address, the NAT rule is the mapping relation between the virtual IP address and the application instance IP address deployed by the mobile edge host serving the terminal. If the terminal accesses through the allocated IP address, the NAT rule is the mapping relation between the IP address and the IP address of the application instance deployed by the mobile edge host serving the terminal. If the IP address is exactly the same as the application instance IP address deployed by the mobile edge host, the above address translation process may not be executed, and certainly, the translation may be performed, but the translated IP address is the same as the IP address before the translation.
The mobile edge management system maintains and configures a mapping relationship between an application's IP address and the application instance's IP address for the application on each edge host. In order to enable the terminal to access the application quickly after switching and reduce the time delay, the mobile edge management system can configure corresponding application instances and corresponding mapping relations on adjacent mobile edge hosts in advance. Referring to fig. 4, if mobile edge host 1 and mobile edge host 2 are adjacent mobile edge hosts, if the terminal device is located in the coverage of mobile edge host 1 and needs to access application a at this time, then for application a, the mobile edge management system configures a mapping relationship that IP address IP _ a of application a is converted into IP address IP1 of an application instance on mobile edge host 1, and IP1 is the IP address of application instance 1 corresponding to application a on mobile edge host 1; the mobile edge management system may deploy an application instance 2 of application a on the mobile edge host 2 in advance, with the IP address IP2, and configure a mapping relationship that IP _ a translates to IP 2. For the application N, the mapping relationship for converting IP _ N into IPx is configured on the mobile edge host 1, and the mapping relationship for converting IP _ N into IPy is configured on the mobile edge host 2, which may specifically refer to the following mapping relationship table one.
The operator can determine the range and number of adjacent mobile edge hosts according to its own needs or pre-established corresponding rules, and configure application instances through the mobile edge management system, for example: the range of the neighboring mobile edge host may be determined according to the service distance (physical distance) between the neighboring mobile edge host and the terminal, for example, the neighboring mobile edge host with a certain range (physical distance 5KM) is selected to perform the above-mentioned advance deployment with the terminal as the center. It is also possible that the mobile edge management system detects that the terminal is handing off and then deploys an application instance on an adjacent target mobile edge host during the terminal handoff process. Thus, when the terminal is switched to the adjacent mobile edge host, the adjacent mobile edge host directly routes the message sent by the terminal to the local application instance, otherwise, before the adjacent mobile edge host locally deploys the corresponding application instance, the adjacent mobile edge host may need to route the message to the mobile edge host accessed before the terminal is switched, or cache the message to wait for the local application instance to be deployed completely.
| Main unit | IP address | Application instance IP address |
| Mobile edge host 1 | IP_A | IP1 |
| Mobile edge host 2 | IP_A | IP2 |
| Mobile edge host 1 | IP_N | IPx |
| Mobile edge host 2 | IP_N | IPy |
Watch 1
Referring to fig. 4, when the terminal switches from the coverage of the mobile edge host 1 to the coverage of the adjacent mobile edge host 2, if the terminal needs to access the application a before the switching, the destination IP address carried in the subsequent message sent by the terminal will remain unchanged and still be the IP address IP _ a of the application a. When the adjacent mobile edge host 2 deploys the application instance 2 of the application a in advance, the adjacent mobile edge host 2 converts the IP address into the IP address IP2 of the locally deployed application instance 2 through NAT, and routes the packet to the application instance 2. And if the adjacent mobile edge host does not have the application instance of the application deployed in advance, the mobile edge management system requests the adjacent mobile edge host to deploy the application instance of the application.
In the following, a detailed description is provided with reference to fig. 5, in which the IP address allocated by the mobile edge management system for the application a is a virtual IP address IP _ a.
501. If the edge host of the current service terminal is the mobile edge host 1, and the application instance 1 of the application a is deployed on the mobile edge host 1, the terminal accesses the application instance 1 of the application a through the virtual IP address IP _ a of the application a.
502. The mobile edge host 1 performs address translation on the message according to the configured NAT rule, and translates the destination IP address IP _ a carried by the message into the real IP address IP1 of the application instance 1 on the host.
503a-503b, when the terminal moves, the mobile edge host serving the terminal is switched from mobile edge host 1 to mobile edge host 2, and the destination IP address of the terminal packet does not change and is still the virtual IP address IP _ a. The mobile edge host 1 detects that the terminal is switched, and sends a UE switching notification to the mobile edge management system.
505. The mobile edge host 2 performs address translation on the message according to the NAT rule corresponding to the deployed application instance, and translates the destination IP address IP _ a into the real IP address IP2 of the application instance 2 on the mobile edge host 2; and routes the message to application instance 2.
If the application instance 2 and the corresponding NAT rule corresponding to the application a are not configured in advance on the mobile edge host 2, or although there are the application instance 2 and the corresponding NAT rule, it is necessary to migrate the relevant data of the terminal from the application instance 1, such as the process data and the running state generated during the terminal access process stored on the application instance 1, and so on, then a corresponding step needs to be added between the above 503a-503b and 505, and an application instance and a corresponding NAT rule are created on the mobile edge host 2 and the state of the application instance 1 is migrated to the application instance 2 or only the state of the application instance 1 is migrated to the application instance 2 (the application instance 2 and the corresponding NAT rule have been created in advance). The specific steps are shown as a dotted line frame, and specifically comprise the following steps:
504a-504c. the mobile edge management system instructs the mobile edge host 2 to set session level NAT rules that convert the message destination virtual IP address IP _ a of the session to IP 1; the mobile edge host 2 routes the message to application instance 1 on the mobile edge host 1. This step is an optional step in order to maintain the continuity of the session, otherwise the access of the application of the terminal may be delayed or temporarily interrupted. The session level NAT rule may specifically perform session matching and setting in a five-tuple manner (source IP address, destination IP address, source port number, destination port number, protocol type), and the like, and since the application instance 2 on the mobile edge host 2 may have two NAT translation rules at this time, one is the application instance 2 and the corresponding NAT rule deployed in advance in step 504, and the other is the session level NAT rule added in this step 504a in order to maintain the continuity of the session, the priority of the session level NAT rule is higher than the application level NAT rule described in step 504, so that the mobile edge host 2 routes the packet to the application instance 1 on the mobile edge host 1 at this time.
504d-504e. create application instance 2 on the mobile edge host 2 and configure the corresponding NAT rule, or application instance 2 synchronizes the state from application instance 1.
504f-504g after the application instance 2 on the mobile edge host 2 completes creation, configures the corresponding NAT rule, and migrates the state of the application instance 1 to the application instance 2, or after the application instance 2 only migrates or synchronizes the state from the application instance 1, the mobile edge management system instructs the mobile edge host 2 to delete the session-level NAT rule created in step 503 c.
And returning to the step 505, the mobile edge host 2 performs address translation on the message according to the application level NAT rule configured in the step 502d or the existing application level NAT rule, translates the destination IP address IP _ a of the subsequent message into the real IP address IP2 of the application instance 2 on the host, and routes the message to the application instance 2, thereby realizing that the terminal accesses the application instance 2 nearby.
The above embodiment is a flow of allocating, by the mobile edge management system, the IP address to the application a as the virtual IP address IP _ a. When the IP address allocated by the mobile edge management system for the application a is an IP address, the procedure is basically the same as the above embodiment, except that at this time, the DNS rule configured by the mobile edge management system to the mobile edge host is a mapping between a domain name of the application and an IP address of an application instance deployed on the mobile edge host, when the terminal initially accesses a network or accesses the application a, the IP address of the accessed application is obtained from the DNS of the mobile edge host through a domain name resolution process, and at this time, the IP address is the IP address IP1 of the application instance 1.
The terminal accesses the application through the IP address IP1 of the application instance 1, and at this time, the application instance 1 is deployed on the mobile edge host 1, so the mobile edge host 1 may not perform IP address conversion or may perform conversion, and only the IP address after conversion is the same as the IP address before conversion, which is IP 1. Also in an optional step of creating session level NAT in step 503c, the NAT rule translates the message destination IP address IP1 to IP1, and the mobile edge host 2 then routes the message to application instance 1 on the mobile edge host 1.
After the terminal completes the access to the application, the mobile edge management system receives a request message for terminating the application, and the request may come from an operation support system of an operator or other systems. The mobile edge management system interacts with the mobile edge host and the adjacent mobile edge host, deletes the NAT rule and the DNS rule configured on the mobile edge host, and deletes the application instance and the related resources. The mobile edge management system and releases the IP address of the application.
The address translation function may be implemented on the data plane on the mobile edge host, through a separate NAT service on the mobile edge host, or in an application on the mobile edge host.
Fig. 6 is a block diagram of a mobile edge host according to an embodiment of the present invention, which can be used to perform the steps performed by the mobile edge host in the above methods, and may include a receiving device 6001, an address translation device 6002 and a routing device 6003, wherein,
a receiving device 6001, configured to receive a message sent by a terminal, where the message carries an IP address of an application that the terminal needs to access, and an application instance of the application is deployed on the mobile edge host, where the application instance has the IP address;
address translation means 6002 for translating the IP address to an IP address of the application instance;
and a routing device 6003, configured to route the packet to a corresponding application instance according to the converted IP address.
Specifically, the receiving device 6001 may be an interface for communicating with other communication devices (e.g., a base station) and a corresponding processing device. The address translation device 6002 may be a module or device with NAT translation functionality, and may be implemented on the data plane on the mobile edge host as shown in fig. 7, or by a separate NAT service on the mobile edge host, or in an application on the mobile edge host. Routing device 6003 may be a program module or a device with routing capabilities.
The receiving device 6001, the address translation device 6002 and the routing device 6003 of the mobile edge host are configured to respectively perform the corresponding steps of the above-mentioned method embodiments.
Referring to fig. 8, an embodiment of the present invention further provides a mobile edge communication system, including a mobile edge host 1 and one or more neighboring mobile edge hosts 2,
the mobile edge host 1 is configured to receive a message sent by a terminal, where the message carries an IP address of an application that the terminal needs to access, and an application instance of the application is deployed on the mobile edge host 1 and has the IP address; the mobile edge host 1 converts the IP address into the IP address of the application example and routes the message to the application example;
and the adjacent mobile edge host 2 is used for receiving the message of the terminal when the terminal is switched to the coverage area, wherein the message carries the IP address, converting the IP address into the IP address of the application instance deployed on the adjacent mobile edge host 2, and routing the message to the application instance of the application deployed on the adjacent mobile edge host 2.
Wherein, the application instance deployed by the mobile edge host 1 and the application instance deployed by the adjacent mobile edge host 2 have different IP addresses.
Optionally, the mobile edge communication system further includes a mobile edge management system, configured to deploy, before the mobile edge host 1 receives the terminal packet, an application instance of the application in advance in the mobile edge host 1; or when the mobile edge host 1 receives the terminal message, requesting the mobile edge host 1 to deploy the application instance of the application.
Optionally, when the terminal is switched to the coverage of the adjacent mobile edge host 2 and the adjacent mobile edge host 2 does not deploy the application instance of the application, the mobile edge management system requests the adjacent mobile edge host 2 to deploy the application instance of the application. Before the deployment of the application instance requesting the deployment is completed, the adjacent mobile edge host 2 routes the message to the application instance of the application deployed on the mobile edge host 1; after the deployment of the application instance requested to be deployed by the neighboring mobile edge host 2 is completed, the neighboring mobile edge host 2 routes the subsequent message to the application instance of the application deployed on the neighboring mobile edge host 2.
Fig. 9 is a hardware diagram of a mobile edge host according to another embodiment of the present invention, where the mobile edge host may include: a processor, a communication interface, and a memory.
The processor 91 may include one or more processing units, which may be a Central Processing Unit (CPU) or a Network Processor (NP), etc.
The communication interface 94 is used for interfacing and information interaction with other communication devices, including receiving and transmitting corresponding messages; the network device 90 may further comprise a memory 93, and the processor 91 may be connected to the memory 93 and the communication interface 94 by a bus. The memory 93 may be used to store software programs that may be executed by the processor 91 to implement the method steps in the embodiments shown in fig. 3a, 3b, 4 and 5. In addition, the memory 93 may also store various service data or user data, including user status data in the above method steps.
Optionally, the network device 90 may also include an output device 95 and an input device 97. An output device 95 and an input device 97 are connected to the processor 91. The output device 95 may be a display for displaying information, a power amplifier device for playing sound, or a printer, and the like, and the output device 95 may further include an output controller for providing output to the display, the power amplifier device, or the printer. The input device 97 may be a device such as a mouse, keyboard, electronic stylus, or touch panel for user input of information, and the input device 97 may also include an output controller for receiving and processing input from devices such as a mouse, keyboard, electronic stylus, or touch panel.
It will be understood by those of ordinary skill in the art that all or part of the steps executed by the processor to implement the above embodiments may be implemented by hardware, or may be implemented by instructions controlling the associated hardware, and the instructions may be stored in a computer-readable storage medium, which may be a read-only memory, a magnetic disk, an optical disk, or the like. In addition, the embodiment of the invention also provides a computer program product and a storage medium storing the computer program. The computer program product comprises program code stored in a computer readable storage medium and loaded by a processor to implement the above-described method.
The above description is only for the purpose of implementing one or more specific embodiments of the present invention, but the scope of the claims is not limited to the above embodiments, and any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.
Claims (21)
1. A message routing method is characterized by comprising the following steps:
a mobile edge host receives a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, an application instance of the application is deployed on the mobile edge host, and the application instance has the IP address;
and the mobile edge host converts the IP address of the application in the terminal message into the IP address of the application example and routes the message to the application example.
2. The method of claim 1, wherein deploying the application instance of the application on the mobile edge host comprises:
before a mobile edge host receives a terminal message, a mobile edge management system deploys an application instance of the application in the mobile edge host in advance; or
When the mobile edge host receives the terminal message, the mobile edge management system requests the mobile edge host to deploy the application instance of the application.
3. The method of claim 1, comprising: when the terminal is switched to the coverage area of the adjacent mobile edge host, the adjacent mobile edge host receives the message of the terminal, the message carries the IP address,
when the adjacent mobile edge host is deployed with the application instance of the application in advance, the adjacent mobile edge host converts the IP address into the IP address of the application instance deployed on the adjacent mobile edge host, and routes the message to the application instance of the application deployed on the adjacent mobile edge host;
wherein the application instance deployed by the mobile edge host and the application instance deployed by the adjacent mobile edge host have different IP addresses.
4. The method of claim 3, comprising: the application instances on the adjacent mobile edge hosts are deployed in advance by a mobile edge management system according to the service distance of the adjacent mobile edge hosts and the terminal.
5. The method of claim 3, comprising: and the application instances on the adjacent mobile edge hosts are detected by the mobile edge management system that the terminal is switched and then are deployed in advance.
6. The method of claim 1, comprising: when the terminal is switched to the coverage area of the adjacent mobile edge host, the adjacent mobile edge host receives the message of the terminal, the message carries the IP address,
when the adjacent mobile edge host does not deploy the application instance of the application in advance, the mobile edge management system requests the adjacent mobile edge host to deploy the application instance of the application, wherein the application instance requested to be deployed at the adjacent mobile edge host and the application instance deployed at the mobile edge host have different IP addresses;
and the adjacent mobile edge host converts the IP address into the IP address of the application instance deployed on the adjacent mobile edge host, and routes the message to the application instance of the application deployed on the adjacent mobile edge host.
7. The method of claim 6, wherein the neighboring mobile edge host routes the message to the application instance of the application deployed on the mobile edge host before the neighboring mobile edge host requests the application instance deployed to be complete; after the deployment of the application instance requesting deployment is completed, the neighboring mobile edge host routes subsequent messages to the application instance of the application deployed on the neighboring mobile edge host.
8. The method according to any one of claims 3 to 7, comprising: the mobile edge host and the adjacent mobile edge host are provided with network address conversion rules, and the rules comprise the mapping relation between the IP address of the application accessed by the terminal and the IP address of the application instance deployed on the mobile edge host serving the terminal or the adjacent mobile edge host; and the mobile edge host and the adjacent mobile edge host carry out address translation according to the network address translation rule.
9. The method according to any one of claims 1 to 7, wherein the IP address of the application that the message carries the terminal to access is a virtual IP address.
10. A mobile edge communications system comprising a mobile edge host and one or more neighboring mobile edge hosts, characterized in that:
the mobile edge host is used for receiving a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, an application instance of the application is deployed on the mobile edge host, and the application instance has the IP address; the mobile edge host converts the IP address into the IP address of the application example and routes the message to the application example;
the adjacent mobile edge host is used for receiving the message of the terminal when the terminal is switched to the coverage area of the terminal, wherein the message carries the IP address, converting the IP address into the IP address of the application instance deployed on the adjacent mobile edge host, and routing the message to the application instance of the application deployed on the adjacent mobile edge host;
wherein the application instance deployed by the mobile edge host and the application instance deployed by the adjacent mobile edge host have different IP addresses.
11. The system of claim 10, wherein the mobile edge communication system further comprises a mobile edge management system,
the application instance is used for deploying the application on the mobile edge host before the mobile edge host receives the terminal message; or
And when the mobile edge host receives the terminal message, requesting the mobile edge host to deploy the application instance of the application.
12. The system of claim 10, wherein the application instances on the neighboring mobile edge hosts are deployed in advance by a mobile edge management system according to a service distance of the neighboring mobile edge hosts from the terminal.
13. The system of claim 10, comprising: and the application instances on the adjacent mobile edge hosts are detected by the mobile edge management system that the terminal is switched and then are deployed in advance.
14. The system of claim 10,
and when the terminal is switched to the coverage area of the adjacent mobile edge host and the adjacent mobile edge host does not deploy the application instance of the application, the mobile edge management system requests the adjacent mobile edge host to deploy the application instance of the application.
15. The system of claim 14,
before the application instance requesting deployment is deployed, the adjacent mobile edge host routes the message to the application instance of the application deployed on the mobile edge host; after the deployment of the application instance requested to be deployed by the adjacent mobile edge host is completed, the adjacent mobile edge host routes the subsequent message to the application instance of the application deployed on the adjacent mobile edge host.
16. The system according to any one of claims 10 to 15, comprising: the mobile edge host and the adjacent mobile edge host are provided with network address conversion rules, and the rules comprise the mapping relation between the IP address of the application accessed by the terminal and the IP address of the application instance deployed on the mobile edge host serving the terminal or the adjacent mobile edge host; and the mobile edge host and the adjacent mobile edge host carry out address translation according to the network address translation rule.
17. The system according to any one of claims 10 to 15, wherein the IP address of the application that the terminal needs to access carried in the message is a virtual IP address.
18. A mobile edge host, comprising:
the mobile edge host is used for receiving a message sent by a terminal, wherein the message carries an IP address of an application which the terminal needs to access, an application instance of the application is deployed on the mobile edge host, and the application instance has the IP address;
address translation means for translating the IP address to an IP address of the application instance;
and the routing device is used for routing the message to the corresponding application example according to the converted IP address.
19. The mobile edge host of claim 18, wherein the application instance on which the application is deployed on the mobile edge host comprises:
before a mobile edge host receives a terminal message, a mobile edge management system deploys an application instance of the application in the mobile edge host in advance; or
And when the mobile edge host receives the terminal message, the mobile edge management system requests the mobile edge host to deploy the application instance of the application.
20. The mobile edge host of claim 18, comprising: the address conversion device converts the IP address of the application accessed by the terminal into the IP address of the application instance according to a network address conversion rule; the rules include a mapping relationship between the IP address of the application accessed by the terminal and the IP address of the application instance deployed on the mobile edge host serving the terminal.
21. The mobile edge host according to any of claims 18 to 20, wherein the IP address of the application that the terminal needs to access is carried in the packet as a virtual IP address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710245998.5A CN108737271B (en) | 2017-04-14 | 2017-04-14 | Message routing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710245998.5A CN108737271B (en) | 2017-04-14 | 2017-04-14 | Message routing method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108737271A CN108737271A (en) | 2018-11-02 |
| CN108737271B true CN108737271B (en) | 2021-06-01 |
Family
ID=63924705
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710245998.5A Active CN108737271B (en) | 2017-04-14 | 2017-04-14 | Message routing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108737271B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111385318B (en) * | 2018-12-27 | 2022-11-08 | 北京数聚鑫云信息技术有限公司 | Method and device for deploying and/or using API (application program interface) service and cloud service network |
| CN111800283B (en) * | 2019-04-08 | 2023-03-14 | 阿里巴巴集团控股有限公司 | Network system, service providing and resource scheduling method, device and storage medium |
| CN112217856B (en) * | 2019-07-11 | 2024-06-18 | 华为技术有限公司 | Address acquisition method, device, equipment and storage medium of application instance |
| CN113839874A (en) * | 2019-08-02 | 2021-12-24 | 华为技术有限公司 | Method and device for obtaining routing table entry |
| CN110597510B (en) | 2019-08-09 | 2021-08-20 | 华为技术有限公司 | Dynamic layout method and device for interface |
| CN111262784B (en) * | 2020-01-13 | 2022-05-17 | 杭州朗和科技有限公司 | Message forwarding method, message forwarding device, storage medium and electronic equipment |
| CN111614657B (en) * | 2020-05-18 | 2021-06-04 | 北京邮电大学 | Mobile edge security service method and system based on mode selection |
| CN113938812A (en) * | 2020-06-29 | 2022-01-14 | 中国移动通信有限公司研究院 | Redirection method, device and storage medium of application service |
| CN112291363B (en) * | 2020-11-06 | 2023-09-08 | 腾讯科技（深圳）有限公司 | Method, apparatus, electronic device, and computer-readable storage medium for wireless communication |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102821000A (en) * | 2012-09-14 | 2012-12-12 | 乐视网信息技术（北京）股份有限公司 | Method for improving usability of PaaS platform |
| CN104169881A (en) * | 2012-01-18 | 2014-11-26 | Dh2I公司 | Systems and methods for server cluster application virtualization |
| CN104468625A (en) * | 2014-12-26 | 2015-03-25 | 浙江宇视科技有限公司 | Dialing tunnel broker device and method for NAT traversal by means of dialing tunnel |
| CN104486217A (en) * | 2014-12-08 | 2015-04-01 | 杭州华三通信技术有限公司 | Cross network message transmitting method and equipment |
| CN104811328A (en) * | 2014-01-27 | 2015-07-29 | 杭州华三通信技术有限公司 | Virtual network resource management method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120110207A1 (en) * | 2010-11-01 | 2012-05-03 | International Business Machines Corporation | Embedding zone identifiers in ip addresses |
-
2017
- 2017-04-14 CN CN201710245998.5A patent/CN108737271B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104169881A (en) * | 2012-01-18 | 2014-11-26 | Dh2I公司 | Systems and methods for server cluster application virtualization |
| CN102821000A (en) * | 2012-09-14 | 2012-12-12 | 乐视网信息技术（北京）股份有限公司 | Method for improving usability of PaaS platform |
| CN104811328A (en) * | 2014-01-27 | 2015-07-29 | 杭州华三通信技术有限公司 | Virtual network resource management method and device |
| CN104486217A (en) * | 2014-12-08 | 2015-04-01 | 杭州华三通信技术有限公司 | Cross network message transmitting method and equipment |
| CN104468625A (en) * | 2014-12-26 | 2015-03-25 | 浙江宇视科技有限公司 | Dialing tunnel broker device and method for NAT traversal by means of dialing tunnel |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108737271A (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108737271B (en) | Message routing method, device and system | |
| CN111385369B (en) | Domain name server distribution method and device | |
| US20220377045A1 (en) | Network virtualization of containers in computing systems | |
| EP3316532B1 (en) | Computer device, system and method for implementing load balancing | |
| US10887276B1 (en) | DNS-based endpoint discovery of resources in cloud edge locations embedded in telecommunications networks | |
| US9749145B2 (en) | Interoperability for distributed overlay virtual environment | |
| US20200323029A1 (en) | Session Processing Method and Apparatus | |
| US11095534B1 (en) | API-based endpoint discovery of resources in cloud edge locations embedded in telecommunications networks | |
| WO2017045471A1 (en) | Method and apparatus for acquiring service chain information in cloud computing system | |
| CN108347493B (en) | Hybrid cloud management method and device and computing equipment | |
| CN111212134A (en) | Request message processing method and device, edge computing system and electronic equipment | |
| JP7427082B2 (en) | Service offloading methods, devices, systems, electronic devices, and computer programs | |
| JP5579778B2 (en) | Data transmission / reception path control apparatus and method | |
| US11381543B2 (en) | Mitigating network/hardware address explosion in network devices | |
| CN112202673B (en) | Configuration method and device | |
| CN111345008B (en) | Mobile edge host service notification method and device | |
| WO2016169218A1 (en) | Gateway virtualization method and system, and computer storage medium | |
| JP6999931B2 (en) | Communication method, communication system, MEC server, DNS server, and traffic guidance router | |
| US11743325B1 (en) | Centralized load balancing of resources in cloud edge locations embedded in telecommunications networks | |
| US10608942B1 (en) | Reducing routes based on network traffic utilization | |
| CN111615128A (en) | Multi-access edge computing method, platform and system | |
| CN109067573B (en) | Traffic scheduling method and device | |
| CN114553771A (en) | Method for loading virtual router and related equipment | |
| CN112398896B (en) | Apparatus, method, device and computer readable storage medium for providing service | |
| CN113556410B (en) | Domain name server distribution method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |