Harmonic, Inc.

Adam Levy

Michael W Patrick

Alex Muller

Nitin Sasi Kumar

Victoria Sinitsky

Vladyslav Buslov

Pavlo Shcherbyna

Anton Grichina

Approaches for processing packets transmitted within a Passive Optical Network (PON) using executable software. Processing packets within a PON may be performed by classifying one or more packets, of a plurality of received packets, to a particular PON system component, and then processing the one or more packets classified to the same PON system component on a single physical or virtual processor. The one or more packets may be forwarded between a sequence of one or more software stages. The software stages may each be configured to execute on separate logical cores or on a single logical core.

Multiple core software forwarding

Recovering or restarting an execution instance. In response to detecting that a particular execution instance in which a software application, such as an optical line terminal (OLT) software application or a broadband network gateway (BNG) software application, providing services for a Passive Optical Network (PON) has failed, restarting the execution instance having only downstream service flow classifiers and entries of an access control list for the particular execution instance to support default service flows and/or voice calls. After restarting the execution instance, the configuration of the instance is adjusted over time to add one or more downstream service flow classifiers or access control list entries such that the instance can provide additional services, beyond the initially supported default service flows and voice calls, to optical network units. Required time to register optical network units with the execution instance is advantageously reduced while maintaining quality of service.

Improving recovery time of execution instances in a passive optical network (PON)

Recovering or restarting an execution instance. In response to detecting that a particular execution instance, in which a cable modem termination system (CMTS) software application, an optical line terminal (OLT) software application, and/or broadband network gateway (BNG) software application has failed, restarting the execution instance without adding any downstream service flow classifiers to the instance or configuring any entries of an access control list for the instance. After restarting the execution instance, over time adjusting the configuration of the instance to add one or more downstream service flow classifiers or access control list entries such that the instance can provide additional services, beyond a default service flow, to cable modems or optical network units. Support for voice calls may be initially added to the execution instance upon startup. Required time to register cable modems or optical network units with the execution instance is advantageously reduced while maintaining quality of service.

Recovery time of execution instances

Approaches for performing all DOCSIS downstream and upstream data forwarding functions using executable software. DOCSIS data forwarding functions may be performed by classifying one or more packets, of a plurality of received packets, to a particular DOCSIS system component, and then processing the one or more packets classified to the same DOCSIS system component on a single CPU core. The one or more packets may be forwarded between a sequence of one or more software stages. The software stages may each be configured to execute on separate logical cores or on a single logical core.

Scheduling of packets to be forwarded onto DOCSIS downstream channels as part of a Virtual Converged Cable Access Platform (CCAP). A packet to be forwarded onto a DOCSIS downstream channel is enqueued in a service flow queue. The packets stored in the service flow queue are associated with a single service flow. A request is propagated up a hierarchy of schedule elements to a scheduler process to schedule the packet for delivery. The scheduler process determines a grant of how much traffic to offer the DOCSIS downstream channel. The grant determined for the DOCSIS downstream channel may be expressed in units of symbols rather than in bytes. The scheduler process extends a particular grant to the service flow queue by translating symbols in the grant for the service flow queue which issued the request.

Growing community of inventors

Hadera, Israel

Adam Levy