Future Wei Technologies, Inc.

Huawei Technologies Co., Limited

Intel Corporation

Cisco Technology, Inc.

Lin Han

Renwei Li

Katherine Zhao

Qianglin Quintin Zhao

Yingzhen Qu

Shujin Zhang

Tao Zhou

Ying Chen

Xiaoqian Wu

Lijun Dong

Uma S Chunduri

Alexander Clemm

Alvaro E Retana

Anantha Ramaiah

Abhijeet Ashok Kolekar

Ming Li

Xiaoyong Yi

Amol Khare

Mitesh Dalal

Kiran Makhijani

Xuesong Dong

Bisong Tao

Hongtao Yin

Shrirang Arvind Bage

Neal P Smith

Sivakumar Murugesu

Mario Barba Garcia

Ooi Ping Chuin

Yonghui Wu

John C Wong

Pinzhong Liu

Jose Gerardo Galindo Valadez

Chai Eong Boo

Tan Zheng Jing

Chan Wai Phang

Adrian Ortega Garcia

Shing Yung Lo

Soon Yueh Shen

Ong Gee Tat

Alan Previn Teres Alexis

Andrey Larionov

Yang Su Ming

Allen Hung

Tung Ean Ean

Armando Rubio Torroella

Ivan Gomes Castellanos

Soo Phing Tan

Ooi Joo Aik

An apparatus includes a network interface for connection to a network and a database configured to store traffic shaping parameters for a traffic shaping scheme for a plurality of classes of data packets. A database loading circuit is configured to obtain the traffic shaping parameters from in-band communication received in a data packet by the network interface and load the traffic shaping parameters into the database. One or more traffic shapers are configured to access the traffic shaping parameters in the database and apply the traffic shaping scheme according to the traffic shaping parameters to the plurality of classes of data packets received by the network interface.

Systems and methods for differentiation of service using in-band signaling

A method implemented by a network element (NE) in a network, comprising receiving, by the NE, an advertisement comprising preferred path route (PPR) information representing a PPR from a source to a destination in the network, the PPR information comprising a PPR identifier (PPR-ID) and a plurality of PPR description elements (PPR-PDEs) each representing an element on the PPR, receiving, by the NE, a data packet comprising the PPR-ID, and forwarding, by the NE, the data packet having the PPR-ID to a next element on the PPR based on the plurality of PPR-PDEs.

Advertising and programming preferred path routes using interior gateway protocols

The disclosure includes a method of performing congestion control by a server device in a network. The method includes setting an effective window equal to a congestion window; sending traffic including the effective window to a client device; receiving an acknowledgment (ACK) from the client device; incrementing the congestion window if the ACK is not a duplicate; and updating the effective window based at least partly on the incremented congestion window.

Method of traffic and congestion control for a network with quality of service

A method implemented by a network element (NE) in a network receiving, by the NE, an advertisement comprising preferred path route (PPR) information describing a path from an ingress NE to an egress NE in the network, the PPR information comprising a PPR identifier (PPR-ID) and an attribute associated with a resource to be reserved on the PPR, transmitting, by the NE, the advertisement comprising the PPR-ID and the attribute associated with the resource to be reserved on the PPR to another NE in the network, and updating, by the NE, a local forwarding database to include the PPR information in association with the egress NE in response to the NE being identified in the PPR information.

Resource reservation and maintenance for preferred path routes in a network

A method implemented by a network element (NE) comprises generating, by a processor, an Internet Protocol version 4 (IPv4) packet comprising an IPv4 header, a plurality of extension headers, and upper layer data, wherein the IPv4 packet indicates a total length of the IPv4 packet and a total length of the plurality of extension headers, indicating, by the processor, a protocol number associated with a first extension header of the plurality of extension headers in a protocol field of the IPv4 header, indicating, by the processor, a protocol used to encode the upper layer data of the IPv4 packet in a last protocol field of a last extension header of the plurality of extension headers, and transmitting, by a transmitter, the IPv4 packet to another NE.

Supporting internet protocol version 4 (IPv4) extension headers

A method implemented by an end user device in a network, comprises transmitting user service expectation data to a network element (NE) in the network, the user service expectation data describing an expected network attribute of a path between the end user device and a destination, receiving path aware network data from the NE in response to transmitting the user service expectation data describing the expected network attribute to the NE, the path aware network data comprising a path index, path quality information, and data plane information, the path index identifying the path, the path quality information describing a network attribute supported by the NE on the path, and the data plane information comprising information associated with a protocol by which to transmit a data packet along the path, and transmitting the data packet along the path based on the data plane information.

Systems and methods to implement path aware networking

A method implemented by a network element (NE) comprises receiving, by a receiver of the NE, an Internet Protocol (IP) version 4 (IPv4) packet from another NE, wherein the IPv4 packet comprises an IPv4 header, an extension header, and upper layer data, wherein the IPv4 header comprises a protocol number associated with the extension header, and wherein the IPv4 packet comprises a total length of the extension header, and processing, by a processor coupled to the receiver, the IPv4 packet based on the total length of the extension header.

