A message transmission method and related device

Abstract

The application discloses a message transmission method and related equipment. A first pseudo wire (PW) is established between a first node and a second node. The first node acquires a first service message, performs SRv6 encapsulation on the first service message to obtain a second service message, and the second service message comprises the first service message and information of the first PW. The first node sends the second service message to the second node through the first PW. After receiving the second service message, the second node performs SRv6 decapsulation on the second service message to obtain the first service message. It can be seen that the entry PE device can perform SRv6 encapsulation on the PW service, encapsulate the information describing the PW and the service message to be transmitted into the actual service message to be transmitted, the exit PE device performs SRv6 decapsulation on the service message received through the PW to obtain the service message to be transmitted, the PW simulation service of various services is conveniently and quickly completed, and the transmission of the service message in the SRv6 network is realized.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and related equipment for message transmission. Background Technology

[0002] A pseudowire (PW) is a point-to-point connection established between provider edge (PE) devices. In IP packet networks, PWs are tunneled and encapsulated. Various emulated service packets (such as Frame Relay, Time Division Multiplexing (TDM), and Asynchronous Transfer Mode (ATM) services) are encapsulated into packet data at the PW's ingress PE device and transmitted transparently through the PW (i.e., intermediate devices on the PW do not modify the transmitted packet data). After transmission to the PW's egress PE device, the egress PE device restores the packet data to its original service message, thus emulating various services.

[0003] With the development of Segment Routing over Internet Protocol version 6 (SRv6) networks, there is a need to implement pseudowire emulation for SRv6 networks, so as to facilitate and quickly complete the transmission of messages for various services. Summary of the Invention

[0004] Based on this, embodiments of this application provide a method and related equipment for message transmission, enabling fast and convenient PW emulation for various services, and providing PW emulation services suitable for SRv6 networks.

[0005] Firstly, this application provides a method for message transmission, executed by a first node, where a first pseudowire (PW) is established between the first node and a second node. This method may include, for example, the first node acquiring a first service message, encapsulating the first service message using SRv6 to obtain a second service message, the second service message including the first service message and information from the first PW; thus, the first node can send the second service message to the second node through the first PW. It is evident that this method, by defining processing mechanisms corresponding to the PW on the PE devices at both ends of the PW, enables the ingress PE devices to perform SRv6 encapsulation on the PW service, encapsulating the information describing the PW and the service message to be transmitted into the actual transmitted service message. The egress PE devices then decapsulate the service message received through the PW using SRv6 to obtain the aforementioned service message to be transmitted. This process uses only IP and does not involve multi-protocol nesting to achieve the transmission of service messages in the SRv6 network, thereby conveniently and quickly completing PW emulation services for various services.

[0006] As an example, the first node performs SRv6 encapsulation on the first service packet. This could include, for instance, encapsulating a Segment Routing Header (SRH) outside the first service packet, where the SRH includes the segment list corresponding to the first PW. In this way, since the segment list in the second service packet corresponds to the first PW, it can be guaranteed that the first node forwards the second service packet to the second node via the first PW.

[0007] In one implementation, the method may further include: a first node determining that the first service packet matches an SR policy. Specifically, the first node may store the correspondence between interfaces and PWs. When the first node receives the first service packet, it can determine, based on the interface through which the first node receives the first service packet, that the first service packet needs to be transmitted through the first PW. Furthermore, the first node may use the address of the egress PE device (i.e., the second node) of the determined first PW as the destination address of the first service packet, and based on the destination address and color, search its local routing table to determine the next hop—the SR policy corresponding to the first PW, which is the aforementioned SR policy matching the first service packet.

[0008] As an example, the determined SR policy matching the first service message can correspond to the first instruction action. Therefore, the first node's SRv6 encapsulation of the first service message to obtain the second service message can include: the first node performing the SRv6 encapsulation on the first service message according to the first instruction action to obtain the second service message. Thus, by configuring the first instruction action corresponding to the SR policy of the first PW on the first PW's entry PE device (i.e., the first node), the first node can quickly and conveniently process the first service message, improving the efficiency of PW emulation and consequently increasing the efficiency of message transmission.

[0009] As another example, the SR policy determined to match the first service message may not correspond to the instruction action designed in this application embodiment. Therefore, before the first node performs SRv6 encapsulation on the first service message to obtain the second service message, the method may further include the first node processing the first service message according to a normal SR policy, that is, the first node processing the first service message based on the SR policy to obtain a third service message, and the first node determining the destination address of the third service message as the first node's first SID, where the first SID corresponds to a second instruction action. Thus, the first node performing SRv6 encapsulation on the first service message to obtain the second service message may include: the first node processing the third service message according to the second instruction action to obtain the second service message. In this way, by configuring a second instruction action corresponding to the first SID of the first PW on the first node, the first node can implement the processing of the first service message.

[0010] In another implementation, the first node can also be an intermediate PE device between the second PW and the first PW, i.e., a second PW is established between the third node and the first node. In this case, the method may further include: the first node receiving a fourth service packet from the third node through the second PW; the first node determining the destination address of the fourth service packet as the second SID of the first node, where the second SID corresponds to a third instruction action. Then, the first node obtaining the first service packet may include: the first node performing SRv6 decapsulation on the fourth service packet according to the third instruction action to obtain the first service packet. In this implementation, the second SID can correspond to a fourth instruction action. Therefore, the first node performing SRv6 encapsulation on the first service packet to obtain the second service packet may include: the first node performing SRv6 encapsulation on the first service packet according to the fourth instruction action to obtain the second service packet. Thus, in a multi-segment PW scenario, by configuring two instruction actions (i.e., the third instruction action and the fourth instruction action) corresponding to the second SID on the intermediate PE device between two PW segments, respectively handling the operations required by the PE device as the exit PE device of the previous PW segment and the entry PE device of the next PW segment, the first node can achieve rapid simulation of PW and process the messages.

[0011] In one possible implementation, a third PW can be established between the first node and the second node. The method may further include: the first node acquiring a fifth service message, encapsulating the fifth service message using SRv6 to obtain a sixth service message, the sixth service message including information from the fifth service message and the third PW; and then, the first node sending the sixth service message to the second node through the third PW. In this way, the transmission of service messages in an SRv6 network can be achieved without multi-protocol nesting, thus facilitating and quickly completing PW emulation services for various services.

[0012] Secondly, this application also provides a message transmission method executed by a second node, wherein a first pseudowire (PW) is established between the first node and the second node. This method may include, for example, the second node receiving a second service message from the first node through the first PW, the second service message including a first service message and information about the first PW; the second node performing segment routing (SRv6) decapsulation on the second service message based on Internet Protocol version 6 (IP6) to obtain the first service message. It is evident that this method, by defining processing mechanisms corresponding to the PW on the PE devices at both ends of the PW, enables the ingress PE devices to perform SRv6 encapsulation on the PW service, encapsulating the information describing the PW and the service message to be transmitted into the actual transmitted service message. The egress PE devices perform SRv6 decapsulation on the service message received through the PW to obtain the aforementioned service message to be transmitted. This process uses only IP and does not involve multi-protocol nesting to achieve the transmission of service messages in the SRv6 network, thus conveniently and quickly completing PW emulation services for various services.

[0013] As an example, the second node's SRv6 decapsulation of the second service packet may include: the second node stripping the Segment Routing Header (SRH) of the second service packet, wherein the SRH includes the Segment list corresponding to the first PW. In this way, the second node can obtain the first service packet.

[0014] In one implementation, the SRH of the second service packet includes the SID of the second node, which corresponds to a first instruction action. The second node performs SRv6 decapsulation on the second service packet to obtain the first service packet. This can include: the second node performing SRv6 decapsulation on the second service packet according to the first instruction action to obtain the first service packet. Thus, the processing of service packets transmitted from the first PW can be achieved by configuring the correspondence between the SID of the second node and the first instruction action on the egress PE device (i.e., the second node) of the first PW.

[0015] In one implementation, the method may further include: the second node reconstructing the service corresponding to the first service message based on the information of the first PW, to obtain the third service message.

[0016] As an example, if no other PW is connected after the second node, the method may further include: the second node sending the third service message to the destination host.

[0017] As another example, if a second PW is established between the second node and the third node, the method may further include: the second node performing SRv6 encapsulation on the third service packet to obtain a fourth service packet, the fourth service packet including information from the third service packet and the second PW; and the second node sending the fourth service packet to the third node through the second PW. In this example, the SRH of the second service packet includes the SID of the second node, which also corresponds to a second instruction action. The second node performing SRv6 encapsulation on the third service packet to obtain the fourth service packet may include: the second node performing SRv6 encapsulation on the third service packet according to the second instruction action to obtain the fourth service packet. Thus, in scenarios with multiple PW segments, the intermediate PE device between the two PW segments can continue processing the decapsulated service packet according to the requirements of the next PW segment, completing the effective transmission of the service packet in the next PW segment, thereby realizing packet transmission in scenarios with multiple PW segments in an SRv6 network.

[0018] It should be noted that, in order to ensure the reliability of PW emulation, the PW can be verified before the PW's outgoing PE device decapsulates the received service packets. For example, the PW ID can be obtained from the received service packets, and the control plane can be checked to see if a PW corresponding to the PW ID is configured. If it is, the verification passes, and the SRv6 decapsulation operation of the received service packets is performed; otherwise, if it is not found, the verification fails, and the service packets are discarded.

[0019] It should be noted that, in the methods provided in the first and second aspects above, the IPv6 DOH of the second service packet can be used to carry information about the first PW. Alternatively, the SRH of the second service packet can also be used to carry information about the first PW.

[0020] The information of the first PW may include: the identifier of the first PW, multiple flags, and a sequence number. The multiple flags and the sequence number may also be referred to as the control words of the first PW.

[0021] It should be noted that the first service message can be a message corresponding to a non-Ethernet service. The non-Ethernet service includes any of the following services: Frame Relay service, Time Division Multiplexing (TDM) service, or Asynchronous Transfer Mode (ATM) service. TDM can include, but is not limited to: E1 service, E3 service, T1 service, T3 service, SONET service, or SDH service.

[0022] Thirdly, this application also provides a message transmission apparatus applied to a first node, wherein a first pseudowire (PW) is established between the first node and a second node. The apparatus may include: a first obtaining unit, a first processing unit, and a first sending unit. The first obtaining unit is used to obtain a first service message; the first processing unit is used to encapsulate the first service message using segment routing (SRv6) based on Internet Protocol version 6 (IP6) to obtain a second service message, the second service message including the first service message and information from the first PW; and the first sending unit is used to send the second service message to the second node through the first PW.

[0023] In one implementation, the first processing unit is specifically used to: encapsulate a segment routing header (SRH) outside the first service message, wherein the SRH includes a segment list corresponding to the first PW.

[0024] In one implementation, the apparatus further includes a first determining unit. This first determining unit is configured to determine whether the first service packet matches a segment routing policy (SR policy).

[0025] As an example, the SR policy corresponds to the first instruction action, and the first processing unit is specifically used to: perform SRv6 encapsulation on the first service message according to the first instruction action to obtain the second service message.

[0026] As another example, the apparatus further includes a second processing unit and a second determining unit. The second processing unit is configured to process the first service packet based on the SR policy to obtain a third service packet; the second determining unit is configured to determine that the destination address of the third service packet is a first SID of the first node, and the first SID corresponds to a second instruction action. Specifically, the first processing unit is configured to process the third service packet according to the second instruction action to obtain the second service packet.

[0027] In another implementation, a second PW is established between the third node and the first node, and the apparatus further includes a receiving unit and a third determining unit. The receiving unit is used to receive a fourth service packet from the third node through the second PW; the third determining unit is used to determine that the destination address of the fourth service packet is the second SID of the first node, and the second SID corresponds to a third instruction action. Then, the first obtaining unit is specifically used to: decapsulate the fourth service packet using SRv6 according to the third instruction action to obtain the first service packet. In this implementation, the second SID corresponds to the fourth instruction action, and the first processing unit is specifically used to: encapsulate the first service packet using SRv6 according to the fourth instruction action to obtain the second service packet.

