Abstract: A method for managing software on a device is provided. The method comprises: receiving, from a third party associated with the device, by a software administrator of an organization different from the third party, release information regarding software versions for the device; creating, by the software administrator, a profile that specifies whether or not at least one of the software versions is allowed on the device; and transmitting the profile, by the software administrator to a server computer associated with the third or other parties, to promote enforcement of the profile for the device.

Abstract: A system and method are provided for proactively buffering quantum key distribution (QKD) key material. The method includes monitoring key generation rates and surpluses at QKD devices at each node of a QKD link in a QKD network, retrieving surplus key material from the QKD devices at one or both nodes of the QKD link, and buffering the surplus key material in a local storage at one or both nodes in the QKD link. The surplus key material can be used to offset overhead introduced in securely relaying keys between non-adjacent demand pairs in the QKD network. The surplus key material can also be used to offset future transient decreases in key generation rates.

Abstract: A system and method are described for proactively performing key swaps among nodes in a quantum key distribution (QKD) network. The method includes determining a routing solution for nodes in the QKD network; making the routing solution available to the nodes in the QKD network; and initiating key swaps among the nodes in the QKD network according to the routing solution, prior to key requests being made within the QKD network. The method can also include continuously performing key swaps among the nodes in the QKD network according to the routing solution; detecting a change in capacity and/or a change in demand on one or more links within the QKD network; determining a new routing solution based on the detected change; and continuously preforming subsequent key swaps according to the new routing solution.

Abstract: A system and method are provided for proactively buffering quantum key distribution (QKD) key material. The method includes monitoring key generation rates and surpluses at QKD devices at each node of a QKD link in a QKD network, retrieving surplus key material from the QKD devices at one or both nodes of the QKD link, and buffering the surplus key material in a local storage at one or both nodes in the QKD link. The surplus key material can be used to offset overhead introduced in securely relaying keys between non-adjacent demand pairs in the QKD network. The surplus key material can also be used to offset future transient decreases in key generation rates.

Abstract: A system and method are described for proactively performing key swaps among nodes in a quantum key distribution (QKD) network. The method includes determining a routing solution for nodes in the QKD network; making the routing solution available to the nodes in the QKD network; and initiating key swaps among the nodes in the QKD network according to the routing solution, prior to key requests being made within the QKD network. The method can also include continuously performing key swaps among the nodes in the QKD network according to the routing solution; detecting a change in capacity and/or a change in demand on one or more links within the QKD network; determining a new routing solution based on the detected change; and continuously preforming subsequent key swaps according to the new routing solution.

Abstract: Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Multiple groups of endpoints are identified by name and defined by group criteria expressed in terms of the one or more arbitrary properties of the one or more components of the endpoints that are members of the group. For each group, the group criteria of the group is stored in a data store in association with the name of the group. Packages and releases may be targeted to endpoints in various manners.

Abstract: Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Multiple groups of endpoints are identified by name and defined by group criteria expressed in terms of the one or more arbitrary properties of the one or more components of the endpoints that are members of the group. For each group, the group criteria of the group is stored in a data store in association with the name of the group. Packages and releases may be targeted to endpoints in various manners.

Abstract: Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Multiple groups of endpoints are identified by name and defined by group criteria expressed in terms of the one or more arbitrary properties of the one or more components of the endpoints that are members of the group. For each group, the group criteria of the group is stored in a data store in association with the name of the group. Packages and releases may be targeted to endpoints in various manners.

Abstract: A method for managing software on a device is provided. The method comprises: receiving, from a third party associated with the device, by a software administrator of an organization different from the third party, release information regarding software versions for the device; creating, by the software administrator, a profile that specifies whether or not at least one of the software versions is allowed on the device; and transmitting the profile, by the software administrator to a server computer associated with the third or other parties, to promote enforcement of the profile for the device.

