WO2022166464A1

WO2022166464A1 - Packet transmission method and system, and device

Info

Publication number: WO2022166464A1
Application number: PCT/CN2021/141436
Authority: WO
Inventors: 廖婷; 肖亚群; 古锐; 方晟
Original assignee: 华为技术有限公司
Priority date: 2021-02-07
Filing date: 2021-12-27
Publication date: 2022-08-11
Also published as: CN114915518A

Abstract

Disclosed in the embodiments of the present application are a packet transmission method and system, and a device. Specifically, after acquiring a first packet, a first network device can establish, in real time and according to attribute information and a destination address in the first packet, a first tunnel that meets an SLA requirement, or the first network device sends, to a controller, a request message for establishing the first tunnel, so as to acquire information regarding the first tunnel from the controller, and then establishes the first tunnel according to the information of the first tunnel, so as to forward the first packet to a second network device by using the first tunnel. It can be seen that the first network device can create tunnels on demand according to an SLA requirement corresponding to service traffic, and it is not necessary for the first network device to pre-create the tunnels, and therefore, not only is the pressure and performance costs of the first network device reduced, but dynamically changed requirements of a network system can also be met in a timely manner.

Description

A message transmission method, system and device

This application claims the priority of the Chinese patent application with the application number 202110171282.1 and the application title "A message transmission method, system and device" filed on February 7, 2021, the entire contents of which are incorporated into this application by reference .

technical field

The present application relates to the field of communication technologies, and in particular, to a message transmission method, system, and device.

Background technique

During service packet transmission, in order to ensure the timeliness of service transmission, a transmission tunnel may be created in advance between the source network device and each destination network device. Since different service packets correspond to different SLA requirements, in order to meet the service requirements, the source network device and each destination network device establish tunnels corresponding to different SLA requirements. However, when there are a large number of destination network devices, the source network device needs to establish a large number of tunnels, which not only causes a heavy load on the source device, but also increases performance requirements for the source network device.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a packet transmission method, system, and device, so as to reduce the pressure on network devices and the performance cost of network devices.

In a first aspect of the embodiments of the present application, a packet transmission method is provided, the method includes: a first network device obtains a first packet, the first packet includes attribute information and a destination address, and the attribute information It is used to indicate the service level agreement SLA requirements that need to be met when forwarding the service traffic to which the first packet belongs; the first network device establishes a first tunnel according to the attribute information and the destination address, or the first A network device uses the attribute information and the destination address to send a request message for establishing the first tunnel to the controller, where the first tunnel is a forwarding tunnel that meets the SLA requirements, and is used to transfer the first message to the controller. The message is forwarded to the second network device, and the second network device determines according to the destination address.

In this embodiment, after acquiring the service traffic packet, that is, the first packet, the first network device may establish a first tunnel that meets the SLA requirements in real time according to the attribute information and the destination address in the first packet, or , the first network device sends a request message for establishing a first tunnel to the controller, so as to obtain information about the first tunnel from the controller, and then establish a first tunnel according to the information of the first tunnel, so as to use the first tunnel to transfer the first tunnel to the controller. The message is forwarded to the second network device. That is, the purpose of creating a tunnel on demand according to traffic is realized without pre-creation, which not only reduces the pressure and performance cost of the first network device, but also can meet the dynamically changing requirements of the network system in time.

In a specific implementation manner, establishing, by the first network device, the first tunnel according to the attribute information and the destination address includes: the first network device creating the first tunnel according to the attribute information and the destination address. or the first network device searches and obtains the first tunnel locally according to the attribute information and the destination address.

In this embodiment, the first network device may pre-store the first tunnel on the control plane, and after acquiring the first packet, search for and acquire the first tunnel locally according to the attribute information and destination address in the first packet. Or, when the first network device has the tunnel calculation and creation capability, the first network device establishes the first tunnel according to the attribute information and the destination address.

In a specific implementation manner, the method further includes: the first network device sending the information of the first tunnel from the control plane of the first network device to the forwarding plane.

In this implementation manner, after establishing the first tunnel, the first network device may send the information of the first tunnel from the control plane to the forwarding plane, so that the first network device uses the first tunnel on the forwarding plane to send the first packet to the forwarding plane. forward.

In a specific implementation manner, after the first network device sends a request message for establishing the first tunnel to the controller by using the attribute information and the destination address, the method includes: the first network device The device receives a response message sent by the controller, where the response message includes information of the first tunnel corresponding to the attribute information and the destination address.

In this embodiment, when the first network device does not have the tunnel computing capability, a request message for establishing the first tunnel may be sent to the controller, so that the controller obtains the information of the first tunnel according to the attribute information and the destination address, and sends the information of the first tunnel to the controller. The information of the first tunnel is sent to the first network device.

In a specific implementation manner, the method further includes: determining, by the first network device, that the first tunnel is not used for forwarding packets within a preset time period, and deleting or changing the state of the first tunnel to Do not use.

In this implementation manner, in order to save resources, the first network device can detect whether the first tunnel is not used for forwarding packets within a preset period of time, and if so, delete the first tunnel or change the state to not used to avoid the first tunnel. The occupation of forwarding resources by a tunnel.

In a specific implementation manner, the first network device is an ingress network device of the first tunnel.

In a specific implementation manner, the egress network device of the first tunnel is a second network device, the second network device is a device corresponding to the destination address, or the second network device is a device used to transfer The destination device indicated by the destination address is a device that accesses the network.

In a specific implementation manner, the method further includes: acquiring, by the first network device, a second packet, where the second packet includes the attribute information and the destination address, and the second packet belong to the service flow; the first network device is changed from the second network device to the third network device according to the device used to access the destination device indicated by the destination address to the network, the attribute information and the The destination address establishes a second tunnel to the third network device; the first network device uses the second tunnel to forward the second packet to the third network device.

In this embodiment, when the device corresponding to the access network of the destination device indicated by the destination address is changed from the second network device to the third network device, the first network device re-establishes a new network device according to the attribute information, the destination address and the third network device reaching the second tunnel of the third network device, so as to use the second tunnel to forward the second packet to the third network device.

In a specific implementation manner, the method further includes: the first network device obtains a third packet, where the third packet includes attribute information and a destination address, the third packet belongs to service traffic, and the third packet The attribute information in the text is different from the attribute information in the first packet. The first network device establishes a third tunnel to the second network device according to the attribute information and the destination address, so as to use the third tunnel to forward the third packet to the second network device.

