CN103037322A - Method for reducing message transmission between client and server and communication device thereof - Google Patents

Abstract

A method for reducing message transmission between a client and a server and a communication device thereof are provided. The method for reducing message transmission is used in a device management client of a service system and comprises the steps of generating a message containing data and an identification code, wherein the identification code indicates a device management server of the service system not to reply a result obtained by processing the data; and transmitting the message to the device management server to provide the device management server with the data to process.

Description

Method and communication device for reducing message transmission between client and server

technical field

The present invention relates to a method for a service system and its communication device, in particular to a method for reducing message transmission between a device management client and a device management server and its communication device.

Background technique

The Open Mobile Alliance (OMA) was established to develop OMA Specifications that meet user needs. Specifically, the Open Mobile Alliance specification is dedicated to providing mobile services that are interoperable across different geographic regions (such as countries), operators, service providers, networks, operating systems, and mobile devices. When users use mobile services that comply with the Open Mobile Alliance specifications, they are not limited to specific operators and service providers. OMA-compliant mobile services are also independent of the bearer used, for example, the bearer used by OMA-compliant mobile services can be Global System for Mobile Communications (GSM), Data Rate Enhanced GSM evolution technology (Enhanced Data rates for GSM Evolution, EDGE) or general packet radio service (General Packet Radio Service, GPRS) and other second-generation mobile communication systems can also be Universal Mobile Telecommunications System (Universal Mobile Telecommunications System, UMTS), Long Term Evolution (LTE) or Advanced Long Term Evolution (LTE-Advanced, LTE-A) and other third-generation and their evolution mobile communication systems. In addition, the mobile service is not limited to the operating system used by the mobile device, and can run on the mobile device running the operating system such as Windows, Android or Linux. Therefore, the industry can benefit from the substantial growth market brought about by the interoperability of mobile services while providing mobile devices and mobile services that comply with the OMA specifications. In addition, when users use mobile devices and mobile services that comply with the Open Mobile Alliance specifications, they can also enjoy a better experience brought about by the interoperability of mobile services.

In the Open Mobile Alliance Device Management (DM) requirements, a device management server (DM server) is defined as one or more device management clients (DM clients) (such as mobile device) a legally authorized unit. Specifically, the Open Mobile Alliance Device Management Specification is used to define the way to exchange packets, messages and/or packages (ie, several messages sent in the same direction) between the Device Management Server and the Device Management Client, and also Used to define how the device management client reports commands, status or reports. Further, when using the Open Mobile Alliance device management specification, the device management server manages the device management client through multiple management objects (Management Objects) in the device management client, where a management object can be as small as an integer or as large as a picture. For example, a management object can be a software component management object (Software Component Management Object, SCOMO), a software and application control management object (Software and Application Control Management Object, SACMO) or a firmware update management object (Firmware Update Management Object, FUMO ) and other objects.

According to the device management protocol version 1.x (DM 1.x protocol), the device management server and the device management client need to exchange two or more messages to complete a complete communication. Specifically, at least two messages are required to complete a task, such as reporting the value of a node in the device management client to the device management server, and the two messages are used in package 1 and package 2 respectively. However, in some cases, the device management client only wants to perform a simple task, such as reporting a value to the device management server, but still needs to exchange two or more messages between the device management server and the device management client , resulting in a waste of communication resources. Therefore, how to reduce the message transmission required to perform simple tasks is an issue to be discussed and resolved.

Contents of the invention

Therefore, the main purpose of the present invention is to provide a method and its communication device for reducing the message transmission between the device management client and the device management server, so as to solve the above problems.

The invention discloses a method for reducing message transmission, which is used in a device management client of a service system. The method includes generating a message including a data and an identification code, and the identification code indicates a service system. The device management server does not reply with a result of processing the data; and sending the message to the device management server for the device management server to process the data.

Description of drawings

FIG. 1 is a schematic diagram of a service system according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a communication device according to Embodiment 1 of the present invention.

FIG. 3 is a schematic diagram of a process in Embodiment 1 of the present invention.

[Description of main component symbols]

10 Service System

20 Communication device

