Patent Description:
The present disclosure generally relates to optical networking systems and methods. More particularly, the present disclosure relates to Flexible Optical (FlexO)/ZR partial survivability as well as partial survivability for multi-carrier and multi-module optical interfaces such as Optical Transport Network (OTN), Flexible Ethernet (FlexE), and FlexO.

In high bandwidth optical transport networks, recent standards such as ITU-T Recommendation G. <NUM> "Interfaces for the optical transport network" (<NUM>/<NUM>), , describe the use of multiple optical carriers for a single digital transport interface in line side applications, such as an Optical Transport Unit-Cn (OTUCn) which is carried via multiple Optical Tributary Signal (OTSi) carriers (lambdas). For client side applications, ITU-T Recommendation G. <NUM> (under progress) defines the use of multiple client services/modules for a single OTUCn transport service. Similarly, the Optical Internetworking Forum (OIF) has worked on IA # OIF-FLEXE-<NUM> "Flex Ethernet Implementation Agreement" (<NUM>/<NUM>), for FlexE to transport an Ethernet client service across multiple standard rate client interfaces/servers. The standards behavior is that upon a failure of any single carrier/module for the interface; the entire group is considered failed, and consequential actions are taken on the entire interface (or all services carried). As described herein, an interface is used for a network port and a service is used for individual services being carried within the interface. A single group interface can carry one or more services.

Of course, taking down the entire transport interface, although compliant to existing standards, can impact a significant amount of services. As services are deployed across multiple carriers/modules, the overall reliability (Failures in Time (FITS)/Mean Time Between Failures (MTBF)) is at risk. The components involved in the electro-optical interfaces typically have associated high failure rates. As an example, if the entire network interface is <NUM> and is being carried over four carriers, then a failure of a single carrier affects all <NUM> even though that single carrier may be responsible for only a quarter of that traffic (<NUM>). Such lack of partial survivability has a major impact on the network in regard to failures. For failures, a network controller requires sufficient bandwidth to restore failed services. The lack of partial survivability significantly increases the amount of bandwidth, e.g., <NUM> instead of just <NUM> based on the aforementioned network interface example.

In addition to the use of multiple OTSi for increasing bandwidth, individual interfaces themselves are expanding to support high bit rates, e.g., <NUM>, <NUM>, etc. There are situations where a single interface may need to be subrated for partial survivability. Of note, there are approaches defined at the Optical Data Unit level k (ODUk) service layer, but not at the OTUCn/FlexO/ZR interface layer. That is, there are no current definitions for subrating and partial survivability for FlexO/ZR interfaces. <CIT> describes partial survivability for multi-carrier and multi-module optical interfaces.

In an embodiment, an optical interface and a method include steps of operating an optical interface at a first rate; subsequent to a requirement to subrate the optical interface to a second rate, determining which one or more services are affected; signaling one or more partial failures for the one or more affected services; an operating the optical interface at a second rate that is less than the first rate. The optical interface can be a Flexible Optical (FlexO) interface. The FlexO interface can include a plurality of Optical Transport Unit C (OTUC) slices each at about 100Gb/s, and wherein the one or more partial failures are for one or more OTUC slices. The optical interface can be a ZR interface. The optical interface can include a plurality of slices each at about 100Gb/s, and wherein the one or more partial failures is for one or more slices.

The one or more partial failures can be signaled through one or more of a partial Alarm Indication Signal (P-AIS), a partial Backward Defect Indication (P-BDI), and a partial Server Signal Fail (P-SSF). The steps can further include adjusting overhead of the optical interface based on the one or more partial failures. The steps can further include adjusting one or more of the affected services based on priority. The requirement to subrate can be due to any of optical margin and a requirement to support an alternate path. The optical interface can be part of an Optical Tributary Signal (OTSi).

In another embodiment, a network element includes one or more ports forming a plurality of optical carriers (Optical Tributary Signal (OTSi)) that transport a single Optical Transport Unit Cn (OTUCn) in a network; and circuitry communicatively coupled to the one or more ports and configured to, subsequent to an optical carrier failure of the plurality of optical carriers, determine which services in the OTUCn are affected, cause signaling of a partial failure for the OTUCn and signaling a failure for the affected services, and cause adjustment of some or all of the affected services on non-failed optical carriers of the plurality of optical carriers. The adjustment can include a move of the some or all of the affected services from the optical carrier failure to the non-failed optical carriers based on priority. The OTUCn can have a bandwidth N and the plurality of optical carriers are X optical carriers, X > <NUM>, each having a bandwidth M<NUM>, M<NUM>,. , MX each being less than N and a total being equal to N. The circuitry can be further configured to cause overhead adjustment on the OTUCn based on the optical carrier failure such that the overhead is transport on non-failed optical carriers of the plurality of optical carriers The overhead adjustment can include a move of the overhead from the failed optical carrier to one of the non-failed optical carriers. The overhead adjustment can include a defect indication to indicate which of the non-failed optical carriers has the overhead. The overhead adjustment can include identical copies of the overhead on the non-failed optical carriers with a weighted scheme used to determine which copy of the overhead is valid.

In another embodiment, a method include, in a network element with one or more ports forming a plurality of optical carriers (Optical Tributary Signal (OTSi)) that transport a single Optical Transport Unit Cn (OTUCn) in a network, and subsequent to an optical carrier failure of the plurality of optical carriers, determining which services in the OTUCn are affected; signaling a partial failure for the OTUCn and signaling a failure for the affected services; and adjusting some or all of the affected services on non-failed optical carriers of the plurality of optical carriers.

In a further embodiment, a non-transitory computer-readable storage medium having computer readable code stored thereon for programming a network element with one or more ports forming a plurality of optical carriers (Optical Tributary Signal (OTSi)) that transport a single Optical Transport Unit Cn (OTUCn) in a network to, subsequent to an optical carrier failure of the plurality of optical carriers, determine which services in the OTUCn are affected, cause signaling of a partial failure for the OTUCn and signaling a failure for the affected services, and cause adjustment of some or all of the affected services on non-failed optical carriers of the plurality of optical carriers.

In a further embodiment, a partial survivability method implemented in a node in an Optical Transport Unit Cn (OTUCn) network includes, subsequent to an optical carrier (Optical Tributary Signal (OTSi)) failure of a plurality of optical carriers, determining which Optical Data Unit k (ODUk) services in an OTUCn associated with the OTSi are affected; signaling a partial failure for the OTUCn and signaling a failure only for the affected ODUk services; adjusting overhead associated with the OTUCn based on the OTSi failure; and applying actions on the affected ODUk services subsequent to the OTSi failure. The signaling the partial failure can include signaling one or more of a partial Alarm Indication Signal (P-AIS), a partial Backward Defect Indication (P-BDI), and a partial Server Signal Fail (P-SSF) for the OTUCn, and wherein the signaling the failure can include signaling one or more of an Alarm Indication Signal (AIS), a Backward Defect Indication (BDI), and a Server Signal Fail (SSF) only for the affected ODUk services. The adjusting overhead can include adjusting overhead associated with the OTUCn and with an associated Optical Data Unit Cn (ODUCn) and with an associated Optical Payload Channel Cn (OPUCn) between slices.

