KR101390013B1 - Method for periodcally managing dm clients and system therefor - Google Patents

Abstract

The present invention provides a system for periodically managing a DM client in a device management (DM) server.

The DM client periodically sends a check message to the DM server to check whether there is a DM action for the DM client. The DM server confirms the check message and, if there is a DM action for the DM client, sends a notification message for establishing the DM session to the DM client.

DM server, DM client

Description

System and method for periodically managing DM clients {METHOD FOR PERIODCALLY MANAGING DM CLIENTS AND SYSTEM THEREFOR}

The present invention relates to device management, and more particularly to a technique for establishing a DM session by a Device Management server.

As the number of wireless terminals has increased exponentially, a standardized method for managing wireless devices has been needed. A wireless service provider or a service provider communicates with the terminals wirelessly. Software, Parameters, Schedules and the like have been developed for mobile device management (Mobile Device Management) method. One example is OMA DM, developed by the Open Mobile Alliance, which creates application standards for wireless devices. OMA DM can manage the firmware, software, parameters, etc. inside the wireless terminal using the DM protocol. The device managing the wireless terminal is a DM server, and the managed object is a DM client like the wireless terminal.

The DM server uses the OMA DM protocol defined by OMA to manage devices remotely. The OMA DM protocol consists of five messages from Pkg # 0 to Pkg # 4, and a DM session can be established between the DM server and the device through the DM protocol. At this time, the DM session may be initiated by a DM server or a DM client, that is, a device.

1 is a diagram illustrating a general DM session set up process.

The server initiated session (Server Initiated Session) is as follows.

When there is a management action to be performed on the device, the DM server 20 transmits a Pkg # 0 notification message to the device, that is, the DM client 10 to inform that the DM management action exists (step). 32). The DM management action refers to an operation that needs to be executed to manage the DM client 10. Upon receiving the Pkg # 0 notification message, the DM client 10 sends a Pkg # 1 message to the DM server 20 to request a session establishment (step 34). Thereafter, the DM server 20 transmits a management command to the DM client 10 through Pkg # 2 messages (step 36). Thereafter, Pkg # 3 and Pkg # 4 messages are transmitted and received between the DM client 10 and the DM server 20 (steps 38 and 40). In this case, the Pkg # 0 notification message is mainly transmitted using a push mechanism, and Pkg # 1 to # 4 messages are mainly transmitted through a transport protocol such as HTTP (S).

The client initiated session (Client Initiated Session) is as follows.

The case where the DM client 10 initiates a DM session is mainly when there is an alarm message to be transmitted to the DM server 20 by the DM client 10. In this case, the DM client 10 transmits a Pkg # 1 message to the DM server 20 to request a DM session.

As such, in order to establish a DM session, the DM client 10 should deliver a Pkg # 1 message to the DM server 10. The Pkg # 1 message contains device information. The device information has the form of a MO (Management Object). OMA DM defines the terminal management targets as Management Objects (MO). That is, the terminal management is performed by the DM client 10 and the DM server 20 delivering management objects (hereinafter referred to as MO) using the DM protocol. The MO is an interface of the data model accessible by the DM server 20 and the DM client 10. MOs are defined in the OMA standard according to the service to be provided using the DM protocol.

2 illustrates DevInfo MO included in Pkg # 1. Referring to Figure 2, DevInfo MO is Bearer / <x> /, Vendor Ext. And so on. The DM client 10 passes the URI and data for all nodes of DevInfo Mo to the DM server 20 through a replace command through Pkg # 1, and the DM server 20 receives this command and receives the command. Compare and change with DevInfo in database's database.

As described above, the DM server 20 uses a push mechanism when initiating a DM session. When the device, that is, the DM client 10 is a general cellular phone, the DM server 20 transmits a DM Pkg # 0 notification message to the device through WAP PUSH or SMS.

In addition, in the case of a device that does not have a mechanism such as SMS or WAP Push, such as a WiMAX device, UDP push may be used. When using UDP push to deliver a DM Pkg # 0 notification message, the device must be in the Listening state with its UDP port always open. However, if a personal firewall is installed in the target device, this UDP port is not a well known port, so it is likely to be closed. Therefore, there is a high possibility that the Pkg # 0 message from the DM server 20 is blocked by the personal firewall.

