WO2021036482A1 - 一种实现报文传输的方法及装置 - Google Patents

一种实现报文传输的方法及装置 Download PDF

Info

Publication number
WO2021036482A1
WO2021036482A1 PCT/CN2020/099019 CN2020099019W WO2021036482A1 WO 2021036482 A1 WO2021036482 A1 WO 2021036482A1 CN 2020099019 W CN2020099019 W CN 2020099019W WO 2021036482 A1 WO2021036482 A1 WO 2021036482A1
Authority
WO
WIPO (PCT)
Prior art keywords
subdomain
node
message
bier
tunnel
Prior art date
Application number
PCT/CN2020/099019
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 南京中兴软件有限责任公司
Publication of WO2021036482A1 publication Critical patent/WO2021036482A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • 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/74—Address processing for routing

Definitions

  • This application relates to, but is not limited to, Internet communication technology, in particular to a method and device for realizing message transmission.
  • BIER Bit Index Explicit Replication
  • the relevant standards define in detail the detailed calculation process of the unicast protocol in a BIER subdomain. However, if the BIER is in a different subdomain (Subdomain), BIER intercommunication cannot be realized.
  • This application provides a method and device for realizing message transmission, which can realize BIER intercommunication in different subdomains.
  • This application provides a method for realizing message transmission, including: a node receives a message carrying subdomain information, and determines that the subdomain information includes a subdomain that the node does not belong to; the node creates a subdomain route, and the outgoing direction is directed A boundary node tunnel, where the boundary node is a node that sends the message.
  • the present application also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute any of the foregoing methods for implementing message transmission.
  • the present application also provides a device for implementing message transmission, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory: Steps of the method.
  • This application further provides an apparatus for implementing message transmission, including: a confirmation module and a first processing module; wherein the confirmation module is configured to receive a message carrying subdomain information, and determine that the subdomain information includes the node itself A subdomain that does not belong to; the first processing module is set to create a subdomain route, and the outgoing direction is a tunnel pointing to a border node, where the border node is a node that sends the message.
  • the subdomain information that the node itself does not belong to is carried in the message received by the node, which indicates the subdomain ID information of the subdomain to which the border node itself belongs to which the message is sent.
  • Create a corresponding BIER subdomain route for the subdomains, and the outgoing direction is a tunnel to the border node that sends and receives the message, which realizes the intercommunication of BIER in different subdomains.
  • FIG. 1 is a flowchart of a method for implementing message transmission in this application
  • FIG. 2 is a schematic diagram of an embodiment of an extension of the sub_sub_tlv structure of the ISIS protocol of this application;
  • FIG. 3 is a schematic diagram of an embodiment of the OSPF protocol extension sub_sub_tlv structure of this application;
  • FIG. 4 is a schematic diagram of a network of an embodiment of applying a BIER cross-subdomain
  • FIG. 5 is a schematic diagram of an embodiment of implementing message transmission across multiple BIER subdomain function networks in this application;
  • FIG. 6 is a schematic diagram of the composition structure of an apparatus for implementing message transmission in this application.
  • the computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in a computer readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices.
  • computer-readable media does not include non-transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.
  • Fig. 1 is a flowchart of a method for implementing message transmission in this application, as shown in Fig. 1, including:
  • Step 100 The node receives a message carrying subdomain information, and determines that the subdomain information includes subdomains that the node does not belong to.
  • the method before this step, the method further includes:
  • the border node sending the message carries the subdomain identification (ID) information of the subdomain to which the border node itself belongs. That is, the subdomain information that the node itself does not belong to carried in the message is included in the subdomain ID information of the subdomain to which the border node itself belongs to which the message is sent.
  • ID subdomain identification
  • carrying the subdomain ID information of the subdomain to which the border node itself belongs in the message includes:
  • a subdomain boundary type-length-value (tlv) structure, or sub-tlv (sub_tlv) structure, or sub-sub-tlv (sub_sub_tlv) structure, or an attribute structure is added for carrying and sending The subdomain ID information of the subdomain that the boundary node of the message can reach.
  • the unicast protocol message may include, for example, an Intermediate System to Intermediate System (ISIS, Intermediate System to Intermediate System) protocol message, and Open Shortest Path First (OSPF, Open Shortest Path First) Protocol messages, etc., Border Gateway Protocol (BGP, Border Gateway Protocol), and Fat Tree Routing Protocol (RIFT, Fat Tree Routing).
  • ISIS Intermediate System to Intermediate System
  • OSPF Open Shortest Path First
  • BGP Border Gateway Protocol
  • RIFT Fat Tree Routing Protocol
  • the message is carried in the advertised route or prefix, and specifically includes:
  • the border node adopts local policies (for example: configuring bier subdomain border 1 2, indicating that the device is a border device of BIER subdomain 1 and subdomain 2) or automatically discovers that it belongs to different BIER subdomains at the same time, then it is carried in the advertised route or prefix The expanded message.
  • local policies for example: configuring bier subdomain border 1 2, indicating that the device is a border device of BIER subdomain 1 and subdomain 2
  • the boundary node is a device that enables the BIER function.
  • the border node may include routers, switches, or other devices or virtual devices that support the BIER forwarding function.
  • Boundary nodes can also be called BIER nodes.
  • Step 101 The node creates a subdomain route, and the outgoing direction is a tunnel pointing to a border node, where the border node is a node that sends the message.
  • Step 101 may include:
  • the key is the destination subdomain ID, such as the subdomain ID of the subdomain to which the node itself does not belong.
  • the outgoing direction is the tunnel to the border node that sends the received message.
  • the created tunnel may be a BIER tunnel in the common subdomain of the node and the boundary node (in this case, the BIER node) that sends the received message, and the BIER outgoing direction is the one that sends the received message.
  • the boundary node in this case, the BIER node
  • the BIER outgoing direction is the one that sends the received message.
  • the created tunnel may also be a unicast tunnel, and the destination address of the unicast tunnel is the prefix Prefix of the boundary node that sends the received message.
  • the node is a non-BIER node, that is, a node that does not enable the BIER function, and step 101 may include:
  • the present application further includes:
  • the node replaces the route or prefix with a route or prefix local to the node through an existing rule or a local policy, and the subdomain ID carried is the subdomain ID of the received message and the subdomain ID of the node itself.
  • the existing rules or local policies mentioned here are related to the regional area deployment and policies of the IGP, which are not limited in this application.
  • the subdomain ID is carried in the prefix tlv, and the border node can choose not to be directly generalized.
  • the received prefix tlv is flooded, but the subdomain ID is placed in the bier prefix tlv of the border node itself, and the prefix tlv received is continued to be flooded.
  • the subdomain information that the node itself does not belong to in the message received by the node of this application indicates the subdomain ID information of the subdomain to which the border node itself belongs, and is passed as the subdomain to which the node does not belong.
  • the domain creates the corresponding BIER subdomain route, and the outgoing direction is the tunnel to the boundary node that sends the received message, which realizes the intercommunication of BIER in different subdomains.
  • the method for implementing message transmission in this application further includes:
  • the node When the node receives the multicast traffic, if the multicast specifies the BIER outgoing direction of the remote subdomain, the BIER header is encapsulated, and then a layer of outer header is encapsulated according to the outgoing tunnel of the remote subdomain route and forwarded to the border node.
  • the node is a BIER node
  • a BFIR incoming node of the BIER domain
  • the method further includes:
  • the node is a non-BIER node, that is, a node that does not enable the BIER function, and when the non-BIER node forwards a multicast message, the method further includes:
  • the node is a BIER subdomain boundary node, and after receiving the above message, it further includes:
  • An embodiment of the present invention also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute any of the foregoing methods for implementing message transmission.
  • An embodiment of the present invention also provides a device for implementing message transmission, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory: it is used to execute any of the foregoing implementation messages. The steps of the method of transmission.
  • Fig. 2 is a schematic diagram of an embodiment of an extension of the sub_sub_tlv structure of the ISIS protocol of this application.
  • a sub-domain boundary sub-subtype-length-value (sub_sub_tlv) structure is added.
  • the Type field is to be determined
  • the Length field is a variable length
  • the length is related to the number of sub-domain IDs (Sub-domain IDs).
  • FIG. 3 is a schematic diagram of an embodiment of the application of the OSPF protocol to extend the sub-tlv structure.
  • the sub-domain boundary sub-type-length-value (sub_tlv) structure is added.
  • the Type field is to be determined
  • the Length field is variable length, and the length is related to the number of subdomain ids.
  • the ISIS protocol extension sub-tlv structure shown in Figure 2 as an example, when the ISIS protocol discovers that it belongs to multiple subdomains at the same time, when the prefix tlv is issued, it carries the bier sub tlv and the above sub-domain boundary sub_sub_tlv, and the prefix is The configured BIER prefix;
  • the sub-domain boundary sub_sub_tlv only carries the subdomain id of the boundary.
  • the prefix tlv is leaked to other domains through a policy, and the sub-domain boundary sub_sub_tlv option is carried.
  • Fig. 4 is a schematic diagram of a network of an embodiment of applying a BIER cross-subdomain. Combined with the network shown in Fig. 4, in the first embodiment, the subdomain boundary sub_sub_tlv sent by the node R2 carries Subdomain id 1 and Subdomain id 2.
  • node R1 After node R1 receives the above message, it creates a subdomain route to Subdomain id 2.
  • the outgoing direction is a unicast tunnel to node R2 or a BIER tunnel with the prefix of Subdomain id 1 of node R2 as the BFER.
  • the tunnel type can pass Configuration control.
  • Node R1 receives the multicast traffic, and finds that the outgoing direction of the traffic is node R3 of subdomain 2 through the multicast protocol or the controller, then encapsulates the BIER header according to the BFER of subdomain 2; because node R1 itself is not in subdomain 2, The subdomain route created above will be searched, and the corresponding outer layer encapsulation will be carried out according to its outgoing direction to deliver the message; for node R2, after receiving the message from node R1, the outer header will be stripped to obtain subdomain 2 The BIER message is then forwarded further.
  • the subdomain boundary node R2 can be made to send an ISIS message carrying the subdomain boundary sub_sub_tlv as in the first embodiment, but the message only includes Subdomain id 2, and
  • the difference in the first embodiment is that only unicast tunnel encapsulation is supported. I won’t repeat them here.
  • FIG. 5 is a schematic diagram of an embodiment of implementing message transmission across multiple BIER subdomain function networks in this application.
  • node R3 publishes a prefix tlv, which carries bier subtlv and the aforementioned subdomain boundary sub_sub_tlv, and sub_sub_tlv carried It includes Subdomain id 2 and Subdomain id 3, and the prefix is the BIER prefix configured locally on node R3.
  • node R2 After node R2 receives the above message, it sends the prefix tlv to node R1.
  • the prefix is the BIER prefix configured locally by node R2, which carries bier sub tlv and the aforementioned subdomain boundary sub_sub_tlv.
  • the carried sub_sub_tlv includes Subdomain id 1, Subdomain id 2, and Subdomain id 3;
  • Node R2 creates a subdomain routing table of Subdomain id 3 at the same time, and the outgoing direction is the BIER tunnel with node R3 as the BFER or the unicast tunnel pointing to node R3.
  • node R1 After node R1 receives the prefix tlv sent from node R2, it creates a subdomain routing table of Subdomain id 2 and Subdomain id 3, and the outgoing direction is the BIER tunnel of node R2 or the unicast tunnel pointing to R2. Other implementations will not be repeated here.
  • FIG. 6 is a schematic diagram of the composition structure of an apparatus for implementing message transmission in this application. As shown in FIG. 6, it at least includes: a confirmation module and a first processing module; wherein,
  • the confirmation module is configured to receive a message carrying subdomain information, and determine that the subdomain information includes a subdomain to which the node itself does not belong;
  • the first processing module is configured to create a subdomain route, and the outgoing direction is a tunnel pointing to a border node, where the border node is a node that sends the message.
  • the message carries the subdomain ID information of the subdomain to which the border node sending the message belongs.
  • a subdomain boundary type-length-value tlv structure, or sub-tlv (sub_tlv) structure, or sub-sub-tlv (sub_sub_tlv) structure, or an attribute structure can be added, using It carries the subdomain ID information of the subdomain that can be reached by the boundary node itself that sends the message.
  • the unicast protocol message may include, for example, an Intermediate System to Intermediate System (ISIS, Intermediate System to Intermediate System) protocol message, and Open Shortest Path First (OSPF, Open Shortest Path First) Protocol messages, Border Gateway Protocol (BGP, Border Gateway Protocol), Fat Tree Routing Protocol (RIFT, Fat Tree Routing), etc.
  • ISIS Intermediate System to Intermediate System
  • OSPF Open Shortest Path First
  • Border Gateway Protocol Border Gateway Protocol
  • RIFT Fat Tree Routing Protocol
  • the message is carried in the advertised route or prefix.
  • the boundary node that sends the message is a device that enables the BIER function.
  • the border node may include routers, switches, or other devices or virtual devices that support the BIER forwarding function.
  • Boundary nodes can also be called BIER nodes.
  • the node is a BIER node
  • the first processing module is specifically set as:
  • the corresponding BIER subdomain route is generated for the subdomain to which the device to which the first processing module belongs does not belong to, the key is the destination subdomain ID, and the outgoing is the tunnel to the border node that sends the received message.
  • the created tunnel may be a BIER tunnel in the common subdomain of the device to which the first processing module belongs and the boundary node (in this case, the BIER node) that sends the received message, and its BIER outgoing direction is sending and receiving Prefix of the boundary node of the message;
  • the created tunnel may also be a unicast tunnel, and the destination address of the unicast tunnel is the prefix Prefix of the boundary node that sends the received message.
  • the node is a non-BIER node, that is, a node that does not enable the BIER function, and the first processing module is specifically set as:
  • the corresponding BIER subdomain route is generated for the subdomain to which the device to which the first processing module belongs, the key is the destination subdomain ID, and the outgoing is a unicast tunnel to the border node that sends the received message.
  • the first processing module is further configured as:
  • the carried subdomain ID is the subdomain ID of the received message and the device to which the first processing module belongs. The ID of the subdomain.
  • the apparatus for implementing message transmission further includes a second processing module, which is configured to:
  • the multicast When multicast traffic is received, if the multicast specifies the BIER outgoing direction of the remote subdomain, the BIER header is encapsulated, and then a layer of outer header is encapsulated according to the outgoing tunnel of the remote subdomain route, and then forwarded to the border node.
  • the device to which the second processing module belongs is a BIER node, and when a multicast packet is forwarded at the BFIR (the ingress node of the BIER domain) node, the second processing module is further set to:
  • the device to which the second processing module belongs is a non-BIER node, that is, a node that does not enable the BIER function.
  • the second processing module is further set to:
  • the device to which the second processing module belongs is the BIER subdomain boundary node. After receiving the above message, the second processing module is further set to:
  • This application also provides a node, including any one of the above-mentioned devices for realizing message transmission.
  • the method and device for implementing message transmission provided by the embodiments of the present invention have the following beneficial effects: the subdomain information that the node does not belong to is carried in the message received by the node, indicating that the message is sent The subdomain ID information of the subdomain to which the border node itself belongs, and by creating a corresponding BIER subdomain route for the subdomain to which the node itself does not belong, the outgoing direction is the tunnel to the border node that sends the received message. Interoperability in different subdomains.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种实现报文传输的方法及装置，在本申请中，节点收到的报文中携带的节点自身不属于的子域信息，表明了发送所述报文的边界节点自身属于的子域的子域ID信息，并通过为节点自身不属于的子域创建相应BIER子域路由，出向为到达发送接收到的报文的边界节点的隧道，实现了BIER在不同的子域中互通。

