CN112512090A

CN112512090A - Communication processing method and device, computer readable medium and electronic equipment

Info

Publication number: CN112512090A
Application number: CN202011519616.1A
Authority: CN
Inventors: 俞一帆
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-03-15
Filing date: 2019-03-15
Publication date: 2021-03-16
Anticipated expiration: 2039-03-15
Also published as: CN109951880A; CN109951880B; CN112512090B

Abstract

The embodiment of the application provides a communication processing method, a communication processing device, a computer readable medium and electronic equipment. The communication processing method comprises the following steps: acquiring a scheduling request data packet from terminal equipment, wherein the destination address of the scheduling request data packet is the network address of a specified service scheduler; replacing the source address of the scheduling request data packet with a set address to obtain a target data packet; sending the target data packet to a designated service scheduler so that the designated service scheduler returns a scheduling feedback data packet containing the network address of the edge computing device; and receiving the scheduling feedback data packet, replacing the destination address of the scheduling feedback data packet with the network address of the terminal equipment, and then sending the scheduling feedback data packet to the terminal equipment, so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment. According to the technical scheme of the embodiment of the application, the time delay of the terminal equipment for accessing the service can be effectively reduced through the edge computing equipment.

Description

Communication processing method and device, computer readable medium and electronic equipment

The application is a divisional application with application number 201910197452.6, which is filed on 15.03.2019 and named as a communication processing method, device, computer readable medium and electronic equipment.

Technical Field

The present application relates to the field of computer and communication technologies, and in particular, to a communication processing method and apparatus, a computer-readable medium, and an electronic device.

Background

The internet service platform generally needs to rely on a service scheduler disposed in the core data center to respond to the service request of the user, and the service scheduler selects a service server to process the service request of the user. However, the service scheduler of the internet service platform proposed in the related art cannot identify whether the service request of the terminal device is from an area that can be served by an MEC (Mobile Edge Computing) device, and therefore, in order to ensure service availability, the service scheduler can only select a service server located in a core data center to respond to the service request of the user, which results in that the MEC device cannot process the service request of the terminal device in a scheduled manner.

Disclosure of Invention

Embodiments of the present application provide a communication processing method and apparatus, a computer-readable medium, and an electronic device, so that a service scheduler can identify whether a service request of a terminal device can be processed by an edge computing device at least to a certain extent, and further can deliver a service to the terminal device through the edge computing device, thereby effectively reducing a time delay of accessing the service by the terminal device, and reducing bandwidth consumption of a core data center.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.

According to an aspect of an embodiment of the present application, there is provided a communication processing method, including: acquiring a scheduling request data packet from terminal equipment, wherein the destination address of the scheduling request data packet is the network address of a specified service scheduler; replacing the source address of the scheduling request data packet with a set address to obtain a target data packet; sending the target data packet to the designated service scheduler so that the designated service scheduler returns a scheduling feedback data packet containing the network address of the edge computing device; and receiving the scheduling feedback data packet, replacing the destination address of the scheduling feedback data packet with the network address of the terminal equipment, and then sending the scheduling feedback data packet to the terminal equipment, so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment.

According to an aspect of an embodiment of the present application, there is provided a communication processing method, including: receiving a scheduling request data packet sent by terminal equipment; if the destination address of the scheduling request data packet is the network address of the appointed service scheduler, the scheduling request data packet is sent to edge computing equipment, so that the edge computing equipment replaces the source address of the scheduling request data packet with a set address and sends the set address to the appointed service scheduler; receiving a scheduling feedback data packet returned by the edge computing device, wherein the scheduling feedback data packet is generated by the specified service scheduler according to the scheduling request data packet and contains the network address of the edge computing device; and sending the scheduling feedback data packet to the terminal equipment so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment.

According to an aspect of an embodiment of the present application, there is provided a communication processing apparatus including: an obtaining unit, configured to obtain a scheduling request packet from a terminal device, where a destination address of the scheduling request packet is a network address of a specified service scheduler; the first processing unit is used for replacing the source address of the scheduling request data packet with a set address to obtain a target data packet; a sending unit, configured to send the target data packet to the specified service scheduler, so that the specified service scheduler returns a scheduling feedback data packet including a network address of the edge computing device; and the second processing unit is used for receiving the scheduling feedback data packet, replacing the destination address of the scheduling feedback data packet with the network address of the terminal equipment and then sending the destination address of the scheduling feedback data packet to the terminal equipment, so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment.

In some embodiments of the present application, based on the foregoing solution, the communication processing apparatus is disposed in the edge computing device, and the obtaining unit is configured to: receiving a scheduling request data packet from the terminal device, which is forwarded by a offloading device, wherein the scheduling request data packet is forwarded to the edge computing device when the offloading device detects that a destination address of the scheduling request data packet is a network address of the specified service scheduler.

In some embodiments of the present application, based on the foregoing solution, the communication processing apparatus further includes: a receiving unit, configured to receive, before receiving a scheduling request data packet from the terminal device forwarded by a offloading device, Domain Name System (DNS) response information sent by the offloading device, where the DNS response information is generated by a DNS server according to a DNS request sent by the terminal device and is sent to the offloading device; a generating unit, configured to, when domain name information in the DNS response message includes a target domain name, use a network address included in the DNS response message as a network address of the specified service scheduler, and generate a offloading policy according to the network address of the specified service scheduler, where the offloading policy is used to enable the offloading device to forward a scheduling request packet whose destination address matches the network address of the specified service scheduler to the edge computing device; the sending unit is further configured to send the offloading policy to the offloading device.

In some embodiments of the present application, based on the foregoing scheme, the sending unit is further configured to: if the domain name information in the DNS response message does not include the target domain name, sending a notification message to the offloading device, so that the offloading device forwards a scheduling request packet whose destination address matches the network address included in the DNS response message to a target service scheduler, where the network address of the target service scheduler is the network address included in the DNS response message.

In some embodiments of the present application, based on the foregoing solution, the communication processing apparatus further includes: a third processing unit, configured to receive a service access request from the terminal device forwarded by the offloading device, respond to the service access request, and send a response packet of the service access request to the offloading device, so that the offloading device forwards the response packet to the terminal device.

According to an aspect of an embodiment of the present application, there is provided a communication processing apparatus including: a first receiving unit, configured to receive a scheduling request packet sent by a terminal device; a first sending unit, configured to send the scheduling request packet to an edge computing device when a destination address of the scheduling request packet is a network address of a specified service scheduler, so that the edge computing device replaces a source address of the scheduling request packet with a set address and sends the source address to the specified service scheduler; a second receiving unit, configured to receive a scheduling feedback data packet returned by the edge computing device, where the scheduling feedback data packet is generated by the specified service scheduler according to the scheduling request data packet and includes a network address of the edge computing device; a second sending unit, configured to send the scheduling feedback data packet to the terminal device, so that the terminal device initiates a service access request to the edge computing device according to the network address of the edge computing device.

