CN107181689B - Message interaction method and device between routers - Google Patents
Message interaction method and device between routers Download PDFInfo
- Publication number
- CN107181689B CN107181689B CN201610136162.7A CN201610136162A CN107181689B CN 107181689 B CN107181689 B CN 107181689B CN 201610136162 A CN201610136162 A CN 201610136162A CN 107181689 B CN107181689 B CN 107181689B
- Authority
- CN
- China
- Prior art keywords
- router
- message
- application
- tlv
- applications
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
Abstract
A method and a device for message interaction between routers are provided, the method comprises: adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which application or applications; a router performs an operation corresponding to an application that is using the router ID of the router that sent the message, through the router ID usage information TLV in the message received from the other router. The technical scheme solves the problem of redundant operation caused by the fact that the router does not know the application using the router ID, and avoids resource waste.
Description
Technical Field
The present disclosure relates to the field of message interaction technologies between routers, and in particular, to a method and an apparatus for message interaction between routers.
Background
The routers generally need to complete routing through message interaction, and in the related art, the message interacted among the routers only includes a router ID TLV (type, length, value), and through the router ID TLV, the router receiving the message can know the ID of the router sending the message and perform routing accordingly.
When the router ID TLV information is shared by a plurality of applications, the router receiving the message performs many redundant operations due to any case where the ID of the router sending the message is not known, thereby causing a waste of resources.
Disclosure of Invention
In view of the above, the technical problem to be solved by the present invention is to provide a method and an apparatus for message interaction between routers, so as to solve the redundant operations caused by the fact that the router does not know the application using the router ID, and avoid resource waste.
In order to solve the problems, the following technical scheme is adopted:
a method of message interaction between routers, the method comprising:
adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which application or applications;
a router performs an operation corresponding to an application that is using the router ID of the router that sent the message, through the router ID usage information TLV in the message received from the other router.
Optionally, the message further includes a router ID of a router that sends the message.
Optionally, the content fields included in the router ID usage information TLV include a sub-TLV type, a sub-TLV length, and sub-TLV content.
Optionally, the sub-TLV types include two types of IPv4 router ID usage information and IPv6 router ID usage information.
Optionally, the application that is using the router ID includes: one or more of TE (Traffic Engineering), Remote-LFA (Loop free alternative), and SR (Segment Routing).
Optionally, the sub-TLV content field includes a flag and a corresponding description, by which it can be indicated which application or applications the router ID of the router sending the message is being used by, while reflecting which application or applications the router ID is not being used by.
Optionally, the step of executing the corresponding operation of the application using the router ID of the router sending the message includes:
when the router ID use information TLV indicates that the router ID of the router sending the message is being used by a certain application or certain applications, establishing a topology or a tunnel corresponding to the application or the applications;
and when the router ID use information TLV reflects that the router ID of the router sending the message is not used by a certain application or certain applications, abandoning or stopping establishing the topology or the tunnel corresponding to the application or the applications.
A message interaction apparatus, the apparatus comprising: at least one processor executing the following modules:
a message processing module configured to: adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which application or applications;
an operating module configured to: a router performs an operation corresponding to an application that is using the router ID of the router that sent the message, through the router ID usage information TLV in the message received from the other router.
Optionally, the message processing module is further configured to: the router ID of the router is set in the message.
Optionally, the message processing module is configured to add a router ID usage information TLV to messages exchanged between routers as follows: setting a sub-TLV type, a sub-TLV length, and sub-TLV content in a content field included in the router ID usage information TLV.
Optionally, the message processing module is configured to set the sub-TLV type as follows: setting the sub-TLV type to IPv4 router ID usage information or IPv6 router ID usage information.
Optionally, the message processing module is configured to add a router ID usage information TLV to messages exchanged between routers as follows: setting the application that is using the router ID includes: one or more of TE (Traffic Engineering), Remote-LFA (Loop free alternative), and SR (Segment Routing).
Optionally, the message processing module is configured to set the sub-TLV content as follows: setting a flag and a corresponding description in the content field of the sub-TLV, wherein the flag and the description indicate that the router ID of the router sending the message is used by which application or applications and reflect that the router ID is not used by which application or applications.
Optionally, the operation module is configured to perform the corresponding operation of the application that is using the router ID of the router sending the message as follows:
when the router ID use information TLV indicates that the router ID of the router sending the message is being used by a certain application or certain applications, establishing a topology or a tunnel corresponding to the application or the applications;
and when the router ID of the router which sends the message is not used by a certain application or certain applications through the mapping of the router ID using information TLV, abandoning or stopping establishing the topology or the tunnel corresponding to the application or the applications.
Optionally, the apparatus is located in a router.
After the technical scheme is adopted, the router ID of the router sending the message is indicated to be used by a certain application or certain applications through adding the router ID use information TLV, so that the router receiving the message can directly perform routing related operations such as topology establishment or tunnel establishment according to the router ID use information TLV, the flexibility of analyzing and using the router ID information by the router is improved, and unnecessary resource loss of the router due to redundant operation is reduced.
Drawings
FIG. 1 is a flow chart of a message interaction method according to the present invention;
FIG. 2 is a topology diagram of an application example 1 of the present invention;
FIG. 3 is a topology diagram of an embodiment 2 of the present invention;
FIG. 4 is a topology diagram of an embodiment 3 of the present invention;
fig. 5 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
Detailed Description
The technical solution of the present invention will be described in more detail with reference to the accompanying drawings and examples.
In order to make the objects, technical means and advantages of the present invention more apparent, the following detailed description of the method of using the present invention is provided together with the accompanying drawings.
When an LSP (link state PDU) of a router floods router ID information, there may be a case where a plurality of applications or functions use the router ID at the same time. The technical scheme of the invention indicates that the router ID of the router sending the message is used by a certain application or certain applications by adding the router ID use information TLV, so that the router receiving the message can directly perform routing related operations such as topology establishment or tunnel establishment according to the information, the flexibility of analyzing and using the router ID information by the router is improved, and the unnecessary resource loss of the router due to redundant operation is reduced.
An embodiment of the present invention provides a method for message interaction between routers, as shown in fig. 1, the method includes:
adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which applications;
a router performs an operation corresponding to an application that is using the router ID of the router that sent the message, through the router ID usage information TLV in the message received from the other router.
Optionally, the message further includes a router ID of a router that sends the message.
Optionally, the content fields included in the router ID usage information TLV include a sub-TLV type, a sub-TLV length, and sub-TLV content.
Optionally, the sub-TLV types include two types of IPv4 router ID usage information and IPv6 router ID usage information.
Optionally, the application that is using the router ID includes: one or more of TE (Traffic Engineering), Remote-LFA (Loop free alternative), and SR (Segment Routing).
Optionally, the sub-TLV content field includes a flag and a corresponding description, by which it can be indicated which application or applications the router ID of the router sending the message is being used by, while reflecting which application or applications the router ID is not being used by. It can be reflected here that the router ID is not used by which application or applications, rather than indicating that the router ID is not used by which application or applications, because it can be seen from the first embodiment below that the sub-TLV content field, via flag and corresponding description, can only indicate which application or applications the router ID of the router sending the message is being used by.
Optionally, the step of executing the corresponding operation of the application using the router ID of the router sending the message includes:
when the router ID use information TLV indicates that the router ID of the router sending the message is being used by a certain application or certain applications, establishing a topology or a tunnel corresponding to the application or the applications;
and when the router ID of the router sending the message is not mapped by a certain application or certain applications by using the TLV, abandoning or stopping establishing the topology or the tunnel corresponding to the application or the applications.
The first embodiment is as follows:
the specific format of the router ID use information TLV of the embodiment of the invention is defined as follows:
router ID usage information-this optional TLV, should occur at most once within the LSP to indicate router ID usage.
Type code-undetermined
Length-total length of content
Content-
sub-TLV type code-1 or 2.
sub-TLV length-sub-TLV content length.
sub-TLV content-
Wherein, sub-TLV type 1: IPv4 router ID usage information
Contained within such sub-TLV is IPv4 route ID usage information, and it should appear at most once within the router ID usage information TLV. The length of this sub-TLV is not fixed to 1 byte (eight bits) for flexibility and ease of expansion.
sub-TLV type 2: IPv6 router ID usage information
Contained within such sub-TLV is IPv6 route ID usage information, and it should appear at most once within the router ID usage information TLV. The length of this sub-TLV is not fixed to 1 byte (eight bits) for flexibility and ease of expansion.
The following is further illustrated with a few application examples of the invention.
Assume that the routing device supports a router ID usage information TLV:
application example 1:
assuming the network topology as in fig. 2, the directly connected nodes are interworking and the bidirectional Metric cost value (10 in the figure) is the same. Now a Remote-LFA backup route is attempted to be generated for link S-E, which is known by the algorithm that node C is an alternative PQ node. If the router ID carried by the C node is not applied to Remote-LFA by analyzing the router ID use information TLV of the C node, the S node gives up the standby topology from the S node to the C node immediately, and simultaneously tries to establish the tunnel from the S node to the C node.
Application example 2: assuming the network topology as shown in fig. 3, the directly connected nodes are intercommunicated, and the bidirectional Metric values are the same. A TE tunnel is now established for the S-node to the E-node. Although the router ID is acquired from the LSP of the E node, if the router ID carried by the E node is found not to be applied to TE by analyzing the router ID use information TLV of the E node, the S node immediately abandons the establishment of a TE tunnel from the S node to the E node.
Application example 3: assuming the network topology as shown in fig. 4, the directly connected nodes are intercommunicated, and the bidirectional Metric values are the same. Now planning to implement SR for the S-node to D-node path requires that S-A, A-B, B-C and C-D must be traversed. Although the router ID is acquired from the LSP of the A node, if the router ID carried by the A node is found not to be applied to the SR by analyzing the router ID use information TLV of the A node, the S node abandons the analysis of the SR-specific sub TLV and stops the SR-related action.
An embodiment of the present invention provides a message interaction apparatus, as shown in fig. 5, the apparatus includes: at least one processor executing the following modules:
a message processing module 501 configured to: adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which application or applications;
an operation module 502 configured to: performing an application corresponding operation using the router ID of the router sending the message through the router ID usage information TLV in the message received from other routers.
Optionally, the message processing module 501 is further configured to: the router ID of the router is set in the message.
Optionally, the message processing module 501 is configured to add the router ID usage information TLV to the message exchanged between the routers as follows: setting a sub-TLV type, a sub-TLV length, and sub-TLV content in a content field included in the router ID usage information TLV.
Optionally, the message processing module 501 is configured to set the sub-TLV type as follows: setting the sub-TLV type to IPv4 router ID usage information or IPv6 router ID usage information.
Optionally, the message processing module 501 is configured to add the router ID usage information TLV to the message exchanged between the routers as follows: setting the application that is using the router ID includes: one or more of TE (Traffic Engineering), Remote-LFA (Loop free alternative), and SR (Segment Routing).
Optionally, the message processing module 501 is configured to set the sub-TLV content as follows: setting a flag and a corresponding description in the content field of the sub-TLV, wherein the flag and the description indicate that the router ID of the router sending the message is used by which application or applications and reflect that the router ID is not used by which application or applications. It can be reflected here that the router ID is not used by which application or applications, rather than indicating that the router ID is not used by which application or applications, because it can be seen from the first embodiment below that the sub-TLV content field, via flag and corresponding description, can only indicate which application or applications the router ID of the router sending the message is being used by.
Optionally, the operation module 502 is configured to perform the corresponding operation of the application that is using the router ID of the router sending the message as follows:
when the router ID use information TLV indicates that the router ID of the router sending the message is being used by a certain application or certain applications, establishing a topology or a tunnel corresponding to the application or the applications;
and when the router ID of the router which sends the message is not used by a certain application or certain applications through the mapping of the router ID using information TLV, abandoning or stopping establishing the topology or the tunnel corresponding to the application or the applications.
Optionally, the apparatus is located in a router.
The corresponding parts of the above device and method are the same as the realization of the method, and are not described herein again.
In the technical scheme, if the received message comprises the router ID use information TLV, the router device uses the router ID according to the information in the router ID use information TLV after analyzing the router ID in the message, so that useless processing is avoided, and unnecessary resource loss of the router is reduced.
It should be noted that, if not conflicting, the embodiments of the present invention and the features of the embodiments may be combined with each other within the scope of protection of the present invention. Additionally, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by instructing the relevant hardware through a program, and the program may be stored in a computer readable storage medium, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiments may be implemented in the form of hardware, and may also be implemented in the form of a software functional module. The present invention is not limited to any specific form of combination of hardware and software.
The present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof, and it should be understood that various changes and modifications can be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (15)
1. A method for message interaction between routers, the method comprising:
adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which application or applications;
a router performs an operation corresponding to an application that is using the router ID of the router that sent the message, through the router ID usage information TLV in the message received from the other router;
wherein the executing of the corresponding operation of the application using the router ID of the router sending the message comprises at least one of the following: and establishing a topology or a tunnel corresponding to the application or the applications, abandoning the topology or the tunnel corresponding to the application or the applications, and stopping establishing the topology or the tunnel corresponding to the application or the applications.
2. The method of message interaction between routers of claim 1, wherein the message further includes a router ID of the router sending the message.
3. The method of message interaction between routers as claimed in claim 1, wherein said router ID usage information TLV includes content fields including sub-TLV type, sub-TLV length and sub-TLV content.
4. The method of message interaction between routers of claim 3, wherein said sub-TLV type includes both types of IPv4 router ID usage information and IPv6 router ID usage information.
5. The method of message interaction between routers of claim 1, wherein the application that is using the router ID comprises: one or more of TE (Traffic Engineering), Remote-LFA (Loop free alternative), and SR (Segment Routing).
6. The method of message interaction between routers as claimed in claim 3, wherein said sub-TLV content field includes a flag and a corresponding description, by which it can be indicated which application or applications the router ID of the router sending the message is being used by, while reflecting which application or applications the router ID is not being used by.
7. The method of message interaction between routers of claim 1, wherein the step of performing an operation corresponding to the application that is using the router ID of the router that sent the message comprises:
when the router ID use information TLV indicates that the router ID of the router sending the message is being used by a certain application or certain applications, establishing a topology or a tunnel corresponding to the application or the applications;
and when the router ID use information TLV reflects that the router ID of the router sending the message is not used by a certain application or certain applications, abandoning or stopping establishing the topology or the tunnel corresponding to the application or the applications.
8. A message interaction apparatus, comprising: at least one processor executing the following modules:
a message processing module configured to: adding router ID use information TLV in messages interacted among routers, wherein the router ID use information TLV is used for indicating that the router ID of a router sending the messages is being used by which application or applications;
an operating module configured to: a router performs an operation corresponding to an application that is using the router ID of the router that sent the message, through the router ID usage information TLV in the message received from the other router;
wherein the operation module is configured to perform an operation corresponding to an application using the router ID of the router sending the message in one of the following manners: and establishing a topology or a tunnel corresponding to the application or the applications, abandoning the topology or the tunnel corresponding to the application or the applications, and stopping establishing the topology or the tunnel corresponding to the application or the applications.
9. The message interaction device of claim 8, wherein the message processing module is further configured to: the router ID of the router is set in the message.
10. Message interaction device according to claim 8 or 9, characterized in that the message handling module is arranged to add the router ID usage information TLV in messages interacted between routers as follows: setting a sub-TLV type, a sub-TLV length, and sub-TLV content in a content field included in the router ID usage information TLV.
11. Message interaction means according to claim 10, characterised in that the message handling module is arranged to set the sub-TLV type as follows: setting the sub-TLV type to IPv4 router ID usage information or IPv6 router ID usage information.
12. Message interaction device according to claim 8, characterized in that the message handling module is arranged to add the router ID usage information TLV in messages interacted between routers as follows: setting the application that is using the router ID includes: one or more of TE (Traffic Engineering), Remote-LFA (Loop free alternative), and SR (Segment Routing).
13. Message interaction means according to claim 10, characterised in that the message handling module is arranged to set the sub-TLV content as follows: setting a flag and a corresponding description in the content field of the sub-TLV, wherein the flag and the description indicate that the router ID of the router sending the message is used by which application or applications and reflect that the router ID is not used by which application or applications.
14. The message interaction device of claim 8, wherein the operation module is configured to perform application-specific operations that are using the router ID of the router sending the message as follows:
when the router ID use information TLV indicates that the router ID of the router sending the message is being used by a certain application or certain applications, establishing a topology or a tunnel corresponding to the application or the applications;
and when the router ID of the router which sends the message is not used by a certain application or certain applications through the mapping of the router ID using information TLV, abandoning or stopping establishing the topology or the tunnel corresponding to the application or the applications.
15. The message interaction device of claim 8, wherein the device is located in a router.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610136162.7A CN107181689B (en) | 2016-03-10 | 2016-03-10 | Message interaction method and device between routers |
| PCT/CN2016/095728 WO2017152585A1 (en) | 2016-03-10 | 2016-08-17 | Method and device for message exchange between routers |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610136162.7A CN107181689B (en) | 2016-03-10 | 2016-03-10 | Message interaction method and device between routers |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107181689A CN107181689A (en) | 2017-09-19 |
| CN107181689B true CN107181689B (en) | 2021-09-14 |
Family
ID=59789953
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610136162.7A Active CN107181689B (en) | 2016-03-10 | 2016-03-10 | Message interaction method and device between routers |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107181689B (en) |
| WO (1) | WO2017152585A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110061920B (en) * | 2018-01-18 | 2021-10-19 | 中兴通讯股份有限公司 | Method, equipment and storage medium for establishing bidirectional segment routing tunnel |
| CN114124806B (en) * | 2018-05-25 | 2022-11-25 | 华为技术有限公司 | Method and equipment for generating route |
| CN113507416B (en) | 2018-10-27 | 2022-05-10 | 华为技术有限公司 | Message processing method, related equipment and computer storage medium |
| CN112104552B (en) * | 2019-06-17 | 2021-12-28 | 华为技术有限公司 | Method and device for processing message and computer storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101155135A (en) * | 2006-09-28 | 2008-04-02 | 华为技术有限公司 | Method and device for flooding autonomous system border router ability information |
| CN101369958A (en) * | 2007-08-15 | 2009-02-18 | 华为技术有限公司 | Fast rerouting method and label exchange router |
| CN101610205A (en) * | 2008-06-20 | 2009-12-23 | 华为技术有限公司 | Method for obtaining path, transmitting apparatus, receiving equipment and network system |
| CN102833157A (en) * | 2012-08-10 | 2012-12-19 | 华为技术有限公司 | Method and device for eliminating media access control withdrawal message concussion in VPLS (virtual private LAN service) |
| WO2013181130A1 (en) * | 2012-05-30 | 2013-12-05 | Alcatel-Lucent Usa Inc. | System and method for managing mpls-te overload |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9019865B2 (en) * | 2011-03-04 | 2015-04-28 | Juniper Networks, Inc. | Advertising traffic engineering information with the border gateway protocol |
| US20160094439A1 (en) * | 2014-09-26 | 2016-03-31 | Futurewei Technologies, Inc. | Method and apparatus for interface capability and elastic content response encoding in information centric networking |
-
2016
- 2016-03-10 CN CN201610136162.7A patent/CN107181689B/en active Active
- 2016-08-17 WO PCT/CN2016/095728 patent/WO2017152585A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101155135A (en) * | 2006-09-28 | 2008-04-02 | 华为技术有限公司 | Method and device for flooding autonomous system border router ability information |
| CN101369958A (en) * | 2007-08-15 | 2009-02-18 | 华为技术有限公司 | Fast rerouting method and label exchange router |
| CN101610205A (en) * | 2008-06-20 | 2009-12-23 | 华为技术有限公司 | Method for obtaining path, transmitting apparatus, receiving equipment and network system |
| WO2013181130A1 (en) * | 2012-05-30 | 2013-12-05 | Alcatel-Lucent Usa Inc. | System and method for managing mpls-te overload |
| CN102833157A (en) * | 2012-08-10 | 2012-12-19 | 华为技术有限公司 | Method and device for eliminating media access control withdrawal message concussion in VPLS (virtual private LAN service) |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017152585A1 (en) | 2017-09-14 |
| CN107181689A (en) | 2017-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3016323B1 (en) | Service transmission path determination method, device and system | |
| US20160352578A1 (en) | System and method for adaptive paths locator for virtual network function links | |
| EP2996287B1 (en) | Method for notifying information of pe device and pe device | |
| CN102833109B (en) | Positional information processing method and equipment of fault point | |
| CN107181689B (en) | Message interaction method and device between routers | |
| US10044770B2 (en) | Method and apparatus for managing a plurality of sessions in a multi-path routing based network | |
| EP3474493B1 (en) | Network performance measurement method and detection device | |
| EP3713160A1 (en) | Packet transmission method and apparatus | |
| EP4175250A1 (en) | Information exchange and tunnel establishment methods, apparatuses, communication nodes, and storage medium | |
| CN107294856B (en) | Method, equipment and system for determining topology change | |
| JP7448597B2 (en) | Message generation method and device and message processing method and device | |
| US10715628B2 (en) | Attribute operating method and device | |
| CN114513429A (en) | Transmission method for detection message, and method and equipment for determining reverse path | |
| WO2022012489A1 (en) | Capability indication method and related device | |
| WO2021057530A1 (en) | Method, apparatus and system for determining mapping relationship between routing prefix and segment identification | |
| CN113630316B (en) | Data transmission method and communication device | |
| US20170041216A1 (en) | Method and Apparatus for Determining Intermediate Routing Node and System | |
| WO2020029928A1 (en) | Method for establishing bgp session and sending interface address and alias, and network device | |
| US20120176930A1 (en) | System and method for providing co-signaled return label switch paths | |
| CN111464440A (en) | Communication method and device | |
| CN111464441A (en) | Communication method and device | |
| CN113904972B (en) | Path detection method and device, controller and PE (polyethylene) equipment | |
| CN116489237A (en) | Data packet processing method and device and network equipment | |
| JP2023539689A (en) | Operation, management, and maintenance OAM packet processing methods and devices | |
| WO2018205887A1 (en) | Delay collection method and apparatus |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |