KR101417012B1 - Method and apparatuses for holding Device Management(DM) session - Google Patents

Method and apparatuses for holding Device Management(DM) session Download PDF

Info

Publication number
KR101417012B1
KR101417012B1 KR1020070102119A KR20070102119A KR101417012B1 KR 101417012 B1 KR101417012 B1 KR 101417012B1 KR 1020070102119 A KR1020070102119 A KR 1020070102119A KR 20070102119 A KR20070102119 A KR 20070102119A KR 101417012 B1 KR101417012 B1 KR 101417012B1
Authority
KR
South Korea
Prior art keywords
session
client
server
message
management
Prior art date
Application number
KR1020070102119A
Other languages
Korean (ko)
Other versions
KR20090036841A (en
Inventor
금지은
전해영
김욱
Original Assignee
삼성전자주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자주식회사 filed Critical 삼성전자주식회사
Priority to KR1020070102119A priority Critical patent/KR101417012B1/en
Publication of KR20090036841A publication Critical patent/KR20090036841A/en
Application granted granted Critical
Publication of KR101417012B1 publication Critical patent/KR101417012B1/en

Links

Images

Abstract

The present invention provides a system and method for maintaining a DM session.

A method for maintaining a DM session according to the present invention comprises the steps of: the DM server including an element for instructing to maintain a DM session in a message transmitted to the DM client immediately before the end of the DM session; And maintaining the DM session when receiving the message.

DM server, DM client

Description

[0001] The present invention relates to a method and apparatus for maintaining a DM session,

The present invention relates to device management, and more particularly to techniques for maintaining a DM session for device management.

As the number of wireless terminals increases exponentially, a standardized method for managing wireless devices is needed. A wireless provider or a service provider communicates wirelessly with terminals, and the firmware, software, parameters, schedule (Mobile Device Management) method has been developed in order to manage the functions (firmware, software, parameters, schedule, etc.). One example is OMA DM, developed by the Open Mobile Alliance, which creates application standards for wireless devices. The OMA DM can manage the firmware, software, and parameters inside the terminal by reading, adding, changing, and executing the object of the wireless terminal using the DM protocol. The device managing the wireless terminal is a DM server, and the management object is a client like a wireless terminal.

The DM server uses the OMA DM protocol defined by OMA to remotely manage the device. The OMA DM protocol consists of a total of five messages from Package # 0 to Package # 4. A DM Session can be formed between the DM server and the device through the DM protocol. At this point, the DM session may be initiated by the DM server or client, i. E., The device.

1 is a diagram illustrating a general DM session setup process.

1, when there is a management operation to be performed on a device, the DM server 20 transmits a Package # 0 Notification Message to the device, that is, the DM client 10, (Step 101). Upon receiving the Package # 0 notification message, the DM client sends a Package # 1 message to the DM server to request session formation (step 103). The DM server 10 transmits a Pkg # 2 message for DM session setup to the DM client 10 and the DM client 10 transmits a Package # 3 message to the DM server 20 in response to the Package # 2 message 105).

Then, the DM server 20 transmits a management operation to the DM client via the Package # 4 message (step 107), and the DM client 10 sends a Package # 5 message to the DM To the server 20 (step 109). Then, the DM server 20 can provide management commands to the DM client 10 through the Package # 4 message. In this case, the DM session is maintained if the management operation contained in the Package # 4 message requires immediate transmission of a response, e.g., status or results, from the DM client 10. If the management operation does not request a response from the DM client 10, the DM session is terminated.

However, even if the management operation does not require a response from the client 10, the DM client 10 may transmit a predetermined message in response to the management operation. For example, the DM client 10 can send a result to the DM server 20 after performing a management operation. In this case, if the DM client 10 tries to transmit a result to the DM server 20 in a state where the DM session is terminated, a DM session must be newly formed. That is, a DM session between the DM client 10 and the DM server 20 should be newly formed through the Package # 0 to Package # 2 messages (steps 111 to 115). Accordingly, the DM server 20 and the DM client 10 have to newly connect a connection of a transport layer, and also have to undergo an authentication process. In this case, frequent DM session setups result in wasted resources.

The present invention provides a system and method for holding a DM session to prevent resource waste due to frequent DM session setup.

To this end, the present invention provides a method for maintaining a DM session between a device management (DM) server and a DM client, wherein the DM server maintains a DM session in a message sent to the DM client immediately before the end of the DM session And a step of maintaining a DM session when the DM client receives the message.

According to the present invention, since the DM server can selectively transmit a message for maintaining the DM session to the DM client, resource waste due to frequent setup of the DM session can be prevented.

Conventionally, if the management operation included in the Package # 4 message transmitted from the DM server does not require a response from the DM client, the DM session is terminated. Therefore, When transferring to the server, a new DM session had to be formed.

According to the present invention, when a condition for maintaining a DM session occurs, the DM server includes an element for instructing to maintain a DM session in a Package # 4 message, and then transmits a Package # 4 message to the DM client. If the DM client includes an element instructing to maintain a DM session in the Package # 4 message, the DM client maintains the DM session without terminating the DM session.

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.

2 is a diagram illustrating a message flow between a DM server and a DM client according to a preferred embodiment of the present invention.

2, when the DM server 400 has a management operation to be performed on a device, the DM server 400 transmits a Package # 0 Notification Message to the DM client 300 to establish a DM session, (Step 201). Upon receiving the Package # 0 notification message, the DM client 300 sends a Package # 1 message to the DM server 400 to request a session formation (step 203). The DM server 400 transmits a Package # 2 message for DM session setup to the DM client 300 and the DM client 300 transmits a Package # 3 message to the DM server 400 in response to the Package # 2 message (Step 205). Then, the DM server 400 delivers management operations to the DM client 300 through the Package # 4 message (step 207). At this time, the DM server 400 transmits the management operations to the DM client 300 It is determined whether it is efficient to maintain the current DM session even if the management action does not require an immediate response from the DM client. Specifically, the DM server 400 may receive the result of the management operation transferred to the DM client 300 by the DM client 300, from the DM client after the management operation is completed. In addition, the DM server 400 may receive a status from the DM client in accordance with the management operation transferred to the DM client 300 by the DM client 300. [

Accordingly, if the management operation to be transmitted to the DM client 300 does not require a response from the DM client, the DM server 400 instructs the DM client 300 to maintain the DM session, Element in the Package # 4 message or in the Package # 4 message. An element for instructing to maintain such a DM session, a so-called sessionhold element, can be inserted into any part of the part constituting the Package # 4 message. Preferably, the element directing to maintain the DM session is inserted into the sync header of the Package # 4 message.

An element (Sessionhold element) instructing to maintain a DM session can be defined as shown in Table 1 below.

Sessionhold  element definition Usage : Specify server's request for client to terminate ongoing session.
Parent Elements : SyncHdr ,
Restrictions :
- This Element SHALL NOT be included in the message from the DM Client to DM Server. When the DM Client receives a message with this element, the DM Client SHALL NOT disconnect the DM session. If the value of this element is not present or this element is not exist, that means the DM session is not necessary to hold hold.
Content Model :
(# PCDATA )
Attributes: None.

As shown in Table 1 above, the session maintenance element is not included in the message from the DM client to the DM server. When a DM client receives a message with this session maintenance element, it must not terminate the DM session. If this session holding element is not present or does not exist in the message from the DM server, this means that there is no need to maintain a DM session.

If the DM server 400 needs to maintain the DM session, the DM client 400 transmits a message including the above-described session maintenance element to the DM client 300 (step 209). When the DM client 300 receives the message including the session maintenance element, it does not terminate the DM session.

Accordingly, the DM client 300 can transmit status information or result information as a result of performing the management operation from the DM server 400 to the DM server 400 through the Generic Alert message (step 211).

A description will be given of a case where the DM server 400 wishes to transmit a management operation instructing the DM client 300 to update the firmware of the DM client 300 to the DM client 300. [

First, the DM server 400 transmits a Package # 0 message to the DM client 300 to start forming a DM session. Accordingly, the DM client 300 transmits its device information to the DM server 400 through the Package # 1 message. Upon receiving the Package # 1 message, the DM server 400 transmits an initial management operation or a command through the Package # 2 message. In this embodiment, the DM server 400 requests the information on the firmware of the DM client 300 as a Package # 2 message. When the DM client 300 receives the Package # 2 message, the DM client 300 transmits a Package # 3 message including information on the firmware itself to the DM client 300 in response to the message. Then, the DM server 400 informs the URL where the download package exists by using the Package # 4 message, and instructs the firmware update using the EXEC DM command.

At this time, the DM server 400 determines whether it is efficient to maintain the current DM session even if the management operation to be transmitted to the DM client 300 does not require a response from the DM client. Specifically, when delivering the firmware update management operation, the DM server 400 determines whether it is necessary to report the device status or the result of the firmware update execution from the DM client 400. [

If the DM server 400 determines that it is necessary to maintain the current DM session even though the management operation transmitted to the DM client 300 does not require a response from the DM client, Element in the Package # 4 message or in the Package # 4 message.

An example of the Package # 4 message in this case is shown in Table 2 below.

<SyncML xmlns = 'SYNCML: SYNCML1.2'>
<SyncHdr>
<VerDTD> 1.2 </ VerDTD>
<VerProto> DM / 1.2 </ VerProto>
<SessionID> 1 </ SessionID>
< HoldSession > 1 </ HoldSession >
<MsgID> 3 </ MsgID>
<Target>
<LocURI> IMEI: 493005100592800 </ LocURI>
</ Target>
<Source>
<LocURI> http://www.syncml.org/mgmt-server </ LocURI>
</ Source>
</ SyncHdr>
<SyncBody>
<Status>
<MsgRef> 3 </ MsgRef>
<CmdID> 1 </ CmdID>
<CmdRef> 0 </ CmdRef>
<Cmd> SyncHdr </ Cmd>
<Data> 200 </ Data>
</ Status>
<Final />
</ SyncBody>
</ SyncML>

The session maintenance element is coded and placed in the <HoldSession> 1 <HoldSession> portion of the Package # 4 message.

It will be apparent to those skilled in the art that the present invention is not limited to the embodiments described above, but may also be applied, for example, to software updates.

As described above, according to the present invention, when a session holding element is included in the last package message sent by the DM server 400, a waste of resources required for newly setting a DM session to transmit a result of execution of the management operation .

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

Referring to FIG. 3, the DM server 400 includes a DM package generation and processing unit 410 and a session maintenance element generation unit 720 for generating and processing a DM package message transmitted and received to and from the DM client 300.

When the DM server 400 transmits a DM package message to deliver the management operation to the DM client 300, the DM server 300 maintains the current DM session even if the management operation does not require a response from the DM client 300 Is efficient.

If it is determined that it is necessary to maintain the current DM session, the session maintenance element generation unit 420 generates a session maintenance element as shown in Table 1 and provides the session maintenance element to the DM package creation and processing unit 410, for example. The DM package creation and processing unit 410, when receiving the session maintenance element generated by the session maintenance element generation unit 420, generates a package message including the session maintenance element. The DM session maintenance element may be inserted into the sync header of the package message. The package message including the session maintenance element is transmitted to the DM client 300.

The DM client 300 includes a DM package creation and processing unit 310 and a session maintenance condition determination unit 320 for generating and processing a DM package message transmitted and received to and from the DM server 400.

When the DM client 300 receives the package message including the session maintenance element from the DM server 400, the DM client 300 maintains the current DM session even if the management operation included in the corresponding package message does not require a response from the DM client.

The session maintenance condition determination unit 320 checks whether the condition for maintaining the session is satisfied. If the condition for maintaining the session is satisfied, the session maintenance condition determination unit 320 can terminate the DM session that is being held. For example, if the management operation is a firmware update, the session maintenance condition determination unit 320 determines whether the device status or the result of execution of the firmware update has been transmitted to the DM server 400. If the DM client 300 transmits a status or a result of the management operation to the DM server 400, the DM client 300 can terminate the DM session maintained. Of course, the session maintenance condition does not depend only on the management operation. The DM server 400 may need to maintain a DM session with the DM client 300 regardless of the management operation. Therefore, it is apparent to those skilled in the art that the session maintenance conditions are not limited to the above-described examples and may vary depending on the field to which the present invention is applied.

1 is a diagram illustrating a general DM session setup process.

2 is a diagram illustrating a message flow between a DM server and a DM client according to a preferred embodiment of the present invention.

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

Claims (10)

A method for maintaining a device management (DM) session between a server and a client, The server sending a notification message for forming the DM session to the client to form the DM session between the server and the client; Determining whether the server maintains the DM session with the client when the server transmits the management action message to the client, the response message including no response to the management action message; And transmitting, to the client, an element indicating that the server keeps the DM session in the management operation message if it is determined to hold the DM session, Wherein the DM session is maintained when the client receives the management action message including the element according to transmission of the management action message including the element. 2. The apparatus of claim 1, Wherein the management header is inserted into a sync header of the management operation message. A server for maintaining a Device Management (DM) session, A DM package creation and processing unit for generating a management operation message, And a session maintenance element generation unit for generating an element instructing to maintain the DM session, The server comprises: Wherein the DM session is established with the client by sending a notification message for forming the DM session to the client and when sending the management action message to the client that does not include a response request for the management action message, And generates an element for instructing to maintain the DM session in the session maintenance element generation unit when it is determined that the DM session is to be maintained, And transmitting the management operation message including the element to the client, wherein, in response to the transmission of the management operation message including the element, the client transmits the management operation message including the management Upon receiving the operation message, Wherein the session is maintained. 4. The apparatus of claim 3, Wherein the management header is inserted into a sync header of the management operation message. A method for maintaining a device management (DM) session between a server and a client, Receiving a notification message for forming the DM session from the server, the client transmitting a request message for forming the DM session to the server; Receiving a transmitted request message from the server and receiving a management operation message from the server when the DM session is established; Wherein if the received management action message includes an element for instructing to maintain the DM session without including a response request for the management action message, the formed DM session is maintained. Way. 6. The method of claim 5, Further comprising the step of, when the created DM session is maintained, transmitting status information or result information of performing a management operation according to the received management operation message to the server. 6. The apparatus of claim 5, Wherein the management header is inserted into a sync header of the management operation message. CLAIMS 1. A client for maintaining a device management (DM) session, And a session maintenance condition determination unit for checking whether a condition for maintaining the DM session is satisfied, The client includes: Upon receipt of a notification message for forming the DM session from the server, transmits a request message for forming the DM session to the server, receives the transmitted request message from the server, Receives a management action message from the server, If the received management action message does not include a response request for the management action message and it is determined that the session maintenance condition determination unit includes an element for instructing to maintain the DM session, the formed DM session is maintained A client for maintaining a DM session. 9. The method according to claim 8, Wherein when the DM session is maintained, status information or result information of performing a management operation according to the received management operation message is transmitted to the server. 9. The apparatus of claim 8, Wherein the management header is inserted into a sync header of the management operation message.
KR1020070102119A 2007-10-10 2007-10-10 Method and apparatuses for holding Device Management(DM) session KR101417012B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020070102119A KR101417012B1 (en) 2007-10-10 2007-10-10 Method and apparatuses for holding Device Management(DM) session

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020070102119A KR101417012B1 (en) 2007-10-10 2007-10-10 Method and apparatuses for holding Device Management(DM) session

Publications (2)

Publication Number Publication Date
KR20090036841A KR20090036841A (en) 2009-04-15
KR101417012B1 true KR101417012B1 (en) 2014-07-08

Family

ID=40761697

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020070102119A KR101417012B1 (en) 2007-10-10 2007-10-10 Method and apparatuses for holding Device Management(DM) session

Country Status (1)

Country Link
KR (1) KR101417012B1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101477646B1 (en) * 2013-06-28 2014-12-30 재단법인대구경북과학기술원 Service Oriented Device Management System and Method

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060048616A (en) * 2004-06-30 2006-05-18 마이크로소프트 코포레이션 Sustaining session connections
KR20060049893A (en) * 2004-07-09 2006-05-19 엘지전자 주식회사 Device management system and device management command scheduling method thereof

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060048616A (en) * 2004-06-30 2006-05-18 마이크로소프트 코포레이션 Sustaining session connections
KR20060049893A (en) * 2004-07-09 2006-05-19 엘지전자 주식회사 Device management system and device management command scheduling method thereof

Also Published As

Publication number Publication date
KR20090036841A (en) 2009-04-15

Similar Documents

Publication Publication Date Title
JP4268969B2 (en) Media message upload control method via wireless communication network
CN101523946B (en) Conditional parallel execution of access stratum (AS) and non-access stratum (NAS) signaling
EP2978144B1 (en) Unified device management method and system
CN112449315B (en) Network slice management method and related device
EP3539269B1 (en) Node type based control of assistance for data streaming
KR100989716B1 (en) Method for suspending and resuming delivery of content
CN107835257B (en) Session management method and device
US9417887B2 (en) Method and apparatus for bootstrapping gateway in device management system
WO2011158377A1 (en) Wireless communication method, wireless communication apparatus and wireless communication system
EP2424162B1 (en) Method, apparatus and system for device management
KR101417012B1 (en) Method and apparatuses for holding Device Management(DM) session
CN105791361A (en) Remote assisted setting method, server, terminal and system
KR102362244B1 (en) Method and apparatus for transmitting and receiving data in mission-critical data communication system
KR101177978B1 (en) Providing network connectivity and service state information to application servers
JP4724721B2 (en) A method for ensuring that a service platform obtains user terminal information in a multi-application protocol
KR101377947B1 (en) Method of roaming in broadcast service and system and terminal thereof
JP2005304052A (en) System and method for implementing wireless access protocol push
WO2010124567A1 (en) Method and server for transferring large object
EP3352492A1 (en) Authentication method
JP2004289605A (en) Protocol converter and protocol converting method
KR100513203B1 (en) Method for controlling secondly up-load of media data in a wireless communication network
US10187833B2 (en) Method and apparatus for running network function
KR101390013B1 (en) Method for periodcally managing dm clients and system therefor
KR20090130744A (en) Method and system for remote management in mobile communication terminal
CN105306287A (en) Method and equipment for counting user flow

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E90F Notification of reason for final refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant
FPAY Annual fee payment

Payment date: 20170629

Year of fee payment: 4

FPAY Annual fee payment

Payment date: 20180628

Year of fee payment: 5