In some embodiments of the application, based on the foregoing scheme, the first sending unit is further configured to, before sending the scheduling request packet to an edge computing device, forward, if a DNS request sent by the terminal device is received, the DNS request to a DNS server, and send, when receiving a DNS response message returned by the DNS server, the DNS response message to the edge computing device, so that the edge computing device generates a offloading policy for domain name information according to the domain name information included in the DNS response message; the communication processing device further comprises a determining unit, configured to acquire the offloading policy, and determine a network address of the specified service scheduler according to the offloading policy.

In some embodiments of the application, based on the foregoing scheme, the first sending unit is further configured to send, if a DNS response message returned by the DNS server is received, the DNS response message to the terminal device, so that the terminal device sends the scheduling request packet according to the DNS response message.

In some embodiments of the present application, based on the foregoing scheme, the first sending unit is configured to: and forwarding the DNS request to the DNS server through a first user plane functional entity, and sending the DNS response message to the edge computing device through a second user plane functional entity.

In some embodiments of the present application, based on the foregoing scheme, the first sending unit is further configured to: and if the destination address of the scheduling request data packet is not the network address of the specified service scheduler, sending the scheduling request data packet to a core data center.

In some embodiments of the present application, based on the foregoing solution, the communication processing apparatus further includes: a third receiving unit, configured to receive a service access request sent by the terminal device; a third sending unit, configured to forward the service access request to the edge computing device when the service access request includes the network address of the edge computing device, and return a service response result to the terminal device when receiving a service response result to the service access request returned by the edge computing device.

According to an aspect of the embodiments of the present application, there is provided a computer-readable medium on which a computer program is stored, the computer program, when executed by a processor, implementing the communication processing method as described in the above embodiments.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: one or more processors; a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the communication processing method as described in the above embodiments.

In the technical solutions provided in some embodiments of the present application, a target data packet is obtained by replacing a source address of a scheduling request data packet of a terminal device with a set address (the set address may be an address associated with a network address of an edge computing device), and then the target data packet is sent to a specified service scheduler, so that the specified service scheduler can identify that an edge computing device can respond to a service access request of the terminal device according to the source address of the target data packet, and can return a scheduling feedback data packet including the network address of the edge computing device. By replacing the destination address of the scheduling feedback data packet with the network address of the terminal device and sending the network address to the terminal device, the terminal device can obtain the network address of the edge computing device allocated by the appointed service scheduler, and further can initiate a service access request to the edge computing device. Therefore, according to the technical scheme of the embodiment of the application, the service scheduler can identify whether the service request of the terminal device can be processed by the edge computing device, and then can deliver the service to the terminal device through the edge computing device, so that not only is the time delay of the terminal device for accessing the service reduced, but also the bandwidth consumption of the core data center is reduced, and meanwhile, the bandwidth cost of the edge computing device is usually lower than that of the core data center, so that the technical scheme of the embodiment of the application can also effectively reduce the overall bandwidth cost of a service provider.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

FIG. 1 is a diagram illustrating an exemplary system architecture to which aspects of embodiments of the present application may be applied;

FIG. 2 shows a schematic diagram of an exemplary system architecture to which aspects of embodiments of the present application may be applied;

FIG. 3 shows a flow diagram of a communication processing method according to one embodiment of the present application;

FIG. 4 shows a flow diagram of a communication processing method according to one embodiment of the present application;

FIG. 5 shows a flow diagram of a communication processing method according to an embodiment of the present application;

FIG. 6 shows a flow diagram of a communication processing method according to one embodiment of the present application;

FIG. 7 shows a flow diagram of a communication processing method according to an embodiment of the present application;

FIG. 8 shows a flow diagram of a communication processing method according to an embodiment of the present application;

FIG. 9 shows a block diagram of a communication processing system according to an embodiment of the present application;

FIG. 10 shows an interaction process diagram of a communication processing system according to an embodiment of the present application;

FIG. 11 shows a block diagram of a communication processing apparatus according to an embodiment of the present application;

FIG. 12 shows a block diagram of a communication processing apparatus according to an embodiment of the present application;

FIG. 13 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

It should be noted that: the MEC equipment in the embodiment of the application is located in an edge computing center, the edge computing center is compared with a core data center, the core data center is a centralized data center located at the rear end, a user can access the core data center through a network to acquire required data, but the distance between the user and the core data center is possibly longer, and further the service access delay is possibly increased; the edge data center is located closest to the user, and can keep real-time data updating with the core data center through the wide area network so as to directly provide good service for the user.

Fig. 1 shows a schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied.

As shown in fig. 1, the system architecture may include a terminal device 101 (the terminal device 101 may be the smart phone shown in fig. 1, or may also be a tablet computer, a portable computer, a desktop computer, and the like), an Uplink Classifier (UL CL)102, a User Plane Function (UPF) entity 103, a core data center 104, a User Plane Function entity 105, an edge computing device 106, and a Policy Control Function (PCF) entity 107. The user plane functional entity 103 and the user plane functional entity 105 are both connected to the uplink classifier 102, the user plane functional entity 103 is configured to forward communication data between the uplink classifier 102 and the core data center 104, and the user plane functional entity 105 is configured to forward communication data between the uplink classifier 102 and the edge computing device 106.

It should be understood that the number of terminal devices, user plane functional entities, servers within the core data center, edge computing devices and policy control functional entities shown in fig. 1 is merely illustrative. There may be any number of terminal devices, user plane functional entities, servers within the core data center, edge computing devices, and policy control functional entities, as desired for implementation.

In an embodiment of the present application, the terminal device 101 generates a DNS request and sends the DNS request to the uplink classifier 102, and the uplink classifier 102 forwards the DNS request to the user plane functional entity 103, and then sends the DNS request to the core data center 104 by the user plane functional entity 103. A DNS server in core data center 104 may generate a DNS response message according to the DNS request, and then forward the DNS response message to upstream classifier 102 through user plane functional entity 103. The DNS Server may be GSLB (Global Server Load Balance).

In an embodiment of the present application, after receiving the DNS response message forwarded by the user plane functional entity 103, the uplink classifier 102 sends the DNS response message to the terminal device 101 on the one hand, and sends the DNS response message to the user plane functional entity 105 on the other hand, and then the user plane functional entity 105 sends the DNS response message to the edge computing device 106.

In an embodiment of the present application, after receiving a DNS response message sent by the user plane functional entity 105, the edge computing device 106 parses the DNS response message to obtain domain name information and an IP (Internet Protocol) address included in the DNS response message, and if the domain name information included in the DNS response message is domain name information already stored by the edge computing device 106 (the domain name information already stored by the edge computing device 106 may be domain name information configured in advance to the edge computing device 106, for example, domain name information corresponding to a service scheduler capable of scheduling the edge computing device 106), it indicates that the edge computing device 106 can process a service request of the terminal device 101, and further the edge computing device 106 may generate a offloading policy, and send the offloading policy to the upstream classifier 102 through the policy control functional entity 107, where the offloading policy is used for enabling the upstream classifier 102 to send a scheduling request packet whose destination address is the aforementioned IP address through the user plane functional entity 107 Entity 105 forwards to edge computing device 106.

