Service message transmission method and apparatus, network device, and storage medium

Abstract

The present disclosure provides a service message transmission method and apparatus, a network device, and a storage medium. The method is applied to a first provider edge (PE), and comprises: receiving a pseudo wire emulation edge to edge (PWE3) service message from a source customer edge (CE), the PWE3 service message comprising a target pseudo wire (PW) identifier, the target PW identifier being used for indicating a PW between the source CE and a destination CE; encapsulating the PWE3 service message on the basis of the target PW identifier, to obtain a segment routing IPv6 (SRv6) service message; and sending the SRv6 service message to a second PE through a target SRv6 tunnel between the first PE and the second PE, the second PE being a PE connected to the destination CE.

Description

Business message transmission method, device, network equipment and storage medium

[0001] This disclosure claims priority to Chinese patent application No. 202410204959.0, filed on February 23, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present disclosure relates to the field of communication technology, and in particular to a method, apparatus, network equipment, and storage medium for transmitting a service message. Background Art

[0003] Pseudowire emulation edge to edge (PWE3) uses the label distribution protocol (LDP) as its signaling protocol. It carries various Layer 2 services (such as various Layer 2 packets) on the customer edge (CE) side through a tunnel and transparently transmits Layer 2 packets on the CE side. Summary of the Invention

[0004] In one aspect, embodiments of the present disclosure provide a method for transmitting service packets, applied to a first operator edge device (PE). The method comprises: receiving an edge-to-edge pseudowire emulation (PWE3) service packet from a source customer edge device (CE), the PWE3 service packet including a target pseudowire (PW) identifier, which indicates the PW between the source CE and a destination CE. Based on the target PW identifier, the PWE3 service packet is encapsulated to obtain a segment-routed SRv6 service packet based on an Internet Protocol version 6 forwarding plane. The SRv6 service packet is then sent to the second PE via a target SRv6 tunnel between the first PE and the second PE, where the second PE is connected to the destination CE.

[0005] In another aspect, embodiments of the present disclosure provide another method for transmitting service packets, which is applied to a second PE connected to a destination CE. The method includes: receiving an SRv6 service packet from a first PE via a target SRv6 tunnel, wherein the SRv6 service packet is a service packet obtained by the first PE encapsulating a PWE3 service packet using a target PW identifier, wherein the target PW identifier is used to indicate the PW between the source CE and the destination CE, and the PWE3 service packet is received by the first PE from the source CE. The SRv6 service packet is decapsulated to obtain a PWE3 service packet, and the PWE3 service packet is sent to the destination CE.

[0006] On the other hand, an embodiment of the present disclosure provides a device for transmitting a service message, which includes: an acquisition module, a processing module, and a sending module.

[0007] The acquisition module is configured to receive edge-to-edge pseudowire emulation (PWE3) service packets from a source customer edge device (CE). The PWE3 service packets include a target pseudowire (PW) identifier, which indicates the PW between the source CE and the destination CE. The processing module is configured to encapsulate the PWE3 service packets based on the target PW identifier to obtain segment-routed SRv6 service packets based on the Internet Protocol version 6 forwarding plane. The sending module is configured to send the SRv6 service packets to the second PE via a target SRv6 tunnel between the first PE and the second PE, where the second PE is connected to the destination CE.

[0008] On the other hand, an embodiment of the present disclosure provides another device for transmitting service messages, which includes: an acquisition module, a processing module and a sending module.

[0009] The acquisition module is configured to receive an SRv6 service message from the first PE via the target SRv6 tunnel. The SRv6 service message is obtained by the first PE encapsulating a PWE3 service message using the target PW identifier. The target PW identifier indicates the PW between the source CE and the destination CE. The PWE3 service message is received by the first PE from the source CE. The processing module is configured to decapsulate the SRv6 service message to obtain a PWE3 service message. The sending module is configured to send the PWE3 service message to the destination CE.

[0010] In another aspect, an embodiment of the present disclosure provides an electronic device comprising: a memory and a processor. The memory and the processor are coupled. The memory is configured to store a computer program. When the processor executes the computer program, the method for transmitting a service message according to any of the above embodiments is implemented.

[0011] On the other hand, an embodiment of the present disclosure provides a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the method for transmitting the service message of any of the above embodiments is implemented.

[0012] On the other hand, an embodiment of the present disclosure provides a computer program product, which includes computer program instructions, and when the computer program instructions are executed by a processor, implements the method for transmitting the service message of any of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in the present disclosure, the following briefly introduces the drawings required for use in some embodiments of the present disclosure. Obviously, the drawings described below are only drawings of some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0014] FIG1 is a schematic diagram of a communication system provided by some embodiments of the present disclosure.

[0015] FIG2 is a flow chart of a method for transmitting a service message provided in some embodiments of the present disclosure.

[0016] FIG3 is a flow chart of another method for transmitting a service message provided in some embodiments of the present disclosure.

[0017] FIG4 is a flow chart of another method for transmitting a service message provided in some embodiments of the present disclosure.

[0018] FIG5 is a schematic structural diagram of a device for transmitting service messages provided in some embodiments of the present disclosure.

[0019] FIG6 is a schematic structural diagram of another device for transmitting service messages provided in some embodiments of the present disclosure.

[0020] FIG7 is a schematic structural diagram of a service message transmission device provided in some embodiments of the present disclosure. DETAILED DESCRIPTION