Description

一种实现报文传输的方法及装置 技术领域
本申请涉及但不限于互联网通信技术，尤指一种实现报文传输的方法及装置。
背景技术
互联网协议(IP)组播转发技术之后，基于位索引显式复制(BIER，Bit Index Explicit Replication)技术慢慢开始发展，BIER是一种新的用于构建组播转发路径的技术，该技术提供了一种不需要构建组播分发树的组播技术架构。
相关标准详细定义了在一个BIER子域中，单播协议详细的算路过程，但是，如果BIER在不同的子域(Subdomain)中，是不能实现BIER互通的。
针对相关技术中存在的上述问题，目前尚未提出有效的解决方案。
发明内容
本申请提供一种实现报文传输的方法及装置，能够实现BIER在不同的子域中互通。
本申请提供了一种实现报文传输的方法，包括：节点接收携带有子域信息的报文，并确定子域信息包括有节点自身不属于的子域；节点创建子域路由，出向为指向边界节点的隧道，其中，边界节点为发送所述报文的节点。
本申请还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项所述的实现报文传输的方法。
本申请又提供了一种实现报文传输的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述任一 项所述的实现报文传输的方法的步骤。
本申请再提供了一种实现报文传输的装置，包括：确认模块、第一处理模块；其中，确认模块，设置为接收携带有子域信息的报文，并确定子域信息包括有节点自身不属于的子域；第一处理模块，设置为创建子域路由，出向为指向边界节点的隧道，其中，边界节点为发送所述报文的节点。
本申请中，节点收到的报文中携带的节点自身不属于的子域信息，表明了发送所述报文的边界节点自身属于的子域的子域ID信息，并通过为节点自身不属于的子域创建相应BIER子域路由，出向为到达发送接收到的报文的边界节点的隧道，实现了BIER在不同的子域中互通。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为本申请实现报文传输的方法的流程图；
图2为本申请ISIS协议扩展sub_sub_tlv结构的实施例的示意图；
图3为本申请OSPF协议扩展sub_sub_tlv结构的实施例的示意图；
图4为本申请BIER跨子域的实施例的网络示意图；
图5为本申请跨多个BIER子域功能的网络实现报文传输的实施例的示意图；
图6为本申请实现报文传输的装置的组成结构示意图。
具体实施方式
在本申请一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
图1为本申请实现报文传输的方法的流程图，如图1所示，包括：
步骤100：节点接收携带有子域信息的报文，并确定子域信息包括有节点自身不属于的子域。
在一种示例性实例中，本步骤之前还包括：
发送所述报文的边界节点在所述报文中携带边界节点自身属于的子域的子域标识(ID)信息。也就是说，报文中携带的节点自身不属于的子域信息包括在发送所述报文的边界节点自身属于的子域的子域ID信息中。
在一种示例性实例中，在所述报文中携带边界节点自身属于的子域的 子域ID信息，包括：
通过扩展单播协议报文类型，增加一子域边界类型-长度-值(tlv)结构、或子tlv(sub_tlv)结构、或子子tlv(sub_sub_tlv)结构、或一属性结构，用于携带发送所述报文的边界节点自身能够到达的子域的子域ID信息。
在一种示例性实例中，所述单播协议报文可以包括如：中间系统到中间系统(ISIS，Intermediate System to Intermediate System)协议报文、开放式最短路径优先(OSPF，Open Shortest Path First)协议报文等、边界网关协议(BGP，Border Gateway Protocol)、胖树路由协议(RIFT，Fat Tree Routing)。
在一种示例性实例中，所述报文携带在发布的路由或前缀中，具体包括：
如果边界节点通过本地策略(比如：配置bier subdomain border 1 2，表示设备是BIER子域1和子域2的边界设备)或自动发现自身同时属于不同BIER子域，那么，在发布的路由或前缀携带所述扩展后的报文。
在一种示例性实例中，所述边界节点为使能BIER功能的设备。可选地，边界节点可以包括如路由器、交换机或其他支持BIER转发功能的设备或虚拟设备。边界节点也可以称为BIER节点。
步骤101：节点创建子域路由，出向为指向边界节点的隧道，其中，边界节点为发送所述报文的节点。
在一种示例性实例中，所述节点为BIER节点，节点检查发现自身不同时属于收到的报文通告的子域，步骤101可以包括：
为节点自身不属于的子域产生相应BIER子域路由，关键字为目的子域ID如节点自身不属于的子域的子域ID，出向为到达发送接收到的报文的边界节点的隧道。
在一种示例性实例中，创建的隧道可以是本节点和发送接收到的报文的边界节点(此时为BIER节点)共同子域的BIER隧道，其BIER出向 为发送接收到的报文的边界节点的前缀Prefix；
在一种示例性实例中，创建的隧道也可以是一条单播隧道，单播隧道目的地址为发送接收到的报文的边界节点的前缀Prefix。
在一种示例性实例中，所述节点为非BIER节点即未使能BIER功能的节点，步骤101可以包括：
为节点自身不属于的子域产生相应BIER子域路由，关键字为目的子域ID，出向为到达发送接收到的报文的边界节点的单播隧道。
在一种示例性实例中，在步骤101之前或之后，本申请还包括：
所述节点通过既有规则或本地策略，将路由或前缀替换为节点本地的路由或前缀，携带的子域ID为收到的报文的子域ID和节点自身的子域ID。需要说明的是，这里提到的既有规则或本地策略与IGP的区域area部署和策略相关，本申请并不做限定，比如：子域ID携带在前缀tlv中，边界节点可以选择不直接泛洪收到的前缀tlv，而是用将子域ID放在边界节点自身的bier prefix tlv中发布出去；或者，继续泛洪收到的前缀tlv等。
本申请节点收到的报文中携带的节点自身不属于的子域信息，表明了发送所述报文的边界节点自身属于的子域的子域ID信息，并通过为节点自身不属于的子域创建相应BIER子域路由，出向为到达发送接收到的报文的边界节点的隧道，实现了BIER在不同的子域中互通。
在一种示例性实例中，本申请实现报文传输的方法，还包括：
节点收到组播流量，如果组播指定远端子域的BIER出向，则封装BIER头，再根据所述远端子域路由的出向隧道封装一层外层头后，转发到边界节点。
在一种示例性实例中，所述节点为BIER节点，在BFIR(BIER域的入节点)节点，转发组播报文时，还包括：
首先封装远端BIER子域的BIER头作为内层BIER封装，发现本设备没有此子域的BIER转发表，则查找BIER子域路由，外层封装隧道， 投递到BIER子域边界节点。
在一种示例性实例中，所述节点为非BIER节点即未使能BIER功能的节点，非BIER节点转发组播报文时，还包括：
可以通过策略选择通过BIER子域路由转发，方法和上述步骤相同。
在一种示例性实例中，所述节点为BIER子域边界节点，收到上述报文后，还包括：
剥掉外层隧道封装，通过内层BIER正常转发。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项所述的实现报文传输的方法。
本发明实施例还提供一种实现报文传输的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述任一项所述的实现报文传输的方法的步骤。
图2为本申请ISIS协议扩展sub_sub_tlv结构的实施例的示意图，如图2所示，增加子域边界子子类型-长度-值(sub_sub_tlv)结构。其中，Type字段待定，Length字段为变长，长度和其子域标识(Sub-domain id)个数相关。
图3为本申请OSPF协议扩展sub sub tlv结构的实施例的示意图，如图3所示，增加子域边界子类型-长度-值(sub_tlv)结构。其中，Type字段待定，Length字段为变长，长度和其Subdomain id个数相关。
以图2所示的ISIS协议扩展sub sub tlv结构为例，当ISIS协议发现自身同时属于多个子域(Subdomain)，则在发布前缀tlv时，携带bier sub tlv和上述子域边界sub_sub_tlv，前缀为配置的BIER prefix；
需要说明的是，本申请中可以通过本地策略控制自己是否能作为子域边界，如果不能不作为子域边界则不携带上述子域边界sub_sub_tlv选项。
如果通过本地配置控制自己作为某个或某几个子域边界，那么，子域 边界sub_sub_tlv仅携带自己作为边界的Subdomain id。可选地，在ISIS域边界，通过策略泄露前缀tlv到其他域，携带上述子域边界sub_sub_tlv选项。
图4为本申请BIER跨子域的实施例的网络示意图，结合图4所示的网络，在第一实施例中，节点R2发送的子域边界sub_sub_tlv中携带Subdomain id 1和Subdomain id 2。
这样，节点R1收到上述报文后，创建到Subdomain id 2的子域路由，出向为指向节点R2的单播隧道或以节点R2的Subdomain id 1的前缀作为BFER的BIER隧道，隧道类型可以通过配置控制。节点R1收到组播流量，通过组播协议或控制器发现流量的出向为子域2的节点R3，那么，封装按照子域2的BFER封装BIER头；由于节点R1自己不在子域2中，则会查找上述创建的子域路由，根据其出向进行相应外层封装后进行报文投递；对于节点R2，在收到来自节点R1的报文后，会剥掉外层头，得到子域2的BIER报文，然后再进一步转发。
仍以图4所示，假设网络中存在(非BIER节点)没有使能BIER功能的节点如节点R1；节点R2和节点R3使能了BIER功能，且属于子域2。那么，通过本地策略，在第二实施例中，可以使得子域边界节点R2发送携带如第一实施例中的子域边界sub_sub_tlv的ISIS报文，但是，报文中只包括Subdomain id 2，与第一实施例不同的是只支持单播隧道封装。其他这里不再赘述。
图5为本申请跨多个BIER子域功能的网络实现报文传输的实施例的示意图，如图5所示，节点R3发布前缀tlv，携带bier sub tlv和上述子域边界sub_sub_tlv，携带的sub_sub_tlv中包括Subdomain id 2和Subdomain id 3，前缀为节点R3本地配置的BIER prefix。
节点R2收到上述报文后，向节点R1发送前缀tlv，前缀为节点R2本地配置的BIER prefix，携带bier sub tlv和上述子域边界sub_sub_tlv，携带的sub_sub_tlv中包括Subdomain id 1、Subdomain id 2和Subdomain id 3； 节点R2同时创建Subdomain id 3的子域路由表，出向为BFER为节点R3的BIER隧道或指向节点R3的单播隧道。
节点R1收到来自节点R2发送的前缀tlv后，创建Subdomain id 2和Subdomain id 3的子域路由表，出向为BFER为节点R2的BIER隧道或指向R2的单播隧道。其他实现这里不再赘述。
图6为本申请实现报文传输的装置的组成结构示意图，如图6所示，至少包括：确认模块、第一处理模块；其中，
确认模块，设置为接收携带有子域信息的报文，并确定子域信息包括有节点自身不属于的子域；
第一处理模块，设置为创建子域路由，出向为指向边界节点的隧道，其中，边界节点为发送所述报文的节点。
在一种示例性实例中，在所述报文中携带有发送所述报文的边界节点自身属于的子域的子域ID信息。可选地，可以通过扩展单播协议报文类型，增加一子域边界类型-长度-值tlv结构、或子tlv(sub_tlv)结构、或子子tlv(sub_sub_tlv)结构、或一属性结构，用于携带发送所述报文的边界节点自身能够到达的子域的子域ID信息。
在一种示例性实例中，所述单播协议报文可以包括如：中间系统到中间系统(ISIS，Intermediate System to Intermediate System)协议报文、开放式最短路径优先(OSPF，Open Shortest Path First)协议报文、边界网关协议(BGP，Border Gateway Protocol)、胖树路由协议(RIFT，Fat Tree Routing)等。
在一种示例性实例中，所述报文携带在发布的路由或前缀中。
在一种示例性实例中，发送所述报文的边界节点为使能BIER功能的设备。可选地，边界节点可以包括如路由器、交换机或其他支持BIER转发功能的设备或虚拟设备。边界节点也可以称为BIER节点。
在一种示例性实例中，所述节点为BIER节点，第一处理模块具体设置为：
为第一处理模块所属装置自身不属于的子域产生相应BIER子域路由，关键字为目的子域ID，出向为到达发送接收到的报文的边界节点的隧道。
在一种示例性实例中，创建的隧道可以是第一处理模块所属装置和发送接收到的报文的边界节点(此时为BIER节点)共同子域的BIER隧道，其BIER出向为发送接收到的报文的边界节点的前缀Prefix；
在一种示例性实例中，创建的隧道也可以是一条单播隧道，单播隧道目的地址为发送接收到的报文的边界节点的前缀Prefix。
在一种示例性实例中，节点为非BIER节点即未使能BIER功能的节点，第一处理模块具体设置为：
为第一处理模块所属装置自身不属于的子域产生相应BIER子域路由，关键字为目的子域ID，出向为到达发送接收到的报文的边界节点的单播隧道。
在一种示例性实例中，第一处理模块还设置为：
通过既有规则或本地策略，将路由或前缀替换为第一处理模块所属装置本地的路由或前缀，携带的子域ID为收到的报文的子域ID和第一处理模块所属装置自身的子域ID。
在一种示例性实例中，实现报文传输的装置还包括第二处理模块，设置为：
收到组播流量，如果组播指定远端子域的BIER出向，则封装BIER头，再根据所述远端子域路由的出向隧道封装一层外层头后，转发到边界节点。
在一种示例性实例中，第二处理模块所属装置为BIER节点，在BFIR(BIER域的入节点)节点，转发组播报文时，第二处理模块，还设置为：
首先封装远端BIER子域的BIER头作为内层BIER封装，发现第二处理模块所属装置没有此子域的BIER转发表，则查找BIER子域路由，外层封装隧道，投递到BIER子域边界节点。
在一种示例性实例中，第二处理模块所属装置为非BIER节点即未使能BIER功能的节点，非BIER节点转发组播报文时，第二处理模块还设置为：
可以通过策略选择通过BIER子域路由转发。
在一种示例性实例中，第二处理模块所属装置为BIER子域边界节点，收到上述报文后，第二处理模块还设置为：
剥掉外层隧道封装，通过内层BIER正常转发。
本申请还提供一种节点，包括上述任一项实现报文传输的装置。
以上所述，仅为本发明的较佳实例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种实现报文传输的方法及装置具有以下有益效果：节点收到的报文中携带的节点自身不属于的子域信息，表明了发送所述报文的边界节点自身属于的子域的子域ID信息，并通过为节点自身不属于的子域创建相应BIER子域路由，出向为到达发送接收到的报文的边界节点的隧道，实现了BIER在不同的子域中互通。