The adjusting can include using a partial Backward Defect Indication (P-BDI) or a Remote Defect Indication (RDI) to decide by an adjacent transmitter which OTUCn slice overhead is used. The adjusting can include an adjacent transmitter broadcasting the overhead to all OTUCn slices with identical copies with a weighted scheme used by the node to determine which copy of the overhead is valid. The determining can be based on monitoring fault points of the OTSi which failed by the node and determining the affected the ODUk services based on an association maintained by the node of the ODUk services to the failed OTSi. The actions can include one or more of restoring the affected ODUk services, resizing the affected ODUk services, and moving the affected ODUk services, performed through one of a control plane and a Software Defined Networking (SDN) controller. The partial survivability method can further include, responsive to an ODUk service of the affected ODUk services being partially affected by the OTSi failure, adjusting a size of the ODUk service to operate on operational OTSi unaffected by the OTSi failure. The partial survivability method can further include shuffling one or more of the affected ODUk services with unaffected ODUk services based on priority through an edit operation at the node.

In yet another embodiment, a node adapted for partial survivability in an Optical Transport Unit Cn (OTUCn) network includes one or more line modules forming a plurality of optical carriers (Optical Tributary Signal (OTSi)); and a controller adapted to, subsequent to an OTSi failure, determine which Optical Data Unit k (ODUk) services in an OTUCn associated with the OTSi are affected, cause signaling of a partial failure for the OTUCn and signaling a failure only for the affected ODUk services, cause adjustment of overhead associated with the OTUCn based on the OTSi failure, and cause actions on the affected ODUk services subsequent to the OTSi failure. The signaling the partial failure can include signaling one or more of a partial Alarm Indication Signal (P-AIS), a partial Backward Defect Indication (P-BDI), and a partial Server Signal Fail (P-SSF) for the OTUCn, and wherein the signaling the failure can include signaling one or more of an Alarm Indication Signal (AIS), a Backward Defect Indication (BDI), and a Server Signal Fail (SSF) only for the affected ODUk services. The adjustment of overhead can include adjustment of the overhead associated with the OTUCn and with an associated Optical Data Unit Cn (ODUCn) and with an associated Optical Payload Channel Cn (OPUCn) between slices.

The adjustment can include using a partial Backward Defect Indication (P-BDI) or a Remote Defect Indication (RDI) to decide by an adjacent transmitter which OTUCn slice overhead is used. The adjustment can include an adjacent transmitter broadcasting the overhead to all OTUCn slices with identical copies with a weighted scheme used by the node to determine which copy of the overhead is valid. The affected ODUk services can be determined based on monitoring fault points of the OTSi which failed by the node and determining the affected the ODUk services based on an association maintained by the node of the ODUk services to the failed OTSi. The actions can include one or more of restoring the affected ODUk services, resizing the affected ODUk services, and moving the affected ODUk services, performed through one of a control plane and a Software Defined Networking (SDN) controller. The controller can be further adapted to, responsive to an ODUk service of the affected ODUk services being partially affected by the OTSi failure, cause adjustment of a size of the ODUk service to operate on operational OTSi unaffected by the OTSi failure. The controller can be further adapted to cause shuffling one or more of the affected ODUk services with unaffected ODUk services based on priority through an edit operation at the node.

In yet another embodiment, a partial survivability apparatus implemented in a node in an Optical Transport Unit Cn (OTUCn) network includes circuitry adapted to determine, subsequent to an optical carrier (Optical Tributary Signal (OTSi)), failure, which Optical Data Unit k (ODUk) services in an OTUCn associated with the OTSi are affected; circuitry adapted to signal a partial failure for the OTUCn and signal a failure only for the affected ODUk services; circuitry adapted to adjust overhead associated with the OTUCn based on the OTSi failure; and circuitry adapted to apply actions on the affected ODUk services subsequent to the OTSi failure. The signal the partial failure can include signaling one or more of a partial Alarm Indication Signal (P-AIS), a partial Backward Defect Indication (P-BDI), and a partial Server Signal Fail (P-SSF) for the OTUCn, and wherein the signal the failure can include signaling one or more of an Alarm Indication Signal (AIS), a Backward Defect Indication (BDI), and a Server Signal Fail (SSF) only for the affected ODUk services.

Again, in various embodiments, the present disclosure relates to Flexible Optical (FlexO)/ZR partial survivability. The objective is to provide subrating at the FlexO/ZR interface layer. In this manner, high-speed interfaces, e.g., <NUM>, <NUM>, can be reduced in bandwidth to support applications with different reach/application requirements. The present disclosure includes a partial-Alarm Indication Signal (AIS), partial-Backward Defect Indicator (BDI) and partial-Server Signal Fail (SSF) signal, techniques for handling overhead, and moving of ODUk services and mesh restoration. This approach includes OTN FlexO or OIF ZR and addresses the use case of partial survivability when an interface is subrated. Standards typically define fixed rate FlexO/ZR interfaces, and do not define scenarios where interfaces are subrated dynamically (change of rate). One use case includes optical networks where modems are configured for variable rates based on available margin. This application requires dynamic capacity changes on optical modem coherent interfaces, and this disclosure explores the protocol implications of doing so.

Also, in various embodiments, the present disclosure relates to partial survivability for multi-carrier and multi-module optical interfaces such as Optical Transport Network (OTN), Flexible Ethernet (FlexE), and Flexible Optical (FlexO). As described herein, a failure of any OTSi carriers, the entire OTUCn network interface associated with the OTSi carriers is considered as failed and consequent actions are applied across the entire Optical Data Unit Cn (ODUCn) associated with the OTUCn, affecting all ODUk services within the ODUCn. This also applies similarly to FlexO client interfaces carrying a single High Order (HO) OTUCn and multiple Low Order (LO) Optical Data Unit k (ODUk) services. Note, the term services can be used interchangeably with clients, e.g., ODUk services and FlexE clients. Systems and methods described herein apply consequent actions to only the channelized services which are directly impacted by failed carriers and allow other channelized services to remain intact within the network interface. The consequent actions are not applied across the entire interface (e.g., ODUCn layer for an OTUCn interface) but instead prescriptively applied for each ODUk service (e.g., an ODUk within an OTUCn interface), as required. The signal fail conditions can be selective to events located in a specific OTSi/interface (e.g., degraded defect (dDEG[i]), Loss of Signal (LOS), Loss of Frame (LOF), etc.). A new partial-Alarm Indication Signal (AIS), partial-Backward Defect Indicator (BDI) and partial-Server Signal Fail (SSF) signal is defined as a replacement signal for only the HO OTUC/ODUC slices being affected. The partial-AIS/BDI signal can work along with RS regen nodes.

Partial Survivability for multi-carrier or multi-module interfaces determines specifically which optical carriers are failed for a network service, using specific triggers such as signal degrade, loss of frame delineation (LOF), loss of signal (LOS), etc. which are associated with the specific optical carrier or module. It is able to correlate the available bandwidth assignment information for each of the channelized services within the network service to the failed optical carriers. For those channelized services which occupy bandwidth which is impacted by the failed optical carriers, it will apply consequent actions to signal that traffic is impacted for that channelized service.

Advantageously, the systems and methods provide an ability for an interface to be declared as partially failed with P-AIS, P-SSF and P-BDI statuses and signaling. Further, the systems and methods use various techniques to ensure overhead (OH) survives in the event the first OTUC/ODUC slice is failed (which normally carries various OH). The systems and methods determine which services are up or down on a partially failed interface. Also, the systems and methods can automatically adjust the size of a service based on capacity being automatically adjusted within the interface. Further, the systems and methods can shuffle (substitute) failed and working services based on priority. The systems and methods can disassociate provisioned services (tributary ports in OTN) within an interface from all tributary slots, via an edit instead of having to delete and re-provision the services. The systems and methods can recognize the opportunity to adjust interface capacity to provide greater Signal-to-Noise margin in optical networks, without affecting active services. The systems and methods can exchange partially failed interface information with other networking layers (i.e. Layer <NUM>). Also, the systems and methods allow the server layer (Layer <NUM>) to deprioritize or completely suspend restoration of a partially failed interface's wavelength(s).

