(19)
(11)EP 3 531 617 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
29.07.2020 Bulletin 2020/31

(21)Application number: 17862851.7

(22)Date of filing:  18.10.2017
(51)International Patent Classification (IPC): 
H04L 12/18(2006.01)
(86)International application number:
PCT/CN2017/106660
(87)International publication number:
WO 2018/072704 (26.04.2018 Gazette  2018/17)

(54)

MESSAGE TRANSMISSION METHOD AND APPARATUS, NODE AND COMPUTER STORAGE MEDIUM

NACHRICHTENÜBERTRAGUNGSVERFAHREN UND -VORRICHTUNG, KNOTEN UND COMPUTERSPEICHERMEDIUM

PROCÉDÉ ET APPAREIL DE TRANSMISSION DE MESSAGES, NOEUD ET SUPPORT DE STOCKAGE INFORMATIQUE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 20.10.2016 CN 201610915563

(43)Date of publication of application:
28.08.2019 Bulletin 2019/35

(73)Proprietor: ZTE Corporation
Shenzhen, Guangdong 518057 (CN)

(72)Inventors:
  • ZHANG, Zheng
    Shenzhen Guangdong 518057 (CN)
  • WANG, Cui
    Shenzhen Guangdong 518057 (CN)

(74)Representative: Hervouet-Malbec, Sylvie 
Ipsilon Le Centralis 63, avenue du Général Leclerc
92340 Bourg-la-Reine
92340 Bourg-la-Reine (FR)


(56)References cited: : 
CN-A- 105 556 899
US-A1- 2015 181 309
US-A1- 2016 301 628
CN-A- 105 743 793
US-A1- 2016 127 139
  
  • Xu ET AL: "BIER encapsulation", , 24 February 2015 (2015-02-24), XP055561700, Retrieved from the Internet: URL:https://www.ietf.org/archive/id/draft- xu-bier-encapsulation-02.txt [retrieved on 2019-02-26]
  • HE, YUANTAO ET AL.: 'Comparative Analysis of Wireless Mesh Network in Active Routing Protocol' WIRELESS INTERNET TECHNOLOGY 15 August 2014, ISSN 1672-6944 pages 99 - 100
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

Technical Field



[0001] The present disclosure relates to the communication field, and in particular to a method, device, and node for message transmission, and a computer storage medium.

Background



[0002] Multicast technologies play an increasingly significant role in the Internet today. Interactive Personality TV (IPTV), Net-Meeting, and live action use the multicast technologies. The existing multicast technologies include Protocol Independent Multicast (PIM), Internet Control Message Protocol (IGMP), Multicast Listener Discovery Protocol (MLD), and so on. In an initial small-scale application scenario, these existing protocols may satisfy users' requirements. However, with the increasingly wide-scale application of multicast technologies, the networking form becomes more and more complex. When the multicast is directly applied in the Internet, a large number of control resources and signaling interactions of intermediate nodes are often occupied due to too many multicast states in a backbone network, and the development of Virtual Private Network (VPN) technology which is widely applied at present cannot be well supported. Therefore, the development direction at present tends to complete the transmission of multicast traffic by means of other technologies instead of running the traditional multicast protocol in the backbone network. Related technologies which may solve these problems include a Multicast Label Distribution Protocol (MLDP) technology, a Point-to-Multi Point Traffic Engineering (P2MPTE) technology, a Bit Indexed Explicit Replication (BIER) technology, and so on.

[0003] The core of the BIER technology is representing each node of a network edge by only one bit, the multicast traffic is transmitted in an intermediate network, and an extra specific BIER header is encapsulated, herein this message header indicates all destination nodes of the multicast traffic in the form of a bit string. An intermediate network forwarding device routes according to the bits, so as to ensure that the traffic can be sent to all the destination nodes. The intermediate node forwarding device forwards node information in advance through internal protocols like an Open Shortest Path First (OSPF) protocol and an Intermediate System to Intermediate System (ISIS) protocol in the layer-3 network, forms a Bit Index Forwarding Table (BIFT) used for guiding BIER forwarding, and completes the forwarding to the destination nodes of the message according to the BIFT when receiving the traffic encapsulated with a BIER header. Prior art documents disclosing BIER technology are, for instance: US 2016/301628 A1, US 2015/181309 A1, US 2016/127139 A1, and XP055561700.

[0004] A distance-vector routing protocol (Babel) is a routing protocol using a distance-vector routing algorithm and supporting IPv6 and IPv4, has merits such as good stability and high efficiency, and may be applied to wired and wireless networks. Compared with a wired network protocol represented by RIP, the Babel no longer uses a hop count to select an optimal route, but uses an Expected Transmission Count (ETC) to calculate the hop count reaching a certain node. The ETC not only considers information about the hop count reaching a certain node, but considers a series of indexes like link bandwidth and degree of congestion as the basis of route selection. However, the ETC will keep changing due to the change of wireless environments and the joining and exit of network nodes, which causes the route to keep turning, thereby making the network difficult to converge. Therefore, the Babel uses a history-sensitive mechanism to accelerate the convergence of the network, that is, a used path is selected in the case of approximate ETC values. The Babel will not perform periodical route update and declaration over the entire network after the convergence of the network, and triggers the update passively only when node information and state changes.

[0005] Thus, the BIER technology, as a multicast technology with advanced significance, may provide multicast traffic forwarding based on the shortest path, and eliminates a multicast entry state that the intermediate node needs to save in the multicast technology. However, in the related art, relevant information about the BIER technology cannot be transmitted in a network running the Babel routing protocol.

Summary



[0006] The embodiments of the present disclosure provide a method, device and node for message transmission, which may at least solve a problem in the related art that relevant information about BIER technology cannot be transmitted in a network running a Babel routing protocol.

[0007] According to an embodiment of the present disclosure, a method for message transmission is provided. The method includes: BIER information which is sent by other nodes except a first node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner is received, herein the BIER information is used for acquiring a BIER forwarding entry; the BIER forwarding entry is acquired according to the BIER information; and a message encapsulated in a BIER manner is sent to said other nodes according to the BIER forwarding entry.

[0008] According to an exemplary embodiment, the BIER information includes at least one of Bit Forwarding Router Identifier (BFR-id) information of a node and BFR-Prefix information of the node.

