Triggering event processing

• US 10,038,999 B2
• Filed: 09/01/2015
• Issued: 07/31/2018
• Est. Priority Date: 12/19/2002
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Sprigg, Stephen A., Minear, Brian, Jacobs, Paul E.
• Primary Examiner(s): MADAMBA, GLENFORD J
• Application Number:
  US14/842,581
• Publication Number:
  US 20150373536A1
• Time in Patent Office: 1,064 Days
• Field of Search: 709228
• CPC Class Codes: H04L 67/30 Profiles
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

Systems, methods, and programs for processing extra data when a triggering event occurs. In one embodiment, an application, triggering event data, and extra data is stored on a wireless device. The wireless device monitors a triggering event parameter associated with an application, such as the expiration of the application. When the triggering event occurs, the wireless device processes the extra data in addition to processing associated with the triggering event data. The extra data may include URLs, scripts or other instructions that involve processing locally to the wireless device or requiring connection to a wireless network for remote processing on other devices.

Claims

1. A method of operating a client device, comprising:

downloading, to the client device, a software feature, a triggering event parameter associated with a triggering event, and extra data, wherein the triggering event includes deactivation of the software feature on the client device, and wherein the extra data is locally stored on the client device after the downloading and includes a set of actions to be executed and/or a link to a location from which to retrieve the set of actions to be executed;

monitoring, after the downloading, the triggering event parameter;

determining, based on the monitoring, that the triggering event parameter has occurred;

performing, in response to the determining and before processing the triggering event, the set of actions based on the locally stored extra data; and

processing, in response to the determining and after the performing, the triggering event.

2. The method of claim 1, wherein the triggering event parameter is date or time related.

3. The method of claim 1, wherein the triggering event parameter includes a number of uses or accesses to the software feature on the client device.

4. The method of claim 1, wherein the triggering event parameter includes execution of another software feature on the client device.

5. The method of claim 1, wherein the locally stored extra data includes a Uniform Resource Locator (URL).

6. The method of claim 1, wherein the set of actions includes a set of local actions to be performed locally by the client device, a set of remote actions to be implemented by the client device in coordination with a remote system, or a combination thereof.

7. The method of claim 1,

wherein the downloading downloads the software feature, the triggering event parameter, and the extra data from the same entity, or

wherein the downloading downloads the software feature, the triggering event parameter, and the extra data from two or more different entities.

8. A client device, comprising:

a processor means for downloading, to the client device, a software feature, a triggering event parameter associated with a triggering event, and extra data, wherein the triggering event includes deactivation of the software feature on the client device, and wherein the extra data is locally stored on the client device after the downloading and includes a set of actions to be executed and/or a link to a location from which to retrieve the set of actions to be executed;

a processor means for monitoring, after the downloading, the triggering event parameter;

a processor means for determining, based on the monitoring, that the triggering event parameter has occurred;

a processor means for performing, in response to the determination and before processing the triggering event, the set of actions based on the locally stored extra data; and

a processor means for processing, in response to the determination and after the set of actions is performed, the triggering event.

9. The client device of claim 8, wherein the triggering event parameter is date or time related.

10. The client device of claim 8, wherein the triggering event parameter includes a number of uses or accesses to the software feature on the client device.

11. The client device of claim 8, wherein the triggering event parameter includes execution of another software feature on the client device.

12. The client device of claim 8, wherein the locally stored extra data includes a Uniform Resource Locator (URL).

13. The client device of claim 8, wherein the set of actions includes a set of local actions to be performed locally by the client device, a set of remote actions to be implemented by the client device in coordination with a remote system, or a combination thereof.

14. The client device of claim 8,

wherein the processor means for downloading downloads the software feature, the triggering event parameter, and the extra data from the same entity, or

wherein the processor means for downloading downloads the software feature, the triggering event parameter, and the extra data from two or more different entities.

15. A client device, comprising:

at least one processor; and

at least one memory coupled to the at least one processor, the at least one processor and the at least one memory being configured to;

download, to the client device, a software feature, a triggering event parameter associated with a triggering event, and extra data, wherein the triggering event includes deactivation of the software feature on the client device, and wherein the extra data is locally stored on the client device after the downloading and includes a set of actions to be executed and/or a link to a location from which to retrieve the set of actions to be executed;

monitor, after the download, the triggering event parameter;

determine, based on the monitoring, that the triggering event parameter has occurred;

perform, in response to the determination and before processing the triggering event, the set of actions based on the locally stored extra data; and

process, in response to the determination and after the set of actions is performed, the triggering event.

16. The client device of claim 15, wherein the triggering event parameter is date or time related.

17. The client device of claim 15, wherein the triggering event parameter includes a number of uses or accesses to the software feature on the client device.

18. The client device of claim 15, wherein the triggering event parameter includes execution of another software feature on the client device.

19. The client device of claim 15, wherein the locally stored extra data includes a Uniform Resource Locator (URL).

20. The client device of claim 15, wherein the set of actions includes a set of local actions to be performed locally by the client device, a set of remote actions to be implemented by the client device in coordination with a remote system, or a combination thereof.

21. The client device of claim 15,

wherein the at least one processor is configured to download the software feature, the triggering event parameter, and the extra data from the same entity, or

wherein the at least one processor is configured to download the software feature, the triggering event parameter, and the extra data from two or more different entities.

22. A non-transitory computer readable medium containing instructions stored thereon, which, when executed on a client device, cause the client device to perform actions, the instructions comprising:

at least one instruction to cause the client device to download, to the client device, a software feature, a triggering event parameter associated with a triggering event, and extra data, wherein the triggering event includes deactivation of the software feature on the client device, and wherein the extra data is locally stored on the client device after the downloading and includes a set of actions to be executed and/or a link to a location from which to retrieve the set of actions to be executed;

at least one instruction to cause the client device to monitor, after the download, the triggering event parameter;

at least one instruction to cause the client device to determine, based on the monitoring, that the triggering event parameter has occurred;

at least one instruction to cause the client device to perform, in response to the determination and before processing the triggering event, the set of actions based on the locally stored extra data; and

at least one instruction to cause the client device to process, in response to the determination and after the set of actions is performed, the triggering event.

23. The non-transitory computer readable medium of claim 22, wherein the triggering event parameter is date or time related.

24. The on-transitory computer readable medium of claim 22, wherein the triggering event parameter includes a number of uses or accesses to the software feature on the client device.

25. The non-transitory computer readable medium of claim 22, wherein the triggering event parameter includes execution of another software feature on the client device.

26. The non-transitory computer readable medium of claim 22, wherein the locally stored extra data includes a Uniform Resource Locator (URL).

27. The non-transitory computer readable medium of claim 22, wherein the set of actions includes a set of local actions to be performed locally by the client device, a set of remote actions to be implemented by the client device in coordination with a remote system, or a combination thereof.

28. The non-transitory computer readable medium of claim 22,

wherein the at least one instruction to cause the client device to download causes the client device to download the software feature, the triggering event parameter, and the extra data from the same entity, or

wherein the at least one instruction to cause the client device to download causes the client device to download the software feature, the triggering event parameter, and the extra data from two or more different entities.