WO2021164236A1 - 报文的处理方法及装置 - Google Patents

报文的处理方法及装置 Download PDF

Info

Publication number
WO2021164236A1
WO2021164236A1 PCT/CN2020/113799 CN2020113799W WO2021164236A1 WO 2021164236 A1 WO2021164236 A1 WO 2021164236A1 CN 2020113799 W CN2020113799 W CN 2020113799W WO 2021164236 A1 WO2021164236 A1 WO 2021164236A1
Authority
WO
WIPO (PCT)
Prior art keywords
mep
message
bfd
lookup table
session
Prior art date
Application number
PCT/CN2020/113799
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 WO2021164236A1 publication Critical patent/WO2021164236A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G06F16/9017—Indexing; Data structures therefor; Storage structures using directory or table look-up
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management

Definitions

  • the present invention relates to the field of computers, and in particular to a method and device for processing messages.
  • Multipoint BFD is defined in RFC8562 (Bidirectional Forwarding Detection (BFD) for Multipoint Networks).
  • BFD Bidirectional Forwarding Detection
  • Two roles are defined in RFC8562: Head and Tail.
  • the Head end The MEP (Maintenance End Point) on the MEP only sends and does not receive, while the MEP on the Tail only receives but does not send.
  • the essence of the protocol is to detect the unidirectional connectivity from Head to Tail.
  • RFC8562 BFD packets will only be sent from Head is sent to Tail, and only the connectivity of Head to Tail is detected in Tail, and Head does not need to know Tail. Therefore, according to the standard RFC8562, a Multipoint Tail session is found on the Tail side based on Source address and My Discriminator. If it is found, the Multipoint Tail MEP related state machine is updated; if it is not found, a new session is created or discarded.
  • RFC8563 Bidirectional Forwarding Detection (BFD) Multipoint Active Tails
  • Head may need to obtain the connection status of each Tail and introduce the standard. The standard proposes three methods :
  • the embodiment of the present invention provides a message processing method and device, so as to at least solve the problem in the related art that Tail MEP needs to create multiple MEP sessions for unicast BFD and multicast BFD.
  • a message processing method including: a first maintenance terminal node MEP receives a bidirectional forwarding detection BFD message; the first MEP detects a BFD message according to key fields in the BFD message Query the corresponding MEP session; in the case that the corresponding MEP session is not found, the first MEP sends the BFD message to the processor CPU, completes the BFD session learning in the CPU subsystem, and sends it to the chip
  • Two MEP look-up tables are used to issue KEY; wherein, the two MEP look-up tables include a first look-up table and a second look-up table; the first look-up table is used to look up a multicast BFD report that carries the first key field
  • the text sum searches the index of the first MEP, and the second look-up table is used to search the unicast BFD packet carrying the second key field and search the index of the first MEP; the first key and the index of the first MEP are searched.
  • the second key field is different; the first MEP detects
  • a message processing device which is applied to the MEP side of a first maintenance terminal node, and includes: a first receiving module configured to receive two-way forwarding detection BFD messages; a query module configured to In order to query the corresponding MEP session according to the key fields in the BFD message; the processing module is configured to send the BFD message to the processor CPU when the corresponding MEP session is not found, in the CPU subsystem
  • the BFD session learning is completed in the chip, and the KEY is issued to the two MEP lookup tables in the chip;
  • the lookup table includes a first lookup table and a second lookup table; the first lookup table is used to look up the A multicast BFD message with a key field and an index for searching the first MEP, and the second lookup table is used for searching for a unicast BFD message carrying the second key field and searching for the first MEP.
  • Index the first key is different from the second key field; the first lookup table and the second lookup table are
  • a computer-readable storage medium in which a computer program is stored, wherein, when the computer program is executed by a processor, processing of the message is realized Method steps.
  • an electronic device including a memory, a processor, and a computer program stored on the memory and running on the processor, and the processor executes the computer program When realizing the steps of the message processing method.
  • the first MEP when the corresponding MEP session is not found, sends a BFD message to the processor CPU, completes the BFD session learning in the CPU subsystem, and sends it to the two MEP lookup tables in the chip.
  • Send KEY where the lookup table includes a first lookup table and a second lookup table; the first lookup table is used to look up the multicast BFD message carrying the first key field and look up the index of the first MEP, and the second lookup table Used to search for unicast BFD packets carrying the second key field and search for the index of the first MEP; the first key is different from the second key field; the first lookup table and the second lookup table are associated with the same MEP session, That is to say, you can learn from the BFD message and find the corresponding MEP session, so that the Tail MEP can create a new session without finding the Multipoint Tail session to implement the function of the RFC8563 Tail end, which solves the problem of solving related problems in related technologies.
  • the lookup table includes a
  • Figure 1 is a flowchart of a message processing method according to an embodiment of the present invention
  • Fig. 2 is a schematic diagram of M-BFD message searching MEP table according to an embodiment of the present invention
  • Fig. 3 is a structural block diagram of a message processing device according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a message processing method according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps:
  • Step S102 the first maintenance terminal node MEP receives the bidirectional forwarding detection BFD message
  • Step S104 the first MEP queries the corresponding MEP session according to the key fields in the BFD message;
  • Step S106 In the case that the corresponding MEP session is not found, the first MEP sends a BFD message to the processor CPU, completes the BFD session learning in the CPU subsystem, and delivers to the two MEP lookup tables in the chip KEY; where the lookup table includes a first lookup table and a second lookup table; the first lookup table is used to look up the multicast BFD message carrying the first key field and the index of the first MEP, and the second lookup table is used To search for unicast BFD packets carrying the second key field and search for the index of the first MEP; the first key is different from the second key field; the first lookup table and the second lookup table are associated with the same MEP session.
  • the lookup table includes a first lookup table and a second lookup table
  • the first lookup table is used to look up the multicast BFD message carrying the first key field and the index of the first MEP
  • the second lookup table is used To search for unicast BFD packets carrying the second key field and
  • the first MEP sends a BFD message to the processor CPU, completes the BFD session learning in the CPU subsystem, and sends a message to the two chips in the chip.
  • the MEP lookup table delivers the KEY; where the lookup table includes a first lookup table and a second lookup table; the first lookup table is used to look up the multicast BFD message carrying the first key field and look up the index of the first MEP, The second lookup table is used to search for unicast and multicast BFD messages carrying the second key field and search for the index of the first MEP; the first key is different from the second key field; the first lookup table and the second lookup table Associating with the same MEP session, you can learn from the BFD message and find the corresponding MEP session, so that Tail MEP can create a new session without finding the Multipoint Tail session to implement the function of the RFC8563 Tail side, which solves the problem.
  • the related technology solves the problem in the related technology that Tail MEP needs to create multiple MEP sessions for unicast BFD and multicast BFD.
  • first MEP involved in this embodiment may be Tail MEP in specific application scenarios
  • second MEP may be Head MEP in specific application scenarios.
  • steps S102 to S106 in specific application scenarios may be:
  • the Multipoint Tail MEP session state machine is maintained in the chip, but the Multipoint Tail MEP session learning is performed in the Offload Engine, for example In the CPU subsystem, the following takes the CPU subsystem as an example for description;
  • a Multipoint Tail session is obtained on the Tail side based on Source address and My Discriminator. If it is found, the Multipoint Tail MEP related state machine is updated; if it is not found, a new session is created or discarded. In the specific application scenario of this embodiment, if the session is not found, the default entry will send the Multipoint BFD message to the CPU subsystem for learning, and the CPU subsystem will send it to the two MEP lookup tables in the chip.
  • Source address i.e. IPSa
  • My Discriminator corresponding to the first lookup table
  • the Session information mainly relates to the local Tail information:
  • My Discriminator represents the local Tail session identifier
  • IPSA represents the IP address of the local Tail
  • L4SrcPort represents the local Tail bound SourePort
  • Your Discriminator store the identifier of the remote Head
  • IPDA stores the IP address of the remote Head
  • L4DstPort equals 3784 to identify the port information used to reply to the Head
  • RXEn indicates whether the local Tail receives the BFD packet
  • TxEn indicates whether the local Tail is directed to the Head end Sending BFD packets and other information, as shown in Figure 2
  • M-BFD packets look up the MEP table.
  • the method of this embodiment further includes multiple ways for the first MEP to reply to the second MEP status information:
  • Manner 1 The first MEP receives a multicast message for querying the status of all the first MEPs sent by the second MEP; the first MEP replies to the second MEP in response to the multicast message with a BFD message indicating the status of the first MEP.
  • the Tail side receives the BFD message
  • Manner 2 The first MEP receives the unicast message sent by the second MEP for querying the status of the designated MEP; where the first MEP is the designated MEP; the first MEP replies to the second MEP in response to the unicast message to indicate the first BFD packets in the MEP state.
  • Manner 3 In the case that the first MEP detects the alarm of the loss of the link, the first MEP actively reports to the second MEP a BFD message for indicating the state of the first MEP.
  • dLoc will be generated when Tail actively detects that the Multipoint path fails, and at this time, it will actively report to the Head.
  • the method of this embodiment further includes: Set TxEn in the first MEP to 1; where TxEn is set to 1 to indicate that the first MEP is allowed to send BFD packets to the second MEP.
  • the active message sending mechanism will be used to send the message.
  • the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes a number of instructions to enable a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present invention.
  • a message processing device is also provided, which is used to implement the above-mentioned embodiments and preferred implementations, and the descriptions that have already been described will not be repeated.
  • the term "module” can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 3 is a structural block diagram of a message processing device according to an embodiment of the present invention. As shown in Fig. 3, the device includes:
  • the first receiving module 32 is configured to receive a bidirectional forwarding detection BFD message
  • the query module 34 is configured to query the corresponding MEP session according to the key fields in the BFD message;
  • the processing module 36 is configured to send a BFD message to the processor CPU when the corresponding MEP session is not found, complete the BFD session learning in the CPU subsystem, and look up the two MEPs in the chip Table is issued KEY; where, the lookup table includes a first lookup table and a second lookup table; the first lookup table is used to look up the multicast BFD message carrying the first key field and look up the index of the first MEP, and the second The lookup table is used to look up the unicast BFD message carrying the second key field and the index of the first MEP; the first key is different from the second key field; the first lookup table and the second lookup table are associated with the same MEP Conversation.
  • the lookup table includes a first lookup table and a second lookup table; the first lookup table is used to look up the multicast BFD message carrying the first key field and look up the index of the first MEP, and the second The lookup table is used to look up the unicast BFD message carrying the second key field and the
  • the apparatus of this embodiment may further include: a second receiving module configured to receive a multicast message sent by the second MEP for querying the status of all the first MEPs; and a first reply module configured to respond to the multicast The message replies to the second MEP with a BFD message indicating the state of the first MEP.
  • the apparatus of this embodiment may further include: a third receiving module configured to receive a unicast message sent by the second MEP for querying the status of the designated MEP; wherein the first MEP is the designated MEP; and the second reply module , It is set to reply to the second MEP in response to the unicast message with a BFD message indicating the state of the first MEP.
  • a third receiving module configured to receive a unicast message sent by the second MEP for querying the status of the designated MEP; wherein the first MEP is the designated MEP; and the second reply module , It is set to reply to the second MEP in response to the unicast message with a BFD message indicating the state of the first MEP.
  • the apparatus of this embodiment may further include: a reporting module configured to actively report a BFD message indicating the state of the first MEP to the second MEP in the case of detecting a link loss alarm.
  • a reporting module configured to actively report a BFD message indicating the state of the first MEP to the second MEP in the case of detecting a link loss alarm.
  • the apparatus of this embodiment may further include: a setting module configured to set TxEn in the first MEP to 1 before actively reporting a status message for indicating the status of the first MEP to the second MEP; wherein, TxEn is set to 1 to indicate that the first MEP is allowed to send BFD packets to the second MEP.
  • a setting module configured to set TxEn in the first MEP to 1 before actively reporting a status message for indicating the status of the first MEP to the second MEP; wherein, TxEn is set to 1 to indicate that the first MEP is allowed to send BFD packets to the second MEP.
  • each of the above modules can be implemented by software or hardware.
  • it can be implemented in the following manner, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination.
  • the forms are located in different processors.
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, wherein the processing of the message is realized when the computer program is executed by a processor.
  • the above-mentioned computer-readable storage medium may include, but is not limited to: U disk, Read-Only Memory (Read-Only Memory, ROM for short), Random Access Memory (Random Access Memory, RAM for short) , Mobile hard drives, magnetic disks or optical disks and other media that can store computer programs.
  • U disk Read-Only Memory
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Mobile hard drives magnetic disks or optical disks and other media that can store computer programs.
  • an electronic device including a memory, a processor, and a computer program stored on the memory and running on the processor.
  • the processor executes the computer program, Implement the steps of the message processing method.
  • the aforementioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the aforementioned processor, and the input-output device is connected to the aforementioned processor.
  • modules or steps of the present invention can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
  • they can be implemented with program codes executable by the computing device, so that they can be stored in the storage device for execution by the computing device, and in some cases, can be executed in a different order than here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computational Linguistics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供了一种报文的处理方法及装置，其中，该方法包括：第一维护终端节点MEP接收双向转发检测BFD报文；第一MEP根据BFD报文中的关键字段查询对应的MEP会话；在未查找到对应的MEP会话的情况下，第一MEP向处理器CPU发送BFD报文，并在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，该两张MEP查找表包括第一查找表和第二查找表；第一查找表用于查找携带有第一关键字段的组播BFD报文和查找第一MEP的索引，第二查找表用于查找携带有第二关键字段的单播BFD报文和查找第一MEP的索引；第一关键字与第二关键字段不同；第一查找表与第二查找表关联同一MEP会话。