[0028] In another implementation, a third PW is established between the first node and the second node, and the apparatus further includes: a second obtaining unit, a third processing unit, and a second sending unit. The second obtaining unit is used to obtain a fifth service message; the third processing unit is used to encapsulate the fifth service message using SRv6 to obtain a sixth service message, the sixth service message including the information of the fifth service message and the third PW; the second sending unit is used to send the sixth service message to the second node through the third PW.

[0029] Fourthly, this application also provides a message transmission apparatus applied to a second node, wherein a first pseudowire (PW) is established between the first node and the second node. The apparatus includes a first receiving unit and a first processing unit. The first receiving unit is configured to receive a second service message from the first node via the first PW, the second service message including information about the first service message and the first PW. The first processing unit is configured to perform segment routing (SRv6) decapsulation on the second service message to obtain the first service message.

[0030] In one implementation, the first processing unit is specifically used to: strip the Segment Routing Header (SRH) of the second service packet, wherein the SRH includes the Segment list corresponding to the first PW.

[0031] In another implementation, the SRH of the second service message includes the SID of the second node, and the SID of the second node corresponds to the first instruction action. The first processing unit is specifically used to: perform SRv6 decapsulation on the second service message according to the first instruction action to obtain the information of the first service message and the first PW.

[0032] In one implementation, the apparatus further includes a restoration unit. This restoration unit is configured to restore the service corresponding to the first service message based on the information of the first PW, thereby obtaining a third service message.

[0033] As an example, the apparatus further includes a first sending unit. This first sending unit is configured to send the third service message to the destination host.

[0034] As another example, a second PW is established between the second node and the third node. The apparatus further includes a second processing unit and a second sending unit. The second processing unit is used to perform SRv6 encapsulation on the third service message to obtain a fourth service message, the fourth service message including information from the third service message and the second PW. The second sending unit is used to send the fourth service message to the third node through the second PW. In this example, the SRH of the second service message includes the SID of the second node, and the SID of the second node also corresponds to a second instruction action. The second processing unit is specifically used to: perform SRv6 encapsulation on the third service message according to the second instruction action to obtain the fourth service message.

[0035] It should be noted that, in the methods provided in the third and fourth aspects above, the IPv6 DOH of the second service packet can be used to carry information about the first PW. Alternatively, the SRH of the second service packet can also be used to carry information about the first PW.

[0036] The information of the first PW may include: the identifier of the first PW, multiple flags, and a sequence number. The multiple flags and the sequence number may also be referred to as the control words of the first PW.

[0037] It should be noted that the first service message can be a message corresponding to a non-Ethernet service. The non-Ethernet service includes any of the following services: Frame Relay service, Time Division Multiplexing (TDM) service, or Asynchronous Transfer Mode (ATM) service. TDM can include, but is not limited to: E1 service, E3 service, T1 service, T3 service, SONET service, or SDH service.

[0038] It should be noted that the specific implementation method and the effect achieved by the message transmission device provided in the third aspect of this application can be found in the relevant description in the embodiment shown in the first aspect above, and will not be repeated here.

[0039] It should be noted that the specific implementation method and the effect achieved by the message transmission apparatus provided in the fourth aspect of this application can be found in the relevant description in the embodiments shown in the second aspect above, and will not be repeated here.

[0040] Fifthly, this application provides a communication device, which includes a memory and a processor; the memory is used to store program code; the processor is used to execute instructions in the program code, causing the communication device to perform the method described in the first aspect and any one of the first aspects above, or to cause the communication device to perform the method described in the second aspect and any one of the second aspects above.

[0041] Sixthly, this application provides a communication system comprising a first node and a second node; wherein the first node is configured to perform the method described in the first aspect and any one thereof; and the second node is configured to perform the method described in the second aspect and any one thereof.

[0042] In a seventh aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect and any one thereof, or cause the computer to perform the methods described in the second aspect and any one thereof.

[0043] Eighthly, this application provides a computer program product, including a program that, when run on a processor, implements the method described in the first aspect and any one of the first aspects above, or implements the method described in the second aspect and any one of the second aspects above. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0045] Figure 1 This is a schematic diagram of the structure of a service packet obtained based on the IP+UDP encapsulation method;

[0046] Figure 2 This is a schematic diagram of the structure of a service message obtained based on the L2TPv3 encapsulation method;

[0047] Figure 3a A schematic diagram illustrating the framework of an application scenario provided in an embodiment of this application;

[0048] Figure 3bA schematic diagram illustrating another application scenario provided by an embodiment of this application;

[0049] Figure 4 For the embodiments of this application Figure 3a A schematic diagram of the PW 100 simulation process;

[0050] Figure 5a This is a schematic diagram of the structure of service message 2 in the embodiments of this application;

[0051] Figure 5b This is a schematic diagram of the structure of service message 4' in the embodiments of this application;

[0052] Figure 6a This is an exemplary structural diagram of service message 2 in an embodiment of this application;

[0053] Figure 6b This is another exemplary structural diagram of service message 2 in the embodiments of this application;

[0054] Figure 7a This is a schematic diagram of a service message 1 in an embodiment of this application;

[0055] Figure 7b This is a schematic diagram of another service message 1 in the embodiments of this application;

[0056] Figure 8 A flowchart illustrating a message transmission method 100 provided in an embodiment of this application;

[0057] Figure 9 A flowchart illustrating another message transmission method 200 provided in an embodiment of this application;

[0058] Figure 10 A flowchart illustrating another message transmission method 300 provided in an embodiment of this application;

[0059] Figure 11 A schematic diagram of the structure of a message transmission device 1100 provided in an embodiment of this application;

[0060] Figure 12 A schematic diagram of the structure of a message transmission apparatus 1200 provided in an embodiment of this application;

[0061] Figure 13 This is a schematic diagram of the structure of a communication device 1300 provided in an embodiment of this application;

[0062] Figure 14 This is a schematic diagram of the structure of a communication system 1400 provided in an embodiment of this application. Detailed Implementation

[0063] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings. The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0064] In this application, ordinal numbers such as “1”, “2”, “3”, “first”, “second”, and “third” are used to distinguish multiple objects, not to limit the order of multiple objects.

[0065] The reference to "A and / or B" in this application should be understood to include the following situations: including only A, including only B, or including both A and B.

[0066] PW, as a point-to-point connection established between PE devices, primarily functions to simulate various services.

[0067] Currently, PW emulation methods typically require multiple protocol nesting, making the processing of service packets by network devices on the PW complex and resulting in low forwarding efficiency. Taking PW emulation of TDM services as an example, based on the two encapsulation methods provided in Request for Comments (RFC) 5087 (i.e., Time Division Multiplexing over IP (TDMoIP) emulation), we introduce the current PW emulation methods: Method 1, IP + User Datagram Protocol (UDP) encapsulation method; Method 2, Layer 2 Tunneling Protocol Version 3 (L2TPv3) encapsulation method.

[0068] For example, regarding the IP+UDP encapsulation method defined in RFC 5087, in an SRv6 network, the service packets obtained after encapsulation by the PW's ingress PE device can be found in [reference needed]. Figure 1 .like Figure 1As shown, the service message may include: an Internet Protocol version 6 (IPv6) header, a UDP header, a TDMoIP control word, and a payload. Optionally, a Real-time Transport Protocol (RTP) header may also be included between the UDP header and the TDMoIP control word. Figure 1 Taking the RTP header as an example, the specific format of the RTP header can be found in the relevant definitions in RFC 3550. The IPv6 header is shown in the first four lines of this service message, including: Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, and Destination Address. The UDP header is shown in lines 5 and 6 of this service message, including: Source Port Number, Destination Port Number, UDP Length, and UDP Checksum. The RTP header is shown in lines 7, 8, and 9 of this service message, and includes: RTP Version (RTV) field, Padding Flag (P) field, Extension Flag (X) field, Contributing Source Counter (CC) field, Marker (M) field, Payload Type (PT) field, RTP Sequence Number field, Timestamp field, and Synchronization Source Identifier (SSRC) field. The TDMoIP control word is shown in line 10 of this service message, and includes: Reserved (RES) field, Local Fault (L) bit, Remote Fault (R) bit, Defect Correction Fault (M) field, Reserved (RES) field, Length field, and Sequence Number field.

[0069] For emulation of TDM services using IP+UDP encapsulation, the PW can be identified using the source or destination port number field in the UDP header. That is, the source or destination port number in the UDP header is used as the PW label. The PE devices at both ends of the PW need to agree on a consistent mapping between the PW label and the specific pseudowire. For example, if the source port number in the UDP header is used as the PW label, then the destination port number in the UDP header must be set to 0x085E (2142) assigned by the Internet Assigned Numbers Authority (IANA) to indicate that this is a TDMoIP pseudowire service. The TDMoIP control word is used to determine whether the payload corresponds to a pseudowire service. It also provides alarm indication and order preservation functions for the pseudowire service when it is determined to be a pseudowire service. Specific encapsulation formats and contents can be found in the relevant definitions in RFC 4385, and will not be elaborated here.

[0070] It is evident that the service packets obtained using this IP+UDP encapsulation method require additional UDP nesting and identification outside the IP layer for the PE devices at both ends of the PW to achieve the purpose of PW emulation of TDM services. This multi-layered header complexity complicates the processing of service packets by the PE devices at both ends of the PW, resulting in low forwarding efficiency. Furthermore, RFC 5087 explicitly states that in networks with intermediate box devices (such as Network Address Translation (NAT) devices), these devices modify the port numbers in the UDP header of the service packets. This causes the implementation to use the source or destination port number in the UDP header as the PW label, preventing the PW's outgoing PE devices from correctly reconstructing the TDM service emulated by the PW based on the modified port numbers in the service packets. Therefore, this IP+UDP encapsulation method cannot achieve the purpose of PW emulation of TDM services when intermediate box devices with port number modification exist in the network.

[0071] For example, regarding the L2TPv3 encapsulation method defined in RFC 5087, the service packets obtained after encapsulation by the PW's ingress PE device can be found in [reference needed]. Figure 2 .like Figure 2As shown, this service message may include: an IPv6 header, an L2TPv3 header, a TDMoIP control word, and a payload. Optionally, an RTP header may also be included between the TDMoIP control word and the payload. The IPv6 header, TDMoIP control word, RTP header, and payload can be found in [reference needed]. Figure 1 The relevant explanation is provided in the documentation. The L2TPv3 header, see lines 5, 6, and 7 of this service message, includes: a Session ID field and optional random Cookie 1 and random Cookie 2 fields. The Session ID field can carry a PW Label; the Cookie 1 and Cookie 2 fields are used to verify the association between the received frame and the PW.

[0072] It is evident that the service packets obtained through this L2TPv3 encapsulation method require additional L2TPv3 protocol nesting and recognition outside the IP layer for the PE devices at both ends of the PW (see relevant explanations in RFC 3931) to achieve the purpose of PW emulation for TDM services. This multi-layered header structure complicates the processing of service packets by the PW devices at both ends, resulting in low forwarding efficiency. Furthermore, RFC 5087 defines Generic Routing Encapsulation (GRE) encapsulation, which also requires additional GRE protocol nesting and recognition outside the IP layer for the PE devices at both ends of the PW. This multi-layered protocol nesting also leads to complex processing and low forwarding efficiency for the service packets by the PE devices at both ends of the PW.

[0073] In addition, the aforementioned encapsulation methods requiring protocol nesting not only necessitate that the PE devices at both ends of the PW have interface boards for processing IP packets, but also dedicated service boards for handling other protocols nested on top of IP. For example, in the L2TPv3-based encapsulation solution, the PE devices at both ends of the PW not only need interface boards, but also dedicated service boards with network processors (NPs) or field-programmable gate arrays (FPGAs) to process the L2TPv3 header. It is evident that the current implementation methods have high hardware performance and resource requirements, making them unsuitable for large-scale application in carrying PW emulation services.

[0074] Because IPv6 offers a richer address set than Internet Protocol version 4 (IPv4), its applications will become increasingly widespread. SRv6, the application of segment routing (SR) technology in the IPv6 network plane, will become a mainstream technology for operators' research and application due to its ability to meet the requirements of mobile internet and cloud services for bearer networks. Therefore, providing a pseudowire emulation mechanism suitable for SRv6 networks to achieve transparent transmission of various services and thus complete the interconnection of various services becomes crucial.

