Computing power routing method and device, routing node, node and client equipment

Abstract

The invention provides a computing power routing method and device, a routing node, a node and client equipment, and relates to the technical field of communication, the computing power routing method is applied to a first routing node, and the method comprises the following steps: receiving a first message sent by a second routing node; performing de-encapsulation processing on the first message to obtain a second message and a first segment of routing identifier SID; determining a local first target node connected with the first routing node according to the first SID; the second message is sent to the first target node; wherein the first routing node is a first hop provider edge (PE) routing node of the first target node access network; the first target node is a first edge computing MEC device or a first computing power service node. According to the scheme of the invention, the problem of routing chaos in a distributed scene can be avoided, and the problems of multi-point decision and inconsistent routing states are further avoided.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a computing power routing method, device, routing node, node and client device. Background Art

[0002] In the existing computing power routing mechanism, the Border Gateway Protocol (BGP) is used to support the notification of computing power information. The purpose of the computing power network is to jointly schedule the computing network to find a suitable service node (a suitable service node is a service node that is close to the user and has sufficient computing resources). On the one hand, it meets the user's business needs, and on the other hand, it optimizes the use of network and computing power resources.

[0003] In the existing distributed computing power routing mechanism, multiple routing nodes in the network can support serviceID1, and serviceID1 (an anycast) route is spread in the network (currently there are many means, and it has not converged yet). The ingress node integrates the network and computing power conditions (monitors the computing power and latency of several candidate nodes) to generate a forwarding table entry for serviceID1. For example, one of the candidate tunnels reaching R6 and R14 is selected. Ingress1 (for example, R1) receives a message with a destination address (DA) of serviceID1 and enters the tunnel according to the aforementioned table entry. However, the above-mentioned distributed computing power routing mechanism has the problems of multiple decision-making points and inconsistent routing status, which leads to continuous traffic jumping in the network and routing confusion. Summary of the invention

[0004] The technical solution of the present invention aims to provide a computing power routing method, device, routing node, server and client device to solve the problem of routing confusion in the existing distributed computing power routing mechanism.

[0005] In order to solve the above technical problems, the embodiments of the present invention provide the following technical solutions:

[0006] In a first aspect, an embodiment of the present invention provides a computing power routing method, which is applied to a first routing node, and the method includes:

[0007] Receiving a first message sent by a second routing node;

[0008] Decapsulate the first message to obtain a second message and a first segment routing identifier SID;

[0009] Determine, according to the first SID, a local first target node connected to the first routing node;

[0010] Sending the second message to the first target node;

[0011] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0012] The first target node is a first mobile edge computing MEC device or a first computing power service node.

[0013] Optionally, the first SID is a SID associated with target information, and the target information is used to instruct the first routing node to send the second message to a local MEC device or computing power service node.

[0014] Optionally, determining, according to the first SID, a local first target node to which the first routing node is connected includes:

[0015] Determine, according to the target information corresponding to the first SID, a local node connected to the first routing node;

[0016] Determine the first target node from the local nodes;

[0017] The local node is a local MEC device or a local computing service node.

[0018] Optionally, the receiving a first message sent by the second routing node includes:

[0019] Sending the first SID to the second routing node;

[0020] Receive the first message after the second routing node encapsulates the second message according to the first SID.

[0021] Optionally, sending the first SID to the second routing node includes:

[0022] Sending Border Gateway Protocol (BGP) routing attribute information to the second routing node, where the BGP routing attribute information carries the first SID.

[0023] Optionally, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

[0024] In a second aspect, an embodiment of the present invention further provides a computing power routing method, which is applied to a second routing node, and the method includes:

[0025] Sending a first message to a first routing node, where the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection;

[0026] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0027] The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0028] Optionally, sending a first message to a first routing node includes:

[0029] receiving the first SID sent by the first routing node;

[0030] receiving a second message sent by the first client device;

[0031] encapsulate the second message according to the first SID to obtain the first message;

[0032] Send the first message to the first routing node.

[0033] Optionally, receiving the first SID sent by the first routing node includes:

[0034] Receive routing attribute information of Border Gateway Protocol BGP sent by the first routing node, where the BGP routing attribute information carries the first SID.

[0035] Optionally, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

[0036] In a third aspect, an embodiment of the present invention further provides a computing power routing method, which is applied to a first target node, and the method includes:

[0037] receiving a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for the first target node to access a network; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried in the first message;

[0038] Determine a first client device according to the second message;

[0039] Establishing a first connection with the first client device, where the first connection is a connection between a server in the first target node and the first client device;

[0040] Sending a third message to the first client device through the first connection, where the third message is used to instruct the first client device to establish a second connection, where the second connection is a connection between the first client device and a server in the first target node;

[0041] Among them, the first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0042] Optionally, the third message carries a unicast address corresponding to a server in the first target node.

[0043] In a fourth aspect, an embodiment of the present invention further provides a computing power routing method, which is applied to a first client device, and the method includes:

[0044] receiving a third message sent by a server in a first target node through a first connection, where the first connection is a connection between the server in the first target node and the first client device; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried in the first message;

[0045] Establishing a second connection with the server in the first target node according to the third message;

[0046] Among them, the first target node is the first mobile edge computing MEC device or the first computing power service node.

[0047] Optionally, the third message carries a unicast address corresponding to a server in the first target node.

[0048] Optionally, before receiving the third message sent by the server in the first target node through the first connection, the method further includes:

[0049] Send a second message to the second routing node.

[0050] In a fifth aspect, an embodiment of the present invention further provides a computing power routing device, the device comprising:

[0051] A first receiving module, used to receive a first message sent by a second routing node;

[0052] A first processing module, configured to decapsulate the first message to obtain a second message and a first segment routing identifier SID;

[0053] A first determining module, configured to determine a local first target node to which the first routing node is connected according to the first SID;

[0054] A first sending module, used for sending the second message to the first target node;

[0055] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0056] The first target node is a first mobile edge computing MEC device or a first computing power service node.

