Device management scheduling based on trap mechanism
First Claim
Patent Images
1. A terminal, comprising:
- a network interface; and
a processor configured to install into the terminal a schedule context upon receipt from a server using a device management protocol,wherein the schedule context comprises at least one command for device management, and condition information,wherein the scheduling context further comprises a valid element for specifying a period in which the scheduling context is valid, and a server node for representing an owner of the scheduling context,wherein before installing, validity of the scheduling context is verified,wherein the condition information includes a trap element including an identifier specifying an event generated in the terminal,wherein the condition information further includes a time element specifying a time trigger to execute the at least one command,wherein the time element comprises a base element which specifies a time to execute the at least one command,wherein the time element further comprises a recurrence rule element which specifies a recurrence rule of the time trigger,wherein the processor is further configured to execute the at least one command according to the condition information when the event specified by the identifier occurs or when the time trigger occurs, andwherein the processor is further configured to report, to the server, at least one of a result from executing the at least one command or a state of the scheduling context.
0 Assignments
0 Petitions
Accused Products
Abstract
Performing device management scheduling based upon a trap mechanism is provided. A scheduling context, upon receipt from a server, is installed. The scheduling context may have at least one of a first element specifying information including at least one command for device management and a second element specifying a trap-based condition to execute the command. The command is the message specified by the first element is executed, if an occurrence of particular event specified by the second element is found.
-
Citations
4 Claims
-
1. A terminal, comprising:
-
a network interface; and a processor configured to install into the terminal a schedule context upon receipt from a server using a device management protocol, wherein the schedule context comprises at least one command for device management, and condition information, wherein the scheduling context further comprises a valid element for specifying a period in which the scheduling context is valid, and a server node for representing an owner of the scheduling context, wherein before installing, validity of the scheduling context is verified, wherein the condition information includes a trap element including an identifier specifying an event generated in the terminal, wherein the condition information further includes a time element specifying a time trigger to execute the at least one command, wherein the time element comprises a base element which specifies a time to execute the at least one command, wherein the time element further comprises a recurrence rule element which specifies a recurrence rule of the time trigger, wherein the processor is further configured to execute the at least one command according to the condition information when the event specified by the identifier occurs or when the time trigger occurs, and wherein the processor is further configured to report, to the server, at least one of a result from executing the at least one command or a state of the scheduling context. - View Dependent Claims (2)
-
-
3. A method for performing device management, the method comprising:
-
installing a schedule context into a terminal upon receipt from a server using a device management protocol, the schedule context comprising at least one command for device management, and condition information, wherein the scheduling context further comprises a valid element for specifying a period in which the scheduling context is valid, and a server node for representing an owner of the scheduling context, wherein before installing, validity of the scheduling context is verified, wherein the condition information includes a trap element including an identifier specifying an event generated in the terminal, wherein the condition information further includes a time element specifying a time trigger to execute the at least one command, wherein the time element comprises a base element which specifies a time to execute the at least one command, and wherein the time element further comprises a recurrence rule element which specifies a recurrence rule of the time trigger; executing, by the terminal, the at least one command according to the condition information when the event specified by the identifier occurs or when the time trigger occurs; and reporting, by the terminal to the server, at least one of a result from executing the at least one command or a state of the scheduling context. - View Dependent Claims (4)
-
Specification