[0075] Based on this, this application provides a method for message transmission in SRv6 networks. It uses a newly defined PW emulation mechanism to process service messages transmitted via PW, and the encapsulation method does not require nesting multiple protocols. In this method, when the ingress PE device of the PW receives the first service message corresponding to the PW, it can perform SRv6 encapsulation on the first service message to obtain a second service message. This second service message includes the first service message and the information of the PW. Thus, the ingress PE device can send the second service message to the egress PE device through the PW. After receiving the second service message from the ingress PE device through the PW, the egress PE device performs SRv6 decapsulation on the second service message to obtain the first service message. As can be seen, in this method, a processing mechanism corresponding to the PW is defined on the PE devices at both ends of the PW, enabling the ingress PE device to encapsulate the PW service using SRv6, encapsulating the information describing the PW and the service message to be transmitted into the actual service message to be sent. The egress PE device decapsulates the service message received through the PW using SRv6 to obtain the aforementioned service message to be transmitted. In this process, only IP is used, and the transmission of service messages in the SRv6 network can be realized without multi-protocol nesting, thus conveniently and quickly completing the PW simulation service for various services.

[0076] It should be noted that the PW emulation involved in the embodiments of this application refers to the PW emulation of non-Ethernet Layer 2 services in the SRv6 network. Non-Ethernet Layer 2 services may include, but are not limited to: Frame Relay services, TDM services, ATM services, High-level Data Link Control (HDLC) services, and Point-to-Point Protocol (PPP) services. Among these, TDM service messages may include, but are not limited to: E1 services, T1 services, E3 services, T3 services, Synchronous Optical Network (SONET) services, or Synchronous Digital Hierarchy (SDH) services.

[0077] For example, such as Figure 3a The scenario shown may include: Customer Edge (CE) device 1, CE device 2, CE device 3, CE device 4, CE device 5, PE device 1, PE device 2, PE device 3, and Provider (P) device (also known as core layer device) device 1, P device 2, and P device 3. CE device 1 and CE device 2 are connected to PE device 1. PE device 1 is connected to PE device 2 via P device 1 and P device 2. PE device 2 is connected to CE device 3 and CE device 4. PE device 1 is also connected to PE device 3 via P device 3. PE device 3 is connected to CE device 5. The networks between PE device 1 and PE device 2, and between PE device 1 and PE device 3, are both SRv6 networks. CE device 1 and CE device 3 correspond to user A. User A's services are transmitted through PW 100. PW 100 can be the path from PE device 1 to PE device 2 via P device 1 and P device 2. CE device 2, CE device 4 and CE device 5 correspond to user B. User B's services are transmitted through PW 201 and PW 202. PW 201 can be the path from PE device 1 to PE device 2 via P device 1 and P device 2. PW 202 can be the path from PE device 1 to PE device 3 via P device 3.

[0078] Before PW emulation, on the one hand, each device in the SRv6 network can advertise its segment identifier (SID) within the SRv6 network using either the Interior Gateway Protocol (IGP) or the Link Gateway Protocol-LinkState (BGP-LS); on the other hand... Figure 3a The scenario shown may also include a controller 10, which can send SR policies to PE device 1. These SR policies include, but are not limited to: SR policy 0: Segment list 0 corresponding to PW 100, SR policy 1: Segment list 1 corresponding to PW 201, and SR policy 2: Segment list 2 corresponding to PW 202. Segment list 0 may include SID 0, SID 11, SID 12, and SID 3; Segment list 1 may include SID 1, SID 11, SID 12, and SID 4; and Segment list 2 may include SID 2, SID 13, and SID 5. SID 0, SID 1, and SID 2 are the SIDs on PE device 1 corresponding to PW 100, PW 201, and PW 202, respectively, and SID 3 and SID 4 are the SIDs on PE device 2 corresponding to PW 100, PW 201, and PW 202, respectively. SID 100 corresponds to PW 201, SID 5 is the SID on PE device 3 corresponding to PW 202, and SIDs 11, 12, and 13 are the SIDs corresponding to P device 1, P device 2, and P device 3, respectively. It should be noted that controller 10 can send at least one SR policy to PE device 1 via, for example, the Path Computation Element Protocol (PCEP). This prepares PE device 1 for receiving and processing service messages, making PW emulation possible in the SRv6 network.

[0079] It should be noted that the segment list may include the SIDs of all devices between the inlet PE device and the outlet PE device (including both the inlet and outlet PE devices), or it may only include the SIDs of the inlet PE device and the outlet PE device. The SIDs included in the segment list do not affect the implementation of the embodiments of this application. In this embodiment, the example described is that the segment list includes the SIDs of all devices between the inlet PE device and the outlet PE device (including both the inlet and outlet PE devices).

[0080] It should be noted that if information 0 of PW 100 is carried through SID 0 (such as the Arguments field in SID 0), and information 1 of PW 201 is carried through SID 1 (such as the Arguments field in SID 1), then SID 0 and SID 1 can be different SIDs. If information 0 of PW 100 is not carried through SID 0, and information 1 of PW 201 is not carried through SID 1, then SID 0 and SID 1 can be the same SID. Similarly, SID 3 and SID 4 can be the same SID or different SIDs. The following description uses the example of SID 0 and SID 1 being different, and SID 3 and SID 4 being different.

[0081] As an example, for the PE device that serves as the entry point for PW 100, PW 201, and PW 202—PE device 1—corresponding instruction actions can be configured for each of the three SR policies. Specifically, PE device 1 can be configured with: SR policy 0 corresponding to instruction action 0, SR policy 1 corresponding to instruction action 1, and SR policy 2 corresponding to instruction action 2. Instruction action 0 instructs PE device 1 to encapsulate service packets belonging to PW 100 with the corresponding Segment list 0 and PW 100 information 0. Similarly, instruction action 1 instructs PE device 1 to encapsulate service packets belonging to PW 201 with the corresponding Segment list 1 and PW 201 information 1. Instruction action 2 instructs PE device 1 to encapsulate service packets belonging to PW 202 with the corresponding Segment list 2 and PW 202 information 2. For the egress PE device (PE device 2) of PW 100 and PW 201, corresponding command actions can be configured for the SIDs corresponding to the two PWs. Specifically, PE device 2 can be configured with command action 3 for SID 3 and command action 4 for SID 4. Command action 3 instructs PE device 2 to decapsulate service packets belonging to PW 100; similarly, command action 4 instructs PE device 2 to decapsulate service packets belonging to PW 201. For the egress PE device (PE device 3) of PW 202, corresponding command action 5 can be configured for SID 5 of PW 202. This command action 5 instructs PE device 3 to decapsulate service packets belonging to PW 202.

[0082] In this example, for service message 1 sent from CE device 1 to PE device 1 that needs to pass through PW 100, see [link to relevant documentation]. Figure 4 As shown, the PW simulation process may include: S11, PE device 1 receives service message 1 from interface 1 connected to CE device 1, and determines that service message 1 needs to be transmitted to PE device 2 via PW 100, with the next hop being SR policy 0. S12, PE device 1 encapsulates service message 1 according to instruction action 0 corresponding to SR policy 0 to obtain service message 2. Service message 2 can be found in [reference needed]. Figure 5aThe process includes: an IPv6 header, a Segment Routing Header (SRH), and service packet 1. Optionally, an RTP header may also be included between the SRH and service packet 1. On one hand, the SRH of service packet 2 may include the Segment list 0 corresponding to PW 100; on the other hand, service packet 2 may also include information 0, which describes the attributes of PW 100. S13, PE device 1 sends service packet 2 to PE device 2 via PW 100. S14, PE device 2 receives service packet 2, determines that the last SID 3 in the Segment list of service packet 2's SRH is the SID corresponding to PW 100 configured locally, and thus determines that it is the egress PE device of PW 100. According to the instruction action 3 corresponding to SID 3, it decapsulates service packet 2 to obtain service packet 1 and information 0. Optionally, the process may also include: S15, PE device 2 restores the service corresponding to PW 100 based on service message 1 and information 0, and sends the restored service data to the corresponding service module or interface (such as TDM service module or interface) on PE device 2 to complete the subsequent processing of the service. For example, PE device 2 sends the processed service data to the user equipment corresponding to user A (i.e., the destination host of the service data) through CE device 3. It should be noted that, for S11, PE device 1 can bind PW 100 to interface 1 connected to CE device 1, or it can bind PW 100 to the virtual private network (VPN) 1 corresponding to interface 1. Then, PE device 1 can determine that the PW corresponding to service packet 1 is PW 100 based on interface 1 that receives service packet 1. Next, PE device 1 can determine that the egress PE device of PW 100 is PE device 2. Thus, PE device 1 can use the address of PE device 2 as the destination address, and search for a matching routing table entry in the local routing table of PE device 1 based on the destination address and color. From the matching routing table entry, it obtains the next hop of service packet 1—SR policy 0. In this way, the preparation work is completed for PE device 1 to perform SRv6 encapsulation on service packet 1 according to the instruction action 0 corresponding to SR policy 0 in S12.

[0083] As another example, for the entry PE device of PW 100, PW 201 and PW 202, PE device 1 can also be configured with corresponding instruction actions for the three SIDs respectively. That is, PE device 1 can be configured with: instruction action 0 for SID 0, instruction action 1 for SID 1 and instruction action 2 for SID 2.

[0084] In this example, for a service message 3 sent from CE device 2 to PE device 1 that needs to pass through PW 201, the PW emulation process may include: S21, PE device 1 receives service message 3 from interface 2 connected to CE device 2, determines that service message 3 needs to be transmitted to PE device 2 through PW 201, and the next hop is SR policy 1. S22, PE device 1 processes service message 3 according to SR policy 0 to obtain service message 4, which includes Segment list 1 and the destination address field in the IPv6 header is SID 1; S23, PE device 1 processes service message 4 according to instruction action 1 corresponding to SID 1 to obtain service message 4', which can be found in [reference needed]. Figure 5bOn one hand, the SRH of service message 4' may include Segment list 1 corresponding to PW 201; on the other hand, service message 4' may also include information 1. S24, PE device 1 sends service message 4' to PE device 2 via PW 201. S25, PE device 2 receives service message 4', determines that the last SID 4 in the Segment list of service message 4' is its locally configured SID corresponding to PW 201, thus determining itself as the outgoing PE device of PW 201, and decapsulates service message 4' according to instruction action 4 corresponding to SID 4 to obtain service message 3 and information 1. Optionally, this process may also include: S26, PE device 2 restores the service corresponding to PW 201 based on service message 3 and information 1, and sends the restored service data to the corresponding service module or interface on PE device 2 to complete the subsequent processing of the service. For example, PE device 2 sends the processed service data to the user equipment corresponding to user B via CE device 4. It should be noted that in this example, SR policy 0 is a normal SR policy, corresponding to the normal SRv6 encapsulation command action. PE device 1 can perform regular SRv6 encapsulation on the service packet based on this SR policy 1. SID 1 in SR policy 1 is a special SID, corresponding to the special command action 1 that the PE device at the PW entry point needs to execute. For S22, after PE device 1 determines the next hop of the service packet 3—SR policy 1, PE device 1 can encapsulate the service packet 3 with an SRH based on this SR policy 1. The SRH includes Segment list 1, and the SID 1 corresponding to PE device 1 in Segment list 1 is filled into the destination address field of the IPv6 header to obtain the service packet 4. Then, PE device 1 performs a local table lookup according to the destination address as SID 1 to determine the command action 1 corresponding to SID 1, and then executes the command action 1 corresponding to SID 1 to encapsulate the service packet 4 with the PW information 1 to obtain the service packet 4'.

[0085] For example, embodiments of this application are also applicable to, such as Figure 3b The scene shown is compared to Figure 3a The scene shown, Figure 3bIn the scenario shown, between CE device 1 and PE device 1, there are also PE device 4 and P device 4. CE device 1 is connected to PE device 4, and PE device 4 is connected to PE device 1 through P device 4. The network between PE device 4 and PE device 1 is also an SRv6 network. CE device 1 and CE device 3 correspond to user A. User A's services are transmitted through PW 101 and PW 100 respectively. PW 101 can be the path from PE device 4 to PE device 1 via P device 4.

