A service processing method and device of a computing power network, an equipment and a medium

Abstract

The application provides a service processing method and device of a computing power network, equipment and a medium. The method determines a target service instance for processing a service of a customer based on a first service obtained by the customer. Then, identification information of the target service instance is added to a data packet and sent to an exit routing device corresponding to the target service instance. The above process only requires the entry routing device to make a decision. The exit routing device directly processes the data packet according to the identification information carried by the packet to indicate the service instance, thereby solving the loop problem that may be caused by simultaneous decision-making of the entry and exit routing devices. Since the exit routing device does not need to make a decision, it does not need to maintain a session table item for mapping a service flow to a server, thereby effectively reducing the forwarding resource requirement of the exit routing device.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a service processing method, apparatus, equipment, and medium for a computing power network. Background Technology

[0002] As the information society enters a new stage of intelligence, the demand for information infrastructure is no longer limited to solving device connectivity issues. Currently, computing power and big data resources have become the key to new types of information infrastructure. Computing power networks are a new type of information infrastructure that allocates and flexibly schedules resources on demand among the cloud, edge, and endpoints based on business needs.

[0003] Computing power services have a "sticky" requirement for servers. That is, once the first message of a computing power service is processed by a certain server, subsequent messages of that computing power service must also be processed by the same server; otherwise, the continuity of the service will be disrupted. Based on this, computing power networks require routing devices to maintain a session table to record the mapping relationship between service flows and servers.

[0004] Current computing power networks mostly adopt the Dyncast (draft-li-dyncast-architecture-08) distributed architecture. Both ingress and egress routing devices make routing decisions based on the service's identifier (D-SID). Ingress routing devices connect to local users, and the number of session entries is controllable. However, egress routing devices connect to servers, and all access to that service is recorded in the session table. This leads to egress devices consuming significant memory to maintain these session entries. Furthermore, during the convergence of the computing power routing control plane due to fluctuations in computing power information, the computing power resource information of the ingress and egress routing devices may become asynchronous. This can result in differing routing decisions between the ingress and egress routing devices, leading to loop problems, wasting network resources, and impacting service experience. Summary of the Invention

[0005] This application provides a service processing method, apparatus, device, and medium for a computing network. It is used to perform routing decisions through ingress routing devices to resolve loop problems that may arise from simultaneous decisions by ingress and egress routing devices, and to effectively reduce the forwarding resource requirements of egress routing devices.

[0006] To achieve the above objectives, the technical solution of this application embodiment is implemented as follows:

[0007] In a first aspect, embodiments of this application provide a service processing method for a computing power network, applied to an ingress routing device, the method comprising:

[0008] Determine the target service instance corresponding to the first service accessed by the client; wherein, the first service is provided by the computing power network;

[0009] The identification information of the target service instance is encapsulated in a data packet from the client;

[0010] The data packet is sent to the egress routing device corresponding to the target service instance so that the target service instance of the egress routing device processes the data packet.

[0011] In some possible embodiments, encapsulating the identification information of the target service instance in a data packet from the client includes:

[0012] Add the identification information of the target service instance to the IPv6 extension header of the data packet.

[0013] In some possible embodiments, the IPv6 extension header of the data packet includes a target option header, which includes first option content carrying the identification information.

[0014] In some possible embodiments, the IPv6 extension header of the data packet includes a segment routing header, which includes a first type length value (TLV) and the first TLV includes identification information of the target service instance.

[0015] In some possible embodiments, the IPv6 extension header of the datagram includes a segment routing header, which includes a segment list, with the identification information located at the end of the path indicated by the segment list.

[0016] In some possible embodiments, the computing power network includes multiple routing devices connected to servers for providing the first service;

[0017] The determination of the target service instance corresponding to the first service accessed by the client includes:

[0018] Obtain the computing power resource information of the server corresponding to each routing device in the computing power network and the network parameter information of each routing device; wherein, the network parameter information includes at least the network latency and bandwidth of the routing device;

[0019] Based on the computing power resource information and the network parameter information, the target service instance is selected from each service instance under the first service in each routing device.