In this embodiment, when the attribute information corresponding to the service traffic changes, the first network device re-establishes a tunnel according to the updated attribute information and the destination address, so as to use the newly established tunnel to transmit the service traffic.

In a specific embodiment, the method further includes: the first network device reserves resources for the first tunnel according to the network slice information in the first packet.

In a specific implementation manner, the attribute information is carried in a priority field, a flow label field or a time-to-live field of the first packet.

In a specific embodiment, the first tunnel is a segment routing policy SR Policy tunnel or a segment routing traffic engineering SR TE tunnel.

In a second aspect of the embodiments of the present application, a message transmission system is provided, the system includes: a first network device and a second network device; the first network device is configured to acquire a first message, and the The first packet includes attribute information and a destination address, and the attribute information is used to indicate the service level agreement SLA requirements that need to be met when forwarding the service traffic to which the first packet belongs; the first network device is also used for Establish a first tunnel according to the attribute information and the destination address, or use the attribute information and the destination address to send a request message for establishing the first tunnel to the controller, where the first tunnel meets the SLA The required forwarding tunnel is used, and the first packet is forwarded to the second network device by using the first tunnel. The second network device is configured to receive the first packet.

In a specific implementation manner, the system further includes: a controller; the controller is configured to receive a request message for establishing the first tunnel sent by the first network device, and, according to the request information Obtain the information of the first tunnel; the controller is further configured to send a response message to the first network device, where the response message includes the attribute information and the destination address corresponding to the first tunnel information; the first network device, configured to establish the first tunnel according to the information of the first tunnel.

In a third aspect of the embodiments of the present application, a communication device is provided, the device includes: a processor and a memory; the memory is used to store instructions or computer programs; the processor is used to execute the memory in the memory. of the instructions or computer program to cause the communication device to perform the method of the first aspect.

In a fourth aspect of the embodiments of the present application, a computer-readable storage medium is provided, including instructions, which, when executed on a computer, cause the computer to execute the method described in the first aspect.

In a fifth aspect of the embodiments of the present application, a computer program is provided, which, when the program runs on a computer, causes the computer to execute the method described in the first aspect.

With the technical solutions provided in the embodiments of the present application, after acquiring the first packet, the first network device can establish, in real time, a first tunnel that meets the SLA requirements according to the attribute information and the destination address in the first packet, or, the first The network device sends a request message for establishing a first tunnel to the controller, so as to obtain information about the first tunnel from the controller, and then establish a first tunnel according to the information of the first tunnel, so as to use the first tunnel to forward the first packet to the second network device. It can be seen that the first network device can create tunnels on demand according to the SLA requirements corresponding to the service traffic, without the need for the first network device to create a tunnel in advance, which not only reduces the pressure and performance cost of the first network device, but also can meet the dynamic changes of the network system in time. .

Description of drawings

FIG. 1 is a structural diagram of a network system provided by an embodiment of the present application;

2 is a schematic diagram of an application scenario provided by an embodiment of the present application;

3 is a flowchart of a message transmission method provided by an embodiment of the present application;

FIG. 4 is a flowchart of another message transmission method provided by an embodiment of the present application;

FIG. 5 is a structural diagram of a message transmission apparatus provided by an embodiment of the present application;

FIG. 6 is a structural diagram of a network device provided by an embodiment of the present application;

FIG. 7 is another structural diagram of a network device provided by an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described implementation The examples are only a part of the embodiments of the present invention, but not all of the embodiments.

In order to facilitate the understanding of the technical solutions provided by the embodiments of the present application, the technologies and network elements involved in the embodiments of the present application will first be described below.

In some point-to-multipoint or multipoint-to-multipoint application scenarios, such as Layer 3 virtual private network (L3VPN) and virtual private lan service (VPLS), due to the access side (access, ACC) equipment If the number is too large (for example, M), and the transmitted traffic has different service level agreement (SLA) requirements (for example, the demand level is N), the provider edge (PE) equipment needs to go to each Tunnels on the ACC side that meet different SLA requirements reach the magnitude of M*N. The current implementation is that when a PE establishes a neighbor relationship with each ACC, it is created in advance based on a configuration or a tunnel creation policy. For example, as shown in FIG. 1 , it is described by taking as an example that there is one PE device and three ACC devices, which are ACC1 , ACC2 and ACC3 respectively. For example, if there are 3 different SLA requirements, then three tunnels with different SLA requirements are established between PE and ACC1, 3 tunnels with different SLA requirements are established with ACC2, and 3 different SLA tunnels are established with ACC3 Demand-level tunnels. Based on this, when there is traffic destined for different ACCs and different SLA requirements on the PE side, it can be forwarded based on the pre-created tunnel. However, since it is uncertain whether there will be traffic sent from PEs to ACCs, pre-creating tunnels not only wastes resources, but also puts enormous pressure on PEs. In addition, with the continuous development of the network, the software-defined network (SDN) is more and more inclined, and the network requires flexibility. The current implementation cannot meet the needs of creating tunnels on demand.

Based on this, an embodiment of the present application provides a packet transmission method, which is used to realize the purpose of creating a tunnel on demand according to traffic. Specifically, after acquiring the first packet in the service traffic, the first network device establishes the first tunnel according to the attribute information and the destination address in the first packet, or sends the information to the controller to establish the first tunnel by using the attribute information and the destination address. A tunnel request message, so that the controller obtains the information of the first tunnel according to the attribute information and the destination address, and then the first network device creates the first tunnel according to the information of the first tunnel. The attribute information is used to indicate an SLA requirement that needs to be met when forwarding the service traffic described in the first packet.

The tunnel refers to a forwarding path between two network devices, allowing service packets to be transmitted thereon. In the scenario described in the embodiment of this application, a network device may include multiple tunnels, and the multiple tunnels respectively correspond to multiple egress ports on the network device. Different tunnels may correspond to different network fragmentation resources respectively. In specific implementation, it can be divided into different tunnel types according to the protocol used to establish the tunnel, for example, segment routing policy (SR-Policy) tunnel, segment routing traffic engineering (SR-Policy) A TE) tunnel or a tunnel based on slice granularity, etc., the tunnel type is not specifically limited in this embodiment of the present application. The tunnel based on slice granularity may be a tunnel obtained according to a flexible-algorithm (Flex-Algo) mechanism or a flexible Ethernet (flex ethernet, FlexE) tunnel.