[0086] As an example, in Figure 3b In the scenario shown, PE device 4 can obtain SR policy 4, which includes segment list 4. Segment list 4 can include SID 40, SID 14, and SID 0', where SID 40 is the SID on PE device 4 corresponding to PW 101, SID 14 is the SID corresponding to P device 14, and SID 0' is the SID corresponding to PE device 1. For the ingress PE device of PW 101—PE device 4—corresponding instruction action 40 can be configured for SR policy 4. Instruction action 40 can instruct PE device 4 to encapsulate the segment list 4 corresponding to PW 101 and the information 10 of PW 101 into the service packets belonging to PW 101. For the intermediate PE devices of segmented PWs (i.e., the egress PE device of PW 101 and the ingress PE device of PW 100)—PE device 1—corresponding instruction actions 41 and 42 can be configured for SID 0' of PE device 1, respectively. Specifically, instruction action 41 can instruct PE device 1 to perform SRv6 decapsulation on service packets belonging to PW 101, and instruction action 42 can instruct PE device 1 to perform SRv6 encapsulation on service packets belonging to PW 100.

[0087] In this example, for a service message 5 sent from CE device 1 to PE device 4 that needs to pass through PE 101 and PW 100 sequentially, the PW emulation process may include: S31, PE device 4 receives service message 5 from interface 4 connecting to CE device 1, determines that service message 5 needs to be transmitted to PE device 1 via PW 101, and the next hop is SR policy 4. S32, PE device 4 encapsulates service message 5 according to the instruction action 40 corresponding to SR policy 4 to obtain service message 6. On the one hand, the SRH of service message 6 may include the segment list 4 corresponding to PW 101; on the other hand, service message 6 may also include information 4, which describes the attributes of PW 101. S33, PE device 4 sends service message 6 to PE device 1 via PW 101. S34, PE device 1 receives service message 6 and determines that the last SID 0' in the Segment list of the SRH of service message 6 is the SID corresponding to PW 101 and PW 100 configured locally, thus identifying itself as the outgoing PE device of PW 101. It then decapsulates service message 6 according to instruction action 41 corresponding to SID 0' to obtain service message 5 and information 4. Optionally, after S34, the process may further include: S35, PE device 1 restores the service corresponding to PW 101 based on service message 5 and information 4 to obtain the restored service data (such as service message 5). Next, this process may further include: S36, PE device 1 encapsulates service message 5 according to instruction action 42 corresponding to SID 0' to obtain service message 6'. On one hand, the SRH of service message 6' may include Segment list 0 corresponding to PW 100; on the other hand, service message 6' may also include information 0, which describes the attributes of PW 100. S37, PE device 1 sends service message 6' to PE device 2 via PW 100. S38, PE device 2 receives service message 6', determines that the last SID 3 in the Segment list of service message 6' is its locally configured SID corresponding to PW 100, thus identifying itself as the outgoing PE device of PW 100. It then decapsulates service message 6' according to instruction action 42 corresponding to SID 0', obtaining service message 5 and information 0. Optionally, S38 may be followed by: S39, PE device 2, based on service message 5 and information 0, restores the service corresponding to PW 100, obtaining the restored service data.

[0088] In this embodiment, the PW information can also be called metadata, which refers to information describing PW attributes. This includes, on the one hand, the functionality of control words (such as TDMoIP control words) in current PW emulation encapsulation methods, and on the other hand, information that identifies the PW (similar to a PW label). Therefore, the PW information in this embodiment may include, but is not limited to, multiple flags, a sequence number, and a PW ID. As an example, the PW information in the message may include the following fields: Flags field, Length field, Reserved (Rvd) field, Sequence Number field, and PW ID field. The Flags field may include, but is not limited to, L bits, R bits, N bits, and P bits. Optionally, when the PW emulated service is segmented, the Flags field may also include FRG bits to indicate service segmentation. The value of the Length field indicates the length of service message 1. The value of the Sequence Number field is used to sort the data frames included in service message 1. The value of the PW ID field is used to uniquely identify a PW. For example, in service message 1 transmitted through PW 100, the value of the PW ID field in information 0 can be equal to 100, which is used to identify that service message 1 is transmitted through PW 100, and implements the simulation service of PW 100.

[0089] for Figure 5a As an example, information 0 in service message 2 can also include an IPv6 extension header. This IPv6 extension header carries information 0 through a newly added Type Length Value (TLV) field. The IPv6 options header can be either a Hop-by-Hop Options Header (HBH) or a Destination Options Header (DOH). Taking service message 2 as an example of carrying information 0 through the DOH-extended TLV field, service message 2 can be found in [reference needed]. Figure 6a As shown. As another example, the SRH in service message 2 can also have an additional SRH TLV field added. This SRH TLV field is used to carry information 0. Service message 2 can be found in [reference needed]. Figure 6b As shown.

