Future Wei Technologies, Inc.

Huawei Technologies Co., Limited

Young Lee

Greg M Bernstein

Linda Dunbar

James Neil Guichard

Dhruv Dhody

Haomian Zheng

Yangsong Xia

Ricard Vilalta

Lucy Yong

Kaippallimalil Mathew John

Italo Busi

Jianrui Han

T Benjamin Mack-Crane

Hong Zhang

Yufei Wang

Wei Wang

Robert Sultan

Maarten Vissers

Peter J Ashwood-Smith

Jie Dong

Shibi Huang

Yijun Xiong

Mingui Zhang

Sam K Aldrin

Susan Hares

Satish Karunanithi

Greg Bernstein

A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport. The method includes setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Transporting MTNC-ID over SRV6-enabled dataplane for 5G transport

A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) header for fifth generation (5G) transport. The method receives a data packet that includes an MTNC-ID in a data plane header of the data packet. The MTNC-ID is extracted from the data plane header of the data packet, and is encapsulated in an argument field in a last segment of a segment list (SL[0]) of the SRV6 header of the data packet. An instruction for forwarding the MTNC-ID is encapsulated within a function field in the SL[0] of the SRH of the data packet. The data packet is transmitted over a SRV6 enabled data plane domain along a forwarding path corresponding to the MTNC-ID.

Transporting MTNC-ID over SRV6-header for 5G transport

A method performed by a Next Generation Node B (gNB) in a communications system implementing User Datagram Protocol (UDP) comprises indicating that a data packet comprises a multi-transport network context-identifier (MTNC-ID) corresponding to a forwarding path and being associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for traffic forwarding on the forwarding path, inserting the MTNC-ID into a Generic UDP Encapsulation (GUE) header of the data packet, and transmitting the data packet to a network element (NE) in the communications system based on the forwarding path corresponding to the MTNC-ID.

Transporting a multi-transport network context-identifier (MTNC- ID) across multiple domains

An apparatus comprising an application cross-stratum optimization (CSO) gateway (ACG) coupled to an application layer that handles a plurality of servers, a network CSO gateway (NCG) coupled to a network layer that handles a plurality of network nodes and configured to communicate with the ACG using a CSO protocol (CSOP), and a CSO interface established between the ACG and the NCG that enables the exchange of a plurality of CSOP messages to allow joint application-network resource allocation, provisioning, and optimization. Also disclosed is a network apparatus implemented method comprising sending a user profile from a user plane to an application plane, sending an application profile from the application plane to a network plane via a CSO interface between an ACG and a NCG, and sending network capability information from the network plane to the application plane via the CSO interface.

Cross-stratum optimization protocol across an interface between the service stratum and the transport stratum

A method for establishing end-to-end tunnels extending across multiple domains using a network element. The method includes receiving a request from a customer controller to implement a virtual network (VN) created by the customer controller, wherein the VN identifies the end-to-end tunnels extending across the multiple domains, mapping the VN to available resources based on network constraints in response to the request, and transmitting, after the VN has been mapped, a message to a network controller managing one of the domains that includes a network path used to form a portion of one of the end-to-end tunnels, wherein the message includes an association object having a Type-Length-Value (TLV) field containing a virtual network identifier binding the network path to the VN.

Method of establishing relationships between sets of label switched paths and virtual networks

A method for establishing a tunnel between VTEPs includes receiving at an SDN controller a tunnel creation request to establish a VxLAN tunnel from a first VTEP to a second VTEP, determining a VxLAN tunnel of network nodes coupling the first VTEP to the second VTEP, assigning a SvcPI to the VxLAN tunnel, and sending a tunnel initiation command to the first VTEP, the tunnel initiation command causing the first VTEP to convert an Ethernet frame to a path-ID frame by adding an NSH encapsulation header and to forward the path-ID frame to the next network node in the VxLAN tunnel.

NSH encapsulation for traffic steering