[0009] According to an exemplary embodiment, the BIER information further includes one or more of: a Sub-domain Identifier (Sub-domain-id), a Set Identifier (SI), a Bit String Length (BSL), a Topology Identifier (Topology-id), an encapsulation manner, algorithm information, a Multiprotocol Label Switching (MPLS) label, and tunnel encapsulation information.

[0010] According to an exemplary embodiment, the BIER forwarding entry is acquired according to the BIER information may further include: the BIER forwarding entry is acquired according to the BIER information and either of a default distance-vector routing algorithm and a Shortest Path First (SPF) algorithm.

[0011] According to an exemplary embodiment, after the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner is received, the method further includes: the BIER information and BIER information of the first node are sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner.

[0012] According to an exemplary embodiment, the BIER information is sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner may further include: the BIER information is sent to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, the BIER information is sent to other interfaces except an interface having a shortest path to the first node in said other nodes.

[0013] According to an exemplary embodiment, the Babel protocol extension manner may include at least one of a Type Length Value (TLV) manner and a sub-TLV manner.

[0014] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in an MPLS+BIER manner.

[0015] According to another embodiment of the present disclosure, a device for message transmission is provided, which includes: a receiving module, an acquiring module, and a sending module. The receiving module is configured to receive BIER information which is sent by other nodes except a first node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner, herein the BIER information is used for acquiring a BIER forwarding entry. The acquiring module is configured to acquire the BIER forwarding entry according to the BIER information. The sending module is configured to send a message encapsulated in a BIER manner to said other nodes according to the BIER forwarding entry.

[0016] According to an exemplary embodiment, the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0017] According to an exemplary embodiment, the BIER information further includes one or more of: a Sub-domain-id, an SI, a BSL, a Topology-id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0018] According to an exemplary embodiment, the acquiring module is further configured to acquire the BIER forwarding entry according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0019] According to an exemplary embodiment, the sending module is further configured to, after receiving the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner, send the BIER information and BIER information of the first node to said other nodes except the first node in the Babel network in the Babel protocol extension manner.

[0020] According to an exemplary embodiment, the sending module is further configured to send the BIER information to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, send the BIER information to other interfaces except an interface having a shortest path to the first node in said other nodes.

[0021] According to an exemplary embodiment, the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner.

[0022] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0023] According to another embodiment of the present disclosure, a node is provided. The node includes: a receiving device, which is configured to receive the BIER information which is sent by other nodes except the node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner, herein the BIER information is used for acquiring a BIER forwarding entry; a processor, which is configured to acquire the BIER forwarding entry according to the BIER information; and a sending device, which is configured to send a message encapsulated in a BIER manner to said other nodes according to the BIER forwarding entry.

[0024] According to an exemplary embodiment, the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0025] According to an exemplary embodiment, the BIER information further includes one or more of: a Sub-domain-id, an SI, a BSL, a Topology-id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0026] According to an exemplary embodiment, the processor is further configured to acquire the BIER forwarding entry according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0027] According to an exemplary embodiment, the sending device is further configured to send the BIER information and BIER information of the node to said other nodes except the node in the Babel network in the Babel protocol extension manner.

[0028] According to an exemplary embodiment, the sending device is further configured to send the BIER information to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, send the BIER information to other interfaces except an interface having a shortest path to the node in said other nodes.

[0029] According to an exemplary embodiment, the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner.

[0030] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0031] According to yet another embodiment of the present disclosure, a storage medium is also provided. The storage medium is configured to store program codes for performing the following operations: BIER information which is sent by other nodes except a first node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner is received, herein the BIER information is used for acquiring a BIER forwarding entry; the BIER forwarding entry is acquired according to the BIER information; and a message encapsulated in a BIER manner is sent to said other nodes according to the BIER forwarding entry.

[0032] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operation: the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0033] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operation: the BIER information further includes one or more of: a Sub-domain-id, an SI, a BSL, a Topology-id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0034] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operation: the BIER forwarding entry is acquired according to the BIER information may further include: the BIER forwarding entry is acquired according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0035] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operation: after the BIER information which is sent by said other nodes except the first node in the Babel network in a Babel protocol extension manner is received, the BIER information and BIER information of the first node are sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner.

[0036] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operations: the BIER information is sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner may further include: the BIER information is sent to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, the BIER information is sent to other interfaces except an interface having a shortest path to the first node in said other nodes.

[0037] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operation: the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner.

[0038] According to an exemplary embodiment, the storage medium is further configured to store program codes for performing the following operation: the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0039] In the embodiments of the present disclosure, BIER information which is sent by other nodes except a first node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner is received, herein the BIER information is used for acquiring a BIER forwarding entry; the BIER forwarding entry is acquired according to the BIER information; and the message encapsulated in the BIER manner is sent to said other nodes according to the BIER forwarding entry. Because the BIER related information may be transmitted in the network in the Babel protocol extension manner, the node may calculate the BIER forwarding entry according to the BIER related information, and traffic encapsulation and forwarding of the BIER may be implemented, so that the BIER technology may be applied in the network running the Babel protocol. Therefore, the technical solution provided in the embodiments of the present disclosure may solve the problem in the related art that relevant information about BIER technology cannot be transmitted in the network running the Babel routing protocol, thereby having a very important promotion effect on the development of multicast technology and network.

Brief Description of the Drawings



[0040] The accompanying drawings described here are used for providing deeper understanding of the present disclosure, and constitute a part of the present application. Schematic embodiments of the present disclosure and description thereof are used for illustrating the present disclosure and not intended to form an improper limit to the present disclosure. In the accompanying drawings:

Fig. 1 is a hardware structure diagram of a mobile terminal for a method for message transmission according to an embodiment of the present disclosure;

Fig. 2 is a flowchart of a method for message transmission according to an embodiment of the present disclosure;

Fig. 3 is a first schematic diagram of a Babel protocol based network according to an embodiment of the present disclosure;

Fig. 4 is a first schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 5 is a second schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 6 is a second schematic diagram of the Babel protocol based network according to an embodiment of the present disclosure;

Fig. 7 is a third schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 8 is a fourth schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 9 is a third schematic diagram of the Babel protocol based network according to an embodiment of the present disclosure;

Fig. 10 is a fifth schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 11 is a sixth schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 12 is a seventh schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 13 is an eighth schematic diagram of notification of BIER related information according to an embodiment of the present disclosure;

Fig. 14 is a structure diagram of a device for message transmission according to an embodiment of the present disclosure; and

Fig. 15 is a structure diagram of a node according to an embodiment of the present disclosure.


