Packet transmission method, communication device, storage medium, and program product

Abstract

Embodiments of the present application provide a packet transmission method, a communication device, a storage medium, and a program product. The method comprises: receiving a computing network delivery policy and a first service packet from a physical client terminal device, wherein the computing network delivery policy is generated on the basis of computing power state information related to a service and network state information, and the first service packet carries a first service identifier used for representing the service type of the first service packet; and when determining, on the basis of the first service identifier, that a virtual client terminal device corresponding to the physical client terminal device is in a multi-cloud resource pool deployment mode, determining a first target cloud resource pool on the basis of the first service identifier and the computing network delivery policy, and forwarding the first service packet to the first target cloud resource pool.

Description

Message transmission method, communication device, storage medium and program product

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on and claims the priority of Chinese patent application with application number 2023106966679 and application date June 13, 2023. The entire content of the Chinese patent application is hereby incorporated into this application as a reference. Technical Field

[0003] The embodiments of the present application relate to the field of communication technology, and in particular to a message transmission method, communication equipment, storage medium, and program product. Background Art

[0004] In related technologies, computing-network integration has become a basic industry consensus and hot topic in the 5G (5th Generation) and post-5G eras. Under the network-centric computing-network addressing and routing solution, the network needs to select appropriate computing nodes from multiple service instances based on computing power status and network status. However, in the cross-cloud pool multi-instance deployment mode of computing nodes, the network conducts traffic diversion and addressing based on the computing-network status, and the traditional globally unique host address is no longer applicable. For example, in a scenario where the functions of customer premises equipment (CPE) are virtualized and deployed in a cloud-side resource pool, the virtualized CPE can be deployed in multiple edge cloud resource pools. Therefore, user access requests face the need to execute multiple strategies on demand between multiple cloud resource pools, such as load balancing. However, the Internet Protocol (IP) address obtained by the user terminal points to the virtual customer premises equipment (vCPE) on the cloud side. Therefore, the L3-based computing network integration scheduling and routing mechanism is not applicable to this scenario. The physical customer premises equipment (pCPE) on the user side always maintains an L2 layer connection with the cloud side vCPE.

[0005] Flexible network traffic diversion in L2 / L3 / L4 networking scenarios is crucial for cloud-based deployment scenarios like vCPE. For example, in a vCPE deployment scenario, the existing mechanism encapsulates user access requests into a specific tunnel based on the virtual LAN identifier, source and destination MAC (Media Access Control) addresses encapsulated in the user message, and, following pre-configured policies, forwards them to a fixed cloud-side gateway, which then forwards them to the corresponding vCPE. Therefore, under the existing mechanism, flexible scheduling of user access requests across multiple cloud resource pools is impossible.

[0006] Summary of the Invention

[0007] Embodiments of the present application provide a message transmission method, communication device, storage medium, and program product, which are intended to achieve flexible scheduling of user service messages between multi-cloud resource pools.

[0008] In a first aspect, an embodiment of the present application provides a message transmission method, including:

[0009] receiving a computing network traffic diversion strategy and a first service message from a physical client terminal device, wherein the computing network traffic diversion strategy is generated based on computing power status information and network status information related to the service, and the first service message carries a first service identifier for characterizing a service type of the first service message;

[0010] When the virtual customer terminal device corresponding to the physical customer terminal device is determined to be deployed in a multi-cloud resource pool according to the first service identifier, the first target cloud resource pool is determined according to the first service identifier and the computing network diversion strategy, and the first business message is forwarded to the first target cloud resource pool.

[0011] In a second aspect, an embodiment of the present application provides a message transmission method, including:

[0012] A first business message carrying a first service identifier is sent to a target gateway, so that the target gateway forwards the first business message to the first target cloud resource pool after determining the first target cloud resource pool based on the first service identifier and the received computing network diversion strategy; wherein the first service identifier is used to characterize the service type of the first business message, and the computing network diversion strategy is generated based on business-related computing power status information and network status information.

[0013] In a third aspect, an embodiment of the present application provides a message transmission method, including:

[0014] Obtaining computing power status information and network status information related to the business, and generating a computing network traffic diversion strategy based on the computing power status information and the network status information;

[0015] The computing network diversion strategy is sent to the target gateway so that the target gateway determines the first target cloud resource pool based on the computing network diversion strategy and the first service identifier of the received first business message, and then forwards the first business message to the first target cloud resource pool; wherein, the first service identifier is used to characterize the service type of the first business message.

[0016] In a fourth aspect, an embodiment of the present application provides a communication device, including:

[0017] at least one processor;

[0018] at least one memory for storing at least one program;

[0019] When at least one of the programs is executed by at least one of the processors, the message transmission method of the first aspect, the second aspect or the third aspect described above is executed.

[0020] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a program executable by a processor, and the program executable by the processor executes the message transmission method of the first aspect, the second aspect or the third aspect mentioned above when the processor is running.

[0021] In a sixth aspect, an embodiment of the present application provides a computer program product, comprising a computer program or computer instructions, wherein the computer program or the computer instructions are stored in a computer-readable storage medium, and a processor of a computer device reads the computer program or the computer instructions from the computer-readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device executes the message transmission method of the first aspect, the second aspect or the third aspect mentioned above.

[0022] According to the message transmission method, communication equipment, storage medium and program product provided by the embodiment of the present application, first, the embodiment of the present application will receive a computing network diversion strategy and a first business message from a physical client terminal device, wherein the computing network diversion strategy is generated based on the computing power status information and network status information related to the business, and the first business message carries a first service identifier for characterizing the service type of the first business message; then, the embodiment of the present application will determine the deployment method of the virtual client terminal device corresponding to the physical client terminal device based on the first service identifier; then, when the deployment method is a multi-cloud resource pool deployment, the embodiment of the present application will determine the first target cloud resource pool based on the first service identifier and the computing network diversion strategy, and forward the first business message to the first target cloud resource pool. For the multi-cloud resource pool deployment method, since the embodiment of the present application can select the corresponding first target cloud resource pool to divert the first business message based on the service type corresponding to the first business message and the computing power status and network status, it can achieve flexible scheduling of user business messages between multi-cloud resource pools. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG1 is a schematic diagram of a computing network traffic diversion architecture based on L2 service identification provided in an embodiment of the present application;

[0024] FIG2 is a schematic diagram of a network traffic diversion architecture based on L3 service identification provided in an embodiment of the present application;

[0025] FIG3 is a schematic diagram of a network traffic diversion architecture based on L4 service identification provided in an embodiment of the present application;

[0026] FIG4 is a flowchart of a message transmission method performed by a target gateway side according to an embodiment of the present application;

[0027] FIG5 is a specific flow chart of determining an access policy in a message transmission method according to an embodiment of the present application;

[0028] FIG6 is a specific flow chart of step S420 in the message transmission method provided in one embodiment of the present application;

[0029] 7 is a specific flow chart of generating a flow affinity table in a message transmission method provided in an embodiment of the present application;

