Abstract:
Techniques described herein may enable users to manage the division of storage, for multiple applications and on a per-content type basis, between cloud storage and local storage. A mobile device may receive user preference information relating to storage limits, each of the storage limits being applicable to an aggregate amount of data, of a particular content type, and associated with a number of applications executed by the mobile device. The mobile device transfer data, to and from cloud storage, to enforce the storage limits included in the user preference information.
Abstract:
A server device may communicate with a user device by engaging in a telephone call with the user device, by providing a webpage to the user device, or in another way. The user device may communicate a request to the server device for a particular web service, such as a mapping service, a banking service, technical support, customer service, etc., and the server device may communicate the request to an instant access device that may cause the user device to instantly access the web service, whether by automatically downloading and installing a mobile application with the web service or by automatically accessing a web page. In some implementations, the instant access device may authenticate the user device in order to provide the user device with access to the web server.
Abstract:
A system described herein may allow for the frictionless authentication of a user and/or user device (e.g., without requiring that the user provide login details, such as a user name and password). The frictionless authentication may occur via a licensed wireless network, even when the user device is actively engaged in communications with an unlicensed wireless network (and/or is not engaged in communications with the licensed wireless network).
Abstract:
A device may receive an identifier for a subscriber of a first network. The subscriber may be associated with the device. The device may store the identifier and receive a request for content. The device may generate a modified request by adding the identifier to the request. The device may send the modified request using a network communication. The network communication may communicate via a second network without using the first network, and the first network may be different than the second network. The device may receive the content and targeted content based on the modified request. The targeted content may be targeted to the subscriber based on the identifier.
Abstract:
Techniques described herein may allow for the automatic downloading, installing, and/or launching of applications (commonly referred to as “apps”), during the presentation of content. For example, a user device (e.g., a smart phone) may play video content, such as a trailer for a video game app. During the presentation of the trailer, a button, to install the video game app, may be presented. Based on a single click of the button, the video game app may be downloaded and installed. The app may further be launched as soon as it is installed, and/or as soon as the trailer ends. Some techniques described herein may be applicable for the automatic downloading, installing, and/or launching of an application on a wearable device while another device presents content, or vice versa.
Abstract:
A network device receives a collection of technical steps for implementing a type of service campaign. The technical steps include application programming interface (API) level calls to a service provider network. The network device associates the technical steps with particular customer software, receives validation criteria for each of the technical steps, generates a diagnostic map of the technical steps for the particular customer software, and conducts, based on the diagnostic map, a test of the API level calls for the particular customer software to obtain test results. The network device receives a customer deployment record of changes occurring during software deployments for the service campaign for the particular customer software and receives a provider record of service provider changes to network level software that impact the service campaign for the particular customer software. The network device correlates the test results with the customer deployment record and the provider record.
Abstract:
A device may provide an upload request to upload a file. The device may receive, based on the upload request, a unique identifier associated with the device. The device may obtain a file key for encrypting the file and a security key for encrypting the file key. The security key may be obtained based on the unique identifier. The device may encrypt the file, using the file key, to create an encrypted file. The device may encrypt the file key, using the security key, to create an encrypted file key. The device may provide the encrypted file and the encrypted file key for storage by a storage device.
Abstract:
A server device may communicate with a user device by engaging in a telephone call with the user device, by providing a webpage to the user device, or in another way. The user device may communicate a request to the server device for a particular web service, such as a mapping service, a banking service, technical support, customer service, etc., and the server device may communicate the request to an instant access device that may cause the user device to instantly access the web service, whether by automatically downloading and installing a mobile application with the web service or by automatically accessing a web page. In some implementations, the instant access device may authenticate the user device in order to provide the user device with access to the web server.
Abstract:
A first server device may receive, from a second server device, a unique identifier (ID) relates to content stored by the second server device; determine a policy based on the unique ID; generate a policy tag identifying the determined policy; and output the policy tag to the second server device. Outputting the policy tag may cause the second server device to apply the policy tag to a packet associated with the content, and output the packet towards a requesting user device that requests the content.