Referring to a schematic diagram of an application scenario shown in Fig. 2, in the network system, an example of including 5 network devices and 1 controller is used for description. Specifically, it includes a network device PE, a network device ACC1, a network device ACC2 and a network device ACC3, a network device P and a controller. Among them, one or more tunnels may be pre-established between PE and ACC1, and the two are end devices of the tunnel. Similarly, one or more tunnels can be pre-established between PE and ACC2, which are end devices of the tunnel, and one or more tunnels can be pre-established between PE and ACC3, which are end devices of the tunnel. The tunnel between PE1 and each ACC may be a tunnel of a general SLA requirement level, such as a segment routing best effort (SR-BE) tunnel. The first network device may be a PE device or a controller. Each of the above-mentioned network devices may be independent network devices, or may be functional modules with packet forwarding capability in a certain network device. For ease of understanding, the description will be given by taking each network device as an independent network device as an example. Wherein, each network device may also be referred to as a node, which is a device with a packet forwarding function in a network system, for example, may be a router, a switch, a repeater, or a label switching router (LSR), etc.

In this application scenario, there may be service traffic from PE to ACC1, and traffic from PE to ACC2 and ACC3. For ease of understanding, the following will take the service flow from the PE to the ACC1 as an example for description. In this embodiment, PE is the head node 201 , P is the intermediate node 202 , and ACC1 is the tail node 203 .

For the head node, in a possible situation, it may be the node that generates the first packet, that is, the head node may be the node indicated by the source address in the first packet. In this case, the head node is the first node on the end-to-end transmission path of the first packet, and the head node adds attribute information and a destination address when generating the packet.

In another possible situation, the source node on the end-to-end transmission path of the first packet is another node, and the head node is connected to the source node. After the head node receives the first packet sent by the source node, Add attribute information and destination address to the first packet. In this case, the head node may be the first tunnel end device on the end-to-end transmission path or may be the first end device on the end-to-end transmission path that needs to acquire the tunnel based on the attribute information and the destination address.

For the tail node, in one possible situation, it may be the node indicated by the destination address in the message; in another situation, it may be the access node corresponding to the node indicated by the destination address. The tail node may be the receiving end device of the tunnel on the end-to-end transmission path.

The intermediate node is a network device located in the tunnel between the head node and the tail node when the packet is forwarded.

For ease of understanding, the following description will be given by taking the network system shown in FIG. 2 as an example. Specifically, taking the PE sending service traffic to the ACC1 as an example, see FIG. 3 , which is a message transmission provided in this embodiment of the present application. The flow chart of the method is shown in Figure 3, and the method includes:

S301: The head node 201 obtains the first packet.

In this embodiment, when the head node 201 is the source node, the head node 201 may generate a first packet, where the first packet includes attribute information and a destination address. The attribute information is used to indicate the service level agreement SLA requirement that needs to be met for forwarding the service traffic to which the first packet belongs, that is, the service level of the service traffic. The SLA requirement is a constraint condition of the first tunnel, such as bandwidth, delay, and jitter rate required for forwarding service traffic, or any other possible reliability indicators, or a combination of indicators, and the like. When the head node 201 is an access device connected to the source node, the head node 201 may receive a first packet from the source node, and the source node adds attribute information and a destination address to the first packet. The first packet may also include network slice information, and the head node 201 may reserve resources for the first tunnel according to the network slice information, and the resources may be bandwidth, delay, quality of service (quality of service) allocated for service traffic service, QoS) queue, physical port, etc.

The destination address may be the address of the tail node 203 or the address of a node (eg, a user terminal) connected to the tail node 203 . In this case, the node indicated by the destination address accesses the network through the tail node 203 . The attribute information may be carried in a priority field, a flow label (flow label, FL) field, or a time to live (time to live, TTL) field, etc. of the first packet. Specifically, when the first packets are different types of packets, the priority fields are also different. For example, when the first packet is an internet protocol version 4 (IPv4) packet, there are three priority fields, which are the Layer 2-based code of service (CoS) field (IEEE802. 1p), the type of service (ToS) field based on the IP layer, and the differentiated services code point (DSCP) field based on the IP layer; when the first packet is Internet Protocol version 6 (internet protocol When the first packet is a multi-protocol label switching (MPLS) packet, the attribute information can be carried in the traffic class (TC) field, etc. It can be carried in the EXP field, etc.

S302: The head node 201 establishes a first tunnel according to the attribute information and the destination address.

After obtaining the first packet, the head node 201 can perform a route search on the forwarding plane based on the attribute information and the destination address in the first packet. When the SLA level indicated by the attribute information belongs to the high guarantee level, the The forwarding plane does not store the tunnel that reaches the tail node 203 and meets the SLA requirements, that is, the first tunnel. Among them, the forwarding plane of the head node 201 does not store the first tunnel, there may be the following situations. One is that the head node 201 has established the first tunnel on the control plane, but has not delivered it to the forwarding plane; the other is that the head node 201 has established the first tunnel on the control plane. The control plane does not establish the first tunnel. The head node 201 is an ingress network device of the first tunnel.

In the case that the control plane of the head node 201 has established the first tunnel and has not delivered it to the forwarding plane, the head node 201 searches locally and obtains the first tunnel according to the attribute information and the destination address. Specifically, the head node 201 may search for and acquire the first tunnel according to the locally stored correspondence table, attribute information and destination address, wherein the correspondence table includes the correspondence between the attribute information, the destination address and the first tunnel. After acquiring the first tunnel, the head node 201 sends the information of the first tunnel from the control plane to the forwarding plane. Wherein, the information of the first tunnel may include node information of the tunnel path, tunnel priority level, network equipment at the exit of the tunnel, and the like. In this case, the first tunnel may be created manually or acquired by the head node 201 from the controller.

When the control plane of the head node 201 has not established the first tunnel, and the head node 201 has the capability to calculate and create the tunnel, the head node 201 can create the first tunnel according to the attribute information and the destination address; after the creation is completed, the head node 201 will Information about a tunnel is sent from the control plane to the forwarding plane. Specifically, the head node 201 may calculate the first tunnel based on a preconfigured tunnel policy template to obtain the information of the first tunnel. Wherein, different SLAs and different destination addresses may correspond to different tunnel policy templates, and the tunnel policy templates are used to constrain the establishment of the tunnel, so that the established tunnel meets the SLA requirements.

In an implementation manner, when the destination address is a private network address, that is, when the network device indicated by the destination address accesses the network through the tail node 203 , the egress network device of the first tunnel is the tail node 203 . In order to establish the first tunnel to reach the tail node 203, the head node 201 can determine, according to the destination address, the identity of the virtual private network identity (virtual private network, VPN) to which the network device indicated by the destination address belongs, and then search according to the VPN identity. The corresponding access node, that is, the tail node 203 , and obtains the address of the tail node 203 . In this case, the head node 201 determines the matching tunnel policy template according to the attribute information, the VPN identifier and the address of the tail node 203, and then determines the information of the first tunnel according to the tunnel policy template. The tunnel policy template can provide different policy templates for different VPN users. For example, for a user of VPN A, for a packet with a DSCP value of 11-20, a tunnel or slice with a bandwidth of 1000M and a delay of 200ms is provided; for a packet with a DSCP value of 21-30, a bandwidth of 1000M, Tunnels or slices with a delay of 400ms, etc. For users of VPN B, a packet with a DSCP value of 11-20 provides a tunnel or slice with a bandwidth of 1000M and no delay requirement; for a packet with a DSCP value of 21-30, a packet with no bandwidth requirement and no delay is provided. For 400ms tunnels or slices etc. The address of the tail node 203 may be a loopback address, a locator address, or the like of the tail node 203 .

It should be noted that, in the case where the head node 201 has the tunnel calculation and creation capability, after the head node 201 has established the first tunnel, it can directly execute S306, and use the first tunnel to forward the first packet to the second network device without the need for S303 is executed. In the case that the head node 201 does not have the tunnel calculation and creation capability, before executing S302 to establish the tunnel, S303 may be executed first to trigger the controller to execute S304 and S305.

S303: The head node 201 sends a request message for establishing the first tunnel to the controller by using the attribute information and the destination address.

When the head node 201 cannot independently create the first tunnel, the head node 201 can use the attribute information and the destination address to send a request message for establishing the first tunnel to the controller, and the request message can include the attribute information and the destination address to request the controller Calculate the information of the first tunnel. Further, the request message may further include the device identifier of the head node 201, so that the controller can know the device sending the request message, and then establish the first tunnel with the head node 201 as the ingress network device. The device identifier of the head node 201 may be the IP address of the head node 201, the loopback address, etc., which may uniquely represent the identifier of the head node 201.

S304: The controller obtains the information of the first tunnel according to the attribute information and the destination address.

After receiving the request message sent by the head node 201, the controller obtains the information of the first tunnel according to the attribute information and the destination address in the request message. Specifically, in an example, the controller may search and acquire the information of the first tunnel locally according to the attribute information and the destination address. In another example, when the controller does not find the information of the first tunnel according to the attribute information and the destination address, it can calculate and acquire the information of the first tunnel according to the attribute information and the destination address. In this case, the controller may determine the matching tunnel policy template from the preconfigured tunnel policy template according to the attribute information and the destination address, and perform path calculation according to the matched tunnel policy template, thereby obtaining the information of the first tunnel. For the implementation of tunnel path calculation of corresponding SLA by using the tunnel policy template, reference may be made to the relevant description of S203.

It can be seen from the foregoing that there are two different situations for the network device indicated by the destination address. One case is that when the network device indicated by the destination address is the tail node 203, the head node 201 can directly convert the attribute information and the destination address. The request message is sent to the controller. In this case, the controller may search the information of the first tunnel or calculate the information of the first tunnel according to the attribute information and the destination address in the request message. In another case, when the network device indicated by the destination address accesses the network through the tail node 203, that is, the destination address is the private network address, if the head node 201 directly sends the request message including the attribute information and the destination address to the control When the controller is used, the controller also needs to determine the address of the tail node 203 according to the identity of the VPN to which the network device indicated by the destination address belongs, and then searches for the information of the first tunnel or calculates the first tunnel according to the attribute information, the VPN identity, and the address of the tail node 203. information about the tunnel. Specifically, the controller determines the matching tunnel policy template according to the attribute information, the VPN identifier and the address of the tail node 203, and then determines the information of the first tunnel according to the tunnel policy template. Wherein, for the information that the controller calculates the first tunnel according to the attribute information, the VPN identifier and the address of the tail node 203, reference may be made to the relevant description of S203.

S305: The controller sends a response message including the information of the first tunnel to the head node 201.

After the controller acquires the information of the first tunnel, it sends a response message including the information of the first tunnel to the head node 201, so that the head node 201 creates the first tunnel according to the information of the first tunnel.

In a specific implementation manner, in addition to delivering the information of the first tunnel to the head node 201, the controller may also deliver a resource reservation request to each required node included in the first tunnel, so that the first Each node along the tunnel can reserve resources. The reserved resources may be bandwidths, time slots, quality of service (quality of service, QoS) queues, physical ports, etc. allocated for service traffic.

S306: The head node 201 forwards the first packet to the intermediate node 202 by using the first tunnel.

After receiving the information of the first tunnel sent by the controller, the head node 201 creates a first tunnel according to the information of the first tunnel, and forwards the service traffic to the intermediate node 202 by using the first tunnel. It should be noted that, in order to ensure the normal transmission of the service traffic, before creating the first tunnel, the head node 201 may forward the service traffic to the intermediate node 202 by using the currently established tunnel.

In some application scenarios, the first tunnel may not carry traffic for a long time. In order to reduce the occupation of resources, the head node 201 may detect the carrying condition of the first tunnel. For forwarding packets, delete the first tunnel or change the status to unavailable. The preset duration may be determined according to actual application conditions, for example, the preset duration is 1 hour. Specifically, the head node 201 deletes the first tunnel on the forwarding plane; or, the head node 201 marks the first tunnel as unavailable on the forwarding plane; or the head node 201 marks the first tunnel as unavailable on the control plane, and deletes the first tunnel on the forwarding plane a tunnel; or the head node 201 deletes the first tunnel on the control plane and the forwarding plane at the same time. The head node 201 may configure different processing policies, and process the first tunnel based on the current processing policy.

In some application scenarios, there is a situation in which the access device corresponding to the network device in the private network migrates. For example, in Figure 2, the device corresponding to the access network of the network device indicated by the destination address migrates from ACC1 to ACC2, that is, The tail node 203 is changed from ACC1 to ACC2. In this case, after receiving the second packet belonging to the service flow, the head node 201 establishes a second tunnel to the updated tail node 203 according to the attribute information and the destination address in the second packet; The second tunnel forwards the second packet to the tail node 203 . Wherein, for the implementation of the establishment of the second tunnel by the head node 201 to the updated tail node 202 according to the attribute information and the destination address, reference may be made to the relevant descriptions of S302-S306.

In some application scenarios, there may also be changes in attribute information corresponding to service traffic, such as a decrease or increase in the SLA requirement level. In this case, after receiving the third packet belonging to the service traffic, the head node 201 establishes a third tunnel to the tail node according to the attribute information and the destination address in the third packet, wherein the third packet carries Compared with the first packet, the attribute information of the packet has changed; the head node 201 forwards the third packet to the tail node 203 by using the third tunnel. Wherein, for the implementation of the establishment of the third tunnel by the head node 201 according to the attribute information and the destination address, reference may be made to the relevant descriptions of S302-S306.

S307: The intermediate node 202 forwards the first packet to the tail node 203 by using the first tunnel.

After receiving the first packet, the intermediate node 202 forwards the first packet to the tail node 203 according to the created first tunnel. After receiving the first packet forwarded by the intermediate node 202, the tail node 203 can perform different processing in different application scenarios. Specifically, the following operations can be included:

In one case, the tail node 203 no longer forwards the packet after receiving the packet. For example, when the tail node 203 is the network device indicated by the destination address, the tail node 203 may only receive the packet without forwarding it.

In another case, for example, when the network device indicated by the destination address is the user equipment connected by the tail node 204, the tail node 204 can pop up the attribute information in the first packet, and the first packet that does not include the attribute information can be ejected. The message is forwarded to the user equipment.

It can be understood that the above situation is only an example, and the processing operation performed by the tail node 203 on the packet may be determined in combination with a specific application scenario.

In order to reflect the continuity of the transmission of packets (such as the first packet and the second packet mentioned above), in this embodiment of the present application, the first packet sent by the head node 201 to the intermediate node 202 and the intermediate node 202 The first packet sent to the tail node 203 is called the first packet, but it is understandable that the first packet sent by the head node 201 to the intermediate node 202 and the first packet sent by the intermediate node 202 to the tail node 203 There are differences in practical application scenarios. For example, there may be differences in information such as time to live (TTL) and the next hop node, that is, when the intermediate node 202 forwards the first packet sent by the head node 201 to the tail node 203, it can actually modify the The updated first message with some necessary information. The first packet sent by the head node 201 and the updated first packet sent by the intermediate node 202 may carry the same payload (payload), attribute information and destination address.

It can be seen from the above that, as the ingress network device of the first tunnel, the head node can dynamically trigger the creation or take effect of the tunnel based on the service traffic. It is not necessary to create all the tunnels required by the SLA in advance. The need for live device migration.

To facilitate further understanding of the technical solutions provided by the embodiments of the present application, see FIG. 4 , which is a flowchart of another message transmission method provided by the embodiments of the present application. As shown in FIG. 4 , the method may include:

S401: The first network device obtains the first packet.

In this embodiment, the first network device may be a head node, which may generate the first packet, or obtain the first packet from its corresponding user equipment. The first packet includes attribute information and a destination address, and the attribute information is used to indicate an SLA requirement that needs to be met when forwarding the service traffic to which the first packet belongs. The attribute information may be carried in the priority field, flow label field or time-to-live field of the first packet. As a specific implementation of the first network device acquiring the first packet, reference may be made to S301.

S402: The first network device establishes a first tunnel according to the attribute information and the destination address.

After the first network device obtains the first packet, it obtains attribute information and a destination address by parsing the first packet, and judges whether there is a tunnel that meets the SLA requirements, that is, the first tunnel, according to the attribute information and the destination address, so as to pass the first tunnel. The tunnel forwards the first packet to the second network device. After the first network device determines that the first tunnel does not exist, the first tunnel may be established according to the attribute information and the destination address. The first tunnel is a forwarding tunnel that meets the SLA requirements, and is used to forward the first packet to the second network device. The second network device is determined according to the destination address. The first network device may be an ingress network device of the first tunnel, and the second network device may be an egress network device of the first tunnel. The second network device may be the device indicated by the destination address, or the second network device may be a device for connecting the destination device indicated by the destination address to the network. In addition, the first packet may further include network slice information, and the first network device may reserve resources for the first tunnel according to the network slice information. The first tunnel may be an SR Policy tunnel, an SR TE tunnel, or a tunnel based on slice granularity.

In an example, the first network device creates the first tunnel according to the attribute information and the destination address. That is, when the first network device has the ability to create a tunnel, it can independently create the first tunnel according to the attribute information and the destination address. After the first tunnel is created, the first network device sends the information of the first tunnel from the control plane of the first network device to the forwarding plane, and then forwards the first packet to the second network device through the forwarding plane. As a specific implementation for the first network device to create the first tunnel according to the attribute information and the destination address, reference may be made to S302.

In another example, the first network device searches and obtains the first tunnel locally according to the attribute information and the destination address. After acquiring the information of the first tunnel, the first network device sends the information of the first tunnel from the control plane of the first network device to the forwarding plane. For a specific implementation of the first network device searching and acquiring the first tunnel locally according to the attribute information and the destination address, for example, reference may be made to S302.

S403: The first network device sends a request message for establishing the first tunnel to the controller by using the attribute information and the destination address.

In this embodiment, after determining that there is no tunnel that meets the SLA requirement, the first network device may also send a request message for establishing the first tunnel to the control, where the request message may include attribute information and a destination address. Further, the request message may further include the device identifier of the first network device, so that the controller can know the network device that sends the request message. For a specific implementation of S403, for example, reference may be made to S303.

S404: The controller obtains the information of the first tunnel according to the request message.

In this embodiment, after receiving the request message, the controller may acquire the information of the first tunnel according to the attribute information and the destination address in the request message. Specifically, the controller may determine the matching tunnel policy template according to the attribute information and the destination address, and obtain the information of the first tunnel according to the tunnel policy template. Wherein, as an implementation for the controller to acquire the information of the first tunnel, reference may be made to S304.

S405: The controller sends a response message to the first network device.

After acquiring the information of the first tunnel, the controller sends a response message to the first network device, where the response message includes the information of the first tunnel corresponding to the attribute information and the destination address. For a specific implementation of S405, for example, reference may be made to S305.

S406: The first network device creates a first tunnel according to the information of the first tunnel, and forwards the first packet to the second network device by using the first tunnel.

For a specific implementation of S405, reference may be made to S306.

In a specific implementation manner, the first network device may further delete the first tunnel or change the state to unavailable when it is determined that the first tunnel is not used for forwarding packets within a preset period of time. For the processing implementation of the first tunnel by the first network device, reference may be made to the relevant description in S306.

In a specific implementation manner, when the corresponding device changes when the destination device indicated by the destination address in the packet accesses the network, the first network device will re-establish the tunnel according to the attribute information and the destination address in the packet , to use the newly created tunnel to forward service traffic. Specifically, the first network device receives a second packet, where the second packet includes attribute information and a destination address, and the second packet and the first packet belong to the same service flow; The indicated destination device accessing the network is changed from the second network device to the third network, the attribute information and the destination address establish a second tunnel to the third network device; the first network device uses the second tunnel to transfer the second packet Forwarded to the third network device. Wherein, as a specific implementation of establishing the second tunnel by the first network device, for example, reference may be made to S402-406.

Based on the foregoing method embodiments, the embodiments of the present application further provide a message transmission device, which will be described below with reference to the accompanying drawings.

Referring to FIG. 5 , which is a structural diagram of a message transmission apparatus provided by an embodiment of the present application, the apparatus 500 can be applied to a first network device to implement the functions of the first network device in the foregoing method embodiments, and the apparatus 500 may include : obtaining unit 501 , establishing unit 502 and sending unit 503 .

The obtaining unit 501 is configured to obtain a first packet, where the first packet includes attribute information and a destination address, and the attribute information is used to indicate a service level that needs to be met when forwarding the service traffic to which the first packet belongs Agreement SLA requirements.

For the specific implementation of the acquisition unit 501 acquiring the first packet, reference may be made to the relevant description of S301 or S401.

The establishing unit 502 is configured to establish a first tunnel according to the attribute information and the destination address.

The specific implementation of establishing the first tunnel by the establishing unit 502 may refer to the relevant description of S302 or S402.

The sending unit 503 is configured to use the attribute information and the destination address to send a request message for establishing the first tunnel to the controller, where the first tunnel is a forwarding tunnel that meets the SLA requirements, and is used to transfer the first tunnel to the controller. The first packet is forwarded to the second network device, and the second network device determines the destination address according to the destination address.

The specific implementation of the sending unit 503 may refer to the relevant description of S303 or S403.

In a specific implementation manner, the establishing unit 502 is specifically configured to create the first tunnel according to the attribute information and the destination address; or, search locally according to the attribute information and the destination address and get the first tunnel.

The specific implementation of the establishing unit 502 may refer to the relevant description of S302 or S402.

In a specific implementation manner, the sending unit 503 is further configured to send the information of the first tunnel from the control plane to the forwarding plane.

In a specific implementation manner, the apparatus further includes: a receiving unit (not shown in the figure);

The receiving unit is configured to receive a response message sent by the controller, where the response message includes information of the first tunnel corresponding to the attribute information and the destination address.

In a specific implementation manner, the apparatus further includes: a processing unit (not shown in the figure)

The processing unit is configured to delete the first tunnel or change the state to unused after determining that the first tunnel is not used for forwarding packets within the preset time period.

In a specific implementation manner, the network device applied by the apparatus 500 is the ingress network device of the first tunnel.

In a specific implementation manner, the obtaining unit 501 is further configured to obtain a second packet, where the second packet includes the attribute information and the destination address, and the second packet belongs to the service traffic ;

The establishing unit 502 is further configured to change from the second network device to the third network device, the attribute information and the destination address according to the device for accessing the network of the destination device indicated by the destination address. the second tunnel of the third network device;

The sending unit 503 is configured to forward the second packet to the third network device by using the second tunnel.

For the implementation of establishing the second tunnel by the establishing unit 502, reference may be made to the relevant description of S306 or S406.

In a specific implementation manner, the apparatus further includes: a processing unit (not shown in the figure);

A processing unit, configured to reserve resources for the first tunnel according to the network slice information in the first packet.

It should be noted that, for specific executable functions and implementations of the message transmission apparatus 500 , reference may be made to the corresponding description of the first network device in the embodiment shown in FIG. 3 or FIG. 4 , and details are not repeated here.

FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application. The network device may be, for example, the first network device or the second network device in the embodiment shown in FIG. 3 or FIG. 4 , or may also be the first network device in FIG. 5 . The device implementation of the message transmission apparatus 500 in the illustrated embodiment.

Referring to FIG. 6 , the network device 600 includes: a processor 610 , a communication interface 620 and a memory 630 . The number of processors 610 in the packet forwarding device 600 may be one or more, and one processor is taken as an example in FIG. 6 . In this embodiment of the present application, the processor 610, the communication interface 620, and the memory 630 may be connected through a bus system or other manners, wherein the connection through the bus system 640 is taken as an example in FIG. 6 .

Processor 610 may be a CPU, NP, or a combination of CPU and NP. The processor 610 may further include hardware chips. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (generic array logic, GAL) or any combination thereof.

When the network device is the head node 201, the processor 610 may perform related functions such as acquiring the first packet and establishing the first tunnel according to the attribute information and the destination address in the foregoing method embodiments.

The communication interface 620 is used for receiving and sending messages. Specifically, the communication interface 620 may include a receiving interface and a sending interface. The receiving interface may be used to receive packets, and the sending interface may be used to send packets. The number of communication interfaces 620 may be one or more.

The memory 630 may include a volatile memory (English: volatile memory), such as random-access memory (RAM); the memory 630 may also include a non-volatile memory (English: non-volatile memory), such as a fast memory A flash memory (English: flash memory), a hard disk drive (HDD) or a solid-state drive (SSD); the memory 630 may also include a combination of the above-mentioned types of memory. The memory 630 may store, for example, the aforementioned attribute information, the correspondence between the destination address and the tunnel.

Optionally, the memory 630 stores an operating system and programs, executable modules or data structures, or their subsets, or their extended sets, wherein the programs may include various operation instructions for implementing various operations. The operating system may include various system programs for implementing various basic services and handling hardware-based tasks. The processor 610 may read the program in the memory 630 to implement the message transmission method provided by the embodiment of the present application.

The memory 630 may be a storage device in the network device 600 , or may be a storage device independent of the network device 600 .

The bus system 640 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus or the like. The bus system 640 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.

FIG. 7 is a schematic structural diagram of another network device 700 provided by an embodiment of the present application. The network device 700 may be configured as the first network device or the second network device in the foregoing embodiments, or the network device in the embodiment shown in FIG. 5 . Device implementation of the message transmission apparatus 500 .

The network device 700 includes: a main control board 710 and an interface board 730 .

The main control board 710 is also called the main processing unit (main processing unit, MPU) or the route processor card (route processor card). The main control board 710 controls and manages various components in the network device 700, including route calculation, Equipment maintenance, protocol processing functions. The main control board 710 includes: a central processing unit 711 and a memory 712 .

The interface board 730 is also referred to as a line processing unit (LPU), a line card or a service board. The interface board 730 is used to provide various service interfaces and realize data packet forwarding. The service interface includes, but is not limited to, an Ethernet interface, a POS (Packet over SONET/SDH) interface, etc. The Ethernet interface is, for example, a flexible Ethernet service interface (Flexible Ethernet Clients, FlexE Clients). The interface board 730 includes: a central processing unit 731 , a network processor 732 , a forwarding table entry memory 734 and a physical interface card (ph8sical interface card, PIC) 733 .

The central processing unit 731 on the interface board 730 is used to control and manage the interface board 730 and communicate with the central processing unit 711 on the main control board 710 .

The network processor 732 is used to implement packet forwarding processing. The network processor 732 may be in the form of a forwarding chip. Specifically, the processing of the uplink packet includes: processing of the incoming interface of the packet, and searching of the forwarding table; processing of the downlink packet: searching of the forwarding table, and so on.

The physical interface card 733 is used to realize the interconnection function of the physical layer, the original traffic enters the interface board 730 through this, and the processed packets are sent from the physical interface card 733 . The physical interface card 733 includes at least one physical interface, and the physical interface is also called a physical port. The physical interface card 733 corresponds to the FlexE physical interface 204 in the system architecture 200 . The physical interface card 733 is also called a daughter card, which can be installed on the interface board 730 , and is responsible for converting the photoelectric signal into a message, checking the validity of the message and forwarding it to the network processor 732 for processing. In some embodiments, the central processor 731 of the interface board 703 can also perform the functions of the network processor 732 , such as implementing software forwarding based on a general-purpose CPU, so that the network processor 732 is not required in the physical interface card 733 .

Optionally, the network device 700 includes multiple interface boards, for example, the network device 700 further includes an interface board 740, and the interface board 740 includes: a central processing unit 741, a network processor 742, a forwarding table entry storage 744, and a physical interface card 743.

Optionally, the network device 700 further includes a switch fabric board 720 . The switch fabric unit 720 may also be referred to as a switch fabric unit (switch fabric unit, SFU). In the case that the network device has multiple interface boards 730, the switching network board 720 is used to complete data exchange between the interface boards. For example, the interface board 730 and the interface board 740 can communicate through the switch fabric board 720 .

The main control board 710 and the interface board 730 are coupled. E.g. The main control board 710 , the interface board 730 , the interface board 740 , and the switch fabric board 720 are connected to the system backplane through a system bus to achieve intercommunication. In a possible implementation manner, an inter-process communication (IPC) channel is established between the main control board 710 and the interface board 730, and the main control board 710 and the interface board 730 communicate through the IPC channel.

Logically, the network device 700 includes a control plane and a forwarding plane, the control plane includes a main control board 710 and a central processing unit 731, and the forwarding plane includes various components that perform forwarding, such as forwarding entry storage 734, physical interface card 733, and network processing device 732. The control plane performs functions such as routers, generating forwarding tables, processing signaling and protocol packets, and configuring and maintaining the status of devices. The control plane issues the generated forwarding tables to the forwarding plane. On the forwarding plane, the network processor 732 is based on the control plane. The delivered forwarding table forwards the packets received by the physical interface card 733 by looking up the table. The forwarding table issued by the control plane may be stored in the forwarding table entry storage 734 . In some embodiments, the control plane and forwarding plane may be completely separate and not on the same device.

If the network device 700 is configured as the first network device, the central processing unit 711 may acquire the first packet; and establish the first tunnel according to the attribute information and the destination address in the first packet. The network processor 732 may trigger the physical interface card 733 to send the first packet to the second network device according to the determined first tunnel.

It should be understood that the sending unit 503 and the like in the message transmission apparatus 500 may be equivalent to the physical interface card 733 or the physical interface card 743 in the network device 700; the acquiring unit 501 and the establishing unit 502 and the like in the message transmission apparatus 500 may be equivalent to The central processing unit 711 or the central processing unit 731 in the network device 700 .

It should be understood that the operations on the interface board 740 in the embodiments of the present application are the same as the operations on the interface board 730 , and for brevity, details are not repeated here. It should be understood that the network device 700 in this embodiment may correspond to the first network device or the second network device in the foregoing method embodiments, and the main control board 710 , the interface board 730 and/or the interface board 740 in the network device 700 The functions and/or various steps performed by the first network device or the second network device in the foregoing method embodiments can be implemented, which are not repeated here for brevity.

It should be understood that there may be one or more main control boards, and when there are more than one main control board, it may include an active main control board and a backup main control board. There may be one or more interface boards. The stronger the data processing capability of the network device, the more interface boards are provided. There can also be one or more physical interface cards on the interface board. There may be no switch fabric boards, or there may be one or more boards. When there are multiple boards, load sharing and redundancy backup can be implemented together. Under the centralized forwarding architecture, the network device does not need to switch the network board, and the interface board is responsible for the processing function of the service data of the entire system. Under the distributed forwarding architecture, a network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices in a distributed architecture are greater than those in a centralized architecture. Optionally, the form of the network device can also be that there is only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on this board. The central processing unit on the board can be combined into a central processing unit on this board to perform the functions of the two superimposed, the data exchange and processing capacity of this form of equipment is low (for example, low-end switches or routers and other networks. equipment). The specific architecture used depends on the specific networking deployment scenario.

In some possible embodiments, the above-mentioned first network device or second network device may be implemented as a virtualized device. For example, the virtualization device may be a virtual machine (English: Virtual Machine, VM) running a program for sending a message, and the virtual machine is deployed on a hardware device (for example, a physical server). A virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment. The virtual machine can be configured as a first network device or a second network device. For example, the first network device or the second network device may be implemented based on a general physical server in combination with a network function virtualization (Network Functions Virtualization, NFV) technology. The first network device or the second network device is a virtual host, a virtual router or a virtual switch. Those skilled in the art can virtualize a first network device or a second network device having the above functions on a general physical server in combination with the NFV technology by reading this application, and details are not described herein again.

It should be understood that the network devices in the above-mentioned various product forms respectively have any functions of the first network device or the second network device in the above method embodiments, and details are not described herein again.

An embodiment of the present application also provides a chip, including a processor and an interface circuit, where the interface circuit is used to receive instructions and transmit them to the processor; the processor, for example, may be one of the message transmission apparatuses 500 shown in FIG. 5 . The specific implementation form can be used to execute the above method for message transmission. The processor is coupled to a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the chip system enables the method in any of the foregoing method embodiments.

Optionally, the number of processors in the chip system may be one or more. The processor can be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software codes stored in memory.

Optionally, the number of memories in the chip system may also be one or more. The memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application. Exemplarily, the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be provided on different chips. The setting method of the processor is not particularly limited.

Exemplarily, the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller). controller unit, MCU), it can also be a programmable logic device (PLD) or other integrated chips.

