Device validation, distress indication, and remediation

• US 9,652,320 B2
• Filed: 12/15/2014
• Issued: 05/16/2017
• Est. Priority Date: 11/05/2010
• Status: Expired due to Fees

• Current Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Original Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Inventors: Shah, Yogendra C., Case, Lawrence, Howry, Dolores F., Cha, Inhyok, Leicher, Andreas, Schmidt, Andreas
• Primary Examiner(s): Manoskey, Joseph D
• Application Number:
  US14/570,301
• Publication Number:
  US 20150099510A1
• Time in Patent Office: 883 Days
• Field of Search: 714 27, 714 41, 714 43, 714 44, 714 25, 714 33, 714 36, 714 381, 714 471
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/08 Error detection or correction by redundancy in data representation, e.g. by using checking codes
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/575 Secure boot
• CPC Class Codes: G06F 2221/2103 Challenge-response
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04M 1/24 Arrangements for testing
• CPC Class Codes: H04W 12/10 Integrity
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

A wireless communications device may be configured to perform integrity checking and interrogation with a network entity to isolate a portion of a failed component on the wireless network device for remediation. Once an integrity failure is determined on a component of the device, the device may identify a functionality associated with the component and indicate the failed functionality to the network entity. Both the wireless network device and the network entity may identify the failed functionality and/or failed component using a component-to-functionality map. After receiving an indication of an integrity failure at the device, the network entity may determine that one or more additional iterations of integrity checking may be performed at the device to narrow the scope of the integrity failure on the failed component. Once the integrity failure is isolated, the network entity may remediate a portion of the failed component on the wireless communications device.

Claims

1. A wireless device comprising a processor, a memory, and communication circuitry, the wireless device configured to connect to a communications network via the communication circuitry, the wireless device including computer-executable instructions stored in the memory of the wireless device which, when executed by the processor of the wireless device, perform operations comprising:

performing a first integrity check on a component of the wireless device;

determining that the component has failed the first integrity check;

in response to determining that the component has failed the first integrity check, preventing a release of a key used for attachment to the communications network;

determining a functionality that corresponds to the failed component; and

sending, to a network entity, an indication of the functionality that corresponds to the failed component.

2. The wireless device claim 1, the operations further comprising:

storing a component-to-functionality map; and

determining the functionality that corresponds to the failed component based on the component-to-functionality map.

3. The wireless device of claim 1, the operations further comprising:

performing a second integrity check on the failed component to isolate a portion of the failed component for remediation by a network entity.

4. The wireless device of claim 3, the operations further comprising:

sending, to a network entity, an indication of the functionality that corresponds to the failed component, the indication comprising an alarm configured to trigger a remote update procedure with the network entity to replace the portion of the failed component.

5. The wireless device of claim 3, the operations further comprising:

receiving a request from the network entity to perform the second integrity check on the failed component to determine the portion of the failed component that caused the component to fail the first integrity check.

6. The wireless device of claim 3, the operations further comprising:

receiving a replacement component associated with the portion of the failed component; and

replacing the portion of the failed component with the replacement component.

7. The wireless device of claim 3, the operations further comprising:

performing one or more iterations of the second integrity check on the portion of the failed component to further isolate the portion of the failed component for remediation by the network entity.

8. The wireless device of claim 7, the operations further comprising:

sending, to a network entity, an indication of a functionality that corresponds to the portion of the failed component that caused the component to fail the first integrity check; and

receiving a request from the network entity to perform the one or more iterations of the second integrity check on the portion of the failed component.

9. The wireless device of claim 1, wherein determining that the component has failed the first integrity check further comprises:

determining an integrity measurement associated with the component;

comparing the integrity measurement with a trusted reference value associated with the component; and

determining that the integrity measurement does not match the trusted reference value.

10. In a system that comprises a wireless device and a network entity configured to communicate with each other directly or via a communications network, a method performed by the wireless device, the method comprising:

performing a first integrity check on a component of the wireless device;

determining that the component has failed the first integrity check; and

in response to determining that the component has failed the first integrity check, preventing a release of a key used for attachment to the communications network;

determining a functionality that corresponds to the failed component; and

sending, to the network entity, an indication of the functionality that corresponds to the failed component.

11. The method of claim 10, the method further comprising:

storing a component-to-functionality map; and

determining the functionality that corresponds to the failed component based on the component-to-functionality map.

12. The method of claim 10, the method further comprising:

performing a second integrity check on the failed component to isolate a portion of the failed component for remediation by a network entity.

13. The method of claim 12, the method further comprising:

sending, to the network entity, an indication of the functionality that corresponds to the failed component, the indication comprising an alarm configured to trigger a remote update procedure with the network entity to replace the portion of the failed component.

14. The method of claim 12, the method further comprising:

receiving a request from the network entity to perform the second integrity check on the failed component to determine the portion of the failed component that caused the component to fail the first integrity check.

15. The method of claim 12, the method further comprising:

receiving a replacement component associated with the portion of the failed component; and

replacing the portion of the failed component with the replacement component.

16. The method of claim 12, the method further comprising:

performing one or more iterations of the second integrity check on the portion of the failed component to further isolate the portion of the failed component for remediation by the network entity.

17. The method of claim 16, the method further comprising:

sending, to the network entity, an indication of a functionality that corresponds to the portion of the failed component that caused the component to fail the first integrity check; and

receiving a request from the network entity to perform the one or more iterations of the second integrity check on the portion of the failed component.

18. The method of claim 10, wherein determining that the component has failed the first integrity check further comprises:

determining an integrity measurement associated with the component;

comparing the integrity measurement with a trusted reference value associated with the component; and

determining that the integrity measurement does not match the trusted reference value.

19. A method comprising:

performing, in a wireless communication device, an integrity check on at least one component associated with the wireless communication device;

determining whether the at least one component has failed the integrity check;

when the at least one component is determined to have failed the integrity check, determining functionalities that correspond to the at least one failed component;

accessing a policy, at the wireless communication device, that maps the functionalities determined to correspond to the at least one failed component to at least one capability of the wireless communication device; and

enforcing a policy on the wireless communication device based on the determined at least one capability.

20. The method of claim 19, wherein the capability is a platform capability.

21. The method of claim 19, wherein a component-to-functionality map is used to determine the functionalities of a component.

22. The method of claim 21, wherein at least one functionality from the component-to-functionality map is used to determine the at least one capability.

23. The method of claim 22, wherein the capability corresponds to at least one policy to enforce.

24. The method of claim 19, wherein the policy enforces restrictions to access resources on the device.

25. The method of claim 19, wherein the policy changes the order in which components may be loaded by a loader of the device.

26. The method of claim 19, wherein the policy enforces control on execution of the at least one capability which is enabled by a loader of the device.

27. A wireless communication device comprising:

a processor adapted to execute computer-readable instructions;

a memory communicatively coupled to the processor, the memory having stored therein computer-readable instructions that, when executed by the processor, cause the processor to perform operations, the operations comprising;

performing, in a wireless communication device, an integrity check on at least one component associated with the wireless communication device;

determining whether the at least one component has failed the integrity check;

when the at least one component is determined to have failed the integrity check, determining functionalities that correspond to the at least one failed component;

accessing a policy, at the wireless communication device, that maps the functionalities determined to correspond to the at least one failed component to at least one capability of the wireless communication device; and

enforcing a policy on the wireless communication device based on the determined at least one capability.

28. The device of claim 27, wherein the capability is a platform capability.

29. The device of claim 27, wherein a component-to-functionality map is used to determine the functionalities of a component.

30. The device of claim 29, wherein at least one functionality from the component-to-functionality map is used to determine the at least one capability.

31. The device of claim 30, wherein the capability corresponds to at least one policy to enforce.

32. The device of claim 27, wherein the policy enforces restrictions to access resources on the device.

33. The device of claim 27, wherein the policy changes the order in which components may be loaded by a loader of the device.

34. The device of claim 27, wherein the policy enforces control on execution of the at least one capability which is enabled by a loader of the device.