Detailed Description of the Embodiments



[0041] The present disclosure is elaborated below with reference to the accompanying drawings and embodiments. It is to be noted that the embodiments in the present application and the characteristics in the embodiments may be combined under the condition of no conflicts.

[0042] It is to be noted that the terms like "first" and "second" in the specification, the claims and the accompanying drawings of the present disclosure are used for differentiating the similar objects, but do not have to describe a specific order or a sequence.

First embodiment



[0043] The method provided by the first embodiment may be performed in a mobile terminal, a computer terminal or similar operating devices. By taking that the method is performed on the mobile terminal, Fig. 1 is a hardware structure diagram of a mobile terminal for a method for message transmission according to an embodiment of the present disclosure. As shown in Fig. 1, the mobile terminal 10 may include one or more (only one is shown here) of a processor 102 (the processor 102 may include, but not limited to, a Micro Processor Unit (MCU) or a Field Programmable Gate Array (FPGA), and other processing devices), a memory 104 for storing data, and a transmission device 106 for a communication function. Those of ordinary skill in the art may understand that the structure shown in Fig. 1 is only schematic, and does not form a limit to the structure of the above electronic device. For example, the mobile terminal 10 may also include more or less components than that in Fig. 1, or has a configuration different from that in Fig. 1.

[0044] The memory 104 may be configured to store a software program and module of application software, for example, a program instruction/module corresponding to the method for message transmission in the embodiments of the present disclosure. The processor 102 executes various function applications and data processing by running the software program and module stored in the memory 104, namely implementing the above method. The memory 104 may include a high-speed RAM, and may also include a nonvolatile memory, for example, one or more than one magnetic storage device, a flash memory, or other nonvolatile solid state memory. In some examples, the memories 104 may further include memories remotely set relative to the processor 102, and these remote memories may be coupled to the mobile terminal 10 through the network. The examples of the network include, but not limited to, Internet, Intranet, LAN, mobile communication networks and a combination of them.

[0045] The transmission device 106 is configured to receive or send data via a network. A specific example of the network may include a wireless network provided by a communication provider of the mobile terminal 10. In an example, the transmission device 106 includes a Network Interface Controller (NIC), which may be connected with other network devices through a base station to communicate with the Internet. In an example, the transmission device 106 may be a Radio Frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0046] In the present embodiment, a method for message transmission performed on the mobile terminal is provided. Fig. 2 is a flowchart of a method for message transmission according to an embodiment of the present disclosure. As shown in Fig. 2, the flow includes the following operations.

[0047] At S202, BIER information which is sent by other nodes except a first node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner is received, herein the BIER information is used for acquiring a BIER forwarding entry.

[0048] At S204, the BIER forwarding entry is acquired according to the BIER information.

[0049] At S206, a message encapsulated in a BIER manner is sent to said other nodes according to the BIER forwarding entry.

[0050] Through the above operations, because the BIER related information may be transmitted in the network in the Babel protocol extension manner, the node may calculate the BIER forwarding entry according to the BIER related information, and traffic encapsulation and forwarding of the BIER may be implemented, so that the BIER technology may be applied in the network running the Babel protocol. Therefore, a problem in the related art that relevant information about BIER technology cannot be transmitted in a network running a Babel routing protocol may be solved, thereby having a very important promotion effect on the development of multicast technology and network.

[0051] According to an exemplary embodiment, the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0052] According to an exemplary embodiment, the BIER information may also include one or more of: a Sub-domain-id, an SI, a BSL, a Topology-id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0053] For example, the BIER information includes: the BFR-id information of the node, the BFR-Prefix information of the node, and/or other BIER related information. The other BIER related information includes one or more of the Sub-domain-id, the SL, the BSL, the Topology-id, the encapsulation manner, algorithm, the MPLS label, and the tunnel encapsulation.

[0054] According to an exemplary embodiment, the BIER forwarding entry is acquired according to the BIER information may further include: the BIER forwarding entry is acquired according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm. Alternatively, the BIER forwarding entry may also be acquired according to the BIER information and other algorithms carried in the algorithm information.

[0055] According to an exemplary embodiment, after the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner is received, the method further includes: the BIER information and BIER information of the first node are sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner.

[0056] According to an exemplary embodiment, the BIER information is sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner may further include: the BIER information is sent to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, the BIER information is sent to other interfaces except an interface having a shortest path to the first node in said other nodes.

[0057] According to an exemplary embodiment, the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner. For example, the Babel protocol extension manner may be the TLV manner or the sub-TLV manner, and may also be a combination of several manners.

[0058] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in an MPLS+BIER manner.

[0059] Fig. 3 is a first schematic diagram of a Babel protocol based network according to an embodiment of the present disclosure. In order to facilitate understanding the above embodiment, an elaboration is given by taking the network shown in Fig. 3 for example. As shown in Fig. 3, the network is a network using the Babel protocol as the routing protocol, and has a BIER function. In order to implement a BIER forwarding function, the BIER related information needs to be spread to each node through the Babel protocol. If the nodes 1/2/3/4/5 are edge nodes of a connection source or a receiver network, for the purpose of simplicity, the number identifies following the nodes in Fig. 3 represent the allocated BFR-id information. For example, the allocated BFR-id information of the node 1 is 1, and the allocated BFR-id information of the node 2 is 2.

[0060] The manners of notifying the BIER related information in the Babel protocol may be the TLV manner or the sub-TLV manner. The specific content of the BIER related information may be notified in a manner shown in Fig. 4, here a type value is assumed as 1, and the BFR-id and the BFR-Prefix information are also notified.

[0061] Because the Babel is a distance-vector routing protocol, after the BIER related information sent from another node is received, it is needed to send the BIER related information to other nodes, so as to ensure that all the nodes may receive the BIER information of other nodes. As shown in Fig. 5, the information in Fig. 5 is the BIER related information of the node 2, in which the value of the Sub-domain id is 1, the BSL is 64, the SI is 1, the value of the BFR-id is 2, and the value of the BFR-Prefix is 10.40.2.1. After being sent by one BIER node to its adjacent nodes 1/3/5, the information is also forwarded by the nodes 1/3/5. By virtue of this manner, all the nodes will receive the BIER information of all the other nodes except itself.