The systems and methods provide greater availability and reliability of services within high capacity, multi-channel networks. These partial-survivability systems and methods can complement control-plane and mesh restoration techniques as well as Software Defined Networking (SDN) schemes. As a result, there are reduced network impacts due to fewer services being affected by a partial failure of a group interface. Again, some services can be maintained on partially failed interfaces without declaring an entire ODUCn down. Higher priority services can be maintained on the existing interfaces, reducing the impact of moving the services or declaring them as operationally down. Again, as a result, restoring only those services which are failed requires fewer network resources. If restoring at Layer <NUM> (TDM), a network only requires enough bandwidth elsewhere to accommodate the failed services, because non-failed services do not need to be restored. Consuming less capacity per interface can result in a wavelength requiring less SNR and therefore could provide additional net system margin back to the network (e.g., downshift from <NUM> using 8QAM to <NUM> using QPSK because the additional <NUM> capacity offered by the 8QAM is not usable by the <NUM> services). Such additional net system margin can be used by other wavelengths to expand their capacity with flexible, software programmable optical modems. Partially failed interfaces can be reduced in size to eliminated failed bandwidth, additionally freeing up network (Layer <NUM>) bandwidth.

Referring to <FIG>, in an embodiment, a network diagram illustrates an network <NUM> with various interconnected nodes <NUM> (illustrated as nodes 12A - 12J). The nodes <NUM> are interconnected by a plurality of links <NUM>. The nodes <NUM> communicate with one another over the links <NUM> through Layer <NUM> (L0) such as optical wavelengths (DWDM), Layer <NUM> (L1) such as OTN, Layer <NUM> (L2) such as Ethernet, MPLS, etc., and/or Layer <NUM> (L3) protocols. The nodes <NUM> can be network elements which include a plurality of ingress and egress ports forming the links <NUM>. An example node implementation is illustrated in <FIG>. The network <NUM> can include various services or calls between the nodes <NUM>. Each service or call can be at any of the L0, L1, L2, and/or L3 protocols, such as a wavelength, a Subnetwork Connection (SNC), a Label Switched Path (LSP), etc., and each service or call is an end-to-end path or an end-to-end signaled path and from the view of the client signal contained therein, it is seen as a single network segment. The nodes <NUM> can also be referred to interchangeably as network elements (NEs). The network <NUM> is illustrated, for example, as an interconnected mesh network, and those of ordinary skill in the art will recognize the network <NUM> can include other architectures, with additional nodes <NUM> or with fewer nodes <NUM>, etc..

The network <NUM> can include a control plane <NUM> operating on and/or between the nodes <NUM>. The control plane <NUM> includes software, processes, algorithms, etc. that control configurable features of the network <NUM>, such as automating discovery of the nodes <NUM>, capacity on the links <NUM>, port availability on the nodes <NUM>, connectivity between ports; dissemination of topology and bandwidth information between the nodes <NUM>; calculation and creation of paths for calls or services; network level protection and restoration; and the like. Example control planes may include Automatically Switched Optical Network (ASON) as defined in ITU-T G. <NUM>, Architecture for the automatically switched optical network (ASON) (<NUM>/<NUM>); Generalized Multi-Protocol Label Switching (GMPLS) Architecture as defined in IETF Request for Comments (RFC): <NUM> (<NUM>/<NUM>) and the like; Optical Signaling and Routing Protocol (OSRP) from Ciena Corporation which is an optical signaling and routing protocol similar to Private Network-to-Network Interface (PNNI) and Multi-Protocol Label Switching (MPLS); or any other type control plane for controlling network elements at multiple layers, and establishing connections among nodes. Those of ordinary skill in the art will recognize the network <NUM> and the control plane <NUM> can utilize any type of control plane for controlling the nodes <NUM> and establishing, maintaining, and restoring calls or services between the nodes <NUM>.

An SDN controller <NUM> can also be communicatively coupled to the network <NUM> through one or more of the nodes <NUM>. SDN is an emerging framework which includes centralized control decoupled from the data plane. SDN provides the management of network services through abstraction of lower-level functionality. This is done by decoupling the system that makes decisions about where traffic is sent (the control plane) from the underlying systems that forward traffic to the selected destination (the data plane). SDN works with the SDN controller <NUM> knowing a full network topology through configuration or through the use of a controller-based discovery process in the network <NUM>. The SDN controller <NUM> differs from a management system in that it controls the forwarding behavior of the nodes <NUM> only, and performs control in real time or near real time, reacting to changes in services requested, network traffic analysis and network changes such as failure and degradation. Also, the SDN controller <NUM> provides a standard northbound interface to allow applications to access network resource information and policy-limited control over network behavior or treatment of application traffic. The SDN controller <NUM> sends commands to each of the nodes <NUM> to control matching of data flows received and actions to be taken, including any manipulation of packet contents and forwarding to specified egress ports.

Note, the network <NUM> can use the control plane <NUM> separately from the SDN controller <NUM>. Conversely, the network <NUM> can use the SDN controller <NUM> separately from the control plane <NUM>. Also, the control plane <NUM> can operate in a hybrid control mode with the SDN controller <NUM>. In this scheme, for example, the SDN controller <NUM> does not necessarily have a complete view of the network <NUM>. Here, the control plane <NUM> can be used to manage services in conjunction with the SDN controller <NUM>. The SDN controller <NUM> can work in conjunction with the control plane <NUM> in the sense that the SDN controller <NUM> can make the routing decisions and utilize the control plane <NUM> for signaling thereof. In the terminology of ASON and OSRP, SNCs are end-to-end signaled paths or calls since from the point of view of a client signal; each is a single network segment. In GMPLS, the connections are an end-to-end path referred to as LSPs. In SDN, such as in OpenFlow, services are called "flows. " Those of ordinary skill in the art will recognize that SNCs, LSPs, flows, or any other managed service in the network can be used with the systems and methods described herein for end-to-end paths. Also, as described herein, the term services is used for generally describing OTN connections in the network <NUM>.

Referring to <FIG>, in an embodiment, a block diagram illustrates an example node <NUM> for use with the systems and methods described herein. In an embodiment, the example node <NUM> can be a network element that may consolidate the functionality of a Multi-Service Provisioning Platform (MSPP), Digital Cross-Connect (DCS), Ethernet and/or Optical Transport Network (OTN) switch, Wave Division Multiplexed (WDM)/ Dense WDM (DWDM) platform, Packet Optical Transport System (POTS), etc. into a single, high-capacity intelligent switching system providing Layer <NUM>, <NUM>, <NUM>, and/or <NUM> consolidation. In another embodiment, the node <NUM> can be any of an OTN Add/Drop Multiplexer (ADM), a Multi-Service Provisioning Platform (MSPP), a Digital Cross-Connect (DCS), an optical cross-connect, a POTS, an optical switch, a router, a switch, a Wavelength Division Multiplexing (WDM) terminal, an access/aggregation device, etc. That is, the node <NUM> can be any digital system with ingress and egress digital signals and switching of channels, timeslots, tributary units, etc. While the node <NUM> is generally shown as an optical network element, the systems and methods contemplated for use with any switching fabric, network element, or network based thereon. Specifically, in the systems and methods described herein, the node <NUM> is an OTN capable network element, supporting OTSi, OTUCn, and ODUCn.