[0020] In this embodiment, the ingress routing device, after obtaining the first service requested by the customer, determines the target service instance for processing the customer's business based on the first service. Then, it adds the identification information of the target service instance to the data packet and sends it to the egress routing device corresponding to the target service instance. This process only requires the ingress routing device to make the decision; the egress routing device directly instructs the service instance to process the data packet based on the identification information carried in the packet, thus resolving the loop problem that may occur if both the ingress and egress routing devices make decisions simultaneously. Furthermore, since the egress routing device does not need to make decisions, it does not need to maintain session entries mapping the business flow to the server, thus effectively reducing the forwarding resource requirements of the egress routing device.

[0021] Secondly, embodiments of this application provide a service processing method for a computing power network, applied to an egress routing device, the method comprising:

[0022] Receive data packets sent by the ingress routing device, and parse the data packets to obtain the identification information of the target service instance;

[0023] The indication address of the data packet is determined based on the identification information, and the data packet is sent to the indication address so that the target service instance processes the data packet.

[0024] In some possible embodiments, the identification information is obtained by parsing in the following manner:

[0025] Method 1: Parse the destination option header of the data packet to obtain the custom option content carried by the destination option header; determine the identification information based on the custom option content;

[0026] Method 2: Parse the segment routing header of the data packet to obtain the type length value of the segment routing header; determine the identification information based on the type length value;

[0027] Method 3: Parse the segment routing header of the data packet to obtain the segment list of the segment routing header; determine the identification information according to the path indicated by the segment list.

[0028] In this embodiment, the egress routing device receives data packets from the ingress routing device, processes the data packets to obtain the identification information of the target service instance, and then determines the indication address of the data packet based on the identification information. The device then sends the data packet to the indication address so that the target service instance at that address can process the client's service. In this process, the egress routing device directly instructs the service instance to process the data packet loop based on the identification information carried in the packet, without needing to make routing decisions. This solves the loop problem that may arise from simultaneous decisions by both ingress and egress routing devices. Furthermore, since the egress routing device does not need to make decisions, it does not need to maintain session entries mapping service flows to servers, thus effectively reducing the forwarding resource requirements of the egress routing device.

[0029] Thirdly, embodiments of this application provide a service processing apparatus for a computing power network, the apparatus comprising:

[0030] The instance selection module is configured to determine the target service instance corresponding to the first service accessed by the client.

[0031] The information encapsulation module is configured to encapsulate the identification information of the target service instance in a data packet from the client;

[0032] The message forwarding module is configured to send the data packet to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet.

[0033] In some possible embodiments, the process of encapsulating the identification information of the target service instance in a data packet from the client is performed, wherein the information encapsulation module is configured to:

[0034] Add the identification information of the target service instance to the IPv6 extension header of the data packet.

[0035] In some possible embodiments, the IPv6 extension header of the data packet includes a target option header, which includes first option content carrying the identification information.

[0036] In some possible embodiments, the IPv6 extension header of the data packet includes a segment routing header, which includes a first type length value (TLV) and the first TLV includes identification information of the target service instance.

[0037] In some possible embodiments, the IPv6 extension header of the datagram includes a segment routing header, which includes a segment list, with the identification information located at the end of the path indicated by the segment list.

[0038] In some possible embodiments, the computing power network includes multiple routing devices connected to servers for providing the first service;

[0039] The instance selection module is configured to execute the target service instance corresponding to the first service accessed by the client, and the execution is performed as follows:

[0040] Obtain the computing power resource information of the server corresponding to each routing device in the computing power network and the network parameter information of each routing device; wherein, the network parameter information includes at least the network latency and bandwidth of the routing device;

[0041] Based on the computing power resource information and the network parameter information, the target service instance is selected from each service instance under the first service in each routing device.

[0042] Fourthly, embodiments of this application provide a service processing apparatus for a computing power network, the apparatus comprising:

[0043] The message parsing module is configured to receive data packets sent by the ingress routing device and parse the data packets to obtain the identification information of the target service instance;

[0044] The business processing module is configured to determine the indication address of the data packet based on the identification information, and send the data packet to the indication address so that the target service instance can process the data packet.

[0045] In some possible embodiments, the identification information is obtained by parsing in the following manner:

[0046] Method 1: Parse the destination option header of the data packet to obtain the custom option content carried by the destination option header; determine the identification information based on the custom option content;

[0047] Method 2: Parse the segment routing header of the data packet to obtain the type length value of the segment routing header; determine the identification information based on the type length value;