[0090] for Figure 5aThe business message 1 shown in business message 2 is an example of TDM Circuit Emulation Service (CES). If business message 1 were a structured TDM CES, then business message 1 can be found in [reference needed]. Figure 7a As shown, a structured TDM CES can, for example, include n data frames (Frame 1# to Frame n#), each data frame including N time slots (TS 1 to TS N). In this example, if service message 2 is as follows... Figure 6a As shown, the value of the Next Header field in the IPv6 DOH indicates that the payload of service packet 2 (i.e., service packet 1) encapsulates TDM data in NxDS0 format (i.e., the structured TDM CES mentioned above); if service packet 2 is as follows... Figure 6b As shown, the value of the Next Header field in the SRH field indicates that the payload of service message 2 is the structured TDM CES described above. As another example, if service message 1 is a SONET or SDH CES, then service message 1 can be seen... Figure 7b As shown, the payload can include, for example, SONET data or SDH data. In this example, if business message 2 is as follows... Figure 6a As shown, the value of the Next Header field in the IPv6 DOH indicates whether the payload of service message 2 is SONET data or SDH data; if service message 2 is as follows... Figure 6b As shown, the value of the Next Header field in the SRH field is used to indicate whether the payload of the service message 2 is the aforementioned SONET data or SDH data.

[0091] It should be noted that the way information is carried is unrelated to the specific content of business message 1 (i.e., payload) in business message 2, and can be designed according to actual needs. For example, Figure 6a The payload of the business message 2 shown can be as follows: Figure 7a As shown, it can also be as follows Figure 7b As shown; for example, Figure 6b The payload of the business message 2 shown can be as follows: Figure 7a As shown, it can also be as follows Figure 7b As shown.

[0092] It should be noted that the processing procedures for service packets corresponding to PW 201 belonging to VPN 2 on user B, and for service packets corresponding to PW 202 belonging to VPN 3 on user B, are similar to the processing procedures for service packets corresponding to PW 100 belonging to VPN 1 on user A, and will not be repeated in this embodiment. User B's CE device 2 can connect to interfaces 2 and 3 of PE device 1. Interfaces 2 and 3 correspond to VPN 2 and VPN 3 respectively, and interfaces 2 and 3 can be two logical interfaces implemented through one or two physical interfaces.

[0093] It should be noted that the types and quantities of devices included between PE devices in this embodiment are merely exemplary. For example, the positions of P devices 1, P devices 2, and P devices 3 can also be PE devices. The number of P devices or PE devices included between PE devices 1 and PE devices 2, and the number of P devices or PE devices included between PE devices 1 and PE devices 3 are not specifically limited in this embodiment.

[0094] As can be seen, the method provided in this application defines a message processing mechanism corresponding to the PW on the PE devices at both ends of the PW. For example, on the ingress PE device, a corresponding instruction action is configured for the SR policy corresponding to the PW, or on the ingress PE device, a corresponding instruction action is configured for the SID corresponding to the PW. The flexible programmable instruction action corresponding to the SR policy or SID is used to encapsulate the PW service message with SRv6 and carry information describing the PW. Alternatively, on the egress PE device, a corresponding instruction action is configured for the SID corresponding to the PW. The flexible programmable instruction action corresponding to the SID is used to decapsulate the PW service message with SRv6. This achieves fast and convenient processing of PW emulation service messages in the SRv6 network on the PE devices at both ends of the PW, without the need for multi-protocol nesting, thus improving the processing efficiency of the PW service messages on the PE devices at both ends of the PW. Furthermore, it overcomes the problem that the current IP+UDP encapsulation method cannot achieve PW emulation in networks with intermediate box devices. Furthermore, this method only requires the PE devices at both ends of the PW to have interface boards for processing IP packets, without the need for dedicated service boards for processing other protocols. This reduces the requirements for the hardware performance and resources of the PE devices at both ends of the PW, and expands the application scope of PW simulation in SRv6 networks.

[0095] It should be noted that in this embodiment, the PE device can be a network device such as a switch, router, or firewall. The control plane of the PE device (such as the central processing unit (CPU) of the PE device) can process the PW information in the service packets (such as the PW information carried in the TLV field of the IPv6 extension header or the PW information carried in the SRH TLV field); the forwarding plane of the PE device (such as the NP, FPGA, etc. of the PE device) can encapsulate and decapsulate the received service packets based on the PW, realizing PW emulation. The CE device can be a device with private network access capabilities, such as a switch, router, Internet of Things (IoT) terminal, host, etc.

[0096] It should be noted that in this embodiment of the application, the endpoint PE device of the PW is the same as the endpoint PE device of the SRv6 network. That is, the first SID and the last SID in the Segment list in the SR policy correspond to the ingress PE device and the egress PE device of the PW, respectively.

[0097] It should be noted that, in this embodiment of the application, in order to ensure the reliability of PW emulation, the PW can be verified before the PW's outgoing PE device decapsulates the received service packets. For example, the PW ID can be obtained from the received service packets, and the control plane can be checked to see if a PW corresponding to the PW ID is configured. If it is, the verification is successful, and the SRv6 decapsulation operation of the received service packets is performed; otherwise, if it is not found, the verification fails, and the service packets are discarded.

[0098] The above Figure 3a , Figure 3b Taking the illustrated scenario as an example, this paper introduces the application of the technical solution of the embodiments of this application in a real-world scenario. The following, in conjunction with the accompanying drawings, describes the message transmission method provided by the embodiments of this application.

[0099] Figure 8 This is a flowchart illustrating a message transmission method 100 provided in an embodiment of this application. Method 100 is applicable to PW (Personal Message Builder) simulation of service messages in an SRv6 network, and is described in terms of the interaction between the two endpoints of a first PW (i.e., the first node and the second node). The first node can also be referred to as the ingress PE (Personal Equipment) device of the first PW, and the second node can also be referred to as the egress PE device of the first PW. For example, the first PW in method 100 is... Figure 3a or Figure 3b In PW 100, the first node can be Figure 3a or Figure 3bIn the PE device 1, the second node can be Figure 3a or Figure 3b PE device 2 in the example; or, for example, the first PW in method 100 is Figure 3a or Figure 3b In PW 201, the first node can be Figure 3a or Figure 3b In the PE device 1, the second node can be Figure 3a or Figure 3b PE device 2 in the example; for example, the first PW in method 100 is Figure 3a or Figure 3b In PW 202, the first node can be Figure 3a or Figure 3b In the PE device 1, the second node can be Figure 3a or Figure 3b PE device 3 in the example; or, for example, the first PW in method 100 is Figure 3b In PW 101, the first node can be Figure 3b In the PE device 4, the second node can be Figure 3b PE device 1. See also Figure 8 The method 100 may include, for example, S101 to S105:

[0100] S101, the first node obtains the first service message.

[0101] The first service message can refer to any message corresponding to a service that can be PW emulated through the embodiments of this application, such as a message corresponding to a non-Ethernet Layer 2 service. The non-Ethernet service can include, but is not limited to, any of the following services: Frame Relay service, TDM service, ATM service, HDLC service, or PPP service. TDM service can include, but is not limited to, E1 service, E3 service, T1 service, T3 service, SONET service, or SDH service. For each type of non-Ethernet service, the first service message can include at least one structured structure. For example, if the non-Ethernet service is TDM, then the first service message can be a structured TDM CES; the specific format can be found in [reference needed]. Figure 7a As shown; the first service message can also be SONET CES or SDH CES, and the specific format can be found in [reference needed]. Figure 7b As shown.

[0102] The first service message can be a service message to be transmitted received by the first node from the service side. For example, the first service message can be... Figure 3aIn the scenario shown, PE device 1 receives service message 1 from CE device 1; or, in the scenario of segmented PW, if the first node is the intermediate PE device between two PW segments, then the first service message can also be a message obtained by the first node processing the received service message. For example, the first service message could be... Figure 3b In the scenario shown, PE device 1 performs SRv6 decapsulation on service message 6 received from PE device 4 via PW 101 to obtain service message 5.

[0103] In practical implementation, on the one hand, the first node can pre-store the correspondence between each interface and the PW locally. This correspondence can be represented, for example, through the Pseudo-WireEmulation (PWE3) forwarding table on the first node. In one scenario, the PWE3 forwarding table can include the direct correspondence between interfaces and PWs. Then, when the first node receives the first service packet, it can directly determine the PW corresponding to the first service packet based on the interface through which the first node receives the packet. Alternatively, in another scenario, the PWE3 forwarding table can include the correspondence between interfaces, VPNs, and PWs. Then, when the first node receives the first service packet, it can determine the VPN corresponding to the first service packet based on the interface through which the first node receives the packet, and thus determine the PW that the first service packet needs to pass through based on the VPN. For example, in... Figure 3a In the scenario shown, PE device 1 can store the following correspondences: between interface 1 and PW 100, between interface 2 and PW 201, and between interface 3 and PW 202. Therefore, when PE device 1 receives a first service message from interface 1, it can determine that the first service message needs to be transmitted through PW 100. As another example, PE device 1 can store the following correspondences: between interface 1, VPN 1, and PW 100; between interface 2, VPN 2, and PW 201; and between interface 3, VPN 3, and PW 202. Then, when PE device 1 receives a first service message from interface 1, it can determine that the first service message belongs to VPN 1, and thus, based on VPN 1, it can determine that the first service message needs to be transmitted through PW 100.

[0104] On the other hand, the first node also has a local routing table. Therefore, when the first node receives the first service packet, it can determine the PW bound to the interface through the PWE3 forwarding table on the first node, using the address of the PW's egress PE device (i.e., the second node) as the destination address of the first service packet. By searching the routing table on the first node for a matching destination address and color, it obtains the next hop of the first service packet from the matching entry (e.g., the SR policy corresponding to the determined PW). For example, in... Figure 3a In the scenario shown, the routing table of PE device 1 includes routing table entry 1: the correspondence between route prefix 1, color 1, and SR policy 0 corresponding to PW 100. Therefore, when PE device 1 receives the first service packet from interface 1, it can determine that the first service packet is transmitted through PW 100. Using the address of the egress PE device (i.e., PE device 2) of PW 100 as the destination address 1, it obtains the destination address 1 and color 1 of the first service packet. Since destination address 1 and route prefix 1 belong to the same network segment, PE device 1 can determine that the first service packet matches routing table entry 1, and thus determine that the first service packet should be processed according to SR policy 0 corresponding to PW 100. It should be noted that typically, between a pair of PE devices, there is only one PW for each user.

[0105] In some other possible implementations, the space between the first node and the second node may include, in addition to the first PW, a third PW belonging to another user. In this case, the method 100 may further include: the first node receiving a fifth service message. For example, in... Figure 3a In the scenario shown, PE device 1 and PE device 2 include not only PW 100 but also PW 201. When PE device 1 receives the fifth service packet from interface 2, it can determine that the fifth service packet needs to be transmitted through PW 201. PE device 1's routing table can also include routing table entry 2: the correspondence between routing prefix 2, color 2, and SR policy 1 corresponding to PW 201. Therefore, PE device 1 obtains the destination address 2 (i.e., the address of PE device 2, the egress point of PW 201) and color 2 of the fifth service packet. Since destination address 2 and routing prefix 2 belong to the same network segment, PE device 1 can determine that the fifth service packet matches routing table entry 2, thus determining that the fifth service packet should be processed according to SR policy 1 corresponding to PW 201. It should be noted that the simulation process of the third PW for the fifth service packet by the first and second nodes is similar to the simulation process of the first PW for the first service packet. For specific implementation details, please refer to the following... Figure 9The illustrations in the examples are as follows.

[0106] In some possible implementations, a fourth PW may be included between the first node and another second node (hereinafter referred to as the fourth node). In this case, method 100 may further include: the first PE device receiving a seventh service message. For example, in... Figure 3a In the scenario shown, PW 202 is connected between PE device 1 and PE device 3. When PE device 1 receives the seventh service packet from interface 3, it can determine that the seventh service packet needs to be transmitted through PW 202. PE device 1's routing table includes routing table entry 3: the correspondence between routing prefix 3, color 3, and SR policy 2 corresponding to PW 202. Therefore, PE device 1 obtains the destination address 3 (i.e., the address of PE device 3, the egress point of PW 202) and color 3 of the seventh service packet. Since the destination address 3 and routing prefix 3 belong to the same network segment, PE device 1 can determine that the seventh service packet matches routing table entry 3, and thus determine that the seventh service packet should be processed according to SR policy 2 corresponding to PW 202. It should be noted that the simulation process of the fourth PW for the seventh service packet by the first node and the fourth node is similar to the simulation process of the first PW for the first service packet by the first node and the second node. For specific implementation details, please refer to the following... Figure 10 The illustrations in the examples are as follows.

[0107] S102, the first node performs SRv6 encapsulation on the first service message to obtain a second service message, the second service message including the information of the first service message and the first PW.

[0108] Both the first node and the second node have made the following preparatory work for implementing the method provided in the embodiments of this application:

[0109] On one hand, the first node and the second node define the instruction actions corresponding to the PW in their respective devices. These instruction actions are used to instruct the processing of service packets belonging to the PW. The first node, as the ingress PE device of the first PW, can implement the instruction actions configured on it through the instructions or pseudocode of the SRv6 policy, or through the instructions or pseudocode corresponding to the SID of the first node. The second node, as the egress PE device of the PW, can implement the instruction actions configured on it through the instructions or pseudocode corresponding to the SID of the second node.

[0110] As the entry point PE device for the first PW, the first node, as an example, can configure the correspondence between the SR policy and the first instruction action corresponding to the first PW. The first instruction action instructs the first node to execute S102, that is, the first node performs SRv6 encapsulation on the first service packet according to the first instruction action to obtain the second service packet. Corresponding to the above... Figure 3a In the scenario shown, the first PW is PW 100, the first node is PE device 1, the second node is PE device 2, the first service packet is service packet 1, and the second service packet is service packet 2. Therefore, S102 can be referred to the relevant description of S12 above. Alternatively, as another example, the SR policy on the first node may not correspond to the instruction action defined in this application embodiment, but instead configure a corresponding second instruction action for the first SID corresponding to the first PW on the first node. The second instruction action is used to instruct the first node to execute S102. Between S101 and S102, the method 100 may further include: the first node processes the first service packet based on the SR policy matching the first service packet to obtain a third service packet. The third service packet includes Segment list 0 corresponding to the first PW, and the destination address of the third service packet is the first SID of the first node. Then, S102 may include: the first node processes the third service packet according to the second instruction action corresponding to the first SID to obtain the second service packet. Corresponding to the above... Figure 3a In the scenario shown, the first PW is PW 201, the first node is PE device 1, the second node is PE device 2, the first service message is service message 3, the third service message is service message 4, and the second service message is service message 4'. Therefore, S102 can be referred to the relevant descriptions of S22 to S23 above. The structure of the second service message can be referred to above... Figure 5a , Figure 5b , Figure 6a and Figure 6b .

[0111] The first node acts as the ingress PE device for the first PW and the egress PE device for the second PW. The second PW is the PW between the third node and the first node. As an example, the first node can have different instruction actions corresponding to the second SID that corresponds to both the first and second PWs. For instance, configuring the correspondence between the second SID and the third instruction action, when the first node receives the fourth service packet from the third node through the second PW, step S101 can include: the first node performing SRv6 decapsulation on the fourth service packet according to the third instruction action corresponding to the second SID to obtain the first service packet. If the first node also configures the correspondence between the second SID and the fourth instruction action, then step S102 can include: the first node performing SRv6 encapsulation on the first service packet according to the fourth instruction action corresponding to the second SID to obtain the second service packet. Corresponding to the above... Figure 3b In the scenario shown, the first PW is PW 100, the second PW is PW 101, the first node is PE device 1, the second node is PE device 2, the third node is PE device 4, the fourth service message is service message 6, the first service message is service message 5, and the second service message is service message 6'. Then, S101 can refer to the relevant description of S34 above, and S102 can refer to the relevant description of S36 above.

[0112] For an ingress PE device, as an example, a corresponding SID can be configured for each PW on the ingress PE device. The Function in the SID is used to carry the instruction action to process the service packet to which the PW belongs. For example, the ingress PE device can configure corresponding SIDs for the first PW, the third PW, and the fourth PW respectively. The Function in the SID corresponding to the first PW is used to carry the instruction action a to process the service packet to which the first PW belongs (such as the first service packet); the Function in the SID corresponding to the third PW is used to carry the instruction action b to process the service packet to which the third PW belongs (such as the fifth service packet); and the Function in the SID corresponding to the fourth PW is used to carry the instruction action c to process the service packet to which the fourth PW belongs (such as the seventh service packet).

[0113] In the second service message, the payload carries the first service message, and the SRH includes the Segmentlist corresponding to the first PW, the IPv6 extension header (such as IPv6 DOH), or the SRH carrying the information of the first PW.

[0114] For example, the first instruction action can be used to instruct the first service packet to be encapsulated in the payload of the second service packet; the first instruction action can also be used to instruct the encapsulation of an SRH outside the first service packet, the SRH including the segment list corresponding to the first PW; the first instruction action can also be used to instruct the second service packet to carry information describing the first PW through an extended TLV field. In one case, the information of the first PW can be carried through the TLV field in the IPv6 extension header (such as IPv6 HBH or IPv6 DOH) in the second service packet. In this case, the value of the NextHeader field of the IPv6 extension header is used to indicate the type of the payload of the second service packet (i.e., the first service packet), that is, the service type emulated by the first PW. In another case, the information of the first PW can also be carried through the SRH TLV field in the second service packet. In this case, the value of the NextHeader field of the SRH is used to indicate the type of the payload of the second service packet. The payload type of the second service message (or the type of the first service message) can be, for example, TDM or ATM, or, for example, structured CES or SDH CES.

[0115] As another example, an ingress PE device can configure a corresponding SID for each PW that is different for an egress PE device, while at least one PW that is the same for an egress PE device can be configured with the same SID. The Function in the SID is used to carry the instruction action to process the service packets belonging to the at least one PW corresponding to that egress PE device. For example, the ingress PE device can configure corresponding SID a for the first PW and the third PW that are both egress PE devices of the second node, and configure corresponding SID b for the fourth PW that is an egress PE device of the fourth node. The Function in SID a is used to carry the common indication content of instruction action a and instruction action b; the Function in SID b is used to carry instruction action c. In this example, the segment lists corresponding to the first PW and the third PW are the same. Instruction action a is used not only to instruct that the service packets corresponding to the first PW or the third PW be encapsulated in the payload, and that the SRH including the segment list corresponding to the first PW or the third PW be encapsulated outside the received service packets, but also to instruct that information describing the attributes of the first PW or the third PW be carried in the received service packets through the extended TLV field.

[0116] It should be noted that for the configuration of the exported PE equipment, please refer to the relevant description in S105 below.

[0117] It should be noted that before method 100 is executed, each device in the SRv6 network can advertise its own SID in the SRv6 network through IGP or BGP-LS, so that each device can process the service packet based on the segment list in the service packet.

[0118] On the other hand, the ingress PE device obtains the SR policy and enables the processing of service packets in the SRv6 network. This prepares the ingress PE device for receiving and processing service packets, making PW emulation possible in the SRv6 network.

[0119] As an example, the controller can send an SR policy to the ingress PE device. This SR policy includes, but is not limited to, the segment list corresponding to each PW; for example, it may include the segment list corresponding to the first PW. Figure 3a Taking the scenario shown as an example, PW 100 can receive the Segment list 0 corresponding to PW 100, Segment list 1 corresponding to PW 201, and Segment list 2 corresponding to PW 202 sent by the controller 10 via PCEP. Segment list 0 and Segment list 1 can be the same or different.

[0120] As another example, the SR policy can also be statically configured on the ingress PE device, or the ingress PE device can determine the SR policy by its own calculation. The SR policy includes, but is not limited to, the segment list corresponding to each PW. For example, it can include the segment list corresponding to the first PW.

[0121] In a specific implementation, S102 may include: the first node encapsulating a Segment Routing Header (SRH) outside the first service packet, wherein the SRH includes a segment list corresponding to the first PW. Between S101 and S102, the method 100 may further include: the first node determining that the first service packet matches the SR policy. For example, if the SR policy corresponds to the first instruction action, then S102 may include: the first node performing the SRv6 encapsulation on the first service packet according to the first instruction action to obtain the second service packet. As another example, if the SR policy does not correspond to the instruction action provided in this application embodiment, and the first node's first SID corresponds to the second instruction action, then S101 and S102 may further include: the first node processing the first service packet based on the SR policy to obtain a third service packet; the first node determining the destination address of the third service packet as the first node's first SID; thus, S102 may include: the first node processing the third service packet according to the second instruction action to obtain the second service packet. As another example, if a second PW is established between the third node and the first node, then before S101, the method 100 may further include: the first node receiving a fourth service packet from the third node through the second PW; the first node determining the destination address of the fourth service packet as the second SID of the first node, the second SID corresponding to a third instruction action; then, S101 may include, for example, the first node performing SRv6 decapsulation on the fourth service packet according to the third instruction action to obtain the first service packet; thus, S102 may include, for example, the first node performing SRv6 encapsulation on the first service packet according to the fourth instruction action to obtain the second service packet, wherein the second SID corresponds to the fourth instruction action.

[0122] Information about a Processing Word (PW) describes the corresponding PW and may include, but is not limited to, Flags, PW ID, and Sequence Number. Flags may include multiple flag bits to indicate alarms or other issues in the service message, and also to indicate the processing operations for the service message when a problem occurs (e.g., setting all bits when an alarm occurs in the service message). The Sequence Number indicates the order of data frames in the service message, enabling the restoration of the service according to the order indicated by the Sequence Number. Optionally, this information may also include Length, which indicates the length of the received service message. For example, the information of the first PW may include: Flags, PW 100, Sequence Number, and the length of the first service message. In the TLV field carrying PW information, the value of the Type field is used to indicate that the Value field in the TLV field carries PW information; the Length field in the TLV field is an optional field, and its value is used to indicate the length of the PW information carried in the Value field; the Value field in the TLV field is used to carry PW information, and may include multiple Flags fields, PW ID field, Sequence Number field and Length field.

[0123] S103, the first node sends the second service message to the second node through the first PW.

[0124] S104, the second node receives the second service message from the first node through the first PW.

[0125] In specific implementation, after S102, the first node sends the second service packet along the first PW to the second node until the second service packet arrives at the second node. As an example, each device on the first PW can process the second service packet based on the SID indicated by SL in the SRH of the second service packet. For example, the intermediate device of the first PW forwards the second service packet based on the Function indication in the SID indicated by SL.

[0126] S105, the second node performs SRv6 decapsulation on the second service message to obtain the first service message.

[0127] The egress PE device of a PW defines its own SID corresponding to the PW. The SID corresponds to the instruction action used to process the service packets belonging to that PW. As an example, a corresponding SID can be configured for each PW on the egress PE device. The Function in the SID is used to carry the instruction action used to process the service packets belonging to that PW. For example, the first node can configure corresponding SIDs d and e for the first PW and the third PW respectively. The Function in SID a corresponding to the first PW is used to carry the instruction action d for processing the service packets belonging to the first PW (such as the second service packet); the Function in SID e corresponding to the third PW is used to carry the instruction action e for processing the service packets belonging to the third PW (such as the sixth service packet).

[0128] In a specific implementation, S105 may include, for example, the second node stripping the SRH of the second service packet, wherein the SRH includes the segment list corresponding to the first PW, so that the second node can obtain the first service packet in the payload of the second service packet. As an example, if the SRH of the second service packet includes the SID of the second node, and the SID of the second node corresponds to the first instruction action, then S102 may include, for example, the second node performing SRv6 decapsulation on the second service packet according to the first instruction action to obtain the first service packet.

[0129] For example, the instruction action corresponding to the SID of the second node can be used to instruct the removal of the IPv6 header and SRH from the second service packet to obtain the first service packet in the payload. The instruction action corresponding to the SID of the second node can also be used to instruct the retrieval of the first PW information from the TLV field of the extended IPv6 header of the second service packet. In one case, the information of the first PW can be carried through the TLV field of the IPv6 extended header (such as IPv6 HBH or IPv6 DOH) in the second service packet. In this case, the second node can obtain the information of the first PW from the TLV field of the IPv6 extended header of the second service packet, and the value of the Next Header field of the IPv6 extended header is used to indicate the type of the payload (i.e., the first service packet) of the second service packet, that is, the service type emulated by the first PW. In another case, the information of the first PW can also be carried through the SRH TLV field of the second service packet. In this case, the second node can obtain the information of the first PW from the SRH TLV field of the second service packet, and the value of the Next Header field of the SRH is used to indicate the type of the payload of the second service packet.

[0130] As another example, the outgoing PE device can configure the same SID for PWs that use that PE device as the outgoing PE device. The Function in the SID is used to carry instructions for processing the service packets belonging to the PW that uses that PE device as the outgoing PE device. For example, the outgoing PE device can configure corresponding SIDf for the first PW and the third PW that use that PE device as the outgoing PE device. The Function in SID f is used to carry the common indication content of instruction action d and instruction action e, that is, it can instruct to decapsulate the received second service packet using SRv6 to obtain the first service packet.

[0131] In some possible implementations, to ensure the reliability of PW emulation, the first PW can be verified before the egress PE device of the first PW decapsulates the received second service message. For example, the second node obtains the identifier of the first PW from the received second service message and checks from the control plane whether the egress PE device is configured with the first PW. If it is, the verification passes, and the above S105 is executed to realize the SRv6 decapsulation of the second service message; otherwise, if it is not found, the verification fails, and the second service message is discarded.

[0132] Corresponding to Figure 3a In the scenario shown, the first PW is PW 100, the first node is PE device 1, the second node is PE device 2, the first service message is service message 1, and the second service message is service message 2. Therefore, S105 can be referred to in the relevant description of S14 above. Alternatively, the first PW is PW 201, the first node is PE device 1, the second node is PE device 2, the first service message is service message 3, and the second service message is service message 4'. Therefore, S105 can be referred to in the relevant description of S25 above.

[0133] Optionally, after S105, the method 100 may further include the following S106:

[0134] S106, the second node restores the service corresponding to the first service message based on the information of the first PW, and obtains the ninth service message.

[0135] In practice, after the second node obtains the information of the first service message and the first PW based on S105, it can restore the service based on the information of the first PW.

[0136] For example, the second node can restore the first service packet to the corresponding service queue based on the first PW indicated by the PW ID in the information of the first PW; it can also process the first service packet according to the alarms and other issues of the first service packet indicated by the Flags in the information of the first PW; and it can sort the data frames based on the order of the data frames in the first service packet indicated by the SequenceNumber in the information of the first PW. Furthermore, the second node can verify the accuracy of obtaining the first service packet from the payload of the second service packet based on the length of the first service packet indicated by the Length in the information of the first PW. Thus, after the second PE device receives the second service packet, it executes S105-S106 to restore the service corresponding to the first PW.

[0137] In some possible implementations, after restoring the service corresponding to the first PW, the PE device can also send the restored service data to the corresponding service module or interface (such as the TDM service module or interface) on the export PE device, so that the corresponding service module or interface on the export PE device can continue to process the restored service data.

[0138] As an example, if the second node is connected to the destination host of the ninth service message but not to another PW segment, then after S106, the second node can send the ninth service message to the destination host. For example, corresponding to... Figure 3a In the scenario shown, the first PW is PW 100 and the second node is PE device 2. Then, after S106, PE device 2 can send the ninth service message (i.e. the service data obtained by PE device 2 in restoring service message 1) to the destination host through CE device 2.

[0139] As another example, if the second node connects to another PW—the fifth PW, that is, the second node is the exit PE device of the first PW and the inlet PE device of the fifth PW, where the fifth PW is the PW between the second node and the fifth node, then the second node can configure different instruction actions for the SID corresponding to both the first PW and the fifth PW. For example, configuring the correspondence between the SID and the fifth instruction action and the sixth instruction action, then when the second node receives the second service message from the first node through the first PW, S105 may include: the second node performs SRv6 decapsulation on the second service message according to the fifth instruction action to obtain the first service message; S106 may include: the second node performs service restoration according to the information of the first service message and the first PW to obtain the ninth service message. At this time, the method 100 may also include: the second node performs SRv6 encapsulation on the ninth service message according to the sixth instruction action to obtain the tenth service message, which includes the information of the ninth service message and the fifth PW; then, the second node can send the tenth service message to the fifth node through the fifth PW. Corresponding to the above... Figure 3b In the scenario shown, the first PW is PW 101, the fifth PW is PW 100, the first node is PE device 4, the second node is PE device 1, the fifth node is PE device 2, the first service message is service message 5, the second service message is service message 6, the ninth service message is service message 5, and the tenth service message is service message 6'. Then, S105 can refer to the relevant description of S34 above, and S106 can refer to the relevant description of S35 above.

[0140] As can be seen, in method 100, by defining the service packet processing method corresponding to PW on the PE devices at both ends of PW, the PE devices at both ends can realize functions such as encapsulating PW services, carrying information describing PW, and decapsulating. This enables fast and convenient processing of service packets of PW emulation services in SRv6 networks on the PE devices at both ends of PW, without the need for multi-protocol nesting, thus improving the processing efficiency of the service packets on the PE devices at both ends of PW. Moreover, it overcomes the problem that the current IP+UDP encapsulation method cannot realize PW emulation in networks with intermediate box devices. In addition, method 100 only requires the PE devices at both ends of PW to have interface boards for processing IP packets, without the need for dedicated service boards for processing other protocols, reducing the requirements for hardware performance and resources of the PE devices at both ends of PW, and expanding the application scope of PW emulation in SRv6 networks.

[0141] Figure 9This is a flowchart illustrating a message transmission method 200 provided in an embodiment of this application. Method 200 is applicable to PW (Programmable Message Warp) simulation of service messages in an SRv6 network. The difference between method 200 and method 100 is that method 200 describes the simulation process of another PW (i.e., a third PW) between a first node and a second node. For example, the first node could be... Figure 3a or Figure 3b In the PE device 1, the second node can be Figure 3a or Figure 3b In PE device 2, the first PW in method 100 is Figure 3a or Figure 3b PW100 in method 200, while the second PW is Figure 3a or Figure 3b PW 201 in [the document / reference]. See also: Figure 9 The method 200 may include, for example, S201 to S205:

[0142] S201, the first node obtains the fifth service message.

[0143] S202, the first node performs SRv6 encapsulation on the fifth service message to obtain the sixth service message, which includes the information of the fifth service message and the third PW.

[0144] The segment list corresponding to the third PW can be the same as or different from the segment list corresponding to the first PW, depending on whether the first and second nodes configure a unique corresponding SID for each different PW. If so, the segment list corresponding to the third PW is different from the segment list corresponding to the first PW. If the first node configures the same SID for the first and third PWs with the same path, and the second node configures the same SID for the first and third PWs with the same path, then the segment list corresponding to the third PW is the same as the segment list corresponding to the first PW.

[0145] S203, the first node sends the sixth service message to the second node through the third PW.

[0146] S204, the second node receives the sixth service message from the first node through the third PW.

[0147] S205, the second node performs SRv6 decapsulation on the sixth service message to obtain the fifth service message.

[0148] Optionally, the method 200 may further include the following step S206:

[0149] S206, the second node restores the service corresponding to the sixth service message based on the information of the third PW, and obtains the eleventh service message.

[0150] It should be noted that the specific implementation methods and technical effects of S201 to S206 can be found in the relevant descriptions of S101 to S106 in the above method 100.

[0151] Figure 10 This is a flowchart illustrating a message transmission method 300 provided in an embodiment of this application. Method 300 is applicable to PW (Programmable Message Warp) simulation of service messages in an SRv6 network. The difference between method 300 and method 100 is that it describes the simulation process of another PW (i.e., the fourth PW) between the first node and the fourth node. For example, the first node could be... Figure 3a or Figure 3b In the PE device 1, the fourth node can be Figure 3a or Figure 3b In the PE device 3, the first PW in method 100 is Figure 3a or Figure 3b PW100 in method 300, while the fourth PW is Figure 3a or Figure 3b PW 202 in the middle.

[0152] See Figure 10 The method 300 may include, for example, S301 to S305:

[0153] S301, the first node obtains the seventh service message.

[0154] S302, the first node performs SRv6 encapsulation on the seventh service message to obtain the eighth service message, which includes the information of the seventh service message and the fourth PW.

[0155] S303, the first node sends the eighth service message to the fourth node through the fourth PW.

[0156] S304, the fourth node receives the eighth service message from the first node through the fourth PW.

[0157] S305, the fourth node performs SRv6 decapsulation on the eighth service message to obtain the seventh service message.

[0158] Optionally, the method 300 may further include the following S306:

[0159] S306, the fourth node restores the service corresponding to the seventh service message based on the information of the fourth PW, and obtains the twelfth service message.

[0160] It should be noted that the specific implementation methods of S301 to S306 and the technical effects achieved can be found in the relevant descriptions of S101 to S106 in the above method 100.

[0161] Furthermore, this application embodiment also provides a message transmission apparatus 1100, see [link to relevant documentation]. Figure 11 As shown. Figure 11 This is a schematic diagram of a message transmission apparatus 1100 provided in an embodiment of this application. The message transmission apparatus 1100 is applied to a first node, and a first PW is established between the first node and a second node. The apparatus 1100 may include a first obtaining unit 1101, a first processing unit 1102, and a first sending unit 1103. The apparatus 1100 can be used to execute method 100, method 200, or method 300 in the above embodiments.

[0162] The first obtaining unit 1101 is used to obtain the first service message.

[0163] The first processing unit 1102 is configured to encapsulate the first service message using SRv6 to obtain a second service message, wherein the second service message includes information of the first service message and the first PW.

[0164] The first sending unit 1103 is used to send the second service message to the second node through the first PW.

[0165] The specific implementation method and effect of the operation performed by the first obtaining unit 1101 can be found in the relevant description of S101 in method 100. The specific implementation method and effect of the operation performed by the first processing unit 1102 can be found in the relevant description of S102 in method 100. The specific implementation method and effect of the operation performed by the first sending unit 1103 can be found in the relevant description of S103 in method 100.

[0166] In one implementation, the first processing unit 1101 is specifically used to: encapsulate a segment routing header (SRH) outside the first service message, wherein the SRH includes a segment list corresponding to the first PW.

[0167] In one implementation, the apparatus 1100 may further include a first determining unit. This first determining unit is configured to determine whether the first service packet matches the segment routing policy (SR policy).

[0168] As an example, if the SR policy corresponds to the first instruction action, then the first processing unit 1102 is specifically used to: perform SRv6 encapsulation on the first service message according to the first instruction action to obtain the second service message.

[0169] As another example, the device 1100 may further include: a second processing unit and a second determining unit. The second processing unit is configured to process the first service packet based on the SR policy to obtain a third service packet; the second determining unit is configured to determine that the destination address of the third service packet is a first SID of the first node, and the first SID corresponds to a second instruction action. Then, the first processing unit 1102 is specifically configured to: process the third service packet according to the second instruction action to obtain the second service packet.

[0170] In one implementation, a second PW is established between the third node and the first node. The device 1100 may further include a receiving unit and a third determining unit. The receiving unit is configured to receive a fourth service packet from the third node via the second PW. The third determining unit is configured to determine that the destination address of the fourth service packet is the second SID of the first node, and the second SID corresponds to a third instruction action. The first obtaining unit 1101 is specifically configured to: perform SRv6 decapsulation on the fourth service packet according to the third instruction action to obtain the first service packet. The second SID corresponds to the fourth instruction action. The first processing unit 1102 is specifically configured to: perform SRv6 encapsulation on the first service packet according to the fourth instruction action to obtain the second service packet.

[0171] In one implementation, the device 1100 may further include: a second obtaining unit, a third processing unit, and a second sending unit. The second obtaining unit is used to obtain a fifth service message; the third processing unit is used to encapsulate the fifth service message using SRv6 to obtain a sixth service message, the sixth service message including the information of the fifth service message and the third PW; the second sending unit is used to send the sixth service message to the second node through the third PW. The specific implementation and effects of the second obtaining unit's operations can be found in the description of S201 in method 200. The specific implementation and effects of the third processing unit's operations can be found in the description of S202 in method 200. The specific implementation and effects of the second sending unit's operations can be found in the description of S203 in method 200.

[0172] In one implementation, the IPv6 DOH of the second service packet carries the information of the first PW; or, the SRH of the second service packet carries the information of the first PW.

[0173] In one implementation, the information of the first PW may include: multiple flags, the identifier of the first PW, and a sequence number.

[0174] In one implementation, the first service message is a message corresponding to a non-Ethernet service. The non-Ethernet service includes any one of the following services: Frame Relay service, Time Division Multiplexing (TDM) service, or Asynchronous Transfer Mode (ATM) service. The TDM service may include, but is not limited to: E1 service, T1 service, E3 service, T3 service, SONET service, or SDH service.

[0175] Furthermore, this application embodiment also provides a message transmission apparatus 1200, see [link to relevant documentation]. Figure 12 As shown. Figure 12 This is a schematic diagram of a message transmission apparatus 1200 provided in an embodiment of this application. The message transmission apparatus 1200 is applied to a second node, and a first PW is established between the first node and the second node. The apparatus 1200 may include a first receiving unit 1201 and a first processing unit 1202. The apparatus 1200 can be used to execute method 100, method 200, or method 300 in the above embodiments.

[0176] The first receiving unit 1201 is used to receive a second service message from the first node through the first PW, wherein the second service message includes the information of the first service message and the first PW.

[0177] The first processing unit 1202 is used to decapsulate the second service packet using segment routing SRv6 based on Internet Protocol version 6 to obtain the first service packet.

[0178] The specific implementation method and effect of the operation performed by the first receiving unit 1201 can be found in the relevant description of S104 in method 100. The specific implementation method and effect of the operation performed by the first processing unit 1202 can be found in the relevant description of S105 in method 100.

[0179] In one implementation, the first processing unit 1201 is specifically used to: strip the segment routing header (SRH) of the second service packet, wherein the SRH includes the segment list corresponding to the first PW.

[0180] In one implementation, the SRH of the second service message includes the SID of the second node, and the SID of the second node corresponds to the first instruction action. The first processing unit 1201 is specifically used to: perform SRv6 decapsulation on the second service message according to the first instruction action to obtain the information of the first service message and the first PW.

[0181] In one implementation, the device 1200 may further include a restoration unit. This restoration unit is configured to restore the service corresponding to the first service message based on the information of the first PW, thereby obtaining a third service message. The specific implementation method and effect of the restoration unit's operation can be found in the relevant description of S106 in method 100.

[0182] As an example, the apparatus 1200 may further include: a first sending unit for sending the third service message to a destination host.

[0183] As another example, a second PW is established between the second node and the third node. The device 1200 may further include a second processing unit and a second sending unit. The second processing unit is used to perform SRv6 encapsulation on the third service message to obtain a fourth service message, the fourth service message including information from the third service message and the second PW. The second sending unit is used to send the fourth service message to the third node through the second PW. The SRH of the second service message may include the SID of the second node, which also corresponds to a second instruction action. Specifically, the second processing unit is used to perform SRv6 encapsulation on the third service message according to the second instruction action to obtain the fourth service message.

[0184] In one implementation, the IPv6 DOH of the second service packet carries the information of the first PW; or, the SRH of the second service packet carries the information of the first PW.

[0185] In one implementation, the information of the first PW may include: multiple flags, the identifier of the first PW, and a sequence number.

[0186] In one implementation, the first service message is a message corresponding to a non-Ethernet service. The non-Ethernet service includes any one of the following services: Frame Relay service, Time Division Multiplexing (TDM) service, or Asynchronous Transfer Mode (ATM) service. The TDM service may include, but is not limited to: E1 service, T1 service, E3 service, T3 service, SONET service, or SDH service.

[0187] It should be noted that the specific implementation methods and effects of the message transmission apparatus 1100 and message transmission apparatus 1200 provided in the embodiments of this application can be found in the relevant descriptions in the above-mentioned methods 100, 200 or 300, and will not be repeated here.

[0188] In addition, this application also provides a communication device 1300, see [link to relevant documentation]. Figure 13 As shown, Figure 13 This is a schematic diagram of a communication device 1300 provided in an embodiment of this application. The communication device 1300 can be used to execute method 100, method 200 or method 300 in the above embodiments.

[0189] like Figure 13As shown, the communication device 1300 may include a processor 1310 and a memory 1320 coupled to the processor 1310. The processor 1310 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor 1310 may refer to a single processor or may include multiple processors. Memory 1320 may include volatile memory, such as random-access memory (RAM); memory may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); memory 1320 may also include combinations of the above types of memory. Memory 1320 may refer to a single memory or may include multiple memories. In one embodiment, the memory 1320 stores computer-readable instructions, which include multiple software modules, such as a first processing module 1321 and a second processing module 1322. Furthermore, it may include at least one of a third, fourth, and fifth processing module, which may correspond to a functional module of the first processing unit 1102 in the message transmission device 1100, or to a functional module of the first processing unit 1202 in the message transmission device 1200. After executing each software module, the processor 1310 can perform corresponding operations according to the instructions of each software module.In this embodiment, the operation performed by a software module actually refers to the operation performed by the processor 1310 according to the instructions of the software module. For example, the operation of the first processing module 1321 to "encapsulate the first service message with SRv6 to obtain the second service message" can actually refer to the operation of the processor 1310 to "encapsulate the first service message with SRv6 to obtain the second service message" according to the instructions of the first processing module 1321. In this case, the first processing module 1321 can correspond to the first processing unit 1102 in the message transmission device 1100.