[0057] In a sixth aspect, an embodiment of the present invention further provides a computing power routing device, the device comprising:

[0058] A second sending module, configured to send a first message to a first routing node, wherein the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection;

[0059] Wherein, the first routing node is a first-hop provider edge PE routing node of the first target node access network;

[0060] The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0061] In a seventh aspect, an embodiment of the present invention further provides a computing power routing device, the device comprising:

[0062] A second receiving module is used to receive a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for a first target node to access a network; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried in the first message;

[0063] A second determining module, configured to determine a first client device according to the second message;

[0064] A second processing module, configured to establish a first connection with the first client device, wherein the first connection is a connection between a server in the first target node and the first client device;

[0065] A third sending module, configured to send a third message to the first client device through the first connection, wherein the third message is used to instruct the first client device to establish a second connection, where the second connection is a connection between the first client device and a server in the first target node;

[0066] Among them, the first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0067] In an eighth aspect, an embodiment of the present invention further provides a computing power routing device, the device comprising:

[0068] A third receiving module is used to receive a third message sent by the server in the first target node through the first connection, where the first connection is a connection between the server in the first target node and the first client device; the first target node is a local node determined by the first routing node according to the first segment routing header SID carried by the first message;

[0069] A third processing module, configured to establish a second connection with the server in the first target node according to the third message;

[0070] Among them, the first target node is the first mobile edge computing MEC device or the first computing power service node.

[0071] In the ninth aspect, an embodiment of the present invention further provides a routing node, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the computing power routing method as described in any one of the first aspect is implemented, or the computing power routing method as described in any one of the second aspect is implemented.

[0072] In the tenth aspect, an embodiment of the present invention further provides a node, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, a computing power routing method as described in any one of the third aspects is implemented.

[0073] In the eleventh aspect, an embodiment of the present invention further provides a client device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, a computing power routing method as described in any one of the fourth aspects is implemented.

[0074] In the twelfth aspect, an embodiment of the present invention further provides a readable storage medium, on which a program is stored, and when the program is executed by a processor, the steps in the computing power routing method as described in any one of the first aspect are implemented, or the steps in the computing power routing method as described in any one of the second aspect are implemented, or the steps in the computing power routing method as described in any one of the third aspect are implemented, or the steps in the computing power routing method as described in any one of the fourth aspect are implemented.

[0075] At least one of the above technical solutions of the present invention has the following beneficial effects:

[0076] The computing power routing method provided by the solution of the present invention comprises the following steps: a first routing node receives a first message sent by a second routing node, decapsulates the first routing node, obtains the second message and the first SID, and determines the local first target node connected to the first routing node according to the first SID, thereby sending the second message to the local first target node; the first routing node is the first hop PE routing node for the first target node to access the network; the first routing node performs a local search according to the first SID to determine the local first target node, and forwards the message, thereby avoiding the problem of multi-point decision-making and inconsistent routing status caused by the first routing node performing a global search for other routing nodes after receiving the first message in a distributed scenario, forwarding the first message to the other found routing nodes, and then the other routing nodes performing global forwarding, thereby solving the problem of routing confusion in a distributed scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Figure 1 One of the schematic diagrams of the distributed computing power routing scenario provided by the present invention;

[0078] Figure 2 The second schematic diagram of the distributed computing power routing scenario provided by the present invention;

[0079] Figure 3 A flowchart of a computing power routing method applied to a first routing node provided in an embodiment of the present invention;

[0080] Figure 4 A schematic diagram of function information corresponding to Router1 provided in an embodiment of the present invention;

[0081] Figure 5 A schematic diagram of function information corresponding to Router3 provided in an embodiment of the present invention;

[0082] Figure 6 A schematic diagram of function information corresponding to Router5 provided in an embodiment of the present invention;

[0083] Figure 7 A schematic diagram of function information corresponding to Egress2 provided in an embodiment of the present invention;

[0084] Figure 8 A flowchart of a computing power routing method applied to a second routing node provided in an embodiment of the present invention;

[0085] Fig. 9 A flowchart of a computing power routing method applied to a first target node provided by an embodiment of the present invention;

[0086] Fig.10 A flowchart of a computing power routing method applied to a client device provided by an embodiment of the present invention;

[0087] Fig.11 A schematic diagram of the structure of a computing power routing system provided by an embodiment of the present invention;

[0088] Fig.12 A schematic diagram of the structure of a computing power routing device applied to a first routing node provided in an embodiment of the present invention;

[0089] Fig.13 A schematic diagram of the structure of a computing power routing device applied to a second routing node provided by an embodiment of the present invention;

[0090] Fig.14 A schematic diagram of the structure of a computing power routing device applied to a first target node provided by an embodiment of the present invention;

[0091] Fig.15 A schematic diagram of the structure of a computing power routing device applied to a client device provided by an embodiment of the present invention;

[0092] Fig.16 A schematic diagram of the structure of a first routing node provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0093] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0094] Before describing the specific implementation method, the following description is first given:

[0095] The core of the computing power routing mechanism is to expand the L3 load balancing (LB) at the Ingress node, supporting LB or anycast that considers computing power information, rather than just LB or anycast that considers traditional network distance.

[0096] Specifically, the core of the computing power routing mechanism includes: computing power registration, computing power nodes register in the network; computing power notification, computing power information is spread in the network; network status detection, entry nodes collect network status information; user request scheduling, the entry node decides which service node to forward user data to based on the collected computing power and network status.

[0097] In the distributed computing power routing scenario, such as Figure 1 and Figure 2As shown in the figure, it is necessary to sense the computing power information and network information at the Ingress node (Ingress1), and then select the Egress for a specific anycast address (service ID) (for example, the comprehensive decision selects the mobile edge computing (MEC, or multi-access edge computing (MEC)) MEC2), and then the Client (client device) accesses service1 in MEC2. Figure 1 As shown in the figure, the latency monitoring of Ingress1 usually involves periodically measuring the latency to the peer egress node (Egress), that is, Figure 1 RTT1, RTT2 and RTT3 in. Figure 2 As shown, the service load monitoring of Ingress1 can be to carry computing power status information or server load information through BGP.