If HTTP is used as the transport protocol, the device acts as an HTTP client and the DM server acts as an HTTP server. Therefore, only the HTTP response transmitted in response to the HTTP request transmitted from the device to the DM server 20 may pass through the personal firewall. However, since the Pkg # 0 DM notification message is initiated by the DM server 20, it is not a response message to the request from the device. Therefore, the Pkg # 0 DM notification message sent to the device via HTTP cannot be received by the device because it is blocked by the device's personal firewall.

Conventionally, a periodic polling method is used to solve this problem. Specifically, the DM client 10 periodically sends a Pkg # 1 message to the DM server 20 to check whether the DM management action exists in the DM server 20. In this case, when the DM client 10 transmits Pkg # 1 to the DM server 20, the DM server 20 puts a DM command in the Pkg # 2 message when there is a management action. To 10). On the other hand, when there is no management action, the DM server 20 terminates the DM session by transferring the command to the device, that is, the DM client 10, without putting any command in the Pkg # 2 message. As described above, according to the periodic polling method, a DM session is periodically established between the DM client 10 and the DM server 20 and then released.

Such periodic polling is inefficient by causing a load on the network because the DM client 10 periodically sends a message to the DM server 20 to form a DM session. Since there are a large number of devices in one network, if they all request a DM session periodically, it can put a heavy burden on the DM server 20 and the network. Especially in case of Pkg # 1 message, since DevInfo MO must be transmitted every time, it can be a bigger burden.

In addition, in order to reduce the load on the network, when the polling period is extended, when the data to be provisioned occurs due to the user's specific service subscription, the user cannot use the subscription service immediately because it cannot be provisioned in real time immediately. May occur.

An object of the present invention is to minimize the network load associated with periodic polling by defining a new message in order to minimize the above problems when the periodic polling method is used. That is, the present invention provides a system and method for managing a DM client by generating the periodic polling message without significantly changing the existing DM protocol.

To this end, the present invention provides a method for periodically managing a DM client in a device management (DM) server, before the DM server transmits a notification message for establishing a DM session to the DM client. Periodically transmitting a check message to the DM server to check whether a DM action for the DM client exists in the DM server, the DM server confirms the check message, and the DM action for the DM client And if present, sending a notification message for establishing the DM session to the DM client.

The present invention also provides a system for periodically managing a DM client in a device management (DM) server, wherein the DM server transmits a notification message for establishing a DM session to the DM server before the DM server transmits a notification message to the DM client. The DM client periodically sending a check message to the DM server to check whether there is a DM action for a DM client, and checking the check message, and if the DM action exists for the DM client, And the DM server sending a notification message for forming to the DM client.

According to the present invention, since the client always sends a request to the server and the server sends a response, the problem of the personal firewall of the client can be solved.

In addition, since the DM action check message for periodic polling (Check_DM_Action message) is small in size and the Ack code transmitted in response thereto is also simple, network burden due to periodic polling can be minimized.

Conventionally, a device that does not have a mechanism such as SMS, WAP Push, etc. cannot establish a DM session initiated by a DM server using UDP push. Therefore, in order to establish a DM session, the device, that is, the DM client, has to periodically transmit a Pkg # 1 message including device information (DM client information), that is, a DevInfo MO, to the DM server. However, since the Pkg # 1 message including the DevInfo MO has a large capacity, it may burden the network.

In addition, since device management actions for the DM client do not occur frequently, it is wasteful for the DM client to establish a DM session for device management with the DM server periodically.

To this end, the present invention periodically introduces a new message for checking whether a DM management action for a DM client exists in a DM server of a network. According to the present invention, the DM client periodically sends a check message to the DM server to check whether there is a DM Management Action for the DM server. In this specification, such a message is referred to as a DM action check message (Check_DM_Action message).

When the DM server receives the DM action check message, the DM server checks whether there is a management action for the corresponding DM client, and if the management action exists, transmits a Pkg # 0 notification message to initiate a DM session. In addition, the DM server transmits a response message in the form of an Ack code to the DM client indicating that the management action does not exist.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail.