[0190] In one example, the communication device 1300 can execute method 100 in the above embodiments. When the communication device 1300 executes method 100 in the above embodiments: the processor 1310 is used to execute all processing-related operations in method 100. For example, the processor 1310 is used to encapsulate a first service message using SRv6 to obtain a second service message; as another example, the processor 1310 is also used to decapsulate the second service message using SRv6 to obtain the first service message.

[0191] In one example, the communication device 1300 can execute method 200 in the above embodiments. When the communication device 1300 executes method 200 in the above embodiments: the processor 1310 is used to execute all processing-related operations in method 200. For example, the processor 1310 is used to encapsulate the fifth service message using SRv6 to obtain the sixth service message; as another example, the processor 1310 is also used to decapsulate the sixth service message using SRv6 to obtain the fifth service message.

[0192] In addition, this application also provides a communication system 1400, see [link to relevant documentation]. Figure 14 As shown. Figure 14 This is a schematic diagram of the structure of a communication system 1400 provided in an embodiment of this application. The communication system 1400 may include a first node 1401 and a second node 1402.

[0193] The first node 1401, for example, could be... Figure 3a or Figure 3b PE device 1 in the middle can also be Figure 8 , Figure 9 or Figure 10 The first node in the method is used to execute the operations performed by the first node in method 100, method 200, and method 300.