[0021] The following will clearly and completely describe the technical solutions of this disclosure in conjunction with the accompanying drawings. Obviously, the embodiments described are only some of the embodiments of this disclosure, not all of them. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0022] It should be noted that in this disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this disclosure as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0023] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the quantity of the technical features indicated. Therefore, a feature specified as "first" or "second" may explicitly or implicitly include one or more of the features.

[0024] In the description of this disclosure, unless otherwise specified, " / " means "or." For example, A / B can mean A or B. "And / or" in this document simply describes an association relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can mean: A exists alone, A and B exists simultaneously, and B exists alone. Furthermore, "at least one" means one or more, and "a plurality" means two or more.

[0025] Before introducing in detail the method for transmitting a service message provided by an embodiment of the present disclosure, the implementation environment and application scenarios of the embodiment of the present disclosure are first introduced.

[0026] First, the application scenarios of the embodiments of the present disclosure are introduced.

[0027] PWE3 uses LDP as the signaling protocol, carries various Layer 2 services on the CE side through tunnels, and transparently transmits Layer 2 packets on the CE side.

[0028] With the transition from the fourth generation mobile communication technology (4G) to the fifth generation mobile communication technology (5G), software-defined networks (SDN) are increasingly being used in a wide range of scenarios. For example, traditional virtual private networks (VPNs) are transitioning to SDN.

[0029] However, in traditional Layer 2 virtual private network (L2VPN) networking, narrowband PWE3 technology is used. With the transition from 4G to 5G, Segment Routing over IPv6 (SRv6) tunnels based on the Internet Protocol version 6 (IPv6) forwarding plane have become the primary tunnels for carrying services in SDN. Therefore, during the transition from traditional VPN to SDN, support for SRv6 technology will not be expanded in traditional narrowband PWE3 networking, affecting the compatibility of new and existing equipment in the network.

[0030] In order to solve the above problems, the embodiments of the present disclosure provide a method for transmitting service messages, and the method for transmitting service messages provided by the embodiments of the present disclosure is applied to the scenario of transition from traditional VPN to SDN. The present disclosure enables PE to support the SRv6 protocol in the existing PWE3 network structure, and encapsulates the PWE3 service messages from CE, so that the processed PWE3 service messages can reach the opposite PE through the SRv6 tunnel. Then, the opposite PE decapsulates the processed PWE3 service messages, restores them to the original PWE3 service messages, and sends the original PWE3 service messages to the destination CE, thereby realizing the SRv6 technology to carry PWE3 service messages, improving the compatibility of new and old equipment in the network, facilitating the transition from traditional VPN to SDN, making the replacement of old and new networks more convenient, reducing the difficulty of network upgrades, and reducing the risks of technology updates.

[0031] The implementation environment of the embodiments of the present disclosure is introduced below.

[0032] As shown in Figure 1, a schematic diagram of a communication system provided in an embodiment of the present disclosure is provided. The communication system may include: a first PE 101, a second PE 102, a source CE 103, and a destination CE 104. The first PE 101 and the second PE 102 are connected via an SRv6 tunnel of a virtual private wire service (VPWS). The first PE 101 and the source CE 103 are connected via a VPN, and the second PE 102 and the destination CE 104 are also connected via a VPN. The two VPNs are different.

[0033] Source CE 103 may obtain an initial service packet carrying the identifier of destination CE 104 and, based on the identifier of destination CE 104, determine the target PW identifier of the pseudo wire (PW) between source CE 103 and destination CE 104. Source CE 103 may then encapsulate the initial service packet into a PWE3 service packet using the target PW identifier and send the PWE3 service packet carrying the target PW identifier to first PE 101.

[0034] First PE 101 can receive a PWE3 service packet from source CE 103 and, based on the target PW identifier in the PWE3 service packet, encapsulate the PWE3 service packet into an SRv6 service packet. Then, first PE 101 can send the SRv6 service packet to second PE 102 via the target SRv6 tunnel connected to second PE 102.

[0035] The second PE 102 receives the SRv6 service packet from the first PE 101 through the target SRv6 tunnel connected to the first PE 101, decapsulates the SRv6 service packet to obtain a PWE3 service packet, and then sends the PWE3 service packet to the destination CE 104.

[0036] The destination CE 104 may receive the PWE3 service message from the second PE 102 and decapsulate the PWE3 service message to obtain an initial service message.

[0037] After introducing the application scenario and implementation environment of the embodiment of the present disclosure, the following describes in detail the service message transmission method provided by the embodiment of the present disclosure in combination with the above implementation environment.

[0038] An embodiment of the present disclosure provides a method for transmitting a service message, which is applied to a first PE. As shown in FIG. 2 , the method for transmitting the service message may include S201 - S203 .

[0039] In S201 , a first PE receives a PWE3 service packet from a source CE.

[0040] The PWE3 service message may include a target PW identifier, where the target PW identifier is used to indicate the PW between the source CE and the destination CE.

[0041] As a possible implementation, a first PE is configured with an LDP-based L2VPN tunnel and an SRv6 tunnel, and the first PE's interior gateway protocol (IGP) enables the LDP-based L2VPN tunnel and the SRv6 tunnel. Furthermore, an LDP L2VPN tunnel of a first VPN is configured on the first PE, and the first PE is connected to a source CE in the first VPN via the LDP L2VPN tunnel of the first VPN. The first PE can receive PWE3 service packets from the source CE via the LDP L2VPN tunnel of the first VPN to obtain the PWE3 service packets to be transmitted.