Description

报文的处理方法及装置 技术领域
本发明涉及计算机领域，具体而言，涉及一种报文的处理方法及装置。
背景技术
Multipoint BFD是在RFC8562(Bidirectional Forwarding Detection(BFD)for Multipoint Networks)中定义，针对多点或组播网络中的一种特殊应用，它和传统BFD(Bidirectional Forwarding Detection，双向转发检测)的双向检测是有“冲突”的，因为多点传输本质上是单向的，该标准仅仅是为了验证单向连接的连通性，在RFC8562中定义了两种角色：Head和Tail，对于BFD报文，Head端上的MEP(Maintenance End Point，维护终端节点)只发不收，而Tail端的MEP只收不发，协议的本质是只为了检测Head到Tail的单向的连通性，BFD的报文只会从Head发向Tail，只在Tail检测Head到Tail的连通性，Head不需要知道Tail。因此，根据标准RFC8562，在Tail端基于Source address和My Discriminator查找得到Multipoint Tail会话，如果找到则更新Multipoint Tail MEP相关的状态机；如果没有找到，则创建新的会话或丢弃。而在RFC8563(Bidirectional Forwarding Detection(BFD)Multipoint Active Tails)是对RFC8562的一个补充，在某些特定的应用中，Head可能需要获取各个Tail的连接情况而引入的标准，标准中提出了三种方法：
1)Tail当检测到Fail时，主动发送单播BFD给Client告知；
2)Head偶尔发送Poll(仍为组播)查询所有Tail，Tail回复单播Final告知；
3)Client主动发送Poll到Tail(单播)查询指定Tail状态，Tail回复单播Final告知。
针对相关技术中的上述问题，目前尚未存在有效的解决方案。
发明内容
本发明实施例提供了一种报文的处理方法及装置，以至少解决相关技术中Tail MEP对于单播BFD和组播BFD需要创建多个MEP会话的问题。
根据本发明的一个实施例，提供了一种报文的处理方法，包括：第一维护终端节点MEP接收双向转发检测BFD报文；所述第一MEP根据所述BFD报文中的关键字段查询对应的MEP会话；在未查找到对应的MEP会话的情况下，所述第一MEP向处理器CPU发送所述BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，所述两张MEP查找表包括第一查找表和第二查找表；所述第一查找表用于查找携带有第一关键字段的组播BFD报文和查找所述第一MEP的索引，所述第二查找表用于查找携带有第二关键字段的单播BFD报文和查找所述第一MEP的索引；所述第一关键字与所述第二关键字段不同；所述第一查找表与所述第二查找表关联同一MEP会话。
根据本发明的另一个实施例，提供了一种报文的处理装置，应用于第一维护终端节点MEP侧，包括：第一接收模块，设置为接收双向转发检测BFD报文；查询模块，设置为根据所述BFD报文中的关键字段查询对应的MEP会话；处理模块，设置为在未查找到对应的MEP会话的情况下，向处理器CPU发送所述BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，所述查找表包括第一查找表和第二查找表；所述第一查找表用于查找携带有第一关键字段的组播BFD报文和查找所述第一MEP的索引，所述第二查找表用于查找携带有第二关键字段的单播BFD报文和查找所述第一MEP的索引；所述第一关键字与所述第二关键字段不同；所述第一查找表与所述第二查找表关联同一MEP会话。
根据本发明的另一个实施例，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述报文的处理方法的步骤。
根据本发明的另一个实施例，提供了一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现所述报文的处理方法的步骤。
通过本发明，在未查找到对应的MEP会话的情况下，第一MEP向处理器CPU发送BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，查找表包括第一查找表和第二查找表；第一查找表用于查找携带有第一关键字段的组播BFD报文和查找第一MEP的索引，第二查找表用于查找携带有第二关键字段的单播BFD报文和查找第一MEP的索引；第一关键字与第二关键字段不同；第一查找表与第二查找表关联同一MEP会话，即可以BFD报文中进行学习进而查找到对应的MEP会话，从而实现了Tail MEP在未查找得到Multipoint Tail会话的情况下创建新的会话用于实现RFC8563 Tail端的功能，解决了相关技术中解决相关技术中Tail MEP对于单播BFD和组播BFD需要创建多个MEP会话的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的报文的处理方法的流程图；
图2是根据本发明实施例的M-BFD报文查找MEP表的示意图；
图3是根据本发明实施例的报文的处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序 或先后次序。
在本实施例中提供了一种的报文的处理方法，图1是根据本发明实施例的报文的处理方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，第一维护终端节点MEP接收双向转发检测BFD报文；
步骤S104，第一MEP根据BFD报文中的关键字段查询对应的MEP会话；
步骤S106，在未查找到对应的MEP会话的情况下，第一MEP向处理器CPU发送BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，查找表包括第一查找表和第二查找表；第一查找表用于查找携带有第一关键字段的组播BFD报文和查找第一MEP的索引，第二查找表用于查找携带有第二关键字段的单播BFD报文和查找第一MEP的索引；第一关键字与第二关键字段不同；第一查找表与第二查找表关联同一MEP会话。
通过上述步骤S102至步骤S106，在未查找到对应的MEP会话的情况下，第一MEP向处理器CPU发送BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，查找表包括第一查找表和第二查找表；第一查找表用于查找携带有第一关键字段的组播BFD报文和查找第一MEP的索引，第二查找表用于查找携带有第二关键字段的单组播BFD报文和查找第一MEP的索引；第一关键字与第二关键字段不同；第一查找表与第二查找表关联同一MEP会话，即可以BFD报文中进行学习进而查找到对应的MEP会话，从而实现了Tail MEP在未查找得到Multipoint Tail会话的情况下创建新的会话用于实现RFC8563 Tail端的功能，解决了相关技术中解决相关技术中Tail MEP对于单播BFD和组播BFD需要创建多个MEP会话的问题。
需要说明的是，本实施例中涉及到的第一MEP在具体应用场景中可以为Tail MEP，第二MEP在具体应用场景可以为Head MEP。基于此，对于上述步骤S102至步骤S106在具体应用场景中可以是：
由上述本实施例的方法可知，在本实施例的具体应用场景中Multipoint Tail MEP的会话状态机维护在芯片中，但对于Multipoint Tail MEP会话的学习放在Offload Engine(卸载引擎)中进行，例如CPU子系统中，下述以CPU子系统为例进行说明；
现有技术中根据标准RFC8562，在Tail端基于Source address和My Discriminator查找得到Multipoint Tail会话，如果找到则更新Multipoint Tail MEP相关的状态机；如果没有找到，则创建新的会话或丢弃。而在本实施例的具体应用场景中，如果会话没有找到，默认条目将把Multipoint BFD报文送到CPU子系统中进行学习，在CPU子系统中将向芯片中的两张MEP查找表下发KEY：
一种是基于Source address(即IPSa)、My Discriminator的查找表(对应于第一查找表)，用于匹配带M＝1的组播BFD报文，并在查找表配置对应Tail MEP的Index；
另一种是基于Your Discriminator的查找表(第二查找表)，用于匹配带M＝0的单播BFD报文，也需要在查找表配置对应Tail MEP的Index，这个MEP Index和匹配M＝1组播BFD报文是相同的；
然后，再将Multipoint Tail MEP的会话信息配置到芯片去，其中，该会话信息主要涉及本地Tail的信息：My Discriminator表示本地Tail会话标识、IPSA表示本地Tail的IP地址、L4SrcPort表示本地Tail绑定的SourePort、Your Discriminator存放远端Head的标识、IPDA存放远端Head的IP地址、L4DstPort等于3784标识回复Head使用的端口信息、RXEn表示本地Tail是否接收BFD报文、TxEn表示本端Tail是否向Head端发送BFD报文等信息，如图2所示M-BFD报文查找MEP表。
在本实施例的可选实施方式中，本实施例的方法还包括多种第一MEP回复第二MEP状态信息的方式：
方式1：第一MEP接收第二MEP发送的用于查询所有第一MEP状态的组播消息；第一MEP响应于组播消息向第二MEP回复用于指示第一 MEP状态的BFD报文。
对于该方式1，在本实施例的具体应用场景中可以是：Head端(第二MEP)通过发送组播的Poll查询远端所有Tail的状态信息，即报文中M＝1，P＝1；此时当Tail端收到BFD报文时，Tail将回复Head；特别地，Head端在发起时间协商时，也会发送M＝1，P＝1，但是标准中通过Required Min RX Interval是否等于0来区分在两种情况，如果Required Min RX Interval＝0表明报文用于时间协商，不需要回复Head；而Required Min RX Interval！＝0表示报文用于查询状态需要回复Head；
方式2：第一MEP接收第二MEP发送的用于查询指定MEP状态的单播消息；其中，第一MEP为指定MEP；第一MEP响应于单播消息向第二MEP回复用于指示第一MEP状态的BFD报文。
对于该方式2，在本实施例的具体应用场景中可以是：在Head端也可以通过发送单播的Poll查询远端某个特定Tail的状态信息，即报文中M＝0，P＝1，Desired Min TX Interval！＝0；Required Min RX Interval！＝0；此时当Tail端收到此种BFD报文时，将Tail将回复Head。
方式3：在第一MEP检测到丢失链接的告警的情况下，第一MEP向第二MEP主动上报用于指示第一MEP状态的BFD报文。
对于该方式3，在本实施例的具体应用场景中可以是：当Tail主动检测到Multipoint路径失败时将会产生dLoc，此时主动上报给Head。
在本实施例的可选实施方式，对于上述方式1至3中涉及到的在第一MEP向第二MEP主动上报用于指示第一MEP状态的状态消息之前，本实施例的方法还包括：将第一MEP中的TxEn置为1；其中，TxEn置为1用于指示允许第一MEP向第二MEP发送BFD报文。
也就是说，无论是在Head端主动查询Tail的状态信息还是Tail端产生dLoc时主动上报Head都将采用主动报文发送机制将报文发送出去。
在正常情况下，Tail MEP会话中TxEn始终置为0，即表示不主动发送BFD，只有在Tail端接收到Head端主动查询Tail的状态信息时在接收 处理流程中将TxEn置为1，表示向远端Head发送BFD报文；而当Tail端主动检测到路径失败产生dLoc时，也将TxEn置为1，发送处理流程检测到TxEn＝1后，根据Tail MEP的会话封装BFD的报文信息，包括报文IPDA、IPSA、L4port等信息，并根据IPDA从芯片的路由表中查找得到下一跳出口和编辑信息，完成二层头MACDA和MACSA的封装，最终将报文发送处理，报文发送处理之后再次将TXEn置为0。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种报文的处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的报文的处理装置的结构框图，如图3所示，该装置包括：
(1)第一接收模块32，设置为接收双向转发检测BFD报文；
(2)查询模块34，设置为根据BFD报文中的关键字段查询对应的MEP会话；
(3)处理模块36，设置为在未查找到对应的MEP会话的情况下，向处理器CPU发送BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，查找表包括第一查找表 和第二查找表；第一查找表用于查找携带有第一关键字段的组播BFD报文和查找第一MEP的索引，第二查找表用于查找携带有第二关键字段的单播BFD报文和查找第一MEP的索引；第一关键字与第二关键字段不同；第一查找表与第二查找表关联同一MEP会话。
可选地，本实施例的装置还可以包括：第二接收模块，设置为接收第二MEP发送的用于查询所有第一MEP状态的组播消息；第一回复模块，设置为响应于组播消息向第二MEP回复用于指示第一MEP状态的BFD报文。
可选地，本实施例的装置还可以包括：第三接收模块，设置为接收第二MEP发送的用于查询指定MEP状态的单播消息；其中，第一MEP为指定MEP；第二回复模块，设置为响应于单播消息向第二MEP回复用于指示第一MEP状态的BFD报文。
可选地，本实施例的装置还可以包括：上报模块，设置为在检测到丢失链接的告警的情况下，向第二MEP主动上报用于指示第一MEP状态的BFD报文。
可选地，本实施例的装置还可以包括：设置模块，设置为在向第二MEP主动上报用于指示第一MEP状态的状态消息之前，将第一MEP中的TxEn置为1；其中，TxEn置为1用于指示允许第一MEP向第二MEP发送BFD报文。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
在本发明的实施例中，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述报文的处理方法的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于： U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例中，还提供了一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现所述报文的处理方法的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (12)

  1. 一种报文的处理方法，包括：
    第一维护终端节点MEP接收双向转发检测BFD报文；
    所述第一MEP根据所述BFD报文中的关键字段查询对应的MEP会话；
    在未查找到对应的MEP会话的情况下，所述第一MEP向处理器CPU发送所述BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，所述两张MEP查找表包括第一查找表和第二查找表；所述第一查找表用于查找携带有第一关键字段的组播BFD报文和查找所述第一MEP的索引，所述第二查找表用于查找携带有第二关键字段的单播BFD报文和查找所述第一MEP的索引；所述第一关键字与所述第二关键字段不同；所述第一查找表与所述第二查找表关联同一MEP会话。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一MEP接收第二MEP发送的用于查询所有第一MEP状态的组播消息；
    所述第一MEP响应于所述组播消息向所述第二MEP回复用于指示所述第一MEP状态的BFD报文。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第一MEP接收第二MEP发送的用于查询指定MEP状态的单播消息；其中，所述第一MEP为所述指定MEP；
    所述第一MEP响应于所述单播消息向所述第二MEP回复用于指示所述第一MEP状态的BFD报文。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    在所述第一MEP检测到丢失链接的告警的情况下，所述第一 MEP向第二MEP主动上报用于指示所述第一MEP状态的BFD报文。
  5. 根据权利要求2至4中任一项所述的方法，其中，在所述第一MEP向第二MEP主动上报用于指示所述第一MEP状态的状态消息之前，所述方法还包括：
    将所述第一MEP中的TxEn置为1；其中，所述TxEn置为1用于指示允许所述第一MEP向所述第二MEP发送BFD报文。
  6. 一种报文的处理装置，应用于第一维护终端节点MEP侧，包括：
    第一接收模块，设置为接收双向转发检测BFD报文；
    查询模块，设置为根据所述BFD报文中的关键字段查询对应的MEP会话；
    处理模块，设置为在未查找到对应的MEP会话的情况下，向处理器CPU发送所述BFD报文，在CPU子系统中完成BFD的会话学习，并向芯片中的两张MEP查找表下发KEY；其中，所述两张MEP查找表包括第一查找表和第二查找表；所述第一查找表用于查找携带有第一关键字段的组播BFD报文和查找所述第一MEP的索引，所述第二查找表用于查找携带有第二关键字段的组播BFD报文和查找所述第一MEP的索引；所述第一关键字与所述第二关键字段不同；所述第一查找表与所述第二查找表关联同一MEP会话。
  7. 根据权利要求6所述的装置，其中，所述装置还包括：
    第二接收模块，设置为接收第二MEP发送的用于查询所有第一MEP状态的组播消息；
    第一回复模块，设置为响应于所述组播消息向所述第二MEP回复用于指示所述第一MEP状态的BFD报文。
  8. 根据权利要求6所述的装置，其中，所述装置还包括：
    第三接收模块，设置为接收第二MEP发送的用于查询指定MEP状态的单播消息；其中，所述第一MEP为所述指定MEP；
    第二回复模块，设置为响应于所述单播消息向所述第二MEP回复用于指示所述第一MEP状态的BFD报文。
  9. 根据权利要求6所述的装置，其中，所述装置还包括：
    上报模块，设置为在检测到丢失链接的告警的情况下，向第二MEP主动上报用于指示所述第一MEP状态的BFD报文。
  10. 根据权利要求7至9中任一项所述的装置，其中，所述装置还包括：
    设置模块，设置为在向第二MEP主动上报用于指示所述第一MEP状态的状态消息之前，将所述第一MEP中的TxEn置为1；其中，所述TxEn置为1用于指示允许所述第一MEP向所述第二MEP发送BFD报文。
  11. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述权利要求1至5任一项中所述的方法的步骤。
  12. 一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现所述权利要求1至5任一项中所述的方法的步骤。
PCT/CN2020/113799 2020-02-21 2020-09-07 报文的处理方法及装置 WO2021164236A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010108236.2A CN111294358B (zh) 2020-02-21 2020-02-21 报文的处理方法及装置
CN202010108236.2 2020-02-21

Publications (1)

Publication Number Publication Date
WO2021164236A1 true WO2021164236A1 (zh) 2021-08-26

Family

ID=71030042

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/113799 WO2021164236A1 (zh) 2020-02-21 2020-09-07 报文的处理方法及装置

Country Status (2)

Country Link
CN (1) CN111294358B (zh)
WO (1) WO2021164236A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111294358B (zh) * 2020-02-21 2021-08-31 苏州盛科通信股份有限公司 报文的处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005915A1 (en) * 2015-07-02 2017-01-05 Telefonaktiebolaget L M Ericsson (Publ) Fast convergence in vrrp with multipoint bidirectional forwarding detection
CN106911571A (zh) * 2017-02-28 2017-06-30 烽火通信科技股份有限公司 一种基于网络处理器的远端pw bfd描述符学习方法及系统
US20190268256A1 (en) * 2018-02-28 2019-08-29 Zte Corporation Failure detection in a data network
CN111294358A (zh) * 2020-02-21 2020-06-16 盛科网络（苏州）有限公司 报文的处理方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104935581B (zh) * 2015-05-12 2018-04-03 盛科网络（苏州）有限公司 以太网oam和bfd双栈处理引擎的实现方法及装置
CN105791156B (zh) * 2016-03-03 2019-03-15 盛科网络（苏州）有限公司 一种支持多种bfd发送时间的芯片实现方法
CN106209640B (zh) * 2016-06-24 2019-03-05 湖南恒茂高科股份有限公司 Down MEP报文处理方法与系统
CN105933231B (zh) * 2016-06-24 2019-04-19 湖南恒茂高科股份有限公司 Up mep报文处理方法与系统
CN107846292B (zh) * 2016-09-19 2020-12-04 新华三技术有限公司 防止故障处理延迟的方法和装置
US10237206B1 (en) * 2017-03-05 2019-03-19 Barefoot Networks, Inc. Equal cost multiple path group failover for multicast

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005915A1 (en) * 2015-07-02 2017-01-05 Telefonaktiebolaget L M Ericsson (Publ) Fast convergence in vrrp with multipoint bidirectional forwarding detection
CN106911571A (zh) * 2017-02-28 2017-06-30 烽火通信科技股份有限公司 一种基于网络处理器的远端pw bfd描述符学习方法及系统
US20190268256A1 (en) * 2018-02-28 2019-08-29 Zte Corporation Failure detection in a data network
CN111294358A (zh) * 2020-02-21 2020-06-16 盛科网络（苏州）有限公司 报文的处理方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
D. KATZ JUNIPER NETWORKS D. WARD CISCO SYSTEMS S. PALLAGATTI, ED. VMWARE G. MIRSKY, ED. ZTE CORP.: "Bidirectional Forwarding Detection (BFD) for Multipoint Networks; rfc8562.txt", BIDIRECTIONAL FORWARDING DETECTION (BFD) FOR MULTIPOINT NETWORKS; RFC8562.TXT, 3 April 2019 (2019-04-03), pages 1 - 23, XP015130708 *