In an embodiment of the present application, after receiving a DNS response message sent by the uplink classifier 102, the terminal device 101 initiates a scheduling request packet according to an IP address included in the DNS response message (that is, the IP address is used as a destination address of the scheduling request packet), and after receiving the scheduling request packet, the uplink classifier 102 forwards the scheduling request packet to the user plane functional entity 105 according to the foregoing offloading policy, and the user plane functional entity 105 sends the scheduling request packet to the edge computing device 106. When the edge computing device 106 receives the scheduling request packet, the source address of the scheduling request packet is replaced with the network address of the edge computing device 106, and then the scheduling request packet is sent to the core data center 104.

In an embodiment of the present application, after the service scheduler in the core data center 104 receives the scheduling request data packet sent by the edge computing device 106, it is determined that the edge computing device 106 can process the service request of the terminal device 101 according to the source address of the scheduling request data packet, and then a scheduling feedback data packet is generated according to the network address of the edge computing device 106, and the scheduling feedback data packet is sent to the edge computing device 106.

In an embodiment of the present application, after receiving the scheduling feedback packet, the edge computing device 106 replaces the destination address of the scheduling feedback packet with the network address of the terminal device 101, and then sends the scheduling feedback packet to the uplink classifier 102 through the user plane functional entity 105, and the uplink classifier 102 forwards the scheduling feedback packet to the terminal device 101.

In an embodiment of the present application, after receiving a scheduling feedback data packet sent by the uplink classifier 102, the terminal device 101 may obtain a network address of the edge computing device 106 by analyzing the scheduling feedback data packet, and then may initiate a service access request to the edge computing device 106 based on the network address of the edge computing device 106.

As can be seen, the system architecture of the embodiment shown in fig. 1 enables the service scheduler in the core data center 104 to identify whether the service request of the terminal device 101 can be processed by the edge computing device 106, and further enables the service to be delivered to the terminal device 101 through the edge computing device 106, which not only reduces the time delay of the terminal device 101 for accessing the service, but also reduces the bandwidth consumption of the core data center 104.

Fig. 2 shows a schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied. Among them, the system architecture shown in fig. 2 is different from the system architecture shown in fig. 1 in that the policy control function entity 107 shown in fig. 1 is removed from the system architecture shown in fig. 2.

Based on the system architecture shown in fig. 2, in an embodiment of the present application, the terminal device 101 generates a DNS request and sends the DNS request to the uplink classifier 102, and the uplink classifier 102 forwards the DNS request to the user plane functional entity 103, and then sends the DNS request to the core data center 104 by the user plane functional entity 103. A DNS server in core data center 104 may generate a DNS response message according to the DNS request, and then forward the DNS response message to upstream classifier 102 through user plane functional entity 103. After receiving the DNS response message forwarded by the user plane functional entity 103, the uplink classifier 102 sends the DNS response message to the terminal device 101, and the uplink classifier 102 directly resolves the DNS response message to obtain the domain name information and the IP address included in the DNS response message, and if the domain name information included in the DNS response message is the domain name information already stored by the edge computing device 106 (assuming that the uplink classifier 102 already obtains the domain name information already stored by the edge computing device 106), the uplink classifier 102 may determine that the edge computing device 106 can process the service request of the terminal device 101.

In the system architecture shown in fig. 2, after receiving the DNS response message sent by the uplink classifier 102, the terminal device 101 initiates a scheduling request packet according to the IP address contained in the DNS response message (i.e. the IP address is used as the destination address of the scheduling request packet), and after receiving the scheduling request packet, the uplink classifier 102 may send the scheduling request packet to the edge computing device 106 through the user plane functional entity 105 according to the flow of the system architecture shown in fig. 1, and the edge computing device 106 replaces the source address of the scheduling request packet with the network address of the edge computing device 106, and then sends the scheduling request packet to the core data center 104. Alternatively, after the uplink classifier 102 receives the scheduling request packet, the uplink classifier 102 may replace the source address of the scheduling request packet with the network address of the edge computing device 106 (assuming that the uplink classifier 102 has acquired the network address of the edge computing device 106), and then send the scheduling request packet to the core data center 104 through the user plane functional entity 103 or the user plane functional entity 105.

In the system architecture shown in fig. 2, after a service scheduler in a core data center 104 receives a scheduling request data packet sent by an edge computing device 106, it is determined that the edge computing device 106 can process a service request of a terminal device 101 according to a source address of the scheduling request data packet, and further, a scheduling feedback data packet is generated according to a network address of the edge computing device 106, and the scheduling feedback data packet is sent to the terminal device 101 through an uplink classifier 102 (for example, the scheduling feedback data packet is sent to the uplink classifier 102 through a user plane functional entity 103, or the scheduling feedback data packet is sent to the uplink classifier 102 through the edge computing device 106 and the user plane functional entity 105).

The system architecture of the embodiment shown in fig. 2 also enables the service scheduler in the core data center 104 to identify whether the service request of the terminal device 101 can be processed by the edge computing device 106, and further enable the service to be delivered to the terminal device 101 through the edge computing device 106, but the network address of the edge computing device 106 and the domain name information stored by the edge computing device 106 need to be configured in the upstream classifier 102 in advance.

The implementation details of the technical solution of the embodiment of the present application are set forth in detail below:

fig. 3 illustrates a flow diagram of a communication processing method according to an embodiment of the present application, which may be performed by an edge computing device, such as the edge computing device 106 shown in fig. 1. Referring to fig. 3, the communication processing method at least includes steps S310 to S340, which are described in detail as follows:

in step S310, a scheduling request packet from a terminal device is obtained, where a destination address of the scheduling request packet is a network address of a specified service scheduler.

In one embodiment of the present application, the scheduling request packet is a packet for requesting the service scheduler to allocate a service server, which is used for responding to a service access request of the terminal device, and may be a service server in the edge computing device or a service server in the core data center. Wherein the designated service scheduler may be a service scheduler capable of scheduling the edge computing device to process the service request of the terminal device.

In one embodiment of the present application, the edge computing device may receive a scheduling request packet from the terminal device forwarded by the offloading device. The terminal device may send the scheduling request packet to the base station device, and the base station device forwards the scheduling request packet to the offloading device, so that the offloading device forwards the scheduling request packet to the edge computing device when detecting that a destination address of the scheduling request packet is a network address of the specified service scheduler. The shunting device in this embodiment may be the upstream classifier 102 shown in fig. 1.

In an embodiment of the present application, in order to enable the offloading device to forward a scheduling request packet having a destination address as a network address of a specified service scheduler to the edge computing device, the edge computing device may send a corresponding offloading policy to the offloading device, which may be specifically as shown in fig. 4, including the following steps S410 to S440, which are described in detail as follows:

