Translating high-level configuration instructions to low-level device configuration
US-10200248-B1 · Feb 5, 2019 · US
US11894970B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11894970-B2 |
| Application number | US-201916453692-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 26, 2019 |
| Priority date | Dec 26, 2016 |
| Publication date | Feb 6, 2024 |
| Grant date | Feb 6, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A DCN packet processing method, a network device, and a network system are provided. The DCN packet processing method includes: generating, by a network device, a first DCN packet whose destination address is an IP address of an NMS, loading the first DCN packet into a Flex Ethernet (Flex Eth) overhead multiframe, and sending, over a physical link, the Flex Eth overhead multiframe to a network device that has accessed a network, so that the network device that has accessed the network extracts the first DCN packet, and sends the first DCN packet to the NMS based on the destination address, so as to enable the NMS to perceive that a new network device accesses the network.
Opening claim text (preview).
What is claimed is: 1. A data communication network (DCN) packet processing method, wherein the method comprises: generating, by a first network device, a first DCN packet that includes a destination address and a payload, wherein the first network device and a second network device are connected using a physical link, and the DCN includes a network management system (NMS) communicatively coupled to the second network device; monitoring, by the first network device, a state of a Flex Ethernet client, and determining that the state of the Flex Ethernet client is not a conducted state: adding, by the first network device, the first DCN packet into a flexible Ethernet (Flex Ethernet) overhead multiframe; and sending, by the first network device, the Flex Ethernet overhead multiframe to the second network device by using the physical link, so that the second network device extracts the first DCN packet from the Flex Ethernet overhead multiframe, and forwards the first DCN packet to the NMS according to the destination address; generating, by the first network device, a second DCN packet that includes the destination address; monitoring, by the first network device, the state of a Flex Ethernet client, and determining that the state of the Flex Ethernet client is the conducted state; and sending, by the first network device, the second DCN packet to the second network device through the Flex Ethernet client according to the destination address. 2. The method according to claim 1 , wherein adding the first DCN packet into the Flex Ethernet overhead multiframe comprises: adding, by the first network device, the first DCN packet on a section management channel of the Flex Ethernet overhead multiframe. 3. The method according to claim 1 , further comprising: buffering, by the first network device, the first DCN packet. 4. The method according to claim 1 , wherein adding the first DCN packet into the Flex Ethernet overhead multiframe comprises: adding, by the first network device, the first DCN packet on a shim to shim management channel of the Flex Ethernet overhead multiframe. 5. The method according to claim 1 , wherein adding the first DCN packet into the Flex Ethernet overhead multiframe comprises: splitting, by the first network device, the first DCN packet and adding the first DCN packet on a section management channel and a shim to shim management channel of the Flex Ethernet overhead multiframe. 6. The method according to claim 1 , further comprising: buffering, by the first network device, the second DCN packet. 7. The method according to claim 1 , wherein: the second network device is communicatively coupled to the NMS using a second physical link; or the second network device is communicatively coupled to the NMS via one or more additional network devices, wherein a local routing table included in the second network device maps an address associated with the NMS to a third physical link associated with a particular network device of the one or more additional network devices. 8. The method according to claim 1 , further comprising: receiving, from the NMS, a management packet via a Flex Ethernet channel established between the NMS and the first network device based on the first DCN packet. 9. A network device, used as a first network device, wherein the first network device comprises: a memory comprising instructions; one or more processors coupled to the memory, wherein the instructions, when executed by the one or more processors, cause the first network device to be configured to: generate a first data communication network (DCN) packet that includes a destination address and a payload, wherein the first network device and a second network device are connected using a physical link, and the DCN includes a network management system (NMS) communicatively coupled to the second network device; monitor a state of a Flex Ethernet client, and determining that the state of the Flex Ethernet client is not a conducted state; load the first DCN packet into a flexible Ethernet (Flex Ethernet) overhead multiframe; and send the Flex Ethernet overhead multiframe to the second network device over the physical link, so that the second network device extracts the first DCN packet from the Flex Ethernet overhead multiframe, and forwards the first DCN packet to the NMS according to the destination address, generate a second DCN packet that includes the destination address; monitor the state of a Flex Ethernet client, and determining that the state of the Flex Ethernet client is the conducted state; and send the second DCN packet to the second network device through the Flex Ethernet client according to the destination address. 10. The network device according to claim 9 , wherein the instructions cause the first network device to be configured to: load the first DCN packet on a section management channel of the Flex Ethernet overhead multiframe. 11. The network device according to claim 9 , wherein the instructions cause the first network device to be configured to: buffer the first DCN packet. 12. The network device according to claim 9 , wherein the instructions cause the first network device to be configured to: load the first DCN packet on a shim to shim management channel of the Flex Ethernet overhead multiframe. 13. The network device according to claim 9 , wherein the instructions cause the first network device to be configured to: load the first DCN packet on a section management channel and a shim to shim management channel of the Flex Ethernet overhead multiframe.
Related publications grouped by family.
Answers are generated from the same data shown on this page.