[0030] 8 is a specific flow chart of transmitting subsequent service messages according to a flow affinity table in a message transmission method according to an embodiment of the present application;

[0031] FIG9 is a flowchart of a message transmission method performed by a physical client terminal device according to an embodiment of the present application;

[0032] FIG10 is a flowchart of a message transmission method performed by a computing network control system side according to an embodiment of the present application;

[0033] 11 is a flowchart of an access gateway network flow calculation based on an L2 service identifier according to an embodiment of the present application;

[0034] 12 is a flow chart of an edge gateway network flow calculation based on L3 service identification according to an embodiment of the present application;

[0035] 13 is a flowchart of a service gateway network flow calculation based on L4 service identification according to an embodiment of the present application;

[0036] FIG14 is a schematic structural diagram of a message transmission device provided in an embodiment of the present application;

[0037] FIG15 is a structural diagram of a message transmission device provided in another embodiment of the present application;

[0038] FIG16 is a structural diagram of a message transmission device provided in another embodiment of the present application;

[0039] FIG17 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0041] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, in the specification, claims, and drawings, are used to distinguish similar items and are not necessarily used to describe a specific sequence or precedence.

[0042] In the embodiments of the present application, words such as "further," "exemplarily," or "optionally" are used to indicate examples, illustrations, or descriptions and should not be interpreted as being more preferred or advantageous over other embodiments or designs. The use of words such as "further," "exemplarily," or "optionally" is intended to present related concepts in a concrete manner.

[0043] In some cases, computing-network convergence has become a fundamental industry consensus and hot topic in the 5G and post-5G eras. Under network-centric computing-network addressing and routing solutions, the network must select appropriate computing nodes from multiple service instances based on computing power and network status. However, in a multi-instance deployment model where computing nodes are deployed across cloud pools, the network directs traffic and addresses traffic based on computing-network status, making traditional globally unique host addresses inapplicable. For example, in scenarios where CPE functions are virtualized and deployed in cloud-side resource pools, virtualized CPEs can be deployed in multiple edge cloud resource pools. Consequently, user access requests face the need to execute various policies, such as load balancing, across multiple cloud resource pools on demand. However, the IP address obtained by the user terminal points to the cloud-side vCPE, so L3-based computing-network convergence scheduling and routing mechanisms are not applicable in this scenario. The user-side pCPE and the cloud-side vCPE always maintain an L2 connection.

[0044] Flexible network traffic diversion in L2 / L3 / L4 networking scenarios is crucial for cloud-based deployment scenarios like vCPE. For example, in existing vCPE deployments, the L2 access gateway encapsulates user access requests into a specific tunnel based on the virtual LAN identifier, source and destination MAC addresses, and pre-configured policies. This tunnel is then forwarded to a fixed cloud-side gateway, which then forwards the request to the corresponding vCPE. Therefore, under existing mechanisms, flexible scheduling of user access requests across multiple cloud resource pools is impossible.

[0045] Based on this, the present application provides a message transmission method, communication equipment, storage medium and program product, aiming to achieve flexible scheduling of user business messages between multi-cloud resource pools.

[0046] The following further describes the network traffic diversion architecture of the embodiment of the present application in conjunction with the accompanying drawings.

[0047] Figure 1 is a schematic diagram of a computing network traffic diversion architecture based on L2 service identification provided by an embodiment of the present application; as shown in Figure 1, the computing network traffic diversion architecture includes but is not limited to a physical customer terminal device 100 (pCPE), an access switching device 210, an access gateway 220, a cloud-side device 230 (cloud PE), a cloud resource pool 300 and a computing network control system 400, wherein the cloud resource pool 300 is provided with a virtual customer terminal device 310 (vCPE). Specifically, the pCPE is connected to the cloud resource pool 300 through the access switching device 210, the access gateway 220 and the cloud-side device 230 in sequence. In addition, the input side of the computing network control system 400 is communicated with the cloud resource pool 300, and the output side of the computing network control system 400 is communicated with the access gateway 220.

[0048] In one embodiment, as shown in Figure 1, the cloud resource pool 300 generates a control signaling flow, and flows it to the computing network control system 400; in addition, the computing network control system 400 generates a computing power perception flow based on the control signaling flow, and flows it to the access gateway 220; in addition, the pCPE generates a data flow carrying an L2 service identifier, and the data flow flows through the access switching device 210, the access gateway 220, the cloud-side device 230 and the cloud resource pool 300 in sequence.

[0049] Figure 2 is a schematic diagram of a computing network traffic diversion architecture based on L3 service identification provided by an embodiment of the present application; as shown in Figure 2, the computing network traffic diversion architecture includes but is not limited to physical customer terminal equipment 100 (pCPE), a packet bearer network, a cloud resource pool 300 and a computing network control system 400, wherein the packet bearer network includes but is not limited to an ingress side device 240 (ingress PE), a packet data network 250 and a cloud side device 230 (cloud PE), and the cloud resource pool 300 is provided with a virtual customer terminal device 310 (vCPE). Specifically, the pCPE is connected to the cloud resource pool 300 through the ingress side device 240, the packet data network 250 and the cloud side device 230 in sequence. In addition, the input side of the computing network control system 400 is communicated with the cloud resource pool 300, and the output side of the computing network control system 400 is communicated with the packet bearer network.

[0050] In one embodiment, as shown in Figure 2, the cloud resource pool 300 generates a control signaling flow, and flows it to the computing network control system 400; in addition, the computing network control system 400 generates a computing power perception flow based on the control signaling flow, and flows it to the packet bearer network; in addition, the pCPE generates a data flow carrying an L3 service identifier, and the data flow flows through the ingress side device 240, the packet data network 250, the cloud side device 230 and the cloud resource pool 300 in sequence.

[0051] Figure 3 is a schematic diagram of a computing network traffic diversion architecture based on L4 service identification provided by an embodiment of the present application; as shown in Figure 3, the computing network traffic diversion architecture includes but is not limited to a physical customer terminal device 100 (pCPE), an ingress service gateway 260, a packet data network 250, an egress service gateway 270, a cloud resource pool 300 and a computing network control system 400, and the cloud resource pool 300 is provided with a virtual customer terminal device 310 (vCPE). Specifically, the pCPE is connected to the cloud resource pool 300 through the ingress service gateway 260, the packet data network 250 and the egress service gateway 270 in sequence. In addition, the input side of the computing network control system 400 is communicated with the cloud resource pool 300, and the output side of the computing network control system 400 is communicated with the ingress service gateway 260 and the egress service gateway 270.

[0052] In one embodiment, as shown in Figure 3, the cloud resource pool 300 generates a control signaling flow, and flows it to the computing network control system 400; in addition, the computing network control system 400 generates a computing power perception flow based on the control signaling flow, and flows it to the packet bearer network; in addition, the pCPE generates a data flow carrying an L4 service identifier, and the data flow enters the service gateway 260, the packet data network 250, the egress service gateway 270 and the cloud resource pool 300 in sequence.