[0048] Method 3: Parse the segment routing header of the data packet to obtain the segment list of the segment routing header; determine the identification information according to the path indicated by the segment list.

[0049] Fifthly, embodiments of this application also provide a service processing system for a computing power network, the system including an ingress routing device and an egress routing device, wherein:

[0050] The ingress routing device is configured to: determine the target service instance corresponding to the first service accessed by the client, and encapsulate the identification information of the target service instance in a data packet from the client;

[0051] The data packet is sent to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet.

[0052] The outbound routing device is configured to: receive data packets sent by the inbound routing device, and parse the data packets to obtain the identification information of the target service instance;

[0053] The indication address of the data packet is determined based on the identification information, and the data packet is sent to the indication address so that the target service instance processes the data packet.

[0054] In a sixth aspect, embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and when the computer program is executed by the processor, the processor causes the processor to implement any of the methods in the first or second aspect described above.

[0055] In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements any of the methods described in the first or second aspect above.

[0056] Eighthly, according to an embodiment of this application, a computer program product includes computer instructions stored in a computer-readable storage medium; when a processor of a computer device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the computer device to perform any of the methods in the first or second aspect described above.

[0057] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing this disclosure. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0058] Figure 1 A schematic diagram of a computing network provided in an embodiment of this application;

[0059] Figure 2 A schematic diagram of the traditional business processing flow of a computing power network provided in the embodiments of this application;

[0060] Figure 3 An overall flowchart of a service processing method for a computing power network provided in this application embodiment;

[0061] Figure 4 A schematic diagram illustrating how the ingress routing device selects a target service instance, as provided in an embodiment of this application.

[0062] Figure 5 This is a schematic diagram of the purpose option header provided for embodiments of this application;

[0063] Figure 6 A schematic diagram illustrating the addition of identification information to the destination option header as provided in an embodiment of this application;

[0064] Figure 7 A schematic diagram illustrating the addition of identification information to the segment routing header provided in this application embodiment;

[0065] Figure 8 Another schematic diagram illustrating the addition of identification information to the segment routing header provided in this application embodiment;

[0066] Figure 9 Another flowchart of a service processing method for a computing power network provided in an embodiment of this application;

[0067] Figure 10 A structural diagram of the service processing device 1000 for a computing network provided in this application embodiment;

[0068] Figure 11 A structural diagram of the service processing device 1100 for the computing power network provided in this application embodiment;

[0069] Figure 12 A schematic diagram of a service processing system for a computing power network provided in an embodiment of this application;

[0070] Figure 13 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0071] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0072] The terms "first" and "second" in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. The term "multiple" in this application can mean at least two, for example, two, three, or more, and is not limited by the embodiments of this application.

[0073] A computing power network is a network architecture that deeply integrates computing power and networks, connecting widely distributed computing resources through a network. Specifically... Figure 1 As shown, a computing network comprises three levels of computing resources: cloud computing nodes, edge computing nodes, and terminal computing nodes. Terminal computing nodes include terminal devices such as mobile phones, computers, and laptops; edge computing nodes include computing nodes in wireless access networks (such as base stations) and computing nodes in Passive Optical Networks (PONs) (such as routing equipment and operator servers). In practical applications, the architecture of a computing network can include more or fewer levels of computing resources, and each level of computing nodes can employ different implementation methods.

[0074] In a computing network, scheduling computing applications to the optimal computing nodes improves user experience and optimizes computing and network resource utilization. However, network and computing resources change in real time, causing the optimal computing nodes to change as well. If a business flow's data is distributed across different servers for processing, it can lead to business interruptions.

[0075] Therefore, the computing power networks in related technologies require routing devices to maintain a session table to record the mapping relationship between service flows and servers. Both ingress and egress routing devices make routing decisions based on the service identifier (D-SID). Ingress routing devices connect to local users, and the number of their session tables is controllable. However, egress routing devices connect to servers, and all access to that service is recorded in the session table. This leads to egress devices consuming significant forwarding resources to maintain the session tables. Furthermore, during the convergence of the computing power routing control plane due to fluctuations in computing power information, the computing power resource information of the ingress and egress routing devices may become asynchronous, leading to loop problems.