[0098] The technical solution of the present invention aims to provide a computing power routing method, apparatus, routing node, node and client device to solve the problem of routing confusion in the existing distributed computing power routing mechanism.

[0099] like Figure 3 As shown, an embodiment of the present invention provides a computing power routing method, which is applied to a first routing node, and the method includes:

[0100] Step 301: Receive a first message sent by a second routing node.

[0101] The computing power routing method provided by the embodiment of the present invention is applied to Figure 2 In the computing power routing scenario shown, the second routing node is Ingress1.

[0102] Among them, the servers in MEC1, MEC2 and MEC3 all support a certain service ID. Three computing power node entries (computing power node entries of Egress1, Egress2 and Egress3) are established in Ingress1, and relevant computing power status information and network status information (server load information) are collected. The service load monitoring of Ingress1 can be to carry computing power status information or server load information through BGP.

[0103] Specifically, a computing power node table entry is established in Ingress1 to record the routing information of the computing power service node that uses itself as the egress node (Egress). These routing information are sent from the external access network and carry computing power related information (external computing power routing information notification). The Egress is the first hop provider edge (PE) router for these computing power service nodes to access the network. Specifically, the computing power service node can be an MEC, and the relevant computing power services can be deployed on the server or virtual server.

[0104] In this step, the first client device (Client1) sends a second message to Ingress1, and the second message includes the source address (Source Address, SA) clientIP and the destination address (serviceID) serviceID1 of Client1. Ingress1 uses the first segment routing identifier (Segment Routing ID, SID) to encapsulate the second message to obtain the first message. Specifically, the second message has an outer encapsulation, and the last SID is of END.DTCL6 type, and the first SID is the SID released in advance by Egress. The newly defined END.DTCL6 indicates to look up a local computing power service forwarding table after decapsulation, and the address also exists in the global routing table. Among them, D means decapsulation, T means table lookup, C represents the computing power service table, L represents Local, and 6 represents IPv6.

[0105] After Ingress1 receives the second message, it determines the SRv6 Policy (SRv6 policy) whose destination is Egress2 according to serviceID1 and the three computing node entries established in Ingress1, and forwards the first message to Egress2, where Egress2 is the first routing node. Egress2 is the first hop provider edge PE routing node for the first target node (the first target node is the first local MEC device or the first computing service node connected to the first routing node) to access the network. Egress2 receives the first message sent by the second routing node. The first message also includes the destination address serviceID1.

[0106] Exemplarily, the forwarding path of the first message is<Router1,Router3,Router5,Egress2> .

[0107] Specifically, during the forwarding process, the function (FUNCT) information corresponding to Router1 is as follows: Figure 4 As shown, the function (FUNCT) information corresponding to Router3 is as follows Figure 5As shown, the function (FUNCT) information corresponding to Router5 is as follows Figure 6 As shown, the function (FUNCT) information corresponding to Egress2 is as follows Figure 7 shown.

[0108] in, Figures 4 to 7 The information shown includes the virtual network (overlay): source address SA (clientIP) and destination address DA (serviceID). Figures 4 to 7 The same information is in Figures 4 to 7 The information shown also includes the physical layer network (underlay): the segment routing extension header SRH of the source address SA and the destination address DA, Figure 4 In the information shown, the SA in the underlay is Ingress1, and the DA in the underlay is Router1END. Figure 5 In the information shown, the SA in the underlay is Ingress1, and the DA in the underlay is Router3END. Figure 6 In the information shown, the SA in the underlay is Ingress1, and the DA in the underlay is Router5END. Figure 7 In the information shown, the SA in the underlay is Ingress1, and the DA in the underlay is Egress2END.DTCL6. Figures 4 to 7 The information shown also includes several END functions, namely: Egress2END.DTCL6, Router5END, Router3END, Router1END.

[0109] Figures 4 to 7 In the information of the local computing service table (LOC: FUNCT) of the segment routing based on IPv6 (SRv6), it is assumed that, for example, E2, R1, R3, and R5 are LOC, and specific function values ​​are set, such as 0000 represents END FUNCT and D300 represents END.DTCL6 FUNCT.

[0110] Step 302: Decapsulate the first message to obtain a second message and a first segment routing identifier SID.

[0111] In this step, Egress2 decapsulates the first message sent by Ingress1 to obtain a second message and the first SID.

[0112] Step 303: According to the first SID, determine a local first target node to which the first routing node is connected, where the first target node is a first MEC device or a first computing service node.

[0113] In this step, Egress2 determines that the decapsulated second message needs to be forwarded to the local first target node based on the decapsulated first SID. In this embodiment, taking the first target node as the first MEC device as an example, the first target node is MEC2, and it does not matter to whom the forwarding address corresponding to the destination address serviceID1 in the Global routing table is given.

[0114] Step 304: Send the second message to the first target node.

[0115] In this step, Egress2 forwards the second message to the first target node, namely MEC2.

[0116] Optionally, the first SID is a SID associated with target information, and the target information is used to instruct the first routing node to send the second message to a local MEC device or a local computing power service node.

[0117] In this embodiment, the target information is the newly defined function END.DTCL6, which is used to instruct the routing node to decapsulate the received message and look up the local computing service forwarding table. The local computing service forwarding table includes the local MEC device (or local computing service node) and the corresponding network status information, etc., where D means decapsulation, T means table lookup, C represents the computing service table, L represents Local, and 6 represents IPv6.

[0118] It should be noted that the END function is a common function in SRv6, mainly used for explicit paths. It has a series of extensions, such as END.DT4, which means to search for a certain IPv4 VPN instance routing table for forwarding after decapsulation.