Claims (18)

  1. 一种实现报文传输的方法，包括：
    节点接收携带有子域信息的报文，并确定子域信息包括有节点自身不属于的子域；
    节点创建子域路由，出向为指向边界节点的隧道，其中，边界节点为发送所述报文的节点。
  2. 根据权利要求1所述的方法，所述子域信息包括：子域表示ID信息；
    所述方法之前还包括：
    发送所述报文的边界节点在所述报文中携带边界节点自身所属子域的子域标识ID信息。
  3. 根据权利要求2所述的方法，其中，所述在所述报文中携带边界节点自身属于的子域的子域ID信息，包括：
    通过扩展单播协议报文类型，增加一子域边界类型-长度-值tlv结构、或子tlv结构、或子子tlv结构、或一属性结构，用于携带发送所述报文的边界节点自身能够到达的子域的子域ID信息。
  4. 根据权利要求3所述的方法，其中，所述单播协议报文包括：中间系统到中间系统ISIS协议报文、开放式最短路径优先OSPF协议报文、边界网关协议BGP、胖树路由协议RIFT。
  5. 根据权利要求1～4任一项所述的方法，其中，所述报文携带在发布的路由或前缀中。
  6. 根据权利要求1所述的方法，其中，所述节点为位索引显式复制BIER节点；所述创建子域路由，包括：
    为所述节点自身不属于的子域产生相应BIER子域路由，关键字为目的子域ID，出向为到达发送接收到的所述报文的边界节点的隧道。
  7. 根据权利要求6所述的方法，其中，所述隧道为所述节点和发送接收到的所述报文的边界节点共同子域的BIER隧道，其BIER出向 为发送接收到的所述报文的边界节点的前缀Prefix；或者，
    所述隧道也为单播隧道，单播隧道目的地址为发送接收到的所述报文的边界节点的前缀Prefix。
  8. 根据权利要求1所述的方法，其中，所述节点为非BIER节点；所述创建子域路由，包括：
    为所述节点自身不属于的子域产生相应BIER子域路由，关键字为目的子域ID，出向为到达发送接收到的所述报文的边界节点的单播隧道。
  9. 根据权利要求1、6或8所述的方法，所述创建子域路由之前或之后，还包括：
    所述节点将路由或前缀替换为所述节点本地的路由或前缀，携带的子域ID为收到的所述报文的子域ID和所述节点自身的子域ID。
  10. 根据权利要求1所述的方法，所述方法还包括：
    所述节点收到组播流量，如果组播指定远端子域的BIER出向，则封装BIER头，再根据所述子域路由的出向隧道封装一层外层头后，转发到边界节点。
  11. 根据权利要求10所述的方法，所述节点为BIER节点，转发所述组播报文时，还包括：
    封装所述远端BIER子域的BIER头作为内层BIER封装；
    发现所述节点没有该子域的BIER转发表，查找BIER子域路由，外层封装隧道，投递到BIER子域边界节点。
  12. 根据权利要求10所述的方法，所述节点为非BIER节点，转发组播报文时，还包括：通过策略选择通过BIER子域路由转发。
  13. 根据权利要求10所述的方法，所述节点为BIER子域边界节点，收到所述报文后，还包括：剥掉外层隧道封装，通过内层BIER正常转发。
  14. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～权利要求13任一项所述的实现报文传输的方法。
  15. 一种实现报文传输的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行权利要求1～权利要求13任一项所述的实现报文传输的方法的步骤。
  16. 一种实现报文传输的装置，包括：确认模块、第一处理模块；其中，
    确认模块，设置为接收携带有子域信息的报文，并确定子域信息包括有节点自身不属于的子域；
    第一处理模块，设置为创建子域路由，出向为指向边界节点的隧道，其中，边界节点为发送所述报文的节点。
  17. 根据权利要求16所述的装置，其中，发送所述报文的边界节点通过在所述报文中扩展单播协议报文类型，增加一子域边界类型-长度-值tlv结构、或子tlv结构、或子子tlv结构、或一属性结构，用于携带发送所述报文的边界节点自身能够到达的子域的子域ID信息。
  18. 根据权利要求16所述的装置，所述装置还包括第二处理模块，设置为收到组播流量，如果组播指定远端子域的BIER出向，则封装BIER头，再根据所述子域路由的出向隧道封装一层外层头后转发到边界节点。
