Abstract: A device can receive, from a network device, information that identifies a user device. The network device might have authenticated the user device based on the user device accessing a radio access network. The device can receive, from the user device, a request for a first token. The request can include an encrypted session identifier. A server device might have encrypted the session identifier. The device can determine the session identifier, and generate the first token based on the session identifier and the information that identifies the user device. The device can encrypt the first token using an application public key, and provide, to the user device, the encrypted first token. The user device can provide, to the server device, the encrypted first token. The server device can register the user device to receive content based on the encrypted first token.

Abstract: A device associated with a cell tower in a Public Land Mobile Network receives, from a mobile device via a network, a uniform resource locator (URL) that is appended with a first signature generated at the mobile device using a private key of a public/private key pair associated with a toll-free campaign. The device obtains a public key of the public/private key pair, extracts the first signature from the URL, decrypts the first signature using the public key to obtain data, and encrypts the data using the private key to generate a second signature. The device compares the second signature with the first signature, denies toll-free network access to content associated with the URL when the second signature does not match the first signature, and designates data involved with accessing the content associated with the URL as being toll-free when the second signature matches the first signature.

Abstract: A device may receive first information. The first information may be based on traffic associated with usage of a toll-free data service. The device may receive an identifier for a user device. The user device may be using the toll-free data service. The device may generate second information. The second information may correspond to usage, by the user device, of the toll-free data service. The second information may be generated based on the first information and the identifier. The device may send the second information to another device to support providing a notification of toll-free data service usage. The notification of toll-free data service usage may be based on the second information.

Abstract: A device may receive campaign information, that includes information identifying a targeted geographic region, for generating a toll-free data service campaign. The targeted geographic region may not coincide with a coverage area of a base station. The device may generate a campaign rule identifying one or more campaign conditions for updating an account of a campaign owner, associated with the toll-free data service campaign, for data used in association with the toll-free data service campaign. The device may receive a request, from a user device, to access a service, and may determine that one or more campaign conditions are satisfied, such as a condition to determine that the user device is located within the targeted geographic region. The device may provide an instruction to update the account, of the campaign owner, for data usage of the user device based on determining that the one or more campaign conditions are satisfied.

Abstract: A method to facilitate secure access to sponsored content may include accessing a portal device to generate a campaign for a sponsored data service (SDS), and providing campaign network addresses and customer identifiers associated with the content aggregator device and at least one content partner device. The method includes generating a unique first security credential associated with each of the content partner device(s), and providing information for a notification of the campaign to the portal device, where the information includes the unique first security credential associated with each of the content partner device(s), and where the notification is provided to each of the at least one content partner device. The method includes signing a unique first SDS network address associated with sponsored content provided by each of the content partner device(s), where the signing is performed using the unique first security credential associated with each of the content partner device(s).

Abstract: A device may receive first information. The first information may be based on traffic associated with usage of a toll-free data service. The device may receive an identifier for a user device. The user device may be using the toll-free data service. The device may generate second information. The second information may correspond to usage, by the user device, of the toll-free data service. The second information may be generated based on the first information and the identifier. The device may send the second information to another device to support providing a notification of toll-free data service usage. The notification of toll-free data service usage may be based on the second information.

Abstract: A device determines a connection status of a Public Land Mobile Network (PLMN) communication interface and a wireless Local Area Network (LAN) communication interface, and stores the connection status in a queue. The device waits, subsequent to storing the connection status, for expiration of a time delay; and retrieves, subsequent to the expiration of the time delay, the connection status or another connection status from the queue. The device sends, based on the retrieved connection status or the other connection status, a service validation request to a server associated with the PLMN, and receives from the server, in response to the service validation request, a validation response that authorizes service delivery to the device via a PLMN.

Abstract: A native content handler in a user device, such as a smart phone, determines whether requested content may by delivered using special handling, such as prioritized or sponsored access. A listener of the content handler determines whether special handling may possibly be applicable to the content, and the listener modifies a universal resource locator (URL) associated with the content to mark the URL. An agent portion of the content handler exchanges data with a validation device to determine whether the user device is actually eligible to receive the content with the special handling. If the user device is eligible, the agent uses data provided by the validation device to obtain the content using the special handling.

Abstract: A method to facilitate secure access to sponsored content may include accessing a portal device to generate a campaign for a sponsored data service (SDS), and providing campaign network addresses and customer identifiers associated with the content aggregator device and at least one content partner device. The method includes generating a unique first security credential associated with each of the content partner device(s), and providing information for a notification of the campaign to the portal device, where the information includes the unique first security credential associated with each of the content partner device(s), and where the notification is provided to each of the at least one content partner device. The method includes signing a unique first SDS network address associated with sponsored content provided by each of the content partner device(s), where the signing is performed using the unique first security credential associated with each of the content partner device(s).

