Control and data channel radio resource configuration
US-2016227522-A1 · Aug 4, 2016 · US
US9838290B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9838290-B2 |
| Application number | US-201514824667-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 12, 2015 |
| Priority date | Jun 30, 2015 |
| Publication date | Dec 5, 2017 |
| Grant date | Dec 5, 2017 |
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 node configured to support a Flexible Ethernet (FlexE) client service in a network includes circuitry configured to receive a FlexE client; and circuitry configured to at least one of monitor and update one or more Operations, Administration, and Maintenance (OAM) fields in FlexE overhead, wherein the OAM fields cover a single client path along many network segments (sections) for the FlexE client. A method, implemented in a node, for supporting a Flexible Ethernet (FlexE) client service in a network includes receiving a FlexE client; and at least one of monitoring and updating one or more Operations, Administration, and Maintenance (OAM) fields in FlexE overhead, wherein the OAM fields cover a single client path along many network segments (sections) for the FlexE client.
Opening claim text (preview).
What is claimed is: 1. A node configured to support a Flexible Ethernet (FlexE) client service in a network, the node comprising: circuitry configured to receive a FlexE client; and circuitry configured to monitor and update one or more Operations, Administration, and Maintenance (OAM) fields in FlexE overhead, wherein the OAM fields are monitored and updated over a single client path for the FlexE client, wherein the one or more OAM fields are implemented by the circuitry configured to monitor and update in a Reconciliation Sublayer. 2. The node of claim 1 , wherein the circuitry configured to monitor and update is configured to monitor and update a client service error monitoring field in the one or more OAM fields to detect errors over the single client path. 3. The node of claim 2 , wherein the client service error monitoring field is a bitstream Bit Interleaved Parity (BIP) code. 4. The node of claim 1 , wherein the circuitry configured to monitor and update is configured to monitor and update any of a connectivity/trace, link fault, remote fault, maintenance states, test signals, link neighbor discovery, and backwards fault and error indication, in the one or more OAM fields. 5. The node of claim 1 , wherein the circuitry configured to monitor and update is configured to monitor and update the one or more OAM fields separate from standard Local Fault and Remote Fault information for an associated FlexE group/PHY. 6. The node of claim 1 , wherein the one or more OAM fields are located by the circuitry configured to monitor and update using a multiframe scheme in the FlexE overhead. 7. A method, implemented by circuitry in a node, for supporting a Flexible Ethernet (FlexE) client service in a network, the method comprising: receiving a FlexE client; and updating and monitoring one or more Operations, Administration, and Maintenance (OAM) fields in FlexE overhead, wherein the OAM fields are monitored and updated over a single client path for the FlexE client, wherein the one or more OAM fields are implemented in a Reconciliation Sublayer during the updating and monitoring by the circuitry. 8. The method of claim 7 , wherein the updating and monitoring comprises updating and modifying a client service error monitoring field in the one or more OAM fields to detect errors over the single client. 9. The method of claim 8 , wherein the client service error monitoring field is a bitstream Bit Interleaved Parity (BIP) code. 10. The method of claim 7 , wherein the updating and monitoring comprises updating and modifying any of a connectivity/trace, link fault, remote fault, maintenance states, test signals, link neighbor discovery, and backwards fault and error indication, in the one or more OAM fields. 11. The method of claim 7 , wherein the updating and monitoring comprises updating and modifying the one or more OAM fields separate from standard Local Fault and Remote Fault information for an associated FlexE group/PHY. 12. The method of claim 7 , wherein the one or more OAM fields are located during the updating and monitoring using a multiframe scheme in the FlexE overhead. 13. A node configured to support a Flexible Ethernet (FlexE) client service in a network, the node comprising: circuitry configured to receive a FlexE client; and circuitry configured to monitor and update one or more Operations, Administration, and Maintenance (OAM) fields in FlexE overhead, wherein the OAM fields are monitored and updated over a single client path for the FlexE client, wherein the circuitry configured to monitor and update is configured to monitor and update the one or more OAM fields separate from standard Local Fault and Remote Fault information for an associated FlexE group/PHY. 14. The node of claim 13 , wherein the circuitry configured to monitor and update is configured to monitor and update a client service error monitoring field in the one or more OAM fields to detect errors over the single client path. 15. The node of claim 14 , wherein the client service error monitoring field is a bitstream Bit Interleaved Parity (BIP) code. 16. The node of claim 13 , wherein the circuitry configured to monitor and update is configured to monitor and update any of a connectivity/trace, link fault, remote fault, maintenance states, test signals, link neighbor discovery, and backwards fault and error indication, in the one or more OAM fields. 17. The node of claim 13 , wherein the one or more OAM fields are located by the circuitry configured to monitor and update using a multiframe scheme in the FlexE overhead. 18. The node of claim 13 , wherein the one or more OAM fields are implemented in a Reconciliation Sublayer during the updating and monitoring by the circuitry.
carrying packets or ATM cells; (H04J3/1664 takes precedence for payloads with different packet types) · CPC title
Support of Ethernet · CPC title
Operations, administration and maintenance [OAM] · CPC title
Support for services · CPC title
by checking connectivity · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.