3 is a block diagram showing the configuration of a DM server and a DM client according to an embodiment of the present invention.

Referring to FIG. 3, the DM client 100 periodically checks whether there is a timer 110 for measuring a period for checking a DM management action, and whether there is a DM action to be executed in the DM server 200. DM action check message generation unit 120 for generating a DM action check message (Check_DM_Action message) and a DM package generation and processing unit 130 for generating and processing a DM package message transmitted and received to the DM server 200; .

The timer 110 periodically measures a period for checking the DM management action, and notifies the DM action check message generator 120 when the period arrives. Upon receiving notification of the arrival of the period from the timer 110, the DM action check message generation unit 120 checks whether the DM management action for the DM client 100 exists in the DM server 200. Create a message. When the DM package 0 (Pkg # 0) notification message is received from the DM server 200 as a response to the check message, the DM package generation and processing unit 130 generates a package 1 message according to the OMA DM standard and generates a DM server ( 200). When receiving a response message from the DM server 200 including a code indicating that the DM management action for the DM client 100 does not exist in the DM server 200 as a response to the check message, the DM package is generated. The processor 130 does not transmit the DM package 1 message for establishing the DM session to the DM server 200.

In addition, the DM server 200 stores the DM action stack unit 210 and the DM client 100 that store the DM action when the DM action occurs to the DM client 100 until the DM action check message (Check_DM_Action message) is received. DM action check message processing unit 220 for processing a DM action check message from and a DM package generation and processing unit 230 for generating and processing a DM package message transmitted and received to the DM client 100.

When a DM action for the DM client 100 occurs, the DM action stack unit 210 stores the DM action until a DM action check message (Check_DM_Action message) is received. When the DM client 100 receives a check message for checking whether there is a DM management action for the DM client 100, the DM action check message processor 220 manages the DM for the DM client 100. It determines whether an action exists and transmits the result to the DM package generation and processing unit 230. If there is a DM management action for the DM client 100, the DM package generation and processing unit 230 generates a notification message for forming a DM session and transmits it to the DM client 100.

Hereinafter, a message flow between the DM server 200 and the DM client 100 according to embodiments of the present invention will be described.

First, a message flow between the DM server 200 and the DM client 100 when there is no DM action for the DM client 100 in the DM server 200 will be described with reference to FIG. 4.

Referring to FIG. 4, the DM client 100 checks whether a polling period has been reached using the timer 110. When the polling period is reached (step 400 and step 430), the DM client 100 sends a DM action check message (Check_DM_Action message) to the DM server 200 to check whether there is a DM action to be executed in the DM server 200. Transmit (step 410).

This DM action check message is a message for inquiring the DM server 200 whether a DM action exists or not, and its capacity is very small and is designed to have a simple structure. That is, the DM action check message includes an address and ID of the corresponding client (source), a DM server (destination) address, a command for instructing to check whether the DM action exists. And the DM action check message may not include information necessary to establish a DM session, for example, DevInfo MO. According to another embodiment, the DM action check message may further include credential information for device authentication.

The DM action check message may have the following structure, for example.

<SyncML xmlns = 'SYNCML: SYNCML1.2'>
<SyncHdr>
<VerDTD> 1.2 </ VerDTD>
<VerProto> DM / 1.2 </ VerProto>
<MsgID> 1 </ MsgID>
<Target>
<LocURI> http://www.syncml.org/mgmt-server </ LocURI>
</ Target>
<Source>
<LocURI> IMEI : 493005100592800 </ LocURI>
</ Source>
</ SyncHdr>
<SyncBody>
<Alert>
<CmdID> 1 </ CmdID>
<Data> 1204 </ Data><!-Check DM Action->
</ Alert>
<Final />
</ SyncBody>
</ SyncML>

In the conventional periodic polling method, since the DM client 100 uses Pkg # 1 to check whether a DM action exists, the DevInfo Mo needs to be transmitted and authenticated unnecessarily. This was inefficient. According to the present invention, as described above, a new simple message called a DM action check message (Check_DM_Action) is defined so that a message including at least the ID of the device, the user, that is, the DM client 100, is transmitted to the DM server 200. do.

Upon receiving the DM action check message from the DM client 100, the DM server 200 checks whether a DM action for the DM client 100 exists. If there is no DM action for the DM client 100, the DM server 200 sends a response message to the DM client 100 indicating that there is no DM management action waiting in response to the DM action check message Check_DM_Action. (Step 420).

This response message contains the address and ID of the client (destination), the DM server (source) address, and a code indicating whether the DM action exists. That is, the response message simply includes a code indicating that there is no DM action in the form of Ack code. This response message may have the following structure, for example.

<SyncML xmlns = 'SYNCML: SYNCML1.2'>
<SyncHdr>
<VerDTD> 1.2 </ VerDTD>
<VerProto> DM / 1.2 </ VerProto>
<MsgID> 1 </ MsgID>
<Target>
<LocURI> IMEI : 493005100592800 </ LocURI>
</ Target>
<Source>
<LocURI> http://www.syncml.org/mgmt-server </ LocURI>
</ Source>
</ SyncHdr>
<SyncBody>
<Status>
<MsgRef> 1 </ MsgRef><CmdRef> 1 </ CmdRef>
<CmdID> 7 </ CmdID>
<Cmd> Alert </ Cmd>
<Data> 220 </ Data><!-NO DM Action->
</ Status>
<Final />
</ SyncBody>
</ SyncML>

Subsequently, upon receiving a response message including a code indicating that there is no DM action from the DM server 200, the DM client 100 may know that there is no DM action to be performed on itself. Accordingly, the DM client 100 may not transmit DM Pkg # 1 for establishing a DM session.

Next, a message flow between the DM server 200 and the DM client 100 when there is a DM action for the DM client 100 in the DM server 200 will be described with reference to FIG. 5.

Referring to FIG. 5, the DM client 100 checks whether a polling period has been reached using the timer 110. When the polling period is reached (step 500), the DM client 100 transmits a DM action check message (Check_DM_Action message) to the DM server 200 to check whether there is a DM action to be executed in the DM server 200 ( Step 510). This DM action check message may be configured as described above.

Upon receiving the DM action check message from the DM client 100, the DM server 200 checks whether a DM action for the DM client 100 exists. If there is a DM action for the DM client 100, the DM server 200 sends a DM Pkg # 0 Notification message to the DM client 100 in response (step 520).

That is, if there is a DM management action to be executed for the DM client 100, the DM server 200 sends Pkg # 0 to the DM client 100 as a response to the DM action check message to form a normal DM session. To help. At this time, since the Pkg # 0 notification message is a response to the DM action check message (Check_DM_Action message) sent by the DM client 100, the Pkg # 0 notification message may be delivered to the DM client 100 safely through the personal firewall of the DM client 100. have. For example, in case of using the HTTP protocol, a DM action check message (Check_DM_Action message) is transmitted from the DM client 100 to the DM server 200 in the form of an HTTP request, and as a response, a Pkg # having an HTTP response form. Since the 0 message is transmitted from the DM server 200 to the DM client 100, the Pkg # 0 message may be delivered to the DM client 100 through the personal firewall of the DM client 100.

Upon receiving the Pkg # 0 notification message from the DM server 200, the DM client 100 transmits the Pkg # 1 message to the DM server 200 in accordance with the existing OMA DM standard to form a DM session (step 530). . Accordingly, the DM server 200 transmits commands for the DM action to the DM client 100 using the DM Pag # 2 message.

Next, specific operations in the DM server 200 and the DM client 100 will be described.

6 is a diagram illustrating an operation of a DM client according to the present invention.

Referring to FIG. 6, first, the DM client 100 drives the timer 110 in step 610 (step 610). Subsequently, the DM client 100 determines whether the timer has expired in step 620. If the timer has expired (step 620: YES), that is, if the value of the timer becomes 0, the DM action check message generator 120 generates a DM action check message and transmits it to the DM server 200 in step 630. . Subsequently, the DM client 100 receives a response message from the DM server 200 in step 640.

Upon receiving the message from the DM server 200 as described above, the DM client 100 determines whether the message is a DM package 0 (Pkg # 0) notification message in step 650.

If the response message is a DM package 0 notification message (step 650: YES), the DM client 100 proceeds to step 660 to generate a package 1 message according to the OMA DM standard through the DM package generation and processing unit 130 to generate a DM message. Send to server 200.

On the other hand, if the response message is not the DM package 0 notification message (step 650: NO), the DM client 100 checks the code indicating there is no DM action in the response message in step 670, and returns to step 610. According to an embodiment, if the timer has not expired (step 620: no), the process returns to step 610.

7 is a view showing the operation of the DM server according to the present invention.

Referring to FIG. 7, the DM server 200 first determines whether a DM action check message is received in step 710. The DM server 200 may identify the DM action check message received through the DM action check message processor 220. If the DM action check message is received (step 710: YES), the DM server 200 determines whether there is a DM management action currently pending for the Device ID included in the DM action check message in step 720. FIG. On the other hand, if the DM action check message has not been received (step 710: NO), it may be checked until the DM action check message is received.

If it is determined that there is a DM action for the corresponding DM client 100 (step 720: YES), the DM server 200 proceeds to step 730 and transmits a DM package 0 message to the DM client 100. On the other hand, if there is no DM action for the DM client 100, the DM server 200 transmits a response message including a code indicating that there is no DM action to the DM client 100 in step 740.

The DM action check message (Check_DM_Action) and its response message (Ack code), or Pkg # 0 to # 4 are all transmitted through a protocol such as HTTP.

1 is a diagram illustrating a general DM session set up process;

2 is a view showing DevInfo MO included in a package # 1 message;

3 is a block diagram showing the configuration of a DM server and a client according to an embodiment of the present invention;

4 is a diagram illustrating a message flow between a DM server and a DM client when there is no DM action for the DM client in the DM server;

5 is a diagram illustrating a message flow between a DM server and a DM client when a DM action for a DM client exists in the DM server;

6 is a view showing the operation of a DM client according to the present invention;

7 is a view showing the operation of a DM server according to the present invention.

Claims (12)

In the device management (DM) server to manage the DM client periodically, Periodically receiving a check message from the DM client instructing to check whether there is a DM management action for the DM client; Determining whether a DM management action exists for the DM client according to the check message; And transmitting a notification message for establishing a DM session to the DM client, if the DM management action exists. The method of claim 1, wherein the check message, And a command indicating to check whether the DM management action exists, an address of a DM server, an address and an ID of the DM client. The method of claim 2, wherein the check message further comprises information for device authentication. The method of claim 1, And if the DM management action does not exist, transmitting a response message including a code indicating that there is no DM management action to the DM client. 5. The method of claim 4, wherein the check message, notification message, and response message are based on the HTTP protocol. A system for periodically managing a DM client in a device management (DM) server, The DM client periodically transmitting a check message to the DM server to check whether there is a DM management action for the DM client, Determining whether the DM management action exists for the DM client according to the check message; and if the DM management action exists, sending the notification message for establishing a DM session to the DM client. DM client management system, characterized in that. The method of claim 6, wherein the check message, And a command for instructing to check whether the DM management action exists, an address of a DM server, an address and an ID of the DM client. 8. The DM client management system of claim 7, wherein the check message further includes information for device authentication. The method of claim 6, wherein the DM server, And if the DM management action does not exist, sending a response message including a code indicating that there is no DM management action to the DM client. The DM client management system of claim 9, wherein the check message, notification message, and response message are based on an HTTP protocol. A DM client periodically managed by a device management (DM) server, A timer that periodically measures the period for checking the DM management action, A message generator for generating a check message for checking whether a DM management action for the DM client exists in the DM server when notified of the arrival of the period from the timer; Receiving a DM package 0 (Pkg # 0) notification message in response to the check message from the DM server, DM package generation and processing unit for generating a package 1 message according to the OMA DM standard and transmits to the DM server; DM client, characterized in that. A DM server for periodically managing a device management (DM) client, A DM action stack unit for storing the DM action when a DM action is generated for the DM client; Upon receiving a check message for checking whether a DM management action for the DM client exists from the DM client, a check message processing unit for determining whether the DM management action for the DM client exists according to the check message. Wow,  And a DM package generation and processing unit for generating a notification message for forming a DM session and transmitting the DM message to the DM client if the DM management action exists.

Images