In an embodiment, the node <NUM> includes common equipment <NUM>, one or more line modules <NUM>, and one or more switch modules <NUM>. The common equipment <NUM> can include power; a control module; Operations, Administration, Maintenance, and Provisioning (OAM&P) access; user interface ports; and the like. The common equipment <NUM> can connect to a management system <NUM> through a data communication network <NUM> (as well as a Path Computation Element (PCE), SDN controller, OpenFlow controller, etc.). The management system <NUM> can include a network management system (NMS), element management system (EMS), or the like. Additionally, the common equipment <NUM> can include a control plane processor, such as a controller <NUM> illustrated in <FIG> configured to operate the control plane as described herein. The node <NUM> can include an interface <NUM> for communicatively coupling the common equipment <NUM>, the line modules <NUM>, and the switch modules <NUM> to one another. For example, the interface <NUM> can be a backplane, midplane, a bus, optical or electrical connectors, or the like. The line modules <NUM> are configured to provide ingress and egress to the switch modules <NUM> and to external connections on the links to/from the node <NUM>. In an embodiment, the line modules <NUM> can form ingress and egress switches with the switch modules <NUM> as center stage switches for a three-stage switch, e.g. a three-stage Clos switch. Other configurations and/or architectures are also contemplated. The line modules <NUM> can include optical transceivers, such as, for example, Beyond <NUM> OTN (FlexO, OTUCn, ODUCn, OTSi), Flex OTN, ODUflex, Flexible Ethernet, etc..

Further, the line modules <NUM> can include a plurality of optical connections per module and each module may include a flexible rate support for any type of connection, such as, for example, N x 100Gb/s (where N can be a real number), and any rate in between as well as future higher rates. The line modules <NUM> can include wavelength division multiplexing interfaces, short reach interfaces, and the like, and can connect to other line modules <NUM> on remote network elements, end clients, edge routers, and the like, e.g., forming connections on the links in the network <NUM>. From a logical perspective, the line modules <NUM> provide ingress and egress ports to the node <NUM>, and each line module <NUM> can include one or more physical ports. The switch modules <NUM> are configured to switch channels, timeslots, tributary units, packets, etc. between the line modules <NUM>. For example, the switch modules <NUM> can provide wavelength granularity (Layer <NUM> switching); OTN granularity such as ODUk, ODUCn, ODUflex, ODTUGs, etc.; Ethernet granularity; and the like. Specifically, the switch modules <NUM> can include Time Division Multiplexed (TDM) (i.e., circuit switching) and/or packet switching engines. The switch modules <NUM> can include redundancy as well, such as <NUM>:<NUM>, <NUM>:N, etc. In an embodiment, the switch modules <NUM> provide OTN switching and/or Ethernet switching.

Those of ordinary skill in the art will recognize the node <NUM> can include other components which are omitted for illustration purposes, and that the systems and methods described herein are contemplated for use with a plurality of different network elements with the node <NUM> presented as an example type of network element. For example, in another embodiment, the node <NUM> may not include the switch modules <NUM>, but rather have the corresponding functionality in the line modules <NUM> (or some equivalent) in a distributed fashion. For the node <NUM>, other architectures providing ingress, egress, and switching are also contemplated for the systems and methods described herein. In general, the systems and methods described herein contemplate use with any network element providing switching of channels, timeslots, tributary units, wavelengths, etc. and using the control plane. Furthermore, the node <NUM> is merely presented as one example node <NUM> for the systems and methods described herein.

Referring to <FIG>, in an embodiment, a block diagram illustrates a controller <NUM> to provide control plane processing and/or operations, administration, maintenance, and provisioning (OAM&P) for the node <NUM>, and/or to implement a Software Defined Networking (SDN) controller. The controller <NUM> can be part of the common equipment, such as common equipment <NUM> in the node <NUM>, or a stand-alone device communicatively coupled to the node <NUM> via the DCN <NUM>. In a stand-alone configuration, the controller <NUM> can be an SDN controller, an NMS, a PCE, etc. The controller <NUM> can include a processor <NUM> which is a hardware device for executing software instructions such as operating the control plane. The processor <NUM> can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the controller <NUM>, a semiconductor-based microprocessor (in the form of a microchip or chip set), or generally any device for executing software instructions. When the controller <NUM> is in operation, the processor <NUM> is configured to execute software stored within the memory, to communicate data to and from memory, and to generally control operations of the controller <NUM> pursuant to the software instructions. The controller <NUM> can also include a network interface <NUM>, a data store <NUM>, memory <NUM>, an I/O interface <NUM>, and the like, all of which are communicatively coupled to one another and to the processor <NUM>.

Note, while the controller <NUM> is shown as a separate module in the node <NUM> and as part of the common equipment <NUM>, the controller <NUM> and its associated functionality can be located elsewhere in the node <NUM> and even external to the node <NUM>. Also, the controller <NUM> can be implemented on the line modules <NUM>, the switch modules <NUM>, etc..

The network interface <NUM> can be used to enable the controller <NUM> to communicate on the DCN <NUM>, such as to communicate control plane information to other controllers, to the management system <NUM>, to the nodes <NUM>, and the like. The network interface <NUM> can include, for example, an Ethernet card (e.g., Gigabit Ethernet) or a wireless local area network (WLAN) card (e.g., <NUM>). The network interface <NUM> can include address, control, and/or data connections to enable appropriate communications on the network. The data store <NUM> can be used to store data, such as control plane information, provisioning data, OAM&P data, etc. The data store <NUM> can include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, flash drive, CDROM, and the like), and combinations thereof. Moreover, the data store <NUM> can incorporate electronic, magnetic, optical, and/or other types of storage media. The memory <NUM> can include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, flash drive, CDROM, etc.), and combinations thereof. Note that the memory <NUM> can have a distributed architecture, where various components are situated remotely from one another, but may be accessed by the processor <NUM>. The I/O interface <NUM> includes components for the controller <NUM> to communicate with other devices. Further, the I/O interface <NUM> includes components for the controller <NUM> to communicate with the other nodes, such as using overhead associated with OTN signals.

In an embodiment, the controller <NUM> is configured to communicate with other controllers <NUM> in the network <NUM> to operate the control plane for control plane signaling. This communication may be either in-band or out-of-band. Out-of-band signaling may use an overlaid Internet Protocol (IP) network such as, for example, User Datagram Protocol (UDP) over IP. In an embodiment, the controllers <NUM> can include an in-band signaling mechanism utilizing OTN overhead. The General Communication Channels (GCC) defined by G. <NUM> are in-band side channels used to carry transmission management and signaling information within Optical Transport Network elements. Based on the intermediate equipment's termination layer, different bytes may be used to carry control plane signaling. Other mechanisms are also contemplated for control plane signaling.