in step S410, a DNS response message sent by the offloading device is received, where the DNS response message is generated by the DNS server according to the DNS request sent by the terminal device and sent to the offloading device.

In an embodiment of the application, after the terminal device generates the DNS request, the terminal device sends the DNS request to the offloading device, and the offloading device forwards the DNS request to the DNS server, and generates a DNS response message in response to the DNS request. After generating the DNS response message, the DNS server sends the DNS response message to the offloading device, and after receiving the DNS response message, the offloading device may send the DNS response message to the terminal device on the one hand and the edge computing device on the other hand.

As shown in fig. 4, in step S420, if the domain name information in the DNS response message includes the target domain name, the network address included in the DNS response message is used as the network address of the designated service scheduler.

In an embodiment of the present application, the DNS response message includes domain name information and an IP address assigned by the DNS server. The target domain name may be domain name information configured and stored in the edge computing device, such as domain name information corresponding to a traffic scheduler capable of scheduling the edge computing device. When the domain name information in the DNS response message includes the target domain name, it indicates that the edge computing device can process the service request of the terminal device, and further, the network address included in the DNS response message can be used as the network address of the specified service scheduler to generate the offloading policy.

In an embodiment of the present application, if the domain name information in the DNS response message does not include the target domain name, it indicates that the edge computing device cannot process the service request of the terminal device, and further the edge computing device may discard the DNS response message; or the edge computing device may also send notification information to the offloading device to notify the offloading device that the scheduling request packet whose destination address matches the IP address in the DNS response message (e.g., if the IP address in the DNS response message includes the destination address of the scheduling request packet, it indicates that the destination address of the scheduling request packet matches the IP address in the DNS response message) does not need to be forwarded to the edge computing device; or the edge computing device may also send a notification message to the offloading device, so that the offloading device forwards the scheduling request packet whose destination address matches the network address included in the DNS response message to the target service scheduler (for example, the scheduling request packet may be directly forwarded to the target service scheduler without passing through the edge computing device), where the network address of the target service scheduler is the network address included in the DNS response message.

Continuing to refer to fig. 4, in step S430, a offloading policy is generated according to the network address of the specified service scheduler, where the offloading policy is used to enable the offloading device to forward a scheduling request packet whose destination address matches the network address of the specified service scheduler to the edge computing device.

In an embodiment of the present application, the generating of the offloading policy according to the network address of the specified service scheduler may be to generate the offloading policy by using the network address of the specified service scheduler as a parameter, so that the offloading device can obtain the network address of the specified service scheduler by analyzing the offloading policy.

Continuing to refer to fig. 4, in step S440, the offloading policy is sent to the offloading device.

In an embodiment of the present application, when the edge computing device sends the offloading policy to the offloading device, the offloading policy may be sent to the policy control function entity, and then forwarded to the offloading device by the policy control function entity.

The technical solution of the embodiment shown in fig. 4 enables the edge computing device to determine whether the service request of the terminal device can be responded by resolving the DNS response message, and further, may generate the offloading policy to enable the offloading device to forward the corresponding scheduling request packet to the edge computing device, so that the edge computing device ensures that the service scheduler identifies that the edge computing device can process the service request of the terminal device by modifying the source address of the scheduling request packet.

Continuing with fig. 3, in step S320, the source address of the scheduling request packet is replaced with the network address of the edge computing device, so as to obtain a target packet.

In an embodiment of the present application, a source address of a scheduling request packet is a network address of a terminal device, and in this embodiment, a target packet is obtained by replacing the source address of the scheduling request packet with the network address of an edge computing device, so that after receiving the target packet, a specified service scheduler can identify that the edge computing device can process a service request of the terminal device according to the source address of the target packet (i.e., the replaced source address).

Continuing with fig. 3, in step S330, the destination data packet is sent to the designated service scheduler, so that the designated service scheduler returns a scheduling feedback data packet containing the network address of the edge computing device.

In an embodiment of the present application, after sending the target data packet to the specified service scheduler, the specified service scheduler may identify, according to a source address of the target data packet (i.e., a replaced source address), that the edge computing device is capable of processing a service request of the terminal device, and may further generate a scheduling feedback data packet including a network address of the edge computing device, and return the scheduling feedback data packet to the edge computing device.

Continuing to refer to fig. 3, in step S340, the scheduling feedback data packet is received, and the destination address of the scheduling feedback data packet is replaced with the network address of the terminal device and then sent to the terminal device, so that the terminal device initiates a service access request to the edge computing device according to the network address of the edge computing device.

In an embodiment of the present application, after replacing the destination address of the scheduling feedback packet with the network address of the terminal device, the destination address of the scheduling feedback packet may be sent to the offloading device, so that the offloading device forwards the scheduling feedback packet to the terminal device.

In an embodiment of the present application, after replacing the destination address of the scheduling feedback packet with the network address of the terminal device and sending the destination address to the terminal device, as shown in fig. 5, the method may further include the following steps:

step S510, receives a service access request from the terminal device forwarded by the offloading device.

In an embodiment of the present application, after sending the scheduling feedback data packet to the terminal device, the terminal device may initiate a service access request to the edge computing device according to a network address of the edge computing device included in the scheduling feedback data packet, and after the service access request reaches the offloading device, the offloading device may forward the service access request to the edge computing device.

Step S520, responding to the service access request, and sending a response packet of the service access request to the offloading device, so that the offloading device forwards the response packet to the terminal device.

In one embodiment of the present application, responding to the service access request may be to generate corresponding response data according to the content requested by the terminal device. For example, if the service access request is an acquisition request for a certain video segment, the data for acquiring the video segment is obtained in response to the service access request.

It should be noted that fig. 3 to fig. 5 illustrate the communication processing method according to the embodiment of the present application from the perspective of the edge computing device. In other embodiments of the present application, the communication processing method shown in fig. 3 may also be executed by a offloading device (e.g., the uplink classifier 102 shown in fig. 1), and when the communication processing method shown in fig. 3 is executed by the offloading device, specific implementation details may refer to the description of the system architecture shown in fig. 2 in the foregoing embodiments.

Fig. 6 shows a flowchart of a communication processing method according to an embodiment of the present application, which may be performed by a offloading device, such as the upstream classifier 102 shown in fig. 1. Referring to fig. 6, the communication processing method at least includes steps S610 to S640, and the following is described in detail:

in step S610, a scheduling request packet transmitted by the terminal device is received.

In an embodiment of the present application, the terminal device may send the scheduling request packet to the base station device, and the base station device forwards the scheduling request packet to the offloading device.

In step S620, if the destination address of the scheduling request packet is the network address of the designated service scheduler, the scheduling request packet is sent to an edge computing device, so that the edge computing device replaces the source address of the scheduling request packet with the network address of the edge computing device and sends the source address of the scheduling request packet to the designated service scheduler.

In one embodiment of the present application, the designated service scheduler may be a service scheduler capable of scheduling the edge computing device to process the service request of the terminal device. In step S620, when the destination address of the scheduling request packet is the network address of the specified service scheduler, the scheduling request packet is sent to the edge computing device, so that the edge computing device can modify the source address of the scheduling request packet, thereby ensuring that the specified service scheduler can identify, according to the modified scheduling request packet, that the edge computing device can process the service request of the terminal device, and further, the edge computing device can be scheduled to provide service to the terminal device, thereby effectively reducing the time delay for the terminal device to access the service.

In an embodiment of the present application, the offloading device needs to know a network address of the specified service scheduler in advance, so as to send the corresponding scheduling request packet to the edge computing device, which may be specifically as shown in fig. 7, and includes the following steps S710 to S730:

in step S710, if a DNS request sent by the terminal device is received, the DNS request is forwarded to the DNS server.

In an embodiment of the application, the DNS request sent by the terminal device may be sent to the offloading device by the base station device, and after receiving the DNS request, the offloading device may forward the DNS request to the DNS server by the user plane functional entity.

In step S720, if a DNS response message returned by the DNS server is received, the DNS response message is sent to the edge computing device, so that the edge computing device generates a offloading policy for the domain name information according to the domain name information included in the DNS response message.

In an embodiment of the present application, the DNS response message is typically encapsulated with port information, such as 53 ports (53 ports are ports opened by the DNS server and mainly used for domain name resolution), so that the offloading device may determine whether DNS corresponding information is received according to the port information encapsulated in the received data packet.

In an embodiment of the present application, after receiving the DNS response message, the edge computing device may determine whether domain name information in the DNS response message includes a target domain name (the target domain name may be domain name information configured and stored in the edge computing device, for example, domain name information corresponding to a service scheduler capable of scheduling the edge computing device), and if the domain name information in the DNS response message includes the target domain name, it indicates that the edge computing device is capable of processing a service request of the terminal device, and further, may use a network address included in the DNS response message as a network address of the specified service scheduler to generate the offloading policy.

In step S730, the offloading policy is obtained, and the network address of the specified service scheduler is determined according to the offloading policy.

In an embodiment of the present application, after the edge computing device generates the offloading policy, the offloading policy may be sent to the policy control function entity, and then forwarded to the offloading device by the policy control function entity.

The technical solution of the embodiment shown in fig. 7 enables the offloading device to send a DNS response message to the edge computing device, so that the edge computing device generates an offloading policy, and further enables the offloading device to forward a corresponding scheduling request packet to the edge computing device according to the offloading policy sent by the edge computing device, so that the edge computing device ensures that the service scheduler identifies that the edge computing device can process the service request of the terminal device by modifying the source address of the scheduling request packet.

In an embodiment of the present application, if the offloading device receives a DNS response message returned by the DNS server, the DNS response message may be sent to the terminal device, so that the terminal device sends the scheduling request packet according to the DNS response message. For example, the terminal device may initiate a scheduling request packet to an IP address contained in the DNS response message (the IP address is the IP address of the traffic scheduler assigned to the terminal device by the DNS server).

In an embodiment of the application, the offloading device may forward the DNS request to the DNS server through the first user plane functional entity, and send the DNS response message to the edge computing device through the second user plane functional entity.

In an embodiment of the present application, if the destination address of the scheduling request packet is not the network address of the specified service scheduler, the offloading device may directly send the scheduling request packet to the core data center, so that other service schedulers in the core data center respond to the scheduling request packet.

Continuing to refer to fig. 6, in step S630, a scheduling feedback packet returned by the edge computing device is received, where the scheduling feedback packet is generated by the specified service scheduler according to the scheduling request packet and includes the network address of the edge computing device.

In one embodiment of the present application, after the offload device sends the scheduling request packet to the edge computing device, the edge computing device may replace the source address of the dispatch request packet with the network address of the edge computing device and send to the designated traffic scheduler, and further specifies that the service scheduler, after receiving the modified scheduling request packet, can identify that the edge computing device can process the service request of the terminal device according to the source address (i.e. the network address of the edge computing device) therein, and may generate a scheduling feedback packet containing the network address of the edge computing device, the designated traffic scheduler, after generating the scheduling feedback packet, may send the scheduling feedback packet to the edge computing device, and then the edge computing device replaces the destination address in the scheduling feedback data packet with the destination address of the terminal device and sends the destination address to the shunting device.

Continuing to refer to fig. 6, in step S640, the scheduling feedback packet is sent to the terminal device, so that the terminal device initiates a service access request to the edge computing device according to the network address of the edge computing device.

In an embodiment of the present application, the offloading device may send the scheduling feedback data packet to the terminal device through the base station device.

In an embodiment of the present application, after the offloading device sends the scheduling feedback packet to the terminal device, as shown in fig. 8, the offloading device may further include the following steps:

step S810, receiving a service access request sent by the terminal device.

In an embodiment of the present application, after sending the scheduling feedback data packet to the terminal device, the terminal device may initiate a service access request to the edge computing device according to a network address of the edge computing device included in the scheduling feedback data packet, and after the service access request reaches the base station device, the base station device may forward the service access request to the offloading device.

Step S820, if the service access request includes the network address of the edge computing device, forwarding the service access request to the edge computing device.

In an embodiment of the present application, if the service access request includes a network address of the edge computing device, for example, a destination address of the service access request is a network address of the edge computing device, it indicates that the service access request is sent to the edge computing device, and therefore, the service access request may be forwarded to the edge computing device.

Step S830, if a service response result for the service access request returned by the edge computing device is received, returning the service response result to the terminal device.

In an embodiment of the present application, the offloading device may return the service response result to the terminal device through the base station device.

In the foregoing embodiment, the communication processing method in the embodiment of the present application is described from the perspective of the edge computing device and the offloading device, and the following describes in detail interaction and processing processes of each device by taking the edge computing device as an example including a preprocessing server and a service server, and taking the offloading device as an uplink classifier:

referring to fig. 9, a communication processing system according to an embodiment of the present application may include: terminal equipment 901, base station equipment 902, uplink classifier 903, user plane function entity 904, core data center 905, user plane function entity 906, edge computing equipment 907, and policy control function entity 908.

The terminal device 901 accesses the uplink classifier 903 through the base station device 902, and a data packet sent from the terminal device 901 is forwarded to the uplink classifier 903 after being received by the base station device 902; data packets destined for terminal equipment 901 also need to be received and processed by uplink classifier 903 before reaching base station equipment 902. The user plane functional entity 904 and the user plane functional entity 906 are both connected to the upstream classifier 903, the user plane functional entity 904 is configured to forward communication data between the upstream classifier 903 and the core data center 905, and the user plane functional entity 906 is configured to forward communication data between the upstream classifier 903 and the edge computing device 907.

