Abstract:
A system can receive an indication associated with establishing a transmission control protocol (TCP) connection. The system can determine, based on the indication, information that identifies a user device associated with the TCP connection. The system can determine, based on the information that identifies the user device, a predicted congestion level of a base station associated with the TCP connection. The system can select, based on the predicted congestion level, a congestion control algorithm to be implemented for the TCP connection. The system can cause the TCP connection to be established and implement the congestion control algorithm for the TCP connection.
Abstract:
A device can receive, from a user device, a hypertext transfer protocol (HTTP) CONNECT request associated with a toll-free data service. The user device can establish a first transmission control protocol (TCP) connection with a proxy server. The HTTP CONNECT request can request the proxy server to establish a second TCP connection with a content provider server. The device can determine, based on the HTTP CONNECT request, that an authorization condition is satisfied. The device can store information associated with a flow between the user device and the content provider server. The user device and the content provider server can establish a transport layer security (TLS) connection based on the first TCP connection and the second TCP connection. The device can provide the information associated with the flow to permit an account of an entity to be adjusted in association with the toll-free data service.
Abstract:
A device can determine a congestion window (CWND) value, associated with a first transmission control protocol (TCP) state, for a TCP flow that involves one or more devices using active queue management (AQM). The first TCP state to cause the CWND value to be increased at a particular rate. The device can determine a round trip time (RTT) value, associated with the first TCP state, for the TCP flow. The device can determine that one or more TCP state conditions are satisfied. The device can classify the TCP flow into a different TCP state. The different TCP state to cause the CWND value to be maintained, decreased, or increased at a rate that is different than the particular rate. The device can transmit one or more packets, associated with the TCP flow, based on classifying the TCP flow into the different TCP state.
Abstract:
A device may receive a request for an authorization code, associated with providing content to a second device, from the second device. The device may provide the authorization code to the second device. The device may receive, from a third device, a request for a unique device identifier corresponding to the authorization code. The request for the unique device identifier may include the authorization code. The unique identifier may be associated with a subscriber of a network. The subscriber may be associated with the second device. The device may provide the unique device identifier to the third device. The third device may be associated with providing the content to the second device. The content may be targeted to the subscriber based on the unique device identifier.
Abstract:
A system can receive an indication associated with establishing a transmission control protocol (TCP) connection. The system can determine, based on the indication, information that identifies a user device associated with the TCP connection. The system can determine, based on the information that identifies the user device, a predicted congestion level of a base station associated with the TCP connection. The system can select, based on the predicted congestion level, a congestion control algorithm to be implemented for the TCP connection. The system can cause the TCP connection to be established and implement the congestion control algorithm for the TCP connection.
Abstract:
A device can be configured to receive a transmission control protocol (TCP) packet from a user device and determine, based on data included in a header portion of the TCP packet, that the TCP packet includes a toll-free token. The toll-free token included in the TCP packet can be identified, an entity associated with the toll-free token can be identified, and an action can be performed based on the entity.
Abstract:
A device can determine a set of flow characteristics associated with an encrypted traffic flow. The set of flow characteristics can include a cumulative length of payload packets included in the encrypted traffic flow, an average payload length of the payload packets, and a throughput associated with the encrypted traffic flow. The device can determine, based on the set of flow characteristics, whether the encrypted traffic flow is likely to be a video traffic flow. The device can cause the encrypted traffic flow to be managed based on whether the encrypted traffic flow is likely to be a video traffic flow.
Abstract:
A device may identify a proxy connection associated with a first device and a second device. An application buffer of the proxy connection may be associated with a first buffer size for at least one of the first device or the second device. The proxy connection may be associated with a video communication. The device may determine a set of parameters relating to the proxy connection. The device may determine a buffer allocation for the proxy connection based on the set of parameters. The device may perform an alteration to the application buffer of the proxy connection to cause the application buffer of the proxy connection to be associated with a second buffer size. The second buffer size may be different from the first buffer size.
Abstract:
An approach is provide for creating a secure and user-identifiable service signature. The approach involves creating a signature associated with a service, wherein the service is provided by a service provider to a user in conjunction with another party, and wherein the signature is personalized to the user. The approach also involves presenting the signature to the user via a device receiving a delivery, a link for initiating the delivery, or a combination thereof of the service to the user.
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.