[0053] In one embodiment, the service identifier mentioned above is a globally unique identifier that represents a specific computing network service and is independent of the semantics of existing network protocol identifiers (such as MAC, QinQ, IP address, port number, etc.). It is not related to the deployment location and ownership of the service, but only to the service type. That is, a service identifier can be associated to refer to equivalent service instances deployed within multiple clouds or across clouds.

[0054] In one embodiment, for L2 network protocol service identification: multiple instances of home terminal virtual functions (such as vCPE) are deployed across cloud pools, and the problem of introducing multiple service node diversion in the L2 access network is introduced. At the forwarding level, a unified service identification is required to represent multiple instances of services on the cloud side, that is, the service identification only represents a given service type and has nothing to do with the location and ownership of the host providing the service. In the existing encapsulation identification of L2 Ethernet, the embodiment of the present application can reuse and expand the semantics of the following three L2 identifications as service identifications and indexes for computing power diversion, which are as follows:

[0055] The first implementation scenario: QinQ (PVLAN + SVLAN) is extended to extend the QinQ semantics of PVLAN or SVLAN or a combination of the two to represent specific service types deployed across multiple instances and clouds.

[0056] The second implementation scenario: The destination MAC address (broadcast address) is extended to represent a specific service type deployed across multiple instances and clouds.

[0057] The third implementation scenario: Extend the upper-layer protocol type to represent specific service types deployed across multiple instances and clouds.

[0058] In one embodiment, the L3 network protocol service identifier includes two types: IPv6 fixed field reuse and extended field separate encapsulation, which are as follows:

[0059] The first implementation scenario: IPv6 fixed fields are reused as service identifiers and their service semantics are extended, which may include but are not limited to the following fields: 1. The source address suffix field is reused as a service identifier and its service semantics are extended; 2. The destination address suffix field is reused as a service identifier and its service semantics are extended; 3. The Flow Label field is reused as a service identifier and its service semantics are extended.

[0060] The second implementation scenario: the service identifier is encapsulated in an IPv6 extension field alone, for example, in an HBH (Hop By Hop Header), a DOH (Destination Option Header), or an SRH (Segment Routing Header) extension header.

[0061] In one embodiment, the L4 network protocol service identifier may be set in the following two ways, but is not limited to:

[0062] The first implementation scenario: reuse the source port number field as a service identifier and extend its service semantics;

[0063] The second implementation scenario: the service identifier is defined and encapsulated separately in the UDP Payload.

[0064] In one embodiment, the process of the network sensing the computing power of the cloud resource pool where the service is located is as follows:

[0065] As shown in Figures 1 to 3, in the network's perception of the computing power of the cloud resource pool where the service is located, under the L2 service identification mechanism, the L2 access gateway interfaces with the computing network control system and perceives the computing power status of the cloud resource pool where the service is located; under the L3 service identification mechanism, the edge nodes of the packet bearer network (such as the ingress PE and cloud PE) interface with the computing network control system and perceive the computing power status of the cloud resource pool where the service is located; under the L4 service identification mechanism, the L4 service gateway interfaces with the computing network control system and perceives the computing power status of the cloud resource pool where the service is located.

[0066] Specifically, under the L2 service identification mechanism, vCPE is deployed on the cloud side. While reducing the functionality and cost of physical terminals at the home, CPE, as a terminal access component, offers greater scalability and flexibility. As cloud resources move to the cloud, vCPE deployment on the cloud side also becomes distributed, connecting and integrating vCPE service resources distributed across different cloud resource pools into a unified resource pool, providing "always-on," high-quality CPE access services to a large number of users. To achieve this computing-to-network capability, the access network must be aware of the computing resources within the cloud resource pool where the vCPE resides.

[0067] In one embodiment, as shown in Figure 1, the cloud resource pool notifies the access network computing control system via the computing power perception interface of dynamic computing power resource data related to vCPEs, including but not limited to the number of available vCPE instances, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, instance quality status parameters, etc., where the aforementioned instance quality status parameters include but are not limited to latency, packet loss, jitter, etc. It should be noted that under the L3 and L4 service identification mechanisms, the types of dynamic computing power resource data for the service are the same as above.

[0068] In one embodiment, the process of directing business requests based on service identification and multi-cloud resource pool computing power scheduling policy is as follows:

[0069] As shown in Figure 1, during the user access request process, the PCPE encapsulates the user's private VLAN (PVLAN, the VLAN identifier of the user's private network) and the source and destination MAC addresses in the user message. The access switch then encapsulates the carrier's public network VLAN (SVLAN) based on the user message, which indicates the user's VLAN identifier on the public network. The combination of the two is QinQ. QinQ uniquely identifies a user in an end-to-end network and can be used to identify users, user groups, and service types.

[0070] Next, the access gateway determines the service type (such as vCPE) accessed by the pCPE based on the L2 service identifier, and performs access node selection for multiple vCPE instances in the multi-cloud resource pool in combination with the vCPE computing power status information obtained above. Specifically, the access policy of the access gateway can be determined by the computing network control system based on the computing power status of multiple vCPE instances and the corresponding network link status fusion optimization. However, the computing power status and the network link status themselves are decoupled, and the access policy of the access gateway can also be based solely on the computing power status or the network link status. Among them, the access policy of the embodiment of the present application can be computing power status priority, network link status priority, computing network status fusion priority, computing power load balancing, etc. In addition, the access gateway usually initiates a connection to the cloud resource pool vCPE based on tunnel technology, such as SRv6, VxLAN, etc.

[0071] In one embodiment, the embodiment of the present application also sets a flow affinity mechanism in the multi-cloud resource pool diversion scenario, as follows:

[0072] Under the L2 service identification mechanism, access requests from the same PCE, after being redirected by the access gateway based on computing power awareness, are forwarded to a specific vCPE within a specific cloud resource pool, such as the vCPE in the third cloud resource pool shown in Figure 1. The user's session state is then maintained on this vCPE. Therefore, the access gateway must ensure that all subsequent uplink packets from the PCE are forwarded to this specific vCPE, rather than reselecting a new vCPE instance based on computing power, which would disrupt user service logic and data. The access gateway must maintain a flow affinity table to guide the consistent forwarding of specific user packets. The flow affinity table forms a combined traffic redirection index using source and destination identifiers. The source identifier is the QinQ and source MAC address in the user packet, while the destination identifier is the identifier of the selected vCPE or the resource pool where the selected vCPE resides, such as the cloud PE address. It should be noted that if there are multiple equivalent vCPE instances within the cloud resource pool, the cloud PE must maintain flow affinity for the selected instance.

[0073] In one embodiment, the access gateway can complete consistent forwarding of the pCPE upstream message flow based on a flow affinity table indexed by QinQ, source MAC address, and cloud pool identifier.

[0074] Furthermore, under the L3 and L4 service identification mechanisms, packet bearer network edge nodes and L4 service gateways also need to maintain the same flow affinity table as above, differing in the table entry parameters. Specifically, under the L3 and L4 service identification mechanisms, a service flow is typically uniquely identified by a 5-tuple (source and destination addresses, source and destination port numbers, and upper-layer protocol number), and the flow affinity table is generated based on this.

