Abstract: A device may receive an indication to establish a communication session between a first device and a second device for a file transfer. The device may receive, from the second device, metadata. The metadata may be used to identify files of a set of files. The device may identify the files for transfer from the second device to the first device based on the metadata. The device may cause multiple communication sessions to be established between the first device and the second device. The multiple connections may be used to transfer the files from the second device to the first device. The device may receive, from the second device, the files. The files may be received via the multiple communication sessions.

Abstract: A device may receive an indication to establish a communication session between a first device and a second device for a file transfer. The device may receive, from the second device, metadata. The metadata may be used to identify files of a set of files. The device may identify the files for transfer from the second device to the first device based on the metadata. The device may cause multiple communication sessions to be established between the first device and the second device. The multiple connections may be used to transfer the files from the second device to the first device. The device may receive, from the second device, the files. The files Day be received via the multiple communication sessions.

Abstract: A device may receive an indication to establish a communication session between a first device and a second device for a file transfer. The device may receive, from the second device, metadata. The metadata may be used to identify files of a set of files. The device may identify the files for transfer from the second device to the first device based on the metadata. The device may cause multiple communication sessions to be established between the first device and the second device. The multiple connections may be used to transfer the files from the second device to the first device. The device may receive, from the second device, the files. The files may be received via the multiple communication sessions.

Abstract: Systems and methods for remote diagnostics are disclosed. In some implementations, a request for a device diagnostic session is provided from a mobile device to a diagnostic server. In response to the request, a messaging service message from the diagnostic server may be received at the mobile device. The messaging service message may include an authentication token. Upon receipt of the messaging service message including the authentication token, a diagnostic client resident at the mobile device may be initialized. Upon authenticating the authentication token included in the received messaging service message, a secure connection for the device diagnostic session may be established between the diagnostic server and the initialized diagnostic client. Diagnostic commands may be received at the diagnostic client from the diagnostic server via the established secure connection. The diagnostic commands may cause the diagnostic server to retrieve device diagnostics of the mobile device.

Abstract: A device may receive an indication to establish a communication session between a first device and a second device for a file transfer. The device may receive, from the second device, metadata. The metadata may be used to identify files of a set of files. The device may identify the files for transfer from the second device to the first device based on the metadata. The device may cause multiple communication sessions to be established between the first device and the second device. The multiple connections may be used to transfer the files from the second device to the first device. The device may receive, from the second device, the files. The files may be received via the multiple communication sessions.

Abstract: A mobile device, such as a smart phone, receives program instructions, such as program instructions to evaluate components and/or software in the mobile device. The mobile device detects a local network and determines whether an attribute of the local network matches a desired attribute, such as a service set identifier (SSID) identified in the program instructions. When the attribute of the local network matches the desired attribute, the mobile device executes the program instructions. If the attribute of the local network does not match the desired attribute, the mobile device continues to look for a matching local network before executing the program instructions.

Abstract: A mobile device, such as a smart phone, receives program instructions, such as program instructions to evaluate components and/or software in the mobile device. The mobile device detects a local network and determines whether an attribute of the local network matches a desired attribute, such as a service set identifier (SSID) identified in the program instructions. When the attribute of the local network matches the desired attribute, the mobile device executes the program instructions. If the attribute of the local network does not match the desired attribute, the mobile device continues to look for a matching local network before executing the program instructions.

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: An example of a system that provides notary services on behalf of an application client running on a mobile device is described. The application client requests a notarization token from an application notary service client running on the same mobile device. The application notary service client utilizes a SIM card of the mobile device to generate a notarization token request which is sent to an application notary service server. The application notary service server utilizes a SIM signature validator server to validate the notarization token request and generates the notarization token for delivery to the application client via the application notary service client. The application client includes the notarization token in a request to an application server, which uses the notarization token to validate the application client for access to a function or data of the server.

Abstract: A customer service system is described that uses a remote device diagnostic system to improve a customer's experience during a customer service call. Mobile device operating system application programming interfaces provide access to resources on a mobile device allowing an external customer service system to access device information. The customer service system utilizes a combination of application programming interfaces and a device management protocol to provide remote device diagnostics during a customer service call. For devices that support device management protocol, the customer service system uses application programming interfaces for retrieval of device parameters and uses device management for device parameter configuration. For devices that do not support device management, the customer service system uses application programming interfaces for device parameter retrievals, but does not provide capabilities for remote device parameter configuration.

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: Systems and methods for remote diagnostics are disclosed. In some implementations, a request for a device diagnostic session is provided from a mobile device to a diagnostic server. In response to the request, a messaging service message from the diagnostic server may be received at the mobile device. The messaging service message may include an authentication token. Upon receipt of the messaging service message including the authentication token, a diagnostic client resident at the mobile device may be initialized. Upon authenticating the authentication token included in the received messaging service message, a secure connection for the device diagnostic session may be established between the diagnostic server and the initialized diagnostic client. Diagnostic commands may be received at the diagnostic client from the diagnostic server via the established secure connection. The diagnostic commands may cause the diagnostic server to retrieve device diagnostics of the mobile device.

Abstract: An example of a system that provides notary services on behalf of an application client running on a mobile device is described. The application client requests a notarization token from an application notary service client running on the same mobile device. The application notary service client utilizes a SIM card of the mobile device to generate a notarization token request which is sent to an application notary service server. The application notary service server utilizes a SIM signature validator server to validate the notarization token request and generates the notarization token for delivery to the application client via the application notary service client. The application client includes the notarization token in a request to an application server, which uses the notarization token to validate the application client for access to a function or data of the server.

Abstract: Single sign on (SSO) functionality is provided across native and hybrid applications executing on a mobile communication device, such that both native and hybrid applications can access authenticated services offered through respective application servers without repeatedly providing authentication credentials. In operation, the mobile device obtains an SSO token from an SSO server providing the SSO functionality, and native applications executing on the mobile device retrieve the SSO token from memory for use in accessing authenticated services. In the case of hybrid applications, an alias is assigned to the mobile device in response to receiving a page request received from the hybrid application. The alias is associated with SSO token of the mobile device in the SSO server, and is used to provide the SSO token directly to the hybrid application from the SSO server such that the hybrid application can use the SSO token for authentication.

Abstract: Single sign on (SSO) functionality is provided across native and hybrid applications executing on a mobile communication device, such that both native and hybrid applications can access authenticated services offered through respective application servers without repeatedly providing authentication credentials. In operation, the mobile device obtains an SSO token from an SSO server providing the SSO functionality, and native applications executing on the mobile device retrieve the SSO token from memory for use in accessing authenticated services. In the case of hybrid applications, an alias is assigned to the mobile device in response to receiving a page request received from the hybrid application. The alias is associated with SSO token of the mobile device in the SSO server, and is used to provide the SSO token directly to the hybrid application from the SSO server such that the hybrid application can use the SSO token for authentication.