[0076] Specifically, such as Figure 2As shown, after receiving a customer's service processing request, the ingress routing device obtains the first service required by the customer, and based on the computing and network resources of the computing network, determines the optimal target service instance (i.e., ...) from among the numerous service instances that can provide the first service. Figure 2 The example shown is Service Instance 1. Since this service instance is located at egress routing device 1, data packets used for service processing are sent to this egress routing device. When egress routing device 1 receives the packet, it needs to re-evaluate the current computing and network resources. If, at this moment, fluctuations in computing power information cause convergence of the computing power routing control plane, asynchrony of computing power resources may occur. That is, the optimal computing power node determined by egress routing device 1 at this time might be Service Instance 4 located at egress routing device 2. This inconsistency in decision-making results creates a loop problem, subsequently preventing service processing.

[0077] To address the aforementioned issues, the inventive concept of this application is as follows: After obtaining a first service based on customer demand, a target service instance for processing customer business is determined based on this first service. Then, the identification information of the target service instance is added to the data packet and sent to the corresponding egress routing device. This process only requires the ingress routing device to make decisions; the egress routing device directly instructs the service instance to process the data packet based on the identification information carried in the packet, thereby resolving the loop problem that may arise from simultaneous decisions by both ingress and egress routing devices. Furthermore, since the egress routing device does not need to make decisions, it does not need to maintain session entries mapping business flows to servers, thus effectively reducing the forwarding resource requirements of the egress routing device.

[0078] Next, as follows Figure 3 As shown, Figure 3 This application provides an embodiment of a service processing method for a computing network, which includes the following steps:

[0079] Step 301: Determine the target service instance corresponding to the first service accessed by the client; wherein, the first service is provided by the computing power network;

[0080] As mentioned above Figure 2 As shown, the ingress routing device is connected to a client. When a client has a business need, such as logging into an application or downloading a video, it sends a business processing request to the ingress routing device. This request carries the first service requested by the client. Taking the application login example, this first service is the service provided by that application.

[0081] The computing network in this application embodiment includes multiple routing devices that connect to at least one server used to provide services. For example... Figure 4 The computing network shown contains multiple routing devices, some of which (such as...) Figure 4The routing device shown 1) connects only to clients, while some routing devices connect both clients and servers (e.g., Figure 4 The routing device shown is 2), and some routing devices can only connect to servers (such as...). Figure 4 The routing device 3 shown above. The purpose of the aforementioned step 301 is to select, based on the first service required by the customer and in combination with the computing power resource information of the server corresponding to each routing device and the network parameter information of each routing device, a service instance located on different routing devices to process data packets in response to the client's business processing request.

[0082] by Figure 4 To illustrate step 301 above, let's assume that client 1, connected to routing device 1, sends a service processing request to routing device 1. In this case, routing device 1 acts as the entry routing device for the request. Routing device 1 will obtain the computing resource information of the servers corresponding to each routing device in the computing power network, as well as the network parameter information of each routing device. Specifically, it will obtain the computing resource information of the servers corresponding to routing devices 2 and 3, and the network parameter information of routing devices 2 and 3 themselves. The computing resource information may include the remaining computing power and processor utilization of the servers connected to the routing devices, while the network parameter information will at least include network parameters such as the network bandwidth and latency of the routing devices.

[0083] Then, based on the acquired computing resource information and network parameter information, a target service instance is selected from the service instances under the first service in each routing device. For example, assuming the first service requested by the customer is service 2, routing device 1 can pre-select routing devices 2 and 3, which are connected to the server corresponding to service 2. Then, combining the aforementioned computing resource information and network parameter information, service instance 4 located in routing device 3 is determined as the optimal computing node. At this time, routing device 3, where service instance 4 is located, is designated as the egress router corresponding to this request. That is, service instance 4 is taken as the target service instance of this request.

[0084] Step 302: Encapsulate the identification information of the target service instance in a data packet from the client;

[0085] Internet Protocol version 6 (IPv6) specifies various extension headers, such as the Hop-by-Hop Options header, Destination Options header, and Segment Routing header. The presence of IPv6 extension headers can provide additional information to packets. Based on this, this application embodiment can pre-check whether a data packet has an IPv6 extension header before adding the target service instance identification information (i.e., D-BID) to the data packet. If an IPv6 extension header does not exist, it can be added to the data packet to carry the target service instance identification information (D-BID).