The controller <NUM> is configured to operate the control plane <NUM> in the network <NUM>. That is, the controller <NUM> is configured to implement software, processes, algorithms, etc. that control configurable features of the network <NUM>, such as automating discovery of the nodes, capacity on the links, port availability on the nodes, connectivity between ports; dissemination of topology and bandwidth information between the nodes; path computation and creation for connections; network level protection and restoration; and the like. As part of these functions, the controller <NUM> can include a topology database that maintains the current topology of the network <NUM> based on control plane signaling (e.g., HELLO messages) and a connection database that maintains available bandwidth on the links <NUM> again based on the control plane signaling. Again, the control plane is a distributed control plane; thus, a plurality of the controllers <NUM> can act together to operate the control plane using the control plane signaling to maintain database synchronization. In source-based routing, the controller <NUM> at a source node for a connection is responsible for path computation and establishing by signaling other controllers <NUM> in the network <NUM>, such as through a SETUP message. Path computation generally includes determining a path, i.e. traversing the links through the nodes from the originating node to the destination node based on a plurality of constraints such as administrative weights on the links, bandwidth availability on the links, etc..

Referring to <FIG>, in an embodiment, a network diagram illustrates an example of network connections <NUM>, <NUM>, <NUM> within a node <NUM> which have ODUk clients/services as channelized services being carried on an OTUCn network interface with multiple OTSi carriers. The network connections <NUM>, <NUM>, <NUM> include OTSi <NUM>, FlexO <NUM>, OTUCn <NUM>, and ODUCn <NUM>. The network services or clients are ODUk <NUM>. The OTSi <NUM> is defined in ITU Recommendation G. <NUM> "Optical transport network physical layer interfaces," (<NUM>/<NUM>). The OTSi is an optical signal that is placed within a network media channel for transport across the optical network. This may include a single modulated optical carrier or a group of modulated optical carriers or subcarriers. In this example, the network connection <NUM> includes four OTSi <NUM> and the network connections <NUM>, <NUM> each includes two OTSi <NUM>. The FlexO <NUM> is a group interface which includes multiple homogeneous OTN interfaces to support a higher rate client, e.g., n x OTUC1. The OTUCn <NUM> is a single network group interface, and in this example, there is one OTUCn for each of the network connections <NUM>, <NUM>, <NUM>. The OTUCn <NUM> and the ODUCn <NUM> are defined in G. <NUM> (<NUM>/<NUM>). The OTUCn contains an ODUCn <NUM>, and the ODUCn <NUM> contains an Optical Payload Unit (OPUCn). The ODUk <NUM> is a single channelized client or service, and in this example, there are six channelized services shown. The network connection <NUM> employs four OTSi <NUM> carriers and is carrying six ODUk <NUM> channelized services. The network connections <NUM>, <NUM> each employ two OTSi <NUM> carriers, and each carries three ODUk <NUM> channelized services.

Those of ordinary skill in the art will recognize the node <NUM> in <FIG> is shown with the three example network connections <NUM>, <NUM>, <NUM> for illustration purposes. Specifically, <FIG> illustrates the network connection <NUM> facing west and the network connections <NUM>, <NUM> facing east with each of the six ODUk <NUM> channelized services between the network connection <NUM> and between the network connections <NUM>, <NUM>. Other embodiments are also contemplated, such as the network connection <NUM> interfacing another network service of the same size (in <FIG>, the network connection <NUM> interfaces the network connection <NUM>, <NUM> which are each half the size of the network connection <NUM>).

Additionally, the examples described herein reference OTN, namely OTSi, OTUCn, ODUCn, and those of ordinary skill in the art will recognize the systems and methods described herein can also be applied to other techniques such as Flexible Ethernet or the like.

Again, typically upon a failure of any OTSi <NUM> carriers on any of the network connections <NUM>, <NUM>, <NUM>, the entire OTUCn <NUM> network group interface is considered to be failed and consequent actions are applied across the entire ODUCn <NUM> layer, affecting all the ODUk <NUM> services within. The same analogy can be used for FlexO client interfaces carrying a single HO OTUCn HO and multiple LO ODUk services LO. Again, the same analogy can be used for FlexE clients carried in a FlexE group interface.

Referring to <FIG>, in an embodiment, block diagrams illustrate bandwidth for network services and how it can be assigned using a time domain multiplexing scheme to specific optical carriers, OTSi. <FIG> illustrates how available bandwidth can be identified for network services. <FIG> illustrates how services can be allocated to available bandwidth and how that bandwidth can be carried across multiple optical carriers, OTSi. <FIG> illustrates a failure on a single optical carrier, OTSi, and how the bandwidth for the network services is identified and adjusted accordingly. In <FIG>, there are two OTSi <NUM>-<NUM>, <NUM>-<NUM> carriers with various boxes identifying a unit of bandwidth. To carry bandwidth on the OTSi <NUM>-<NUM>, <NUM>-<NUM> carriers, there is a FlexO/OTUCn adaptation <NUM> which maps bandwidth from the OTUCn <NUM> to the OTSi <NUM>-<NUM>, <NUM>-<NUM> carriers. Note, the concept of the OTSi <NUM> and the OTUCn <NUM> is meant to decouple Layer <NUM> OTN bandwidth (client layer) from Layer <NUM> DWDM bandwidth (server layer). Specifically, as new modulation formats emerge, optical bandwidth is decoupled from client/service bandwidth. In the OTUk scheme, each wavelength typically carried a single HO OTUk. With the OTSi <NUM> and the OTUCn <NUM>, there can be various combinations such as, for example, an OTUC4 (<NUM>) carried on two OTSi (each at <NUM>), and the like.

In <FIG>, it is shown that tributary slots from the FlexO/OTUCn adaptation <NUM> are assigned to tributary slots in the OTSi <NUM>-<NUM>, <NUM>-<NUM> carriers, and not necessarily on the same OTSi <NUM>-<NUM>, <NUM>-<NUM> carrier. At the adaptation layer into the FlexO / OTSiG (OTSi Group) only those tributary slots which are available can be considered. In this example, the tributary slots identified by <NUM> are carried by the OTSi <NUM>-<NUM> and the tributary slots identified by <NUM> and <NUM> are carried by the OTSi <NUM>-<NUM>. <FIG> shows how channelized services can be allocated to available bandwidth, and how that bandwidth can be carried across multiple carriers. In this example, channelized service #<NUM> and #<NUM> are carried entirely within the OTSi <NUM>-<NUM>, a channelized service #<NUM> is carried entirely within the OTSi <NUM>-<NUM>, but a channelized service #<NUM> is carried partially by each of the OTSi <NUM>-<NUM>, <NUM>-<NUM>. Same analogy can be used with FlexE clients assigned to calendar slots.

<FIG> shows a failure on a single optical carrier, the OTSi <NUM>-<NUM>, and how the system can identify and indicate that the bandwidth has been reduced for a given service. In this example, the failure of the OTSi <NUM>-<NUM> completely affects the services #<NUM> and #<NUM> and affects two of the eight tributary slots which are allocated to the channelized service #<NUM>. The channelized service #<NUM> is unaffected by the failure of the OTSi <NUM>-<NUM> since it is entirely carried on the OTSi <NUM>-<NUM>. If the channelized service #<NUM> is flexible, it can be automatically reduced to use only the usable bandwidth (six tributary slots in this example) to still carry service, albeit with lower bandwidth, during the temporary failure. The amount of available bandwidth would need to be apparent at the node <NUM> where the service is added/dropped so that the service can be throttled according to how much bandwidth it can use through the network. Also, the channelized services #<NUM> and #<NUM> can be restored while the channelized service #<NUM> does not need to be restored. Same analogy can be used with FlexE clients assigned to calendar slots.