In an embodiment of the present application, the core data center 905 may include a service scheduler 9051, may further include a DNS server (not shown in fig. 9), and the like, where the DNS server may be a GSLB, and the core data center 905 may also be provided with a service server for responding to a service access request of the terminal device 901.

In one embodiment of the application, the edge computing device 907 may include a preprocessing server 9071 and a business server 9072. The pre-processing server 9071 may process a received data packet (e.g., a data packet from the upstream classifier 903 or the core data center 905), such as replacing a source address or a destination address of the data packet. The service server 9072 may respond to a service access request of the terminal device 901.

The specific interaction and processing procedure of the communication processing system shown in fig. 9 is shown in fig. 10, and includes the following steps:

in step S1001, the terminal apparatus 901 transmits a DNS request for requesting assignment of a traffic scheduler to the GSLB to the base station apparatus 902.

In step S1002, the base station device 902 forwards the DNS request to the uplink classifier 903.

In step S1003, the uplink classifier 903 forwards the DNS request to the user plane functional entity 904.

In step S1004, the user plane function 904 sends the DNS request to the GSLB via the internet.

In step S1005, the GSLB selects a corresponding service scheduler 9051 according to the DNS request, writes the IP address of the service scheduler 9051 in the DNS response, and sends the DNS response to the user plane functional entity 904 via the internet.

In step S1006, the user plane functional entity 904 sends the DNS response to the upstream classifier 903. For example, the User Plane functional entity 904 may encapsulate the DNS response into a GTP-U (GPRS Tunnel Protocol-User Plane) Tunnel packet, and then forward the packet to the uplink classifier 903.

In step S1007, the uplink classifier 903 transmits a DNS response to the base station apparatus 902.

In step S1008, the base station apparatus 902 forwards the DNS response to the terminal apparatus 901.

In step S1009, the uplink classifier 903 sends the DNS response to the user plane functional entity 906.

In an embodiment of the present application, a rule for shunting the DNS response to the User plane functional entity 906 may be configured in the uplink classifier 903, for example, the rule may be a GTP-U tunnel packet encapsulating a UDP (User Datagram Protocol) with a source port of 53, which needs to be copied, and the copied copy is forwarded to the User plane functional entity 906.

In an embodiment of the present application, the process that the uplink classifier 903 sends the DNS response to the base station device 902 in step S1007 and the process that the uplink classifier 903 sends the DNS response to the user plane functional entity 906 in step S1009 may occur simultaneously, or step S1007 and step S1009 may be executed first, or step S1009 and step S1007 are executed first.

In step S1010, the user plane functional entity 906 sends the DNS response to the preprocessing server 9071 in the edge computing device 907.

In an embodiment of the present application, if the user plane functional entity encapsulates the DNS response into a GTP-U tunnel packet and forwards the GTP-U tunnel packet to the uplink classifier 903, the user plane functional entity 906 decapsulates the GTP-U tunnel packet forwarded by the uplink classifier 903 after receiving the GTP-U tunnel packet, and sends the extracted DNS response to the preprocessing server 9071.

In step S1011, the preprocessing server 9071 generates a offloading policy according to the received DNS response, and sends the offloading policy to the policy control function entity 908.

In an embodiment of the present application, after receiving the DNS response, the preprocessing server 9071 extracts the domain name and the corresponding IP address included in the DNS response. If the domain name extracted by the preprocessing server 9071 is the same as the domain name of a service scheduler capable of scheduling the edge computing device 907, which is configured in advance, a splitting policy is generated according to the extracted IP address, and the splitting policy is sent to the policy control function entity 908. The offloading policy may be expressed as that a GTP-U tunnel packet encapsulating a TCP (Transmission Control Protocol) packet whose destination address is an assigned IP address (the assigned IP address is an IP address extracted by the preprocessing server 9071 from the DNS response) needs to be forwarded to the user plane functional entity 906.

In step S1012, the policy control function 908 forwards the offloading policy to the upstream classifier 903.

In step S1013, after receiving the DNS response, the terminal apparatus 901 generates a service scheduling request from the IP address included in the DNS response and transmits the service scheduling request to the base station apparatus 902.

In one embodiment of the present application, the service scheduling request may be a TCP packet, and the TCP packet may be encapsulated in a GTP-U tunneling packet for transmission.

In step S1014, the base station device 902 forwards the service scheduling request to the uplink classifier 903.

In step S1015, after receiving the service scheduling request, the uplink classifier 903 forwards the service scheduling request to the user plane functional entity 906 according to the foregoing offloading policy.

In step S1016, the user plane functional entity 906 sends the service scheduling request to the preprocessing server 9071.

In an embodiment of the present application, if the service scheduling request is encapsulated in a GTP-U tunnel message for transmission, the user plane functional entity 906 may parse the GTP-U tunnel message to obtain a service scheduling request in the form of a TCP message, and then send the service scheduling request to the preprocessing server 9071.

In step S1017, after receiving the service scheduling request, the preprocessing server 9071 replaces the source IP address with the public network address of the edge computing device 907, and then sends the service scheduling request to the service scheduler 9051. In addition, the preprocessing server 9071 may replace the source port number of the packet of the service scheduling request with the unique port number of the preprocessing server 9071.

In step S1018, after receiving the service scheduling request, the service scheduler 9051 returns a service scheduling response to the preprocessing server 9071.

In an embodiment of the present application, since the source IP address of the service scheduling request has been replaced with the public network address of the edge computing device 907, the service scheduler 9051 may determine accordingly that the service request issued by the terminal device 901 may be processed by the service server 9072 in the edge computing device 907. Subsequently, the service scheduler 9051 may generate a service scheduling response according to the IP address of the service server 9072 in the edge computing device 907, and return to the pre-processing server 9071 through the TCP connection.

In step S1019, after receiving the service scheduling response, the preprocessing server 9071 replaces the destination IP address of the service scheduling response with the IP address of the terminal device 901, and forwards the service scheduling response to the user plane function entity 906.

In step S1020, the user plane functional entity 906 forwards the service scheduling response to the uplink classifier 903.

In an embodiment of the present application, the user plane functional entity 906 may encapsulate the service scheduling response returned by the preprocessing server 9071 into a GTP-U tunnel packet, and then send the GTP-U tunnel packet to the uplink classifier 903.

In step S1021, the uplink classifier 903 sends a service scheduling response to the base station apparatus 902.

In step S1022, the base station device 902 forwards the service scheduling response to the terminal device 901.

In step S1023, after receiving the service scheduling response, the terminal device 901 can obtain the IP address of the service server 9072 in the edge computing device 907, and then generate a service access request according to the IP address of the service server 9072, and send the service access request to the base station device 902.

Step S1024, the base station device 902 forwards the service access request to the uplink classifier 903.

In step S1025, the uplink classifier 903 forwards the service access request to the user plane function entity 906.

In step S1026, the user plane functional entity 906 sends the service access request to the service server 9072.

In step S1027, the service server 9072 returns a service access response to the user plane function entity 906.