[0062] According to an exemplary embodiment, the node sends its own BIER information to other nodes in a manner of sending the information to all the adjacent nodes. For example, in Fig. 3, the node 2 sends its own BIER information to the nodes 1/3/5. Upon receiving the information of the node 2, the nodes 1/3/5 may send the information to the other adjacent nodes, specifically, the information may be sent simply to all other interfaces except the interface receiving the information, or according to a Babel route calculation result, the information may be sent to other interfaces except an interface having a shortest path to the node 2.

[0063] After collecting the BIER information of the other nodes, each of the nodes acquires the BIER forwarding entry according to the route calculation result of the Babel protocol, and when receiving a BIER message, forwards the message according to the BIER forwarding entry, thereby implementing application of the BIER technology.

[0064] Fig. 6 is a second schematic diagram of the Babel protocol based network according to an embodiment of the present disclosure. As shown in Fig. 6, the network uses the Babel protocol as the routing protocol. BIER management of the network adopts a manner of dividing the sub-domains. As shown in Fig. 6, there are nodes 1/2/3/4 in the sub-domain 1; and there are nodes 1/2/3 in the sub-domain 2. The BFR-ids used in the two sub-domains are repeated, so it is possible to notify in a manner of dividing the sub-domains. The notification manner may be a manner shown in Fig. 4 and Fig. 7, and the information may be notified in a manner of sub-domain for which a type value is assumed as 2. The information may also be notified in a manner for which the type value is assumed as 3, as shown in Fig. 8.

[0065] In the same sub-domain network, for the need of services, the nodes may also be divided in a manner of layering the SI, similarly, the information of the SI may also be notified in a manner for which an individual type value is assumed as 4, as shown in Fig. 7. The information may also be notified together with the other BIER information like the BFR-Prefix and the BFR-id in a manner for which the type value is assumed as 5, as shown in Fig. 8.

[0066] Fig. 9 is a third schematic diagram of the Babel protocol based network according to an embodiment of the present disclosure. Because of a forwarding feature of the BIER technology, the BSLs that different nodes in the network may support are different, in the network where the Babel serves as the routing protocol, the information of the BSL may also be notified in the Babel protocol extension manner. As shown in Fig. 10, in the network, the BSL that the node 1 supports is 64; the BSL that the node 2 supports is 128; and the BSL that the node 3 supports is 64 and 128. The node 1 may adopt a manner of BSL value for which the type value is 6, as shown in Fig. 10, to notify the BSL. The node 3 may adopt a manner of BSL value for which the type value is 7, as shown in Fig. 11, to notify the BSL.

[0067] It is to be noted that in a BIER network, many encapsulation manners may be supported, for example, an Ethernet encapsulation, or an MPLS encapsulation, or other encapsulation manners. Similarly, different encapsulation manners and information may also be notified in the Babel protocol extension manner. For example, the encapsulation manner supported by the node is the MPLS encapsulation may be notified in a manner for which the type value is assumed as 8, as shown in Fig. 12. Furthermore, an MPLS encapsulation label of the node and information represented by the MPLS encapsulation label may also be notified in a manner for which the type value is assumed as 9, as shown in Fig. 13. So, the forwarding entry of an MPLS label table is generated at the node, and during message forwarding, the BIER message may be encapsulated according to the corresponding MPLS label notified by each node.

[0068] It is to be noted that if the Babel protocol is used as the routing protocol in a certain BIER network, and the Babel protocol is the distance-vector routing protocol, the BIER related information may be calculated in a common manner of calculating a route (for example, the distance-vector routing algorithm). In some networks, it may be needed to use the SPF algorithm and other algorithms because of service requirements, so the Babel protocol may also be extended to carry an SPF algorithm mark in a manner for which the type value is assumed as 10, as shown in Fig. 12, and each node performs related calculation of the BIER information according to the SPF algorithm.

[0069] It is to be noted that there may be nodes not supporting the BIER technology in some BIER networks, when passing these nodes, a tunnel encapsulation manner is often adopted. There may be a Generic Routing Encapsulation (GRE), an MPLS tunnel encapsulation, an IP tunnel encapsulation, and other forms of encapsulation. Tunnel encapsulation information of the node is also transferred as the BIER related information, and the contents included may also include, except a tunnel encapsulation type, a tunnel end, security, and other related information.

[0070] The Babel protocol may generally be extended to carry information about the tunnel encapsulation type in a manner for which the type value is assumed as 11, as shown in Fig. 12, and may also be extended to carry related information about the tunnel encapsulation in a manner for which the type value is assumed as 13, as shown in Fig. 13.

[0071] It can be seen from each above embodiment that the BIER related information may be transferred in the network in the Babel protocol extension manner, and the TLVs in each embodiment may be combined freely for use, thereby widening the scope and scenario of application of the BIER technology, and having a very important promotion effect on the development of the multicast technology and network.

[0072] Through the above description of the implementations, those skilled in the art may clearly know that the method according to the above embodiments may be implemented by means of software plus a necessary common hardware platform, certainly by means of hardware; but in many cases, the former is the better implementation. Based on this understanding, the technical solution of the present disclosure substantially or the part making a contribution to the related art can be embodied in the form of software product; the computer software product is stored in a storage medium (for example, a Read-Only Memory (ROM)/Random Access Memory (RAM), a magnetic disk, and a compact disc) and includes a number of instructions to make a computer device (which can be a personal computer, a server or a network device, etc.) perform all or part of the method in each embodiment of the present disclosure.

Second embodiment



[0073] The present embodiment also provides a device and node for message transmission. The device is configured to implement the above embodiments and exemplary implementations. The embodiments and exemplary implementations which have been elaborated will not be repeated here. The term "module" used below can realize a combination of software and/or hardware with an intended function. Although the device described in the following embodiment is better realized through software, the realization through hardware or a combination of software and hardware is possible and conceived.

[0074] Fig. 14 is a structure diagram of the device for message transmission according to an embodiment of the present disclosure. As shown in Fig. 14, the device includes: a receiving module 142, an acquiring module 144, and a sending module 146.

[0075] The receiving module 142 is configured to receive BIER information which is sent by other nodes except a first node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner, herein the BIER information is used for acquiring a BIER forwarding entry.

[0076] The acquiring module 144 is coupled to the receiving module 142, and is configured to acquire the BIER forwarding entry according to the BIER information.

[0077] The sending module 146 is coupled to the acquiring module 144, and is configured to send the message encapsulated in the BIER manner to said other nodes according to the BIER forwarding entry.