[0042] In the embodiment of the present disclosure, the PWE3 service message is encapsulated with an initial service message, and the initial service message is a message sent by a user equipment and received by a source CE.

[0043] It should be noted that the embodiments of the present disclosure do not limit the service type of the initial service message. For example, the initial service message may be a message for a voice service. For another example, the initial service message may be a message for a short message service. For another example, the initial service message may be a message for an access service.

[0044] As a possible implementation, the PWE3 service message can be any of the following messages: Ethernet (ETH) message, asynchronous transfer mode (ATM) message, time division multiplexing (TDM) transmission message, frame relay (FR) message, point-to-point protocol (PPP) message.

[0045] That is, the improved PWE3 based on the present disclosure can be applied in broadband metropolitan area access networks or mobile bearer networks to carry various types of services such as ETH, ATM, TDM, FR, and PPP.

[0046] In S202 , the first PE encapsulates the PWE3 service message according to the target PW identifier to obtain an SRv6 service message.

[0047] As a possible implementation method, the first PE stores a preset segment identifier (SID) list and the identifiers of the CEs at both ends of each PW. The preset SID list includes the SID of each PE connected to the preset CE. The first PE device can determine the PW between the source CE and the destination CE based on the target PW identifier, and then determine the identifier of the destination CE. Then, the first PE can obtain the SID of the second PE from the preset SID list based on the identifier of the destination CE. The second PE is the PE connected to the destination CE, and the SID of the second PE is used to encapsulate the PWE3 service message. Afterwards, the first PE can encapsulate the PWE3 service message through the SID of the second PE to obtain an SRv6 service message, and the SRv6 service message includes the PWE3 service message and the SID of the second PE.

[0048] It should be noted that the embodiments of the present disclosure do not limit the CE identifier. For example, the CE identifier may be the CE device number. In another example, the CE identifier may be the CE device name. In another example, the CE identifier may be the CE address information (such as VPN address information). In another example, the CE identifier may be composed of the CE device number, device name, and address information.

[0049] In some embodiments, before the first PE encapsulates the PWE3 service message into an SRv6 service message, the first PE may perform whitelist authentication on the destination CE to determine whether an SRv6 tunnel is established between the PE connected to the destination CE and the first PE, thereby managing the PWE3 service message.

[0050] As one possible implementation, the first PE stores a preset identifier list, which includes identifiers of multiple preset CEs. An SRv6 tunnel is established between the PE connected to the preset CE and the first PE. After the first PE determines the identifier of the destination CE based on the target PW identifier, it can query whether the identifier of the destination CE is in the preset identifier list. If the identifier of the destination CE is in the preset identifier list, the first PE encapsulates the PWE3 service message into an SRv6 service message.

[0051] It can be understood that the PE determines whether to transmit the PWE3 service message through the SRv6 tunnel by matching the destination CE in the PWE3 service message with the whitelist, thereby improving the security of message transmission.

[0052] In other embodiments, before the first PE encapsulates the PWE3 service message into an SRv6 service message, the first PE may determine whether the target SRv6 tunnel can carry the SRv6 service message by judging the status of the target SRv6 tunnel between the first PE and the second PE, thereby managing the PWE3 service message.

[0053] As a possible implementation, before the first PE encapsulates the PWE3 service packet into an SRv6 service packet, the first PE may determine whether the IGP indicates that the target SRv6 tunnel is enabled. If the IGP indicates that the target SRv6 tunnel is enabled, the first PE may encapsulate the PWE3 service packet into an SRv6 service packet.

[0054] In some embodiments, the first PE is further configured with at least one of an LDP tunnel or a public network tunnel corresponding to the target PW identifier. If the IGP does not indicate that the target SRv6 tunnel is enabled, the first PE does not encapsulate the PWE3 service packet as an SRv6 service packet and uses the LDP tunnel or the public network tunnel corresponding to the target PW identifier to carry the PWE3 service packet.

[0055] It should be noted that, in the embodiment of the present disclosure, the target SRv6 tunnel may include at least one of an SRv6 policy tunnel and an SRv6 best effort (BE) tunnel. The encapsulation content of different SRv6 tunnels is also different.

[0056] In some embodiments, the first PE stores mappings between multiple preset PW identifiers and multiple preset SRv6 segment identifiers. When the target SRv6 tunnel includes an SRv6 BE tunnel, the first PE can determine the segment identifier of the target SRv6 BE tunnel corresponding to the target PW identifier based on the target PW identifier and the stored mappings, and encapsulate the PWE3 service packet using the segment identifier of the target SRv6 BE tunnel to obtain an SRv6 service packet. The SRv6 service packet includes the segment identifier of the target SRv6 BE tunnel, and the segment identifier of the target SRv6 BE tunnel includes the SID of the first PE and the SID of the second PE.

[0057] In other embodiments, when the target SRv6 tunnel includes an SRv6 Policy tunnel, the first PE can determine the destination CE identifier based on the target PW identifier, and determine the destination CE's VPN address information based on the destination CE identifier. Simultaneously, the first PE can determine the target SRv6 tunnel's public network forwarding table based on the target PW identifier. The public network forwarding table includes the SIDs of multiple preset PEs between the source CE and the destination CE, where the multiple preset PEs include the first PE and the second PE. The first PE can then encapsulate the PWE3 service message using the destination CE's VPN address information and the public network forwarding table of the target SRv6 Policy tunnel to obtain an SRv6 service message. The SRv6 service message includes the destination CE's VPN address information and the public network forwarding table of the target SRv6 Policy tunnel.

