CN111294358A - Message processing method and device - Google Patents
Message processing method and device Download PDFInfo
- Publication number
- CN111294358A CN111294358A CN202010108236.2A CN202010108236A CN111294358A CN 111294358 A CN111294358 A CN 111294358A CN 202010108236 A CN202010108236 A CN 202010108236A CN 111294358 A CN111294358 A CN 111294358A
- Authority
- CN
- China
- Prior art keywords
- mep
- message
- bfd
- lookup table
- session
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computational Linguistics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a message processing method and a message processing device, wherein the method comprises the following steps: a first maintenance terminal node MEP receives a Bidirectional Forwarding Detection (BFD) message; the first MEP inquires a corresponding MEP session according to the key field in the BFD message; under the condition that the corresponding MEP session is not found, the first MEP sends a BFD message to a CPU (central processing unit), completes session learning of BFD in a CPU subsystem and issues a KEY to two MEP lookup tables in a chip; wherein the two MEP lookup tables comprise a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching indexes of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching indexes of the first MEP; the first key is different from the second key field; the first lookup table is associated with the same MEP session as the second lookup table.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a method and an apparatus for processing a packet.
Background
Multi-point BFD is defined in RFC8562(Bidirectional Forwarding Detection (BFD) for multi-point Networks), which is "conflicting" with the Bidirectional Detection of traditional BFD (Bidirectional Forwarding Detection) for a special application in Multipoint or multicast Networks, because Multipoint transmission is unidirectional in nature, the standard is only for verifying connectivity of unidirectional connections, two roles are defined in RFC 8562: for the Head and the Tail, for the BFD message, the MEP (Maintenance End Point) at the Head End only transmits and does not receive, and the MEP at the Tail End only receives and does not transmit, the essence of the protocol is only to detect the unidirectional connectivity from the Head to the Tail, the BFD message only transmits from the Head to the Tail, only detects the connectivity from the Head to the Tail at the Tail, and the Head does not need to know the Tail. Therefore, according to the standard RFC8562, a Multipoint Tail session is found at the Tail end based on the Source address and the My descriptor, and if the Multipoint Tail session is found, a state machine related to the Multipoint Tail MEP is updated; if not, a new session is created or dropped. Whereas RFC8563(Bidirectional Forwarding Detection (BFD) Multipoint Active tags) is a supplement to RFC8562, in some specific applications, Head may need to obtain standards introduced by the connection condition of each Tail, and three methods are proposed in the standards:
1) when detecting Fail, Tail actively sends unicast BFD to Client to inform;
2) head occasionally sends Poll (still multicast) query for all tails, which reply to unicast Final notification;
3) the Client actively sends a Poll to Tail query specifying Tail status, and Tail replies with a unicast Final announcement.
In view of the above problems in the related art, no effective solution exists at present.
Disclosure of Invention
The embodiment of the invention provides a message processing method and a message processing device, which are used for at least solving the problem that in the related technology, a plurality of MEP sessions are required to be established by TailMEP for unicast BFD and multicast BFD.
According to an embodiment of the present invention, a method for processing a packet is provided, including: a first maintenance terminal node MEP receives a Bidirectional Forwarding Detection (BFD) message; the first MEP inquires a corresponding MEP session according to a key field in the BFD message; under the condition that the corresponding MEP session is not found, the first MEP sends the BFD message to a CPU (central processing unit), session learning of BFD is completed in a CPU subsystem, and a KEY is issued to two MEP lookup tables in a chip; wherein the two MEP lookup tables comprise a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching the index of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching 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.
According to another embodiment of the present invention, there is provided a message processing apparatus applied to a first maintenance terminal node MEP side, including: the first receiving module is used for receiving the Bidirectional Forwarding Detection (BFD) message; the query module is used for querying the corresponding MEP session according to the key field in the BFD message; the processing module is used for sending the BFD message to the CPU under the condition that the corresponding MEP session is not found, completing the session learning of BFD in the CPU subsystem and issuing a KEY to the two MEP lookup tables in the chip; wherein the lookup table comprises a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching the index of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching 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.
According to the invention, under the condition that the corresponding MEP session is not found, the first MEP sends a BFD message to the CPU, completes the session learning of BFD in the CPU subsystem, and issues a KEY to two MEP lookup tables in a chip; the lookup table comprises a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching indexes of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching indexes 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, learning can be performed in the BFD message to find the corresponding MEP session, so that the purpose that a new session is created for realizing the function of the RFC8563 Tail end under the condition that a Multipoint Tail session is not found is realized by the Tail MEP, and the problem that a plurality of MEP sessions are required to be created by the Tail MEP for unicast BFD and multicast BFD in the related technology is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flowchart of a message processing method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of an M-BFD packet lookup MEP table according to an embodiment of the present invention;
fig. 3 is a block diagram of a message processing apparatus according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
Example 1
In this embodiment, a method for processing a message is provided, and fig. 1 is a flowchart of a method for processing a message according to an embodiment of the present invention, as shown in fig. 1, the flowchart includes the following steps:
step S102, a first maintenance terminal node MEP receives a Bidirectional Forwarding Detection (BFD) message;
step S104, the first MEP inquires the corresponding MEP session according to the key field in the BFD message;
step S106, under the condition that the corresponding MEP session is not found, the first MEP sends a BFD message to a CPU (central processing unit), session learning of BFD is completed in a CPU subsystem, and a KEY is issued to two MEP lookup tables in a chip; the lookup table comprises a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching indexes of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching indexes of the first MEP; the first key is different from the second key field; the first lookup table is associated with the same MEP session as the second lookup table.
Through the steps S102 to S106, under the condition that the corresponding MEP session is not found, the first MEP sends a BFD message to the CPU, session learning of BFD is completed in the CPU subsystem, and a KEY is issued to the two MEP lookup tables in the chip; the lookup table comprises a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching indexes of the first MEP, and the second lookup table is used for searching single multicast BFD messages carrying a second key field and searching indexes 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, learning can be performed in the BFD message to find the corresponding MEP session, so that the purpose that a new session is created for realizing the function of the RFC8563 Tail end under the condition that a Multipoint Tail session is not found is realized by the Tail MEP, and the problem that a plurality of MEP sessions are required to be created by the Tail MEP for unicast BFD and multicast BFD in the related technology is solved.
It should be noted that the first MEP related in this embodiment may be a Tail MEP in a specific application scenario, and the second MEP may be a Head MEP in a specific application scenario. Based on this, the steps S102 to S106 may be, in a specific application scenario:
as can be seen from the method of this embodiment, in the specific application scenario of this embodiment, the session state machine of the Multipoint Tail MEP is maintained in the chip, but the learning of the Multipoint Tail MEP session is performed in the offload engine (for example, in the CPU subsystem, the following description takes the CPU subsystem as an example;
in the prior art, according to standard RFC8562, a Multipoint Tail session is found at a Tail end based on Source address and MyDiscrimator, and if found, a state machine related to a Multipoint Tail MEP is updated; if not, a new session is created or dropped. 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 issue a KEY to two MEP lookup tables in the chip:
one is a lookup table (corresponding to a first lookup table) based on Source address (IPSa) and My discovery, and is used for matching multicast BFD messages with M ═ 1, and configuring an Index corresponding to Tail MEP in the lookup table;
the other is a lookup table (second lookup table) based on a Your Discriminator, which is used for matching unicast BFD messages with M ═ 0, and also needs to configure an Index corresponding to Tail MEP in the lookup table, and the MEP Index and the matching M ═ 1 multicast BFD messages are the same;
then, configuring the session information of the Multipoint Tail MEP to the chip, wherein the session information mainly relates to the information of local Tail: my Discriminator represents a local Tail session identifier, IPSA represents an IP address of the local Tail, L4 SrcPort represents a Soureport bound by the local Tail, Your Discriminator stores an identifier of a remote Head, IPDA stores an IP address of the remote Head, L4 DstPort equals 3784 identifier port information used for replying the Head, RXEn represents whether the local Tail receives BFD messages, TxEn represents whether the local Tail sends BFD messages to the Head, and the like, and M-BFD messages search an MEP table as shown in FIG. 2.
In an optional implementation manner of this embodiment, the method of this embodiment further includes multiple manners for the first MEP to reply the status information of the second MEP:
mode 1: the first MEP receives a multicast message which is sent by the second MEP and used for inquiring the states of all the first MEPs; and the first MEP replies a BFD message for indicating the state of the first MEP to the second MEP in response to the multicast message.
For the mode 1, in a specific application scenario of the embodiment, the following may be performed: a Head end (a second MEP) queries state information of all Tail at a remote end through a multicast-sending Poll, namely, M is 1 and P is 1 in a message; at the moment, when the Tail end receives the BFD message, the Tail returns to Head; particularly, when initiating time negotiation, the Head end will also send M1 and P1, but in the standard, whether Required Min RX Interval is equal to 0 is used to distinguish between the two cases, and if Required Min RX Interval is equal to 0, the message is used for time negotiation, and no Head needs to be replied; and Required Min RX Interval! When the message is used for inquiring the state, a Head needs to be replied;
mode 2: the first MEP receives a unicast message which is sent by the second MEP and used for inquiring the state of the specified MEP; wherein the first MEP is a designated MEP; and the first MEP replies a BFD message for indicating the state of the first MEP to the second MEP in response to the unicast message.
For the mode 2, in a specific application scenario of the embodiment, the following may be performed: the Head end may also query the status information of a specific Tail at the remote end by sending unicast Poll, that is, M is 0, P is 1, Desired Min TXInterval | in the message! 0; required Min RX Interval! 0; when the Tail end receives the BFD message, the Tail end returns to Head.
Mode 3: and under the condition that the first MEP detects the alarm of the lost link, the first MEP actively reports a BFD message for indicating the state of the first MEP to the second MEP.
For the mode 3, in a specific application scenario of the embodiment, the following may be performed: when the Tail actively detects that the Multipoint path fails, dLoc is generated, and is actively reported to the Head.
In an optional implementation manner of this embodiment, before the first MEP actively reports the status message used for indicating the status of the first MEP to the second MEP in the foregoing implementation manners 1 to 3, the method of this embodiment further includes: setting TxEn in the first MEP to 1; and the TxEn is set to be 1 and used for indicating that the first MEP is allowed to send the BFD message to the second MEP.
That is, no matter the Head actively queries the state information of the Tail or actively reports the Head when the Tail generates the dLoc, the message is sent out by adopting an active message sending mechanism.
Under normal conditions, TxEn in the Tail MEP session is always set to 0, namely that BFD is not actively sent, and is set to 1 in the receiving processing flow only when the Tail end receives the state information of the Head end actively inquiring the Tail, namely that BFD messages are sent to the far-end Head; and when the Tail end actively detects that the path fails to generate dLoc, setting TxEn to 1, after the sending processing flow detects that TxEn is 1, encapsulating the message information of BFD according to the session of Tail MEP, wherein the message information comprises messages IPDA, IPSA, L4 port and the like, searching and obtaining the next hop exit and editing information from the routing table of the chip according to IPDA, completing the encapsulation of a two-layer header MACDA and MACSA, finally sending the message, and setting TXEn to 0 again after the message is sent and processed.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
In this embodiment, a message processing apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and details of which have been already described are omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 3 is a block diagram of a message processing apparatus according to an embodiment of the present invention, and as shown in fig. 3, the apparatus includes:
(1) a first receiving module 32, configured to receive a bidirectional forwarding detection BFD packet;
(2) the query module 34 is configured to query the corresponding MEP session according to the key field in the BFD packet;
(3) the processing module 36 is configured to send a BFD message to the CPU of the processor when the corresponding MEP session is not found, complete session learning of BFD in the CPU subsystem, and issue a KEY to two MEP lookup tables in the chip; the lookup table comprises a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching indexes of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching indexes of the first MEP; the first key is different from the second key field; the first lookup table is associated with the same MEP session as the second lookup table.
Optionally, the apparatus of this embodiment may further include: a second receiving module, configured to receive a multicast message sent by a second MEP and used for querying the statuses of all the first MEPs; and the first reply module is used for replying a BFD message for indicating the state of the first MEP to the second MEP in response to the multicast message.
Optionally, the apparatus of this embodiment may further include: a third receiving module, configured to receive a unicast message sent by the second MEP and used for querying a status of the specified MEP; wherein the first MEP is a designated MEP; and the second reply module is used for replying a BFD message used for indicating the state of the first MEP to the second MEP in response to the unicast message.
Optionally, the apparatus of this embodiment may further include: and the reporting module is used for actively reporting a BFD message for indicating the state of the first MEP to the second MEP under the condition of detecting the alarm of the lost link.
Optionally, the apparatus of this embodiment may further include: the device comprises a setting module, a sending module and a receiving module, wherein the setting module is used for setting TxEn in a first MEP to 1 before actively reporting a state message for indicating the state of the first MEP to a second MEP; and the TxEn is set to be 1 and used for indicating that the first MEP is allowed to send the BFD message to the second MEP.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for processing a message is characterized by comprising the following steps:
a first maintenance terminal node MEP receives a Bidirectional Forwarding Detection (BFD) message;
the first MEP inquires a corresponding MEP session according to a key field in the BFD message;
under the condition that the corresponding MEP session is not found, the first MEP sends the BFD message to a CPU (central processing unit), session learning of BFD is completed in a CPU subsystem, and a KEY is issued to two MEP lookup tables in a chip; wherein the two MEP lookup tables comprise a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching the index of the first MEP, and the second lookup table is used for searching unicast BFD messages carrying a second key field and searching 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.
2. The method of claim 1, further comprising:
the first MEP receives a multicast message which is sent by a second MEP and used for inquiring the states of all the first MEPs;
and the first MEP replies a BFD message for indicating the state of the first MEP to the second MEP in response to the multicast message.
3. The method of claim 1, further comprising:
the first MEP receives a unicast message which is sent by a second MEP and used for inquiring the state of the specified MEP; wherein the first MEP is the designated MEP;
and the first MEP replies a BFD message for indicating the state of the first MEP to the second MEP in response to the unicast message.
4. The method of claim 1, further comprising:
and under the condition that the first MEP detects the alarm of the lost link, the first MEP actively reports a BFD message for indicating the state of the first MEP to a second MEP.
5. The method of any of claims 2-4, wherein prior to the first MEP actively reporting a status message to a second MEP indicating a status of the first MEP, the method further comprises:
setting TxEn in the first MEP to 1; and the TxEn is set to be 1, and is used for indicating that the first MEP is allowed to send a BFD message to the second MEP.
6. A message processing device is applied to a first maintenance terminal (MEP) side, and is characterized by comprising:
the first receiving module is used for receiving the Bidirectional Forwarding Detection (BFD) message;
the query module is used for querying the corresponding MEP session according to the key field in the BFD message;
the processing module is used for sending the BFD message to the CPU under the condition that the corresponding MEP session is not found, completing the session learning of BFD in the CPU subsystem and issuing a KEY to the two MEP lookup tables in the chip; wherein the two MEP lookup tables comprise a first lookup table and a second lookup table; the first lookup table is used for searching multicast BFD messages carrying a first key field and searching the index of the first MEP, and the second lookup table is used for searching multicast BFD messages carrying a second key field and searching 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.
7. The apparatus of claim 6, further comprising:
a second receiving module, configured to receive a multicast message sent by a second MEP and used for querying the statuses of all the first MEPs;
and the first reply module is used for replying a BFD message for indicating the state of the first MEP to the second MEP in response to the multicast message.
8. The apparatus of claim 6, further comprising:
a third receiving module, configured to receive a unicast message sent by the second MEP and used for querying a status of the specified MEP; wherein the first MEP is the designated MEP;
a second reply module, configured to reply, to the second MEP, a BFD packet indicating the state of the first MEP in response to the unicast message.
9. The apparatus of claim 6, further comprising:
and the reporting module is used for actively reporting a BFD message for indicating the state of the first MEP to the second MEP under the condition of detecting the alarm of the lost link.
10. The apparatus of any one of claims 7 to 9, further comprising:
a setting module, configured to set TxEn in a first MEP to 1 before actively reporting a status message indicating a status of the first MEP to a second MEP; and the TxEn is set to be 1, and is used for indicating that the first MEP is allowed to send a BFD message to the second MEP.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010108236.2A CN111294358B (en) | 2020-02-21 | 2020-02-21 | Message processing method and device |
PCT/CN2020/113799 WO2021164236A1 (en) | 2020-02-21 | 2020-09-07 | Message processing method and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010108236.2A CN111294358B (en) | 2020-02-21 | 2020-02-21 | Message processing method and device |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111294358A true CN111294358A (en) | 2020-06-16 |
CN111294358B CN111294358B (en) | 2021-08-31 |
Family
ID=71030042
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010108236.2A Active CN111294358B (en) | 2020-02-21 | 2020-02-21 | Message processing method and device |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN111294358B (en) |
WO (1) | WO2021164236A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021164236A1 (en) * | 2020-02-21 | 2021-08-26 | 苏州盛科通信股份有限公司 | Message processing method and device |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114302259A (en) * | 2021-12-27 | 2022-04-08 | 杭州迪普信息技术有限公司 | User information collection method, device, equipment and computer readable storage medium |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104935581A (en) * | 2015-05-12 | 2015-09-23 | 盛科网络(苏州)有限公司 | Ethernet OAM and BFD dual-stack processing engine realization method and device |
CN105791156A (en) * | 2016-03-03 | 2016-07-20 | 盛科网络(苏州)有限公司 | Chip implementation method supporting sending time of multiple BFDs (Bidirectional Forwarding Detections) |
CN105933231A (en) * | 2016-06-24 | 2016-09-07 | 醴陵恒茂电子科技有限公司 | UP MEP (Maintenance association End Point) message processing method and system |
CN106209640A (en) * | 2016-06-24 | 2016-12-07 | 醴陵恒茂电子科技有限公司 | Down MEP message processing method and system |
CN107846292A (en) * | 2016-09-19 | 2018-03-27 | 新华三技术有限公司 | The method and apparatus for preventing troubleshooting from postponing |
US10237206B1 (en) * | 2017-03-05 | 2019-03-19 | Barefoot Networks, Inc. | Equal cost multiple path group failover for multicast |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9755958B2 (en) * | 2015-07-02 | 2017-09-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Fast convergence in VRRP with multipoint bidirectional forwarding detection |
CN106911571B (en) * | 2017-02-28 | 2019-08-13 | 烽火通信科技股份有限公司 | A kind of distal end PW BFD descriptor learning method and system based on network processing unit |
US10771312B2 (en) * | 2018-02-28 | 2020-09-08 | Zte Corporation | Failure detection in a data network |
CN111294358B (en) * | 2020-02-21 | 2021-08-31 | 苏州盛科通信股份有限公司 | Message processing method and device |
-
2020
- 2020-02-21 CN CN202010108236.2A patent/CN111294358B/en active Active
- 2020-09-07 WO PCT/CN2020/113799 patent/WO2021164236A1/en active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104935581A (en) * | 2015-05-12 | 2015-09-23 | 盛科网络(苏州)有限公司 | Ethernet OAM and BFD dual-stack processing engine realization method and device |
CN105791156A (en) * | 2016-03-03 | 2016-07-20 | 盛科网络(苏州)有限公司 | Chip implementation method supporting sending time of multiple BFDs (Bidirectional Forwarding Detections) |
CN105933231A (en) * | 2016-06-24 | 2016-09-07 | 醴陵恒茂电子科技有限公司 | UP MEP (Maintenance association End Point) message processing method and system |
CN106209640A (en) * | 2016-06-24 | 2016-12-07 | 醴陵恒茂电子科技有限公司 | Down MEP message processing method and system |
CN107846292A (en) * | 2016-09-19 | 2018-03-27 | 新华三技术有限公司 | The method and apparatus for preventing troubleshooting from postponing |
US10237206B1 (en) * | 2017-03-05 | 2019-03-19 | Barefoot Networks, Inc. | Equal cost multiple path group failover for multicast |
Non-Patent Citations (1)
Title |
---|
D.KATZ: "" Bidirectional Forwarding Detection (BFD) Multipoint Active Tails"", 《IETF》 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021164236A1 (en) * | 2020-02-21 | 2021-08-26 | 苏州盛科通信股份有限公司 | Message processing method and device |
Also Published As
Publication number | Publication date |
---|---|
CN111294358B (en) | 2021-08-31 |
WO2021164236A1 (en) | 2021-08-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11374857B2 (en) | Network device management method and apparatus, and system for indicating a network device to perform management operation | |
US9461928B2 (en) | LACP negotiation processing method, relay node, and system | |
AU2015400309B2 (en) | Long connection sharing method for multi-businesses, system and device, terminal | |
US20160330167A1 (en) | Arp Implementation Method, Switch Device, and Control Device | |
CN101953139B (en) | DHCP in response to Internet connectedness initializes | |
CN103036732B (en) | A kind of method of network monitoring process, system and equipment | |
CN111294358B (en) | Message processing method and device | |
US11139995B2 (en) | Methods and router devices for verifying a multicast datapath | |
US10834033B2 (en) | Method and system for transferring messages between messaging systems | |
US11463349B2 (en) | Fault diagnosis method and apparatus thereof | |
WO2012088910A1 (en) | Method and system for detecting connectivity fault | |
WO2019223534A1 (en) | Method and device for monitoring forwarding table entry | |
CN101977142A (en) | Simple network management method and device based on multiple routing protocol instances | |
WO2021120708A1 (en) | Message processing method and device, storage medium, and electronic device | |
WO2013159492A1 (en) | Method and system for reporting and downloading information | |
CN110380966A (en) | A kind of method and its relevant device finding forward-path | |
US20220417136A1 (en) | Pce controlled network reliability | |
CN115037785B (en) | Instant communication system and method | |
CN106130874B (en) | enterprise integrated information processing method fusing multiple communication modes | |
US20190036793A1 (en) | Network service implementation method, service controller, and communications system | |
CN110474781B (en) | Method and device for forwarding multicast data | |
CN114095759B (en) | Stream media redirection method and related device | |
CN107396334A (en) | The method of wireless sound box and its multiple smart machines of connection | |
WO2022041923A1 (en) | Network slice connection method, terminal, and computer-readable storage medium | |
WO2024049554A1 (en) | Alternative route propogation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
CB02 | Change of applicant information |
Address after: Xinghan Street Industrial Park of Suzhou city in Jiangsu province 215021 B No. 5 Building 4 floor 13/16 unit Applicant after: Suzhou Shengke Communication Co.,Ltd. Address before: Xinghan Street Industrial Park of Suzhou city in Jiangsu province 215021 B No. 5 Building 4 floor 13/16 unit Applicant before: CENTEC NETWORKS (SU ZHOU) Co.,Ltd. |
|
CB02 | Change of applicant information | ||
GR01 | Patent grant | ||
GR01 | Patent grant |