APSIS SCTE Adaptive Power Systems Interface Specification Frank Sandoval – Dir of SW Engineering, Comcast Chair – SCTE APSIS committee

Adaptive Power Systems Application monitoring and control of device energy consumption – Attenuate power consumption to correlate with service demand. E.g. As usage of HSD, VOD, and other services ebbs and flows, so should power consumption Real-world examples: – vendors have demonstrated %15 power reduction on CCAP by disabling ports and interfaces when demand slows – Reduce bias current to RF nodes during off-peak downstream demand APSIS is essentially a Software Defined Networking (SDN) framework that can dramatically reduce overall power usage while improving reliability and QoS – Greater visibility and control of device behavior can lead to better service quality APSIS Energy Management can simply be another aspect of a ‘Smart Network’ framework

APSIS APSIS defines a software interfaces to enable device and operator independent APSIS applications Defines an Information Model (IM) – Co-developed with IETF – Provides protocol independence. IM can be encoded in various protocols. Defines device-level Protocol ‘bindings’ to IM – SNMP inherited from IETF – Future work may include NETCONF(YANG), REST(XML,JSON), IPDR, OpenFlow, etc Defines API – Abstraction layer to isolate applications from device-specific protocols – Implies a ‘middleware’ layer that manages device connections on behalf of APSIS applications

Software Model As with many common frameworks, a ‘northbound’ API provides easy to use interface for application developers ‘southbound’ interfaces manage the details of connecting to plethora of devices and systems

OpenDaylight Model OpenDaylight is an example of an APSIS SW framework. SCTE APSIS defines model (IM), and protocol bindings Cable industry could open source OpenDaylight Energy Mgmt ‘plugin’ to provide interoperable APIs Leverages common framework for other SDN scenarios