[0119] In an optional embodiment of the present invention, the local first target node connected to the first routing node is determined according to the first SID, including: according to the target information corresponding to the first SID (i.e., END.DTCL6), searching the local computing power service forwarding table, determining the local node connected to Ingress1 (i.e., the local MEC device or the local computing power service node), and when the number of local nodes (i.e., the local MEC device or the local computing power service node) is greater than 1, determining the first MEC device or the first computing power service node with the best status from the local nodes according to the local computing power service forwarding table.

[0120] Among them, the network status information corresponding to MEC in the local computing power service forwarding table is announced by the local computing power routing information.

[0121] It should also be noted that, in an embodiment of the present invention, the first SID should be released in advance by Egress to other routing nodes in the network, that is, the first SID is sent in advance by Egress2 to Ingress1 (that is, the first routing node sends the first SID to the second routing node), Ingress1 performs an outer layer encapsulation on the second message according to the first SID to obtain the first message, and the last SID of the outer layer encapsulated segment routing extension header (Segment Routing Header, SRH) is the first SID, and Ingress1 sends the first message to Egress2.

[0122] Optionally, the first routing node sending the first SID to the second routing node includes:

[0123] The routing attribute information of the Border Gateway Protocol BGP is sent to the second routing node, and the routing attribute information of the BGP carries the first SID, that is, the first SID sent in advance by Egress2 to Ingress1 is sent through the routing attribute information of BGP.

[0124] Furthermore, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute (Path Attribute) information or a sub-TLV in a new BGP routing attribute (Path Attribute) (that is, the computing power information sub-TLV is a sub-TLV added in the BGP routing attribute information).

[0125] Specifically, different from the existing BGP Prefix-SID attribute [RFC9252] logic, in this embodiment, this SID is selected to be placed in the computing power information TLV instead of in the ordinary BGP Prefix-SID attribute, where the BGP Prefix-SID attribute [RFC9252] is a TLV specifically used to store the Segment ID of Segment Routing.

[0126] In this embodiment, optionally, the above-mentioned computing power information TLV is carried in the extended community attribute information of the Path Attribute of BGP or in a new BGP routing attribute, that is, in the scheme in which Egress2 sends the first SID to Ingress1 through the routing attribute information of BGP, a sub-TLV (sub-TLV, type=10) is added to the extended community attribute information in the routing attribute information or a new BGP routing attribute (Path Attribute), and the sub-TLV carries the first SID. The sub-TLV contains the SID information of the Egress, and the specific content is the same as the ordinary BGP Prefix-SID, for example, including Information sub-sub-TLV, etc. However, this computing power information sub-tlv does not affect the first SID when the nexthop (BGP next hop) is changed or transmitted across management domains, that is, it will not be deleted.

[0127] After Ingress1 receives the first SID corresponding to END.DTCL6, when forwarding the message of the computing service whose destination address is the anycast address (ServiceID), the first SID corresponding to END.DTCL6 is used as the last SID in the SID list in the matching SRv6 Policy.

[0128] An implementation of the embodiment of the present invention is as follows:

[0129] Egress notifies serviceID1 information through BGP messages. At this time, the relevant routing information is the anycast address serviceID1, and the relevant computing power information is placed in the extended community attribute or a new BGP routing attribute;

[0130] The Path Attributes field in the BGP UPDATE message can contain several different attributes, each of which is organized in TLV format.

[0131] Select the extended community attribute information (Extended Community, RFC4360) in the BGP routing attribute information as the bearer attribute of the computing power information (Attr.Type Code is 16: Extended Communities extended community attribute);

[0132] The subtype field is set to 0x0314, and the length, Flag field, and computing power sub-TLV are added. The computing power TLVs carried are all optional, such as computing power busy and idle information, accumulated delay information, etc. A new computing power information sub-TLV is defined here, type = 10, that is, a new computing power information sub-TLV is defined, which carries the information of function END.DTCL6.

[0133] or,

[0134] Select a new BGP routing attribute information as the bearer attribute of computing power information (Attr.Type Code is 50: Metadata Path Attribute Type metadata routing attribute type);

[0135] This attribute includes the Length length, the Flag field, and the computing power sub-TLV. The computing power sub-TLVs carried are all optional, such as computing power busy and idle information, accumulated delay information, etc. A computing power information sub-TLV is newly defined here, type = 10, that is, a new computing power information sub-TLV is newly defined, which carries the information of the function END.DTCL6.

[0136] It should be noted that for a computing service, there is only one Ingress and one Egress. However, for a PE node, even if it is the same computing service, it may be both the Ingress of a computing service and the Egress of another computing service.

[0137] like Figure 8 As shown, an embodiment of the present invention further provides a computing power routing method, which is applied to a second routing node, and the method includes:

[0138] Step 801: Send a first message to a first routing node, where the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node for a local connection;

[0139] Wherein, the first routing node is a first-hop provider edge PE routing node of the first target node access network;

[0140] The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0141] The computing power routing method provided by the embodiment of the present invention is applied to Figure 2 In the computing power routing scenario shown, the second routing node is Ingress1. The first target node is the first MEC device, namely MEC2.

[0142] In this step, Ingress1 determines the SRv6 Policy that is forwarded to Egress2 according to the DA serviceID1 in the first message and the computing node table entry established in Ingress1. Egress2 is the first routing node.

[0143] The first message is obtained by encapsulating the second message through a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection.

[0144] The first SID should be published in advance by Egress to other routing nodes in the network, that is, the first SID is sent in advance by Egress2 to Ingress1. In an optional embodiment of the present invention, sending a first message to the first routing node includes: Ingress1 receiving the first SID sent by Egress2, and Ingress1 receiving a second message sent by a first client device (Client1), encapsulating the second message using the first SID to obtain a first message, and Ingress1 sending the first message to Egress2. Specifically, the last SID of the outer encapsulation of the second message is the first SID, and the first SID is a SID of the END.DTCL6 type.

[0145] Optionally, Ingress1 receives the first SID sent by Egress2, including:

[0146] The routing attribute information of Border Gateway Protocol (BGP) sent by the first routing node is received, and the routing attribute information of BGP carries the first SID. That is, the first SID sent by Egress2 to Ingress1 in advance is sent through the routing attribute information of BGP.

[0147] Furthermore, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV in a new BGP routing attribute (Path Attribute) (that is, the computing power information sub-TLV is a sub-TLV added in the BGP routing attribute information).

[0148] Specifically, in the scheme where Egress2 sends the first SID to Ingress1 through BGP routing attribute information, a computing power information sub-TLV (sub-TLV, type=10) is added to the extended community attribute information in the routing attribute information, and the target sub-TLV carries the first SID. Alternatively, a computing power information sub-TLV (sub-TLV, type=10) is added to a new routing attribute information, and the computing power information sub-TLV carries the first SID.

[0149] like Fig. 9 As shown, an embodiment of the present invention further provides a computing power routing method, which is applied to a first target node, and the method includes:

[0150] Step 901: Receive a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for the first target node to access the network. The first target node is a local node determined by the first routing node according to the first segment routing header SID carried by the first message; the first target node is a local first mobile edge computing MEC device or a first computing service node connected to the first routing node.

[0151] The computing power routing method provided by the embodiment of the present invention is applied to Figure 2 In the computing power routing scenario shown, the second routing node is Ingress1, the first routing node is Egress2, and the first target node is the first MEC device, namely MEC2.

[0152] The process of the first routing node generating the second message is as follows: Figure 3 The computing power routing method on the first routing node side is described in the figure and will not be repeated here.

[0153] The process of the first routing node determining the first target node in the local node according to the first segment routing header SID carried by the first message is also described in the computing power routing method on the first routing node side, which will not be repeated here. In this step, the server in MEC2 receives the second message sent by Egress2.

[0154] Step 902: Determine a first client device according to the second message.

[0155] In this step, server2 in MEC2 receives a second message, which carries a source address corresponding to the first client device (Client1), and MEC2 determines Client1 based on the source address.

[0156] Step 903: Establish a first connection with the first client device, where the first connection is a connection between a server in a first target node and the first client device.

[0157] That is, in this step, server2 in MEC2 establishes a first connection with Client1.

[0158] Step 904: Send a third message to the first client device through the first connection, where the third message is used to instruct the first client device to establish a second connection, where the second connection is a server connection between the first client device and the first target node.

[0159] After the first connection is established, in this step, the server in MEC2 sends a third message to Client1 through the first connection. Client1 establishes a second connection with the server in MEC2 according to the third message and continues subsequent services.

[0160] Optionally, the third message carries a unicast address corresponding to the server in the first MEC device.

[0161] That is, the third message carries the unicast address (serverIP2) of server2 in MEC2, for example, carried in the Server's Preferred Address of the Quick User Datagram Protocol (UDP) network connection (Quick UDP Internet Connection, QUIC), refer to RFC9000 for details.

[0162] Client1 initiates a second connection according to serverIP2 and continues subsequent services.

[0163] like Fig.10 As shown, an embodiment of the present invention further provides a computing power routing method, which is applied to a first client device, and the method includes:

[0164] Step 1001: Receive a third message sent by a first target node through a first connection, where the first connection is a connection between a server in the first target node and the first client device; the first target node is a local node determined by the first routing node based on a first segment routing header SID carried by the first message.

[0165] The computing power routing method provided by the embodiment of the present invention is applied to Figure 2 In the computing power routing scenario shown, the first target node is the first MEC device, namely MEC2.

[0166] It should be noted that the process of establishing the first connection is as described in the computing power routing method on the first target node side, and will not be repeated here.

[0167] The process of the first routing node determining the first target node in the local node according to the first segment routing header SID carried by the first message is also described in the computing power routing method on the first routing node side, and will not be repeated here.

[0168] In this step, the server in MEC2 sends a third message to the first client device (Client1) through the first connection, and the third message is used to instruct the first client device to establish a second connection.

[0169] Step 1002: Establish a second connection with a server in the first target node according to the third message, where the second connection is a connection between the first client device and the server of the target node.

[0170] In this step, Client1 establishes a second connection with MEC2 according to the third message and continues subsequent services.

[0171] Optionally, the third message carries a unicast address corresponding to the server in the first MEC device.

[0172] That is, the third message carries the unicast address (serverIP2) of server2 in MEC2, for example, carried in the Server's Preferred Address of the Quick User Datagram Protocol (UDP) network connection (Quick UDP Internet Connection) QUIC, refer to RFC9000 for details.

[0173] Optionally, before receiving a third message sent by the server in the first mobile edge computing MEC device through the first connection, the method further includes:

[0174] A second message is sent to the second routing node, Ingress1 receives the second message sent by the first client device (Client1), and encapsulates the second message using the first SID to obtain the first message. Ingress1 sends the first message to Egress2, and Egress2 decapsulates the first message to obtain the second message and the first segment routing identifier SID. Egress2 determines the first MEC device connected to Egress2 according to the first SID, and Egress2 sends the second message to the first MEC device. The server in the first MEC device determines the first client device according to the second message, and establishes a first connection with the first client device. The server in the first MEC device sends a third message to Client1 through the first connection.

[0175] In the embodiment of the present invention, after the message arrives at the Egress, the local computing power service forwarding table is queried through SRv6 network programming, thereby avoiding the routing inconsistency problem caused by inconsistent multi-point decisions in distributed scenarios, and the deployment of the computing power network can improve the efficiency of network transmission and service provision.

[0176] The computing power routing method provided by the embodiment of the present invention can enable the computing power network to avoid some routing confusion problems.

[0177] Combine the following Fig.11 , Fig.11 This is a schematic diagram of the structure of the computing power routing system provided in an embodiment of the present invention, which illustrates the overall process of the computing power routing method provided in an embodiment of the present invention:

[0178] The computing power routing system includes a first routing node, a second routing node, a first target node and a first client device.