[0086] One possible implementation is to add a Destination Options Header (DOH) to the data packet, and use identification information as custom options within the DOH header. Specifically, as follows... Figure 5 As shown, the destination option header can carry multiple options, and the option format is typically Type-Length-Value (TLV). In implementation, the destination option header can be structured as follows: Figure 6 The TLV format options shown define the type (BID Type) and length (BID Len) of the target service instance's identification information. The target service instance's identification information, i.e., D-BID, is added as a custom option content (value).

[0087] Another possible implementation is to add a Segment Routing Header (SRH) to the datagram, using identification information as the first type length value of the SRH. Specifically, the SRH contains a first TLV that functions similarly to the options in the destination options header. This can be implemented as follows: Figure 7 As shown, by defining the type (SRH TLV Type) and length (SRH TLV Len) of the identification information of the target service instance, for example, defining the type (SRH TLV Type) as the first value (BID-Type), and adding D-BID as the value (content) of the first TLV. Furthermore, considering that the segment routing header also carries a segment list (SRH segment list) for recording paths, in implementation, this identification information can be added to the end of the path indicated by the segment list, so that the data packet carries this identification information.

[0088] Correspondingly, if the data packet already carries a segment routing header or a destination option header, there is no need to add a new extension header. Instead, identification information can be added to the header using the methods described above for adding segment routing headers or destination option headers.

[0089] It should also be noted that while the above examples provide various methods for adding identification information, in practical applications, rules for adding identification information must be predefined. After the egress routing device receives the data packet, it must parse the data packet using the corresponding parsing rules to obtain the identification information. For example, the data packet may already contain a segment routing header but not a destination option header. If the pre-defined rules require adding identification information via the destination option header, then even if the data packet contains a segment routing header, a destination option header must still be added to carry the identification information of the target service instance.

[0090] For example, routing devices in a computing network can pre-determine or configure the type (Type) value of the TLV in the segment routing header to be a second value (BID Type), which indicates that the TLV contains the identification information of the target service instance, that is, the TLV is the first TLV mentioned above.

[0091] Alternatively, for example, routing devices (ingress routing devices and egress routing devices) in a computing power network can pre-define or configure the type value of the option in the destination option header to be a second value (BID Type), which indicates that the option contains identification information of the target service instance.

[0092] Step 303: Send the data packet to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet;

[0093] After adding the identification information of the target service instance to the data packet through the aforementioned step 302, the data packet needs to be sent to the egress routing device corresponding to the target service instance so that the egress routing device can instruct the target service instance to perform business processing on the customer based on the identification information.

[0094] The above process requires only the ingress routing device to make decisions. The egress routing device directly instructs the target service instance to process the data packet based on the identification information carried in the packet, in response to the client's service processing request. This resolves the loop problem that may arise from simultaneous decisions by both ingress and egress routing devices. Furthermore, since the egress routing device does not need to make decisions, it does not need to maintain session entries mapping service flows to servers, thus effectively reducing the forwarding resource requirements of the egress routing device.

[0095] The following describes the processing flow of the outbound routing equipment, as follows: Figure 8 As shown, Figure 8 This application provides an embodiment of a service processing method for a computing network, which includes the following steps:

[0096] Step 801: Receive data packets sent by the ingress routing device, and parse the data packets to obtain the identification information of the target service instance;

[0097] As mentioned in step 302 above, in this embodiment of the application, the identification information of the target service instance can be added to the destination option header or segment routing header. Specifically, the rules for adding the identification information can be predefined. After the egress routing device receives the data packet, it uses the corresponding parsing rules to parse the data packet to obtain the identification information.

[0098] Specifically, if identification information is added through the destination option header, the custom option content carried in the destination option header can be obtained by parsing the destination option header of the data packet. Then, the identification information can be determined based on the custom option content.

[0099] If identification information is added via the TLV field of the segment routing header, the type length value of the segment routing header can be obtained by parsing the segment routing header of the data packet. The identification information can then be determined based on the type length value.

[0100] If identification information is added using the segment list in the segment routing header, the segment list can be obtained by parsing the segment routing header of the data packet. The identification information can then be determined based on the path indicated by the segment list.

[0101] Step 802: Determine the indication address of the data packet based on the identification information, and send the data packet to the indication address so that the target service instance can process the data packet.

