Juniper Networks, Inc.

Nokia of America Corporation

Bhupesh Kothari

Philip Winterbottom

Alok Khambatkone

Iswar Biswal

Nischal Sheth

Rahul Aggarwal

Chao Wang

Rex Fernando

Binoy Dash

Iswar Chandra Biswal

A novel method for provisioning network services for a cable system is provided. The method provides a configuration command interpreter/compiler that receives configuration commands of the cable system and generates configuration commands understood by the actual physical devices implementing the cable system. The interpreter transforms the configuration commands of the cable system into the configuration commands of the actual physical devices based on a set of normalized data models describing the cable system. The normalized data models are applicable to the cable system regardless of the actual devices implementing the cable system. The normalized data models are specified using normalized parameters that are generally applicable to different types devices that can be used to implement the cable system.

Provisioning network services for cable systems

A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. The packet engine is configurable to selectively provide Llevel routing or Llevel switching/bridging between different logical interfaces. In some embodiments, the controller selects between configuring the packet engine to perform Lrouting or configuring the packet engine to perform Lbridging based on whether the packet engine support unnumbered interfaces and integrated routing and bridging (IRB). The packet engine of the cable system is configured to use unnumbered interfaces if the number of available IP addresses for use by the cable system is limited.

Selective configuration of packet engine for cable service flows

A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. Upon receiving upstream data packet from a particular cable service flow, the remote distribution node applies a set of tags or labels to the data packet identifying the data packet as being from the particular cable service flow. The remote distribution node then forwards the tagged packet toward the packet engine, where the tags/labels are used to direct the packet toward the corresponding logical interface of the particular cable service flow.

Mapping cable service flows to IP network

A novel method of handling network traffic for cable service flows in a distributed cable system is presented. Such a cable systems use remote distribution nodes in the fields to handle RF communications with cable modems in a distributed fashion. A packet engine is configured to assign a logical interface to each cable service flow in the cable system. Each logical interface in the packet engine is uniquely identifiable by a compound identifier that includes the identifier of the corresponding service flow and the identifier of the remote distribution node. Each service flow is assigned a class of service (CoS) at the packet engine and guarantee a certain level of quality of service (QoS). In some embodiments, each cable service flow is assigned a CoS priority number. For each possible CoS priority number, the packet engine is configured to provide certain resources at certain quality level, i.e., certain level of QoS. Each remote distribution node tags each packet of a cable service flow with its assigned CoS priority number and forwards the tagged packet toward the packet engine.

Assigning QoS to cable service flows

A method performed by a provider edge device includes generating pseudo-wire tables based on virtual private local area network service advertisements from other provider edge devices, where the provider edge device services customer edge devices, and establishing pseudo-wires with respect to the other provider edge devices, based on the pseudo-wire tables, where the pseudo-wires include an active pseudo-wire and at least one standby pseudo-wire with respect to each of the other provider edge devices. The method also includes generating and advertising VPLS advertisement to the other provider edge devices, detecting a communication link failure associated with one of the customer edge devices in which the provider edge device services, and determining whether the at least one standby pseudo-wire needs to be utilized because of the communication link failure.

Redundant pseudowires for border gateway patrol-based virtual private local area network service multi-homing environments

A first network device creates a protection path to a second network device associated with a first service site, and creates a pseudowire between the first service site and a second service site via the first network device and the second network device. The first network device also detects a failure between the first network device and the first service site, and forwards traffic, provided by the pseudowire between the first service site and the second service site, via the protection path. The second network device uses the traffic on the protection path as a trigger to activate a link between the second network device and the first service site.

Fast restoration for provider edge node and access link failures

In general, techniques are described for dynamically configuring cross-domain pseudowires (PWs). A network device positioned between a first domain and a second domain of a computer network may implement the techniques. The intermediate network device comprises at least one interface and an LDP module, a transformation module and a routing protocol module. The interface receives a label distribution protocol (LDP) message that includes data for configuring a cross-domain PW from a first provider edge (PE) device of the first domain. The LDP module parses the received LDP message to extract the cross-domain PW configuration data. The translation module transforms the extracted data to conform to routing protocol extensions for advertising the cross-domain PW configuration data. The routing protocol module forms a routing protocol message that includes the transformed data. The interface outputs the routing protocol message to the second intermediate device of the second domain to establish the cross-domain PW.

Dynamic configuration of cross-domain pseudowires

A method performed by a provider edge device in a multi-autonomous system (AS) includes receiving advertisements from other PEs of the multi-AS, where one or more of the advertisements includes a destination AS parameter that indicates a destination AS of the multi-AS; generating pseudo-wire (PW) tables based on the advertisements received from the other PEs; and establishing PWs with respect to the other PEs based on the PW tables.

Pseudowire establishment to sites across autonomous systems with overlapping customer site ID space

A network device includes a control unit configured to execute an extended layer three (L3) routing protocol within a control plane of the network device. The extended L3 routing protocol is extended to process a routing protocol control message having a set of layer two (L2) identifiers of customer devices attached to an autonomous system (AS) and an indicator that specifies a Route Target associated with a Virtual Private Local Area Network Service (VPLS) domain within the AS. The routing protocol control message conforms to a message type of the L3 routing protocol to initiate a flush of the set of L2 identifiers.

Growing community of inventors

San Jose, CA, United States of America

Bhupesh Kothari