[0078] According to an exemplary embodiment, the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0079] According to an exemplary embodiment, the BIER information further includes one or more of: a Sub-domain-id, an SI, a BSL, a Topology id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0080] According to an exemplary embodiment, the acquiring module 144 is further configured to acquire the BIER forwarding entry according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0081] According to an exemplary embodiment, the sending module is further configured to, after receiving the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner, send the BIER information and BIER information of the first node to said other nodes except the first node in the Babel network in the Babel protocol extension manner.

[0082] According to an exemplary embodiment, the sending module is further configured to send the BIER information to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, send the BIER information to other interfaces except an interface having a shortest path to the first node in said other nodes.

[0083] According to an exemplary embodiment, the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner.

[0084] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0085] The embodiments of the present disclosure also provide a node. Fig. 15 is a structure diagram of the node according to an embodiment of the present disclosure. As shown in Fig. 15, the node includes: a receiving device 152, a processor 154, and a sending device 156.

[0086] The receiving device 152 is configured to receive BIER information which is sent by other nodes except the node in a distance-vector routing protocol (Babel) network in a Babel protocol extension manner, herein the BIER information is used for acquiring a BIER forwarding entry.

[0087] The processor 154 is coupled to the receiving device 152, and is configured to acquire the BIER forwarding entry according to the BIER information.

[0088] The sending device 156 is coupled to the processor 154, and is configured to send the message encapsulated in the BIER manner to said other nodes according to the BIER forwarding entry.

[0089] According to an exemplary embodiment, the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0090] According to an exemplary embodiment, the BIER information further includes one or more of: a Sub-domain-id, an SI, a BSL, a Topology id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0091] According to an exemplary embodiment, the processor 154 is further configured to acquire the BIER forwarding entry according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0092] According to an exemplary embodiment, the sending device 156 is further configured to send the BIER information and BIER information of the node to said other nodes except the node in the Babel network in the Babel protocol extension manner.

[0093] According to an exemplary embodiment, the sending device 156 is further configured to send the BIER information to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, send the BIER information to other interfaces except an interface having a shortest path to the node in said other nodes.

[0094] According to an exemplary embodiment, the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner.

[0095] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0096] It is to be noted that, each of the above modules may be realized by software or hardware. For the latter, the each of the above modules may be realized by, but not limited to, the following way: all of the above modules are in the same processor; or, the above modules are respectively in different processors in form of any combination.

Third embodiment



[0097] The embodiments of the present disclosure also provide a storage medium. In an exemplary embodiment, in the present embodiment, the storage medium may be set to store program codes for performing the following operations.

[0098] At S1, BIER information which is sent, in a Babel protocol extension manner, by other nodes except a first node in a distance-vector routing protocol (Babel) network is received, herein the BIER information is used for acquiring a BIER forwarding entry.

[0099] At S2, the BIER forwarding entry is acquired according to the BIER information.

[0100] At S3, the message encapsulated in the BIER manner is sent to said other nodes according to the BIER forwarding entry.

[0101] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation.

[0102] At S1, the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0103] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation.

[0104] At S1, the BIER information may further include one or more of: a Sub-domain-id, an SI, a BSL, a Topology id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0105] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation: the BIER forwarding entry is acquired according to the BIER information may further include the following operation.

[0106] At S1, the BIER forwarding entry is acquired according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0107] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation: after the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner is received, the method further includes the following operation.

[0108] At S1, the BIER information and BIER information of the first node are sent to said other nodes except the first node in the Babel network in a Babel protocol extension manner.

[0109] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation: the BIER information is sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner may further include one of the following operations.

[0110] At S1, the BIER information is sent to all other interfaces except an interface receiving the BIER information in said other nodes in a Babel protocol extension manner.

[0111] At S2, according to a Babel route calculation result, the BIER information is sent to other interfaces except the interface having the shortest path to the first node in the other nodes.

[0112] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation.

[0113] At S1, the Babel protocol extension manner may include at least one of a TLV manner and a sub-TLV manner.

[0114] According to an exemplary embodiment, the storage medium is also configured to store program codes for performing the following operation.

[0115] At S1, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0116] According to an exemplary embodiment, the storage medium may include, but not limited to, a USB flash disk, an ROM, an RAM, a mobile hard disk, a magnetic disk or a compact disc, and other media capable of storing the program codes.

[0117] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, the following operations: BIER information which is sent, in a manner of Babel protocol extension, by other nodes except a first node in a distance-vector routing protocol (Babel) network is received, herein the BIER information is used for acquiring a BIER forwarding entry; the BIER forwarding entry is acquired according to the BIER information; and the message encapsulated in the BIER manner is sent to said other nodes according to the BIER forwarding entry.

[0118] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, that: the BIER information includes at least one of BFR-id information of a node and BFR-Prefix information of the node.

[0119] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, that: the BIER information further includes one or more of: a Sub-domain-id, an SI, a BSL, a Topology-id, an encapsulation manner, algorithm information, an MPLS label, and tunnel encapsulation information.

[0120] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, that: the BIER forwarding entry is acquired according to the BIER information may further include: the BIER forwarding entry is acquired according to the BIER information and either of a default distance-vector routing algorithm and an SPF algorithm.

[0121] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, that: after the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner is received, the method further includes: the BIER information and BIER information of the first node are sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner.

[0122] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, that: the BIER information is sent to said other nodes except the first node in the Babel network in the Babel protocol extension manner may further include: the BIER information is sent to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, the BIER information is sent to other interfaces except an interface having a shortest path to the first node in said other nodes.

[0123] According to an exemplary embodiment, the processor performs, according to the program codes stored in the storage medium, that: the Babel protocol extension manner may include at least one of the TLV triple manner and the sub-TLV manner.

[0124] According to an exemplary embodiment, the message encapsulated in the BIER manner includes: a message encapsulated by a BIER header, or a message encapsulated in a MPLS+BIER manner.

[0125] The specific examples in the present embodiment may refer to the examples described in the above embodiments and alternative embodiments, and will not be repeated here.

[0126] It is apparent that those skilled in the art should appreciate that the above modules and operations of the present disclosure may be implemented by a general-purpose computing device, and they may be centralized in a single computing device or distributed on a network composed of multiple computing devices; optionally, they may be implemented by a program code which is capable of being executed by the computing device, so that they may be stored in a storage device and executed by the computing device; and in some situations, the presented or described operations may be executed in an order different from that described here; or they are made into integrated circuit modules, respectively; or multiple modules and operations of them are made into a single integrated circuit module to realize. Therefore, the present disclosure is not limited to any particular combination of hardware and software.