[0102] It should be noted that some current solutions utilize a centralized Dyncast architecture to make decisions solely based on the ingress routing device. Specifically, for example... Figure 9 As shown, by converting the destination address of the message sent by the ingress routing device from the address information of the service (D-SID) to the address information of the optimal computing power node (i.e., the target service instance D-BID), this scheme only needs to make decisions at the ingress routing device, which can solve the loop problem that may be caused by simultaneous decision-making.

[0103] However, the return traffic received by the ingress routing device needs to be converted from D-BID to D-SID to maintain consistency with the source and destination addresses of the outbound traffic. This conversion directly increases the complexity of the ingress device. Furthermore, the data packets sent by the ingress routing device in the above process do not carry service address information, preventing the egress routing device from obtaining the service address from the packets. This prevents the egress routing device from customizing its return traffic processing strategy, thus compromising the customer's service experience.

[0104] In this embodiment, after obtaining the identification information of the target service instance, the identification information is used as the indication address of the data packet. The data packet is then sent to the indication address so that the target service instance at the indication address can process the client's business. Specifically, this application does not replace the original destination address carried in the data packet with the target service instance, but instead adds the identification information of the target service instance to the extended header of the data packet. In this way, it is only necessary to configure the egress routing device to not directly forward the data packet to the destination address when receiving the data packet, but instead forward it to the target service instance indicated by the identification information. The target service instance can then process the data packet to respond to the client's business processing request.

[0105] In the above process of this application, the ingress device does not need to convert the return traffic, and since the process does not change the destination address of the data packet, the egress network device can still obtain the address of the first service from the data packet, thereby supporting the setting of custom processing policies for the return traffic, thereby improving the customer's business experience.

[0106] Based on the same inventive concept, this application also provides a service processing device 1000 for a computing power network, specifically as follows: Figure 10 As shown, it includes:

[0107] Instance selection module 101 is configured to determine the target service instance corresponding to the first service accessed by the client.

[0108] The information encapsulation module 102 is configured to encapsulate the identification information of the target service instance in a data packet from the client;

[0109] The message forwarding module 103 is configured to perform the action of sending the data packet to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet.

[0110] In some possible embodiments, the process of encapsulating the identification information of the target service instance in a data packet from the client is performed, wherein the information encapsulation module is configured to:

[0111] Add the identification information of the target service instance to the IPv6 extension header of the data packet.

[0112] In some possible embodiments, the IPv6 extension header of the data packet includes a target option header, which includes first option content carrying the identification information.

[0113] In some possible embodiments, the IPv6 extension header of the data packet includes a segment routing header, which includes a first type length value (TLV) and the first TLV includes identification information of the target service instance.

[0114] In some possible embodiments, the IPv6 extension header of the datagram includes a segment routing header, which includes a segment list, with the identification information located at the end of the path indicated by the segment list.

[0115] In some possible embodiments, the computing power network includes multiple routing devices connected to servers for providing the first service;

[0116] The instance selection module is configured to execute the target service instance corresponding to the first service accessed by the client, and the execution is performed as follows:

[0117] Obtain the computing power resource information of the server corresponding to each routing device in the computing power network and the network parameter information of each routing device; wherein, the network parameter information includes at least the network latency and bandwidth of the routing device;

[0118] Based on the computing power resource information and the network parameter information, the target service instance is selected from each service instance under the first service in each routing device.

[0119] Based on the same inventive concept, this application also provides a service processing device 1100 for a computing power network, specifically as follows: Figure 11 As shown, it includes:

[0120] The message parsing module 111 is configured to receive data packets sent by the ingress routing device and parse the data packets to obtain the identification information of the target service instance;

[0121] The service processing module 112 is configured to determine the indication address of the data packet based on the identification information, and send the data packet to the indication address so that the target service instance processes the data packet.

[0122] In some possible embodiments, the identification information is obtained by parsing in the following manner:

[0123] Method 1: Parse the destination option header of the data packet to obtain the custom option content carried by the destination option header; determine the identification information based on the custom option content;

[0124] Method 2: Parse the segment routing header of the data packet to obtain the type length value of the segment routing header; determine the identification information based on the type length value;

[0125] Method 3: Parse the segment routing header of the data packet to obtain the segment list of the segment routing header; determine the identification information according to the path indicated by the segment list.