[0075] The technical solutions of the embodiments of the present application can be applied to various communication technologies, such as microwave communication, optical wave communication, millimeter wave communication, etc. The embodiments of the present application do not limit the specific technologies and specific device forms used.

[0076] Based on the network traffic diversion architecture of each of the above embodiments, various embodiments of the message transmission method executed by the target gateway side of the present application are proposed below.

[0077] Figure 4 is a flow chart of a message transmission method performed by a target gateway side according to an embodiment of the present application. As shown in Figure 4, the message transmission method may include but is not limited to step S410 and step S420.

[0078] Step S410: Receive a computing network traffic diversion strategy and a first service message from a physical client terminal device, wherein the computing network traffic diversion strategy is generated based on computing power status information and network status information related to the service, and the first service message carries a first service identifier for representing a service type of the first service message;

[0079] Step S420: When the virtual client terminal device corresponding to the physical client terminal device is determined to be deployed in a multi-cloud resource pool according to the first service identifier, the first target cloud resource pool is determined according to the first service identifier and the computing network diversion strategy, and the first business message is forwarded to the first target cloud resource pool.

[0080] In one embodiment, first, the computing network control system receives business-related computing power status information and network status information, and generates a computing network diversion strategy in response, and sends the computing network diversion strategy to the target gateway; then, when the target gateway receives a first business message from a physical customer terminal device, and the first business message carries a first service identifier for characterizing the service type of the first business message, the target gateway determines the deployment method of the virtual customer terminal device corresponding to the physical customer terminal device based on the first service identifier; then, if the deployment method is multi-cloud resource pool deployment, the target gateway determines the first target cloud resource pool based on the first service identifier and the computing network diversion strategy, and forwards the first business message to the first target cloud resource pool.

[0081] According to the technical solution of the embodiment of the present application, for the multi-cloud resource pool deployment method, since the embodiment of the present application can select the corresponding first target cloud resource pool to divert the first business message according to the service type, computing power status and network status corresponding to the first business message, it can realize flexible scheduling of user business messages between multi-cloud resource pools.

[0082] In addition, the first service identifier is set differently in different networking situations, as follows:

[0083] In one embodiment, in the case of L2 networking, the first service identifier is obtained by semantically extending the virtual LAN identifier, the destination MAC address or the upper layer protocol type information, wherein the virtual LAN identifier includes at least one of QinQ, a private virtual LAN identifier or a public virtual LAN identifier.

[0084] In one embodiment, in the case of L3 networking, the first service identifier is obtained by semantically extending an IPv6 fixed field, or the first service identifier is encapsulated in an IPv6 extension field.

[0085] In one embodiment, in the case of L4 networking, the first service identifier is obtained by semantically extending the source port number field, or the first service identifier is encapsulated in a user message protocol payload.

[0086] In addition, the computing power status information may include at least one of the following: the number of available instances of the virtual client terminal device, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, and instance quality status parameters.

[0087] FIG5 is a specific flowchart of determining an access policy in a message transmission method provided in an embodiment of the present application; as shown in FIG5 , after determining the first target cloud resource pool, the message transmission method may further include but is not limited to step S510 and step S520.

[0088] Step S510: Obtain computing power status information and / or network status information of the virtual client terminal device in the first target cloud resource pool;

[0089] Step S520: Determine an access policy for the virtual client terminal device based on the computing power status information and / or network status information of the virtual client terminal device in the first target cloud resource pool.

[0090] In one embodiment, the present application embodiment also sets corresponding access policies, including but not limited to the following three situations:

[0091] In the first case, the access policy of the virtual client terminal device is determined according to the computing power status information of the virtual client terminal device in the first target cloud resource pool.

[0092] In the second case, the access policy of the virtual client terminal device is determined according to the network status information of the virtual client terminal device in the first target cloud resource pool.

[0093] In a third case, the access policy of the virtual client terminal device is determined according to the computing power status information and network status information of the virtual client terminal device in the first target cloud resource pool.

[0094] In one embodiment, the above-mentioned access strategy may be one of the following: computing power status priority strategy, network link status priority strategy, computing network status fusion priority strategy, computing power load balancing strategy.

[0095] Figure 6 is a specific flow chart of step S420 in the message transmission method provided in an embodiment of the present application; as shown in Figure 6, the method of forwarding the first business message to the first target cloud resource pool in step S420 may include but is not limited to step S610 and step S620.

[0096] Step S610: Encapsulate the first service message into a message format corresponding to the target tunnel;

[0097] Step S620: Send the first service message to the first target cloud resource pool through the target tunnel.

[0098] In one embodiment, the target gateway may initiate tunnel encapsulation and forward the first service message to the first target cloud resource pool, wherein the tunnel encapsulation may be SRv6 or VxLAN.

[0099] Figure 7 is a specific flow chart of generating a flow affinity table in a message transmission method provided in an embodiment of the present application; as shown in Figure 7, after executing step S420 of determining the first target cloud resource pool based on the first service identifier and the computing network diversion strategy, the message transmission method may also include but is not limited to steps S710 and S720.

[0100] Step S710: Obtain a source identifier and a destination identifier, wherein the source identifier corresponds to the first service message, and the destination identifier corresponds to the first target cloud resource pool or to a virtual client terminal device in the first target cloud resource pool;

[0101] Step S720: Generate a flow affinity table according to the source end identifier and the destination end identifier, wherein the flow affinity table is used to perform flow indexing on subsequent second service packets.

[0102] In one embodiment, under the L2 service identification mechanism, the access request of the same pCPE is forwarded to a specific vCPE in a specific cloud resource pool after the access gateway diverts traffic based on computing power perception, such as the vCPE in the third cloud resource pool shown in Figure 1. After that, the user's session status will be maintained in this vCPE. Therefore, the access gateway needs to ensure that all subsequent uplink message flows of the pCPE are forwarded to this specific vCPE, rather than reselecting a new vCPE instance based on the computing power status, which would cause confusion in the user's business logic and data. The access gateway needs to maintain a flow affinity table to guide the consistent forwarding of specific user messages. The flow affinity table forms a combined diversion index through the source and destination identifiers.

[0103] In one embodiment, the source identifier is the QinQ or source MAC address in the user message, and the destination identifier is the selected vCPE identifier or the resource pool identifier of the selected vCPE, such as the cloud PE address. It should be noted that if the cloud resource pool includes multiple equivalent vCPE instances, the cloud PE must maintain flow affinity for the selected instance.

[0104] Figure 8 is a specific flow chart of transmitting subsequent business messages according to the flow affinity table in the message transmission method provided in an embodiment of the present application; as shown in Figure 8, after executing step S720 of generating the flow affinity table according to the source end identifier and the destination end identifier, the message transmission method may also include but is not limited to step S810 and step S820.

[0105] Step S810: Receive a second service message from a physical client terminal device, where the second service message carries a second service identifier for characterizing a service type of the second service message;

