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 provides, to a user device, an application for managing viewing and sharing of content available via an Internet service provider, and assigns a unique code for a user of the user device. The network device provides a catalog of available content items that includes toll-free data (TFD) content items with a different TFD uniform resource locator (URL) for each TFD content item in the catalog of available content items. The network device receives a user's selection, from the catalog, of a TFD content item to share, and generates a sharing URL based on a TFD URL for the selected TFD content item and the unique sharing code. The network device provides the sharing URL to the user device for sharing with other users.
Abstract:
A device receives, from a client device, a first request associated with target audience criteria and a time constraint. Based on the target audience criteria, the device sends, to an information device, a network state request. In response to the network state request, the device receives, from the information device, a network state response including user data associated with user devices. Based on the network state response, the device determines a predicted network state, including predicted user data associated with the user devices, associated with the time constraint. Based on the predicted network state and the target audience criteria, the device determines a predicted quantity of user devices associated with both the target audience criteria and the time constraint. The device sends, to the client device, a first response based on the determination of the predicted quantity of user devices.
Abstract:
A device may receive an indication that a first device, a second device, and a third device are within communication range of a target device. The first device may be outside of communication range of a positioning system that provides information for determining a location. The target device may be outside of communication range of the positioning system and outside of communication range of three or more devices which are within communication range of the positioning system. The device may receive information that identifies a first location associated with the first device, a second location associated with the second device, and a third location associated with the third device. The device may determine a target device location based on the information that identifies the first location, the second location, and the third location. The device may provide or store information that identifies the target device location.
Abstract:
A device may receive a request for a mobile device to obtain an application. The request may include a mobile device identifier for the mobile device. The device may send, to the mobile device, a link to a web page. The device may receive, from the mobile device, a request for the web page. The device may send, to the mobile device, a redirect to a software distribution platform to obtain the application from the software distribution platform. The device may receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform. The device may send, to a message server, a request for a message to be sent to the mobile device. The request may be based on the registration identifier and the application.
Abstract:
A device may receive a request for a mobile device to obtain an application. The request may include a mobile device identifier for the mobile device. The device may send, to the mobile device, a link to a web page. The device may receive, from the mobile device, a request for the web page. The device may send, to the mobile device, a redirect to a software distribution platform to obtain the application from the software distribution platform. The device may receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform. The device may send, to a message server, a request for a message to be sent to the mobile device. The request may be based on the registration identifier and the application.
Abstract:
An instant access device may receive a request from a user device to access secure content corresponding to a particular web service. The instant access device may create a hash code based on a telephone number of the user device and a hash code, and may communicate the hash code to an authentication system. The authentication system may authenticate the user device by comparing the hash code to a hash table that includes a list of hash codes associated with user devices that are authorized to access the secure content. Based on whether the user device is authenticated by the authentication system, the instant access device may cause the user device to access the secure content, whether by accessing the secure content directly (when the user device authentication is successful) or by creating a new user account (when the user device authentication is unsuccessful).
Abstract:
A device may receive a request for a mobile device to obtain an application. The request may include a mobile device identifier for the mobile device. The device may send, to the mobile device, a link to a web page. The device may receive, from the mobile device, a request for the web page. The device may send, to the mobile device, a redirect to a software distribution platform to obtain the application from the software distribution platform. The device may receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform. The device may send, to a message server, a request for a message to be sent to the mobile device. The request may be based on the registration identifier and the application.
Abstract:
Techniques described herein may be used to enable users to access services protected by two-factor security systems without having to provide additional authentication information (e.g., a portion of the user's social security number, biometric information, etc.). An application server may provide one or more services, such as a social networking service, an online banking service, etc. When a user device attempts to access the service, the user may provide a username and password, to the application server, as the first factor of a two-factor authentication process required to access the service. However, instead of requiring the user to provide additional authentication information (e.g., the second factor), a network authentication server, the application server, and the user device may collaborate to automatically provide the additional authentication information.
Abstract:
Techniques described herein may be used to enable users to access services protected by two-factor security systems without having to provide additional authentication information (e.g., a portion of the user's social security number, biometric information, etc.). An application server may provide one or more services, such as a social networking service, an online banking service, etc. When a user device attempts to access the service, the user may provide a username and password, to the application server, as the first factor of a two-factor authentication process required to access the service. However, instead of requiring the user to provide additional authentication information (e.g., the second factor), a network authentication server, the application server, and the user device may collaborate to automatically provide the additional authentication information.