[0058] As a possible implementation method, the first PE can determine all PEs between the source CE and the destination CE based on the target PW identifier, and select multiple preset PEs from all PEs between the source CE and the destination CE through the color diversion mechanism, and determine the SID of each preset PE, and then generate the public network forwarding table of the target SRv6 Policy tunnel based on the SIDs of multiple preset PEs.

[0059] In some embodiments, the first PE is also configured with a stream identifier (stream ID) corresponding to the destination CE. The stream ID is used to indicate that the downlink microcode needs to support encapsulating the private network label first and then the segment routing header (SRH). The first PE can encapsulate the PWE3 service message in the order of encapsulation indicated by the stream ID, using the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel to obtain an SRv6 service message. The public network forwarding table of the target SRv6 Policy tunnel serves as the message header of the SRv6 service message.

[0060] It should be noted that in the disclosed embodiments, the target SRv6 tunnel may include both an SRv6 Policy tunnel and an SRv6 BE tunnel, and the SRv6 Policy tunnel has a higher priority than the SRv6 BE tunnel. If the SRv6 Policy tunnel is functioning properly, the first PE determines the SRv6 Policy tunnel as the target SRv6 tunnel. If the SRv6 Policy tunnel is abnormal, the first PE determines the SRv6 BE tunnel as the target SRv6 tunnel. That is, when the first PE sends SRv6 service packets to the second PE via the SRv6 tunnel, the first PE prioritizes sending SRv6 service packets to the second PE via the SRv6 Policy tunnel. Alternatively, if the SRv6 Policy tunnel is unavailable, the first PE sends SRv6 service packets to the second PE via the SRv6 BE tunnel.

[0061] In summary, the PE determines the transmission strategy for PWE3 service packets by sensing the status of the SRv6 tunnel established with the peer PE (i.e., the online or offline state of the Policy tunnel). If the Policy tunnel is online, the PE determines the VPN address information of the destination CE and sends the PWE3 service packet encapsulated with the destination CE's VPN address information to the peer PE through the Policy tunnel. If the Policy tunnel is offline, the peer PE determines the VPN address information of the destination CE and sends the PWE3 service packet without the destination CE's VPN address information to the peer PE through the BE tunnel. This improves the operability of packet transmission.

[0062] In S203 , the first PE sends an SRv6 service packet to the second PE through the target SRv6 tunnel between the first PE and the second PE.

[0063] In the embodiment of the present disclosure, the target SRv6 tunnel between the first PE and the second PE may be a target SRv6 Policy tunnel or a target SRv6 BE tunnel.

[0064] As a possible implementation manner, the first PE may send an SRv6 service packet to the second PE through the target SRv6 BE tunnel.

[0065] It should be noted that for the process of the first PE sending the SRv6 service message to the second PE through the target SRv6 BE tunnel, reference can be made to the SRv6 segment routing IPv6 best effort (SRv6 BE) working mode in the relevant technology, which will not be described in detail here.

[0066] As another possible implementation, the first PE may send the SRv6 service packet to the second PE through the target SRv6 Policy tunnel.

[0067] It should be noted that for the process of the first PE sending SRv6 service packets to the second PE through the target SRv6 Policy tunnel, reference can be made to the SRv6 segment routing IPv6 traffic engineering policy (SRv6TE Policy) working mode in the relevant technology, which will not be described in detail here.

[0068] The embodiment of the present disclosure further provides a method for transmitting a service message, which is applied to a second PE. The second PE is connected to a destination CE. As shown in FIG. 3 , the method for transmitting the service message may include S301 - S303 .

[0069] In S301 , the second PE receives an SRv6 service packet from the first PE through a target SRv6 tunnel.

[0070] The SRv6 service message is a service message obtained by the first PE encapsulating the PWE3 service message using the target PW identifier. The target PW identifier is used to indicate the PW between the source CE and the destination CE. The PWE3 service message is received by the first PE from the source CE.

[0071] In the embodiment of the present disclosure, the SRv6 service message may include the SID of the second PE. After the second PE receives the SRv6 service message, the second PE may manage the SRv6 service message by determining whether the SID in the SRv6 service message is its own SID.

[0072] In some embodiments, when the second PE determines that the SID in the SRv6 service message is different from its own SID, the second PE may forward the SRv6 service message through the SRv6 tunnel according to the SID in the SRv6 service message.

[0073] In other embodiments, when the second PE determines that the SID in the SRv6 service packet is the same as its own SID, the second PE may execute S302.

[0074] In S302 , the second PE decapsulates the SRv6 service packet to obtain a PWE3 service packet.

[0075] As a possible implementation manner, the second PE may obtain the PWE3 service message by deleting the SID of the second PE in the SRv6 message.

[0076] It should be noted that the target SRv6 tunnel can be an SRv6 Policy tunnel or an SRv6 BE tunnel. After the second PE receives the PWE3 service message, it can manage the PWE3 service message based on the SRv6 tunnel used when interacting with the first PE.

