Abstract: A device determines whether a PTT application is authenticated to access a first API and a second API, and prevents the PTT application from accessing the first and second APIs when the PTT application is not authenticated. The device permits the PTT application to access the first and second APIs when the PTT application is authenticated, and modifies, via the first API, a timer that dictates when the device checks for traffic received from a network. The device establishes, via the second API, a data connection with the network, and determines, based on the data connection, a QoS framework for the network. The device utilizes the PTT application and the timer to establish a PTT session with another device via the network, and prioritizes, based on the QoS framework, PTT traffic provided in the PTT session with the other device.

Abstract: A computer includes a processor, a network communication interface controlled by the processor, and a memory accessible by the processor. Programming is stored in the memory which configures the computer as a network server to support configuration of a user interface on a mobile device for control of an appliance. The network server: 1) receives and stores registration information from the appliance, which includes an identification of the appliance and information for configuring the user interface to control the appliance, 2) receives, over a cellular network, a request from a mobile device which includes the identification of the appliance, and 3) transmits, over the cellular network, the configuration information to the mobile device which is used to configure the mobile device to display the user interface for wirelessly controlling the appliance on the mobile device.

Abstract: A computer includes a processor, a network communication interface controlled by the processor, and a memory accessible by the processor. Programming is stored in the memory which configures the computer as a network server to support configuration of a user interface on a mobile device for control of an appliance. The network server: 1) receives and stores registration information from the appliance, which includes an identification of the appliance and information for configuring the user interface to control the appliance, 2) receives, over a cellular network, a request from a mobile device which includes the identification of the appliance, and 3) transmits, over the cellular network, the configuration information to the mobile device which is used to configure the mobile device to display the user interface for wirelessly controlling the appliance on the mobile device.

Abstract: A device may determine to adjust from a first state for an existing communication between the device and another device. The first state may be associated with utilizing a first audio and/or video configuration for communication. The device may determine a second state associated with a second audio and/or video configuration for the communication. The second audio and/or video configuration may be different from the first audio and/or video configuration. The device may provide state information associated with the second audio and/or video configuration via a first session initiation protocol message. The first session initiation protocol message may include directionality information associated with the second audio and/or video configuration. The device may receive confirmation information via a second session initiation protocol message based on providing the state information.

Abstract: Subscription status notification techniques are provided. A request is received by at least one server from a user equipment (UE) to attach to a wireless packet data communication network. The server determines whether the UE is associated with an enterprise identified by a service provider of the network as a sponsor of a data service through the network, based on an account of the UE stored on the server. Upon determining that the UE is associated with the enterprise, a notification message is sent from the server to the UE, through an information element field within an existing message in a bearer channel of the network. The UE is configured to control access to the network responsive to the subscription status in the notification message. The UE permits access to a sponsored data service associated with the enterprise sponsor regardless of the UE's ability to access non-enterprise associated data services.

Abstract: Generation and segregation of mobile device biometric application template storage is described. Applications request a memory domain within mobile device storage for storing enrolled templates in the domain. The application calls a secure API associated with the biometric driver and software of the mobile device. As a result, the biometric driver and software does not search a number of domains to locate the enrolled templates that correspond to the mobile application or search all enrolled templates stored in memory. The mobile device applications maintain control of the storage domain and the template. The enrolled template may only be deleted through the controlling mobile device application.

Abstract: Systems and methods for application signing are disclosed. In some implementations, an application package identifier and a password may be received at an application signing server. Upon authenticating the application package identifier and the password, a fingerprint identifying the developer is received. Upon receipt of the fingerprint, the application signing server generates a secure key for the application based on the fingerprint, where the secure key is provided to the developer for inclusion within the application. Upon determining that the application package identifier and the secure key included in a request from an operating system of a mobile device matches an authorized application package identifier and an authorized secure key stored at the application signing server, the application signing server provides the requested list of the one or more APIs to the operating system to grant the application access to the APIs in the list.

Abstract: A device provides, to another device, a start request for an evolved multimedia broadcast multicast services (eMBMS) session, and receives eMBMS session traffic from the other device based on the start request. The device determines track information from the eMBMS session traffic, and decodes the eMBMS session traffic into a format understood by the device. The device determines quality information associated with the eMBMS session traffic, and presents, for display, the decoded eMBMS session traffic, the track information, and the quality information associated with the eMBMS session traffic.

Abstract: A device may determine to adjust from a first state for an existing communication between the device and another device. The first state may be associated with utilizing a first audio and/or video configuration for communication. The device may determine a second state associated with a second audio and/or video configuration for the communication. The second audio and/or video configuration may be different from the first audio and/or video configuration. The device may provide state information associated with the second audio and/or video configuration via a first session initiation protocol message. The first session initiation protocol message may include directionality information associated with the second audio and/or video configuration. The device may receive confirmation information via a second session initiation protocol message based on providing the state information.

Abstract: To reduce the contribution of data communications for background applications to network congestion, the examples implement techniques in which congestion detection leads a mobile device to impose restriction on data communications by any application running in the background. The mobile device may detect congestion and/or the need to restrict background data communications in response to a message or instruction received from a node of the network; or the mobile device may itself more directly detect congestion from monitoring and analysis of device/network interaction behavior and trends. Upon detecting congestion, the mobile device turns on a background data restriction. For example, with the restriction on, all applications only running in the background without direct user interaction are blocked from sending requests for data communication to/through the network. However, with the restriction active, the mobile device can still provide data communication in response to user interaction with the device.