[0127] The above is only the exemplary embodiments of the present disclosure and not intended to limit the present disclosure; for those skilled in the art, the present disclosure may have various modifications and changes. Any modifications, equivalent replacements, improvements and the like within the principle of the present disclosure should fall within the protection scope of the claims of the present disclosure.

Industrial Applicability



[0128] The technical solution provided by the embodiments of the present disclosure may be applied to the communication field. By using the technical solution provided by the embodiments of the present disclosure may solve the problem in the related art that relevant information about the BIER technology cannot be transmitted in the network running the Babel routing protocol, thereby having a very important promotion effect on the development of the multicast technology and network.


Claims

1. A method , performed by a node, for message transmission, comprising:

receiving (S202) Bit Indexed Explicit Replication, BIER, information which is sent by other nodes except a first node in a distance-vector routing protocol, Babel, network in a Babel protocol extension manner, wherein the BIER information is used for acquiring a BIER forwarding entry;

acquiring (S204) the BIER forwarding entry according to the BIER information; and

sending (S206) a message encapsulated in a BIER manner to said other nodes according to the BIER forwarding entry.


 
2. The method as claimed in claim 1, wherein the BIER information comprises at least one of Bit Forwarding Router Identifier, BFR-id, information of a node and BFR-Prefix information of the node.
 
3. The method as claimed in claim 2, wherein the BIER information further comprises one or more of: a Sub-domain Identifier, Sub-domain-id, a Set Identifier, SI, a Bit String Length, BSL, a Topology Identifier, Topology-id, an encapsulation manner, algorithm information, a Multiprotocol Label Switching, MPLS, label, and tunnel encapsulation information.
 
4. The method as claimed in claim 3, wherein acquiring (S204) the BIER forwarding entry according to the BIER information comprises:
acquiring the BIER forwarding entry according to the BIER information and either of a default distance-vector routing algorithm and a Shortest Path First, SPF, algorithm.
 
5. The method as claimed in claim 1, wherein after receiving (S202) the BIER information which is sent by said other nodes except the first node in the Babel network in the Babel protocol extension manner, further comprising:
sending the BIER information and BIER information of the first node to said other nodes except the first node in the Babel network in the Babel protocol extension manner.
 
6. The method as claimed in claim 5, wherein sending the BIER information to said other nodes except the first node in the Babel network in the Babel protocol extension manner comprises:

sending the BIER information to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner; or,

according to a Babel route calculation result, sending the BIER information to other interfaces except an interface having a shortest path to the first node in said other nodes.


 
7. The method as claimed in any one of claims 1 to 6, wherein the Babel protocol extension manner comprises at least one of a Type Length Value, TLV, manner and a sub-TLV manner.
 
8. The method as claimed in any one of claims 1 to 6, wherein the message encapsulated in the BIER manner comprises: a message encapsulated by a BIER header, or a message encapsulated in an MPLS+BIER manner.
 
9. A node, comprising:

a receiving device (152), which is configured to receive Bit Indexed Explicit Replication, BIER, information which is sent by other nodes except the node in a distance-vector routing protocol, Babel, network in a Babel protocol extension manner, wherein the BIER information is used for acquiring a BIER forwarding entry;

a processor (154), which is configured to acquire the BIER forwarding entry according to the BIER information; and

a sending device (156), which is configured to send a message encapsulated in a BIER manner to said other nodes according to the BIER forwarding entry.


 
10. The node as claimed in claim 9, wherein the BIER information comprises at least one of Bit Forwarding Router Identifier, BFR-id, information of a node and BFR-Prefix information of the node.
 
11. The node as claimed in claim 10, wherein the BIER information further comprises one or more of: a Sub-domain Identifier, Sub-domain-id, a Set Identifier, SI, a Bit String Length, BSL, a Topology Identifier, Topology-id, an encapsulation manner, algorithm information, a Multiprotocol Label Switching, MPLS, label, and tunnel encapsulation information.
 
12. The node as claimed in claim 11, wherein the processor (154) is further configured to acquire the BIER forwarding entry according to the BIER information and either of a default distance-vector routing algorithm and a Shortest Path First, SPF, algorithm.
 
13. The node as claimed in claim 9, wherein the sending device (156) is further configured to send the BIER information and BIER information of the node to said other nodes except the node in the Babel network in the Babel protocol extension manner.
 
14. The node as claimed in claim 13, wherein the sending device (156) is further configured to send the BIER information to all other interfaces except an interface receiving the BIER information in said other nodes in the Babel protocol extension manner, or according to a Babel route calculation result, send the BIER information to other interfaces except an interface having a shortest path to the node in said other nodes.
 
15. The node as claimed in any one of claims 9 to 14, wherein the Babel protocol extension manner comprise at least one of a Type Length Value, TLV, manner and a sub-TLV manner,
or
wherein the message encapsulated in the BIER manner comprises: a message encapsulated by a BIER header, or a message encapsulated in an MPLS+BIER manner.
 


Ansprüche

1. Verfahren zur Nachrichtenübermittlung, ausgeführt in einem Knoten und Folgendes umfassend:

Empfangen (S202) von BIER(Bit Indexed Explicit Replication)-Informationen die von anderen Knoten mit Ausnahme eines ersten Knotens in einem Distanzvektor-Routingprotokoll(Babel)-Netzwerk in einer Babelprotokoll-Erweiterungsweise gesendet werden, wobei die BIER-Informationen zum Erfassen eines BIER-Weiterleitungseintrags verwendet werden,

Erfassen (S204) des BIER-Weiterleitungseintrags gemäß den BIER-Informationen und

Senden (S206) einer Nachricht, die in einer BIER-Weise eingekapselt ist, an die anderen Knoten gemäß dem BIER-Weiterleitungseintrag.


 
2. Verfahren nach Anspruch 1, wobei die BIER-Informationen Bitweiterleitungsrouter-Kennungs(BFR-ID, Bit Forwarding Router Identifier)-Informationen eines Knotens und/oder BFR-Präfixinformationen des Knotens umfassen.
 
3. Verfahren nach Anspruch 2, wobei die BIER-Informationen ferner eines oder mehreres des Folgenden umfassen: eine Teilbereichskennung (Teilbereichs-ID), eine Einstellungskennung (SI, Set Identifier), eine Bitfolgelänge (BSL, Bit String Length), eine Topologiekennung (Topologie-Id), eine Einkapselungsweise, Algorithmusinformationen, ein MPLS(Multiprotocol Label Switching)-Label und Tunneleinkapselungsinformationen.
 
