Patent application number | Description | Published |
20130003950 | SECURITY KEY CREATION - A device may obtain calling security parameters, may communicate the calling security parameters to a network device, and may receive, from the network device, a calling parameters identifier associated with the calling security parameters. The device may communicate the calling parameters identifier to a called device, may receive a called parameters identifier from the called device, and may communicate the called parameters identifier to the network device. The device may receive called security parameters from the network device, may create a security key based on the calling security parameters and the called security parameters, and may communicate with the called device using the security key. | 01-03-2013 |
20130007434 | LOCAL SECURITY KEY GENERATION - A calling device may obtain a first calling security parameter by registering with a network and obtain a second calling security parameter in response to causing an application authentication architecture of the network to verify that that the calling device is authorized to access a network service corresponding to a communication application stored by the calling device. The calling device may communicate the first and second calling security parameters to a called device and receive first and second called security parameters from the called device in response to communicating the first and second calling security parameters. The calling device may generate a security key based on the first calling security parameter, the second calling security parameter, first called security parameter, and the second called security parameter, and use the security key to encrypt or decrypt communication between the calling device and the called device. | 01-03-2013 |
20130149996 | PUBLIC KEY CRYPTOGRAPHY FOR APPLICATIONS REQUIRING GENERIC BOOTSTRAP ARCHITECTURE - A mobile terminal is configured to store information associated with accessing an application that requires bootstrapping; recognize an invocation of the application; identify a rule, included in the information, associated with accessing the application; determine whether the rule indicates that a user of the mobile terminal is allowed to access the application; determine whether the mobile terminal supports the bootstrapping; and provide access to the application when the rule indicates that the user of the mobile terminal is allowed to access the application and when the mobile terminal supports the bootstrapping. | 06-13-2013 |
20130152178 | SECURE ENTERPRISE SERVICE DELIVERY - A device receives enterprise information associated with enterprises supported by a network, and determines enterprise identifiers for one or more enterprises identified in the enterprise information. The device also receives information associated with devices and subscribers of the network, and determines security key parameters based on the information associated with the devices and the subscribers of the network. The device further generates, based on the security key parameters, a security key for each of the enterprise identifiers. | 06-13-2013 |
20130152208 | SECURITY KEY MANAGEMENT BASED ON SERVICE PACKAGING - A device receives application information associated with applications provided by a network, and determines service package identifiers for one or more applications identified in the application information. The device also receives information associated with devices and subscribers of the network, and determines security key parameters based on the information associated with the devices and the subscribers of the network. The device further generates, based on the security key parameters, a security key for each of the service package identifiers. | 06-13-2013 |
20130232335 | NETWORK OPTIMIZATION FOR SECURE CONNECTION ESTABLISHMENT OR SECURE MESSAGING - A first device is configured to receive an instruction to establish a secure connection with a second device or to send a secure message to the second device. The instruction may include a secure connection invitation or a message. The first device may send information, associated with the second device, to a first server; receive a response from the first server; obtain parameters based on the response indicating that the second device is subscribed to the first server; communicate the parameters to the first server; receive a parameters identifier associated with the parameters; store the parameters identifier in the secure connection invitation or the message; and send the secure connection invitation or the message to the second device. The second device may receive the parameters identifier to obtain the parameters to establish the secure connection or to decrypt the secure message. | 09-05-2013 |
20130305040 | SECURE MESSAGING BY KEY GENERATION INFORMATION TRANSFER - A system is configured to receive a first authentication request from a first device, authenticate the first device, establish a secure connection with the first device based on authenticating the first device, and receive, via the secure connection with the first device, a set of parameters from the first device. The first device is capable of generating an encryption key for a secure message, intended for a second device, based on the set of parameters. The system is also configured to receive a second authentication request from a second device, authenticate the second device and establish a secure connection with the second device based on receiving the second authentication request, and send, via the secure connection with the second device, the set of parameters to the second device. The second user device is capable of generating a decryption key for the secure message based on the set of parameters. | 11-14-2013 |
20140044263 | CENTRALIZED KEY GENERATION - A first network device is configured to receive a request for a secret key, generate the secret key, and send the secret key to a second network device, a third network device, and a wireless user device. The second network device may send content, encrypted with the secret key, to the wireless user device. The third network device may send content, encrypted with the secret key, to the wireless user device when the second network device is not sending content to the wireless user device. The wireless user device may use the secret key to decrypt the content received from the second network device or the third network device. | 02-13-2014 |
20140052981 | CENTRALIZED KEY MANAGEMENT - A first network device is configured to receive a first request for a first secret key, generate the first secret key, and send the first secret key to a second network device and a first user device; and is also configured to receive a second request for a second secret key, generate the second secret key, and send the second secret key to a third network device and a second user device. The second network device and the first user device may mutually authenticate each other using the first secret key. The third network device and the second user device may mutually authenticate each other using second secret key. | 02-20-2014 |
20140115333 | SECURE INFORMATION DELIVERY - A first network device is configured to receive a request for content from a user device, determine that the user device is not authenticated, and send information to the user device that the user device requires authentication. The first network device is configured further to receive a notification that the user device is authorized to receive content from multiple content providers. The first network device is configured further to generate a secret key and authenticate the user device by using the secret key. The first network device is further configured to send the content to the user device. | 04-24-2014 |
20140115673 | AUTHENTICATION PROCESS - A first network device is configured to receive a request for content from a user device, determine that the user device is not authenticated, and send information to the user device that the user device requires authentication. The first network device is configured further to receive authentication information for the user device from a second network device. The first network device is configured further to generate a secret key, authenticate the user device. The first network device is configured further to request user knowledge information from the user device, validate the user knowledge information and send the content to the user device. | 04-24-2014 |
20140235258 | APPLICATION SERVER AWARENESS OF DEVICE CAPABILITIES IN A WIRELESS NETWORK - Capability information, relating to hardware and/or software capabilities of different types of mobile devices, may be used to tailor services provided to the mobile device based on the particular type of mobile device. In one implementation, a device, such as an application server that provide services to mobile devices, may: receive a request from a mobile device, for services; obtaining information indicating a type of the mobile device; obtain, based on the type of mobile device, information indicating capabilities of the mobile device; and provide the services to the mobile device, in which the provided services are tailored for the mobile device based on the capabilities of mobile device. | 08-21-2014 |