Reporting information to a network

• US 20070174462A1
• Filed: 01/24/2007
• Published: 07/26/2007
• Est. Priority Date: 01/25/2006
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Kim, Te-Hyun, Hernandez, Pablo
• Granted Patent: US 8,407,329 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• 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/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
• CPC Class Codes: H04L 41/0604 using filtering, e.g. reduction of information by using priority, element types, position or time
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04W 48/08 Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 72/00 Local resource management

Abstract

For achieving device management, the terminal may select certain command execution results and transmit such to the network instead of always sending all command execution results. Accordingly, resources of the terminal and radio communication resources can be more efficiently utilized when compared to previously used device management procedures. Furthermore, since a record that is relevant to operations performed within the terminal is saved, even if a certain result of executing a particular command is not successfully transmitted to the network due to an error, the network may still be able to verify the command execution result by accessing the record that was stored in the terminal.

Claims

1. A terminal comprising:

a first module to search for a gating rule if a command for a device management is executed, and to determine whether a result from executing the command is reported to a server or gated-off according to the gating rule; and

a second module to report to the server the result from executing the command determined to be reported,

wherein the gating rule includes a first element to specify a reference number of the command to be gated-off and a second element to specify a response code to be gated-off.

2. The terminal of claim 1, further comprising:

a third module to receive a scheduling context including the command, a condition to execute the command and the gating rule, and to install the received scheduling context.

3. The terminal of claim 1, wherein the result corresponds to any one type of a Status, a Result, or an Alert.

4. The terminal of claim 3, wherein the determination is performed only for the Status type.

5. The terminal of claim 1, wherein the result includes at least one of:

a first field which represents a reference number of the command or a parameter of the command; and

a second field which represents a response code.

6. The terminal of claim 5, wherein the result further includes a third field which represents a kind of the command.

7. The terminal of claim 1, wherein the result includes at least one of:

any one of a CmdRef field which represents a reference number of the command, or a Correlator field which represents a parameter of the command; and

a Data field which represents a response code.

8. The terminal of claim 5, wherein the first module extracts at least one of the first field and the second field from the result, and compares the extracted first and second fields with the gating rule in order to determine whether the result should be reported.

9. The terminal of claim 1, wherein the first element of the gating rule corresponds to an Ref element and the second element of the gating rule corresponds to a Code element.

10. The terminal of claim 1, wherein the first module stores the result in an internal storage unit if it is determined that the result should not be reported.

11. The terminal of claim 1, wherein the second module achieves the reporting by creating a report message using the result and transmitting the message to the server.

12. The terminal of claim 1, wherein the second module further reports at least one of a status, an event which has been occurred in the terminal, and an error which has been occurred in the terminal to the server.

13. The terminal of claim 12, further comprising:

a third module to receive a scheduling context including the command, a condition to execute the command, the gating rule, and an event reporting rule, and to install the received scheduling context,

wherein the event reporting rule specifies whether at least one of the status, the event, and the error should be reported to the server.

14. The terminal of claim 1, further comprising:

a logging module to log a history relevant to at least one of whether or not a condition to execute the command is satisfied, whether or not an interaction with a user of the terminal with regard to the command execution is performed, whether or not the command is executed, and whether or not the result is reported.

15. The terminal of claim 14, further comprising:

a third module to receive a scheduling context including the command, a condition to execute the command, the gating rule, and a logging rule, and to install the received scheduling context,

wherein the logging rule specifies at least one of whether the logging should be enabled or not, and information for a buffer in which logged data is stored.

16. A server comprising:

a first module to create a scheduling context and to request an installation of the created scheduling context to a terminal; and

a second module to receive at least one of a result from executing a command for a device management and a status of the scheduling context from the terminal, and to parse at least one of the result and the status,

wherein the scheduling context includes at least one of a first element to specify the command, a second element to specify a condition to execute the command, a third element to specify a reference number of the command included in the result to be gated-off and a response code included in the result to be gated-off, and a fourth element to specify whether or not the status of the scheduling context should be reported to the server.

17. The server of claim 16, wherein the second module routes at least one of the result and the status to an other module in the server or an other server.

18. The server of claim 16, wherein the scheduling context further includes

a fifth element to specify whether a history of an operation relevant to the scheduling context should be logged, and information for a buffer in which logged data is stored.

19. The server of claim 18, wherein the history relates to at least one of whether or not the condition is satisfied, whether or not an interaction with a user of the terminal about the execution is performed, whether or not the command is executed, and whether or not the result is reported.

20. A method for reporting information to a server by a terminal, comprising:

searching for a gating rule which specifies whether a result from executing a command for a device management should be reported to a server or gated-off, if the command is executed;

determining whether the result from executing the command is reported to the server or gated-off, according to the gating rule if the gating rule is found; and

reporting the result determined to be reported to the server.

21. The method of claim 20, further comprising:

receiving an installation request for a scheduling context including the command, a condition to execute the command, and the gating rule from the server; and

installing the received scheduling context.

22. The method of claim 20, wherein in the reporting, at least one of a status of the terminal, an event which has been occurred in the terminal and an error which has been occurred in the terminal is further reported to the server.

23. The method of claim 22, further comprising:

receiving an installation request for a scheduling context from the server, the scheduling context including the command, a condition to execute the command, the gating rule, and an event reporting rule to specify whether at least one of the status, the event, and the error should be reported; and

installing the received scheduling context,

wherein the event reporting rule specifies whether at least one of the status, the event, and the error should be reported to the server.

24. The method of claim 20, wherein the reporting includes:

creating a report message using the result or the status; and

transmitting the created report message to the server.

25. The method of claim 21, further comprising:

logging a history relevant to at least one of whether or not a condition to execute the command is satisfied, whether or not an interaction with a user of the terminal about executing the command is performed, whether or not the command is executed, and whether or not a result of the execution has been reported.

26. A method for reporting information to a server by a terminal, comprising:

searching for a gating rule which specifies whether a result from executing a command for a device management should be reported or gated-off, if the command is executed;

extracting a reference number of the command and a response code from the result from executing the command;

comparing the extracted reference number with a reference number specified in the gating rule; and

comparing the extracted response code with a response code specified in the gating rule; and

reporting the result to a server if the extracted reference number and the extracted response code are not matched with each condition according to the gating rule.

27. The method of claim 26, further comprising:

receiving an installation request for a scheduling context from the server, the scheduling context including the command, a condition to execute the command, and the gating rule; and

installing the received scheduling context.

28. The method of claim 27, wherein in the reporting step,

at least one of a status, an event which has been occurred in the terminal and an error which has been occurred in the terminal is further reported to the server.