Abstract:
A first device may receive data, to be provided to a second device, and an application identifier. The data and application identifier may be received from a third device. The first device may be associated with a first network, and the second device may be associated with a second network. The first network may be a different network than the second network. The application identifier may be associated with the second device. The first device may determine that the data is destined to the second device based on the application identifier. The first device may cause a secure session to be established with the second device. The secure session may allow the data to be securely transmitted from the third device to the second device. The first device may provide the data to the second device via the secure session.
Abstract:
A device may receive traffic flow information that includes user device identifiers. The device may receive, from a user device accessing an application associated with a third party service, an authentication request to authenticate the user device with a third party device that provides the third party service. The request may include a session token that identifies a session, an application identifier that identifies the application, and a user device identifier that identifies the user device. The device may determine to authenticate the user device based on whether the user device identifier matches one of the user device identifiers included in the traffic flow information. The device may provide, to the third party device, the session token and an indication of whether the user device has been authenticated to permit the third party device to allow or deny access to the third party service.
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 may receive first data items and second data items that may have been output by sensor devices. The device may add, to a node in a data structure, at least some of the first data items. The device may divide the node to create subnodes that correspond to subregions of a geographic region. The device may add, to at least one of the subnodes, at least some of the second data items. The device may generate a probability of a first relationship, between the first data items and the second data items, based on determining subnodes that include a first data item and determining subnodes that exhibit a predefined second relationship with a second data item. The device may send, to another device, the probability of the first relationship to support location-based services.
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 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.
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 first device may receive a request from a second device. The request may include a device identifier associated with the second device. The request may be transmitted by the second device to obtain a signature, based on which to access a third device. The first device may determine that the device identifier is associated with a secure authentication service. The first device may generate a signature based on determining that the device identifier is associated with the secure authentication service. The first device may provide the signature to the third device. The signature may permit the third device to selectively permit or deny access by the second device based on a result of authenticating the signature. Access may be permitted when the third device successfully authenticates the signature, and access may be denied when the third device fails to authenticate the signature.
Abstract:
A first server may receive, from a user device, a first instruction including a token and a request to register the user device to receive a message associated with a particular application; update registration information to indicate that the user device is to receive the message based on receiving the first instruction; and provide a second instruction to a second server to cause the second server to provide the message to the user device on behalf of the first server. The second instruction may include information regarding the message, the token, and an instruction to provide the message to the user device associated with the token. The first server may receive, from the second server, a report indicating that the message was not delivered to the user device; and update the registration information to indicate that the user device is no longer to receive the message based on receiving the report.
Abstract:
A device may receive first data items and second data items that may have been output by sensor devices. The device may add, to a node in a data structure, at least some of the first data items. The device may divide the node to create subnodes that correspond to subregions of a geographic region. The device may add, to at least one of the subnodes, at least some of the second data items. The device may generate a probability of a first relationship, between the first data items and the second data items, based on determining subnodes that include a first data item and determining subnodes that exhibit a predefined second relationship with a second data item. The device may send, to another device, the probability of the first relationship to support location-based services.