KR101417012B1 - Method and apparatuses for holding Device Management(DM) session - Google Patents
Method and apparatuses for holding Device Management(DM) session Download PDFInfo
- 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
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
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
Then, the
However, even if the management operation does not require a response from the
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
Accordingly, if the management operation to be transmitted to the
An element (Sessionhold element) instructing to maintain a DM session can be defined as shown in Table 1 below.
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
Accordingly, the
A description will be given of a case where the
First, the
At this time, the
If the
An example of the Package # 4 message in this case is shown in Table 2 below.
<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
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
When the
If it is determined that it is necessary to maintain the current DM session, the session maintenance
The
When the
The session maintenance
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)
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)
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)
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 |
-
2007
- 2007-10-10 KR KR1020070102119A patent/KR101417012B1/en active IP Right Grant
Patent Citations (2)
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 |