200 processing device

210 storage units

214 Program code

220 Communication interface unit

30 Process

300, 302, 304, 306 steps

Detailed ways

Please refer to FIG. 1 , which is a schematic diagram of a service system 10 according to an embodiment of the present invention. The service system 10 supports the Device Management (DM) protocol version 1.x (DM 1.x protocol) and its subsequent versions developed by the Open Mobile Alliance (Open Mobile Alliance, OMA). (DM server) and multiple device management clients (DM client).

In FIG. 1 , the device management client and the device management server are used to illustrate the architecture of the service system 10 . In fact, the device management client can be built into a desktop computer or a home appliance that is fixed in one place. Alternatively, the device management client can be built into mobile devices such as mobile phones, notebook computers, tablet computers, and e-books. In addition, the service system 10 is independent of the bearer used by it. For example, the bearer for transmitting information (such as message) can be Global System for Mobile Communications (GSM), Enhanced Datarates for GSM (Enhanced Datarates for GSM Evolution, EDGE) or general packet radio service (General Packet Radio Service, GPRS) second-generation mobile communication system, can also be universal mobile communication system (Universal Mobile Telecommunications System, UMTS), long-term evolution system (Long TermEvolution, LTE) or Third-generation mobile communications such as LTE-Advanced (LTE-A) and their evolution systems can even be wired communications systems such as Asymmetric Digital Subscriber Line (ADSL).

Please refer to FIG. 2 , which is a schematic diagram of a communication device 20 according to an embodiment of the present invention. The communication device 20 can be used to install or store the device management client or the device management server shown in FIG. 1 , and includes a processing device 200 , a storage unit 210 and a communication interface unit 220 . The processing device 200 can be a microprocessor or an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC). The storage unit 210 can be any data storage device for storing a program code 214 , and the processing device 200 can read and execute the program code 214 through the storage unit 210 . For example, the storage unit 210 may be a Subscriber Identity Module (Subscriber Identity Module, SIM), a Read-Only Memory (Read-Only Memory, ROM), a Random-Access Memory (Random-Access Memory, RAM), an optical disc read-only memory (CD-ROM/DVD-ROM), magnetic tape (magnetic tape), hard disk (hard disk) and optical data storage device (optical data storage device), etc., but not limited thereto. The communication interface unit 220 can be a transceiver, which is used to transmit and receive information (such as messages, requests, responses, packages (also referred to as “packages”), etc.) according to the processing results of the processing device 200 .

Please refer to FIG. 3 , which is a flowchart of a process 30 according to Embodiment 1 of the present invention. The process 30 is used in the device management client in FIG. 1 to reduce the message transmission between the device management client and the device management server. Process 30 can be compiled into program code 214, which includes the following steps:

Step 300: start.

Step 302: Generate a message including a data and an identifier, and the identifier instructs the device management server not to reply a result obtained by processing the data.

Step 304: Send the message to the device management server for the device management server to process the data.

Step 306: end.

According to the process 30, the device management client first generates a message including data and an identification code (such as a tag or an indication), wherein the identification code instructs the device management server not to reply a result obtained by processing the data. Then, the device management client sends a message to the device management server to provide the device management server with processing data. Therefore, the process 30 only needs one message to complete the communication (eg work) between the device management client and the device management server, avoiding sending unnecessary messages.

It should be noted that the spirit of the process 30 is that only one message is needed to complete a task, so as to reduce the message transmission between the device management client and the device management server, thereby saving the transmission resources needed to complete the task. The implementation of the process 30 is not limited.

For example, the identification code can be a command and/or a value. In detail, the device management client can use both the command and the value to instruct the device management server not to reply the result obtained by processing the data. Therefore, after receiving the message, according to the instruction and the value, the device management server will only process the data, and will not reply (ie send) the processing result to the device management client. Or, the device management client only uses the value to instruct the device management server not to reply the result of processing the data. Therefore, after receiving the message, the device management server will only process the data according to the value, and will not reply (that is, send) the processing result to the device management client. In this case, since the command is not a part of the identification code, the command can be regarded as a general command (such as updating, replacing, obtaining, etc.), so that the device management server can process data according to the command. For example, the data is a value, and the device management server uses the value to update the value of a node. In another embodiment, the identification code is defined in a tag <Final> in the device management protocol (DM protocol). Therefore, after receiving the message, according to the tag <Final>, the device management server will only process the data, but will not reply (that is, send) the processing result to the device management client.