Based on the foregoing method embodiments, the embodiments of the present application further provide a message transmission system, and the system may include: a first network device and a second network device.

The first network device is used to obtain a first packet, where the first packet includes attribute information and a destination address, and the attribute information is used to indicate that the service traffic to which the first packet belongs is forwarded and needs to meet the Service Level Agreement SLA requirements.

For the specific implementation of acquiring the first packet by the first network device, reference may be made to the relevant description of S401.

The first network device is further configured to establish a first tunnel according to the attribute information and the destination address, or send a request message for establishing the first tunnel to the controller by using the attribute information and the destination address, The first tunnel is a forwarding tunnel that meets the SLA requirement.

For the specific implementation of establishing the first tunnel by the first network device, reference may be made to the relevant description of S402.

The first network device is further configured to forward the first packet to the second network device by using the first tunnel.

It should be noted that, for the function or implementation performed by the first network device, reference may be made to the relevant description of the first network device in the embodiment shown in FIG. 4 .

In a specific embodiment, the system further includes: a controller;

the controller, configured to receive a request message for establishing the first tunnel sent by the first network device, and determine the first tunnel according to the request information;

The controller is further configured to send a response message to the first network device, where the response message includes the information of the first tunnel corresponding to the attribute information and the destination address;

The first network device is configured to establish the first tunnel according to the information of the first tunnel.

