Abstract:
A first device may receive a first session token from a second device; determine that the first session token is expired or invalid; provide a security input to the second device to cause the second device to generate a first hash value of the security input using a key corresponding to a key identifier (ID); receive the key ID and the first hash value from the second device; generate a second hash value using the key corresponding to the key ID; determine that the first hash value matches the second hash value; and establish a session with the second device based on determining that the first hash value matches the second hash value.
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 system may receive from a mobile device, a uniform resource identifier (URI) for accessing secure content associated with a toll-free data campaign for secure content (“campaign”) from a content provider device. The system may identify traffic information included in the URI. The system may compare the traffic information with stored traffic information associated with the campaign and may determine that the traffic information is associated with the campaign if the traffic information matches the stored traffic information. The system may determine that an analysis of a transport layer socket (TLS) handshake, performed between the mobile device and the content provider device, was successful for the campaign. The system may provide information to cause data charges, for a traffic flow, to be charged to a content provider based on determining that the traffic information is associated with the campaign and that the TLS handshake analysis was successful.
Abstract:
A system may include one more devices to receive traffic information for a peer-to-peer communication, between a mobile device and a peer-to-peer client device via a peer-to-peer server, associated with a peer-to-peer network. The system may identify peer-to-peer server information associated with the peer-to-peer server and included in the traffic information and may compare the peer-to-peer server information with stored peer-to-peer server information associated with a toll-free data service campaign (“campaign”). The system may determine that the peer-to-peer server information is associated with the campaign if the peer-to-peer server information matches the stored peer-to-peer server information and may provide information to cause data charges, for the traffic flow, to be charged to a service provider associated with the campaign based on determining that the peer-to-peer server information provided in the traffic information is associated with the campaign.
Abstract:
A device may receive information that identifies a toll-free data service campaign to be tested. The device may receive information that identifies a network to be used to test the toll-free data service campaign. The device may deploy the toll-free data service campaign on the network by deploying a campaign rule, associated with the toll-free data service campaign, that identifies a condition 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 determine a testing criteria for testing the toll-free data service campaign on the network. The device may test the toll-free data service campaign on the network using the testing criteria. The device may determine a test result based on testing the toll-free data service campaign, and may provide information that identifies the test result.
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 digital content distribution platform includes a content distribution device configured to store digital assets and associated metadata, encode and encrypt each of the digital assets, and publish the metadata associated with the assets to one or more catalog servers associated with multiple digital content retailers. The digital content distribution platform further includes a portal server configured to permit registration by the multiple digital content retailers to enable access to the stored digital assets by clients associated with the multiple digital content retailers. The digital content distribution platform also includes one or more license servers configured to engage in digital rights management (DRM) with multiple DRM servers associated with the multiple digital content retailers.
Abstract:
A device can receive, from a user device, a transmission control protocol (TCP) synchronize (SYN) packet associated with a request to establish a TCP connection with a server device. The device can prevent a first TCP connection from being established between the device and the user device based on the TCP SYN packet. The device can cause a second TCP connection to be established between the device and the server device based on the TCP SYN packet and after preventing the first TCP connection from being established. The device can cause a third TCP connection to be established between the device and the user device after causing the second TCP connection to be established. The device can transfer network traffic between the user device and the server device based on the second TCP connection and the third TCP connection.
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.