PCT/CN2020/099019 2019-08-30 2020-06-29 一种实现报文传输的方法及装置 WO2021036482A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910815189.2A CN112448876B (zh) 2019-08-30 2019-08-30 一种实现报文传输的方法及装置
CN201910815189.2 2019-08-30

Publications (1)

Publication Number Publication Date
WO2021036482A1 true WO2021036482A1 (zh) 2021-03-04

Family

ID=74683227

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/099019 WO2021036482A1 (zh) 2019-08-30 2020-06-29 一种实现报文传输的方法及装置

Country Status (2)

Country Link
CN (1) CN112448876B (zh)
WO (1) WO2021036482A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114466008A (zh) * 2021-12-22 2022-05-10 天翼云科技有限公司 一种云边通信系统、方法、装置、电子设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115226038A (zh) * 2021-04-19 2022-10-21 中兴通讯股份有限公司 组播实现方法、路由设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102820977A (zh) * 2012-08-07 2012-12-12 福建星网锐捷网络有限公司 组播方法、装置及网络设备
US20170126481A1 (en) * 2015-11-01 2017-05-04 Cisco Technology, Inc. Bier forwarding validation
CN107592262A (zh) * 2016-07-07 2018-01-16 中兴通讯股份有限公司 报文发送方法和装置、报文跨域转发的网络架构
CN109756425A (zh) * 2017-11-07 2019-05-14 中国电信股份有限公司 组播转发方法、装置以及bfr

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106982157B (zh) * 2016-01-18 2020-11-20 中兴通讯股份有限公司 流量工程隧道建立方法和装置
CN108964940B (zh) * 2017-05-23 2022-04-29 中兴通讯股份有限公司 消息发送方法及装置、存储介质
CN109995634B (zh) * 2017-12-29 2021-08-17 中兴通讯股份有限公司 一种组播虚拟专用网络的承载方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102820977A (zh) * 2012-08-07 2012-12-12 福建星网锐捷网络有限公司 组播方法、装置及网络设备
US20170126481A1 (en) * 2015-11-01 2017-05-04 Cisco Technology, Inc. Bier forwarding validation
CN107592262A (zh) * 2016-07-07 2018-01-16 中兴通讯股份有限公司 报文发送方法和装置、报文跨域转发的网络架构
CN109756425A (zh) * 2017-11-07 2019-05-14 中国电信股份有限公司 组播转发方法、装置以及bfr

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114466008A (zh) * 2021-12-22 2022-05-10 天翼云科技有限公司 一种云边通信系统、方法、装置、电子设备及存储介质
CN114466008B (zh) * 2021-12-22 2023-10-13 天翼云科技有限公司 一种云边通信系统、方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN112448876A (zh) 2021-03-05
CN112448876B (zh) 2023-04-07