4. Verfahren nach Anspruch 3, wobei das Erfassen (S204) des BIER-Weiterleitungseintrags gemäß den BIER-Informationen Folgendes umfasst:
Erfassen des BIER-Weiterleitungseintrags gemäß den BIER-Informationen und eines von einem Standarddistanzvektor-Routingalgorithmus und einem Kürzester-Weg-Zuerst(SPF, Shortest Path First)-Algorithmus.
 
5. Verfahren nach Anspruch 1, wobei nach dem Empfangen (S202) von BIER-Informationen, die von den anderen Knoten mit Ausnahme des ersten Knotens in dem Babel-Netzwerk in der Babelprotokoll-Erweiterungsweise gesendet werden, Folgendes umfassend:
Senden der BIER-Informationen und BIER-Informationen des ersten Knotens an die anderen Knoten mit Ausnahme des ersten Knotens in dem Babel-Netzwerk in der Babelprotokoll-Erweiterungsweise.
 
6. Verfahren nach Anspruch 5, wobei das Senden der BIER-Informationen des ersten Knotens an die anderen Knoten mit Ausnahme des ersten Knotens in dem Babel-Netzwerk in der Babelprotokoll-Erweiterungsweise Folgendes umfasst:

Senden der BIER-Informationen an alle anderen Schnittstellen mit Ausnahme einer Schnittstelle, welche die BIER-Informationen in den anderen Knoten in der Babelprotokoll-Erweiterungsweise empfängt, oder

Senden der BIER-Informationen an andere Schnittstellen mit Ausnahme einer Schnittstelle, die einen kürzesten Weg zu dem ersten Knoten in den anderen Knoten aufweist, gemäß einem Babelroute-Berechnungsergebnis.


 
7. Verfahren nach einem der Ansprüche 1 bis 6, wobei die Babelprotokoll-Erweiterungsweise eine Typlängenwert(TLV, Type Length Value)-Weise und eine Teil-TLV-Weise umfasst.
 
8. Verfahren nach einem der Ansprüche 1 bis 6, wobei die in der BIER-Weise eingekapselte Nachricht Folgendes umfasst: eine Nachricht, die von einem Bier-Header eingekapselt ist, und/oder eine Nachricht, die in einer MPLS+BIER-Weise eingekapselt ist.
 
9. Knoten, Folgendes umfassend:

ein Empfangsgerät (152), das dafür konfiguriert ist, BIER(Bit Indexed Explicit Replication)-Informationen zu empfangen, die von anderen Knoten mit Ausnahme des Knotens in einem Distanzvektor-Routingprotokoll(Babel)-Netzwerk in einer Babelprotokoll-Erweiterungsweise gesendet werden, wobei die BIER-Informationen zum Erfassen eines BIER-Weiterleitungseintrags verwendet werden,

einen Prozessor (154), der dafür konfiguriert ist, den BIER-Weiterleitungseintrag gemäß den BIER-Informationen zu erfassen, und

ein Sendegerät (156), das dafür konfiguriert ist, eine Nachricht, die in einer BIER-Weise eingekapselt ist, gemäß dem BIER-Weiterleitungseintrag an andere Knoten zu senden.


 
10. Knoten nach Anspruch 9, wobei die BIER-Informationen Bitweiterleitungsrouter-Kennungs(BFR-ID, Bit Forwarding Router Identifier)-Informationen eines Knotens und/oder BFR-Präfixinformationen des Knotens umfassen.
 
11. Knoten nach Anspruch 10, wobei die BIER-Informationen ferner eines oder mehreres des Folgenden umfassen: eine Teilbereichskennung (Teilbereichs-ID), eine Einstellungskennung (SI, Set Identifier), eine Bitfolgelänge (BSL, Bit String Length), eine Topologiekennung (Topologie-ID), eine Einkapselungsweise, Algorithmusinformationen, ein MPLS(Multiprotocol Label Switching)-Label und Tunneleinkapselungsinformationen.
 
12. Knoten nach Anspruch 11, wobei der Prozessor (154) ferner dafür konfiguriert ist, den BIER-Weiterleitungseintrag gemäß den BIER-Informationen und einem von einem Standarddistanzvektor-Routingalgorithmus und einem Kürzester-Weg-Zuerst(SPF Shortest Path First)-Algorithmus zu erfassen.
 
13. Knoten nach Anspruch 9, wobei das Sendegerät (156) ferner dafür konfiguriert ist, die BIER-Informationen und BIER-Informationen des Knotens an die anderen Knoten mit Ausnahme des Knotens in dem Babel-Netzwerk in der Babelprotokoll-Erweiterungsweise zu senden.
 
14. Knoten nach Anspruch 13, wobei das Sendegerät (156) ferner dafür konfiguriert ist, die BIER-Informationen an alle anderen Schnittstellen mit Ausnahme einer Schnittstelle, welche die BIER-Informationen in den anderen Knoten in der Babelprotokoll-Erweiterungsweise empfängt, zu senden, oder gemäß einem Babelroute-Berechnungsergebnis die BIER-Informationen an andere Schnittstellen mit Ausnahme einer Schnittstelle, die einen kürzesten Weg zu dem Knoten in den anderen Knoten aufweist, zu senden.
 
15. Knoten nach einem der Ansprüche 9 bis 14, wobei die Babelprotokoll-Erweiterungsweise eine Typlängenwert(TLV, Type Length Value)-Weise und eine Teil-TLV-Weise umfasst
oder
wobei die Nachricht, die in der BIER-Weise eingekapselt ist Folgendes umfasst: eine Nachricht, die von einem BIER-Header eingekapselt ist, oder eine Nachricht, die in einer MPLS+BIER-Weise eingekapselt ist.
 


Revendications

1. Procédé, mis en œuvre par un nœud, pour une transmission de messages, comprenant les étapes ci-dessous consistant à :

recevoir (S202) des informations de réplication explicite indexée sur les bits, BIER, qui sont envoyées par d'autres nœuds, à l'exception d'un premier nœud, dans un réseau de protocole de routage vectoriel à distance, Babel, selon un mode d'extension de protocole de routage Babel, dans lequel les informations de réplication BIER sont utilisées pour acquérir une entrée d'acheminement de réplication BIER ;