Abstract: A method includes attaching to a Packet Data Network (PDN) supporting services over a long term evolution (LTE) network to establish a first network connection. The method includes connecting to a wireless local area network, e.g. a WiFi network, to establish a second network connection. The method further includes launching an application accessing at least one of the supported services and receiving a request from the application to switch between the first and second network connections, according to the supported service, e.g. a policy associated with the service. Switching from the first network connection to the second network connections includes connecting to the PDN via an evolved Packet Data Gateway (ePDG).

Abstract: Systems and methods for device-based authentication are disclosed. In some implementations, a device receives a Single Sign On PIN from a backend server. The device transmits, to a token server, the Single Sign On PIN and credentials of a subscriber identity module (SIM) to request a token for accessing a network resource via a computer different from the device. The token is associated with a user account. The device receives the token from the token server. The device stores the token at a local memory of the device.

Abstract: Systems and methods for remote authentication using mobile single sign on credentials are disclosed. In some implementations, a proxy server receives, from a web access device, a request to access a secure online resource via the web access device. The proxy server receives, from a mobile device different from the web access device, one or more credentials for accessing the secure online resource. The proxy server determines that a geographic distance between the web access device and the mobile device is less than a geographic distance threshold. Upon determining that the geographic distance between the web access device and the mobile device is less than the geographic distance threshold, the proxy server enables the web access device access to the secure online resource.

Abstract: Systems and methods for mobile authentication for web payments are disclosed. In some implementations, a proxy server receives, from a computing device different from a mobile device, a request from a user to process a web payment via a payment account associated with the mobile device, the web payment being associated with an online merchant. The proxy server verifies that the mobile device is associated with the user. The proxy server transmits, to a commerce server of the online merchant, payment information for the web payment in response to verifying that the mobile device is associated with the user.

Abstract: Systems and methods for mobile-based login via wireless credential transfer are disclosed. In some implementations, a proxy server receives a registration request for a receiver device for accessing a secure resource. The proxy server registers the receiver device in response to the registration request. The proxy server receives, from a transmitter device, information identifying the transmitter device along with authentication credentials for authenticating the receiver device to access the secure resource. The proxy server identifies the receiver device based on the information identifying the transmitter device. The proxy server forwards, to the receiver device, the authentication credentials for authenticating access of the receiver device to the secure resource.

Abstract: A device determines whether a PTT application is authenticated to access a first API and a second API, and prevents the PTT application from accessing the first and second APIs when the PTT application is not authenticated. The device permits the PTT application to access the first and second APIs when the PTT application is authenticated, and modifies, via the first API, a timer that dictates when the device checks for traffic received from a network. The device establishes, via the second API, a data connection with the network, and determines, based on the data connection, a QoS framework for the network. The device utilizes the PTT application and the timer to establish a PTT session with another device via the network, and prioritizes, based on the QoS framework, PTT traffic provided in the PTT session with the other device.

Abstract: A device establishes a quality of service (QoS) framework with a network connected to the device. The device includes a push-to-talk (PTT) application, and the QoS framework assigns priorities to different types of traffic associated with the device. The device utilizes the PTT application to establish a PTT session with another device via the network, and prioritizes, based on the QoS framework, PTT traffic, provided in the PTT session, over best effort traffic during the PTT session with the other device.

Abstract: Information is provided to a mobile device while reducing the number of traffic channels established over a predetermined time period. A pull client on a mobile device receives requests for information from applications on the mobile device. The pull client creates a timing list which includes the timing requirements for each application. Applications that have overlapping timing requirements are grouped together into the same timing group. Once the time for creating a traffic channel for one of the groups arrives, a traffic channel is created between the mobile device and a carrier gateway. Information for each respective application within the same timing group is obtained through the network using the same traffic channel. When the requested information is provided to all applications within the same timing group, the traffic channel is released after a predetermined time. The method is repeated for a next timing group entry.

Abstract: Techniques described herein may use perceptual quality measurement techniques to test and/or evaluate communication sessions between mobile devices. A method may include receiving, by a mobile device and as part of an audio or video call with a second mobile device, a streamed version of a reference audio or video file; and reading a version of the reference audio or video file that was previously stored locally to the mobile device. The method may further include calculating, based on a comparison of the streamed version of the reference audio or video file to the version of the reference audio video file that was stored locally, a perceptual quality score for the streamed version of the reference audio or video file.

Abstract: Information is provided to a mobile device while reducing the number of traffic channels established over a predetermined time period. A pull client on a mobile device receives requests for information from applications on the mobile device. The pull client creates a timing list which includes the timing requirements for each application. Applications that have overlapping timing requirements are grouped together into the same timing group. Once the time for creating a traffic channel for one of the groups arrives, a traffic channel is created between the mobile device and a carrier gateway. Information for each respective application within the same timing group is obtained through the network using the same traffic channel. When the requested information is provided to all applications within the same timing group, the traffic channel is released after a predetermined time. The method is repeated for a next timing group entry.