Abstract: A device may receive information associated with media content that is capable of being provided by a first content delivery network and a second content delivery network. The first content delivery network may include a first host device and a second host device. The device may determine scores associated with the first content delivery network and the second content delivery network. The device may provide, based on the scores, information regarding the first content delivery to a user device to cause the user device to request the media content from the first content delivery network. The device may determine scores associated with the first host device and the second host device. The device may provide information regarding the first host device to a network device to cause the network device to route requests for the media content to the first host device.

Abstract: A first device may obtain a session time record that includes information relating to a secure session. The session time record may include a content identifier and a device identifier that is associated with a second device. The content identifier may be associated with content to be provided via a secure session and via the second device. The content may be associated with a sponsored data campaign. The first device may obtain, from the second device, data usage information identifying an amount of data provided via the second device and in association with the secure session. The first device may determine information identifying a party responsible for the amount of data provided in association with the secure session based on the session time record and based on the data usage information. The first device may store or provide the information identifying the party responsible for the amount of data.

Abstract: A device associated with a cell tower in a Public Land Mobile Network receives, from a mobile device via a network, a uniform resource locator (URL) that is appended with a first signature generated at the mobile device using a private key of a public/private key pair associated with a toll-free campaign. The device obtains a public key of the public/private key pair, extracts the first signature from the URL, decrypts the first signature using the public key to obtain data, and encrypts the data using the private key to generate a second signature. The device compares the second signature with the first signature, denies toll-free network access to content associated with the URL when the second signature does not match the first signature, and designates data involved with accessing the content associated with the URL as being toll-free when the second signature matches the first signature.

Abstract: Methods and devices provide access to a sponsored data service (SDS) from a mobile device. A method may include generating a play media command that includes a remote media address and an SDS identifier, and converting the remote media address into a local media address. The method may further include requesting media from an internal content server via the local media address, where the internal content server resides within the mobile device. The method may include determining if the requested media is stored on the internal content server, obtaining the requested media from the internal content server upon determining that the requested media is stored within the internal content server, and playing the requested media on a mobile media player.

Abstract: A system may receive a content identifier corresponding to content to be accessed via a toll free data service (toll-free data service). The system may determine, based on the content identifier, whether a content provider device, associated with the content, is configured with a serving component associated with serving the content via the toll-free data service. The system may provide an indication of whether the content provider device is configured with the serving component. The content may be accessible via the toll-free data service when the content provider device is configured with the serving component.

Abstract: A device may determine a resource identifier for accessing a segment of streaming media content. The device may determine that a signature associated with the resource identifier is not stored in memory. The signature may be generated based on a character string of the resource identifier. The device may request validation of the resource identifier based on determining that the signature is not in memory. The device may receive the signature associated with the resource identifier based on requesting validation. The device may store the signature based on receiving the signature. The device may request the segment of streaming media content using the resource identifier and the signature, stored in memory, to receive toll-free access to the segment of streaming media content.

Abstract: A device may receive campaign information for deploying a toll-free data service campaign. The campaign information may identify a total amount of data to be allocated for a toll-free data service associated with the toll-free data service campaign. The device may determine enforcement devices associated with the toll-free data service campaign, and may allocate a portion of data, of the total amount of data, to an enforcement device. The device may receive, from the enforcement device, data usage information that indicates an amount of the portion of data consumed during a first time period, by mobile devices associated with the enforcement device, in association with the toll-free data service campaign. The device may determine, based on the data usage information, an additional amount of data to be allocated to the enforcement device, and may allocate the additional amount of data to the enforcement device.

Abstract: A device may receive campaign information for deploying a toll-free data service campaign. The campaign information may identify a uniform resource identifier for accessing a toll-free data service associated with the toll-free data service campaign. The device may determine a host name included in the uniform resource identifier. The device may determine a network address associated with the host name. The device may modify the uniform resource identifier, to generate a modified uniform resource identifier for accessing the toll-free data service, by replacing the host name, included in the uniform resource identifier, with the network address. The device may deploy the toll-free data service campaign by providing, to an enforcement device, the modified uniform resource identifier.

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 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 receive campaign information for deploying a toll-free data service campaign. The campaign information may identify a geographic region in which the toll-free data service campaign is to be deployed. The device may mark the toll-free data service campaign as ready to deploy, and may generate campaign rules based on the campaign information. The campaign rules may identify conditions for charging a content provider, associated with the toll-free data service campaign, for data used by a mobile device in association with the toll-free data service campaign. The device may deploy the toll-free data service campaign by providing the campaign rules to enforcement devices associated with the geographic region. The device may mark the toll-free data service campaign as being deployed. The device may determine that deployment of the toll-free data service campaign has been completed, and may mark the toll-free data service campaign as deployed.