[0077] In some embodiments, when a second PE receives an SRv6 service packet through an SRv6 Policy tunnel, the SRv6 service packet contains the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel. The second PE can sequentially decapsulate the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel in the SRv6 service packet to obtain the PWE3 service packet and the VPN address information of the destination CE. The second PE can then execute S303 based on the VPN address information of the destination CE obtained from the decapsulation of the SRv6 service packet.

[0078] In other embodiments, when a second PE receives an SRv6 service packet via an SRv6 BE tunnel, the SRv6 service packet contains the segment identifier of the target SRv6 BE tunnel. The second PE can decapsulate the segment identifier of the target SRv6 BE tunnel in the SRv6 service packet to obtain a PWE3 service packet. The second PE can then determine the destination CE identifier based on the target PW identifier in the PWE3 service packet, determine the destination CE's VPN address information based on the destination CE identifier, and then execute S303 based on the destination CE's VPN address information determined based on the destination CE identifier.

[0079] In S303, the second PE sends a PWE3 service message to the destination CE.

[0080] The following describes the service message transmission method provided by the embodiment of the present disclosure in conjunction with the embodiment. As shown in FIG4 , the service message transmission method in the embodiment of the present disclosure may include S401 - S408 .

[0081] In S401, the source CE sends a PWE3 service message to the first PE.

[0082] In S402, the first PE receives a PWE3 service message.

[0083] In S403 , the first PE encapsulates the PWE3 service message according to the target PW identifier to obtain an SRv6 service message.

[0084] In S404, the first PE sends an SRv6 service packet to the second PE through the target SRv6 tunnel.

[0085] In S405 , the second PE receives the SRv6 service packet through the target SRv6 tunnel.

[0086] In S406 , the second PE decapsulates the SRv6 service message to obtain a PWE3 service message.

[0087] In S407 , the second PE sends a PWE3 service message to the destination CE.

[0088] In S408 , the destination CE obtains the PWE3 service message from the source CE.

[0089] It can be understood that the present disclosure enables PEs to support the SRv6 protocol within the existing PWE3 network structure and encapsulate PWE3 service packets from CEs, allowing the processed PWE3 service packets to reach the peer PE through the SRv6 tunnel. The peer PE then decapsulates the processed PWE3 service packets, restoring them to the original PWE3 service packets and sending them to the destination CE. This enables SRv6 technology to carry PWE3 service packets, improving the compatibility of new and old equipment in the network, facilitating the transition from traditional VPNs to SDNs, and making the replacement of old and new networks more convenient, reducing the difficulty of network upgrades, and minimizing the risks of technology updates.

[0090] The following describes the service message transmission method provided by the embodiment of the present disclosure with reference to an example. The VPN next hop (VPNNH) egress of the PWE3 service data module in the PE supports SRv6 tunnels, which are divided into SRv6 BE tunnels and SRv6 Policy tunnels.

[0091] If the VPNNH egress of the PWE3 service data module in the PE supports SRv6 BE tunnels, the PE can determine whether to transmit the message from the CE by querying the prefix table (i.e., a preset identifier list). If transmission is confirmed, the PE determines the SID of the peer PE by querying the private network uplink encapsulation table (ifte, i.e., a preset SID list). The PE then performs tunnel encapsulation (tunnel encapsulation, or tunnellencap) on the message from the CE and the peer PE's SID, and sends the encapsulated message to the peer PE via the SRv6 BE tunnel between the PE and the peer PE.

[0092] Similarly, if the VPNNH egress of the PWE3 service data module in the PE supports SRv6 Policy tunnels, the PE can determine whether to transmit the message from the CE by querying the prefix table (i.e., the preset identifier list). If transmission is confirmed, the PE can determine the SID of the peer PE by querying the private network uplink encapsulation table. Simultaneously, the PE can determine the VPN address of the peer CE by querying the VPNNH list. The PE can then perform forwarding encapsulation on the message from the CE and the peer PE's SID, and use the color diversion mechanism to allocate other PEs for message forwarding to the SRv6 Policy tunnel between the PE and the peer PE. The PE can then send the encapsulated message to the peer PE via the allocated SRv6 Policy tunnel.

[0093] It should be noted that due to the SRv6 public process, two levels of SID are required (i.e., the SID of the sending device and the SID of the receiving device), so the PE is configured with ifte including multiple PW-SRv6 identifiers. The PE can determine the segment identifier of the SRv6 tunnel between the PE and the opposite PE by querying ifte based on the PW between the CE and the opposite CE, and determine the SID of the opposite PE based on the segment identifier of the SRv6 tunnel.

[0094] In the embodiment of the present disclosure, the PE may perform differentiated management on the uplink message according to the information carried in the uplink message.

[0095] It should be noted that in the disclosed embodiments, if the uplink message is transmitted through an SRv6 tunnel, the information carried by the message is the common header + IPv6 + SRH + PBU. If the uplink message is transmitted through a tunnel or LDP tunnel, the information carried by the message is the common header + IPv6 + PBU.

[0096] After receiving a message transmitted via the SRv6 tunnel, the PE can match the SID in the message with the PW-SRv6 identifier in the private network downlink encapsulation table (iete) to determine whether the PE's SID is the last hop SID of the message.

[0097] When the PE determines that the SID of the PE is not the last hop SID of the message, the PE may send the message to the next hop PE through the SRv6 tunnel according to IETE.