Also Published As

Publication number Publication date
CN111294358B (zh) 2021-08-31
CN111294358A (zh) 2020-06-16

Similar Documents

Publication Publication Date Title
AU2015400309B2 (en) Long connection sharing method for multi-businesses, system and device, terminal
US20160330167A1 (en) Arp Implementation Method, Switch Device, and Control Device
WO2020173080A1 (zh) 调用链信息查询方法以及设备
US10855576B2 (en) Information transmission method and device
US11139995B2 (en) Methods and router devices for verifying a multicast datapath
WO2021128927A1 (zh) 报文的处理方法及装置、存储介质和电子装置
WO2018072732A1 (zh) 一种信息处理方法、装置和计算机存储介质
CN111818187B (zh) 一种内外网通信方法及系统
WO2019223534A1 (zh) 一种转发表项的监测方法及装置
WO2016091156A1 (zh) 节点故障的判断方法及装置
US11522792B2 (en) Method for discovering forwarding path and related device thereof
US20230300051A1 (en) In-band Edge-to-Edge Round-Trip Time Measurement
WO2021164236A1 (zh) 报文的处理方法及装置
WO2021120708A1 (zh) 报文的处理方法及装置、存储介质和电子装置
TW202333534A (zh) 運用於邊緣計算之資料傳送系統、方法及其電腦可讀媒介
WO2013159492A1 (zh) 信息上报与下载的方法及系统
CN110995413B (zh) 一种防止伪节点攻击的联盟链共识节点管理方法
TWI660284B (zh) 網路封鎖方法及設備，以及電腦可讀取儲存媒體
CN111064825B (zh) 一种基于arp实现dpi数据采集和控制方法和装置
US20220417136A1 (en) Pce controlled network reliability
CN104396216A (zh) 用于识别网络流量特征以关联和管理一个或多个后续流的方法及其装置
CN106130874B (zh) 融合多通信方式的企业一体化信息处理方法
CN110474781B (zh) 一种组播数据转发的方法及装置
CN114090342A (zh) 存储容灾的链路管理方法及消息执行节点、存储控制集群
CN108418709B (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: 20920656

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: 20920656

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 27/03/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20920656

Country of ref document: EP

Kind code of ref document: A1