WO2022021818A1 - 数据报文的处理方法及装置、存储介质、电子装置 - Google Patents

数据报文的处理方法及装置、存储介质、电子装置 Download PDF

Info

Publication number
WO2022021818A1
WO2022021818A1 PCT/CN2021/073373 CN2021073373W WO2022021818A1 WO 2022021818 A1 WO2022021818 A1 WO 2022021818A1 CN 2021073373 W CN2021073373 W CN 2021073373W WO 2022021818 A1 WO2022021818 A1 WO 2022021818A1
Authority
WO
WIPO (PCT)
Prior art keywords
bier
message
field
packet
header
Prior art date
Application number
PCT/CN2021/073373
Other languages
English (en)
French (fr)
Inventor
朱小龙
张征
冯军
陈勇
马汝胜
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP21849736.0A priority Critical patent/EP4191966A4/en
Priority to US18/018,905 priority patent/US20230291682A1/en
Publication of WO2022021818A1 publication Critical patent/WO2022021818A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/58—Association of routers
    • H04L45/586—Association of routers of virtual routers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering

Definitions

  • the embodiments of the present disclosure relate to the field of communications, and in particular, to a data packet processing method and device, a storage medium, and an electronic device.
  • IPv6 Internet Protocol Version 6
  • IETF Internet Engineering Task Force
  • Bit Indexed Explicit Replication (BIER for short) (RFC8279) is a new type of multicast data forwarding technology.
  • the nodes at the edge of the network are represented by only one bit, and the multicast traffic is transmitted in the intermediate network. , additionally encapsulates a specific BIER header, which marks all destination nodes of the multicast stream in the form of bit strings, and the intermediate network forwarding nodes route according to the bits to ensure that the traffic can be sent to all destination nodes .
  • the intermediate node forwarding device passes a routing protocol in advance, such as the Open Shortest Path First (OSPF Open Shortest Path First, OSPF) protocol in the three-layer network, the Intermediate System-to-Intermediate System (Intermediate System-to-Intermediate System, referred to as ISIS) ) protocol to form a Bit Index Forwarding Table (BIFT) table for guiding BIER forwarding.
  • OSPF Open Shortest Path First
  • ISIS Intermediate System-to-Intermediate System
  • BIFT Bit Index Forwarding Table
  • BIER is a data plane forwarding technology that eliminates the delay in establishing a multicast tree because it does not have the problem of establishing a multicast tree, and when a link or node problem occurs in the network, the convergence speed is the same as that of OSPF or ISIS, which is faster than the original multicast. Tree reconstruction reduces huge latency.
  • BIER technology When the BIER technology is transmitted, only a certain multicast traffic needs to be encapsulated in a BIER packet and transmitted as a payload.
  • BFIR Bit-Forwarding Ingress Router
  • BFERs Bit-Forwarding Egress Routers
  • BIER technology can be directly encapsulated in Ethernet packets for transmission (protocol number 0xAB37). When some nodes cannot support direct identification of Ethernet BIER packets, if Ethernet packets are still used for transmission, the node of the packet cannot be correctly identified. Will become a black hole and discard packets.
  • the embodiments of the present disclosure provide a data packet processing method and device, a storage medium, and an electronic device, so as to at least solve the technical solution of how to optimize the BIER packet in the IPv6 packet in the related art.
  • a method for processing a data packet including: an in-bit forwarding ingress router BFIR performs a bit-indexed explicit copy BIER packet encapsulation on the data packet, and encapsulates an outer IPv6 packet.
  • an in-bit forwarding ingress router BFIR performs a bit-indexed explicit copy BIER packet encapsulation on the data packet, and encapsulates an outer IPv6 packet.
  • the Entropy field in the BIER message header is copied to the position of the Flow Label field of the outer IPv6 message, and the label value allocated for the virtual private network VPN data is placed in the BIER message header.
  • the position of the original Entropy field of The packet types include at least one of the following: IPv4 packets, IPv6 packets, Ethernet packets, Multi-Protocol Label Switching (MPLS for short) packets, Operation Administration and Maintenance (Operation Administration and Maintenance) , referred to as OAM) message.
  • IPv4 packets IPv6 packets
  • Ethernet packets Ethernet packets
  • MPLS Multi-Protocol Label Switching
  • OAM Operation Administration and Maintenance
  • a data packet processing apparatus including: a processing module configured to perform bit-index explicit copy BIER packet encapsulation on the data packet by the in-position forwarding ingress router BFIR, and In the case of outer IPv6 packet encapsulation, copy the Entropy field in the BIER packet header to the position of the Flow Label field of the outer IPv6 packet, and place the label value allocated for the VPN data in the virtual private network.
  • the position of the original Entropy field in the BIER message header; the setting module is set to set the data message after the BIER message header, and the Proto field in the BIER message header is set to represent the data message of the data message
  • a computer-readable storage medium where a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any one of the above methods when running steps in the examples.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to run the computer program to execute any of the above Steps in Method Examples.
  • the BIER message and the IPv6 message can be processed as follows: the Entropy field in the BIER message header is copied to the position of the Flow Label field of the outer IPv6 message, and the data is stored in the virtual private network VPN data.
  • the assigned label value is placed in the position of the original Entropy field in the BIER header; the data message is set after the BIER header, and the Proto field in the BIER header is set to represent the value of the data message.
  • the value corresponding to the data packet type, thereby realizing the encapsulation of the BIER packet in the IPv6 packet, and the DSCP field can also be escaped in the same way.
  • FIG. 1 is a block diagram of a hardware structure of a computer terminal according to a method for processing a data message according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for processing a data packet according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram (1) of encapsulating a BIER message in an IPv6 message according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a TLV according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a BIER message transmission mechanism applied in a BIER domain according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram (2) of encapsulating a BIER message in an IPv6 message according to an embodiment of the present disclosure
  • FIG. 7 is a schematic structural diagram of a data packet processing apparatus according to an embodiment of the present disclosure.
  • FIG. 1 is a hardware structural block diagram of a computer terminal according to a method for processing a data packet according to an embodiment of the present disclosure.
  • the computer terminal may include one or more (only one is shown in FIG.
  • processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.
  • the above-mentioned computer terminal may further include a transmission device 106 and an input/output device 108 configured as a communication function.
  • the structure shown in FIG. 1 is only a schematic diagram, which does not limit the structure of the above-mentioned computer terminal.
  • the computer terminal may also include more or fewer components than shown in FIG. 1 , or have a different configuration than that shown in FIG. 1 .
  • the memory 104 may be configured to store computer programs, for example, software programs and modules of application software, such as computer programs corresponding to the data packet processing methods in the embodiments of the present disclosure.
  • the processor 102 runs the computer programs stored in the memory 104 , so as to perform various functional applications and data processing, that is, to implement the above method.
  • Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • memory 104 may further include memory located remotely from processor 102, which may be connected to a computer terminal through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • Transmission means 106 are arranged to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by the communication provider of the computer terminal.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is configured to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • multicast technology is being used more and more on the Internet, such as multi-party conferences, distance education, telemedicine, and webcasting.
  • IPv6 IPv6
  • encapsulating BIER in the IPv6 header has become a must-have function.
  • the following embodiments of the present disclosure propose a new packet encapsulation method, which combines BIER encapsulation with IPv6 encapsulation, and performs escaping processing on some of the repeated fields. Combined with the capability notification of the control plane, the function is not affected at all. Next, optimize the packet encapsulation and processing flow.
  • FIG. 2 is a flowchart of a method for processing a data packet according to an embodiment of the present disclosure. As shown in FIG. 2 , the process includes: Follow the steps below:
  • Step S102 in the case that the bit forwarding ingress router BFIR performs bit index explicit copy BIER packet encapsulation on the data packet, and encapsulates the outer layer IPv6 packet, copy the Entropy field in the BIER packet header to the outer layer IPv6
  • the position of the Flow Label field of the message, and the label value allocated for the virtual private network VPN data is placed in the position of the original Entropy field in the BIER message header;
  • Step S104 setting a data message after the BIER message header, and setting the Proto field in the BIER message header to a value corresponding to the data message type representing the data message, wherein the data message type is at least It includes one of the following: IPv4 packets, IPv6 packets, Ethernet packets, MPLS packets, and OAM packets.
  • the BIER message and the IPv6 message can be processed as follows: the Entropy field in the BIER message header is copied to the position of the Flow Label field of the outer IPv6 message, and the data is stored in the virtual private network VPN data.
  • the assigned label value is placed in the position of the original Entropy field in the BIER header; the data message is set after the BIER header, and the Proto field in the BIER header is set to represent the value of the data message.
  • the value corresponding to the data packet type and then realize the encapsulation of the BIER packet in the IPv6 packet.
  • the execution subject of the above steps may be a base station, a terminal, etc., but is not limited thereto.
  • step S102 and step S104 can be interchanged, that is, step S104 may be executed first, and then step S102 may be executed.
  • the Proto field is no longer set to the MPLS type, but is directly set to the real type of the data packet, That is, IPv4, IPv6, Ethernet, MPLS or OAM, etc.
  • the above method further includes: copying the Entropy field in the BIER packet header to the position of the Flow Label field in the outer IPv6 packet, the The method also includes: when the equipment that needs to process the data packet performs forwarding processing on the data packet, only performing load balancing processing according to the Flow Label field in the IPv6 packet header, it can be understood that , when forwarding processing, the devices along the road only perform load balancing processing according to the Flow Label field in the IPv6 header, and no longer perform processing according to the Entropy field in the BIER header.
  • the method further includes: when the forwarding egress router BFER receives the data packet, stripping the outer IPv6 packet header from the data packet, according to the BIER packet header According to the label value in the original Entropy field, the VPN corresponding to the label value is found; according to the data type indicated by the Proto field, the data packet is forwarded, that is, in the embodiment of the present disclosure, the BFER receives In the packet, after stripping the outer IPv6 header, the original Entropy field in the BIER packet header is now the Label field to find the corresponding VPN, and then directly according to the instructions of Proto, read the subsequent data packets for forwarding processing . Assuming that Proto is IPv4, BFER performs IPv4 routing table lookup processing in the corresponding VPN, and forwards the data packet to the correct receiver.
  • the Entropy value when the Entropy value is 0, it can be used to indicate global multicast, that is, when the VPN is 0 or there is no VPN. In this case, you can search the corresponding global routing table according to Proto.
  • the extension methods include:
  • the method further includes: for non-BFIR and non-BFER pure intermediate nodes, if the intermediate node only performs load balancing processing according to the Flow Label in the IPv6 packet header, executing the following steps: Process flow of capability negotiation and notification between BFIR and BFER.
  • the method further includes: the definition of the capability negotiation information in the processing flow of the capability negotiation and notification is embodied in the form of TLV (Type, Length, Value).
  • the definition of the capability negotiation information in the capability negotiation and notification processing flow is embodied in the form of TLV, including at least one of the following: the Type in the TLV is 1 and the Length is 1 bytes, and the Value value is defined as 1 to indicate that the Entropy field in the BIER packet header has been copied to the position after the Flow Label field of the outer IPv6 packet, and the label that has been assigned to the virtual private network VPN data
  • the value is placed in the position of the original Entropy field in the BIER header;
  • the Type in the TLV is 1, the Length is 0, and there is no Value value to indicate that the Entropy field in the BIER header has been copied
  • the position after the Flow Label field of the outer IPv6 packet, and the label value that has been allocated for the virtual private network VPN data, are placed in the position of the original Entropy field in the BIER packet header.
  • the method further includes: indicating that the DSCP field in the BIER packet header has been copied by setting the TLV Type as 2, the Length as 1 byte, and the Value value as 1 To the location of the Traffic Class field of the outer IPv6 packet, or other locations, the original DSCP field in the BIER packet header can be used for other purposes; the Type in the TLV in the DSCP field is 2, the Length is 0, and there is no Value value To indicate that the DSCP field in the BIER packet header has been copied to the location of the Traffic Class field of the outer IPv6 packet, or other locations, the original DSCP field in the BIER packet header can be used for other purposes.
  • the definition of capability negotiation information can be embodied in the form of TLV, as shown in Figure 4.
  • TLV TLV
  • the first method defines Type as 1, which means "escape”, Length as 1 byte, and Value as 1, which means that the Entropy field is escaped as the service VPN label of the data packet.
  • the second method directly defines the Type as 1 and the Length as 0, and no need to follow the Value, but directly uses the Type value of 1 to indicate that the Entropy field is escaped as the business VPN Label of the data packet. If the DSCP field is to be escaped later, for the first method, Value can be defined as 2 to indicate the DSCP field escape, or the second method can be used to directly define the type 2 to indicate the DSCP field escape.
  • the DSCP field in the BIER header similarly, after the value is copied in the Traffic Class of the outer IPv6 header, the DSCP field can be used to represent other content.
  • TLV TLV extension
  • BGP BGP, MVPN, MLD and other protocols
  • the BFR device When the BFR device originally performs load balancing processing according to the Entropy field in the BIER packet header, it can also notify the node's escape capability when flooding the BIER's BFR-ID value and other information in protocols such as OSPF or ISIS. To avoid load balancing processing errors.
  • the method further includes: carrying the form of the TLV in at least one of the following protocols between BFIR and BFER: border gateway protocol BGP, multicast virtual private network MVPN protocol, multicast Listen to the discovery protocol.
  • Border gateway protocol BGP border gateway protocol BGP
  • multicast virtual private network MVPN protocol multicast Listen to the discovery protocol.
  • the method further includes: copying the Entropy field in the BIER packet header to the position of the Flow Label field of the outer IPv6 packet, and copying the Entropy field allocated for the virtual private network VPN data
  • the label value is placed after the position of the original Entropy field in the BIER message header, and the method further includes: the reservation of the BIER message header is set to 1 for RSV.
  • BFIR/BFER supports both escaped and unescaped encapsulation processing methods
  • another bit in the BIER header can be used, such as the reserved RSV bit.
  • a certain bit, such as the low bit is set to 1 to indicate that the Entropy field has been escaped.
  • the encapsulation process of BFIR will add the following steps: after escaping the Entropy field, set RSV to 1.
  • the judgment of RSV will be added. If the corresponding bit is found to be set to 1, it means that the Entropy field in the BIER header has been escaped, so that BFER can The value of is used as the VPN label to locate the VPN entry.
  • the method further includes: in the case that the escape capability of any node in the network changes, notifying other nodes in the network except the any node by means of protocol notification node, wherein the escape capability is used to indicate whether the any node has the Entropy field in the BIER packet header, copied to the position of the Flow Label field of the outer IPv6 packet, and will be a virtual private network VPN The label value assigned by the data, the ability to place the position of the original Entropy field in the BIER header.
  • the node's support for the escape capability changes, it can notify other nodes in the form of protocol announcement.
  • the way can be re-announced through the capability, but with a special value, such as the newly added type in the above capability TLV or the Value is set to Special values such as full F; or re-announcement through the basic information of the protocol, such as the BGP protocol re-announces the supported address family, but no longer carries the capability information; so that other nodes can learn this information.
  • the BFIR node will be encapsulated according to the existing rules during encapsulation, and the BFR node can also be dynamically adjusted according to the situation of the next hop node to avoid packet processing errors.
  • the BIER domain shown in Figure 5 uses the IPv6-encapsulated BIER packet transmission mechanism.
  • the multicast data packets between BFIR and BFER are based on VPN1 or VPN2.
  • BFIR assigns label 10 to VPN1, which is VPN2 assigns label 20.
  • a BGP-based MVPN runs between BFIR and BFER to exchange data packet information, that is, to exchange escape capabilities when determining which recipients of a traffic are located in the BFER. Escape capability announcements can also be made when the initial protocol session is established. If the BFIR supports the escape capability, it advertises the capability; if the BFER supports the escape capability, it also advertises the capability, and if it does not support the capability, it does not.
  • BFER2 does not support escape capability
  • BFER1 and BFER3 support escape capability
  • BFIR finds that the traffic of recipients including BFER2 cannot be escaped.
  • the traffic of VPN2 can be escaped and encapsulated.
  • Step 10 BFIR receives the traffic from VPN2, BFER corresponds to BFER1 and BFER3, and encapsulates the value that originally needs to be encapsulated in the Entropy field in the BIER header for load balancing into the Flow Label field of the outer IPv6 header;
  • Step 12 BFIR encapsulates the label value 20 corresponding to VPN2 into the Entropy field of the BIER header;
  • Step 14 since BFER1 and BFER3 support both escape and non-escaping methods, in order to distinguish, BFIR sets the low bit position of RSV to 1, indicating that the Entropy field has been escaped.
  • Step 16 the BFIR directly attaches the multicast data packet as the payload of the BIER packet to the header of the BIER packet, and directly assigns the type of the multicast data packet to the Proto field in the BIER packet header. If the data packet is an IPv4 multicast data packet, directly set the value of the Proto field in the BIER packet header to the IPv4 type.
  • step 18 the BIER header and other fields in the IPv6 header are encapsulated according to the original rules.
  • Step 20 Perform load balancing processing according to the Flow Label field in the IPv6 header.
  • Step 22 The rest of the forwarding process is the same as the existing rules.
  • Step 24 BFER identifies the RSV low bit in the BIER message header, and when this value is 1, it is known that the message carries out escape processing;
  • Step 26 BFER reads the value of the Entropy field and locates the corresponding VPN when it is not 0. In this example, it will be recognized that the field is the label value of 20, and the BFER is located to VPN2; if it is 0, the global routing table will be looked up.
  • Step 28 BFER directly searches the routing table in VPN2 for forwarding according to the Proto value in the BIER packet header.
  • the current packet processing node can automatically adjust the packet encapsulation according to the situation of the next hop node, so as to avoid the situation that the node cannot process the packet correctly.
  • BFIR performs escape processing on the packets sent to the BFER supporting the escape capability. As shown in the illustration, BFIR learns that both BFER1 and BFER3 support the escape capability through the protocol notification, and also uses the method in the first embodiment to perform normal escape and encapsulation processing.
  • Step 30 the BFIR receives the capability revocation message of BFER, which may be re-announced through capability, but carries special values, such as adding a new type in the above capability TLV or setting Value to a special value such as full F, etc. ; Or re-announce the basic information of the protocol, but no longer carry the capability information; let other nodes know the information.
  • BFER capability revocation message of BFER
  • Step 32 when the BFIR encapsulates the message from VPN2, it no longer adopts the escape encapsulation mode, but uses the existing encapsulation rules to encapsulate and forward.
  • the escape encapsulation method is still used for BFER1
  • the existing encapsulation rules are used for BFER3 for encapsulation and forwarding.
  • Step 40 After receiving the message, BFRn performs normal load balancing processing according to the Flow Label in the IPv6 header, reads the RSV low-bit field in the BIER message header, and finds that it has been set to 1;
  • Step 42 BFRn re-adjusts and encapsulates the message, sets the Proto field in the BIER message header to MPLS, inserts a label into the BIER message header and subsequent data messages, and the value is the original Entropy field of the BIER message header .
  • the RSV position is reset to 0, and the encapsulated message is similar to Figure 6, that is, the escaped field is restored according to the original rules.
  • Step 44 BFRn forwards the re-encapsulated packet to BFER3.
  • BFER3 When BFER3 receives the packet, it processes it according to the normal processing rules, and there will be no packet processing error.
  • an optional embodiment of the present disclosure proposes a new packet encapsulation method, which combines BIER encapsulation with IPv6 encapsulation, performs escaping processing on part of its fields, and negotiates with the capability of the control plane.
  • optimizing the encapsulation and processing flow of service packets can improve the efficiency of encapsulation and processing, which is conducive to the further optimization of BIER technology.
  • the fields in the outer IPv6 header are used without affecting the function implementation.
  • the fields in the BIER header are escaped and negotiated with capability announcements. To optimize service carrying, optimize packet encapsulation and improve processing speed.
  • a data packet processing apparatus is also provided, and the apparatus is configured to implement the above-mentioned embodiments and preferred implementations, and what has been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that implements a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, implementations in hardware, or a combination of software and hardware, are also possible and contemplated.
  • FIG. 7 is a structural block diagram of an apparatus for processing a data message according to an embodiment of the present disclosure. As shown in FIG. 7 , the apparatus includes:
  • the processing module 70 is configured to perform bit-indexed explicit copying of the BIER packet encapsulation on the data packet by the in-bit forwarding router BFIR, and copy the Entropy field in the BIER packet header to the encapsulation of the outer IPv6 packet.
  • the position of the Flow Label field of the outer layer IPv6 message, and the label value allocated for the virtual private network VPN data is placed in the position of the original Entropy field in the BIER message header;
  • the setting module 72 is configured to set the data message after the BIER message header, and set the Proto field in the BIER message header to a value corresponding to the data message type representing the data message, wherein the data message
  • the packet type includes at least one of the following: IPv4 packet, IPv6 packet, Ethernet packet, MPLS packet, and OAM packet.
  • the BIER message and the IPv6 message can be processed as follows: the Entropy field in the BIER message header is copied to the position of the Flow Label field of the outer IPv6 message, and the data is stored in the virtual private network VPN data.
  • the assigned label value is placed in the position of the original Entropy field in the BIER header; the data message is set after the BIER header, and the Proto field in the BIER header is set to represent the value of the data message.
  • the value corresponding to the type of the data message thereby realizing the encapsulation of the BIER message in the IPv6 message, and using the above technical solution to solve the problem that the related technology has not been able to effectively realize the encapsulation of the BIER message in the IPv6 message. optimization, etc.
  • the Proto field is no longer set to the MPLS type, but is directly set to the real type of the data packet, that is, IPv4, IPv6, Ethernet, MPLS, OAM, etc.
  • the processing module 70 is further configured to, when the device that needs to process the data packet performs forwarding processing on the data packet, only according to the Flow in the IPv6 packet header
  • the Label field performs load balancing processing. It is understandable that when forwarding processing, the devices along the road only perform load balancing processing based on the Flow Label field in the IPv6 header, and no longer perform processing based on the Entropy field in the BIER header.
  • the processing module 70 is further configured to strip the outer IPv6 packet header from the data packet when the forwarding egress router BFER receives the data packet, according to the BIER packet header According to the label value in the original Entropy field of the Proto field, the VPN corresponding to the label value is found; according to the data type indicated by the Proto field, the data packet is forwarded, that is, in the embodiment of the present disclosure, the BFER is receiving When the packet arrives, after stripping the outer IPv6 header, the original Entropy field in the BIER packet header is replaced by the Label field to find the corresponding VPN, and then directly read the subsequent data packets for forwarding according to the instructions of Proto. deal with. Assuming that Proto is IPv4, BFER performs IPv4 routing table lookup processing in the corresponding VPN, and forwards the data packet to the correct receiver.
  • the Entropy value when the Entropy value is 0, it can be used to indicate global multicast, that is, when the VPN is 0 or there is no VPN. In this case, you can search the corresponding global routing table according to Proto.
  • the extension methods include:
  • the processing module 70 is further configured to execute the Process flow of capability negotiation and notification between BFIR and BFER.
  • the method further includes: the definition of the capability negotiation information in the processing flow of the capability negotiation and notification is embodied in the form of TLV (Type, Length, Value).
  • the definition of the capability negotiation information in the capability negotiation and notification processing flow is embodied in the form of TLV, including at least one of the following: the Type in the TLV is 1 and the Length is 1 bytes, and the Value value is defined as 1 to indicate that the Entropy field in the BIER packet header has been copied to the position after the Flow Label field of the outer IPv6 packet, and the label that has been assigned to the virtual private network VPN data
  • the value is placed in the position of the original Entropy field in the BIER header;
  • the Type in the TLV is 1, the Length is 0, and there is no Value value to indicate that the Entropy field in the BIER header has been copied
  • the position after the Flow Label field of the outer IPv6 packet, and the label value that has been allocated for the virtual private network VPN data, are placed in the position of the original Entropy field in the BIER packet header.
  • the Type of the TLV is 2, the Length is 1 byte, and the Value value is defined as 1 to indicate that the DSCP field in the BIER packet header has been copied to the outer IPv6 packet
  • the location of the Traffic Class field, the original DSCP field in the BIER header can be used to represent other meanings; in the TLV, the Type is 2, the Length is 0, and there is no Value value to indicate that the DSCP in the BIER header has been field, copied to the Traffic CLass field of the outer IPv6 packet, and the original DSCP field in the BIER header can be used to express other meanings.
  • the definition of capability negotiation information can be embodied in the form of TLV, as shown in Figure 4.
  • TLV TLV
  • the first method defines Type as 1, which means "escape”, Length as 1 byte, and Value as 1, which means that the Entropy field is escaped as the service VPN label of the data packet.
  • the second method directly defines the Type as 1 and the Length as 0, and no need to follow the Value, but directly uses the Type value of 1 to indicate that the Entropy field is escaped as the business VPN Label of the data packet. If the DSCP field is to be escaped later, for the first method, Value can be defined as 2 to indicate the DSCP field escape, or the second method can be used to directly define the type 2 to indicate the DSCP field escape.
  • the DSCP field in the BIER header similarly, after the value is copied in the Traffic Class of the outer IPv6 header, the DSCP field can be used to represent other content.
  • TLV TLV extension
  • BGP BGP, MVPN, MLD and other protocols
  • the BFR device When the BFR device originally performs load balancing processing according to the Entropy field in the BIER packet header, it can also notify the node's escape capability when flooding the BIER's BFR-ID value and other information in protocols such as OSPF or ISIS. To avoid load balancing processing errors.
  • the method further includes: carrying the form of the TLV in at least one of the following protocols between BFIR and BFER: border gateway protocol BGP, multicast virtual private network MVPN protocol, multicast Listen to the discovery protocol.
  • Border gateway protocol BGP border gateway protocol BGP
  • multicast virtual private network MVPN protocol multicast Listen to the discovery protocol.
  • the method further includes: copying the Entropy field in the BIER packet header to a position after the Flow Label field of the outer IPv6 packet, and assigning it to the virtual private network VPN data
  • the label value of the BIER message header is placed after the position of the original Entropy field in the BIER message header, and the method further includes: the reservation of the BIER message header is set to 1 as RSV.
  • BFIR/BFER supports both escaped and unescaped encapsulation processing methods
  • another bit in the BIER header can be used, such as the reserved RSV bit.
  • a certain bit, such as the low bit is set to 1 to indicate that the Entropy field has been escaped.
  • the encapsulation process of BFIR will add the following steps: after escaping the Entropy field, set RSV to 1.
  • the judgment of RSV will be added. If the corresponding bit is found to be set to 1, it means that the Entropy field in the BIER header has been escaped, so that BFER can The value of is used as the VPN label to locate the VPN entry.
  • the escape capability of any node in the network changes, other nodes in the network except the any node are notified by means of protocol notification, wherein the The escape capability is used to indicate whether any of the nodes has the Entropy field in the BIER packet header, copied to the position after the Flow Label field of the outer IPv6 packet, and the label assigned to the virtual private network VPN data. Value, the ability to place the position of the original Entropy field in the BIER header.
  • the node's support for the escape capability changes, it can notify other nodes in the form of protocol announcement.
  • the way can be re-announced through the capability, but with a special value, such as the newly added type in the above capability TLV or the Value is set to Special values such as full F; or re-announcement through the basic information of the protocol, such as the BGP protocol re-announces the supported address family, but no longer carries the capability information; so that other nodes can learn this information.
  • the BFIR node will be encapsulated according to the existing rules during encapsulation, and the BFR node can also be dynamically adjusted according to the situation of the next hop node to avoid packet processing errors.
  • the above modules can be implemented by software or hardware, and the latter can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.
  • Embodiments of the present disclosure also provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include, but is not limited to, a USB flash drive, a read-only memory (Read-Only Memory, referred to as ROM for short), and a random access memory (Random Access Memory, referred to as RAM for short) , mobile hard disk, magnetic disk or CD-ROM and other media that can store computer programs.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • An embodiment of the present disclosure also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • modules or steps of the present disclosure can be implemented by a general-purpose computing device, and they can be centralized on a single computing device or distributed in a network composed of multiple computing devices
  • they can be implemented in program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, can be performed in a different order than shown here.
  • the described steps, or they are respectively made into individual integrated circuit modules, or a plurality of modules or steps in them are made into a single integrated circuit module to realize.
  • the present disclosure is not limited to any particular combination of hardware and software.

Abstract

本公开实施例提供了一种数据报文的处理方法及装置、存储介质、电子装置，上述方法包括：在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下，将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，MPLS报文，OAM报文，采用上述方案，解决了相关技术中，尚未提供如何将BIER报文在IPv6报文中进行优化的问题。

Description

数据报文的处理方法及装置、存储介质、电子装置 技术领域
本公开实施例涉及通信领域，具体而言，涉及一种数据报文的处理方法及装置、存储介质、电子装置。
背景技术
互联网协议第6版(Internet Protocol Version 6，简称为IPv6)是互联网工程任务组(Internet Engineering Task Force，简称为IETF)设计的用于替代IPv4的下一代IP协议。IPv6的使用，不仅能解决网络地址资源数量的问题，而且也解决了多种接入设备连入互联网的障碍。
位索引显式复制(Bit Indexed Explicit Replication，简称为BIER)(RFC8279)是一种新型组播数据转发技术，该将网络边缘的节点都只用一个bit位来表示，组播流量在中间网络传输，额外封装一个特定的BIER报文头，这个报文头以bit位串的形式标注了该组播流的所有目的节点，中间网络转发节点根据bit位进行路由，保障流量能够发送到所有目的节点。中间节点转发设备事先通过路由协议，如三层网络中的开放式最短路径优先(OSPF Open Shortest Path First，简称为OSPF)协议，中间系统到中间系统(Intermediate System-to-Intermediate System，简称为ISIS)协议，形成用于指导BIER转发的位索引转发表(Bit Index Forwarding Table，简称为BIFT)表，在收到封装BIER报文头的流量时，依据BIFT来完成报文到目的节点的转发。BIER这种数据面转发技术因为没有组播树的建立问题，消除了组播树建立的时延，并且在网络出现链路或者节点问题时，收敛速度同OSPF或ISIS协议，比原来的组播树重建降低了巨大的时延。
BIER技术在传输的时候，仅需要将某条组播流量封装在BIER报文内作为载荷(payload)传输。对于BIER域的入口设备BFIR(Bit-Forwarding Ingress Router)来说，需要知道哪些BIER域的出口设备BFERs(Bit-Forwarding Egress Routers)需要这条组播流量，这样在BFER收到这条组播流量后，才能转发给BIER域外需要收到这条流量的组播接收者。BIER技术可以直接封装在以太报文中进行传输(协议号0xAB37)，在某些节点不能支持对以太BIER报文进行直接辨识时，如果仍然采用以太报文传输，不能正确辨识该报文的节点将成为黑洞丢弃报文。
针对相关技术中，如何将BIER报文在IPv6报文中进行优化的问题，尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种数据报文的处理方法及装置、存储介质、电子装置，以至少解决相关技术中尚未提供如何将BIER报文在IPv6报文中进行优化的问题的技术方案。
根据本公开的一个实施例，提供了一种数据报文的处理方法，包括：在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下， 将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，多协议标签交换(Multi-Protocol Label Switching，简称为MPLS)报文，运行、管理和维护(Operation Administration and Maintenance，简称为OAM)报文。
根据本公开的另一个实施例，还提供了一种数据报文的处理装置，包括：处理模块，设置为在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下，将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；设置模块，设置为在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，MPLS报文，OAM报文。
根据本公开的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开，可以对BIER报文和IPv6报文进行如下处理：将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，进而实现了将BIER报文封装在IPv6报文中，同样对DSCP字段也可以同样进行转义处理。采用上述技术方案，解决了相关技术中，还未能有效实现将BIER报文在IPv6报文中进行优化等问题。
附图说明
图1是本公开实施例的一种数据报文的处理方法的计算机终端的硬件结构框图；
图2是根据本公开实施例的数据报文的处理方法的流程图；
图3是根据本公开实施例的BIER报文封装在IPv6报文中的示意图(一)；
图4是根据本公开实施例的TLV的示意图；
图5是根据本公开实施例的应用在BIER域的BIER报文传输机制的示意图；
图6是根据本公开实施例的BIER报文封装在IPv6报文中的示意图(二)；
图7是根据本公开实施例的数据报文的处理装置的结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等 是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本公开实施例中所提供的方法实施例可以在计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图1是本公开实施例的一种数据报文的处理方法的计算机终端的硬件结构框图。如图1所示，计算机终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和设置为存储数据的存储器104，其中，上述计算机终端还可以包括设置为通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述计算机终端的结构造成限定。例如，计算机终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可设置为存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的数据报文的处理方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其设置为通过无线方式与互联网进行通讯。
相关技术中，组播技术在互联网上正得到越来越多的应用，比如多方会议，远程教育，远程医疗，网络直播等。随着IPv6的部署，这些组播数据报文，穿越IPv6网络已成为必须，对于一些不能直接支持BIER以太封装报文处理的节点，将BIER封装在IPv6头中已成为一个必须具备的功能。
本公开实施例以下提出一种新的报文封装方式，将BIER封装与IPv6封装结合起来，并将其中重复的部分字段进行转义处理，结合控制面的能力通告，在完全不影响功能的情况下，优化报文的封装与处理流程。
在本实施例中提供了一种运行于上述计算机终端的数据报文的处理方法，图2是根据本公开实施例的数据报文的处理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S102，在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下，将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；
步骤S104，在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，MPLS报文，OAM报文。
通过本公开，可以对BIER报文和IPv6报文进行如下处理：将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分 配的标签值，置于所述BIER报文头中的原Entropy字段的位置；在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，进而实现了将BIER报文封装在IPv6报文中，采用上述技术方案，解决了相关技术中，还未能有效实现将BIER报文封装在IPv6报文中等问题。
其中，上述步骤的执行主体可以为基站、终端等，但不限于此。
步骤S102和步骤S104的执行顺序是可以互换的，即可以先执行步骤S104，然后再执行S102。
应用上述步骤S102-步骤S104的技术方案，如图3所示，这种情况下，即使是基于VPN的业务，Proto字段不再设置为MPLS类型，而是直接设置为数据报文的真正类型，也就是IPv4，IPv6，Ethernet，MPLS或者OAM等.
在一个示例性实施例中，在通过步骤S102-S104的字段设置之后，上述方法还包括：将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，所述方法还包括：在需要对所述数据报文进行处理的设备在对所述数据报文进行转发处理时，仅根据所述IPv6报文头中的Flow Label字段进行负载均衡处理，可以理解的是，沿路的设备在进行转发处理时，仅根据IPv6头中的Flow Label字段进行负载均衡处理，而不再根据BIER报文头中的Entropy字段进行处理。
在一个示例性实施例中，所述方法还包括：在位转发出口路由器BFER收到数据报文时，将外层IPv6报文头从所述数据报文中剥离，根据BIER报文头中的原Entropy字段中的标签值，查找到与所述标签值对应的VPN；根据Proto字段所指示的数据类型，对所述数据报文进行转发处理，即在本公开实施例中，BFER在收到报文时，将外层IPv6头剥离后，将BIER报文头中的原Entropy字段，现Label字段，查找到对应的VPN，然后直接根据Proto的指示，读取后续的数据报文进行转发处理。假设Proto是IPv4，则BFER在对应的VPN中进行IPv4路由表查表处理，将数据报文转发给正确的接收者。
需要注意的是，Entropy值为0时，可以用于表示全局组播，也就是VPN为0或者没有VPN的情况，这种情况下，根据Proto查找相应的全局路由表即可。
BFIR和BFER对报文的转义处理，如果设备全都支持且仅支持这种方式，即只要BIER报文封装到IPv6头中都采用这样的解析方法，不需要其他的控制手段。但网络中部署的设备有的无法支持这种转义处理方式，因此可能存在两种方式都支持的情况，这种情况下，需要控制面进行扩展，扩展方式包括：
在一个示例性实施例中，所述方法还包括：对于非BFIR和非BFER的纯中间节点，如果所述中间节点仅根据所述IPv6报文头中的Flow Label进行负载均衡处理，则执行在BFIR和BFER之间进行能力协商与通告的处理流程。
在一个示例性实施例中，所述方法还包括：所述能力协商与通告的处理流程中的能力协商信息的定义通过TLV(Type，Length，Value)的形式体现。
在一个示例性实施例中，所述能力协商与通告的处理流程中的能力协商信息的定义通过TLV的形式体现，至少包括以下之一：通过所述TLV中的Type为1,Length为1个字节,且Value值定义为1来指示已将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，以及已将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；通过所述TLV中的Type为1,Length为0,且无Value 值来指示已将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，以及已将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置。
在一个示例性实施例中，所述方法还包括：通过所述TLV的Type为2,Length为1个字节,且Value值定义为1来指示已将BIER报文头中的DSCP字段，拷贝到外层IPv6报文的Traffic Class字段的位置，或者其他位置，BIER报文头中原DSCP字段则可以做其他用途；在DSCP字段中的TLV中的Type为2,Length为0,且无Value值来指示已将BIER报文头中的DSCP字段，拷贝到外层IPv6报文的Traffic Class字段的位置，或者其他位置，BIER报文头中原DSCP字段可以做其他用途。
即对于非BFIR和非BFER的纯中间节点，如果这些节点仅根据IPv6头中的Flow Label进行负载均衡处理，不看BIER报文头中的Entropy字段，则仅需要在BFIR和BFER之间进行能力协商与通告，能力协商信息的定义可以通过TLV的形式来体现，如图4所示。比如第一种方式定义Type为1，表示“转义”，Length为1个字节，Value值定义为1表示Entropy字段转义为数据报文的业务VPN label。第二种方式直接定义Type为1，Length为0，后面无需跟Value，而是直接用Type值为1表示Entropy字段转义为数据报文的业务VPN Label。后续如果对DSCP字段也进行转义时，对于第一种方式可以定义Value为2来表示DSCP字段转义，也可以采用第二种方式，直接定义类型2来表示DSCP字段转义。
对于BIER报文头中的DSCP字段，类似的，在外层IPv6头的Traffic Class复制了该值后，DSCP字段可以用于表示其他的内容。
需要说明的是，TLV的通告则是随着BFIR和BFER之间的协议信息交互进行，可以扩展BGP，MVPN，MLD等等协议，比如BFIR与BFER之间使用BGP进行数据报文信息交互，则可以将此TLV扩展随着BGP的报文进行通告；假设BFIR与BFER之间使用MLD进行数据报文信息交互，则可以将此扩展随着MLD的报文进行通告。
在其中的BFR设备原本根据BIER报文头中的Entropy字段进行负载均衡处理时，也可以在OSPF或者ISIS等协议泛洪BIER的BFR-ID值等信息时，同样通告节点的转义能力。以免出现负载均衡处理错误的情况。
在一个示例性实施例中，所述方法还包括：将所述TLV的形式携带在BFIR和BFER之间的至少以下之一协议中：边界网关协议BGP，组播虚拟专用网络MVPN协议，组播侦听发现协议。
在一个示例性实施例中，所述方法还包括：在将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置之后，所述方法还包括：BIER报文头的保留为RSV设置为1。
可以理解的是，在BFIR/BFER同时支持转义和不转义的封装处理方式时，可能无法识别出Entropy的真正含义，这时可以使用BIER报文头中另外的位，比如保留RSV位中的某一位，比如低bit位设置为1来表示Entropy字段已经通过转义处理。这样BFIR的封装流程将增加如下步骤：在对Entropy字段进行转义处理后，将RSV设置为1。BFER的解封装处理流程中，将增加对RSV的判断，如果发现相应的位被设置成1时，则说明该BIER报文头中的Entropy字段已经被转义处理，这样BFER可以将Entropy字段中的值作为VPN label来进行定位VPN 表项的操作。
在一个示例性实施例中，所述方法还包括：在网络中的任一节点的转义能力出现变化的情况下，通过协议通告的方式通知所述网络中除所述任一节点外的其他节点，其中，所述转义能力用于指示所述任一节点是否具备将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置的能力。
即在节点对转义能力的支持出现变化时，能够以协议通告的方式告知其他节点，方式可以通过能力的再次通告，但携带特殊值的方式，比如上述能力TLV中新增类型或者Value设置为特殊值如全F等方式；或者通过协议基础信息重新通告，如BGP协议重新通告所支持的地址族，但不再携带该能力信息的方式；使其他节点获知该信息。这样BFIR节点在封装时会按照已有规则进行封装，BFR节点还可以根据下一跳节点的情况进行动态调整，以免出现报文处理错误的情况。
为了更好的理解上述数据报文的处理流程，以下结合可选实施例对上述技术方案进行说明，但不用于限定本公开实施例的技术方案。
可选实施例一：
如图5所示的BIER域，该域使用IPv6封装的BIER报文传输机制，BFIR和BFER之间的组播数据报文有基于VPN1的，也有基于VPN2的，BFIR为VPN1分配标签10，为VPN2分配标签20。
BFIR与BFER之间运行基于BGP的MVPN，进行数据报文信息交互，也就是确定某条流量有哪些接收者所在BFER时，进行转义能力交互。也可以在最初协议会话建立的时候就进行转义能力通告。BFIR支持转义能力，则通告该能力，BFER支持转义能力的也通告该能力，不支持该能力的则不通告。
假设BFER2不支持转义能力，BFER1和BFER3支持转义能力，BFIR发现对接收者包括BFER2的流量不能进行转义处理。在这个图例中，对于VPN2的流量可以进行转义封装处理。
BFIR对数据报文的处理流程为：
步骤10，BFIR收到来自VPN2的流量，BFER对应BFER1和BFER3，将本来需要封装到BIER报文头中Entropy字段，用于负载均衡的值，封装到外层IPv6头的Flow Label字段中；
步骤12，BFIR将VPN2所对应的标签值20，封装到BIER报文头的Entropy字段中；
步骤14，因BFER1和BFER3同时支持转义和非转义方式，为了进行区分，BFIR将RSV的低bit位置为1，表示Entropy字段已进行转义。
步骤16，BFIR将组播数据报文直接作为BIER报文的payload直接附加在BIER报文头后，并将组播数据报文的类型直接赋值在BIER报文头中的Proto字段。如该数据报文是IPv4组播数据报文，则直接将BIER报文头中的Proto字段值设置为IPv4类型。
步骤18，BIER报文头及IPv6头中的其他字段按照原有规则进行封装。
中间BFR设备的处理流程：
步骤20：根据IPv6头中的Flow Label字段进行负载均衡处理。
步骤22：其余处理转发流程同已有规则。
BFER收到报文时的处理流程为：
步骤24：BFER识别BIER报文头中的RSV低bit位，当该值为1时知道该报文进行转义 处理；
步骤26：BFER读取Entropy字段的值，并在其不为0时，定位到相应的VPN。在该例中，将识别出该字段是标签值20，BFER定位到VPN2；如果为0时则查找全局路由表。
步骤28：BFER根据BIER报文头中的Proto值，直接查找VPN2中的路由表进行转发。
可选实施例二：
在网络中的节点能力支持出现变化时，当前的报文处理节点，能根据下一跳节点的情况，自动调整报文封装，以免出现节点无法正确处理报文的情况。
如图5所示，假设网络中已经进行转义能力的通告，BFIR对发送给支持转义能力BFER的报文，都进行转义处理。如图例中所述，BFIR通过协议通告，学习到BFER1和BFER3都支持转义能力，也用实施例一中的方式进行正常转义封装处理。
当BFER3由于配置或者其他情况出现能力变化时，比如BFER3进行设备更新后，不能支持转义能力，BFIR对需要发送给BFER3的报文，不能再进行转义处理。具体步骤为：
步骤30，BFIR收到BFER的能力撤销报文，该报文可能是通过能力的再次通告，但携带特殊值的方式，比如上述能力TLV中新增类型或者Value设置为特殊值如全F等方式；或者通过协议基础信息重新通告，但不再携带该能力信息的方式；使其他节点获知该信息。
步骤32，BFIR在对来自VPN2的报文封装，不再采用转义封装方式，而是采用已有封装规则进行封装转发。或者对BFER1仍然采用转义封装方式，对BFER3采用已有封装规则进行封装转发。
对于BFR节点的处理，可选支持如下步骤：
如图5中的BFRn节点，在获知BFER3不再支持转义功能时，收到了具有转义功能且需要发送给BFER3的报文，处理步骤为：
步骤40，BFRn收到报文，根据IPv6头中的Flow Label进行正常的负载均衡处理后，读取BIER报文头中的RSV低bit位字段，发现已置为1；
步骤42，BFRn对报文进行重新调整封装，将BIER报文头中的Proto字段设置为MPLS，在BIER报文头与后续的数据报文中插入标签，值为BIER报文头的原Entropy字段。重新对RSV位置0，封装后的报文类似图6，也就是将转义字段按照原有规则进行恢复。
步骤44，BFRn将重新封装的报文转发给BFER3。
在BFER3收到报文时，根据正常的处理规则进行处理，不会出现报文处理错误的情况。
通过上述技术方案，本公开可选实施例提出一种新的报文封装方式，将BIER封装与IPv6封装结合起来，将其部分字段进行转义处理，结合控制面的能力协商，在完全不影响功能的情况下，优化业务报文的封装与处理流程，可以起到提高封装及处理效率的作用，有利于BIER技术的进一步优化，利用外层IPv6头中的字段，在不影响功能实现的前提下，对BIER报文头中的字段进行转义处理，并且用能力通告进行协商。起到优化业务携带，优化报文封装及提高处理速度的目的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如 ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
在本实施例中还提供了一种数据报文的处理装置，该装置设置为实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本公开实施例的数据报文的处理装置的结构框图，如图7所示，该装置包括：
处理模块70，设置为在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下，将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；
设置模块72，设置为在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，MPLS报文，OAM报文。
通过本公开，可以对BIER报文和IPv6报文进行如下处理：将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，进而实现了将BIER报文封装在IPv6报文中，采用上述技术方案，解决了相关技术中，还未能有效实现将BIER报文封装在IPv6报文中进行优化等问题。
应用上述技术方案，如图3所示，这种情况下，即使是基于VPN的业务，Proto字段不再设置为MPLS类型，而是直接设置为数据报文的真正类型，也就是IPv4，IPv6，Ethernet，MPLS，OAM等.
在一个示例性实施例中，处理模块70，还设置为在需要对所述数据报文进行处理的设备在对所述数据报文进行转发处理时，仅根据所述IPv6报文头中的Flow Label字段进行负载均衡处理，可以理解的是，沿路的设备在进行转发处理时，仅根据IPv6头中的Flow Label字段进行负载均衡处理，而不再根据BIER报文头中的Entropy字段进行处理。
在一个示例性实施例中，处理模块70，还设置为在位转发出口路由器BFER收到数据报文时，将外层IPv6报文头从所述数据报文中剥离，根据BIER报文头中的原Entropy字段中的标签值，查找到与所述标签值对应的VPN；根据Proto字段所指示的数据类型，对所述数据报文进行转发处理，即在本公开实施例中，BFER在收到报文时，将外层IPv6头剥离后，将BIER报文头中的原Entropy字段，现Label字段，查找到对应的VPN，然后直接根据Proto的指示，读取后续的数据报文进行转发处理。假设Proto是IPv4，则BFER在对应的VPN中进行IPv4路由表查表处理，将数据报文转发给正确的接收者。
需要注意的是，Entropy值为0时，可以用于表示全局组播，也就是VPN为0或者没有VPN的情况，这种情况下，根据Proto查找相应的全局路由表即可。
BFIR和BFER对报文的转义处理，如果设备全都支持且仅支持这种方式，即只要BIER报文封装到IPv6头中都采用这样的解析方法，不需要其他的控制手段。但网络中部署的设备有的无法支持这种转义处理方式，因此可能存在两种方式都支持的情况，这种情况下，需要控 制面进行扩展，扩展方式包括：
在一个示例性实施例中，对于非BFIR和非BFER的纯中间节点，如果所述中间节点仅根据所述IPv6报文头中的Flow Label进行负载均衡处理，处理模块70，还设置为执行在BFIR和BFER之间进行能力协商与通告的处理流程。
在一个示例性实施例中，所述方法还包括：所述能力协商与通告的处理流程中的能力协商信息的定义通过TLV(Type，Length，Value)的形式体现。
在一个示例性实施例中，所述能力协商与通告的处理流程中的能力协商信息的定义通过TLV的形式体现，至少包括以下之一：通过所述TLV中的Type为1,Length为1个字节,且Value值定义为1来指示已将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，以及已将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；通过所述TLV中的Type为1,Length为0,且无Value值来指示已将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，以及已将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置。
在一个示例性实施例中，通过所述TLV的Type为2,Length为1个字节,且Value值定义为1来指示已将BIER报文头中的DSCP字段，拷贝到外层IPv6报文的Traffic Class字段的位置，BIER头中的原DSCP字段可以用于表示其他含义；在所述TLV中的Type为2,Length为0,且无Value值来指示已将BIER报文头中的DSCP字段，拷贝到外层IPv6报文的Traffic CLass字段的位置，以及BIER头中的原DSCP字段可以用于表示其他含义。
即对于非BFIR和非BFER的纯中间节点，如果这些节点仅根据IPv6头中的Flow Label进行负载均衡处理，而不看BIER报文头中的Entropy字段，则仅需要在BFIR和BFER之间进行能力协商与通告，能力协商信息的定义可以通过TLV的形式来体现，如图4所示。比如第一种方式定义Type为1，表示“转义”，Length为1个字节，Value值定义为1表示Entropy字段转义为数据报文的业务VPN label。第二种方式直接定义Type为1，Length为0，后面无需跟Value，而是直接用Type值为1表示Entropy字段转义为数据报文的业务VPN Label。后续如果对DSCP字段也进行转义时，对于第一种方式可以定义Value为2来表示DSCP字段转义，也可以采用第二种方式，直接定义类型2来表示DSCP字段转义。
对于BIER报文头中的DSCP字段，类似的，在外层IPv6头的Traffic Class复制了该值后，DSCP字段可以用于表示其他的内容。
需要说明的是，TLV的通告则是随着BFIR和BFER之间的协议信息交互进行，可以扩展BGP，MVPN，MLD等等协议，比如BFIR与BFER之间使用BGP进行数据报文信息交互，则可以将此TLV扩展随着BGP的报文进行通告；假设BFIR与BFER之间使用MLD进行数据报文信息交互，则可以将此扩展随着MLD的报文进行通告。
在其中的BFR设备原本根据BIER报文头中的Entropy字段进行负载均衡处理时，也可以在OSPF或者ISIS等协议泛洪BIER的BFR-ID值等信息时，同样通告节点的转义能力。以免出现负载均衡处理错误的情况。
在一个示例性实施例中，所述方法还包括：将所述TLV的形式携带在BFIR和BFER之间的至少以下之一协议中：边界网关协议BGP，组播虚拟专用网络MVPN协议，组播侦听发现协议。
在一个示例性实施例中，所述方法还包括：在将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置之后，所述方法还包括：BIER报文头的保留为RSV设置为1。
可以理解的是，在BFIR/BFER同时支持转义和不转义的封装处理方式时，可能无法识别出Entropy的真正含义，这时可以使用BIER报文头中另外的位，比如保留RSV位中的某一位，比如低bit位设置为1来表示Entropy字段已经通过转义处理。这样BFIR的封装流程将增加如下步骤：在对Entropy字段进行转义处理后，将RSV设置为1。BFER的解封装处理流程中，将增加对RSV的判断，如果发现相应的位被设置成1时，则说明该BIER报文头中的Entropy字段已经被转义处理，这样BFER可以将Entropy字段中的值作为VPN label来进行定位VPN表项的操作。
在一个示例性实施例中，在网络中的任一节点的转义能力出现变化的情况下，通过协议通告的方式通知所述网络中除所述任一节点外的其他节点，其中，所述转义能力用于指示所述任一节点是否具备将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置的能力。
即在节点对转义能力的支持出现变化时，能够以协议通告的方式告知其他节点，方式可以通过能力的再次通告，但携带特殊值的方式，比如上述能力TLV中新增类型或者Value设置为特殊值如全F等方式；或者通过协议基础信息重新通告，如BGP协议重新通告所支持的地址族，但不再携带该能力信息的方式；使其他节点获知该信息。这样BFIR节点在封装时会按照已有规则进行封装，BFR节点还可以根据下一跳节点的情况进行动态调整，以免出现报文处理错误的情况。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算 装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (13)

  1. 一种数据报文的处理方法，包括：
    在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下，将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；
    在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，MPLS报文，OAM报文。
  2. 根据权利要求1所述的方法，其中，还包括：将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置之后，所述方法还包括：
    在需要对所述数据报文进行处理的设备在对所述数据报文进行转发处理时，仅根据所述IPv6报文头中的Flow Label字段进行负载均衡处理。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    在位转发出口路由器BFER收到数据报文时，将外层IPv6报文头从所述数据报文中剥离，根据BIER报文头中的原Entropy字段中的标签值，查找到与所述标签值对应的VPN；
    根据Proto字段所指示的数据类型，对所述数据报文进行转发处理。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    对于非BFIR和非BFER的纯中间节点，如果所述中间节点仅根据所述IPv6报文头中的Flow Label进行负载均衡处理，则执行在BFIR和BFER之间进行能力协商与通告的处理流程。
  5. 根据权利要求4所述的方法，其中，所述方法还包括：所述能力协商与通告的处理流程中的能力协商信息的定义通过TLV的形式体现。
  6. 根据权利要求5所述的方法，其中，所述能力协商与通告的处理流程中的能力协商信息的定义通过TLV的形式体现，至少包括以下之一：
    通过所述TLV中的Type为1,Length为1个字节,且Value值定义为1来指示已将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，以及已将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；
    通过所述TLV中的Type为1,Length为0,且无Value值来指示已将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，以及已将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置。
  7. 根据权利要求5所述的方法，其中，所述方法还包括：
    在所述TLV的Type为2,Length为1个字节,且Value值定义为1来指示已将BIER报文头中的DSCP字段，拷贝到外层IPv6报文的Traffic Class或者其他字段的位置；
    在所述TLV中的Type为2,Length为0,且无Value值来指示已将BIER报文头中的DSCP字段，拷贝到外层IPv6报文的Traffic Class或者其他字段的位置。
  8. 根据权利要求5所述的方法，其中，所述方法还包括：将所述TLV的形式携带在BFIR和BFER之间的至少以下之一协议中：边界网关协议BGP，组播虚拟专用网络MVPN协议，组 播侦听发现协议。
  9. 根据权利要求1所述的方法，其中，所述方法还包括：
    在将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置之后，所述方法还包括：BIER报文头的保留为RSV设置为1。
  10. 根据权利要求1至9任一项所述的方法，其中，所述方法还包括：
    在网络中的任一节点的转义能力出现变化的情况下，通过协议通告的方式通知所述网络中除所述任一节点外的其他节点，其中，所述转义能力用于指示所述任一节点是否具备将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段之后的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置的能力。
  11. 一种数据报文的处理装置，包括：
    处理模块，设置为在位转发入口路由器BFIR对数据报文进行位索引显式复制BIER报文封装，以及外层IPv6报文封装的情况下，将BIER报文头中的Entropy字段，拷贝到外层IPv6报文的Flow Label字段的位置，并将为虚拟专用网络VPN数据所分配的标签值，置于所述BIER报文头中的原Entropy字段的位置；
    设置模块，设置为在BIER报文头之后设置数据报文，将BIER报文头中的Proto字段设置为表示所述数据报文的数据报文类型所对应的值，其中，所述数据报文类型至少包括以下之一：IPv4报文，IPv6报文，以太网报文，MPLS报文，OAM报文。
  12. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至10任一项中所述的方法。
  13. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至10任一项中所述的方法。
PCT/CN2021/073373 2020-07-31 2021-01-22 数据报文的处理方法及装置、存储介质、电子装置 WO2022021818A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21849736.0A EP4191966A4 (en) 2020-07-31 2021-01-22 METHOD AND DEVICE FOR PROCESSING DATA MESSAGES, STORAGE MEDIUM AND ELECTRONIC DEVICE
US18/018,905 US20230291682A1 (en) 2020-07-31 2021-01-22 Method and device for processing data packet, storage medium, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010761880.XA CN112491706A (zh) 2020-07-31 2020-07-31 数据报文的处理方法及装置、存储介质、电子装置
CN202010761880.X 2020-07-31

Publications (1)

Publication Number Publication Date
WO2022021818A1 true WO2022021818A1 (zh) 2022-02-03

Family

ID=74920767

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/073373 WO2022021818A1 (zh) 2020-07-31 2021-01-22 数据报文的处理方法及装置、存储介质、电子装置

Country Status (4)

Country Link
US (1) US20230291682A1 (zh)
EP (1) EP4191966A4 (zh)
CN (1) CN112491706A (zh)
WO (1) WO2022021818A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114095305A (zh) * 2020-07-21 2022-02-25 华为技术有限公司 Bier报文转发的方法、设备以及系统
CN114598634A (zh) * 2020-12-02 2022-06-07 华为技术有限公司 报文传输的方法、获取对应关系的方法、装置及系统
CN115314150A (zh) * 2021-04-21 2022-11-08 中兴通讯股份有限公司 一种报文处理方法、装置、存储介质及电子装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180287935A1 (en) * 2017-03-30 2018-10-04 Cisco Technology, Inc. Internet protocol based encapsulation for bit indexed explicit replication (bier)
US20180367456A1 (en) * 2017-06-20 2018-12-20 Cisco Technology, Inc. System and method to facilitate packet forwarding using stateful bit index explicit replication (bier) in a networking environment
CN110650094A (zh) * 2018-06-27 2020-01-03 华为技术有限公司 一种发送报文的方法、设备和系统
CN111147383A (zh) * 2018-11-02 2020-05-12 华为技术有限公司 报文转发的方法、发送报文的装置和接收报文的装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9438432B2 (en) * 2013-09-17 2016-09-06 Cisco Technology, Inc. Bit indexed explicit replication packet encapsulation
CN106656524A (zh) * 2015-10-30 2017-05-10 中兴通讯股份有限公司 一种bier控制信息的传输方法、装置和系统
CN108632150B (zh) * 2017-03-22 2022-02-25 中兴通讯股份有限公司 一种信息传递方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180287935A1 (en) * 2017-03-30 2018-10-04 Cisco Technology, Inc. Internet protocol based encapsulation for bit indexed explicit replication (bier)
US20180367456A1 (en) * 2017-06-20 2018-12-20 Cisco Technology, Inc. System and method to facilitate packet forwarding using stateful bit index explicit replication (bier) in a networking environment
CN110650094A (zh) * 2018-06-27 2020-01-03 华为技术有限公司 一种发送报文的方法、设备和系统
CN111147383A (zh) * 2018-11-02 2020-05-12 华为技术有限公司 报文转发的方法、发送报文的装置和接收报文的装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP4191966A4 *
YU JINGHAI, ZHANG ZHENG;PENG SHAOFU: "New Multicast Technology (BIER) and Prototype System", DIANXIN KEXUE - TELECOMMUNICATIONS SCIENCE, RENMIN YOUDIAN CHUBANSHE, BEIJING, CN, 20 November 2019 (2019-11-20), CN , pages 75 - 83, XP055831516, ISSN: 1000-0801, DOI: 10.11959/j.issn.1000−0801.2019221 *

Also Published As

Publication number Publication date
CN112491706A (zh) 2021-03-12
US20230291682A1 (en) 2023-09-14
EP4191966A1 (en) 2023-06-07
EP4191966A4 (en) 2023-12-20

Similar Documents

Publication Publication Date Title
US11616656B2 (en) Multicast data transmission method, related apparatus, and system
WO2021063232A1 (zh) 建立bier转发表项的方法、装置和系统
JP7208386B2 (ja) パケット転送方法、パケット送信装置、およびパケット受信装置
CN109756425B (zh) 组播转发方法、装置以及bfr
US9832031B2 (en) Bit index explicit replication forwarding using replication cache
US11902049B2 (en) BIER packet sending method and apparatus
US20220078114A1 (en) Method and Apparatus for Providing Service for Traffic Flow
US8339973B1 (en) Multicast traceroute over MPLS/BGP IP multicast VPN
US10009267B2 (en) Method and system for controlling an underlying physical network by a software defined network
WO2022021818A1 (zh) 数据报文的处理方法及装置、存储介质、电子装置
US20200396162A1 (en) Service function chain sfc-based communication method, and apparatus
WO2018072704A1 (zh) 报文传输方法、装置、节点和计算机存储介质
US20160006614A1 (en) Source Routing Using Path Computation Elements
WO2022062506A1 (zh) 一种数据处理方法、装置、存储介质及电子装置
US20230155932A1 (en) Multicast traffic transmission method and apparatus, communication node, and storage medium
WO2018214809A1 (zh) 消息发送方法及装置、存储介质
CN104243270A (zh) 一种建立隧道的方法和装置
US11784917B2 (en) Layer-2 network extension over Layer-3 network using encapsulation
WO2022041916A1 (zh) 报文头的处理方法及装置、存储介质、电子装置
JPWO2006093299A1 (ja) トンネリング装置及びそれに用いるトンネルフレーム振分方法並びにそのプログラム
WO2022117018A1 (zh) 报文传输的方法和装置
CN110708229B (zh) 一种收发消息的方法、装置和系统
WO2021196967A1 (zh) 消息交互方法、装置、设备和存储介质
EP3993357A1 (en) Method for sending bierv6 packet and first network device
WO2024001221A1 (zh) 一种组播信息转发方法、装置、组播信息汇聚节点及介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2021849736

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021849736

Country of ref document: EP

Effective date: 20230228

NENP Non-entry into the national phase

Ref country code: DE