For the function or implementation performed by the controller, reference may be made to the relevant description of the controller in the embodiment shown in FIG. 3 or FIG. 4 .

Embodiments of the present application also provide a computer-readable storage medium, including instructions or computer programs, which, when executed on a computer, cause the computer to execute the message transmission method provided by the above embodiments.

The embodiments of the present application also provide a computer program product including an instruction or a computer program, which, when running on a computer, enables the computer to execute the message transmission method provided by the above embodiments.

The terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances such that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of units is only a logical business division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each service unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, 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 may be implemented in the form of a software business unit.

The integrated unit, if implemented as a software business unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art, or all or part of the technical solutions, which are stored in a storage medium. , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Those skilled in the art should realize that, in one or more of the above examples, the services described in the present invention may be implemented by hardware, software, firmware or any combination thereof. When implemented in software, the services may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

The above specific embodiments further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific embodiments of the present invention.

Above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be used for the foregoing implementations. The technical solutions described in the examples are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

A message transmission method, characterized in that the method comprises:

The first network device obtains a first packet, where the first packet includes attribute information and a destination address, and the attribute information is used to indicate a service level agreement SLA that needs to be satisfied when forwarding the service traffic to which the first packet belongs Require;

The first network device establishes a first tunnel according to the attribute information and the destination address, or the first network device sends a request for establishing the first tunnel to the controller by using the attribute information and the destination address message, the first tunnel is a forwarding tunnel that meets the SLA requirement, and is used to forward the first packet to a second network device, where the second network device determines according to the destination address.
The method according to claim 1, wherein the first network device establishes a first tunnel according to the attribute information and the destination address, comprising:

The first network device creates the first tunnel according to the attribute information and the destination address; or,

The first network device searches and acquires the first tunnel locally according to the attribute information and the destination address.
The method according to claim 2, wherein the method further comprises:

The first network device sends the information of the first tunnel from the control plane of the first network device to the forwarding plane.
The method according to claim 1, wherein after the first network device sends a request message for establishing the first tunnel to a controller by using the attribute information and the destination address, the method comprises:

The first network device receives a response message sent by the controller, where the response message includes information of the first tunnel corresponding to the attribute information and the destination address.
The method according to any one of claims 1-4, wherein the method further comprises:

The first network device determines that the first tunnel is not used for forwarding packets within a preset period of time, and deletes the first tunnel or changes the state to not used.
The method according to any one of claims 1-5, wherein the first network device is an ingress network device of the first tunnel.
The method according to any one of claims 1-6, wherein the egress network device of the first tunnel is a second network device, and the second network device is a device corresponding to the destination address, or all The second network device is a device for connecting the destination device indicated by the destination address to the network.
The method according to claim 7, wherein the method further comprises:

obtaining, by the first network device, a second packet, where the second packet includes the attribute information and the destination address, and the second packet belongs to the service traffic;

The first network device is used to change the device for accessing the network indicated by the destination address from the second network device to the third network device, the attribute information and the destination address to establish and reach the destination address. the second tunnel of the third network device;