[0179] The second routing node sends a first message to the first routing node, and the first message carries the first SID (wherein the first SID is sent by the first routing node to the second routing node in advance, and the first message is obtained by encapsulating the second message after the second routing node receives the first SID), and the target address of the first message is the serviceID corresponding to the first routing node. After receiving the first message, the first routing node decapsulates the first message to obtain the second message and the first SID. The first routing node searches the local table according to the first SID to determine the local node connected to the first routing node, and determines the first target node in the local node. point, the first routing node sends the second message to the first target node, the first target node receives the second message sent by the first routing node, the first target node determines the first client device according to the second message (the first client device is the client device that sends the second message to the second routing node), the first target node establishes a connection with the first client device, the server of the first target node sends a third message to the first client device through the first connection, the first client device receives the third message sent by the server in the first target node through the first connection and establishes a second connection with the server in the first target node according to the third message, and continues subsequent business.

[0180] like Fig.12 As shown, an embodiment of the present invention also provides a computing power routing device, which is applied to a first routing node, and the device includes:

[0181] The first receiving module 1201 is used to receive a first message sent by a second routing node;

[0182] A first processing module 1202 is used to decapsulate the first message to obtain a second message and a first segment routing identifier SID;

[0183] A first determining module 1203, configured to determine a local first target node to which the first routing node is connected according to the first SID;

[0184] A first sending module 1204, configured to send the second message to the first target node;

[0185] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0186] The first target node is a first mobile edge computing MEC device or a first computing power service node.

[0187] Optionally, the first SID is a SID associated with target information, and the target information is used to instruct the first routing node to send the second message to a local MEC device or computing power service node.

[0188] Optionally, the first determining module 1203 includes:

[0189] A first determining unit, configured to determine a local node to which the first routing node is connected according to the target information corresponding to the first SID;

[0190] A second determining unit, configured to determine the first target node from the local node;

[0191] The local node is a local MEC device or a local computing service node.

[0192] Optionally, the first receiving module 1201 includes:

[0193] A first sending unit, configured to send the first SID to the second routing node;

[0194] The first receiving unit is configured to receive the first message after the second routing node encapsulates the second message according to the first SID.

[0195] Optionally, the first sending unit is specifically configured to:

[0196] Sending Border Gateway Protocol (BGP) routing attribute information to the second routing node, where the BGP routing attribute information carries the first SID.

[0197] Optionally, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

[0198] It should be noted that the computing power routing device applied to the first routing node provided in the embodiment of the present invention is a device capable of executing the above-mentioned computing power routing method applied to the first routing node. All embodiments of the above-mentioned computing power routing method applied to the first routing node are applicable to the device and can achieve the same or similar technical effects.

[0199] like Fig.13 The embodiment of the present invention further provides a computing power routing device, which is applied to a second routing node, and the device includes:

[0200] The second sending module 1301 is used to send a first message to a first routing node, where the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection;

[0201] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0202] The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0203] Optionally, the second sending module 1301 includes:

[0204] A second receiving unit, configured to receive the first SID sent by the first routing node;

[0205] A third receiving unit, configured to receive a second message sent by the first client device;

[0206] A first processing unit, configured to encapsulate the second message according to the first SID to obtain the first message;

[0207] The second sending unit is used to send the first message to the first routing node.

[0208] Optionally, the second receiving unit is specifically configured to:

[0209] Receive routing attribute information of Border Gateway Protocol BGP sent by the first routing node, where the BGP routing attribute information carries the first SID.

[0210] Optionally, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

[0211] It should be noted that the computing power routing device applied to the second routing node provided in the embodiment of the present invention is a device capable of executing the above-mentioned computing power routing method applied to the second routing node. All embodiments of the above-mentioned computing power routing method applied to the second routing node are applicable to the device and can achieve the same or similar technical effects.

[0212] like Fig.14 As shown, an embodiment of the present invention further provides a computing power routing device, which is applied to a first target node, and the device includes:

[0213] The second receiving module 1401 is used to receive a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for the first target node to access the network; the first target node is a local node determined by the first routing node according to the first segment routing header SID carried by the first message;

[0214] A second determination module 1402, configured to determine a first client device according to the second message;

[0215] A second processing module 1403 is configured to establish a first connection with the first client device, where the first connection is a connection between a server in the first target node and the first client device;

[0216] A third sending module 1404 is used to send a third message to the first client device through the first connection, where the third message is used to instruct the first client device to establish a second connection, where the second connection is a connection between the first client device and the server in the first target node;

[0217] Among them, the first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0218] Optionally, the third message carries a unicast address corresponding to a server in the first target node.

[0219] It should be noted that the computing power routing device applied to the first mobile edge computing MEC device provided in an embodiment of the present invention is a device capable of executing the above-mentioned computing power routing method applied to the first mobile edge computing MEC device. All embodiments of the above-mentioned computing power routing method applied to the first mobile edge computing MEC device are applicable to the device and can achieve the same or similar technical effects.

[0220] like Fig.15 As shown, an embodiment of the present invention further provides a computing power routing device, which is applied to a first client device, and the device includes:

[0221] The third receiving module 1501 is used to receive a third message sent by the server in the first target node through the first connection, where the first connection is a connection between the server in the first target node and the first client device; the first target node is a local node determined by the first routing node according to the first segment routing header SID carried by the first message;

[0222] A third processing module 1502, configured to establish a second connection with the server in the first target node according to the third message;

[0223] Among them, the first target node is the first mobile edge computing MEC device or the first computing power service node.

[0224] Optionally, the third message carries a unicast address corresponding to a server in the first target node.

[0225] Optionally, the device further comprises:

[0226] The fourth sending module is used to send a second message to the second routing node.

[0227] It should be noted that the computing power routing device applied to the first client device provided in the embodiment of the present invention is a device capable of executing the above-mentioned computing power routing method applied to the first client device. All embodiments of the above-mentioned computing power routing method applied to the first client device are applicable to the device and can achieve the same or similar technical effects.