[0106] Step S820: When the second target cloud resource pool corresponding to the second service identifier is found according to the flow affinity table, the second service message is forwarded to the second target cloud resource pool.

[0107] In one embodiment, when the target gateway receives the second service message from the pCPE, it will first search the flow affinity table for the second service identifier carried by the second service message. If a match is found, it will be forwarded to the selected vCPE cloud pool according to the established tunnel mechanism, thereby ensuring that subsequent uplink message flows of the pCPE are forwarded to the specific vCPE, rather than reselecting a new vCPE instance based on the computing power status, which would cause confusion in user business logic and data.

[0108] In one embodiment, in the case of L2 networking, the source identifier includes at least one of a private virtual local area network identifier, a public virtual local area network identifier, and a source MAC address.

[0109] In one embodiment, in the case of L3 networking or L4 networking, the source identifier includes at least one of a source address, a destination address, a source port number, a destination port number, and an upper layer protocol number.

[0110] Based on the network traffic diversion architecture and the message transmission method executed by the target gateway side of the above-mentioned embodiments, various embodiments of the message transmission method executed by the physical client terminal device side of the present application are proposed below.

[0111] FIG9 is a flowchart of a message transmission method provided by a physical client terminal device according to an embodiment of the present application; as shown in FIG9 , the message transmission method may include but is not limited to step S900 .

[0112] Step S900: Send the first business message carrying the first service identifier to the target gateway, so that the target gateway forwards the first business message to the first target cloud resource pool after determining the first target cloud resource pool based on the first service identifier and the received computing network diversion strategy; wherein, the first service identifier is used to characterize the service type of the first business message, and the computing network diversion strategy is generated based on the computing power status information and network status information related to the business.

[0113] In one embodiment, first, the computing network control system receives business-related computing power status information and network status information, and generates a computing network diversion strategy in response, and sends the computing network diversion strategy to the target gateway; then, when the target gateway receives a first business message from a physical customer terminal device, and the first business message carries a first service identifier for characterizing the service type of the first business message, the target gateway determines the deployment method of the virtual customer terminal device corresponding to the physical customer terminal device based on the first service identifier; then, if the deployment method is multi-cloud resource pool deployment, the target gateway determines the first target cloud resource pool based on the first service identifier and the computing network diversion strategy, and forwards the first business message to the first target cloud resource pool.

[0114] According to the technical solution of the embodiment of the present application, for the multi-cloud resource pool deployment method, since the embodiment of the present application can select the corresponding first target cloud resource pool to divert the first business message according to the service type, computing power status and network status corresponding to the first business message, it can realize flexible scheduling of user business messages between multi-cloud resource pools.

[0115] Since the message transmission method executed by the physical client terminal device side in the embodiment of the present application corresponds to the message transmission method executed by the target gateway side in the above-mentioned embodiment, the specific implementation methods and technical effects of the message transmission method executed by the physical client terminal device side in the embodiment of the present application can refer to the specific implementation methods and technical effects of the message transmission method executed by the target gateway side in any of the above-mentioned embodiments.

[0116] In addition, the first service identifier is set differently in different networking situations, as follows:

[0117] In one embodiment, in the case of L2 networking, the first service identifier is obtained by semantically extending the virtual LAN identifier, the destination MAC address or the upper layer protocol type information, wherein the virtual LAN identifier includes at least one of QinQ, a private virtual LAN identifier or a public virtual LAN identifier.

[0118] In one embodiment, in the case of L3 networking, the first service identifier is obtained by semantically extending an IPv6 fixed field, or the first service identifier is encapsulated in an IPv6 extension field.

[0119] In one embodiment, in the case of L4 networking, the first service identifier is obtained by semantically extending the source port number field, or the first service identifier is encapsulated in a user message protocol payload.

[0120] In addition, the computing power status information may include at least one of the following: the number of available instances of the virtual client terminal device, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, and instance quality status parameters.

[0121] Based on the computing network traffic diversion architecture of each of the above embodiments and the message transmission method executed by the target gateway side and the physical client terminal device side, various embodiments of the message transmission method executed by the computing network control system side of the present application are proposed below.

[0122] FIG10 is a flowchart of a message transmission method provided by a computing network control system side according to an embodiment of the present application; as shown in FIG10 , the message transmission method may include but is not limited to step S1010 and step S1020.

[0123] Step S1010: Obtain computing power status information and network status information related to the business, and generate a computing network traffic diversion strategy based on the computing power status information and network status information;

[0124] Step S1020: Send the network traffic diversion strategy to the target gateway, so that the target gateway forwards the first business message to the first target cloud resource pool after determining the first target cloud resource pool based on the network traffic diversion strategy and the first service identifier of the received first business message; wherein, the first service identifier is used to characterize the service type of the first business message.

[0125] In one embodiment, first, the computing network control system receives business-related computing power status information and network status information, and generates a computing network diversion strategy in response, and sends the computing network diversion strategy to the target gateway; then, when the target gateway receives a first business message from a physical customer terminal device, and the first business message carries a first service identifier for characterizing the service type of the first business message, the target gateway determines the deployment method of the virtual customer terminal device corresponding to the physical customer terminal device based on the first service identifier; then, if the deployment method is multi-cloud resource pool deployment, the target gateway determines the first target cloud resource pool based on the first service identifier and the computing network diversion strategy, and forwards the first business message to the first target cloud resource pool.

[0126] According to the technical solution of the embodiment of the present application, for the multi-cloud resource pool deployment method, since the embodiment of the present application can select the corresponding first target cloud resource pool to divert the first business message according to the service type, computing power status and network status corresponding to the first business message, it can realize flexible scheduling of user business messages between multi-cloud resource pools.

[0127] Since the message transmission method executed by the computing network control system side in the embodiment of the present application corresponds to the message transmission method executed by the target gateway side or the physical client terminal device side in the above-mentioned embodiment, the specific implementation methods and technical effects of the message transmission method executed by the computing network control system side in the embodiment of the present application can refer to the specific implementation methods and technical effects of the message transmission method executed by the target gateway side or the physical client terminal device side in any of the above-mentioned embodiments.

[0128] In addition, the first service identifier is set differently in different networking situations, as follows:

[0129] In one embodiment, in the case of L2 networking, the first service identifier is obtained by semantically extending the virtual LAN identifier, the destination MAC address or the upper layer protocol type information, wherein the virtual LAN identifier includes at least one of QinQ, a private virtual LAN identifier or a public virtual LAN identifier.

[0130] In one embodiment, in the case of L3 networking, the first service identifier is obtained by semantically extending an IPv6 fixed field, or the first service identifier is encapsulated in an IPv6 extension field.

[0131] In one embodiment, in the case of L4 networking, the first service identifier is obtained by semantically extending the source port number field, or the first service identifier is encapsulated in a user message protocol payload.

[0132] In addition, the computing power status information may include at least one of the following: the number of available instances of the virtual client terminal device, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, and instance quality status parameters.

[0133] Based on the computing network traffic diversion architecture and message transmission method of each of the above embodiments, various overall embodiments of the message transmission method of the present application are proposed below.