[0098] When the PE determines that the PE's SID is the last hop SID of the message, the PE can decapsulate the message and perform L2VPN common processes (such as horizontal split, source-in and source-out) on the decapsulated message.

[0099] For example, PE determines the pw label, cword, flag, and raw identifiers in the iete table, calls the public header removal function, performs label cword and other encapsulation, pays attention to the position of pktbase, modifies nexthead (the label's nexthead is 137), and jumps back to the public process.

[0100] It should be noted that the PE can determine the message delivery strategy to the CE based on the different SRv6 tunnels used to transmit the messages.

[0101] When the SRv6 tunnel used to transmit the message is an SRv6 BE tunnel, after receiving the decapsulated message, the PE can query the VPNNH list to determine the VPN address of the destination CE corresponding to the message. It can also query the nhfte list to determine the interface connected to the CE on the PE. The PE can then send the decapsulated message to the CE based on the CE's VPN address and the interface connected to the CE.

[0102] When the SRv6 tunnel used to transmit the message is an SRv6 Policy tunnel, after receiving the decapsulated message, the PE can query the v6lpm list to determine the nhfte list to be queried. Furthermore, the nhfte list can be used to determine the interface connected to the CE on the PE. The PE can then send the decapsulated message to the CE based on the VPN address in the message and the interface connected to the CE.

[0103] It is understandable that, in order to realize the above functions, the transmission device of the service message includes at least one of the hardware structures or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the algorithm steps of each example described in the embodiments of the present disclosure, the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0104] The embodiment of the present disclosure can divide the transmission device of the service message into functional modules according to the above-mentioned method embodiment. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above-mentioned integrated module can be implemented in the form of hardware or software. It should be noted that the division of modules in the embodiment of the present disclosure is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0105] Figure 5 is a schematic diagram of the structure of a service message transmission device provided in an embodiment of the present disclosure. The service message transmission device 500 can execute the service message transmission method shown in Figure 2 of the above method embodiment. As shown in Figure 5, the service message transmission device 500 includes: an acquisition module 501, a processing module 502, and a sending module 503.

[0106] The acquisition module 501 is configured to receive an edge-to-edge pseudowire emulation (PWE3) service message from a source customer edge device (CE). The PWE3 service message includes a target pseudowire (PW) identifier, which indicates the PW between the source CE and the destination CE. The processing module 502 is configured to encapsulate the PWE3 service message based on the target PW identifier to obtain a segment-routed SRv6 service message based on the Internet Protocol version 6 forwarding plane. The sending module 503 is configured to send the SRv6 service message to the second PE via a target SRv6 tunnel between the first PE and the second PE. The second PE is the PE connected to the destination CE.

[0107] In some embodiments, processing module 502 is further configured to determine the identifier of the destination CE based on the target PW identifier. Processing module 502 is further configured to query whether the identifier of the destination CE is in a preset identifier list, where the preset identifier list includes identifiers of multiple preset CEs, and an SRv6 tunnel is established between the PE connected to the preset CE and the first PE. Processing module 502 is further configured to, if the identifier of the destination CE is in the preset identifier list, encapsulate the PWE3 service message based on the target PW identifier to obtain an SRv6 service message.

[0108] In some embodiments, the processing module 502 is further configured to obtain the SID of the second PE from a preset segment identifier SID list based on the identifier of the destination CE, wherein the preset SID list includes the SID of each PE connected to the preset CE. The SID of the second PE is used to encapsulate the PWE3 service message.

[0109] In some embodiments, the first PE is configured with a Layer 2 virtual private network (L2VPN) tunnel and an SRv6 tunnel based on the Label Distribution Protocol (LDP), and the Interior Gateway Protocol (IGP) of the first PE enables the LDP-based L2VPN tunnel and the SRv6 tunnel.

[0110] In some embodiments, the target SRv6 tunnel includes at least one of an SRv6 Policy tunnel and an SRv6 Best Effort BE tunnel.

[0111] In some embodiments, the first PE stores a mapping relationship between multiple preset PW identifiers and multiple preset SRv6 segment identifiers. When the target SRv6 tunnel includes an SRv6 BE tunnel, processing module 502 is configured to determine the segment identifier of the target SRv6 BE tunnel corresponding to the target PW identifier based on the target PW identifier and the mapping relationship. Processing module 502 is further configured to encapsulate the PWE3 service packet using the segment identifier of the target SRv6 BE tunnel to obtain an SRv6 service packet, where the SRv6 service packet includes the segment identifier of the target SRv6 BE tunnel.

[0112] In some embodiments, when the target SRv6 tunnel includes an SRv6 Policy tunnel, processing module 502 is configured to determine the destination CE identifier based on the target PW identifier. Processing module 502 is further configured to determine the destination CE's virtual private network (VPN) address information based on the destination CE identifier. Processing module 502 is further configured to determine the public network forwarding table for the target SRv6 Policy tunnel based on the target PW identifier. The public network forwarding table includes the SIDs of multiple preset PEs between the source CE and the destination CE, where the multiple preset PEs include a first PE and a second PE. Processing module 502 is further configured to encapsulate the PWE3 service message using the destination CE's VPN address information and the public network forwarding table for the target SRv6 Policy tunnel to obtain an SRv6 service message. The SRv6 service message includes the destination CE's VPN address information and the public network forwarding table for the target SRv6 Policy tunnel.