[0228] like Fig.16 As shown, an embodiment of the present invention further provides a routing node, which is a first routing node, including: a processor 1601; and a memory 1603 connected to the processor 1601 through a bus interface 1602, wherein the memory 1603 is used to store programs and data used by the processor 1601 when performing operations, and the processor 1601 calls and executes the programs and data stored in the memory 1603.

[0229] The transceiver 1604 is connected to the bus interface 1602 and is used to receive and send data under the control of the processor 1601. Specifically, the processor 1601 is used to read the program in the memory 1603, and the transceiver 1604 performs the following process:

[0230] Receiving a first message sent by a second routing node;

[0231] The processor 1601 performs the following processes:

[0232] Decapsulate the first message to obtain a second message and a first segment routing identifier SID;

[0233] Determine, according to the first SID, a local first target node connected to the first routing node;

[0234] The transceiver 1604 also performs the following process:

[0235] Sending the second message to the first target node;

[0236] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0237] The first target node is a first mobile edge computing MEC device or a first computing power service node.

[0238] Optionally, the first SID is a SID associated with target information, and the target information is used to instruct the first routing node to send the second message to a local MEC device or computing power service node.

[0239] Optionally, the processor 1601 is configured to:

[0240] Determine, according to the target information corresponding to the first SID, a local node connected to the first routing node;

[0241] Determine the first MEC device from the local node;

[0242] The local node is a local MEC device or a local computing service node.

[0243] Optionally, the transceiver 1604 is used for:

[0244] Sending the first SID to the second routing node;

[0245] Receive the first message after the second routing node encapsulates the second message according to the first SID.

[0246] Optionally, the transceiver 1604 is specifically used for:

[0247] Sending Border Gateway Protocol (BGP) routing attribute information to the second routing node, where the BGP routing attribute information carries the first SID.

[0248] Optionally, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

[0249] Among them, Fig.16In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1601 and memory represented by memory 1603. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides a user interface 1605. The transceiver 1604 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 1601 is responsible for managing the bus architecture and general processing, and the memory 1603 may store data used by the processor 1601 when performing operations.

[0250] An embodiment of the present invention also provides a routing node, which is a second routing node, including: a processor; and a memory connected to the processor through a bus interface, the memory being used to store programs and data used by the processor when performing operations, and the processor calling and executing the programs and data stored in the memory.

[0251] The transceiver is connected to the bus interface and is used to receive and send data under the control of the processor.

[0252] It should be noted that the second routing node provided in the embodiment of the present invention is Fig.16 The structure of the first routing node shown is similar and will not be repeated here.

[0253] Specifically, the processor is used to read the program in the memory, and the transceiver performs the following process:

[0254] Sending a first message to a first routing node, where the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection;

[0255] The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node;

[0256] The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0257] Optionally, the transceiver is used for:

[0258] receiving the first SID sent by the first routing node;

[0259] receiving a second message sent by the first client device;

[0260] The processor is used to:

[0261] encapsulate the second message according to the first SID to obtain the first message;

[0262] The transceiver is used for:

[0263] Send the first message to the first routing node.

[0264] Optionally, the transceiver is specifically used for:

[0265] Receive routing attribute information of Border Gateway Protocol BGP sent by the first routing node, where the BGP routing attribute information carries the first SID.

[0266] Optionally, the first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

[0267] An embodiment of the present invention also provides a node, which is a first target node, including: a processor; and a memory connected to the processor through a bus interface, the memory being used to store programs and data used by the processor when performing operations, and the processor calling and executing the programs and data stored in the memory.

[0268] The transceiver is connected to the bus interface and is used to receive and send data under the control of the processor.

[0269] It should be noted that the node provided by the embodiment of the present invention is Fig.16 The structure of the first routing node shown is similar and will not be repeated here.

[0270] Specifically, the processor is used to read the program in the memory, and the transceiver performs the following process:

[0271] receiving a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for the first target node to access the network; the first target node is a local node determined by the first routing node according to the first segment routing header SID carried by the first message; the processor performs the following process:

[0272] Determine a first client device according to the second message;

[0273] Establishing a first connection with the first client device, where the first connection is a connection between a server in the first target node and the first client device;

[0274] The transceiver also performs the following process:

[0275] Sending a third message to the first client device through the first connection, where the third message is used to instruct the first client device to establish a second connection, where the second connection is a connection between the first client device and a server in the first target node;

[0276] Among them, the first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

[0277] Optionally, the third message carries a unicast address corresponding to a server in the first target node.

[0278] An embodiment of the present invention also provides a client device, comprising: a processor; and a memory connected to the processor via a bus interface, the memory being used to store programs and data used by the processor when performing operations, and the processor calling and executing the programs and data stored in the memory.

[0279] The transceiver is connected to the bus interface and is used to receive and send data under the control of the processor.

[0280] It should be noted that the client device provided in the embodiment of the present invention is Fig.16 The structure of the first routing node shown is similar and will not be repeated here.

[0281] Specifically, the processor is used to read the program in the memory, and the transceiver performs the following process:

[0282] receiving a third message sent by a server in a first target node through a first connection, where the first connection is a connection between the server in the first target node and the first client device; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried by the first message;

[0283] The processor performs the following processes:

[0284] Establishing a second connection with the server in the first target node according to the third message;

[0285] Among them, the first target node is the first mobile edge computing MEC device or the first computing power service node.

[0286] Optionally, the third message carries a unicast address corresponding to a server in the first target node.

[0287] Optionally, the transceiver is further used for:

[0288] Send a second message to the second routing node.

[0289] In addition, a specific embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps of the computing power routing method applied to the first routing node as described above are implemented, or the steps of the computing power routing method applied to the second routing node as described above are implemented, or the steps of the computing power routing method applied to the first mobile edge computing MEC device as described above are implemented, or the steps of the computing power routing method applied to the first client device as described above are implemented.