In an OTUCn network, mesh restoration and the control plane <NUM> can be used to move or resize affected services. Detection of which services have failed (as opposed to those which are still able to carry traffic) in an interface can be accomplished by the controller <NUM>, an NMS, the SDN controller <NUM>, or the like. The detection can be accomplished via status monitoring for the service across the domain, by monitoring of fault points (with no hold-off / debounce being applied) at either the point of failure or at adjacent equipment, by an implied association maintained in the node of which service is carried on which optical carrier, and the like.

Services which have been identified as failed have multiple possible actions which could be applied. First, mesh restoration and the control plane <NUM> can be used to move or resize only the affected services, as opposed to all services from within the group interface, to available bandwidth within other existing interfaces in the network. In the example of <FIG>, this includes moving the channelized services #<NUM> and #<NUM> and resizing or moving the channelized service #<NUM>. Additionally, services within the affected interface could be shuffled, allowing higher prioritized services to be carried via the reduced bandwidth of the existing partially failed interface. In the example of <FIG>, this could include moving the channelized service #<NUM> and replacing it with the channelized service #<NUM> in the OTSi <NUM>-<NUM>, if, for example, the channelized service #<NUM> is a higher priority than the channelized service #<NUM>. Alternatively, this could include reducing the sizes of all of the channelized services such that they could all be carried on the OTSi <NUM>-<NUM>. Controllers across layer <NUM> and layer <NUM> can be integrated to create new interfaces which only need to be large enough to accommodate the services which need to be moved.

The node <NUM> is aware of the bandwidth within the network interface (OTUCn in this example) which is being carried by each optical carrier, OTSi. If any channelized services do not employ bandwidth that is impacted by the failed optical carriers (the OTSi <NUM>-<NUM> in this example), those channelized services will not have consequent actions applied and thus will continue to carry traffic through the network. So, as an example, when the OTSi <NUM>-<NUM> fails, the node <NUM> would determine that the bandwidth being carried by the OTSi <NUM>-<NUM> corresponds to the channelized services #<NUM>, #<NUM> and #<NUM>. Those individual channelized services would have consequent actions applied, but the channelized service #<NUM> would remain unaffected. Referring back to <FIG>, the consequent actions would be applied at the adaptation between the ODUk services and the ODUCn high order path.

Subsequent nodes <NUM> along the traffic path will be unaffected by the upstream optical carrier faults, and the channelized service will pass through regardless of whether it contains an alarm condition or not.