[0126] Based on the same inventive concept, embodiments of this application also provide a service processing system for a computing power network, specifically as follows: Figure 12 As shown, it includes an ingress routing device 1201 and an egress routing device, wherein:

[0127] The ingress routing device 1201 is configured to: determine the target service instance corresponding to the first service accessed by the client, and encapsulate the identification information of the target service instance in a data packet from the client;

[0128] The data packet is sent to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet.

[0129] The outbound routing device 1202 is configured to: receive data packets sent by the inbound routing device, and parse the data packets to obtain the identification information of the target service instance;

[0130] The indication address of the data packet is determined based on the identification information, and the data packet is sent to the indication address so that the target service instance processes the data packet.

[0131] In some possible embodiments, the above-described service processing system further includes a computing power parameter collection unit 1203, a network parameter collection unit 1204, and a comprehensive decision-making unit 1205, wherein:

[0132] Specifically, such as Figure 12 As shown, the computing power network includes multiple routing devices connected to servers. The computing power parameter collection unit 1203 is used to collect computing power resource information of each server connected to each routing device, and the network parameter collection unit 1204 is used to collect network parameter information of the routing devices.

[0133] The computing power parameter collection unit 1203 and the network parameter collection unit 1204 send the collected computing power resource information and network parameter information to the integrated decision-making unit 1205, enabling the integrated decision-making unit 1205 to select the optimal service instance (i.e., target service instance) and network path for the service request based on the collected information. Thus, the ingress routing device 1201 can forward data packets based on the target service instance selected by the integrated decision-making unit 1205.

[0134] The following reference Figure 13 To describe an electronic device 130 according to this embodiment of the present application. Figure 13 The electronic device 130 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0135] like Figure 13 As shown, the electronic device 130 is presented in the form of a general-purpose electronic device. The components of the electronic device 130 may include, but are not limited to: at least one processor 131, at least one memory 132, and a bus 133 connecting different system components (including memory 132 and processor 131).

[0136] Bus 133 represents one or more of several bus structures, including a memory bus or memory controller, peripheral bus, processor, or local bus using any of the various bus structures.

[0137] The memory 132 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 1321 and / or cache memory 1322, and may further include read-only memory (ROM) 1323.

[0138] The memory 132 may also include a program / utility 1325 having a set (at least one) of program modules 1324, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0139] Electronic device 130 can also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), and with one or more devices that enable a user to interact with electronic device 130, and / or with any device that enables electronic device 130 to communicate with one or more other electronic devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 135. Furthermore, electronic device 130 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 136. As shown, network adapter 136 communicates with other modules used in electronic device 130 via bus 133. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0140] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 132 including instructions, which can be executed by the processor 131 of the aforementioned device to perform the aforementioned method. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0141] In an exemplary embodiment, a computer program product is also provided, including a computer program / instructions that, when executed by a processor 131, implement any of the methods in the service processing method of a computing power network provided in this application.

[0142] In an exemplary embodiment, various aspects of the service processing method for a computing network provided in this application can also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to cause the computer device to perform the steps in the service processing method for a computing network according to various exemplary embodiments of this application described above.

[0143] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0144] The program product for service processing in computing networks according to the embodiments of this application can be a portable compact disc read-only memory (CD-ROM) and include program code, and can run on an electronic device. However, the program product of this application is not limited thereto. In this document, the readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0145] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. This propagated data signal may take many forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0146] The program code contained on the readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wired, fiber optic, RF, etc., or any suitable combination thereof.

[0147] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as Java or similar languages. The program code can execute entirely on the user's electronic device, partially on the user's device, as a standalone software package, partially on the user's electronic device and partially on a remote electronic device, or entirely on a remote electronic device or server. In cases involving remote electronic devices, the remote electronic device can be connected to the user's electronic device via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external electronic device (e.g., via the Internet using an Internet service provider).

[0148] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0149] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0150] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0151] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable image scaling device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable image scaling device, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0152] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable image scaling device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0153] These computer program instructions can also be loaded onto a computer or other programmable image scaling device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0154] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0155] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A service processing method for a computing power network, characterized in that, Applied to an ingress routing device, the method includes: Determine the target service instance corresponding to the first service accessed by the client, wherein the first service is provided by the computing power network; The identification information of the target service instance is encapsulated in a data packet from the client; The data packet is sent to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet. The step of encapsulating the identification information of the target service instance in a data packet from the client includes: The identification information of the target service instance is added to the Internet Protocol version 6 (IPv6) extension header of the data packet.

