CN113542386B - Service processing method and related equipment - Google Patents
Service processing method and related equipment Download PDFInfo
- Publication number
- CN113542386B CN113542386B CN202110779893.4A CN202110779893A CN113542386B CN 113542386 B CN113542386 B CN 113542386B CN 202110779893 A CN202110779893 A CN 202110779893A CN 113542386 B CN113542386 B CN 113542386B
- Authority
- CN
- China
- Prior art keywords
- service
- address
- service scheduling
- user plane
- scheduling request
- 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/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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
Abstract
The embodiment of the application discloses a service processing method and related equipment, which comprise the following steps: the user plane functional entity sends a notification message to the agent equipment, wherein the notification message comprises a first Internet Protocol (IP) address of the service scheduler, and the notification message is used for indicating the agent equipment to create a distribution rule; receiving a service scheduling request sent by terminal equipment, wherein the service scheduling request carries a first IP address; sending a service scheduling request to the agent equipment according to the shunting rule, wherein the service scheduling request is used for indicating the agent equipment to acquire a service scheduling response of the service scheduler, and the service scheduling response comprises a second IP address of the service server selected by the service scheduler; receiving a service scheduling response sent by the agent equipment; and sending a service scheduling response to the terminal equipment, wherein the second IP address is used for indicating the terminal equipment to establish communication connection with the service server. By adopting the embodiment of the application, the time delay of service access is reduced, and the management and control of the service background system on the service server are ensured.
Description
The present application is a divisional application of a chinese patent application with an application number of 201910635358.4, and an application name of "a service processing method and related equipment", which is filed on 15.07/15.2019, and the entire contents of the present application are incorporated by reference in the present application.
Technical Field
The present application relates to the field of communications technologies, and in particular, to a service processing method and a related device.
Background
The European Telecommunications Standardization Institute (ETSI) Mobile Edge Computing (MEC) architecture is mainly used for services (e.g., intra-enterprise applications) running within a local private network, and it does not have the capability of implementing cloud-side collaboration. The processing logic of the internet service is more complex. It is often necessary to introduce an access stratum in the data center at a hub location to schedule servers that handle specific service requests. The internet service deployed based on the ETSI MEC architecture cannot interact with the access layer function in the external data center, so that the whole service logic is damaged, and the service front end needs to be reconstructed. In addition, since the ETSI MEC architecture establishes a private closed service management system, the internet service background system cannot effectively manage and control the service server deployed on the ETSI MEC architecture.
Disclosure of Invention
The embodiment of the application provides a service processing method and related equipment. The time delay of service access can be reduced, and the management and control of a service background system on a service server are ensured.
In a first aspect, an embodiment of the present application provides a service processing method, including:
a user plane functional entity sends a notification message to proxy equipment, wherein the notification message comprises a first Internet Protocol (IP) address of a service scheduler, the notification message is used for indicating the proxy equipment to create a distribution rule, and the distribution rule is used for allowing the user plane functional entity to distribute a service scheduling request with a destination address as the first IP address to the proxy equipment;
the user plane functional entity receives the shunting rule sent by the agent equipment;
the user plane functional entity receives the service scheduling request sent by the terminal equipment, wherein the service scheduling request carries the first IP address;
the user plane functional entity sends the service scheduling request to the proxy equipment according to the flow distribution rule, wherein the service scheduling request is used for indicating the proxy equipment to obtain a service scheduling response of the service scheduler, and the service scheduling response comprises a second IP address of the service server selected by the service scheduler;
the user plane functional entity receives the service scheduling response sent by the proxy equipment;
and the user plane functional entity sends the service scheduling response to the terminal equipment, and the second IP address is used for indicating the terminal equipment to establish communication connection with the service server.
Before the user plane functional entity sends the notification message to the proxy device, the method further includes:
the user plane functional entity receives a Domain Name System (DNS) request sent by terminal equipment;
the user plane functional entity sends the DNS request to the operator server;
and the user plane functional entity receives a DNS response sent by the operator server, wherein the DNS response comprises the first IP address.
Wherein the DNS response further comprises a domain name of the traffic dispatcher; the sending of the notification message to the proxy device by the user plane functional entity includes:
the user plane functional entity determines whether the domain name of the service scheduler included in the DNS response is the same as the domain name of the service scheduler configured in advance;
and if the information is the same as the information, the user plane functional entity sends the notification message to the proxy equipment.
After the user plane function entity receives the service scheduling response sent by the proxy device, the method further includes:
the user plane functional entity receives a deletion notification sent by the agent equipment;
and the user plane functional entity deletes the shunting rule.
In a second aspect, an embodiment of the present application provides a service processing method, including:
the method comprises the steps that agent equipment receives a notification message sent by a user plane functional entity, wherein the notification message comprises a first IP address of a service dispatcher;
the proxy equipment sends a distribution rule to the user plane functional entity, wherein the distribution rule is used for allowing the user plane functional entity to distribute the service scheduling request with the destination address as the first IP address to the proxy equipment;
the proxy equipment receives the service scheduling request, wherein the service scheduling request carries the first IP address;
the proxy equipment sends the service scheduling request to the service scheduler;
the proxy equipment receives a service scheduling response sent by the service scheduler, wherein the service scheduling response comprises a second IP address of the service server selected by the service scheduler;
and the proxy equipment sends the service scheduling response to the user plane functional entity, wherein the service scheduling response is used for the user plane functional entity to inform the terminal equipment of establishing communication connection with the service server.
After the proxy device sends the service scheduling response to the user plane functional entity, the method further includes:
and the agent equipment sends a deletion notification to the user plane functional entity, wherein the deletion notification is used for deleting the shunting rule by the user plane functional entity.
In a third aspect, an embodiment of the present application provides a service processing method, including:
a terminal device sends a service scheduling request to a user plane functional entity, wherein the service scheduling request is sent by the user plane functional entity after sending a notification message to a proxy device and receiving a flow distribution rule created by the proxy device, the notification message includes a first IP address of a service scheduler, the flow distribution rule is used for allowing the user plane functional entity to distribute the service scheduling request with a destination address of the first IP address to the proxy device, and the service scheduling request is used for indicating the user plane functional entity to obtain a service scheduling response of the service scheduler through the proxy device, wherein the service scheduling request carries the first IP address, and the service scheduling response includes a second IP address of a service server selected by the service scheduler;
the terminal equipment receives the service scheduling response sent by the user plane functional entity;
and the terminal equipment establishes communication connection with the service server according to the second IP address.
Before the terminal device sends a service scheduling request to the user plane functional entity, the method further includes:
and the terminal equipment receives a DNS response sent by the user plane function entity, wherein the DNS response comprises the first IP address.
In a fourth aspect, an embodiment of the present application provides a user plane function entity, including:
a sending module, configured to send a notification message to a proxy device, where the notification message includes a first internet protocol IP address of a service scheduler, and the notification message is used to instruct the proxy device to create a offloading rule, where the offloading rule is used to allow the user plane functional entity to offload a service scheduling request whose destination address is the first IP address to the proxy device;
a receiving module, configured to receive the offloading rule sent by the proxy device;
the receiving module is further configured to receive the service scheduling request sent by the terminal device, where the service scheduling request carries the first IP address;
the sending module is further configured to send the service scheduling request to the proxy device according to the offloading rule, where the service scheduling request is used to instruct the proxy device to obtain a service scheduling response of the service scheduler, and the service scheduling response includes a second IP address of the service server selected by the service scheduler;
the receiving module is further configured to receive the service scheduling response sent by the proxy device;
the sending module is further configured to send the service scheduling response to the terminal device, and the second IP address is used to instruct the terminal device to establish a communication connection with the service server.
The receiving module is further configured to receive a domain name system DNS request sent by the terminal device;
the sending module is further configured to send the DNS request to the operator server;
the receiving module is further configured to receive a DNS response sent by the operator server, where the DNS response includes the first IP address.
Wherein the DNS response further comprises a domain name of the traffic dispatcher; the user plane functional entity further comprises:
a processing module, configured to determine whether the domain name of the service scheduler included in the DNS response is the same as a preconfigured domain name of the service scheduler; and if the information is the same, sending the notification message to the proxy equipment.
The receiving module is further configured to receive a deletion notification sent by the proxy device; the processing module is further configured to delete the splitting rule.
In a fifth aspect, an embodiment of the present application provides a proxy device, including:
a receiving module, configured to receive a notification message sent by a user plane functional entity, where the notification message includes a first IP address of a service scheduler;
a sending module, configured to send a offloading rule to the user plane functional entity, where the offloading rule is used to allow the user plane functional entity to offload a service scheduling request with a destination address of the first IP address to the proxy device;
the receiving module is further configured to receive the service scheduling request, where the service scheduling request carries the first IP address;
the sending module is configured to send the service scheduling request to the service scheduler;
the receiving module is configured to receive a service scheduling response sent by the service scheduler, where the service scheduling response includes a second IP address of the service server selected by the service scheduler;
the sending module is further configured to send the service scheduling response to the user plane functional entity, where the service scheduling response is used for the user plane functional entity to notify the terminal device to establish a communication connection with the service server.
The sending module is further configured to send a deletion notification to the user plane function entity, where the deletion notification is used for the user plane function entity to delete the offloading rule.
In a sixth aspect, an embodiment of the present application provides a terminal device, including:
a sending module, configured to send a service scheduling request to a user plane functional entity, where the service scheduling request is sent by the user plane functional entity after sending a notification message to an agent device and receiving a splitting rule created by the agent device, where the notification message includes a first IP address of a service scheduler, the splitting rule is used to allow the user plane functional entity to split a service scheduling request with a destination address of the first IP address to the agent device, and the service scheduling request is used to instruct the user plane functional entity to obtain a service scheduling response of the service scheduler through the agent device, where the service scheduling request carries the first IP address, and the service scheduling response includes a second IP address of a service server selected by the service scheduler;
a receiving module, configured to receive the service scheduling response sent by the user plane functional entity;
and the processing module is used for establishing communication connection with the service server according to the second IP address.
The receiving module is configured to receive a DNS response sent by the user plane function entity, where the DNS response includes the first IP address.
By implementing the embodiment of the application, the user plane functional entity sends a notification message to the agent device, wherein the notification message comprises a first Internet Protocol (IP) address of the service scheduler, and the notification message is used for indicating the agent device to create the distribution rule; receiving a service scheduling request sent by terminal equipment, wherein the service scheduling request carries a first IP address; sending a service scheduling request to the agent equipment according to the shunting rule, wherein the service scheduling request is used for indicating the agent equipment to acquire a service scheduling response of the service scheduler, and the service scheduling response comprises a second IP address of the service server selected by the service scheduler; receiving a service scheduling response sent by the agent equipment; and sending a service scheduling response to the terminal equipment, wherein the second IP address is used for indicating the terminal equipment to establish communication connection with the service server. The method and the system can reduce the time delay of service access and ensure the management and control of a service background system on the service server.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic architecture diagram of an ETSI MEC system according to an embodiment of the present disclosure;
fig. 2 is a schematic architecture diagram of a service processing system according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a service processing method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of another service processing method provided in the embodiment of the present application;
fig. 5 is a schematic structural diagram of a user plane functional entity according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a proxy device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of another user plane functional entity proposed in the embodiment of the present application;
fig. 9 is a schematic structural diagram of another proxy device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of another terminal device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As shown in fig. 1, fig. 1 is a schematic structural diagram of an ETSI MEC system according to an embodiment of the present disclosure. The ETSI MEC System defines an Edge computing platform architecture for a Mobile network, and includes three parts, namely, mobile Edge Host (Mobile Edge Host), mobile Edge Host Management (Mobile Edge Host Level Management), and Mobile Edge System Management (Mobile Edge System Level Management).
The Mobile Edge host includes entities of a Mobile Edge Platform (Mobile Edge Platform) and a bottom Virtualization infrastructure (Virtualization infrastructure), and provides computing, storage and network resources for various Mobile Edge applications. The virtual infrastructure provides computing, storage, and network resources for each upper mobile edge application. The mobile edge platform runs various functions needed by mobile edge applications on the mobile edge host, and can provide and use various mobile edge services. Mobile Edge Applications (Mobile Edge Applications) are deployed in instantiated form on a Mobile Edge host with the capability to provide or use Mobile Edge services (Mobile Edge services). The mobile edge application can call the mobile edge service through subscription to acquire the open capability of the underlying network, such as wireless network information, user location information, network bandwidth management and other functions.
Mobile edge host management is a management component that performs specific function management of a particular mobile edge platform, mobile edge host, and mobile edge applications running on it. Mobile edge system management systematically manages a global view of the entire mobile edge system by maintenance. In terms of mobile edge system management, ETSI introduces a mobile edge orchestrator as a core component to globally manage the entire system. And the ETSI defines Application Rules and Requirements (Application Rules and Requirements), and sets related Rules and Requirements for various mobile edge applications, mainly including required resources, maximum delay/latency, required or useful services, traffic Rules, DNS Rules, mobility support, and the like.
The architecture is mainly used for services (such as internal application of an enterprise) running in a local private network, and the architecture does not have the capability of realizing cloud-edge collaboration. The processing logic of internet services is relatively complex. It is often necessary to introduce an access stratum in a data center at a hub location to schedule servers handling specific service requests. The internet service deployed based on the ETSI MEC architecture cannot interact with the access layer function in the external data center, so that the overall service logic is damaged and the service front end needs to be reconstructed. In addition, since the ETSI MEC architecture establishes a private closed service management system, the internet service background system cannot effectively manage and control the service server deployed on the ETSI MEC architecture. In order to solve the above technical problem, embodiments of the present application provide the following solutions.
As shown in fig. 2, fig. 2 is a schematic diagram of an architecture of a service processing system according to an embodiment of the present application. The service processing system comprises terminal equipment, a User Plane Function (UPF), proxy equipment, a service server and a service scheduler. The UPF may be a 5G UPF, and is deployed inside a 5G network and is responsible for forwarding between a user quantity traffic and an edge data center. The proxy equipment and the service server are deployed in the edge data center, wherein the proxy equipment can transparently proxy, and the proxy equipment can acquire the data packet detection information from the 5G UPF, configure the data forwarding rule on the 5G UPF, and forward the service scheduling request of the terminal equipment to the service scheduler. The service server is responsible for processing specific service requests. The service scheduler is deployed in a data center at the network center and is responsible for selecting a specific service server according to the position of the terminal equipment in the network.
The service processing system can be applied to internet services such as cloud games, videos and internet of vehicles. The access layer function of the internet service and the service processing server can be deployed in an edge data center to realize delivery to a user of the terminal equipment. By utilizing the low time delay characteristic of the edge data center, the user experience can be improved, and the management and control of the service background system on the edge service center can be ensured.
As shown in fig. 3, fig. 3 is a schematic flowchart of a service processing method according to an embodiment of the present application. The method comprises the following steps:
s301, the user plane functional entity sends a notification message to the proxy device, where the notification message includes a first Internet Protocol (IP) address of the service scheduler.
In a specific implementation, the terminal device may send a Domain Name System (DNS) request to the user plane functional entity, and after receiving the DNS request, the user plane functional entity sends the DNS request to the operator server through the core network, where the DNS request includes a Domain Name corresponding to the service scheduler. And after receiving the DNS request, the operator server returns a DNS response to the user plane functional entity through the core network, wherein the DNS response comprises the first IP address of the service dispatcher. The core network may be a fifth Generation mobile communication technology (5-Generation, 5G) core network.
Optionally, the user plane functional entity may pre-configure a domain name of the service scheduler, and after receiving the DNS response, the user plane functional entity analyzes the DNS response, obtains the domain name in the DNS response, and determines whether the domain name of the service scheduler included in the DNS response is the same as the domain name of the pre-configured service scheduler; and if the information is the same as the information, the user plane functional entity sends the notification message to the proxy equipment. If not, the step is terminated.
And S302, the agent device creates a distribution rule according to the first IP address and sends the distribution rule to the user plane functional entity, and the user plane functional entity stores the distribution rule after receiving the distribution rule. The distribution rule is used for allowing the user plane functional entity to distribute the service scheduling request with the destination address as the first IP address to the proxy equipment.
S303, the terminal equipment sends a service scheduling request to the user plane functional entity, wherein the service scheduling request carries the first IP address.
In a specific implementation, after receiving the DNS response, the user plane functional entity may send the DNS response to the terminal device, where the DNS response includes the first IP address of the service scheduler. And the terminal equipment sends a service scheduling request according to the first IP address. The destination address of the service scheduling request is the first IP address of the service scheduler, the source address is the address of the terminal device, and the source port is the port of the terminal device.
S304, the user plane functional entity sends the service scheduling request to the agent device according to the shunting rule.
S305, the agent equipment sends the service scheduling request to the service scheduler according to the first IP address carried by the service scheduling request.
In specific implementation, after the proxy device receives a service scheduling request, a source address and a source port in the service scheduling request are modified into a global address of an edge data center and a unique port distributed inside the proxy device. And the proxy equipment sends the service scheduling request with the source address and the source port modified to the service scheduler through an external network interface of the edge data center.
S306, the service scheduler sends a service scheduling response to the proxy equipment, wherein the service scheduling response comprises the second IP address of the service server selected by the service scheduler.
In a specific implementation, after receiving a service scheduling request sent by an agent device, a service scheduler analyzes a source address carried by the service scheduling request according to a pre-configured IP address library, and determines that the service scheduling request is from a specific edge data center, so that the service scheduler selects a service server from the edge data center and writes an IP address of the service server into a service scheduling response. Finally, the service scheduler sends a service scheduling response to the proxy device, the service scheduling response including the second IP address of the selected service server. The service server may be a video server.
S307, the agent equipment sends a service scheduling response to the user plane functional entity.
In the concrete implementation, after receiving the service scheduling response, the proxy server modifies the destination address and the destination port of the service scheduling request into the IP address of the terminal device and the original port allocated by the terminal device respectively. And then transmits a service scheduling response to the terminal device. Wherein the service scheduling response includes the IP address of the terminal device and the original port of the terminal device.
Optionally, the agent device may send a deletion notification to the user plane functional entity, and the user plane functional entity deletes the stored offloading rule after receiving the deletion notification.
S308, the user plane functional entity sends service scheduling response to the terminal equipment according to the modified destination address and the modified destination port.
S309, the terminal device establishes communication connection with the service server according to the second IP address.
In specific implementation, after receiving the service scheduling response, the terminal device acquires a second IP address in the service scheduling response, and initiates communication connection to a service server in the edge data center according to the second IP address to complete file downloading.
As shown in fig. 4, fig. 4 is a schematic flow chart of another service processing method provided in the embodiment of the present application. The method comprises the following steps:
s401, the terminal device sends a DNS request to the user plane functional entity. The DNS request comprises a domain name corresponding to the service dispatcher.
S402, after receiving the DNS request, the user plane functional entity sends the DNS request to an operator server through a core network.
And S403, after receiving the DNS request, the operator server sends a DNS response to the user plane functional entity through the core network. The DNS response includes the first IP address of the traffic dispatcher.
S404, after the user plane functional entity receives the DNS response, the DNS response is analyzed, and the domain name in the DNS response is obtained. Determining whether the domain name of the service scheduler included in the DNS response is the same as a domain name of a pre-configured service scheduler; if so, S405 is executed. If not, the step is terminated.
S405, the user plane functional entity sends a notification message to the agent device, wherein the notification message comprises the first IP address of the service dispatcher.
S406, the user plane functional entity sends a DNS response to the terminal device, where the DNS response includes the first IP address.
S406, the agent device creates a distribution rule according to the first IP address and sends the distribution rule to the user plane functional entity, and the user plane functional entity stores the distribution rule after receiving the distribution rule. The distribution rule is used for allowing the user plane functional entity to distribute the service scheduling request with the destination address as the first IP address to the proxy equipment.
S408, the terminal device sends a service scheduling request to the user plane functional entity, where the service scheduling request carries the first IP address.
In a specific implementation, after receiving the DNS response, the user plane functional entity may send the DNS response to the terminal device, where the DNS response includes the first IP address of the service scheduler. And the terminal equipment sends a service scheduling request according to the first IP address. The destination address of the service scheduling request is the first IP address of the service scheduler, the source address is the address of the terminal device, and the source port is the port of the terminal device.
S409, the user plane functional entity sends the service scheduling request to the agent device according to the distribution rule.
And S410, the agent equipment sends the service scheduling request to the service scheduler according to the first IP address carried by the service scheduling request.
In the specific implementation, after the proxy device receives the service scheduling request, the source address and the source port in the service scheduling request are modified into the global address of the edge data center and the unique port allocated inside the proxy device. And the proxy equipment sends the service scheduling request with the source address and the source port modified to the service scheduler through an external network interface of the edge data center.
S411, the service scheduler sends a service scheduling response to the proxy device, where the service scheduling response includes the second IP address of the service server selected by the service scheduler.
In a specific implementation, after receiving a service scheduling request sent by an agent device, a service scheduler analyzes a source address carried by the service scheduling request according to a pre-configured IP address library, and determines that the service scheduling request is from a specific edge data center, so that the service scheduler selects a service server from the edge data center and writes an IP address of the service server into a service scheduling response. Finally, the service scheduler sends a service scheduling response to the proxy device, the service scheduling response including the second IP address of the selected service server. The service server may be a video server.
S412, the proxy device sends a service scheduling response to the user plane function entity.
In the concrete implementation, after receiving the service scheduling response, the proxy server modifies the destination address and the destination port of the service scheduling request into the IP address of the terminal equipment and the original port allocated by the terminal equipment. And then sending a service scheduling response to the terminal equipment, wherein the service scheduling response comprises the IP address of the terminal equipment and the original port allocated by the terminal equipment.
S413, the user plane functional entity sends a service scheduling response to the terminal device according to the destination address and the destination port. The traffic scheduling response includes the second IP address.
S414, the agent device may send a deletion notification to the user plane functional entity, and after receiving the deletion notification, the user plane functional entity deletes the stored offloading rule.
S415, the terminal device may send a file download request to the user plane function entity, where the file download request includes the second IP address.
And S416, after receiving the file downloading request, the user plane functional entity sends the file downloading request to the service scheduler.
S417, the service dispatcher sends the download file to the user plane functional entity.
And S418, the user plane functional entity sends the download file to the terminal equipment.
The method of the embodiments of the present application is set forth above in detail and the apparatus of the embodiments of the present application is provided below.
As shown in fig. 5, fig. 5 is a schematic structural diagram of a user plane functional entity according to an embodiment of the present application. The user plane functional entity includes a sending module 501, a receiving module 502 and a processing module 503, wherein:
a sending module 501, configured to send a notification message to a proxy device, where the notification message includes a first internet protocol IP address of a service scheduler, and the notification message is used to instruct the proxy device to create a offloading rule, where the offloading rule is used to allow the user plane functional entity to offload a service scheduling request whose destination address is the first IP address to the proxy device;
a receiving module 502, configured to receive the offloading rule sent by the proxy device;
a receiving module 502, configured to receive the service scheduling request sent by a terminal device, where the service scheduling request carries the first IP address;
the sending module 501 is further configured to send the service scheduling request to the proxy device according to the offloading rule, where the service scheduling request is used to instruct the proxy device to obtain a service scheduling response of the service scheduler, and the service scheduling response includes a second IP address of the service server selected by the service scheduler;
a receiving module 502, further configured to receive the service scheduling response sent by the proxy device;
the sending module 501 is further configured to send the service scheduling response to the terminal device, where the second IP address is used to indicate the terminal device to establish a communication connection with the service server.
Optionally, the receiving module 502 is further configured to receive a domain name system DNS request sent by the terminal device;
a sending module 501, configured to send the DNS request to the operator server;
the receiving module 502 is further configured to receive a DNS response sent by the operator server, where the DNS response includes the first IP address.
Optionally, the processing module 503 is configured to determine whether the domain name of the service scheduler included in the DNS response is the same as a domain name of the service scheduler configured in advance; and if the information is the same as the information, sending the notification message to the proxy equipment.
Optionally, the receiving module 502 is further configured to receive a deletion notification sent by the proxy device; the processing module 503 is further configured to delete the splitting rule.
It should be noted that, the implementation of each module may also correspond to the corresponding description of the method embodiment shown in fig. 3 or fig. 4, and execute the method and the function executed by the user plane functional entity in the foregoing embodiment.
As shown in fig. 6, fig. 6 is a schematic structural diagram of a proxy device according to an embodiment of the present application. The proxy device comprises a receiving module 601 and a sending module 602, wherein:
a receiving module 601, configured to receive a notification message sent by a user plane functional entity, where the notification message includes a first IP address of a service scheduler;
a sending module 602, configured to send a offloading rule to the user plane functional entity, where the offloading rule is used to allow the user plane functional entity to offload a service scheduling request with a destination address as the first IP address to the proxy device;
a receiving module 601, configured to receive the service scheduling request, where the service scheduling request carries the first IP address;
a sending module 602, configured to send the service scheduling request to the service scheduler;
a receiving module 601, configured to receive a service scheduling response sent by the service scheduler, where the service scheduling response includes a second IP address of the service server selected by the service scheduler;
the sending module 602 is further configured to send the service scheduling response to the user plane functional entity, where the service scheduling response is used for the user plane functional entity to notify the terminal device to establish a communication connection with the service server.
Optionally, the sending module 602 is further configured to send a deletion notification to the user plane functional entity, where the deletion notification is used for the user plane functional entity to delete the offloading rule.
It should be noted that, the implementation of each module may also correspond to the corresponding description of the method embodiment shown in fig. 3 or fig. 4, and execute the method and the function executed by the proxy device in the foregoing embodiment.
As shown in fig. 7, fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device body includes a sending module 701, a receiving module 702, and a processing module 703, wherein:
a sending module 701, configured to send a service scheduling request to a user plane functional entity, where the service scheduling request is sent by the user plane functional entity to an agent device after sending a notification message to the agent device and receiving a splitting rule created by the agent device, where the notification message includes a first IP address of a service scheduler, the splitting rule is used to allow the user plane functional entity to split a service scheduling request with a destination address of the first IP address to the agent device, and the service scheduling request is used to instruct the user plane functional entity to obtain a service scheduling response of the service scheduler through the agent device, where the service scheduling request carries the first IP address, and the service scheduling response includes a second IP address of a service server selected by the service scheduler;
a receiving module 702, configured to receive the service scheduling response sent by the user plane function entity;
the processing module 703 is configured to establish a communication connection with the service server according to the second IP address.
Optionally, the receiving module 702 is configured to receive a DNS response sent by the user plane function entity, where the DNS response includes the first IP address.
It should be noted that, the implementation of each module may also correspond to the corresponding description of the method embodiment shown in fig. 3 or fig. 4, and execute the method and the function executed by the terminal device in the foregoing embodiment.
Please refer to fig. 8, wherein fig. 8 is a schematic structural diagram of another user plane functional entity according to an embodiment of the present disclosure. As shown in fig. 8, the user plane functional entity may include: at least one processor 801, at least one communication interface 802, at least one memory 803, and at least one communication bus 804.
The processor 801 may be, among other things, a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, transistor logic, a hardware component, or any combination thereof. Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors in combination, a digital signal processor in combination with a microprocessor, and so forth. The communication bus 804 may be a peripheral component interconnect standard PCI bus or an extended industry standard architecture EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus. A communication bus 804 is used to enable communications among the components. In this embodiment, the communication interface 802 of the device in this application is used for performing signaling or data communication with other node devices. The memory 803 may include a volatile memory, such as a nonvolatile dynamic random access memory (NVRAM), a phase change random access memory (PRAM), a Magnetoresistive Random Access Memory (MRAM), and the like, and may further include a non-volatile memory, such as at least one magnetic disk memory device, an electrically erasable programmable read-only memory (EEPROM), a flash memory device, such as a NOR flash memory or a NAND flash memory, a semiconductor device, such as a Solid State Disk (SSD), and the like. The memory 803 may optionally be at least one memory device located remotely from the processor 801 as previously described. A set of program codes may also optionally be stored in the memory 803, and the processor 801 may also optionally execute the program executed in the memory 803.
Sending a notification message to proxy equipment, wherein the notification message comprises a first Internet Protocol (IP) address of a service scheduler, the notification message is used for indicating the proxy equipment to create a distribution rule, and the distribution rule is used for allowing the user plane functional entity to distribute a service scheduling request with a destination address of the first IP address to the proxy equipment;
receiving the shunting rule sent by the agent equipment;
receiving the service scheduling request sent by the terminal equipment, wherein the service scheduling request carries the first IP address;
sending the service scheduling request to the proxy equipment according to the distribution rule, wherein the service scheduling request is used for indicating the proxy equipment to obtain a service scheduling response of the service scheduler, and the service scheduling response comprises a second IP address of the service server selected by the service scheduler;
receiving the service scheduling response sent by the agent equipment;
and sending the service scheduling response to the terminal equipment, wherein the second IP address is used for indicating the terminal equipment to establish communication connection with the service server.
Optionally, the processor 801 is further configured to perform the following operations:
receiving a Domain Name System (DNS) request sent by terminal equipment;
sending the DNS request to the operator server;
and receiving a DNS response sent by the operator server, wherein the DNS response comprises the first IP address.
Optionally, the processor 801 is further configured to perform the following operations:
determining whether the domain name of the service scheduler included in the DNS response is the same as a preconfigured domain name of the service scheduler;
and if the information is the same, sending the notification message to the proxy equipment.
Optionally, the processor 801 is further configured to perform the following operations:
receiving a deletion notification sent by the agent equipment;
and deleting the shunting rules.
Further, the processor may also cooperate with the memory and the communication interface to perform the operations of the user plane functional entity in the embodiments of the above application.
Referring to fig. 9, fig. 9 is a schematic structural diagram of another proxy device according to an embodiment of the present application. As shown, the proxy device may include: at least one processor 901, at least one communication interface 902, at least one memory 903 and at least one communication bus 904.
The processor 901 may be any of the various types of processors mentioned above. The communication bus 904 may be a peripheral component interconnect standard PCI bus or an extended industry standard architecture EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 9, but this does not indicate only one bus or one type of bus. A communication bus 904 is used to enable the connective communication between these components. The communication interface 902 of the device in this embodiment of the present application is used for performing signaling or data communication with other node devices. The memory 903 may be of various types as mentioned earlier. The memory 903 may optionally be at least one storage device located remotely from the processor 901. A set of program codes is stored in the memory 903, and the processor 901 executes the programs executed by the OAM in the memory 903.
Receiving a notification message sent by a user plane functional entity, wherein the notification message comprises a first IP address of a service dispatcher;
sending a distribution rule to the user plane functional entity, where the distribution rule is used to allow the user plane functional entity to distribute the service scheduling request with the destination address as the first IP address to the proxy device;
receiving the service scheduling request, wherein the service scheduling request carries the first IP address;
sending the service scheduling request to the service scheduler;
receiving a service scheduling response sent by the service scheduler, wherein the service scheduling response comprises a second IP address of the service server selected by the service scheduler;
and sending the service scheduling response to the user plane functional entity, wherein the service scheduling response is used for the user plane functional entity to inform the terminal equipment of establishing communication connection with the service server.
Optionally, the processor 901 is further configured to perform the following operations:
and sending a deletion notification to the user plane functional entity, wherein the deletion notification is used for deleting the shunting rule by the user plane functional entity.
Further, the processor may cooperate with the memory and the communication interface to perform the operations of the proxy device in the embodiments of the above application.
Referring to fig. 10, fig. 10 is a schematic structural diagram of another terminal device according to an embodiment of the present disclosure. As shown, the terminal device may include: at least one processor 1001, at least one communication interface 1002, at least one memory 1003 and at least one communication bus 1004.
The processor 1001 may be any of the various types of processors mentioned above. The communication bus 1004 may be a peripheral component interconnect standard PCI bus or an extended industry standard architecture EISA bus or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but this is not intended to represent only one bus or type of bus. A communication bus 1004 is used to enable connective communication between these components. The communication interface 1002 of the device in this embodiment of the present application is used for performing signaling or data communication with other node devices. The memory 1003 may be various types of memories as mentioned earlier. The memory 1003 may optionally be at least one memory device located remotely from the processor 1001. A set of program codes is stored in the memory 1003, and the processor 1001 executes the program executed by the OAM in the memory 1003.
The method comprises the steps that terminal equipment sends a service scheduling request to a user plane functional entity, the service scheduling request is sent after the user plane functional entity sends a notification message to proxy equipment and receives a distribution rule created by the proxy equipment, the notification message comprises a first IP address of a service scheduler, the distribution rule is used for allowing the user plane functional entity to distribute the service scheduling request with a destination address of the first IP address to the proxy equipment, the service scheduling request is used for indicating the user plane functional entity to obtain a service scheduling response of the service scheduler through the proxy equipment, wherein the service scheduling request carries the first IP address, and the service scheduling response comprises a second IP address of a service server selected by the service scheduler;
receiving the service scheduling response sent by the user plane functional entity;
and establishing communication connection with the service server according to the second IP address.
Optionally, the processor 1001 is further configured to perform the following operations:
and receiving a DNS response sent by the user plane function entity, wherein the DNS response comprises the first IP address.
Further, the processor may cooperate with the memory and the communication interface to perform the operations of the terminal device in the embodiments of the above application.
The embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support a user plane function entity, an agent device, or a terminal device to implement the functions involved in any of the foregoing embodiments, for example, to generate or process data and/or information involved in the foregoing method. In one possible design, the system-on-chip may further include a memory for program instructions and data necessary to authenticate the server, operate the business support system, or the terminal device. The chip system may be constituted by a chip, or may include a chip and other discrete devices.
Embodiments of the present application further provide a processor, coupled to a memory, configured to perform any of the methods and functions related to the user plane functional entity, the proxy device, or the terminal device in any of the foregoing embodiments.
Embodiments of the present application further provide a computer program product containing instructions, which when run on a computer, cause the computer to perform any of the methods and functions related to the user plane functional entity, the proxy device, or the terminal device in any of the above embodiments.
The embodiment of the present application further provides an apparatus, configured to execute any method and function related to a user plane functional entity, an agent device, or a terminal device in any of the foregoing embodiments.
In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.
The above-mentioned embodiments further explain the objects, technical solutions and advantages of the present application in detail. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (16)
1. A method for processing a service, comprising:
a user plane functional entity acquires a shunting rule;
when a service scheduling request sent by terminal equipment is received and carries a first IP address of a service scheduler, sending the service scheduling request to agent equipment according to the shunting rule; the proxy equipment is used for modifying a source address and a source port in the received service scheduling request into a global address of an edge data center and a unique port distributed in the proxy equipment, and sending the modified service scheduling request to the service scheduler; the service scheduler is used for determining a specific edge data center according to a source address carried by the modified service scheduling request, and is used for selecting a service server from the edge data center, and the service server has a second IP address;
receiving a service scheduling response sent by the agent equipment, and sending the service scheduling response to the terminal equipment; the service scheduling response comprises a second IP address of one service server of the edge data center selected by the service scheduler, and the second IP address is used for the terminal equipment to establish communication connection with the service server; the agent device and the service server are deployed in the edge data center.
2. The method according to claim 1, wherein the obtaining, by the user plane functional entity, the offloading rule comprises:
the user plane functional entity sends a notification message to the proxy equipment, wherein the notification message comprises the first IP address;
and receiving the shunting rule created by the proxy equipment based on the first IP address.
3. The method of claim 2, wherein before the user plane function entity sends the notification message to the proxy device, the method further comprises:
receiving a Domain Name System (DNS) request sent by the terminal equipment;
sending the DNS request to an operator server;
receiving a DNS response sent by the operator server; the DNS response includes the first IP address.
4. The method of claim 3, wherein the DNS response further comprises a domain name of the traffic scheduler; the notification message is sent after determining that the domain name of the service scheduler is the same as the pre-configured domain name of the service scheduler.
5. A method for processing a service, comprising:
the proxy equipment acquires a service scheduling request sent by a user plane functional entity; the service scheduling request is sent by the user plane functional entity according to a shunting rule when the service scheduling request sent by the terminal equipment is received and carries a first IP address of a service scheduler; the destination address of the service scheduling request is a first IP address of a service scheduler, the source port is a port of the terminal equipment, and the source address is the address of the terminal equipment;
modifying a source address in the service scheduling request into a global address of an edge data center, and modifying a source port in the service scheduling request into a unique port distributed inside the proxy equipment;
sending the service scheduling request with the source address and the source port modified to a service scheduler, and receiving a service scheduling response returned by the service scheduler; the service scheduler is used for determining a specific edge data center according to the modified source address and the source address carried by the service scheduling request after the source port is modified, and is used for selecting a service server from the edge data center, wherein the service server has a second IP address; the service scheduling response comprises a second IP address of one service server of the edge data center selected by the service scheduler; the agent equipment and the service server are deployed in the edge data center;
sending the service scheduling response to a user plane functional entity; and after the user plane functional entity sends the service scheduling response to the terminal equipment, the second IP address is used for establishing communication connection between the terminal equipment and the service server.
6. The method of claim 5, wherein the service scheduling response is sent to the user plane function entity after modifying the source address and the destination address of the service scheduling request after the source port are modified into the IP address of the terminal device, and modifying the destination port of the service scheduling request after the source address and the source port are modified into the original port allocated to the terminal device.
7. The method of claim 5, wherein sending the traffic scheduling request after modifying the source address and the source port to a traffic scheduler comprises:
and sending the service scheduling request with the source address and the source port modified to the service scheduler through an external network interface of the edge data center.
8. The method according to claim 5, wherein the service scheduling response sent by the proxy device to the user plane function entity further includes the IP address of the terminal device and the original port allocated by the terminal device.
9. The method of claim 5, wherein the service scheduling request is sent by the user plane function entity according to a offloading rule.
10. The method of claim 9, wherein the breakout rules are created for the proxy device based on a notification message; the notification message is sent to the agent device by the user plane functional entity; the notification message includes a first IP address of the traffic scheduler.
11. The method of claim 10, further comprising:
sending a deletion notification to the user plane functional entity; and the deletion notification is used for the user plane functional entity to delete the shunting rule.
12. A method for processing a service, comprising:
the service scheduler acquires a modified source address and a service scheduling request sent by the proxy equipment after the source port is modified; the modified source address is the global address of the edge data center; the service scheduling request after the source address and the source port are modified is obtained by modifying the source address and the source port in the service scheduling request by the proxy equipment; the service scheduling request is sent to the proxy equipment according to a shunting rule when a user plane functional entity receives the service scheduling request sent by the terminal equipment and the service scheduling request carries a first IP address of a service scheduler;
analyzing the global address of the edge data center in the service scheduling request after the source address and the source port are modified according to a pre-configured IP address library, and determining that the service scheduling request after the source address and the source port are modified comes from the edge data center;
selecting a service server from the edge data center, and writing a second IP address of the service server into a service scheduling response;
sending a service scheduling response including the second IP address to the proxy equipment; when the proxy equipment sends the service scheduling response comprising the second IP address to a user plane functional entity, and the user plane functional entity sends the service scheduling response comprising the second IP address to terminal equipment, the second IP address is used for establishing communication connection between the terminal equipment and the service server; the agent device and the service server are deployed in the edge data center.
13. The method of claim 12, wherein the service scheduling request is obtained by modifying a source address and a source port of a service scheduling request, where the source address is an address of a terminal device and the source port is a port of the terminal device, by a proxy device; the source address is the address of the terminal equipment, and the service scheduling request of which the source port is the port of the terminal equipment comprises a first IP address of the service scheduler; the service scheduling request of which the source address is the address of the terminal equipment and the source port is the port of the terminal equipment is sent to the proxy equipment by the user plane functional entity according to the shunting rule; the distribution rule is created by the agent device based on the notification message; the notification message is sent to the agent device by the user plane functional entity; the notification message includes a first IP address of the traffic scheduler.
14. A user plane functional entity, characterized in that the user plane functional entity comprises: a processor, a communication interface, and a memory;
the processor is connected to the memory and the communication interface, wherein the communication interface is configured to provide a network communication function, the memory is configured to store program code, and the processor is configured to call the program code to cause the user plane function entity to perform the method of any one of claims 1 to 4.
15. A proxy device, characterized in that the proxy device comprises: a processor, a communication interface, and a memory;
the processor is coupled to the memory and the communication interface, wherein the communication interface is configured to provide a network communication function, the memory is configured to store program code, and the processor is configured to invoke the program code to cause the proxy device to perform the method of any of claims 5-11.
16. A traffic scheduler, characterized in that the traffic scheduler comprises: a processor, a communication interface, and a memory;
the processor is connected to the memory and the communication interface, wherein the communication interface is configured to provide a network communication function, the memory is configured to store program code, and the processor is configured to call the program code to cause the service scheduler to execute the method of any one of claims 12-13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110779893.4A CN113542386B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910635358.4A CN110896411B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
| CN202110779893.4A CN113542386B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910635358.4A Division CN110896411B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113542386A CN113542386A (en) | 2021-10-22 |
| CN113542386B true CN113542386B (en) | 2023-01-06 |
Family
ID=69785541
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110779893.4A Active CN113542386B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
| CN201910635358.4A Active CN110896411B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910635358.4A Active CN110896411B (en) | 2019-07-15 | 2019-07-15 | Service processing method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN113542386B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115118786B (en) * | 2021-03-22 | 2024-03-19 | 中国电信股份有限公司 | Edge service scheduling method, device and system and storage medium |
| CN113242319A (en) * | 2021-07-09 | 2021-08-10 | 军事科学院系统工程研究院网络信息研究所 | Cloud edge cooperative work method and system based on video cloud service architecture |
| CN114285900B (en) * | 2021-12-09 | 2023-10-03 | 中国联合网络通信集团有限公司 | Scheduling system, authentication method, scheduling method, device, server and medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109788078A (en) * | 2017-11-13 | 2019-05-21 | 华为技术有限公司 | Application server switching method, equipment and system |
| CN109842639A (en) * | 2017-11-24 | 2019-06-04 | 华为技术有限公司 | Realize method, equipment and the system of business continuance in handoff procedure |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010142349A1 (en) * | 2009-06-12 | 2010-12-16 | Telefonaktiebolaget L M Ericsson (Publ) | Method and server entity for forwarding a message containing a host name or domain name in an internet based communications network |
| CN102437964B (en) * | 2010-11-17 | 2014-07-09 | 华为技术有限公司 | Method and device for issuing business as well as communication system |
| BR112016017555A2 (en) * | 2014-01-29 | 2017-08-08 | Huawei Tech Co Ltd | WIRELESS NETWORK DATA PROCESSING APPLIANCE, AND WIRELESS NETWORK SYSTEM |
| CN105847398A (en) * | 2016-04-25 | 2016-08-10 | 乐视控股（北京）有限公司 | Business scheduling method, scheduling server and business server |
| FR3051307A1 (en) * | 2016-05-10 | 2017-11-17 | Orange | METHOD FOR ACCESSING HOST CONTENT ON A SELECTED SERVER BASED ON THE LOCATION OF THE USER TERMINAL |
| CN106060149A (en) * | 2016-06-24 | 2016-10-26 | 北京交通大学 | Mobile internet mass data analysis and audit technical architecture |
| CN108243456B (en) * | 2016-12-23 | 2022-07-05 | 中国电信股份有限公司 | Policy control method and policy controller |
| CN107105029B (en) * | 2017-04-18 | 2018-03-20 | 北京友普信息技术有限公司 | A kind of CDN dynamic contents accelerated method and system based on Docker technologies |
| WO2018224126A1 (en) * | 2017-06-06 | 2018-12-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for user plane function allocation |
| CN113194157B (en) * | 2017-06-30 | 2022-10-28 | 华为技术有限公司 | Method and device for converting application instance address |
| CN107920366A (en) * | 2017-07-21 | 2018-04-17 | 深圳星耀智能计算技术有限公司 | The method and device that a kind of business to mobile terminal is shunted |
| CN109640319B (en) * | 2019-01-16 | 2021-08-31 | 腾讯科技（深圳）有限公司 | Scheduling method and device based on access information and electronic equipment |
| CN109889586B (en) * | 2019-02-02 | 2021-05-11 | 腾讯科技（深圳）有限公司 | Communication processing method and device, computer readable medium and electronic equipment |
| CN109951880B (en) * | 2019-03-15 | 2021-01-01 | 腾讯科技（深圳）有限公司 | Communication processing method and device, computer readable medium and electronic equipment |
-
2019
- 2019-07-15 CN CN202110779893.4A patent/CN113542386B/en active Active
- 2019-07-15 CN CN201910635358.4A patent/CN110896411B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109788078A (en) * | 2017-11-13 | 2019-05-21 | 华为技术有限公司 | Application server switching method, equipment and system |
| CN109842639A (en) * | 2017-11-24 | 2019-06-04 | 华为技术有限公司 | Realize method, equipment and the system of business continuance in handoff procedure |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113542386A (en) | 2021-10-22 |
| CN110896411B (en) | 2021-07-27 |
| CN110896411A (en) | 2020-03-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10700979B2 (en) | Load balancing for a virtual networking system | |
| CN111385369B (en) | Domain name server distribution method and device | |
| US9628290B2 (en) | Traffic migration acceleration for overlay virtual environments | |
| CN109889586B (en) | Communication processing method and device, computer readable medium and electronic equipment | |
| US9143582B2 (en) | Interoperability for distributed overlay virtual environments | |
| CN113542386B (en) | Service processing method and related equipment | |
| US20110119388A1 (en) | Optimization of Multimedia Service Over an IMS Network | |
| CN111345008B (en) | Mobile edge host service notification method and device | |
| CN115269184A (en) | Function As A Service (FAAS) execution dispatcher | |
| US10230795B2 (en) | Data replication for a virtual networking system | |
| CN109358967B (en) | ME platform APP instantiation migration method and server | |
| CN111177112A (en) | Database blocking method and device based on operation and maintenance management system and electronic equipment | |
| CN111949364A (en) | Deployment method of containerized VNF and related equipment | |
| CN109417501B (en) | Method and equipment for arranging network resources | |
| CN113422804A (en) | Application instance migration method and multi-access edge computing host | |
| CN105589744A (en) | Virtual machine migration method and apparatus | |
| US11627169B2 (en) | Network-based Media Processing (NBMP) workflow management through 5G Framework for Live Uplink Streaming (FLUS) control | |
| US20180248940A1 (en) | Distributed data management | |
| CN115428514A (en) | Sharing geographically focused workloads between adjacent MEC hosts of multiple operators | |
| CN110609656A (en) | Storage management method, electronic device and computer program product | |
| US10231269B2 (en) | Dynamic generation of geographically bound manet IDs | |
| CN114726657A (en) | Method and device for interrupt management and data receiving and sending management and intelligent network card | |
| CN109547552B (en) | API request processing method and device, storage medium and electronic equipment | |
| CN114531320A (en) | Communication method, device, equipment, system and computer readable storage medium | |
| CN114528114A (en) | Data processing method, device and equipment |
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 |