[0113] In some embodiments, the processing module 502 is configured to determine the SIDs of multiple preset PEs based on the target PW identifier and to generate a public network forwarding table for the target SRv6 Policy tunnel based on the SIDs of the multiple preset PEs.

[0114] In some embodiments, the target SRv6 tunnel includes an SRv6 Policy tunnel and an SRv6 BE tunnel. Processing module 502 is further configured to, if the SRv6 Policy tunnel is normal, determine the SRv6 Policy tunnel as the target SRv6 tunnel. Processing module 502 is further configured to, if the SRv6 Policy tunnel is abnormal, determine the SRv6 BE tunnel as the target SRv6 tunnel.

[0115] In some embodiments, the processing module 502 is configured to encapsulate the PWE3 service message in the order of encapsulation, using the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel, to obtain an SRv6 service message.

[0116] Figure 6 is a schematic diagram of the structure of another device for transmitting service messages provided in an embodiment of the present disclosure. The device for transmitting service messages 600 can execute the method for transmitting service messages shown in Figure 3 of the above method embodiment. As shown in Figure 6, the device for transmitting service messages 600 includes: an acquisition module 601, a processing module 602, and a sending module 603.

[0117] The acquisition module 601 is configured to receive an SRv6 service message from a first PE via a target SRv6 tunnel. The SRv6 service message is obtained by the first PE encapsulating a PWE3 service message using a target PW identifier. The target PW identifier indicates the PW between the source CE and the destination CE. The PWE3 service message is received by the first PE from the source CE. The processing module 602 is configured to decapsulate the SRv6 service message to obtain a PWE3 service message. The sending module 603 is configured to send the PWE3 service message to the destination CE.

[0118] In some embodiments, when the target SRv6 tunnel is an SRv6 Policy tunnel, the SRv6 service packet contains the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel. Processing module 602 is configured to sequentially decapsulate the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel in the SRv6 service packet to obtain the PWE3 service packet and the VPN address information of the destination CE.

[0119] In some embodiments, when the target SRv6 tunnel is an SRv6 BE tunnel, the segment identifier of the target SRv6 BE tunnel is encapsulated in the SRv6 service message. The processing module 602 is configured to decapsulate the segment identifier of the target SRv6 BE tunnel in the SRv6 service message to obtain a PWE3 service message.

[0120] In some embodiments, the PWE3 service message includes a target PW identifier. The processing module 602 is further configured to determine the identifier of the destination CE based on the target PW identifier. The processing module 602 is further configured to determine the VPN address information of the destination CE based on the identifier of the destination CE.

[0121] In the case of implementing the functions of the above-mentioned integrated modules in hardware, the embodiments of the present disclosure provide another possible network device structure for the service message transmission device involved in the above-mentioned embodiments. As shown in Figure 7, the service message transmission device 700 includes: a processor 702 and a bus 704. In some embodiments, the service message transmission device 700 may also include a memory 701; in some embodiments, the service message transmission device 700 may also include a communication interface 703.

[0122] The processor 702 may be a processor that implements or executes the various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of the present disclosure. The processor 702 may be a central processing unit, a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit, a field programmable gate array, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor 702 may be a processor that implements or executes the various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of the present disclosure. The processor 702 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0123] The communication interface 703 is used to connect to other devices via a communication network, which may be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0124] The memory 701 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0125] As a possible implementation, the memory 701 can exist independently of the processor 702. The memory 701 can be connected to the processor 702 via a bus 704 to store instructions or program codes. When the processor 702 calls and executes the instructions or program codes stored in the memory 701, the service message transmission method provided in the embodiment of the present disclosure can be implemented.

[0126] In another possible implementation, the memory 701 may also be integrated with the processor 702 .

[0127] Bus 704 may be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 704 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG7 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0128] Some embodiments of the present disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium), which stores computer program instructions. When the computer program instructions are executed on a computer, the computer executes the method for transmitting a service message as described in any of the above embodiments.

[0129] Exemplarily, the computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in the present disclosure may represent readable storage media of at least one of one or more devices and other machines for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0130] An embodiment of the present disclosure provides a computer program product including instructions. When the computer program product is run on a computer, the computer is enabled to execute the method for transmitting a service message described in any one of the above embodiments.

[0131] The above is only a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or replacements within the technical scope disclosed in the present disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A method for transmitting a service message, applied to a first operator edge device (PE), comprising: receiving an edge-to-edge pseudo wire emulation (PWE3) service message from a source customer edge device (CE), wherein the PWE3 service message includes a target pseudo wire (PW) identifier, where the target PW identifier is used to indicate a PW between the source CE and a destination CE; Encapsulating the PWE3 service message according to the target PW identifier to obtain a segment routing SRv6 service message based on an Internet Protocol version 6 forwarding plane; The SRv6 service packet is sent to the second PE through a target SRv6 tunnel between the first PE and the second PE, where the second PE is a PE connected to the destination CE.

2. The method according to claim 1, wherein Before encapsulating the PWE3 service message according to the target PW identifier to obtain a segment routing SRv6 service message based on an Internet Protocol version 6 forwarding plane, the method further includes: Determining the identifier of the destination CE according to the target PW identifier; Query whether the identifier of the destination CE is in a preset identifier list, where the preset identifier list includes identifiers of multiple preset CEs, and an SRv6 tunnel is established between the PE connected to the preset CE and the first PE; In a case where the identifier of the destination CE exists in the preset identifier list, encapsulating the PWE3 service message according to the target PW identifier is performed to obtain the SRv6 service message.