acquérir (S204) l'entrée d'acheminement de réplication BIER selon les informations de réplication BIER ; et

envoyer (S206) un message encapsulé selon un mode de réplication BIER auxdits autres nœuds selon l'entrée d'acheminement de réplication BIER.


 
2. Procédé selon la revendication 1, dans lequel les informations de réplication BIER comprennent au moins l'une des informations parmi des informations d'identifiant de routeur d'acheminement de bits, BFR-id, d'un nœud, et des informations de préfixe de routeur d'acheminement de bits, BFR-Prefix, du nœud.
 
3. Procédé selon la revendication 2, dans lequel les informations de réplication BIER comprennent en outre un ou plusieurs des éléments suivants : un identifiant de sous-domaine, Sub-domain-id, un identifiant d'ensemble, SI, une longueur de chaîne de bits, BSL, un identifiant de topologie, Topology-id, un mode d'encapsulation, des informations d'algorithme, une étiquette de commutation multiprotocole par étiquette, MPLS, et des informations d'encapsulation de tunnel.
 
4. Procédé selon la revendication 3, dans lequel l'étape d'acquisition (S204) de l'entrée d'acheminement de réplication BIER selon les informations de réplication BIER comprend l'étape ci-dessous consistant à :
acquérir l'entrée d'acheminement de réplication BIER selon les informations de réplication BIER et l'un ou l'autre parmi un algorithme de routage vectoriel à distance par défaut et un algorithme de premier itinéraire le plus court (SPF, Shortest Path First).
 
5. Procédé selon la revendication 1, dans lequel, après l'étape de réception (S202) des informations de réplication BIER qui sont envoyées par lesdits autres nœuds, à l'exception du premier nœud dans le réseau de protocole Babel, selon le mode d'extension de protocole de routage Babel, le procédé comprend en outre l'étape ci-dessous consistant à :
envoyer les informations de réplication BIER et des informations de réplication BIER du premier nœud auxdits autres nœuds, à l'exception du premier nœud dans le réseau de protocole Babel, selon le mode d'extension de protocole de routage Babel.
 
6. Procédé selon la revendication 5, dans lequel l'étape d'envoi des informations de réplication BIER auxdits autres nœuds, à l'exception du premier nœud dans le réseau de protocole Babel, selon le mode d'extension de protocole de routage Babel, comprend les étapes ci-dessous consistant à :

envoyer les informations de réplication BIER à toutes les autres interfaces, à l'exception d'une interface recevant les informations de réplication BIER dans lesdits autres nœuds, selon le mode d'extension de protocole de routage Babel ; ou

selon un résultat de calcul d'itinéraire Babel, envoyer les informations de réplication BIER à d'autres interfaces, à l'exception d'une interface présentant un itinéraire le plus court vers le premier nœud dans lesdits autres nœuds.


 
7. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel le mode d'extension de protocole de routage Babel comprend au moins un mode parmi un mode de valeur de longueur de type, TLV, et un mode de sous-TLV.
 
8. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel le message encapsulé selon le mode de réplication BIER comprend : un message encapsulé par un en-tête de réplication BIER, ou un message encapsulé selon un mode MPLS+BIER.
 
9. Nœud, comprenant :

un dispositif de réception (152), qui est configuré de manière à recevoir des informations de réplication explicite indexée sur les bits, BIER, qui sont envoyées par d'autres nœuds, à l'exception du nœud dans un réseau de protocole de routage vectoriel à distance, Babel, selon un mode d'extension de protocole de routage Babel, dans lequel les informations de réplication BIER sont utilisées pour acquérir une entrée d'acheminement de réplication BIER ;

un processeur (154), qui est configuré de manière à acquérir l'entrée d'acheminement de réplication BIER selon les informations de réplication BIER ; et

un dispositif d'envoi (156), qui est configuré de manière à envoyer un message encapsulé selon un mode de réplication BIER auxdits autres nœuds selon l'entrée d'acheminement de réplication BIER.


 
10. Nœud selon la revendication 9, dans lequel les informations de réplication BIER comprennent au moins l'une des informations parmi des informations d'identifiant de routeur d'acheminement de bits, BFR-id, d'un nœud, et des informations de préfixe de routeur d'acheminement de bits, BFR-Prefix, du nœud.
 
11. Nœud selon la revendication 10, dans lequel les informations de réplication BIER comprennent en outre un ou plusieurs des éléments suivants : un identifiant de sous-domaine, Sub-domain-id, un identifiant d'ensemble, SI, une longueur de chaîne de bits, BSL, un identifiant de topologie, Topology-id, un mode d'encapsulation, des informations d'algorithme, une étiquette de commutation multiprotocole par étiquette, MPLS, et des informations d'encapsulation de tunnel.
 
12. Nœud selon la revendication 11, dans lequel le processeur (154) est en outre configuré de manière à acquérir l'entrée d'acheminement de réplication BIER selon les informations de réplication BIER et l'un ou l'autre parmi un algorithme de routage vectoriel à distance par défaut et un algorithme de premier itinéraire le plus court (SPF, Shortest Path First).
 
13. Nœud selon la revendication 9, dans lequel le dispositif d'envoi (156) est en outre configuré de manière à envoyer les informations de réplication BIER et des informations de réplication BIER du nœud auxdits autres nœuds, à l'exception du nœud dans le réseau de protocole Babel, selon le mode d'extension de protocole de routage Babel.
 
14. Nœud selon la revendication 13, dans lequel le dispositif d'envoi (156) est en outre configuré de manière à envoyer les informations de réplication BIER à toutes les autres interfaces, à l'exception d'une interface recevant les informations de réplication BIER dans lesdits autres nœuds, selon le mode d'extension de protocole de routage Babel, ou, selon un résultat de calcul d'itinéraire Babel, à envoyer les informations de réplication BIER à d'autres interfaces, à l'exception d'une interface présentant un itinéraire le plus court vers le nœud dans lesdits autres nœuds.
 
15. Nœud selon l'une quelconque des revendications 9 à 14, dans lequel le mode d'extension de protocole de routage Babel comprend au moins un mode parmi un mode de valeur de longueur de type, TLV, et un mode de sous-TLV, ou
dans lequel le message encapsulé selon le mode de réplication BIER comprend : un message encapsulé par un en-tête de réplication BIER, ou un message encapsulé selon un mode MPLS+BIER.
 




Drawing


























Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description