Abstract: A method at a network element for monitoring, at the network element, transactions between the network element and at least one client device; applying rules to each transaction; and performing at least one of parsing, storing, or discarding each transaction based on the rules. Further, a method at a client device including storing a session identifier; generating a transaction message; adding the session identifier and a transaction identifier to the transaction message; and sending the transaction message with the session identifier and transaction identifier to a server.

Abstract: A method for managing software on a device is provided. The method comprises: receiving, from a third party associated with the device, by a software administrator of an organization different from the third party, release information regarding software versions for the device; creating, by the software administrator, a profile that specifies whether or not at least one of the software versions is allowed on the device; and transmitting the profile, by the software administrator to a server computer associated with the third or other parties, to promote enforcement of the profile for the device.

Abstract: Transport information is to be used by an endpoint to obtain one or more packages comprised in a deployed release. The transport information is sent in a single message that identifies the deployed release and the one or more packages. The transport information may include allowed bearer settings and transport settings. Release parameters to be used by the endpoint in connection with the deployed release are determined and included in the single message. The message may include one of the packages as streamed inline content. The message may identify one of the packages via a network address of a file of that package. The message may identify one of the packages via an indication of where in local removable storage to find a file of that package, the local removable storage being local to the endpoint.

Abstract: Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Any packages installed on the components are represented in the data structures. Representations of the arbitrary properties within the data structure are aggregated from multiple sources, and conflict resolution methods are described.

Abstract: A system and method to filter content delivered to a device are disclosed. A birthdate for a user associated with a controlled device is received. Based on the birthdate, a present age of the user associated with the controlled device is determined. A request for content is received from the controlled device. An age rating associated with the content is compared to the present age of the user. The content is allowed to be delivered to the controlled device based on comparing the age rating to the present age of the user.

Abstract: An example network device includes a processor configured to execute an Open Mobile Alliance (OMA) Device Management (DM) server, the OMA DM server to perform operations of: participating in mutual authentication with a second OMA DM server; sending a notification to the second OMA DM server for notifying the second OMA DM server to proceed with a delegation process; and sending, to a DM client, information for modifying an access control list (ACL).

Abstract: Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Multiple groups of endpoints are identified by name and defined by group criteria expressed in terms of the one or more arbitrary properties of the one or more components of the endpoints that are members of the group. For each group, the group criteria of the group is stored in a data store in association with the name of the group. Packages and releases may be targeted to endpoints in various manners.

Abstract: Transport information is to be used by an endpoint to obtain one or more packages comprised in a deployed release. The transport information is sent in a single message that identifies the deployed release and the one or more packages. The transport information may include allowed bearer settings and transport settings. Release parameters to be used by the endpoint in connection with the deployed release are determined and included in the single message. The message may include one of the packages as streamed inline content. The message may identify one of the packages via a network address of a file of that package. The message may identify one of the packages via an indication of where in local removable storage to find a file of that package, the local removable storage being local to the endpoint.

Abstract: A method at a network element for monitoring, at the network element, transactions between the network element and at least one client device; applying rules to each transaction; and performing at least one of parsing, storing, or discarding each transaction based on the rules. Further, a method at a client device including storing a session identifier; generating a transaction message; adding the session identifier and a transaction identifier to the transaction message; and sending the transaction message with the session identifier and transaction identifier to a server.

Abstract: Data structures are stored in an endpoint data store. Each data structure represents an endpoint having one or more components, each component having one or more arbitrary properties. Multiple groups of endpoints are identified by name and defined by group criteria expressed in terms of the one or more arbitrary properties of the one or more components of the endpoints that are members of the group. For each group, the group criteria of the group is stored in a data store in association with the name of the group. Packages and releases may be targeted to endpoints in various manners.

Abstract: Personalization of a mobile device, including receiving at the mobile device a unique code; selecting, from a plurality of personalization policies stored on the mobile device a personalization policy that corresponds to the unique code; and storing the selected personalization policy in a persistent protected storage element of the mobile device. Customizing a mobile device, including determining at the mobile device a unique code; selecting, from a plurality of customized data sets stored on the mobile device a data set that corresponds to the unique code; and activating the selected data set on the mobile device.