In step S1028, the user plane functional entity 906 forwards the service access response to the uplink classifier 903.

In step S1029, the uplink classifier 903 transmits a service access response to the base station apparatus 902.

In step S1030, the base station device 902 forwards the service access response to the terminal device 901.

According to the technical scheme of the embodiment of the application, the possibility of delivering the service to the terminal equipment at the network edge is realized by utilizing the edge computing equipment, and through the mode, the service provider can place the service content in the MEC equipment for delivery, so that on one hand, the time delay of a user for accessing the service is reduced, and on the other hand, the bandwidth consumption of a core data center is reduced. Meanwhile, the bandwidth cost of the MEC equipment is usually lower than that of the core data center, so that the technical scheme of the embodiment of the application can effectively reduce the overall bandwidth cost of the service provider. In addition, the service delivery method provided by the technical scheme of the embodiment of the application does not need to reconstruct the existing service delivery architecture of the service provider, so that the system deployment cost of the service provider can be obviously reduced.

It should be noted that the technical solution of the embodiment of the present application may be applied not only to the edge computing scenario of a 5G network, but also to subsequent mobile communications such as 6G, etc

The following describes embodiments of an apparatus of the present application, which may be used to perform the communication processing method in the above embodiments of the present application. For details that are not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the communication processing method described above in the present application.

Fig. 11 shows a block diagram of a communication processing apparatus according to an embodiment of the present application.

Referring to fig. 11, a communication processing apparatus 1100 according to an embodiment of the present application includes: an acquisition unit 1102, a first processing unit 1104, a transmission unit 1106, and a second processing unit 1108.

The obtaining unit 1102 is configured to obtain a scheduling request packet from a terminal device, where a destination address of the scheduling request packet is a network address of a specified service scheduler; the first processing unit 1104 is configured to replace a source address of the scheduling request packet with a network address of an edge computing device to obtain a target packet; the sending unit 1106 is configured to send the target data packet to the specified service scheduler, so that the specified service scheduler returns a scheduling feedback data packet containing a network address of the edge computing device; the second processing unit 1108 is configured to receive the scheduling feedback data packet, replace a destination address of the scheduling feedback data packet with a network address of the terminal device, and send the destination address to the terminal device, so that the terminal device initiates a service access request to the edge computing device according to the network address of the edge computing device.

In an embodiment of the present application, the communication processing apparatus 1100 is disposed in the edge computing device, and the obtaining unit 1102 is configured to: receiving a scheduling request data packet from the terminal device, which is forwarded by a offloading device, wherein the scheduling request data packet is forwarded to the edge computing device when the offloading device detects that a destination address of the scheduling request data packet is a network address of the specified service scheduler.

In one embodiment of the present application, the communication processing apparatus 1100 further includes: a receiving unit, configured to receive, before receiving a scheduling request data packet from the terminal device forwarded by a offloading device, Domain Name System (DNS) response information sent by the offloading device, where the DNS response information is generated by a DNS server according to a DNS request sent by the terminal device and is sent to the offloading device; a generating unit, configured to, when domain name information in the DNS response message includes a target domain name, use a network address included in the DNS response message as a network address of the specified service scheduler, and generate a offloading policy according to the network address of the specified service scheduler, where the offloading policy is used to enable the offloading device to forward a scheduling request packet whose destination address matches the network address of the specified service scheduler to the edge computing device; the sending unit 1106 is further configured to send the offloading policy to the offloading device.

In an embodiment of the present application, the sending unit 1106 is further configured to: if the domain name information in the DNS response message does not include the target domain name, sending a notification message to the offloading device, so that the offloading device forwards a scheduling request packet whose destination address matches the network address included in the DNS response message to a target service scheduler, where the network address of the target service scheduler is the network address included in the DNS response message.

In an embodiment of the present application, the communication processing apparatus 1100 further includes: a third processing unit, configured to receive a service access request from the terminal device forwarded by the offloading device, respond to the service access request, and send a response packet of the service access request to the offloading device, so that the offloading device forwards the response packet to the terminal device.

Fig. 12 shows a block diagram of a communication processing device according to an embodiment of the present application.

Referring to fig. 12, a communication processing apparatus 1200 according to an embodiment of the present application includes: a first receiving unit 1202, a first transmitting unit 1204, a second receiving unit 1206 and a second transmitting unit 1208.

The first receiving unit 1202 is configured to receive a scheduling request packet sent by a terminal device; the first sending unit 1204 is configured to send the scheduling request packet to an edge computing device when a destination address of the scheduling request packet is a network address of a specified service scheduler, so that the edge computing device replaces a source address of the scheduling request packet with the network address of the edge computing device and sends the source address of the scheduling request packet to the specified service scheduler; a second receiving unit 1206 is configured to receive a scheduling feedback data packet returned by the edge computing device, where the scheduling feedback data packet is generated by the specified service scheduler according to the scheduling request data packet and includes a network address of the edge computing device; a second sending unit 1208 is configured to send the scheduling feedback data packet to the terminal device, so that the terminal device initiates a service access request to the edge computing device according to the network address of the edge computing device.

In an embodiment of the present application, the first sending unit 1204 is further configured to, before sending the scheduling request packet to an edge computing device, forward a DNS request sent by the terminal device to a DNS server if the DNS request is received, and send a DNS response message returned by the DNS server to the edge computing device when the DNS response message is received, so that the edge computing device generates a offloading policy for domain name information according to the domain name information included in the DNS response message; the communication processing apparatus 1200 further includes a determining unit, configured to acquire the offloading policy, and determine a network address of the specified service scheduler according to the offloading policy.

In an embodiment of the present application, the first sending unit 1204 is further configured to, if a DNS response message returned by the DNS server is received, send the DNS response message to the terminal device, so that the terminal device sends the scheduling request packet according to the DNS response message.

In one embodiment of the present application, the first sending unit 1204 is configured to: and forwarding the DNS request to the DNS server through a first user plane functional entity, and sending the DNS response message to the edge computing device through a second user plane functional entity.

In an embodiment of the present application, the first sending unit 1204 is further configured to: and if the destination address of the scheduling request data packet is not the network address of the specified service scheduler, sending the scheduling request data packet to a core data center.

In an embodiment of the present application, the communication processing apparatus 1200 further includes: a third receiving unit, configured to receive a service access request sent by the terminal device; a third sending unit, configured to forward the service access request to the edge computing device when the service access request includes the network address of the edge computing device, and return a service response result to the terminal device when receiving a service response result to the service access request returned by the edge computing device.

It should be noted that the computer system 1300 of the electronic device shown in fig. 13 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 13, a computer system 1300 includes a Central Processing Unit (CPU)1301 that can perform various appropriate actions and processes, such as performing the methods described in the above embodiments, according to a program stored in a Read-Only Memory (ROM) 1302 or a program loaded from a storage portion 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for system operation are also stored. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An Input/Output (I/O) interface 1305 is also connected to bus 1304.