2. The method according to claim 1, characterized in that, The IPv6 extension header of the data packet includes a target option header, which includes a first option carrying the identification information.

3. The method according to claim 1, characterized in that, The IPv6 extension header of the data packet includes a segment routing header, which includes a first type length value (TLV) and the first TLV includes the identification information of the target service instance.

4. The method according to claim 1, characterized in that, The IPv6 extension header of the data packet includes a segment routing header, which includes a segment list, and the identification information is located at the end of the path indicated by the segment list.

5. The method according to any one of claims 1-4, characterized in that, The computing power network includes multiple routing devices, which are connected to servers that provide the first service. The determination of the target service instance corresponding to the first service accessed by the client includes: Obtain the computing power resource information of the server corresponding to each routing device in the computing power network and the network parameter information of each routing device; wherein, the network parameter information includes at least the network latency and bandwidth of the routing device; Based on the computing power resource information and the network parameter information, the target service instance is selected from each service instance under the first service in each routing device.

6. A service processing method for a computing power network, characterized in that, Applied to outbound routing equipment, the method includes: Receive data packets sent by the ingress routing device, and parse the data packets to obtain the identification information of the target service instance; The indication address of the data packet is determined based on the identification information, and the data packet is sent to the indication address to enable the target service instance to process the data packet; the Internet Protocol version 6 (IPv6) extension header of the data packet contains the identification information of the target service instance.

7. The method according to claim 6, characterized in that, The identification information is obtained by parsing in the following way: Method 1: Parse the destination option header of the data packet to obtain the custom option content carried by the destination option header; determine the identification information based on the custom option content; Method 2: Parse the segment routing header of the data packet to obtain the type length value of the segment routing header; determine the identification information based on the type length value; Method 3: Parse the segment routing header of the data packet to obtain the segment list of the segment routing header; determine the identification information according to the path indicated by the segment list.

8. A service processing device for a computing power network, characterized in that, The device includes; The instance selection module is configured to determine the target service instance corresponding to the first service accessed by the client. The information encapsulation module is configured to encapsulate the identification information of the target service instance in a data packet from the client; The step of encapsulating the identification information of the target service instance in a data packet from the client includes: Add the identification information of the target service instance to the Internet Protocol version 6 (IPv6) extension header of the data packet; The message forwarding module is configured to send the data packet to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device can process the data packet.

9. A service processing device for a computing power network, characterized in that, The device includes: The message parsing module is configured to receive data packets sent by the ingress routing device and parse the data packets to obtain the identification information of the target service instance; The service processing module is configured to determine the indication address of the data packet based on the identification information, and send the data packet to the indication address so that the target service instance can process the data packet; the Internet Protocol version 6 (IPv6) extension header of the data packet contains the identification information of the target service instance.

10. An electronic device, characterized in that, include: Memory, used to store program instructions; A controller is configured to invoke program instructions stored in the memory and execute the method of any one of claims 1-7 according to the obtained program instructions.

11. A computer program product, characterized in that, The computer program product includes: computer program code, which, when run on a computer, causes the computer to perform the method as described in any one of claims 1-7.

12. A service processing system for a computing power network, characterized in that, The system includes an ingress routing device and an egress routing device, wherein: The ingress routing device is configured to: determine the target service instance corresponding to the first service accessed by the client, and encapsulate the identification information of the target service instance in a data packet from the client; The data packet is sent to the egress routing device corresponding to the target service instance, so that the target service instance of the egress routing device processes the data packet. The step of encapsulating the identification information of the target service instance in a data packet from the client includes: Add the identification information of the target service instance to the Internet Protocol version 6 (IPv6) extension header of the data packet; The outbound routing device is configured to: receive data packets sent by the inbound routing device, and parse the data packets to obtain the identification information of the target service instance; The indication address of the data packet is determined based on the identification information, and the data packet is sent to the indication address to enable the target service instance to process the data packet; the Internet Protocol version 6 (IPv6) extension header of the data packet contains the identification information of the target service instance.

Images