[0134] Figure 11 is a flowchart of the access gateway network calculation and diversion method based on the L2 service identifier provided by an embodiment of the present application; as shown in Figure 11, the access gateway network calculation and diversion method based on the L2 service identifier includes but is not limited to steps S1101 to S1111.

[0135] Step S1101: The access gateway receives a vCPE request carrying an L2 service identifier;

[0136] Step S1102: Determine whether the flow affinity table is matched. If so, execute step S1103; otherwise, execute step S1104.

[0137] Step S1103: forward to the selected vCPE instance;

[0138] Step S1104: Determine whether the vCPE is deployed in a single cloud resource pool. If so, execute step S1105; otherwise, execute step S1108.

[0139] Step S1105: forwarding to a pre-configured vCPE instance;

[0140] Step S1106: The cloud resource pool announces the computing power status indexed by the L2 service identifier;

[0141] Step S1107: The computing network control system receives computing power status data and generates a business diversion strategy;

[0142] Step S1108: The access gateway performs instance optimization based on the L2 service identifier and the computing network policy;

[0143] Step S1109: The access gateway generates a flow affinity table;

[0144] Step S1110: The access gateway performs SRv6 / VxLAN tunnel encapsulation and completes forwarding;

[0145] Step S1111: The cloud-side gateway receives the tunnel request and forwards it to the selected vCPE instance.

[0146] In one embodiment, as shown in FIG1 and FIG11 , in the L2 access network, the access gateway in FIG1 is a general access forwarding node, and the process is as follows:

[0147] 1. The access gateway receives the access request message from the pCPE and searches the flow affinity table based on the L2 service identifier. If a match is found, it forwards the message to the selected vCPE cloud resource pool according to the established tunnel mechanism.

[0148] 2. If the access gateway fails to query the flow affinity table, it determines whether the corresponding vCPE is deployed in a multi-cloud resource pool based on the L2 service identifier. If it is deployed in a single cloud resource pool, it forwards the user request message to the corresponding vCPE cloud resource pool according to the pre-configured information.

[0149] 3. The access gateway determines that the corresponding vCPE is deployed in a multi-cloud resource pool based on the L2 service identifier. It then queries the corresponding computing power diversion policy table based on the L2 service identifier to select a specific vCPE instance. The cloud resource pool where the service is located notifies the computing network control system of its computing power status according to a specific protocol interface. The latter generates a computing network diversion policy indexed by the L2 service identifier and sends it to the access gateway.

[0150] 4. The access gateway generates a flow affinity table based on the L2 service identifier and the selected vCPE cloud resource pool identifier (such as the cloud PE address);

[0151] 5. The access gateway initiates SRv6 or VxLAN tunnel encapsulation and forwards the user message to the cloud resource pool where the selected vCPE is located;

[0152] 6. The cloud-side gateway receives the request message forwarded by the access gateway, terminates the tunnel encapsulation, and forwards the request message to the selected vCPE instance;

[0153] 7. The process ends.

[0154] Figure 12 is a flowchart of edge gateway network calculation and diversion based on L3 service identification provided by an embodiment of the present application; as shown in Figure 12, the access gateway network calculation and diversion method based on L3 service identification includes but is not limited to steps S1201 to S1211.

[0155] Step S1201: The edge gateway receives a service request carrying an L3 service identifier;

[0156] Step S1202: Determine whether the flow affinity table is matched. If so, execute step S1203; otherwise, execute step S1204.

[0157] Step S1203: forward to the selected service instance;

[0158] Step S1204: Determine whether the service is deployed in a single cloud resource pool. If so, execute step S1205; otherwise, execute step S1208.

[0159] Step S1205: forward to a pre-configured service instance;

[0160] Step S1206: The cloud resource pool announces the computing power status indexed by the L3 service identifier;

[0161] Step S1207: The computing network control system receives computing power status data and generates a business diversion strategy;

[0162] Step S1208: The edge gateway performs instance optimization based on the L3 service identifier and the computing network policy;

[0163] Step S1209: The edge gateway generates a flow affinity table;

[0164] Step S1210: The edge gateway performs forwarding according to the computing network strategy;

[0165] Step S1211: The egress gateway receives the service request and forwards it to the selected service instance.

[0166] In one embodiment, as shown in FIG2 and FIG12 , under the L3 service identification mechanism, the ingress side device in FIG2 is an edge gateway of the packet bearer network, and the process is as follows:

[0167] 1. The edge gateway receives the service request message from the terminal and searches the flow affinity table according to the L3 service identifier. If a match is found, it forwards the message to the cloud resource pool where the selected service is located according to the established policy.

[0168] 2. If the edge gateway fails to query the flow affinity table, it determines whether the corresponding service is deployed in a multi-cloud resource pool based on the L3 service identifier. If it is deployed in a single cloud resource pool, it forwards the service request message to the corresponding service cloud resource pool according to the pre-configured information;

[0169] 3. The edge gateway determines that the corresponding service is deployed in a multi-cloud resource pool based on the L3 service identifier, and then queries the corresponding computing network diversion strategy table based on the L3 service identifier to complete the selection of a specific service instance; wherein, the cloud resource pool where the service is located notifies the computing network control system of its computing power status according to a specific protocol interface, and the latter generates a computing network diversion strategy indexed by the L3 service identifier and sends it to the edge gateway. In addition, the computing network control system in the embodiment of the present application can be a centralized control system or a distributed control system.

[0170] 4. The edge gateway generates a flow affinity table based on the L3 service identifier and the selected service cloud resource pool identifier (such as the cloud PE address);

[0171] 5. The edge gateway forwards the service request message to the cloud resource pool where the selected service instance is located according to the network diversion strategy generated by the network control system;

[0172] 6. The egress gateway receives the service request message forwarded by the edge gateway and forwards the request message to the selected service instance;

[0173] 7. The process ends.

[0174] Figure 13 is a flowchart of the service gateway network calculation and diversion based on the L4 service identifier provided by an embodiment of the present application; as shown in Figure 13, the access gateway network calculation and diversion method based on the L4 service identifier includes but is not limited to steps S1301 to S1311.

[0175] Step S1301: The L4 service gateway receives a service request carrying an L4 service identifier;

[0176] Step S1302: Determine whether the flow affinity table is matched. If so, execute step S1303; otherwise, execute step S1304.

[0177] Step S1303: forward to the selected service instance;

[0178] Step S1304: Determine whether the service is deployed in a single cloud resource pool. If so, execute step S1305; otherwise, execute step S1308.

[0179] Step S1305: forward to a pre-configured service instance;

[0180] Step S1306: The cloud resource pool announces the computing power status indexed by the L4 service identifier;

[0181] Step S1307: The computing network control system receives computing power status data and generates a business diversion strategy;

[0182] Step S1308: The L4 service gateway performs instance optimization based on the L4 service identifier and the computing network policy;

[0183] Step S1309: The L4 service gateway generates a flow affinity table;