Similar Documents

Publication Publication Date Title
EP3836490B1 (en) Vpn cross-domain implementation method, device, and border node
EP3734906B1 (en) Method and device for bearing multicast virtual private network
WO2021063232A1 (zh) 建立bier转发表项的方法、装置和系统
EP3103230B1 (en) Software defined networking (sdn) specific topology information discovery
US11689452B2 (en) Method for forwarding service data, network device, and network system
WO2018228490A1 (zh) 组播跨域方法、装置、系统及计算机可读存储介质
US9178816B1 (en) Control plane messaging in all-active multi-homed ethernet virtual private networks
WO2019214589A1 (zh) 组播数据传输方法、相关装置及系统
US20170149685A1 (en) Address information publishing method and apparatus
WO2016058329A1 (zh) 业务传送方法及装置
CN109660460B (zh) Bier-te信息的处理方法、服务器及存储介质
WO2021196717A1 (zh) 组播流量传输方法、装置、通信节点及存储介质
WO2021143279A1 (zh) 段路由业务处理方法和装置、路由设备及存储介质
WO2021036482A1 (zh) 一种实现报文传输的方法及装置
CN113285876A (zh) 路由方法、路由装置及计算机可读存储介质
US20230308391A1 (en) Communication of policy changes in lisp-based software defined networks
WO2020244304A1 (zh) 路由信息发送的方法、路由选路的方法和装置
US20190334814A1 (en) Path establishment method and device, and network node
US20230081052A1 (en) Method and apparatus for sending multicast packet
US20160127269A1 (en) DUAL STACK ROOT BASED mLDP TREE MERGE
EP2985967B1 (en) Method, device, and computer storage medium for implementing ip address advertisement
WO2022042610A1 (zh) 信息处理方法、网络控制器、节点及计算机可读存储介质
CN112511444B (zh) 一种组播流量传输方法、装置、通信节点及存储介质
US20230353484A1 (en) PCE for BIER-TE Path
WO2024082617A1 (zh) 转发表索引的通告方法、节点及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20857550

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20857550

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20857550

Country of ref document: EP

Kind code of ref document: A1