A network analytics engine predicts impairment of one or more communications links included in a current data path being used to transmit data through a network, and transmits information indicating the predicted impairment to a network controller in a warning message. In response to receiving the warning message, the network controller identifies potential alternative data paths that exclude any communication links predicted to experience an impairment. Before setting up an alternative data path, however, the network controller waits for a fault notification confirming the predicted impairment. If the fault notification is received before expiration of a waiting period, the network controller sets up one of the potential alternative data paths in place of the current data path.

Control and management for impairment-aware optical network

A method implemented by a central controller is provided. The method includes receiving traffic monitoring information from a client, and sending a traffic monitor request to a network controller, the traffic monitor request requesting the network controller to monitor one or more traffic parameters based on the traffic monitoring information. The method further includes receiving a traffic report from the network controller, and responsive to determining that a monitored traffic parameter in the traffic report does not satisfy a condition specified by the traffic monitoring information, initiating a scaling operation based on data contained in the traffic report.

Telemetry aggregation and network autonomic scaling

A method of negotiating services. The method includes transmitting a service request to a provider device. The service request includes a base level of service at a base cost and alternative levels of service each at an alternative cost. Each of the alternative levels of service includes an alternative service parameter that has been downgraded relative to a corresponding base level service parameter. The alternative cost is less than the base cost. The method includes receiving a confirmation message from the provider device. The confirmation message indicates whether the base level of service or an alternative level of service has been accepted by the provider device. The method also includes receiving data at the base level of service or at the one of the one or more negotiated levels of service in accordance with the confirmation message.

Dynamic negotiation models in software-defined networks

A method implemented by a customer network controller (CNC) in a network comprises storing, by a memory of the CNC, a mapping between a virtual local area network (VLAN) identifier (ID) of a VLAN, an application ID of an application executed in the VLAN, and a service policy associated with the application, the service policy defining a network requirement for the application, the VLAN being associated with a customer edge (CE), transmitting, by a transmitter of the CNC, a tunnel creation request comprising the VLAN ID, the application ID, and the service policy, and storing, by the memory, a tunnel ID of a tunnel established in response to the tunnel creation request, the tunnel defining a path between an ingress provider edge (PE) node and an egress PE node that satisfies the service policy.

Controller based service policy mapping to establish different tunnels for different applications

A data center interconnection (DCI) network may comprise a data center controller (DCC) managing a plurality of data centers (DCs) interconnected by a provider network managed by a network provider controller (NPC). The provider network may be an OpenFlow based software defined networking (SDN) transport network. The DCC may initiate a virtual network service (VNS) negotiation with the NPC to connect the DCs and may specify a network abstraction granularity level. The NPC may respond by computing paths through the provider network accordingly and providing the DCC with one or more virtual networks (VNs). The DCC may compute virtual paths through the VNs and send virtual network element (VNE) connection setup commands to the DCC. The DCC may convert the VNE connection setup commands into network element (NE) commands to setup connections in NEs of the provider network. The DCC and the NPC may perform fault monitoring, detection, and recovery.

Software defined networking (SDN) controller orchestration and network virtualization for data center interconnection

NSH encapsulation for traffic steering establishing a tunnel between virtual extensible local area network (VxLAN) tunnel end points (VTEPS) using a NSH encapsulation header comprising a VxLAN header whose VNI field has been replaced by an NSH shim

A customer network controller (CNC) including a processor and a memory. The processor is configured to use a virtual private network (VPN)-specific service model for a VPN service and map the VPN-specific service model to one or more traffic engineering (TE)-specific parameters. The memory is coupled to the processor and configured to store a mapping between a VPN identification (ID) of the VPN service corresponding to the VPN-specific service model and a tunnel ID of either an existing TE tunnel or newly-established TE tunnel for the VPN service. The existing TE tunnel or the newly established TE tunnel satisfies the one or more TE-specific parameters.

Growing community of inventors

Plano, TX, United States of America

Young Lee