[0184] Step S1310: The L4 service gateway performs forwarding according to the computing network strategy;

[0185] Step S1311: The L4 service gateway receives the service request and forwards it to the selected service instance.

[0186] In one embodiment, as shown in FIG3 and FIG13 , under the L4 service identification mechanism, the L4 service gateway in FIG3 is an OverLay gateway based on UDP / TCP, which is usually deployed at the edge node close to the terminal and close to the cloud resource pool. The process is as follows:

[0187] 1. The L4 service gateway receives the service request message from the terminal, searches the flow affinity table according to the L4 service identifier, and if a match is found, forwards it to the cloud resource pool where the selected service is located according to the established policy;

[0188] 2. If the L4 service gateway fails to query the flow affinity table, it determines whether the corresponding service is multi-cloud deployed based on the L4 service identifier. If it is a single-cloud deployment, it forwards the service request message to the corresponding service cloud resource pool according to the pre-configured information;

[0189] 3. The L4 service gateway determines that the corresponding service is multi-cloud deployed based on the L4 service identifier. It then queries the corresponding computing network traffic diversion policy table based on the L4 service identifier to complete the selection of a specific service instance.

[0190] Note: The cloud resource pool where the service is located notifies the computing power status to the computing network control system according to a specific protocol interface. The latter generates a computing network traffic diversion strategy indexed by the L4 service identifier and sends it to the L4 service gateway.

[0191] 4. The L4 service gateway generates a flow affinity table based on the L4 service identifier and the selected service cloud resource pool identifier (such as the cloud PE address);

[0192] 5. The L4 service gateway forwards the service request message to the cloud resource pool where the selected service instance is located according to the network diversion strategy generated by the network control system;

[0193] 6. The L4 service gateway receives the service request message forwarded by the L4 service gateway on the receiving end side and forwards the request message to the selected service instance;

[0194] 7. The process ends.

[0195] Based on the message transmission method of any of the above embodiments, various embodiments of the message transmission device, communication equipment, computer-readable storage medium and computer program product of the embodiments of the present application are proposed below.

[0196] FIG14 is a schematic structural diagram of a message transmission device provided in an embodiment of the present application; as shown in FIG14 , the message transmission device includes but is not limited to a receiving unit 510 and a drainage unit 520 .

[0197] Among them, the receiving unit 510 is used to receive the computing network diversion strategy and the first business message from the physical customer terminal device. The computing network diversion strategy is generated based on the business-related computing power status information and network status information. The first business message carries a first service identifier for characterizing the service type of the first business message; when it is determined according to the first service identifier that the virtual customer terminal device corresponding to the physical customer terminal device is deployed in a multi-cloud resource pool mode, the diversion unit 520 is used to determine the first target cloud resource pool based on the first service identifier and the computing network diversion strategy, and forward the first business message to the first target cloud resource pool.

[0198] In one embodiment, the message transmission device also includes but is not limited to an access unit 530, which is used to determine the access policy of the virtual client terminal device based on the computing power status information and / or network status information of the virtual client terminal device in the first target cloud resource pool, wherein the access policy includes one of the following: computing power status priority policy, network link status priority policy, computing-network status fusion priority policy, and computing power load balancing policy.

[0199] In one embodiment, the above-mentioned traffic diversion unit 520 is further configured to encapsulate the first service message into a message format corresponding to the target tunnel, and send the first service message to the first target cloud resource pool through the target tunnel.

[0200] In one embodiment, the message transmission device also includes but is not limited to a table building unit 540, which is used to obtain a source end identifier and a destination end identifier, and generate a flow affinity table based on the source end identifier and the destination end identifier, wherein the source end identifier corresponds to the first business message, the destination end identifier corresponds to the first target cloud resource pool or to the virtual customer terminal device in the first target cloud resource pool, and the flow affinity table is used to divert the index for the subsequent second business message.

[0201] In one embodiment, the message transmission device also includes but is not limited to a table lookup unit 550, which is used to receive a second business message from a physical customer terminal device, and the second business message carries a second service identifier for characterizing the service type of the second business message; when the second target cloud resource pool corresponding to the second service identifier is found according to the flow affinity table, the table lookup unit 550 is used to forward the second business message to the second target cloud resource pool.

[0202] Since the message transmission device of the embodiment of the present application corresponds to the message transmission method executed by the target gateway side of the above-mentioned embodiment, the specific implementation manner and technical effects of the message transmission device of the embodiment of the present application can refer to the specific implementation manner and technical effects of the message transmission method executed by the target gateway side of any of the above-mentioned embodiments.

[0203] FIG15 is a structural diagram of a message transmission device provided in another embodiment of the present application; as shown in FIG15 , the message transmission device includes but is not limited to a message sending unit 610 .

[0204] Among them, the message sending unit 610 is used to send the first business message carrying the first service identifier to the target gateway, so that the target gateway forwards the first business message to the first target cloud resource pool after determining the first target cloud resource pool based on the first service identifier and the received computing network diversion strategy; wherein, the first service identifier is used to characterize the service type of the first business message, and the computing network diversion strategy is generated based on the computing power status information and network status information related to the business.

[0205] Since the message transmission device of the embodiment of the present application corresponds to the message transmission method by the physical client terminal device side of the above-mentioned embodiment, the specific implementation manner and technical effects of the message transmission device of the embodiment of the present application can refer to the specific implementation manner and technical effects of the message transmission method by the physical client terminal device side of any of the above-mentioned embodiments.

[0206] FIG16 is a structural diagram of a message transmission device provided in another embodiment of the present application; as shown in FIG16 , the message transmission device includes but is not limited to a policy sending unit 710 .

[0207] Among them, the policy sending unit 710 is used to obtain business-related computing power status information and network status information, generate a computing network diversion strategy based on the computing power status information and network status information, and send the computing network diversion strategy to the target gateway, so that the target gateway determines the first target cloud resource pool based on the computing network diversion strategy and the first service identifier of the received first business message, and then forwards the first business message to the first target cloud resource pool; wherein, the first service identifier is used to characterize the service type of the first business message.

[0208] Since the message transmission device of the embodiment of the present application corresponds to the message transmission method executed by the computing network control system side of the above-mentioned embodiment, the specific implementation method and technical effects of the message transmission device of the embodiment of the present application can refer to the specific implementation method and technical effects of the message transmission method executed by the computing network control system side of any of the above-mentioned embodiments.

[0209] Figure 17 is a schematic diagram of the structure of a communication device provided in one embodiment of the present application. As shown in Figure 17, the communication device includes a memory 810 and a processor 820. The number of memories 810 and processors 820 can be one or more, and Figure 17 uses one memory 810 and one processor 820 as an example. The memory 810 and processor 820 in the device can be connected via a bus or other means, and Figure 17 uses a bus connection as an example.

[0210] The memory 810, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the message transmission method provided in any embodiment of the present application. The processor 820 implements the above-described message transmission method by executing the software programs, instructions, and modules stored in the memory 810.

