Abstract: Various example embodiments for providing device application support are presented. In at least some example embodiments, device application support may be configured to support device programmability. In at least some example embodiments, device application support may be configured to support device programmability for enabling a customer that operates a device to develop a customer application for the device and to run the customer application on the device. In at least some example embodiments, device application support may be provided in a manner for enabling a customer to develop and run a customer application for a device without a need for the customer to use a software development kit (SDK) to develop the customer application.

Abstract: Various example embodiments for supporting device telemetry control are presented. Various example embodiments may provide a customer of a device, which is monitoring the device based on device telemetry whereby the device exposes device data of the device based on device telemetry control information of the device such that the data of the device may be accessed by the customer, with control over device telemetry of the device. Various example embodiments may provide a customer, which may access device data of a device based on device telemetry supported by the device, with additional control over access to the device data of the device via device telemetry by providing the customer with control over the device telemetry including enabling the customer to insert customer device telemetry control information into the device telemetry control information of the device that controls device telemetry on the device.

Abstract: Various example embodiments for supporting data retrieval flexibility are presented. Various example embodiments for supporting data retrieval flexibility may include supporting data retrieval flexibility for retrieval of data from a device that does not maintain that data using a relational database data format by supporting operation of the device as a device that supports retrieval of that data in a relational database data format using a structured query language. Various example embodiments for supporting data retrieval flexibility may include supporting data retrieval flexibility for retrieval of data from a device by supporting retrieval of data maintained at the device based on a first data format based on generation of a database storing that data in a second data format different than the first data format and using a structured query language configured to support retrieval of the data in the second data format from the database.

Abstract: Various example embodiments for supporting data retrieval flexibility are presented. Various example embodiments for supporting data retrieval flexibility may include supporting data retrieval flexibility for retrieval of data from a device that does not maintain that data using a relational database data format by supporting operation of the device as a device that supports retrieval of that data in a relational database data format using a structured query language. Various example embodiments for supporting data retrieval flexibility may include supporting data retrieval flexibility for retrieval of data from a device by supporting retrieval of data maintained at the device based on a first data format based on generation of a database storing that data in a second data format different than the first data format and using a structured query language configured to support retrieval of the data in the second data format from the database.

Abstract: Various example embodiments for providing device application support are presented. In at least some example embodiments, device application support may be configured to support device programmability. In at least some example embodiments, device application support may be configured to support device programmability for enabling a customer that operates a device to develop a customer application for the device and to run the customer application on the device. In at least some example embodiments, device application support may be provided in a manner for enabling a customer to develop and run a customer application for a device without a need for the customer to use a software development kit (SDK) to develop the customer application.

Abstract: Various example embodiments for supporting device telemetry control are presented. Various example embodiments for supporting device telemetry control may provide a customer of a device, which is monitoring the device based on device telemetry whereby the device exposes device data of the device based on device telemetry control information of the device such that the data of the device may be accessed by the customer, with control over device telemetry of the device. Various example embodiments for supporting device telemetry control may provide a customer, which may access device data of a device based on device telemetry supported by the device, with additional control over access to the device data of the device via device telemetry by providing the customer with control over the device telemetry including enabling the customer to insert customer device telemetry control information into the device telemetry control information of the device that controls device telemetry on the device.

Abstract: A customer Quality-of-Service (QoS) transport capability is depicted and described herein. The customer QoS transport capability enables transparent transport of customer QoS information via a Provider Backbone Bridging (PBB) network. The customer QoS transport capability enables customer QoS information that would normally be terminated at a point of ingress to a PBB network to be transported via the PBB network transparently and recovered at a point of egress from the PBB network.

Abstract: A customer Quality-of-Service (QoS) transport capability is depicted and described herein. The customer QoS transport capability enables transparent transport of customer QoS information via a Provider Backbone Bridging (PBB) network. The customer QoS transport capability enables customer QoS information that would normally be terminated at a point of ingress to a PBB network to be transported via the PBB network transparently and recovered at a point of egress from the PBB network.

Abstract: Providing redundancy between an active component and a standby component in a network router comprises maintaining a first route input information base associated with the active component, synchronizing with the first route information base a second route input information base associated with the standby component, generating a route output information base using the second route input information base, and comparing the generated route output information base, in the event of switchover of the standby component to an active mode, to a synchronized route output information base associated with the standby component which synchronized route output information base reflects routes known to have been shared with one or more peers by the active component prior to the switchover, and sharing and/or withdrawing routes as necessary to reflect any differences between the generated route output information base and the synchronized route output information base.

Abstract: Providing redundancy between an active component and a standby component in a network router comprises maintaining a first route input information base associated with the active component, synchronizing with the first route information base a second route input information base associated with the standby component, generating a route output information base using the second route input information base, and comparing the generated route output information base, in the event of switchover of the standby component to an active mode, to a synchronized route output information base associated with the standby component which synchronized route output information base reflects routes known to have been shared with one or more peers by the active component prior to the switchover, and sharing and/or withdrawing routes as necessary to reflect any differences between the generated route output information base and the synchronized route output information base.