MANAGING HIDDEN SECURITY FEATURES IN USER EQUIPMENT

• US 20160057625A1
• Filed: 11/03/2015
• Published: 02/25/2016
• Est. Priority Date: 10/18/2013
• Status: Active Grant

• Current Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.), Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.), Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: ANDRADA, Mauricio Pati Caldeira de, NOMANI, Muhammad Salman, HAMMER, Howard G., SINHA, Shweta
• Granted Patent: US 9,578,507 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/4061 Push-to services, e.g. push-to-talk or push-to-video
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04M 7/0078 Security; Fraud detection; Fraud prevention
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 28/0215 based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0268 using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 52/0264 by selectively disabling software applications
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 30/70 in wireless communication networks

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.

Claims

1. A method, comprising:

;

modifying, with a device via a first application programming interface (API), a timer associated with the device, the device having a push to talk (PTT) application that is authenticated to access the first API,

the timer establishing when the device checks for traffic received from a network;

establishing, by the device and via a second API a data connection with the network;

determining, by the device and based on the data connection, a quality of service (QoS) framework for the network,

the QoS framework assigning priorities to different types of traffic associated with the device;

utilizing, by the device, the PTT application and the timer to establish a PTT session with another device via the network; and

prioritizing, by the device and based on the QoS framework, PTT traffic provided in the PTT session with the other device.

2. The method claim 1, where authenticating the PTT application comprises:

determining whether an authentication credential, associated with the PTT application, matches an authentication credential associated with a security application of the device;

authenticating the PTT application to access the first API and the second API when the authentication credential, associated the PTT application, matches the authentication credential associated with the security application; and

failing to authenticate the PTT application to access the first API and the second API when the authentication credential, associated the PTT application, fails to match the authentication credential associated with the security application.

4. The method of claim 1, where establishing the data connection with the network further comprises:

accessing the second API with the PTT application; and

utilizing the PTT application to instruct the second. API to establish the data connection with the network.

5. The method of claim 1, further comprising:

determining that the PTT application is removed from the device;

restoring, via the first API, the timer to a default value when the PTT application is removed from the device; and

removing, via the second API, the data connection with the network when the PTT application is removed from the device.

6. The method of claim 1, where the network includes an Internet protocol (IP) multimedia subsystem (IMS) network and a packet data network (PDN), and the method further comprises:

accessing the second API with the PTT application; and

utilizing the second API to establish the data connection with the IMS network and the PDN.

7. The method of claim 1, where modifying the timer further comprises:

decreasing the timer from a first value to a second value,

the first value of the timer causing the device to check for traffic received from the network at a first frequency,

the second value of the timer causing the device to check for traffic received from network at a second frequency, and

the second frequency being greater than the first frequency.

3. The method of claim I., where modifying the timer further comprises:

accessing the first API with the PTT application; and

utilizing the PTT application to instruct the first API to modify the timer.

8. A device comprising:

a memory to store a push-to-talk (PTT) application; and

one or more processors to;

modify, via a first application programming interface (API)), a timer associated with the device, the device having a push to talk (PTT) application that is authenticated to access the first API,

the timer establishing when the device checks for traffic received from a network,

establish, via a second API of the PTT application that is authenticated to access the second API, a data connection with the network,

determine, based on the data connection, a quality of service (QoS) framework for the network,

the QoS framework assigning priorities to different types of traffic associated with the device,

utilize the PTT application and the timer to establish a PTT session with another device via the network,

prioritize, based on the QoS framework, PTT traffic provided in the PTT session with the other device, and

utilize the PTT application to terminate the PTT session with the other device.

9. The device of claim 8, where, when authenticating the PTT application, the one or more processors are further to:

determine whether a credential associated with the PTT application matches a credential associated with a security application of the device, and

authenticate the PTT application to access the first API and the second API when the credential associated the PTT application matches the credential associated with the security application.

10. The device of claim 8, where, when modifying the timer, the one or more processors are further to:

access the first API with the PTT application, and

utilize the PTT application to instruct the first API to modify the timer.

11. The device of claim 8, where, when establishing the data connection with the network, the one or more processors are further to:

access the second API with the PTT application, and

utilize the PTT application to instruct the second API to establish the data connection with the network.

12. The device of claim 8, where the one or more processors are further to:

determine that the PTT application is removed from the device,

restore, via the first API, the timer to a default value when the PTT application is removed from the device, and

terminate, via the second API, the data connection with the network when the PTT application is removed from the device.

13. The device of claim 8, where the network includes an Internet protocol (IP) multimedia subsystem (IMS) network and a packet data network (PDN), and the one or more processors are further to:

access the second API with the PTT application, and

utilize the second API to establish the data connection with the IMS network an PDN.

14. The device of claim 8, where, when modifying the timer, the one or more processors are further to:

decrease the tinier from a first value to a second value,

the first value of the timer causing the device to check for traffic received from the network at a first frequency,

the second value of the timer causing the device to check for traffic received from the network at a second frequency, and

the second frequency being greater than the first frequency.

15. A non-transitory computer-readable medium for storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to;

cause a security application to;

modify, via a first application programming interface (API)), a timer associated with the device, the device having a push to talk (PTT) application that is authenticated to access the first API,

the timer establishing when the device checks for traffic received from a network,

establish, via the second API when the PTT application is permitted to access the second API, a data connection, with the network,

determine, based on the data connection, a quality of service (QoS) framework for the network,

the QoS framework assigning, priorities to different types of traffic associated with the device,

utilize the timer to establish a PTT session with another device via the network, and

prioritize, based on the QoS framework, PTT traffic provided in the PTT session with the other device.

16. The computer-readable medium of claim 15, where the instructions further comprise:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

cause the security application to;

determine whether a credential associated with the PTT application matches a credential associated with the security application, and

authenticate the PTT application to access the first API and second API when the credential associated the PTT application matches the credential associated with the security application.

17. The computer-readable medium of claim 15, where, when modifying the timer, the instructions further comprise:

one or more instructions that when executed by the one or more processors, cause the one or more processors to;

cause the PTT application to;

access the first API, and

instruct the first API to modify the timer.

18. The computer-readable medium of claim 15, where, when establishing the data connection with the network, the instructions further comprise:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

cause the PTT application to;

access the second API, and

instruct the second APE to establish the data connection with the network.

19. The computer-readable medium of claim 15, where the network includes an Internet protocol (IP) multimedia subsystem (EMS) network and a packet data network (PDN), and the instructions further comprise:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

cause the PTT application to;

access the second API, and

instruct the second API to establish the data connection with the IMS network and the PDN.

20. The computer-readable medium of claim 19, where the instructions further comprise:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

cause the security application to;

determine that the PTT application is uninstalled from the device,

restore, via the first API, the timer to a default value when the PTT application is uninstalled from the device, and

terminate, via the second API, the data connection with the network when the PTT application is uninstalled from the device.