[0211] The memory 810 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function. In addition, the memory 810 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 810 may further include a memory remotely located relative to the processor 820, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0212] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, which are used to execute the message transmission method provided in any embodiment of the present application.

[0213] An embodiment of the present application also provides a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device executes the message transmission method provided in any embodiment of the present application.

[0214] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0215] Those skilled in the art will appreciate that all or some of the steps in the methods, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.

[0216] In a hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0217] As used in this specification, the terms "component," "module," "system," and the like are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components can reside in a process or execution thread, and a component can be located on one computer or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, through local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

Claims

1. A message transmission method, comprising: receiving a computing network traffic diversion strategy and a first service message from a physical client terminal device, wherein the computing network traffic diversion strategy is generated according to computing power status information and network status information related to the service, and the first service message carries a first service identifier for characterizing a service type of the first service message; When the virtual client terminal device corresponding to the physical client terminal device is determined to be deployed in a multi-cloud resource pool according to the first service identifier, the first target cloud resource pool is determined according to the first service identifier and the computing network diversion strategy, and the first business message is forwarded to the first target cloud resource pool.

2. The message transmission method according to claim 1, wherein: In the case of L2 networking, the first service identifier is obtained by semantically extending the virtual LAN identifier, the destination MAC address or the upper layer protocol type information, wherein the virtual LAN identifier includes at least one of QinQ, a private virtual LAN identifier or a public virtual LAN identifier.

3. The message transmission method according to claim 1, wherein: In the case of L3 networking, the first service identifier is obtained by semantically extending an IPv6 fixed field, or the first service identifier is encapsulated in an IPv6 extension field.

4. The message transmission method according to claim 1, wherein: In the case of L4 networking, the first service identifier is obtained by semantically extending the source port number field, or the first service identifier is encapsulated in a user message protocol payload.

5. The message transmission method according to claim 1, wherein: The computing power status information includes at least one of the following: the number of available instances of the virtual client terminal device, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, and instance quality status parameters.

6. The message transmission method according to claim 1, wherein: After determining the first target cloud resource pool according to the first service identifier and the computing network diversion strategy, the message transmission method further includes: The access policy of the virtual client terminal device is determined based on the computing power status information and / or network status information of the virtual client terminal device in the first target cloud resource pool, wherein the access policy includes one of the following: computing power status priority policy, network link status priority policy, computing-network status fusion priority policy, computing power load balancing policy.

7. The message transmission method according to claim 1, wherein: The forwarding the first service message to the first target cloud resource pool includes: Encapsulating the first service message into a message format corresponding to the target tunnel; The first service message is sent to the first target cloud resource pool through the target tunnel.

8. The message transmission method according to claim 1, wherein: After determining the first target cloud resource pool according to the first service identifier and the computing network diversion strategy, the message transmission method further includes: Acquire a source identifier and a destination identifier, wherein the source identifier corresponds to the first service message, and the destination identifier corresponds to the first target cloud resource pool or corresponds to the virtual client terminal device in the first target cloud resource pool; A flow affinity table is generated according to the source end identifier and the destination end identifier, wherein the flow affinity table is used to perform flow indexing on subsequent second service messages.

9. The message transmission method according to claim 8, wherein: After generating the flow affinity table according to the source end identifier and the destination end identifier, the message transmission method further includes: Receive a second service message from the physical client terminal device, the second service message carrying information for characterizing the a second service identifier of the service type of the second service message; When the second target cloud resource pool corresponding to the second service identifier is found according to the flow affinity table, the second service message is forwarded to the second target cloud resource pool.

10. The message transmission method according to claim 8, wherein: In the case of L2 networking, the source end identifier includes at least one of a private virtual local area network identifier, a public virtual local area network identifier, and a source MAC address; or, In the case of L3 networking or L4 networking, the source end identifier includes at least one of a source address, a destination address, a source port number, a destination port number, and an upper layer protocol number.

11. A message transmission method, comprising: A first business message carrying a first service identifier is sent to a target gateway, so that the target gateway forwards the first business message to the first target cloud resource pool after determining the first target cloud resource pool based on the first service identifier and the received computing network diversion strategy; wherein the first service identifier is used to characterize the service type of the first business message, and the computing network diversion strategy is generated based on the computing power status information and network status information related to the business.

12. The message transmission method according to claim 11, wherein: In the case of L2 networking, the first service identifier is obtained by semantically extending the virtual LAN identifier, the destination MAC address or the upper layer protocol type information, wherein the virtual LAN identifier includes at least one of QinQ, a private virtual LAN identifier or a public virtual LAN identifier.

13. The message transmission method according to claim 11, wherein: In the case of L3 networking, the first service identifier is obtained by semantically extending an IPv6 fixed field, or the first service identifier is encapsulated in an IPv6 extension field.

14. The message transmission method according to claim 11, wherein: In the case of L4 networking, the first service identifier is obtained by semantically extending the source port number field, or the first service identifier is encapsulated in a user message protocol payload.

15. The message transmission method according to claim 11, wherein: The computing power status information includes at least one of the following: the number of available instances of virtual client terminal devices, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, and instance quality status parameters.

16. A message transmission method, comprising: Obtaining computing power status information and network status information related to the business, and generating a computing network traffic diversion strategy based on the computing power status information and the network status information; The computing network diversion strategy is sent to the target gateway so that the target gateway determines the first target cloud resource pool based on the computing network diversion strategy and the first service identifier of the received first business message, and then forwards the first business message to the first target cloud resource pool; wherein the first service identifier is used to characterize the service type of the first business message.

17. The message transmission method according to claim 16, wherein: In the case of L2 networking, the first service identifier is obtained by semantically extending the virtual LAN identifier, the destination MAC address or the upper layer protocol type information, wherein the virtual LAN identifier includes at least one of QinQ, a private virtual LAN identifier or a public virtual LAN identifier.

18. The message transmission method according to claim 16, wherein: In the case of L3 networking, the first service identifier is obtained by semantically extending an IPv6 fixed field, or the first service identifier is encapsulated in an IPv6 extension field.

19. The message transmission method according to claim 16, wherein: In the case of L4 networking, the first service identifier is obtained by semantically extending the source port number field, or the first service identifier is encapsulated in a user message protocol payload.

20. The message transmission method according to claim 16, wherein: The computing power status information includes at least one of the following: the number of available instances of virtual client terminal devices, overall load data, instance load data, overall remaining session capacity, instance remaining session capacity, and instance quality status parameters.

21. A communication device comprising: at least one processor; at least one memory for storing at least one program; When at least one of the programs is executed by at least one of the processors, the message transmission method according to any one of claims 1 to 20 is executed.

22. A computer-readable storage medium storing a program executable by a processor, wherein the program executable by the processor, when executed by the processor, executes the message transmission method according to any one of claims 1 to 20.

23. A computer program product, comprising a computer program or computer instructions, wherein the computer program or the computer instructions are stored in a computer-readable storage medium, a processor of a computer device reads the computer program or the computer instructions from the computer-readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device executes the message transmission method as described in any one of claims 1 to 20.

Images