3. The method according to claim 2, wherein: After determining the identifier of the destination CE according to the target PW identifier, the method further includes: According to the identifier of the destination CE, the SID of the second PE is obtained from a preset segment identifier SID list, where the preset SID list includes the SID of each PE connected to the preset CE; the SID of the second PE is used to encapsulate the PWE3 service message.

4. The method according to claim 1, wherein The first PE is configured with a Layer 2 virtual private network L2VPN tunnel and an SRv6 tunnel based on the Label Distribution Protocol LDP, and the Interior Gateway Protocol IGP of the first PE enables the L2VPN tunnel and the SRv6 tunnel based on LDP.

5. The method according to claim 1, wherein The target SRv6 tunnel includes at least one of an SRv6 policy tunnel and an SRv6 best effort BE tunnel.

6. The method according to claim 5, wherein: The first PE stores a mapping relationship between a plurality of preset PW identifiers and a plurality of preset SRv6 segment identifiers; In a case where the target SRv6 tunnel includes an SRv6 BE tunnel, encapsulating the PWE3 service message according to the target PW identifier to obtain a segment routing SRv6 service message based on an Internet Protocol version 6 forwarding plane includes: Determine, according to the target PW identifier and the mapping relationship, a segment identifier of a target SRv6 BE tunnel corresponding to the target PW identifier; The PWE3 service message is encapsulated using the segment identifier of the target SRv6 BE tunnel to obtain the SRv6 service message, where the SRv6 service message includes the segment identifier of the target SRv6 BE tunnel.

7. The method according to claim 5, wherein: In a case where the target SRv6 tunnel includes an SRv6 Policy tunnel, encapsulating the PWE3 service message according to the target PW identifier to obtain a segment routing SRv6 service message based on an Internet Protocol version 6 forwarding plane includes: Determining the identifier of the destination CE according to the target PW identifier; Determining the VPN address information of the destination CE according to the identifier of the destination CE; Determine a public network forwarding table for the target SRv6 Policy tunnel based on the target PW identifier; wherein the public network forwarding table includes SIDs of multiple preset PEs between the source CE and the destination CE, and the multiple preset PEs include the first PE and the second PE; The PWE3 service message is encapsulated using the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel to obtain the SRv6 service message, where the SRv6 service message includes the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel.

8. The method according to claim 7, wherein: The determining, according to the target PW identifier, a public network forwarding table of the target SRv6 Policy tunnel includes: Determining the SIDs of the plurality of preset PEs according to the target PW identifier; Generate a public network forwarding table for the target SRv6 Policy tunnel according to the SIDs of the multiple preset PEs.

9. The method according to claim 5, wherein: The target SRv6 tunnel includes an SRv6 Policy tunnel and an SRv6 BE tunnel; and the method includes: If the SRv6 Policy tunnel is normal, determining the SRv6 Policy tunnel as the target SRv6 tunnel; When the SRv6 Policy tunnel is abnormal, the SRv6 BE tunnel is determined as the target SRv6 tunnel.

10. The method according to claim 7, wherein: The encapsulating the PWE3 service message by using the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel to obtain the SRv6 service message includes: The PWE3 service message is encapsulated in sequence using the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel to obtain the SRv6 service message.

11. A method for transmitting a service message, applied to a second PE, the second PE being connected to a destination CE, comprising: Receiving, through the target SRv6 tunnel, an SRv6 service packet from the first PE, where the SRv6 service packet is a service packet obtained by the first PE encapsulating the PWE3 service packet using the target PW identifier, where the target PW identifier is used to indicate the PW between the source CE and the destination CE, and the PWE3 service packet is received by the first PE from the source CE; Decapsulating the SRv6 service message to obtain the PWE3 service message; Send the PWE3 service message to the destination CE.

12. The method according to claim 11, wherein When the target SRv6 tunnel is an SRv6 Policy tunnel, the SRv6 service message encapsulates the VPN address information of the destination CE and the public network forwarding table of the target SRv6 Policy tunnel; Decapsulating the SRv6 service message to obtain the PWE3 service message includes: The VPN address information of the destination CE in the SRv6 service message and the public network forwarding table of the target SRv6 Policy tunnel are sequentially decapsulated to obtain the PWE3 service message and the VPN address information of the destination CE.

13. The method according to claim 11, wherein When the target SRv6 tunnel is an SRv6 BE tunnel, the segment identifier of the target SRv6 BE tunnel is encapsulated in the SRv6 service message; Decapsulating the SRv6 service message to obtain the PWE3 service message includes: Decapsulate the segment identifier of the target SRv6 BE tunnel in the SRv6 service message to obtain the PWE3 service message.

14. The method according to claim 13, wherein: The PWE3 service message includes the target PW identifier; After decapsulating the segment identifier of the target SRv6 BE tunnel in the SRv6 service message to obtain the PWE3 service message, the method further includes: Determining the identifier of the destination CE according to the target PW identifier; Determine the VPN address information of the destination CE according to the identifier of the destination CE.

15. A network device comprising: memory and processor; The memory is coupled to the processor; The memory is used to store instructions executable by the processor; When the processor executes the instructions, the method according to any one of claims 1 to 14 is performed.

16. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, which, when executed on a computer, enable the computer to perform the method according to any one of claims 1 to 14.

Images