[0194] The second node 1402, for example, could be... Figure 3a or Figure 3b PE device 2 or PE device 3 in the text can also be Figure 8 , Figure 9 or Figure 10 The second node in the method is used to execute the operations performed by the second node in method 100, method 200 and method 300.

[0195] For details on the specific implementation and effects of the communication system 1400, please refer to the relevant descriptions of methods 100, 200 and 300 above.

[0196] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform any one or more operations of the methods described in any of the foregoing embodiments (e.g., method 100, method 200, or method 300).

[0197] This application also provides a computer program product, including a computer program that, when run on a computer, causes the computer to perform any one or more operations of the methods described in any of the foregoing embodiments (e.g., method 100, method 200, or method 300).

[0198] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0199] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0200] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical business division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0201] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0202] Furthermore, the various business units in the embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software business unit.

[0203] If the integrated unit is implemented as a software business unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0204] Those skilled in the art will recognize that, in one or more of the examples above, the services described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these services can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of computer programs from one place to another. Storage media can be any available medium accessible to general-purpose or special-purpose computers.

[0205] The above specific embodiments further illustrate the purpose, technical solution and beneficial effects of this application. It should be understood that the above are only specific embodiments of this application.

[0206] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method of packet transmission, characterized by, A method performed by a first node, a first pseudo-wire (PW) being established between the first node and a second node, the method comprising: obtaining a first service packet, the first service packet being a packet corresponding to a non-Ethernet layer 2 service, the non-Ethernet layer 2 service including any one of a frame relay service, a time division multiplexing (TDM) service, or an asynchronous transfer mode (ATM) service; performing segment routing version 6 (SRv6) encapsulation on the first service packet to obtain a second service packet, the second service packet including the first service packet and information of the first PW; sending the second service packet to the second node through the first PW.