The disclosure includes a method for establishing a connection with QoS assurance. In the method, a router receives a first IPv6 packet for establishing a first connection, wherein the first IPv6 packet includes a first QoS requirement for the first connection in a hop-by-hop extension header of the first IPv6 packet. Then, the router modifies the first IPv6 packet by setting first information in the hop-by-hop extension header of the first IPv6 packet, where the first information indicates that the router meets the first QoS requirement. Furthermore, the router sends the modified first IPv6 packet to a second router based on a destination IP address of the modified first IPv6 packet.

Quality of service for data transmission

A server implements a method for sending routing information in an Internet exchange point (IXP) network. The server receives control information from a first IXP member via the IXP network and obtains first routing information from the first IXP member via the IXP network, where the control information comprises an identifier of a second IXP member. Based on the first routing information and the control information, the server generates second routing information for the second IXP member, where the second routing information may be identical to the first routing information or a portion of the second IXP member. After the generation, the server sends the second routing information to the second IXP member. With the second routing information, the second IXP member may obtain some routing capability of the first IXP member.

Route control for internet exchange point

A network element (NE) configured as a local cloud switch point (CSP) comprises a memory configured to store remote virtual routing information in association with an identifier (ID) of a remote CSP in a mapping table, wherein the remote virtual routing information is associated with a remote virtual network associated with the remote CSP, and wherein the remote virtual routing information comprises a virtual extensible network (VXN) type identifier (ID), an address family ID (AFI), and a subsequent AFI (SAFI). The NE further comprises a processor coupled to the memory and configured to perform encapsulation on a data packet to generate a encapsulated data packet by adding an outer header to the data packet based on the AFI, adding a virtualization header to the data packet based on the VXN type ID, and adding an inner header to the data packet based on the SAFI. The NE further comprises a transmitter coupled to the processor and configured to transmit the encapsulated data packet to the remote CSP.

Method to support multi-protocol for virtualization

A method implemented by network element (NE) configured as a local cloud switch point (CSP), the method comprising receiving a first post message from a remote CSP via a cloudcasting network, wherein the first post message indicates a remote virtual extensible network (VXN) identifier (ID) of a remote virtual network attached to the remote CSP, receiving a first data packet from a local virtual network attached to the local CSP, wherein the first data packet is associated with the remote virtual network, performing encapsulation on the first data packet to produce a first encapsulated data packet by selecting an encapsulation header for the first data packet based on the remote VXN ID and not based on network protocols of the local virtual network and the remote virtual network, and sending the first encapsulated data packet to the remote CSP.

Generic packet encapsulation for virtual networking

Embodiments are provided herein to enable single level network abstraction for a service across one or more domains. The embodiments use a single network ID to identify a service and a corresponding virtual network topology across any number of domains at a physical network. A virtual network topology can be abstracted for each service, based on the physical underlying network topology. A network controller determines, for a service, the virtual network topology within a physical network, and binds the service to the virtual network topology via a virtual network ID, which defines a single forwarding domain of the virtual network topology across the physical network. The virtual network ID is then indicated to the nodes of the virtual network topology, thus enabling the nodes to identify and forward traffic for the service, within the single forwarding domain, between end clients from edge to edge of the physical network.

System and method for virtual network abstraction and switching

A method for controlling a data flow in a domain of an OpenFlow protocol controlled software-defined network (SDN) comprising receiving a request from a network element for instructions to route the data flow through the OpenFlow SDN, determining a route for the data flow through the OpenFlow SDN, transmitting a unified header to the network element in the OpenFlow SDN, wherein the unified header facilitates transmission of data flows through the OpenFlow SDN that are encoded according to a plurality of network abstraction types, and transmitting instructions for forwarding the data flow along the route through the OpenFlow SDN, wherein the instructions for forwarding the data flow along the route through the OpenFlow SDN comprise one or more match fields, one or more mask values corresponding to the match fields, and one or more actions for the network element in the OpenFlow SDN to perform on the data flow.

Extending OpenFlow to support packet encapsulation for transport over software-defined networks

Described herein are techniques related to a wireless enhanced projector (WEP) that is utilized by one or more devices, such as a mobile phone, a cellular phone, a Smartphone, a personal digital assistant, a tablet computer, and the like. In an implementation, the one or more devices may connect to the WEP through a server device that may be connected and/or integrated with the WEP. In this implementation, at least one of the one or more devices may be configured to be a super-user device (i.e., moderator or administrator device), while the rest of the one or more devices may be regular client devices.

Wireless enhanced projector

Disclosed herein is a mechanism for discovering SDN specific topology information in a SDN interconnection network. SDN specific topology information may comprise SDN IDs, SDN member router ID lists, and SDN address lists. A SDNC associated with a local SDN domain in the SDN interconnection network may determine a set of routers and/or links in the local SDN domain for link advertisement and may associate the set of routers with the local SDN domain. The SDNC may further determine a set of border routers in the local SDN domain for broadcasting the link advertisements and SDN specific topology information to other interconnected SDN domains. The SDNC may receive link advertisement and SDN specific topology information from other interconnected SDN domains and may compute a best path through each router and/or link across the SDN domains.

Software defined networking (SDN) specific topology information discovery

Growing community of inventors

San Jose, CA, United States of America

Lin Han