[0290] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0291] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0292] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the sending and receiving methods described in various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0293] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary personnel in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A computing power routing method, characterized in that: Applied to a first routing node, the method comprises: Receiving a first message sent by a second routing node; Decapsulate the first message to obtain a second message and a first segment routing identifier SID; Determine, according to the first SID, a local first target node connected to the first routing node; Sending the second message to the first target node; The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node; The first target node is a first mobile edge computing MEC device or a first computing power service node.

2. The computing power routing method according to claim 1, characterized in that: The first SID is a SID associated with target information, and the target information is used to instruct the first routing node to send the second message to a local MEC device or computing power service node.

3. The computing power routing method according to claim 2, characterized in that: Determining, according to the first SID, a local first target node to which the first routing node is connected, includes: Determine, according to the target information corresponding to the first SID, a local node connected to the first routing node; Determine the first target node from the local nodes; The local node is a local MEC device or a local computing service node.

4. The computing power routing method according to claim 1, characterized in that: The receiving a first message sent by the second routing node includes: Sending the first SID to the second routing node; Receive the first message after the second routing node encapsulates the second message according to the first SID.

5. The computing power routing method according to claim 4, characterized in that: Sending the first SID to the second routing node includes: Sending Border Gateway Protocol (BGP) routing attribute information to the second routing node, where the BGP routing attribute information carries the first SID.

6. The computing power routing method according to claim 5, characterized in that: The first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

7. A computing power routing method, characterized in that: Applied to a second routing node, the method comprises: Sending a first message to a first routing node, where the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection; The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node; The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

8. The computing power routing method according to claim 7, characterized in that: Sending a first message to a first routing node includes: receiving the first SID sent by the first routing node; receiving a second message sent by the first client device; encapsulate the second message according to the first SID to obtain the first message; Send the first message to the first routing node.

9. The computing power routing method according to claim 8, characterized in that: Receiving the first SID sent by the first routing node includes: Receive routing attribute information of Border Gateway Protocol BGP sent by the first routing node, where the BGP routing attribute information carries the first SID.

10. The computing power routing method according to claim 9, characterized in that: The first SID is carried in a computing power information sub-TLV, and the computing power information sub-TLV is a sub-TLV added in the extended community attribute information of the BGP routing attribute information or a sub-TLV added in the BGP routing attribute information.

11. A computing power routing method, characterized in that: Applied to the first target node, the method comprises: receiving a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for the first target node to access a network; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried in the first message; Determine a first client device according to the second message; Establishing a first connection with the first client device, where the first connection is a connection between a server in the first target node and the first client device; Sending a third message to the first client device through the first connection, where the third message is used to instruct the first client device to establish a second connection, where the second connection is a connection between the first client device and a server in the first target node; Among them, the first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

12. The computing power routing method according to claim 11, characterized in that: The third message carries the unicast address corresponding to the server in the first target node.

13. A computing power routing method, characterized in that: Applied to a first client device, the method comprises: receiving a third message sent by a server in a first target node through a first connection, where the first connection is a connection between the server in the first target node and the first client device; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried in the first message; Establishing a second connection with the server in the first target node according to the third message; Among them, the first target node is the first mobile edge computing MEC device or the first computing power service node.

14. The computing power routing method according to claim 13, characterized in that: The third message carries the unicast address corresponding to the server in the first target node.

15. The computing power routing method according to claim 13, characterized in that: Before receiving the third message sent by the server in the first target node through the first connection, the method further includes: Send a second message to the second routing node.

16. A computing power routing device, characterized in that: The device comprises: A first receiving module, used to receive a first message sent by a second routing node; A first processing module, configured to decapsulate the first message to obtain a second message and a first segment routing identifier SID; A first determining module, configured to determine a local first target node to which the first routing node is connected according to the first SID; A first sending module, used for sending the second message to the first target node; The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node; The first target node is a first mobile edge computing MEC device or a first computing power service node.

17. A computing power routing device, characterized in that: The device comprises: A second sending module, configured to send a first message to a first routing node, wherein the first message carries a first segment routing header SID, and the first SID is used to instruct the first routing node to determine a first target node of a local connection; The first routing node is a first-hop provider edge PE routing node for accessing a network of the first target node; The first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

18. A computing power routing device, characterized in that: The device comprises: A second receiving module is used to receive a second message sent by a first routing node; the first routing node is a first-hop provider edge PE routing node for a first target node to access a network; the first target node is a local node determined by the first routing node according to a first segment routing header SID carried in the first message; A second determining module, configured to determine a first client device according to the second message; A second processing module, configured to establish a first connection with the first client device, wherein the first connection is a connection between a server in the first target node and the first client device; A third sending module, configured to send a third message to the first client device through the first connection, wherein the third message is used to instruct the first client device to establish a second connection, where the second connection is a connection between the first client device and a server in the first target node; Among them, the first target node is a local first mobile edge computing MEC device or a first computing power service node connected to the first routing node.

19. A computing power routing device, characterized in that: The device comprises: A third receiving module is used to receive a third message sent by the server in the first target node through the first connection, where the first connection is a connection between the server in the first target node and the first client device; the first target node is a local node determined by the first routing node according to the first segment routing header SID carried by the first message; A third processing module, configured to establish a second connection with the server in the first target node according to the third message; Among them, the first target node is the first mobile edge computing MEC device or the first computing power service node.

20. A routing node, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the computing power routing method according to any one of claims 1 to 6 is implemented, or the computing power routing method according to any one of claims 7 to 10 is implemented.

21. A node, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the computing power routing method as claimed in claim 11 or 12.

22. A client device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the computing power routing method as described in any one of claims 13 to 15 is implemented.

23. A readable storage medium, characterized in that: The readable storage medium stores a program, and when the program is executed by the processor, the program implements the steps in the computing power routing method according to any one of claims 1 to 6, or implements the steps in the computing power routing method according to any one of claims 7 to 10, or implements the steps in the computing power routing method according to claim 11 or 12, or implements the steps in the computing power routing method according to any one of claims 13 to 15.

Images