Abstract: A methodology and apparatus for layered licensing is described. A licensable item is detected on a device. A legacy license associated with the licensable item is accessed, wherein the legacy license corresponds to a legacy licensing policy. A layered license associated with the licensable item is accessed, wherein the layered license corresponds to a layered licensing policy. The legacy licensing policy and the layered licensing policy are integrated into an integrated license, and the integrated license is enforced.

Abstract: Techniques for mitigating the transitive data problem using a secure asset manager are provided. These techniques include generating a secure asset manager compliant application by tagging source code for the application with a data tag to indicate that a data element associated with the source code is a sensitive data element, accessing a policy file comprising transitive rules associated with the sensitive data element, and generating one or more object files for the application from the source code. These techniques also include storing a sensitive data element in a secure memory region managed by a secure asset manager, and managing the sensitive data element according to a policy associated with the sensitive data element by an application from which the sensitive data element originates, the policy defining transitive rules associated with the sensitive data element.

Abstract: Techniques for mitigating the transitive data problem using a secure asset manager are provided. These techniques include generating a secure asset manager compliant application by tagging source code for the application with a data tag to indicate that a data element associated with the source code is a sensitive data element, accessing a policy file comprising transitive rules associated with the sensitive data element, and generating one or more object files for the application from the source code. These techniques also include storing a sensitive data element in a secure memory region managed by a secure asset manager, and managing the sensitive data element according to a policy associated with the sensitive data element by an application from which the sensitive data element originates, the policy defining transitive rules associated with the sensitive data element.

Abstract: Techniques for mitigating the transitive data problem using a secure asset manager are provided. These techniques include generating a secure asset manager compliant application by tagging source code for the application with a data tag to indicate that a data element associated with the source code is a sensitive data element, accessing a policy file comprising transitive rules associated with the sensitive data element, and generating one or more object files for the application from the source code. These techniques also include storing a sensitive data element in a secure memory region managed by a secure asset manager, and managing the sensitive data element according to a policy associated with the sensitive data element by an application from which the sensitive data element originates, the policy defining transitive rules associated with the sensitive data element.

Abstract: A methodology and apparatus for layered licensing is described. A licensable item is detected on a device. A legacy license associated with the licensable item is accessed, wherein the legacy license corresponds to a legacy licensing policy. A layered license associated with the licensable item is accessed, wherein the layered license corresponds to a layered licensing policy. The legacy licensing policy and the layered licensing policy are integrated into an integrated license, and the integrated license is enforced.

Abstract: A policy server is arranged to construct device-neutral policies for configuring CBR for MPLS traffic engineering across a network. The policy server translates the device-neutral policies into device-specific commands (e.g. link attribute definitions and affinity profiles). The policy server defines the link attributes, assigns the link attributes to network interfaces, establishes affinity profiles and attaches the affinity profiles to MPLS tunnels. The link attribute definitions and affinity profiles are shared across the network to construct the policies such that IP operators can configure CBR easily across a network.

Abstract: A policy server operates to configure differentiated services over multi-protocol label switching (Diffserv/MPLS) in a communications network. The policy server enables the definition and deployment of a customer policy, a network policy and a mapping policy. The policy server is arranged to create a group of MPLS tunnels, and associate the tunnels to the mapping policy and the customer policy. The customer policy includes a tunnel group identifier and a tunneling mode, and maps customer traffic to MPLS tunnels. The policy server translates the customer policy, the network policy and the mapping policy into device-specific commands, and then deploys the device-specific commands to the network interfaces of the affected network devices.

Abstract: Provided are improved systems, methods, and devices for a distributed network architecture for permitting a low power proxy to wake a power saving device from an offline power saving mode using a wake up agent operating a link layer wake up mechanism. The distributed network architecture using wake up agents allows a power saving device to coordinate a relationship with an access point capable of waking the power saving device from an offline mode, allows the power saving device to communicate that relationship to a proxy entity or other control point, and to permit the proxy entity and other control points to use wake up mechanisms to instruct wake-up capable access points to wake a power saving device from an offline mode, such as to wake a UPnP™ device from a deep sleep offline power saving mode.

Abstract: A policy server is arranged to construct device-neutral policies for configuring CBR for MPLS traffic engineering across a network. The policy server translates the device-neutral policies into device-specific commands (e.g. link attribute definitions and affinity profiles). The policy server defines the link attributes, assigns the link attributes to network interfaces, establishes affinity profiles and attaches the affinity profiles to MPLS tunnels. The link attribute definitions and affinity profiles are shared across the network to construct the policies such that IP operators can configure CBR easily across a network.