The following components are connected to the I/O interface 1305: an input portion 1306 including a keyboard, a mouse, and the like; an output section 1307 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage portion 1308 including a hard disk and the like; and a communication section 1309 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 1309 performs communication processing via a network such as the internet. A drive 1310 is also connected to the I/O interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read out therefrom is mounted into the storage portion 1308 as necessary.

In particular, according to embodiments of the present application, the processes described below with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications component 1309 and/or installed from removable media 1311. The computer program executes various functions defined in the system of the present application when executed by a Central Processing Unit (CPU) 1301.

It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method described in the above embodiments.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A communication processing method, comprising:

acquiring a scheduling request data packet from terminal equipment, wherein the destination address of the scheduling request data packet is the network address of a specified service scheduler;

replacing the source address of the scheduling request data packet with a set address to obtain a target data packet;

sending the target data packet to the designated service scheduler so that the designated service scheduler returns a scheduling feedback data packet containing the network address of the edge computing device;

and receiving the scheduling feedback data packet, replacing the destination address of the scheduling feedback data packet with the network address of the terminal equipment, and then sending the scheduling feedback data packet to the terminal equipment, so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment.

2. The communication processing method according to claim 1, wherein acquiring the scheduling request packet from the terminal device in a case where the communication processing method is executed by the edge computing device, includes:

receiving a scheduling request data packet from the terminal device, which is forwarded by a offloading device, wherein the scheduling request data packet is forwarded to the edge computing device when the offloading device detects that a destination address of the scheduling request data packet is a network address of the specified service scheduler.

3. The communication processing method according to claim 2, wherein before receiving the scheduling request packet forwarded by the offloading device from the terminal device, the communication processing method further includes:

receiving a Domain Name System (DNS) response message sent by the shunting equipment, wherein the DNS response message is generated by a DNS server according to a DNS request sent by the terminal equipment and is sent to the shunting equipment;

if the domain name information in the DNS response message contains a target domain name, taking a network address contained in the DNS response message as a network address of the specified service dispatcher;

generating a shunting strategy according to the network address of the specified service scheduler, wherein the shunting strategy is used for enabling the shunting equipment to forward a scheduling request data packet of which the destination address is matched with the network address of the specified service scheduler to the edge computing equipment;

and sending the shunting strategy to the shunting equipment.

4. The communication processing method according to claim 3, further comprising:

if the domain name information in the DNS response message does not include the target domain name, sending a notification message to the offloading device, so that the offloading device forwards a scheduling request packet whose destination address matches the network address included in the DNS response message to a target service scheduler, where the network address of the target service scheduler is the network address included in the DNS response message.

5. The communication processing method according to any one of claims 2 to 4, wherein after the destination address of the scheduling feedback packet is replaced with the network address of the terminal device and then transmitted to the terminal device, the communication processing method further includes:

receiving a service access request from the terminal equipment, which is forwarded by the shunting equipment;

and responding to the service access request, and sending a response data packet of the service access request to the shunting equipment so that the shunting equipment forwards the response data packet to the terminal equipment.

6. A communication processing method, comprising:

receiving a scheduling request data packet sent by terminal equipment;

if the destination address of the scheduling request data packet is the network address of the appointed service scheduler, the scheduling request data packet is sent to edge computing equipment, so that the edge computing equipment replaces the source address of the scheduling request data packet with a set address and sends the set address to the appointed service scheduler;

receiving a scheduling feedback data packet returned by the edge computing device, wherein the scheduling feedback data packet is generated by the specified service scheduler according to the scheduling request data packet and contains the network address of the edge computing device;

and sending the scheduling feedback data packet to the terminal equipment so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment.

7. The communication processing method according to claim 6, wherein before transmitting the scheduling request packet to an edge computing device, the communication processing method further comprises:

if a DNS request sent by the terminal equipment is received, forwarding the DNS request to a DNS server;

if a DNS response message returned by the DNS server is received, sending the DNS response message to the edge computing equipment so that the edge computing equipment generates a distribution strategy aiming at the domain name information according to the domain name information contained in the DNS response message;

and acquiring the shunting strategy, and determining the network address of the appointed service scheduler according to the shunting strategy.

8. The communication processing method according to claim 7, further comprising:

and if a DNS response message returned by the DNS server is received, sending the DNS response message to the terminal equipment so that the terminal equipment sends the scheduling request data packet according to the DNS response message.

9. The communication processing method of claim 7, wherein forwarding the DNS request to a DNS server comprises: forwarding the DNS request to the DNS server through a first user plane functional entity;

sending the DNS response message to the edge computing device, including: and sending the DNS response message to the edge computing device through a second user plane functional entity.

10. The communication processing method according to claim 6, further comprising:

and if the destination address of the scheduling request data packet is not the network address of the specified service scheduler, sending the scheduling request data packet to a core data center.

11. The communication processing method according to any one of claims 6 to 10, wherein after transmitting the scheduling feedback packet to the terminal device, the communication processing method further includes:

receiving a service access request sent by the terminal equipment;

if the service access request contains the network address of the edge computing equipment, forwarding the service access request to the edge computing equipment;

and if a service response result which is returned by the edge computing device and aims at the service access request is received, returning the service response result to the terminal device.

12. A communication processing apparatus, comprising:

an obtaining unit, configured to obtain a scheduling request packet from a terminal device, where a destination address of the scheduling request packet is a network address of a specified service scheduler;

the first processing unit is used for replacing the source address of the scheduling request data packet with a set address to obtain a target data packet;

a sending unit, configured to send the target data packet to the specified service scheduler, so that the specified service scheduler returns a scheduling feedback data packet including a network address of the edge computing device;

and the second processing unit is used for receiving the scheduling feedback data packet, replacing the destination address of the scheduling feedback data packet with the network address of the terminal equipment and then sending the destination address of the scheduling feedback data packet to the terminal equipment, so that the terminal equipment initiates a service access request to the edge computing equipment according to the network address of the edge computing equipment.

13. A communication processing apparatus, comprising:

a first receiving unit, configured to receive a scheduling request packet sent by a terminal device;

a first sending unit, configured to send the scheduling request packet to an edge computing device when a destination address of the scheduling request packet is a network address of a specified service scheduler, so that the edge computing device replaces a source address of the scheduling request packet with a set address and sends the source address to the specified service scheduler;

a second receiving unit, configured to receive a scheduling feedback data packet returned by the edge computing device, where the scheduling feedback data packet is generated by the specified service scheduler according to the scheduling request data packet and includes a network address of the edge computing device;

a second sending unit, configured to send the scheduling feedback data packet to the terminal device, so that the terminal device initiates a service access request to the edge computing device according to the network address of the edge computing device.

14. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out a communication processing method according to any one of claims 1 to 5, or carries out a communication processing method according to any one of claims 6 to 11.

15. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the communication processing method of any one of claims 1 to 5 or the communication processing method of any one of claims 6 to 11.