2. The method of claim 1, wherein, The SRv6 encapsulation on the first service packet includes: encapsulating a segment routing header (SRH) outside the first service packet, the SRH including a segment list corresponding to the first PW.

3. The method of claim 1, wherein, The method further includes: determining that the first service packet matches a segment routing policy (SR policy).

4. The method of claim 3, wherein, The SR policy corresponds to a first instruction action, and the SRv6 encapsulation on the first service packet to obtain the second service packet includes: performing the SRv6 encapsulation on the first service packet according to the first instruction action to obtain the second service packet.

5. The method of claim 3, wherein, The method further includes: processing the first service packet based on the SR policy to obtain a third service packet; determining that a destination address of the third service packet is a first SID of the first node, the first SID corresponding to a second instruction action; The SRv6 encapsulation on the first service packet to obtain the second service packet includes: processing the third service packet according to the second instruction action to obtain the second service packet.

6. The method according to any one of claims 1 to 5, characterized in that, A second PW is established between a third node and the first node, and the method further includes: receiving a fourth service packet from the third node through the second PW; determining that a destination address of the fourth service packet is a second SID of the first node, the second SID corresponding to a third instruction action; The obtaining of the first service packet includes: performing SRv6 decapsulation on the fourth service packet according to the third instruction action to obtain the first service packet.

7. The method of claim 6, wherein, The second SID corresponds to a fourth instruction action, and the SRv6 encapsulation on the first service packet to obtain the second service packet includes: performing SRv6 encapsulation on the first service packet according to the fourth instruction action to obtain the second service packet.

8. The method according to any one of claims 1 to 5, characterized in that, A third PW is established between the first node and the second node, and the method further includes: obtaining a fifth service packet; performing SRv6 encapsulation on the fifth service packet to obtain a sixth service packet, the sixth service packet including the fifth service packet and information of the third PW; sending the sixth service packet to the second node through the third PW.

9. The method according to any one of claims 1 to 5, characterized in that, The information of the first PW is carried in a destination options header (DOH) of an Internet Protocol version 6 (IPv6) of the second service packet.

10. The method according to any one of claims 1 to 5, characterized in that, The SRH of the second service packet carries information of the first PW.

11. The method according to any one of claims 1 to 5, characterized in that, The information of the first PW includes an identifier of the first PW, a plurality of flags Flags, and a sequence number Sequence Number.

12. A method of packet transmission, characterized by, A second node is configured to establish a first pseudo-wire (PW) with a first node, and the method comprises: receiving a second service packet from the first node via the first PW, the second service packet including a first service packet and information of the first PW; performing segment routing version 6 (SRv6) decapsulation on the second service packet to obtain the first service packet, the first service packet being a packet corresponding to a non-Ethernet layer 2 service, the non-Ethernet layer 2 service including any one of a frame relay service, a time-division multiplexing (TDM) service, or an asynchronous transfer mode (ATM) service.

13. The method of claim 12, wherein, The SRv6 decapsulation on the second service packet includes: stripping a segment routing header (SRH) of the second service packet, the SRH including a segment list corresponding to the first PW.

14. The method of claim 12, wherein, The SRH of the second service packet includes a SID of the second node, the SID of the second node corresponding to a first instruction action, and the SRv6 decapsulation on the second service packet to obtain the first service packet includes: performing SRv6 decapsulation on the second service packet according to the first instruction action to obtain the first service packet.

15. The method according to any one of claims 12-14, characterized in that, The method further includes: restoring a service corresponding to the first service packet according to the information of the first PW to obtain a third service packet.

16. The method of claim 15, wherein, The method further includes: sending the third service packet to a destination host.

17. The method of claim 15, wherein, A second PW is established between the second node and a third node, and the method further includes: performing SRv6 encapsulation on the third service packet to obtain a fourth service packet, the fourth service packet including the third service packet and information of the second PW; sending the fourth service packet to the third node via the second PW.

18. The method of claim 17, wherein, The SRH of the second service packet includes a SID of the second node, the SID of the second node further corresponding to a second instruction action, and the SRv6 encapsulation on the third service packet to obtain the fourth service packet includes: performing SRv6 encapsulation on the third service packet according to the second instruction action to obtain the fourth service packet.

19. The method according to any one of claims 12-14, characterized in that, An IPv6 destination options header (DOH) of the second service packet carries information of the first PW.

20. The method of any one of claims 12-14, wherein, The SRH of the second service packet carries information of the first PW.

21. The method according to any one of claims 12-14, characterized in that, The information of the first PW includes an identifier of the first PW, a plurality of flags Flags, and a sequence number Sequence Number.

22. An apparatus for packet transmission, the apparatus comprising: A first node is configured to establish a first pseudo-wire (PW) with a second node, and the apparatus comprises: The first obtaining unit is configured to obtain a first service packet, the first service packet being a packet corresponding to a non-Ethernet layer 2 service, the non-Ethernet layer 2 service including any one of a frame relay service, a time division multiplexing (TDM) service, or an asynchronous transfer mode (ATM) service; The first processing unit is configured to perform sixth version Internet Protocol (IPv6) segment routing (SRv6) encapsulation on the first service packet to obtain a second service packet, the second service packet including the first service packet and information of the first PW. The first sending unit is configured to send the second service packet to the second node through the first PW.

23. The apparatus of claim 22, wherein, The first processing unit is specifically configured to: encapsulate a segment routing header (SRH) outside the first service packet, the SRH including a segment list corresponding to the first PW.

24. The apparatus of claim 22, wherein, The apparatus further includes: The first determining unit is configured to determine that the first service packet matches a segment routing policy (SR policy).

25. The apparatus of claim 24, wherein, The SR policy corresponds to a first instruction action, and the first processing unit is specifically configured to: perform the SRv6 encapsulation on the first service packet according to the first instruction action to obtain the second service packet.

26. The apparatus of claim 24, wherein, The apparatus further includes: The second processing unit is configured to process the first service packet based on the SR policy to obtain a third service packet. The second determining unit is configured to determine that a destination address of the third service packet is a first SID of the first node, the first SID corresponding to a second instruction action. The first processing unit is specifically configured to: perform processing on the third service packet according to the second instruction action to obtain the second service packet.

27. The apparatus of any of claims 22-26, wherein, A second PW is established between a third node and the first node, and the apparatus further includes: The receiving unit is configured to receive a fourth service packet from the third node through the second PW. The third determining unit is configured to determine that a destination address of the fourth service packet is a second SID of the first node, the second SID corresponding to a third instruction action. The first obtaining unit is specifically configured to: perform SRv6 decapsulation on the fourth service packet according to the third instruction action to obtain the first service packet.

28. The apparatus of claim 27, wherein, The second SID corresponds to a fourth instruction action, and the first processing unit is specifically configured to: perform SRv6 encapsulation on the first service packet according to the fourth instruction action to obtain the second service packet.

29. The apparatus of any one of claims 22-26, wherein, A third PW is established between the first node and the second node, and the apparatus further includes: The second obtaining unit is configured to obtain a fifth service packet. The third processing unit is configured to perform SRv6 encapsulation on the fifth service packet to obtain a sixth service packet, the sixth service packet including the fifth service packet and information of the third PW. The second sending unit is configured to send the sixth service packet to the second node through the third PW.

30. The apparatus of any one of claims 22-26, wherein, Information of the first PW is carried in a destination options header (DOH) of the second service packet.

31. The apparatus of any one of claims 22-26, wherein, The SRH of the second service packet carries information of the first PW.

32. The device of any one of claims 22-26, wherein, The information of the first PW includes an identifier of the first PW, a plurality of flags Flags, and a sequence number Sequence Number.

33. An apparatus for packet transmission, the apparatus comprising: A second node is configured to establish a first pseudo-wire (PW) with a first node, and the device comprises: a first receiving unit configured to receive a second service packet from the first node via the first PW, the second service packet including a first service packet and information of the first PW; a first processing unit configured to perform segment routing version 6 (SRv6) decapsulation on the second service packet based on a sixth version of the Internet Protocol (IPv6) to obtain the first service packet, the first service packet being a packet corresponding to a non-Ethernet layer 2 service, the non-Ethernet layer 2 service including any one of a frame relay service, a time-division multiplexing (TDM) service, or an asynchronous transfer mode (ATM) service.

34. The apparatus of claim 33, wherein, The first processing unit is specifically configured to: strip a segment routing header (SRH) of the second service packet, the SRH including a segment list corresponding to the first PW.

35. The apparatus of claim 33, wherein, The SRH of the second service packet includes a SID of the second node, the SID of the second node corresponding to a first instruction action, and the first processing unit is specifically configured to: perform SRv6 decapsulation on the second service packet according to the first instruction action to obtain the first service packet and the information of the first PW.

36. The apparatus of any one of claims 33-35, wherein, The device further comprises: a restoring unit configured to restore a service corresponding to the first service packet according to the information of the first PW to obtain a third service packet.

37. The device of claim 36, wherein, The device further comprises: a first sending unit configured to send the third service packet to a destination host.

38. The device of claim 36, wherein, A second PW is established between the second node and a third node, and the device further comprises: a second processing unit configured to perform SRv6 encapsulation on the third service packet to obtain a fourth service packet, the fourth service packet including the third service packet and information of the second PW; a second sending unit configured to send the fourth service packet to the third node via the second PW.

39. The device of claim 38, wherein, The SRH of the second service packet includes a SID of the second node, the SID of the second node also corresponding to a second instruction action, and the second processing unit is specifically configured to: perform SRv6 encapsulation on the third service packet according to the second instruction action to obtain the fourth service packet.

40. The apparatus of any one of claims 33-35, wherein, The first PW information is carried in a destination options header (DOH) of the second service packet.

41. The device of any one of claims 33-35, wherein, The SRH of the second service packet carries information of the first PW.

42. The device of any one of claims 33-35, wherein, The information of the first PW includes an identifier of the first PW, a plurality of flags Flags, and a sequence number Sequence Number.

43. A communications device, characterized by The communication device includes a memory and a processor; The memory is configured to store program code; The processor is configured to execute instructions in the program code, so that the communication device performs the method of any one of claims 1-11.

44. A communications device, characterized by The communication device comprises a memory and a processor; The memory is configured to store program codes; The processor is configured to execute instructions in the program codes, so that the communication device performs the method in any one of claims 12-21.

45. A communication system, characterized by The communication system comprises a first node and a second node; The first node is configured to perform the method in any one of claims 1-11; The second node is configured to perform the method in any one of claims 12-21.

46. A computer program product, characterised in that, A program, when executed on a processor, implements the method in any one of claims 1-21.

47. A computer-readable storage medium, characterized in that, A computer readable storage medium comprises instructions, when executed on a processor, implements the method in any one of claims 1-21.

Images