If the channelized service is flexible in how much capacity it can carry through a network, it may be possible for the channelized service to adapt to the partial failure of the network service. When specific tributary slots for a channelized service are failed due to the failed optical carrier (two tributary slots for the channelized service #<NUM> in the example of <FIG>), but other tributary slots are not failed because they are contained within an optical carrier that is not failed, the equipment may be able to temporarily adapt the size of the service to the number of non-failed tributary slots through the network service. This requires throttling of the service being carried within the channel at the points where it enters the network or moving it entirely across another path. Once the failure within the network has been recovered, the channelized service can also recover to its original capacity (or location).

Referring to <FIG>, in an embodiment, a flowchart illustrates a process <NUM> for shuffling services within a partially failed interface to move high priority services to non-failed tributary slots. The process <NUM> is implemented in or by a node <NUM>, e.g., through the control plane <NUM> or the SDN controller <NUM>, and is done via an Edit operation in order to prevent loss of any existing provisioning data that may result if any entity is deleted and re-added with new tributary slot assignments. In the example of <FIG>, the process <NUM> could be used to move the two tributary slots of the channelized service #<NUM> on the OTSi <NUM>-<NUM> to two tributary slots in the OTSi <NUM>-<NUM>.

Reassigning tributary slot assignments between two services within the same interface becomes a sequence of the following events in the process <NUM>. The process <NUM> includes disassociating the connection point for a first service from any tributary slots within the interface (step <NUM>). The Multiplex Structure Identifier (MSI) structure for the High Order OPU will now show those tributary slots as unallocated. The same analogy can be used for FlexE calendar slots. The egress tributary slots would be empty within the payload of the High Order OPU. Because there is no ingress data from the interface, the connection function for the service detects an AIS defect from the interface. Next, the process <NUM> includes assigning the connection point for a second service to use the tributary slots previously assigned to the first service (step <NUM>) and editing the connection point for the first service to assign the tributary slots previously assigned to the second service (step <NUM>).

Referring to <FIG>, in an embodiment, a flowchart illustrates an overhead processing process <NUM> which uses partial AIS and BDI signals and overhead relocation for partial survivability of multi-carrier and multi-module optical interfaces. The process <NUM> is performed by the node <NUM> to enable partial survivability, and the node <NUM> includes a plurality of optical carriers, OTSi, an OTUCn associated with the optical carriers, and a plurality of ODUk services. The process <NUM> initiates subsequent to detection of an optical carrier failure (step <NUM>). For example, in <FIG>, the OTSi <NUM>-<NUM> fails. As described herein, the optical carrier failure can be due to equipment failure, e.g., optical modems, as opposed to fiber cuts. The equipment failure affects a specific optical carrier whereas the fiber cuts can affect all optical carriers on the same fiber. Although the process <NUM> can operate with respect to fiber cuts where the optical carriers for an OTUCn are on different fibers.

The process <NUM> includes determining which ODUk services in the OTUCn are affected by the optical carrier failure (step <NUM>). Again, detection of which services have failed (as opposed to those which are still able to carry traffic) can be accomplished by the controller <NUM>, an NMS, the SDN controller <NUM>, or the like. In the example of <FIG>, the channelized services #<NUM> and #<NUM> would be the ones fully affected by the OTSi <NUM>-<NUM> failure and the channelized service #<NUM> would be partially affected.

The process <NUM> includes signaling partial AIS, partial BDI, and partial SSF for the OTUCn/ODUCn and AIS, BDI, and SSF for the affected services (step <NUM>). Again, ODUCn AIS is currently defined as all or nothing. The process <NUM> introduces the concept of squelching only selected (failed) ODUC slices, resulting in new P-AIS, P-BDI, and P-SSF states for the overall OTUCn/ODUCn. These P-AIS, P-BDI, and P-SSF states are applied to OTUC and ODUC which are affected by the optical carrier failure. Again, consequential actions by the node <NUM>, the OTN network, etc., are applied at the ODUk service level based on the HO P-AIS, and P-SSF. Specifically, the affected ODUk services see the HO AIS, and SSF states whereas the unaffected ODUk services do not. The new P-AIS, P-BDI, and P-SSF can be a replacement signal and STAT field for only the HO OTUC/ODUC slices which are affected by the optical carrier failure. The actions can include resizing, redialing/restoring, moving, etc. performed by a control plane, SDN, etc. Again, resizing can be used when a service is only partially affected by the optical carrier failure such that the service remains with the operational timeslots. The redialing/restoring can include control plane restoration such as mesh restoration and it is only performed on the services with the AIS, BDI, and SSF. That is, operational services not affected by the optical carrier failure do not need restoration. The moving can include replacing the affected services with unaffected services as described herein, such as based on priority. Specifically, an OTUCn in any of the P-AIS, P-BDI, and P-SSF states means this OTUCn has failed optical carriers and operational optical carriers, hence a partial survivability state.

The process <NUM> includes determining if the OTUCn overhead has been affected by the optical carrier failure (step <NUM>). Specifically, in order to continue operating an OTUCn interface in a partial fault/AIS state, some critical overhead must be moved from failed OTUC/ODUC slices onto good ones. In an OTUCn, OTUCn, ODUCn, and OPUCn contain n instances of OTU, ODU, OPU overhead, numbered <NUM> to n. In some embodiments, the first instance (OTUC #<NUM>, ODUC #<NUM>, and OPUC #<NUM>) overhead is used for various OAM&P purposes. For example, the first OTUC slice can be used to carry specific overhead such as trace identification information (TTI) and General Communication Channel (GCC) data. At step <NUM>, it is determined whether or not the optical carrier failure affects the OTUCn overhead, such as, for example, the optical carrier affecting the first OTUC #<NUM> slice.

If the optical carrier failure affects the OTUCn overhead (step <NUM>), the process <NUM> includes moving overhead from failed OTUC slices to an operational OTUC slice (step <NUM>). If the optical carrier failure does not affect the overhead (step <NUM>) then after step <NUM>, the process <NUM> includes operating the OTUCn in a partial fault/AIS state with the unaffected optical carriers carrying unaffected services (step <NUM>).

The moving in step <NUM> can be achieved via various techniques. First, a source (transmitter) can use the P-BDI backward/remote defect indication to decide which OTU/ODU to send its overhead with a bit signaling overhead presence. In cases of bi-directional failures, the transmitter can also use its receiver status. Basically, if it receives a local or remote failure indicator, then the overhead is moved. Second, the source can broadcast the overhead to all slices, with identical copies. A weighted scheme can be used by the sink (receiver) so that it can decide which overhead is valid in cases where there are discrepancies.

With partial survivability, integration across Layer <NUM> and Layer <NUM> controllers could allow right-sizing of existing and new interfaces based explicitly on the services which need to be carried. The existing, partially failed interface, could be resized since it does not currently need to accommodate the failed services. This could potentially free up optical bandwidth (wavelengths) by adjusting the make-up of the interface (add or remove OTSi). A new interface which is created only requires enough bandwidth to accommodate only the failed services which need to be moved, as opposed to all services from within the failed interface. This could result in the consumption of less optical bandwidth (wavelengths) within the optical network. The total capacity of an interface can be adjusted when it is not possible for any service in the client layer to use the stranded capacity. This generally results in a wavelength which requires less SNR, and therefore could provide additional net system margin back to the network (e.g., downshift from <NUM> using <NUM> Quadrature Amplitude Modulation (QAM) to <NUM> using Quadrature Phase Shift Keying (QPSK) because the additional <NUM> capacity offered by the 8QAM is not usable by the <NUM> services). The resultant required SNR for the lower capacity modulation (from 8QAM to QPSK) can be absorbed by the network once the margin has been mined from the wavelength (e.g., via power spectral averaging) and used for additional capacity on other wavelengths.

Referring to <FIG>, in embodiments, network diagrams illustrate a network <NUM> illustrating various OTUCn network configurations. <FIG> illustrates the OTUCn network <NUM> without partial survivability, <FIG> illustrates the OTUCn network <NUM> with partial survivability and <FIG> illustrates the OTUCn network <NUM> with partial survivability and with flexible size services. The OTUCn network <NUM> is shown with five example nodes or network elements, namely NE A, NE B, NE C, NE D, NE E. The network elements NE A, B, D, E are cross-connects (XC) and the network element NE C is a regenerator (3R) from the perspective of example services #<NUM>, #<NUM>, #<NUM>. There are two optical carriers OTSi between each of the network elements with the NE A and the NE E as end nodes and the NE B, NE C, NE Das intermediate nodes. The service #<NUM> is between the NE A and the NE E traversing each of the NE B, NE C, NE D. The service #<NUM> is between the NE A and the NE D traversing each of the NE B, NE C. The service #<NUM> is between the NE B and the NE D traversing the NE C.

In all of the <FIG>, an optical carrier failure is shown on the first optical carrier OTSi between the NE B and the NE C. In <FIG>, the OTUCn network does not have partial survivability. As such, AIS and BDI are shown on all of the services #<NUM>, #<NUM>, #<NUM>. After the optical carrier failure, ODUk BDI is sent backward on each of the services #<NUM>, #<NUM>, #<NUM> and an ODUk AIS is sent forward on each of the services #<NUM>, #<NUM>, #<NUM>. Similarly, there is an OTUCn BDI and ODUCn BDI sent backward on the OTUCn and ODUCn, respectively, and an ODUCn AIS is sent forward on the ODUCn. All of the services #<NUM>, #<NUM>, #<NUM> are down, whether or not they are affected by the optical carrier failure.

In <FIG>, the OTUCn network <NUM> can implement the systems and methods described herein for partial survivability, such as the process <NUM>. For example, assume the services #<NUM>, #<NUM> are affected by the optical carrier failure between the NE B and NE C whereas the service #<NUM> is not. After the optical carrier failure, ODUk BDI is sent backward only on the services #<NUM>, #<NUM> and an ODUk AIS is sent forward only on the services #<NUM>, #<NUM>. Similarly, there is an OTUCn P-BDI and ODUCn P-BDI sent backward on the OTUCn and ODUCn, respectively, and an ODUCn P-AIS is sent forward on the ODUCn. Accordingly, only the services #<NUM>, #<NUM> are down whereas the service #<NUM> is unaffected and the OTUCn/ODUCn is now operated in a partial failure situation as designated by the P-AIS, P-BDI, and P-SSF. The OTUCn network <NUM> can apply consequential actions only to the services #<NUM>, #<NUM>, i.e., restoration, resizing, moving, etc..

In <FIG>, the OTUCn network <NUM> can implement the systems and methods described herein for partial survivability, such as the process <NUM>, as well as service resizing. In this example, assume the service #<NUM> is fully affected by the optical carrier failure between the NE B and NE C, the service #<NUM> is partially affected by the optical carrier failure, and the service #<NUM> is not. After the optical carrier failure, ODUk BDI is sent backward only on the service #<NUM> and an ODUk AIS is sent forward only on the service #<NUM>. The service #<NUM> is resized to occupy only its tributary slots on the second, unaffected optical carrier, thus operating with reduced capacity. Similarly, there is an OTUCn P-BDI and ODUCn P-BDI sent backward on the OTUCn and ODUCn, respectively, and an ODUCn P-AIS is sent forward on the ODUCn. Accordingly, only the service #<NUM> is down whereas the service #<NUM> is unaffected and the service #<NUM> operates with reduced capacity, and the OTUCn/ODUCn is now operated in a partial failure situation as designated by the P-AIS, P-BDI, and P-SSF. The OTUCn network <NUM> can apply consequential actions only to the service #<NUM>, i.e., restoration, resizing, moving, etc..

Referring to <FIG>, in an embodiment, block diagrams illustrate OTUCn/ODUCn overhead. Specifically, <FIG> illustrates the OTUCn frame structure, frame alignment and OTUCn overhead, and <FIG> illustrates the ODUCn frame structure, ODUCn and OPUCn overhead. As can be seen in <FIG>, the overhead is different for OTUC #<NUM>, ODUC #<NUM>, and OPUC #<NUM> versus #<NUM> to #n. Specifically, in <FIG>, the OTUC #<NUM> carriers the OTN Synchronization Message Channel (OSMC) and the Trail Trace Identifier (TTI) whereas #<NUM> to #n do not. In <FIG>, the ODUC #<NUM> carriers the Path Monitoring (PM), Tandem Connection Monitoring (TCM), Automatic Protection Switching (APS), Protection Communication Channel (PCC), Payload Type (PT), and TTI whereas #<NUM> to #n do not. As such, the process <NUM> includes various techniques to ensure this overhead survives in the partial survivability state by moving this overhead out of the OTUC #<NUM> or ODUC #<NUM> when that is affected by the optical carrier failure.

The aforementioned descriptions of partial survivability focus on an OTUCn implementation. Those of ordinary skill in the art will recognize the same approaches can be used with FlexE. Specifically, a FlexE group can include multiple FlexE clients and a failure of one FlexE server or interface within the group can lead to partial survivability. Here, the services are FlexE clients and the network interface is the FlexE group. The failed FlexE clients can be determined based on the calendar slots in the FlexE shim. Instead of an AIS, FlexE would have a partial LF, and instead of a BDI, FlexE would have a Remote PHY Fault (RPF).

As described herein, the concept of partial survivability was originally conceived when multiple interfaces (OTSi) in a group (OTSiG) are used to carry a single OTUCn service. Standard behavior would require that when a member interface (OTSi) in the group fails, the whole group fails. Partial survivability will keep some services alive and running hitlessly even in the event of failure with another OTSi in the group. This concept applies well for hitless subrating use cases.

FlexO/OTUCn interfaces include <NUM> OTUC slices and FlexO instances. As is known in the art, a slice here is a <NUM> signal. Similarly, 400ZR (and future 800ZR/LR) interfaces include the concept <NUM> ZR frame slices. For example, 400ZR is described in OIF Implementation Agreement 400ZR, OIF-400ZR-<NUM>, March <NUM>, <NUM>.

In a variable rate application, the user would typically provision a maximum rate to operate the interface. An interface can then be "downshifted" or subrated, to improve margins or support an alternative optical protection path. Some OTUC slices and FlexO/ZR instances are not transported anymore on the subrated interface while other instances (and services mapped to it) are still operating cleanly. For example, an OTUC8 includes eight <NUM> OTUC slices and may be subrated to <NUM>, losing one of the slices. Partial failure (P-AIS, P-BDI and P-SSF) or unequipped status can be applied to some of the OTUC slices and FlexO/ZR instances on the interface.

All the same aspects of service management described above apply to subrating use cases as well. Controllers would need to be able to detect and identify interfaces that have changed capacity. Services can be shuffled within a downshifted interface to enable the higher priority services to survive regardless of which portion of the interface has been failed. Interfaces can be managed by integrated Layer <NUM> and Layer <NUM> controllers to optimize optical bandwidth (wavelengths) based on services which are still active and those which have failed and need to be moved.

Additionally, it is possible to combine subrating for an individual interface with multiple OTSi grouped interfaces, where all lambdas for the FlexO group interface are downshifted in capacity equally, reducing the overall group capacity.

<FIG> is a block diagram of circuitry <NUM>, in a coherent optical modem that can be used in a network element, for supporting FlexO/ZR partial survivability. The coherent optical modem can be FlexO, and, in other embodiments, a ZR interface. <FIG> illustrates the functional components with the right side including a Digital Signal Processor (DSP) <NUM> that connects to an electro-optic device on the right (not shown). The DSP <NUM> connects to Forward Error Correction (FEC) circuitry <NUM> which connects to mapping circuitry <NUM>. The mapping circuitry <NUM> connects to gearbox circuits <NUM> that connect to FlexO circuitry <NUM>. The FlexO circuitry <NUM> connects to deskew circuitry <NUM> that connects to <NUM> client interface circuitry <NUM>.

The mapping circuitry <NUM> is configured to map data, and when the capacity of the line interface changes, some FlexO instances will be drop, and P-AIS/BDI/SSF will be associated with those FlexO/ZR instances (and OTUC slices) that are partially failed in such scenario. In <FIG>, this example shows how an <NUM> → <NUM> application could be hitless for some services from the protocol's perspective, and some FlexO/ZR instances are failed while other are operating hitlessly (partial survivability).

Such approach could also be applicable to standard FlexO-x-DO (OFEC) or FlexO-x-DSH (CFEC) interfaces, where the rates reduce in capacity from a standard rate (e.g., <NUM>) to another (e.g., <NUM>). It is not just for proprietary interfaces and can simplify operation of standards ones as well.

<FIG> is a flowchart of a process <NUM> of FlexO/ZR partial survivability. The process <NUM> can be implemented as a method, via circuitry, via a coherent modem, via a network element, etc. The process <NUM> includes operating an optical interface at a first rate (step <NUM>); subsequent to a requirement to subrate the optical interface to a second rate, determining which one or more services are affected (step <NUM>); signaling one or more partial failures for the one or more affected services (step <NUM>); and operating the optical interface at a second rate that is less than the first rate.

The optical interface can be a Flexible Optical (FlexO) interface. The FlexO interface can include a plurality of Optical Transport Unit C (OTUC) slices each at about 100Gb/s, and wherein the one or more partial failures are for one or more OTUC slices.

The optical interface can be a ZR interface. The FlexO interface can include a plurality of ZR slices each at about 100Gb/s, and wherein the one or more partial failures are for one or more ZR slices.

The one or more partial failures can be signaled through one or more of a partial Alarm Indication Signal (P-AIS), a partial Backward Defect Indication (P-BDI), and a partial Server Signal Fail (P-SSF). The process <NUM> can further include adjusting overhead of the optical interface based on the one or more partial failures. The process <NUM> can further include adjusting one or more of the one or more affected services based on priority.

The requirement to subrate can be due to any of optical margin and a requirement to support an alternate path. The optical interface can be part of an Optical Tributary Signal (OTSi).

It will be appreciated that some embodiments described herein may include one or more generic or specialized processors ("one or more processors") such as microprocessors; Central Processing Units (CPUs); Digital Signal Processors (DSPs): customized processors such as Network Processors (NPs) or Network Processing Units (NPUs), Graphics Processing Units (GPUs), or the like; Field Programmable Gate Arrays (FPGAs); and the like along with unique stored program instructions (including both software and firmware) for control thereof to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the methods and/or systems described herein. Alternatively, some or all functions may be implemented by a state machine that has no stored program instructions, or in one or more Application Specific Integrated Circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic or circuitry. Of course, a combination of the aforementioned approaches may be used. For some of the embodiments described herein, a corresponding device in hardware and optionally with software, firmware, and a combination thereof can be referred to as "circuitry configured or adapted to," "logic configured or adapted to," etc. perform a set of operations, steps, methods, processes, algorithms, functions, techniques, etc. on digital and/or analog signals as described herein for the various embodiments.

Moreover, some embodiments may include a non-transitory computer-readable storage medium having computer readable code stored thereon for programming a computer, server, appliance, device, processor, circuit, etc. each of which may include a processor to perform functions as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), Flash memory, and the like. When stored in the non-transitory computer readable medium, software can include instructions executable by a processor or device (e.g., any type of programmable circuitry or logic) that, in response to such execution, cause a processor or the device to perform a set of operations, steps, methods, processes, algorithms, functions, techniques, etc. as described herein for the various embodiments.

Claim 1:
A method (<NUM>), implemented via a coherent modem with circuitry (<NUM>), the method (<NUM>) comprising steps of:
operating (<NUM>) an optical interface at a first rate; and
subsequent (<NUM>) to a requirement to subrate the optical interface to a second rate:
(<NUM>) determining which one or more services are affected;
(<NUM>) signaling (<NUM>) one or more partial failures for the one or more affected services; and
(<NUM>) operating (<NUM>) the optical interface at a second rate that is less than the first rate.