The following examples illustrate each of the above messages:

According to the above message embodiment, the device management client can use the command "<Alter>" and the value "1230" as the identification code at the same time. After detecting the command "<Alter>" and the value "1230", the device management server will only process the data without replying (i.e. sending) the processing result to the device management client. Alternatively, the device management client only uses the value "1230" as the identification code, and after detecting the value "1230", the device management server only processes the data without replying (that is, sending) the processing result to the device management client. In this case, the device management server can process the data according to the instruction "<Replace>". In another embodiment, the device management client only uses the tag "<Final>" as the identification code, and after detecting the tag "<Final>", the device management server will only process the data and will not reply (i.e. transmit) The processing result is sent to the device management client.

It should be noted that the transmission method of the above information is not limited. For example, the device management client can use a transmission control protocol (transmission control protocol, TCP), a user data protocol (user datagram protocol, UDP), a short message service (short message service, SMS) protocol or a wireless application Protocol (wireless application protocol, WAP) push, send messages to the device management server. In addition, the message may further include authentication data for identifying the device management client, such as to let the device management server know who sent the message. Since the device management client may not be allowed to request the device management server to process the data (eg, according to an instruction), preferably, before processing the data, the device management server can determine whether to process the data according to the authorization of the device management client. On the other hand, the device management client can be generated according to an extensible markup language (eXtensible Markup Language, XML) format, a type-length-value (type-length-value, TLV) format or a plain text (plain text) format. the message. That is, the device management client can use XML format, type length value format or plain text format to encode the message.

Those skilled in the art may combine, modify or change the above-described embodiments according to the spirit of the present invention, but are not limited thereto. The steps of all the aforementioned processes (including the suggested steps) can be realized by devices, which can be hardware, firmware (a combination of hardware devices and computer instructions and data, and computer instructions and data belong to read-only software on hardware devices) or electronic system. The hardware can be an analog microcomputer circuit, a digital microcomputer circuit, a hybrid microcomputer circuit, a microcomputer chip, or a silicon chip. The electronic system can be a system on chip (SOC), a system in package (SiP), an embedded computer (computer on module, COM) and a communication device 20 .

To sum up, the present invention provides a method for reducing message transmission between a device management client and a device management server, and the message transmission is used to complete a job. Therefore, the transmission resources required to do the job can be saved.

The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the claims of the present invention shall fall within the scope of the present invention.

Claims (10)

1. A method for reducing message transmission, used in a device management client (Device Management client, DM client) of a service system, the method includes: generating a message including a data and an identifier, and the identifier instructs a device management server of the service system not to reply a result obtained by processing the data; and sending the message to the device management server to provide the device management server to process the data. 2. The method of claim 1, wherein the identification code includes an instruction. 3. The method of claim 2, wherein the identification code further comprises a value. 4. The method of claim 1, wherein the identification code includes a value. 5. The method of claim 4, wherein the message further includes an instruction, and according to the instruction, the device management server processes the data. 6. The method of claim 1, wherein the identification code is defined in a <Final> tag in a device management protocol (DM protocol). 7. The method according to claim 1, wherein a transmission control protocol (transmissioncontrol protocol, TCP), a user data protocol (user datagram protocol, UDP), a short message service (short message service, SMS) protocol or a The wireless application protocol (wireless application protocol, WAP) broadcast, the device management client sends the message to the device management server. 8. The method of claim 1, wherein the message further includes authentication data for identifying the device management client. 9. The method of claim 1, wherein before processing the data, according to the authorization of the device management client, the device management server determines whether to process the data. 10. The method of claim 1, wherein according to an extensible markup language (eXtensibleMarkup Language, XML) format, a type length value (type-length-value, TLV) format or a plain text (plain text) format, The device management client generates the message.

Images