The first network device forwards the second packet to the third network device using the second tunnel.
The method according to any one of claims 1-8, wherein the method further comprises:

The first network device reserves resources for the first tunnel according to the network slice information in the first packet.
The method according to any one of claims 1-9, wherein the attribute information is carried in a priority field, a flow label field or a time-to-live field of the first packet.
The method according to any one of claims 1-10, wherein the first tunnel is a segment routing policy SR Policy tunnel or a segment routing traffic engineering SR TE tunnel.
A message transmission system, characterized in that the system includes: a first network device and a second network device;

The first network device is configured to obtain a first packet, where the first packet includes attribute information and a destination address, and the attribute information is used to indicate that the service traffic to which the first packet belongs is forwarded. service level agreement SLA requirements;

The first network device is further configured to establish a first tunnel according to the attribute information and the destination address, or send a request message for establishing the first tunnel to the controller by using the attribute information and the destination address, The first tunnel is a forwarding tunnel that meets the SLA requirement, and the first packet is forwarded to the second network device by using the first tunnel;

The second network device is configured to receive the first packet.
The system of claim 12, wherein the system further comprises: a controller;

the controller, configured to receive a request message for establishing the first tunnel sent by the first network device, and acquire information of the first tunnel according to the request information;

The controller is further configured to send a response message to the first network device, where the response message includes the information of the first tunnel corresponding to the attribute information and the destination address;

The first network device is configured to establish the first tunnel according to the information of the first tunnel.
A communication device comprising: a processor and a memory;

the memory for storing instructions or computer programs;

The processor is configured to execute the instructions or computer program in the memory, so that the communication device executes the method of any one of claims 1-11.
A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1-11 above.