CN103873538A - DM (device management)-protocol-based sever and terminal communication method and system - Google Patents
DM (device management)-protocol-based sever and terminal communication method and system Download PDFInfo
- Publication number
- CN103873538A CN103873538A CN201210552422.0A CN201210552422A CN103873538A CN 103873538 A CN103873538 A CN 103873538A CN 201210552422 A CN201210552422 A CN 201210552422A CN 103873538 A CN103873538 A CN 103873538A
- Authority
- CN
- China
- Prior art keywords
- notification message
- terminal
- service end
- task type
- configuration
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a DM (device management)-protocol-based server and terminal communication method and a DM-protocol-based server and terminal communication system. The method comprises the following steps that a server configures a reserved field in a notification message, and transmits the configured extended notification message to a terminal; the terminal receives and resolves the extended notification message to acquire a task type in the extended notification message; the terminal creates a DM session according to the task type, and transmits the DM session back to the server. According to the method and the system, the server configures the preserved field in the notification message, and transmits the configured extended notification message to the terminal, and the terminal receives and resolves the extended notification message to acquire the task type in the extended notification message, creates the DM session according to the task type, and transmits the DM session back to the server, so that the beneficial effect that the terminal can learn about the specific task type when receiving the notification message from the server is achieved, the system performance is improved, and the data process of the terminal is optimized.
Description
Technical field
The present invention relates to communication technical field, relate in particular to a kind of service end based on DM agreement and communication means and the system of terminal.
Background technology
DM(Device Manager, equipment control) agreement is SyncML(Synchronization Markup Language, the information synchronous standard protocol collection of a platform independence) device management protocol SyncML-DM.At present, what a lot of terminal equipments based on DM agreement can not continue intercepts the connection from server, and based on security consideration, and a lot of terminal equipments do not have open port to receive and being connected of service end.But most of equipment can receive unsolicited type message, such as notice (Notification), server can notify client to initiate a session or connection by Notification, and management server is linked back.Notification message is just wrapped as the 0th of SyncML DM protocol conversation, be usually said Package#0, it is used as the triggering message that initial session is notified, but Notification message is all to use default format, the task type that terminal can not issue according to this Notification message identification service end, can only continue other command messagess of waiting for that terminal issues.
Summary of the invention
Main purpose of the present invention is to provide a kind of service end based on DM agreement and communication means and the system of terminal, when being intended to solve service end and being handed down to terminal notification message, and the problem of the task type that terminal can not issue by notification message identification terminal.
The embodiment of the invention discloses a kind of service end based on management object DM agreement and the communication means of terminal, comprise the following steps:
Reserved field in service end configuration notification message, and the expansion notification message after configuration is handed down to terminal;
Terminal receives and resolves described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to service end.
Preferably, the reserved field in described service end configuration notification message comprises:
Service end is carried out task type description to the reserved field in described notification message trigger-header, and described task type and described reserved field are indicated one by one.
Preferably, described service end is handed down to the expansion notification message after configuration terminal and comprises:
The expansion notification message after configuration is handed down to the transmission proxy gateway of service end by service end, then by described transmission proxy gateway, described expansion notification message is sent to terminal.
Preferably, described terminal receives and resolves described expansion notification message, and the task type obtaining in described expansion notification message comprises:
Terminal receives described expansion notification message, triggers resolve command;
According to described resolve command, DM protocol stack is resolved described expansion notification message, obtains described task type.
The embodiment of the present invention also discloses a kind of service end based on DM agreement and the communication system of terminal, comprising:
Service end, for the reserved field of configuration notification message, and is handed down to terminal by the expansion notification message after configuration;
Terminal, for receiving and resolve described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to service end.
Preferably, described service end also for:
Reserved field in described notification message trigger-header is carried out to task type description, and described task type and described reserved field are indicated one by one.
Preferably, described service end also for:
Expansion notification message after configuration is handed down to the transmission proxy gateway of service end, then by described transmission proxy gateway, described expansion notification message is sent to terminal.
Preferably, described terminal also for:
Receive described expansion notification message, trigger DM protocol stack and resolve described expansion notification message, obtain described task type.
The present invention passes through the reserved field in service end configuration notification message, and the expansion notification message after configuration is handed down to terminal; Terminal receives and resolves described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to the method for service end, has terminal in the time receiving the notification message that service end sends, and just can learn the beneficial effect of specific tasks type, has improved systematic function, has optimized the data processing of terminal.
Accompanying drawing explanation
Fig. 1 the present invention is based on the service end of DM agreement and the communication means of terminal one embodiment schematic flow sheet;
Fig. 2 the present invention is based in the service end of DM agreement and the communication means of terminal, the notification message one example structure schematic diagram after service end configuration;
Fig. 3 the present invention is based on the service end of DM agreement and the communication system of terminal is unified example structure schematic diagram.
Realization, functional characteristics and the advantage of the object of the invention, in connection with embodiment, are described further with reference to accompanying drawing.
Embodiment
Further illustrate technical scheme of the present invention below in conjunction with Figure of description and specific embodiment.Should be appreciated that specific embodiment described herein, only in order to explain the present invention, is not intended to limit the present invention.The present invention is based in the service end of DM agreement and the communication means of terminal and system, described notification message is Notification message.
With reference to Fig. 1, Fig. 1 the present invention is based on the service end of DM agreement and the communication means of terminal one embodiment schematic flow sheet; As shown in Figure 1, the present invention is based on the service end of DM agreement and the communication means of terminal comprises the following steps:
Reserved field in step S01, service end configuration notification message, and the expansion notification message after configuration is handed down to terminal;
The notification message that is sent to terminal due to service end is that Notification message comprises trigger-header and trigger-body, and in DM agreement, in <future-use> field in notification message trigger-header, there are 27 idle reserved fields, therefore can carry out task type while describing to make terminal to receive this notification message by the reserved field in notification message trigger-header, just can learn the type of service that service end is about to issue.Service end indicates this type of service and reserved field one by one, and the notification message after expansion is sent to terminal after completing the type of service of the reserved field in notification message trigger-header being described.
For conventional management object and parameter acquisition configuration task, terminal please refer to Fig. 2 to the configuration of notification message, and Fig. 2 the present invention is based in the service end of DM agreement and the communication means of terminal, the notification message one example structure schematic diagram after service end configuration, as shown in Figure 2, service end indicates respectively task type with 7 of 27 reserved fields of the trigger-header that is arranged in notification message altogether, General Parameters is as shown in Figure 2 adopted and is joined task type, LAWMO(wipes management object) task type, FUMO(Firmware Update Management Object, firmware upgrades management object) task type, Conn MO(Connection Management Object, connection manager object) task type, Diag MO(Diagram Management Object, graphics management object) task type, DCMO(data collection Management Object, Data acquisition, management object) task type and SCO MO (Software Component Management Object, software component management object) task type.
It will be appreciated by those skilled in the art that, it shown in Fig. 2, is only a kind of specific embodiment mode that service end is expanded the reserved field in notification message, expansion and the configuration of service end to the reserved field in notification message is not limited only to the configuration mode shown in Fig. 2, and the concrete mode of the reserved field of the embodiment of the present invention to the trigger-header in service end configuration notification message is not done exhaustive one by one.
In a preferred embodiment, service end sends to the general process of terminal to be the notification message after expansion: service end first sends to the notification message after expansion the transmission proxy gateway of service end, then under asynchronous mode, the notification message after described expansion is sent to terminal by sending proxy gateway.
Step S02, terminal receive and resolve described expansion notification message, obtain the task type in described expansion notification message; According to described task type, structure DM session packet is also back to service end.
Terminal receives the expansion notification message that service end sends, and by resolving this expansion notification message, obtains the corresponding description of reserved field in this expansion notification message, obtains further the task type that service end issues; The task type that terminal issues according to service end, based on DM agreement, structure DM session packet, and this DM session packet is sent to service end, with service end Hui Lian.Like this, notification message is at the very start can the concrete task type of notification terminal, and the specific tasks type that terminal also can issue according to service end is carried out corresponding preparation; Such as, learn that when terminal the task type that service end issues is FUMO task type, terminal can be carried out the preparation of carrying out firmware renewal in advance; If terminal does not expect to carry out firmware renewal this moment, can, by the DM session packet of structure, send to service end the session that refusal firmware upgrades.
In a preferred embodiment, terminal receives and resolves described expansion notification message and can realize by following manner: terminal receives described expansion notification message, triggers resolve command; DM protocol stack, according to this resolve command, is resolved described expansion notification message, obtains the corresponding description of reserved field in this expansion notification message, obtains further the task type that service end issues.
The present embodiment passes through the reserved field in service end configuration notification message, and the expansion notification message after configuration is handed down to terminal; Terminal receives and resolves described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to the method for service end, has terminal in the time receiving the notification message that service end sends, and just can learn the beneficial effect of specific tasks type, has improved systematic function, has optimized the data processing of terminal.
With reference to Fig. 3, Fig. 3 the present invention is based on the service end of DM agreement and the communication system of terminal is unified example structure schematic diagram.As shown in Figure 3, the present invention is based on the service end of DM agreement and the communication system of terminal and comprise service end 01 and terminal 02.
The notification message that is sent to terminal 02 due to service end 01 is that Notification message comprises trigger-header and trigger-body, and in DM agreement, in <future-use> field in notification message trigger-header, there are 27 idle reserved fields, therefore service end 01 can be carried out task type while describing to make terminal 02 to receive this notification message by the reserved field in notification message trigger-header, just can learn the type of service that service end 01 is about to issue.Service end 01 indicates this type of service and reserved field one by one, and the notification message after expansion is sent to terminal 02 after completing the type of service of the reserved field in notification message trigger-header being described.
For conventional management object and parameter acquisition configuration task, terminal 02 please refer to Fig. 2 to the configuration of notification message, and Fig. 2 the present invention is based in the service end of DM agreement and the communication means of terminal, the notification message one example structure schematic diagram after service end configuration; As shown in Figure 2,7 of service end 01 common 27 reserved fields using the trigger-header that is arranged in notification message indicate respectively task type, and General Parameters is as shown in Figure 2 adopted and joined task type, LAWMO task type, FUMO task type, Conn MO task type, Diag MO task type, DCMO task type and SCO MO task type.
It will be appreciated by those skilled in the art that, it shown in Fig. 2, is only a kind of specific embodiment mode that service end 01 is expanded the reserved field in notification message, expansion and the configuration of service end 01 to the reserved field in notification message is not limited only to the configuration mode shown in Fig. 2, and the concrete mode of the reserved field of the embodiment of the present invention to the trigger-header in service end 01 configuration notification message is not done exhaustive one by one.
In a preferred embodiment, service end 01 sends to the general process of terminal 02 to be the notification message after expansion: service end 01 first sends to the notification message after expansion the transmission proxy gateway of service end 01, then under asynchronous mode, the notification message after described expansion is sent to terminal 02 by sending proxy gateway.
In a preferred embodiment, terminal 02 receives and resolves described expansion notification message and can realize by following manner: terminal 02 receives described expansion notification message, triggers resolve command; DM protocol stack, according to this resolve command, is resolved described expansion notification message, obtains the corresponding description of reserved field in this expansion notification message, obtains further the task type that service end 01 issues.
The present embodiment passes through the reserved field in service end configuration notification message, and the expansion notification message after configuration is handed down to terminal; Terminal receives and resolves described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to service end, has terminal in the time receiving the notification message of service end transmission, just can learn the beneficial effect of specific tasks type, has improved systematic function, has optimized the data processing of terminal.
The foregoing is only the preferred embodiments of the present invention; not thereby limit its scope of the claims; every equivalent structure or conversion of equivalent flow process that utilizes specification of the present invention and accompanying drawing content to do; directly or indirectly be used in other relevant technical fields, be all in like manner included in scope of patent protection of the present invention.
Claims (8)
1. the service end based on management object DM agreement and a communication means for terminal, is characterized in that, comprises the following steps:
Reserved field in service end configuration notification message, and the expansion notification message after configuration is handed down to terminal;
Terminal receives and resolves described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to service end.
2. the method for claim 1, is characterized in that, the reserved field in described service end configuration notification message comprises:
Service end is carried out task type description to the reserved field in described notification message trigger-header, and described task type and described reserved field are indicated one by one.
3. method as claimed in claim 1 or 2, is characterized in that, described service end is handed down to terminal by the expansion notification message after configuration and comprises:
The expansion notification message after configuration is handed down to the transmission proxy gateway of service end by service end, then by described transmission proxy gateway, described expansion notification message is sent to terminal.
4. the method for claim 1, is characterized in that, described terminal receives and resolve described expansion notification message, and the task type obtaining in described expansion notification message comprises:
Terminal receives described expansion notification message, triggers resolve command;
According to described resolve command, DM protocol stack is resolved described expansion notification message, obtains described task type.
5. a communication system for the service end based on DM agreement and terminal, is characterized in that, comprising:
Service end, for the reserved field of configuration notification message, and is handed down to terminal by the expansion notification message after configuration;
Terminal, for receiving and resolve described expansion notification message, obtains the task type in described expansion notification message; According to described task type, structure DM session packet is also back to service end.
6. system as claimed in claim 5, is characterized in that, described service end also for:
Reserved field in described notification message trigger-header is carried out to task type description, and described task type and described reserved field are indicated one by one.
7. the system as described in claim 5 or 6, is characterized in that, described service end also for:
Expansion notification message after configuration is handed down to the transmission proxy gateway of service end, then by described transmission proxy gateway, described expansion notification message is sent to terminal.
8. system as claimed in claim 5, is characterized in that, described terminal also for:
Receive described expansion notification message, trigger DM protocol stack and resolve described expansion notification message, obtain described task type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210552422.0A CN103873538A (en) | 2012-12-18 | 2012-12-18 | DM (device management)-protocol-based sever and terminal communication method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210552422.0A CN103873538A (en) | 2012-12-18 | 2012-12-18 | DM (device management)-protocol-based sever and terminal communication method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103873538A true CN103873538A (en) | 2014-06-18 |
Family
ID=50911659
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210552422.0A Pending CN103873538A (en) | 2012-12-18 | 2012-12-18 | DM (device management)-protocol-based sever and terminal communication method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103873538A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101355524A (en) * | 2007-07-24 | 2009-01-28 | 华为技术有限公司 | Method, system, server and terminal for processing information |
| CN101909282A (en) * | 2010-08-20 | 2010-12-08 | 中兴通讯股份有限公司 | Triggering method, device and system of terminal operation |
| CN102571704A (en) * | 2010-12-24 | 2012-07-11 | 华为终端有限公司 | Management conversation initiating and notifying method, managed terminal and management server |
-
2012
- 2012-12-18 CN CN201210552422.0A patent/CN103873538A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101355524A (en) * | 2007-07-24 | 2009-01-28 | 华为技术有限公司 | Method, system, server and terminal for processing information |
| EP2091210A1 (en) * | 2007-07-24 | 2009-08-19 | Huawei Technologies Co., Ltd. | Message processing method, system, server and terminal |
| CN101909282A (en) * | 2010-08-20 | 2010-12-08 | 中兴通讯股份有限公司 | Triggering method, device and system of terminal operation |
| CN102571704A (en) * | 2010-12-24 | 2012-07-11 | 华为终端有限公司 | Management conversation initiating and notifying method, managed terminal and management server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9712632B2 (en) | Method for receiving data, method for sending data, mobile terminal, and server | |
| EP3300311A1 (en) | Interaction method and apparatus for smart watch and wechat platform, and smart watch | |
| EP2860945A3 (en) | Network appliance architecture for unified communication services | |
| CN103179027A (en) | Method and system for realizing compatibility of electrical appliance, and universal peripheral access gateway | |
| WO2014082577A1 (en) | Remote debugging method and system | |
| WO2011116718A3 (en) | Method for controlling internet services, and relevant device and system | |
| CN104463670A (en) | Websocket-based bank preposition transaction system construction method | |
| CN103491512A (en) | Implementation method and device for information pushing | |
| CN101223737A (en) | Method and system for pushing asynchronous notifications to networked devices | |
| CN103699450A (en) | Linux adaptive component communication method | |
| EP2645623B1 (en) | Method, device and system for managing wireless terminal by remote server | |
| WO2010148723A1 (en) | Telnet method for external terminal and master device, slave device thereof | |
| CN104811342A (en) | Method of managing EOC terminals with WIFI (Wireless Fidelity) in batches by EOC local side | |
| CN102694675A (en) | Asynchronous communication method and device based on SNMP (Simple Network Management Protocol) | |
| CN103533001A (en) | Communication method and communication system based on HTTP multi-proxy, and intermediate proxy server | |
| US10454715B1 (en) | Virtual private wire service interworking | |
| CN101237663B (en) | Operation and maintenance management method and system for base station device in wireless communication system | |
| CN103873538A (en) | DM (device management)-protocol-based sever and terminal communication method and system | |
| CA2647019A1 (en) | Electronic mail communications system with client email internet service provider (isp) polling application and related methods | |
| CN107277107B (en) | Application debugging method, device and system | |
| CN102594611B (en) | Trap session chain table updating method for webmaster agent | |
| CN101662391B (en) | SNMPv3-based cluster management method of Ethernet switches | |
| CN108989467B (en) | Centralized addressing method | |
| CN101631303A (en) | Method for processing interception, apparatus and system thereof | |
| CN102262533B (en) | Terminal, triggering method and communication method of application programs between terminals |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140618 |