WO2015042979A1 - Message processing method, and related apparatus and system - Google Patents

Abstract

Disclosed are a message processing method, and a related apparatus and system. The message processing method comprises: a multicast initiation apparatus sending a multicast message to an observer server; the multicast initiation apparatus receiving a response message sent by an observer client; and the multicast initiation apparatus obtaining an identification of the observer server from the response message to determine that the observer server obtains the multicast message. By means of the disclosed convent, the present invention reduces the signaling overhead, and decreases the load of an observer server.

Description

 Message processing method and related device and system

[Technical Field]

The present invention relates to the field of network technologies, and in particular, to a message processing method and related apparatus and system.

【Background technique】

The Internet of Things (IoT) is a network that extends and expands on the basis of the Internet. Its client extends and extends to any item, and exchanges and communicates with each other. The purpose is to realize the connection between all items and the network, so as to facilitate identification and management. And control.

In the Internet of Things, the status of various resources is recorded on the observer server (implemented by content in the application layer), and the client needs to send a message including the status of the specific resource to the server to know the current status of the specific resource. The devices that are the observer servers are all wireless low-power devices. These devices are in a dormant state most of the time, so they cannot respond to polling requests in time. Therefore, in the prior art, the control of the Internet of Things items is realized by the observer mode.

Specifically, the observer service mode specifically includes an observer client and an observer server. In the observer mode, the push model requires a subscription interface for requesting a response to a change in a specific resource in the observer server. The push model is derived from the observer pattern in the design pattern (observer Pattern), for example, assuming that the specific resource in the observer server is the current temperature value, the subscription mechanism is as follows: Observer client (observer Client) to the observer server (observer The server sends a subscription request for the temperature (the temperature of the specific resource is the temperature obtained by the sensor), and the observer server registers the subscription after receiving the subscription request. After the subscription is successfully registered, the observer server immediately sends the current status. To the observer client, once the content (ie, temperature) to which the observer server is subscribed changes, the currently changed state is immediately sent to the observer client. The observer mode is very widely used, and the observer server device is mostly a wireless sensor device.

In the prior art, when the observer server device deploying the observer mode receives the multicast message, the observer server not only needs to send a status change message to the observer client, but also needs to send a multicast message to the multicast message. The sender sends a multicast confirmation message. In this way, the observer server needs to send at least two reply messages, one of which is sent to the observer client, and the other is sent to the multicast sender, which increases the load on the observer server.

 [Summary of the Invention]

In view of this, the embodiments of the present invention provide a message processing method and related apparatus and system thereof, so as to reduce signaling overhead and reduce the load of the observer server.

A first aspect provides a message processing method, comprising: a multicast initiating device transmitting a multicast message to a viewer server, wherein the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server, such that The observer server updates the current state of the resource according to the operation instruction, and sends a state change message to the observer client, the state change message includes the network address of the multicast originating device and the current state after the resource update; the multicast originating device receives the observer client a response message sent by the terminal, the response message including an identifier of the observer server, wherein the response message is sent by the observer client after receiving the state change message sent by the observer server; the multicast initiating device acquires the observer server from the response message Identifies to confirm that the Observer server has obtained the multicast message.

In a first possible implementation of the first aspect, the network address of the multicast originating device in the multicast message is set in an option field in a standard COAP message.

In a second possible implementation of the first aspect, the identifier of the observer server is the network address of the observer server.

In a third possible implementation manner of the first aspect, the multicast message and the state change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message. The latest time that can be accepted.

In conjunction with the third possible implementation of the first aspect, in a fourth possible implementation, the latest acknowledgement time in the multicast message is set in an option field in the standard COAP message.

A second aspect provides a message processing method, including: an observer server receiving a multicast message sent by a multicast originating device, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server; The server updates the current state of the resource according to the operation instruction; the observer server sends a status change message to the observer client, and the status change message includes the network address of the multicast originating device and the current status after the resource is updated.

In a first possible implementation of the second aspect, the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message.

In a second possible implementation manner of the second aspect, the multicast message and the state change message further include a latest acknowledgement time, where the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message The latest time that can be accepted.

In conjunction with the second possible implementation of the second aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message.

A third aspect provides a message processing method, comprising: an observer client acquiring an identifier of an observer server; and an observer client receiving a state change message sent by the observer server, wherein the state change message includes a network address of the multicast initiator and The current state of the resource of the observer server after updating; the observer client sends a response message to the multicast originating device according to the network address of the multicast originating device, wherein the response message includes an identifier of the observer server such that the multicast originating device receives the response message Obtain the identity of the observer server to confirm that the observer server has obtained the multicast message.

In a first possible implementation of the third aspect, the identifier of the observer server is the network address of the observer server.

In a second possible implementation of the third aspect, the multicast message and the state change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message. The latest time that can be accepted.

In conjunction with the second possible implementation of the third aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message.

In conjunction with the second possible implementation of the third aspect, in a fourth possible implementation, the observer client sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

In a fifth possible implementation of the third aspect, the identifier of the observer server in the response message is set in an option field in the standard COAP message.

In a sixth possible implementation manner of the third aspect, before the observer client receives the state change message sent by the observer server, the method further includes: the observer client establishes an observer mode relationship with the observer server, where the observation Establishing an observer mode relationship between the client and the observer server includes: the observer client sends a standard COAP query message to the observer server, and the standard COAP query message includes the resource identifier corresponding to the resource to be queried, so that the observer server identifies the resource according to the resource. Subscribe to the resource for registration, query the current state of the resource, and send a standard COAP response message to the observer client, where the standard COAP response message includes the current state of the resource.

A fourth aspect provides a multicast originating apparatus, including: a first sending module, configured to send a multicast message to a viewer server, where the multicast message includes a network address of the multicast originating device and an operation of a resource for the observer server An instruction to cause the observer server to update the current state of the resource according to the operation instruction, and send a state change message to the observer client, the state change message including a network address of the multicast originating device and a current state after the resource update; the first receiving module And a response message sent by the observer client, where the response message includes an identifier of the observer server, where the response message is sent by the observer client after receiving the state change message sent by the observer server; the confirmation module is configured to: The identity of the observer server is obtained from the response message to confirm that the observer server obtained the multicast message.

In a first possible implementation of the fourth aspect, the network address of the multicast originating device in the multicast message is set in an option field in the standard COAP message.

In a second possible implementation of the fourth aspect, the identifier of the observer server is the network address of the observer server.

In a third possible implementation manner of the fourth aspect, the multicast message and the state change message include a latest acknowledgement time, and the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message. The latest time that can be accepted.

In conjunction with the third possible implementation of the fourth aspect, in a fourth possible implementation, the latest acknowledgement time in the multicast message is set in an option field in the standard COAP message.

A fifth aspect provides an observer server, comprising: a second receiving module, configured to receive a multicast message sent by a multicast initiating device, where the multicast message includes a network address of the multicast initiating device and a resource for the observer server. An operation instruction; a resource processing module, configured to update a current state of the resource according to the operation instruction; and a second sending module, configured to send a state change message to the observer client, where the state change message includes a network address of the multicast initiator and a resource update The current state.

In a first possible implementation of the fifth aspect, the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message.

In a second possible implementation manner of the fifth aspect, the multicast message and the state change message further include a latest acknowledgement time, where the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message The latest time that can be accepted.

In conjunction with the second possible implementation of the fifth aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message.

The sixth aspect provides an observer client, including: an identifier obtaining module, configured to acquire an identifier of the observer server; and a third receiving module, configured to receive a state change message sent by the observer server, where the state change message includes multicasting a network address of the initiating device and a current state after the resource is updated; the third sending module is configured to send a response message to the multicast initiating device according to the network address of the multicast initiating device, where the response message includes an identifier of the observer server, so that the multicasting The initiating device obtains the identity of the observer server from the response message to confirm that the observer server obtained the multicast message.

In a first possible implementation of the sixth aspect, the identifier of the observer server is a network address of the observer server.

In a second possible implementation manner of the sixth aspect, the multicast message and the state change message further include a latest acknowledgement time, where the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message The latest time that can be accepted.

In conjunction with the second possible implementation of the sixth aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message.

In conjunction with the second possible implementation of the sixth aspect, in a fourth possible implementation, the third sending module sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

In a fifth possible implementation of the sixth aspect, the identifier of the observer server in the response message is set in an option field in the standard COAP message.

In a sixth possible implementation manner of the sixth aspect, the third sending module is further configured to send a standard COAP query message to the observer server before the third receiving module receives the state change message sent by the observer server, the standard COAP query The message includes a resource identifier corresponding to the resource to be queried, so that the observer server subscribes the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client, where the standard COAP response message includes the resource. The current state; the third receiving module is further configured to receive a standard COAP response message.

A seventh aspect provides a message processing system, including: a multicast initiating device, comprising: a first sending module, configured to send a multicast message to a viewer server, where the multicast message includes a network address of the multicast initiating device and is directed to an observer An operation instruction of the resource of the server; the observer server, comprising: a second receiving module, configured to receive a multicast message sent by the multicast initiating device; a resource processing module, configured to update a current state of the resource according to the operation instruction; and a second sending module For transmitting a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated; the observer client includes: an identifier obtaining module, configured to acquire the observer server The third receiving module is configured to receive a status change message sent by the observer server, and the third sending module is configured to send a response message to the multicast originating device according to the network address of the multicast originating device, where the response message includes the observer server Identification; the multicast transmitting device further includes a first receiving module And confirmation module, receiving means for receiving a first response message, the response message confirmation means for acquiring from a server to confirm that the viewer identifies the viewer to the server to obtain the multicast message.

In a first possible implementation manner of the seventh aspect, the network address of the multicast initiating device in the multicast message is set in an option field in the standard COAP message; the network address of the multicast initiating device in the state change message is set in The option field in the standard COAP message; the identity of the observer server in the response message is set in the option field in the standard COAP message.

In a second possible implementation manner of the seventh aspect, before the first sending module sends the multicast message to the observer server, the third sending module is configured to send a standard COAP query message to the observer server, the standard COAP query message. The resource identifier module is configured to: perform a subscription registration on the resource according to the resource identifier, and query the current state of the resource; and a second sending module, configured to send a standard COAP response message to the observer client, where The standard COAP response message includes a current state of the resource, and a third receiving module is configured to receive the standard COAP response message.

In a third possible implementation manner of the seventh aspect, the multicast message and the state change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message. The latest time that can be accepted.

In a fourth possible implementation of the seventh aspect, the latest acknowledgement time in the multicast message and the status change message is set in an option field in the standard COAP message.

With reference to the fourth possible implementation manner of the seventh aspect, in a fifth possible implementation manner, the third sending module sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

The eighth aspect provides a multicast initiation apparatus, including a network interface, a memory, a processor, and a bus, a network interface, a memory, and a processor and a bus connection, wherein: the network interface is configured to send a multicast message to the observer server, where The multicast message includes a network address of the multicast originating device and an operation instruction for the resource of the observer server to cause the observer server to update the current state of the resource according to the operation instruction and send a status change message to the observer client, the status change message The network address of the multicast originating device and the current state after the resource update; the network interface is further configured to receive a response message sent by the observer client, where the response message includes an identifier of the observer server, where the response message is the observer client The program is sent after receiving the status change message sent by the observer server; the program is configured to store the identifier of the observer server from the response message to confirm that the observer server acquires the multicast message; the processor is configured to run program.

In a first possible implementation of the eighth aspect, the network address of the multicast originating device in the multicast message is set in an option field in the standard COAP message.

In a second possible implementation of the eighth aspect, the identifier of the observer server is the network address of the observer server.

In a third possible implementation manner of the eighth aspect, the multicast message and the state change message further include a latest acknowledgement time, where the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message The latest time that can be accepted.

In conjunction with the third possible implementation of the eighth aspect, in a fourth possible implementation, the latest acknowledgement time in the multicast message is set in an option field in the standard COAP message.

A ninth aspect provides a viewer server, including a network interface, a memory, a processor, and a bus, a network interface, a memory, and a processor and a bus connection, wherein: the network interface is configured to receive a multicast message sent by the multicast originating device, The multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server, a memory for storing the program, a program for updating a current state of the resource according to the operation instruction, and a processor for running the program; The network interface is configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated.

In a first possible implementation of the ninth aspect, the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message.

In a second possible implementation manner of the ninth aspect, the multicast message and the state change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message. The latest time that can be accepted.

In conjunction with the second possible implementation of the ninth aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message.

A tenth aspect provides an observer client, comprising a memory, a network interface, and a bus, wherein the memory and the network interface are respectively connected to the bus, wherein: the memory is used to store a program, the program is used to obtain an identifier of the observer server; the processor, And a network interface, configured to receive a state change message sent by the observer server, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated; the network interface is further configured to start according to the multicast The network address of the device sends a response message to the multicast originating device, wherein the response message includes an identity of the observer server such that the multicast originating device obtains the identity of the observer server from the response message to confirm that the observer server obtained the multicast message.

In a first possible implementation of the tenth aspect, the identifier of the observer server is a network address of the observer server.

In a second possible implementation of the tenth aspect, the multicast message and the state change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message. The latest time that can be accepted.

In conjunction with the second possible implementation of the tenth aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message.

In conjunction with the second possible implementation of the tenth aspect, in a fourth possible implementation, the third sending module sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

In a fifth possible implementation of the tenth aspect, the identifier of the observer server in the response message is set in an option field in the standard COAP message.

In a sixth possible implementation manner of the tenth aspect, the network interface is further configured to send a standard COAP query message to the observer server before receiving the state change message sent by the observer server, where the standard COAP query message includes the resource to be queried. Corresponding resource identifier, so that the observer server subscribes the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client, where the standard COAP response message includes the current state of the resource; the network interface Further used to receive standard COAP response messages.

The eleventh aspect provides a message processing system, comprising the multicast transmitting apparatus according to any one of the first to fourth possible implementation manners of the eighth aspect, the ninth aspect, and the first aspect of the ninth aspect An observer client of any one of the third possible implementations and the observer client of any of the first to sixth possible implementations of the tenth aspect.

Through the foregoing technical solution, an embodiment of the present invention provides a message processing method and related apparatus and system. After receiving a multicast message sent by a multicast sending apparatus, the observer server only needs to send a status change message to the observer client. End, and the observer client sends a response message to the multicast transmitting device for confirmation. Since the observer server does not need to separately send a response message to the multicast transmitting device and sends a status change message to the observer client, the signaling can be reduced. Overhead, reducing the load on the observer server.

 [Description of the Drawings]

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic structural diagram of a first embodiment of a message processing system according to the present invention;

2 is a flow chart of a first embodiment of a message processing method of the present invention;

3 is a schematic diagram of a data structure of a CoAP protocol stack;

4 is a schematic diagram of a data format of a standard COAP message;

5 is a schematic diagram of a data structure of an option field of a standard COAP message;

6 is a data interaction diagram of a second embodiment of a message processing method according to the present invention;

7 is a data interaction diagram of a third embodiment of a message processing method according to the present invention;

FIG. 8 is a flowchart of a fourth embodiment of a message processing method according to the present invention; FIG.

9 is a flowchart of a fifth embodiment of a message processing method according to the present invention;

FIG. 10 is a flowchart of a sixth embodiment of a message processing method according to the present invention; FIG.

11 is a schematic structural diagram of a first embodiment of a multicast initiating apparatus according to the present invention;

12 is a schematic structural diagram of a first embodiment of an observer server according to the present invention;

Figure 13 is a schematic structural view of a first embodiment of an observer server of the present invention;

14 is a schematic structural diagram of a second embodiment of a message processing system according to the present invention;

15 is a schematic structural diagram of a second embodiment of a multicast initiating apparatus according to the present invention;

Figure 16 is a schematic structural view of a second embodiment of the observer server of the present invention;

Figure 17 is a block diagram showing the structure of a second embodiment of the viewer client of the present invention.

 【detailed description】

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

First, please refer to FIG. 1. FIG. 1 is a schematic structural diagram of a first embodiment of a message processing system according to the present invention. As shown in FIG. 1, the message processing system of the present invention includes a multicast originating device 10, an observer server 20, and an observer client. 30. In the embodiment of the present invention, preferably, the multicast originating device 10 establishes a wireless network connection with the observer server 20, and the observer server establishes a wireless network connection with the observer client 30, of course, in an alternative implementation of the present invention. For example, the multicast originating device 10 and the observer server 20 can also establish a wired network connection, and the observer server and the observer client 30 can also establish a wired network connection, which is not limited by the present invention.

Also, the viewer server 20 device is preferably a wireless sensor device, the observer client 30 is preferably a terminal device, and the multicast originating device 10 is preferably a terminal device or server.

Referring to FIG. 2, FIG. 2 is a flowchart of a first embodiment of a message processing method according to the present invention. As shown in FIG. 3, the message processing method of the present invention includes the following steps:

Step 401: The observer client 30 acquires the identity of the observer server 20. The identifier of the observer server 20 is used to identify the observer server 20, which may be, for example, the network address of the observer server 20 or other identification code that can be used for identification. In this step, the observer client 30 may specifically acquire and record the identifier of the observer server 20 in advance. The specific manner of obtaining the identifier may include: the user manually inputs the identifier of the observer server 20 to the observer client 30, and the observer client. The terminal 30 pre-stores the identity of the observer server 20 or transmits its identity to the viewer client 30 or the like by the observer server 20.

Step 402: The multicast originating device 10 transmits a multicast message to the observer server 20. In this step, the multicast message includes the network address of the multicast originating device 10 and an operation instruction for the resources of the observer server 20. The resources described herein are provided by the observer server 20, which includes temperature, lights, brightness, etc., and the observer server 20 is provided with various types of sensors or controlled devices, such as temperature sensors, lights, brightness sensors, etc., as needed. Instructions are used to operate the above sensors or controlled devices, such as turning them on or off.

Step 403: The observer server 20 receives the multicast message, updates the current state of the resource according to the operation instruction, and sends a status change message to the observer client 30. The status change message includes a network address of the multicast originating device 10 and a current status after the resource is updated.

Step 404: The observer client 30 receives the status change message and sends a response message to the multicast originating device 10 according to the network address of the multicast originating device 10. The response message includes the identity of the observer server 20.

Step 405: The multicast initiating device 10 receives the response message, and acquires the identifier of the observer server 20 from the response message to confirm that the observer server 20 acquires the multicast message.

Alternatively, in the present invention, the multicast message, the status change message, and the response message may be obtained by modifying the standard COAP message.

Since many devices in the wireless Internet of Things (ie, the observer servers described herein) are resource-constrained, these devices have only a small amount of memory space and limited computing power. In March 2010, IETF (Intemet Engineering Task Force, Internet Engineering Task Force) CoRE (Constrained RESTful) Environment, limited RESTful environment) The working group started to develop CoAP (Constrained Application) Protocol, Restricted Application Protocol), which establishes related REST for Restricted Nodes (Representational State) Application layer protocol in the form of Transfer, Representational State Transfer). This is the CoAP protocol being developed by the CoRE Working Group. The CoAP protocol is an application layer protocol for resource-constrained devices in the Internet of Things. It is a network-oriented protocol that uses HTTP (HTTP-Hypertext) Transfer protocol, Hypertext Transfer Protocol) Similar features, such as resource abstraction, RESTful interaction, and extensible header options. Application by URI (Uniform Resource Identifier, the universal resource identifier) identifies the resources on the server, that is, GET (query), PUT (modify), POST (add), and DELETE (delete) operations on the resource like the HTTP protocol.

Referring to FIG. 3, FIG. 3 is a schematic diagram of a data structure of a COAP protocol stack. As shown in FIG. 1, the CoAP protocol stack includes a request/response layer, a service layer, and a UDP (User Datagram). Protocol, User Packet Protocol) layer and 6LoWPAN (IPv6 over Low power WPAN, the IPv6 protocol layer on the low-power wireless personal area network, the transport layer of the COAP protocol stack uses UDP (User Datagram) Protocol, User Datagram Protocol) protocol. Due to the unreliability of UDP transmission, the COAP protocol adopts a two-layer structure, defines a transaction mechanism with retransmission, and provides functions such as resource discovery and resource description.

For further clarity, please refer to FIG. 4, where FIG. 4 is a schematic diagram of a data format of a standard COAP message. As shown in FIG. 4, the standard COAP message includes a header, a payload field, and an option field, where the header includes V (Version, version) field, T (Type, type) field, OC (Option Count, number of options) field, e message type (Cod) field, and message number (Message ID) field.

Specifically, in the header, the V field indicates the version number of the COAP protocol, the OC field indicates the number of optional options following the packet header, the T field indicates the message type of the message, and the message type field indicates the type of the message (including the request message, response). Message, or empty message), the message number field indicates the message number, used for repeated message detection, matching message type, and so on.

Referring to FIG. 5, FIG. 5 is a schematic diagram of a data structure of an option field of a standard COAP message. As shown in FIG. 5, the option field may be specifically divided into multiple subfields 901, 902, ..., each subfield including an option variable field. , length field, and option value field.

In standard COAP messages, standard-based subfields are defined by standardizing the option variable field, length field, and option value field.

In the embodiment of the present invention, the multicast message, the state change message, and the response message may be obtained by modifying an existing standard COAP message. Specifically, the multicast originating device 10 may set the network address of the multicast originating device 10. An option field in the standard COAP message is set to generate a multicast message; the observer server 20 can set the network address of the multicast originating device 10 in an option field in the standard COAP message to generate a status change message; the observer client 30 The network address of the watcher server 20 can be set in an option field in a standard COAP message to generate a response message.

Specifically, the multicast originating device 10 may define an option variable as Mcast in an option field in a standard COAP message. Subfield of option, and the option variable is Mcast The network address of the multicast originating device 10 is recorded in the subfield of the option, thereby generating a multicast message; the observer server 20 may define the option variable as Mcast in the option field in the standard COAP message. Subfield of option, and the option variable is Mcast The network address of the observer server 20 is recorded in the subfield of the option, thereby generating a state change message; the observer client 30 can define the option variable as Mcast in the option field in the standard COAP message. A subfield of option, and the network address of the observer server 20 is recorded in a subfield whose option variable is Mcast option, thereby generating a state change message.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message. The observer client 30 sends a response message according to the latest confirmation time in the received status change message, before the latest confirmation time, and stops sending the response message when the current time is later than the latest latest confirmation time, due to the timeout In the case of the case, the response message is stopped, so the network bandwidth can be effectively saved.

Optionally, the observer client 30 may further define a time tolerance subfield in the option field of the response message for recording the latest time to complete the multicast acknowledgement. After receiving the response message, the multicast transmitting apparatus 10 determines whether the reception time exceeds the latest time, and if so, determines that the observer server 20 does not receive the multicast message, and if not, determines that the observer server 20 receives the multicast message. To achieve the function of timeout judgment.

Optionally, the multicast transmitting apparatus 10 may further define, in the multicast message, an identifier using the multicast confirmation method of the present invention, such as "ION" of step 5 in FIG. It is ensured that the observer server 20 adopts the multicast confirmation method of the present invention after receiving the multicast message, instead of using "NON" or "CON" supported in the prior art.

In an alternative embodiment of the present invention, prior to step 402, the method may further include the observer client 30 establishing an observer mode relationship with the observer server 20, wherein the observer client 30 establishes an observation with the observer server 20. The pattern relationship can be achieved in the following ways:

The observer client 30 sends a standard COAP query message to the observer server 20. The standard COAP query message includes the resource identifier corresponding to the resource to be queried, so that the observer server 20 subscribes to the resource according to the resource identifier, and queries the current state of the resource. And send a standard COAP response message to the observer client 30, where the standard COAP response message includes the current state of the resource.

The COAP query message and the standard COAP response message are existing standards, and the specific format thereof will be described in detail below.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, due to the observer server. There is no need to separately send a response message to the multicast transmitting device and send a status change message to the observer client, thereby reducing signaling overhead and reducing the load on the observer server.

Referring to FIG. 6, FIG. 6 is a data interaction diagram of a message processing method according to a second embodiment of the present invention. As shown in FIG. 6, the multicast message is generally sent in a broadcast manner, that is, in a broadcast manner. In contrast to the first embodiment of the message processing method of the present invention, two observer servers 20 are provided to illustrate that the multicast transmitting device transmits the multicast message to the plurality of observer servers, and only one observer The client sends a response message to the multicast transmitting device to cause the multicast transmitting device to confirm that the plurality of observer servers respectively receive the multicast message.

In the present embodiment, the viewer client 30 first establishes an observer mode relationship with the observer server 20 and the observer server 20', respectively, and the multicast originating device 10 transmits a multicast message, the observer server 20 and the observer server 20' The multicast messages are respectively received, and the status change message is respectively sent to the observer client 30. After receiving the status change message, the observer client 30 sends a response message to the multicast originating device 10 to cause the multicast originating device 10 to confirm the observer. The server 20 acquires a multicast message.

The following is a detailed description with reference to FIG. 6. As shown in FIG. 6, the second embodiment of the message processing method of the present invention specifically includes the following steps:

Step 1: The observer client 30 sends a standard COAP query message to the observer server 20'. In this embodiment, the standard COAP query message is specifically: COAP CON (GET, uri-path: light, Token: 0x3c, Observe: Empty). Where COAP indicates compliance with the COAP standard; CON indicates a verifiable message; GET indicates a REST-based query operation method; uri-path is an option defined by the standard COAP message, indicating that the target resource light (light) is looked up from the observer server 20' The Token is a token that establishes an observation mode relationship, and then sends a status change message to carry the same Token; Observe is also an option defined by the standard COAP message, indicating that it is an observation mode relationship message, and the option value of the option is empty to indicate the application. Establish an observation mode relationship.

Step 2: The observer server 20' subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client 30. In this embodiment, The standard COAP response message is specifically: COAP NON (2.05 Content Token: 0x3c Observe: 12 Payload: OFF). Among them, this type of message is a standard COAP response message, and NON means a message that does not need to be confirmed; 2.05 Content is a response message carrying the content of the message, and OFF indicates that the content of the resource Light is off.

Step 3: The observer client 30 sends a standard COAP query message to the observer server 20. In this embodiment, the standard COAP query message is specifically: COAP CON (GET, uri-path: light, Token: 0x4a, Observe: Empty). The data format of the standard COAP query message is the same as that described in step 1, and details are not described herein.

Step 4: The observer server 20 subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client 30. In this embodiment, the standard COAP response message is specifically: COAP. NON(2.05 Content Token: 0x4a Observe: 12 Payload: OFF). The standard COAP response message is the same as that described in step 2, and details are not described herein.

Step 5: The multicast initiating device 10 sends a multicast message to the observer server 20 and the observer server 20. In this embodiment, the multicast message is specifically: COAP ION Mcast(PUT, payload=lights ON) Mcast option: MI. In this embodiment, the multicast message is obtained by improving on the basis of a standard COAP message, wherein Mcast represents a multicast message, ION represents a multicast confirmation mode using the present invention, and PUT represents a REST-based modification operation method; =lights ON indicates an instruction to turn the light on. MI indicates the network address of the multicast transmitting device, which is set in the custom sub-option field whose option variable is Mcast option.

Step 6: After receiving the multicast message, the observer server 20 sends a status change message to the observer client 30. In this embodiment, the status change message is specifically: COAP. NON(2.05 Content Token: 0x4a Observe: 12 Payload: ON Mcast option: MI). In this step, after the observer server 20 receives the multicast message, it will further according to the lights. The ON instruction operates on the resource Light such that the state of the resource light changes, the state change message is obtained based on the improvement of the standard COAP message, and the MI represents the network address of the multicast transmitting device. Its setting in the option variable is defined as Mcast In the suboption field of option.

Step 7: After receiving the multicast message, the observer server 20' sends a status change message to the observer client 30. In this embodiment, the status change message is specifically: COAP. NON(2.05 Content Token: 0x3c Observe: 12 Payload:ON Mcast option: MI). In this step, after the viewer server 20' receives the multicast message, it will further according to the lights. The ON instruction operates on the resource Light such that the state of the resource light changes, the state change message is obtained based on the improvement of the standard COAP message, and the MI represents the network address of the multicast transmitting device. Its setting in the option variable is defined as Mcast In the suboption field of option.

Step 8: The observer client 30 sends a response message to the multicast originating device 10 after receiving the status change message sent by the observer server 20, respectively. In this embodiment, the response message is specifically: COAP NON (2.04 Changed) Mcast option: MR1, MR2.2.04 Changed is a response message indicating a change in state. MR1 represents the network address of the observer server 20, and MR2 represents the network address of the observer server 20'. MR1 and MR2 are set in the option variable Mcast Option in the custom suboption field.

In this embodiment, the multicast initiating device 10 acquires a response message including the network address MR1 of the observer server 20 and the network address MR2 of the observer server 20' from the observer client 30 after the multicast transmission of the multicast message. , thereby confirming that the received observer server 20 and the observer server 20' respectively receive the multicast message.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message. The observer client 30 sends a response message according to the latest confirmation time in the received status change message, before the latest confirmation time, and stops sending the response message when the current time is later than the latest latest confirmation time, due to the timeout In the case of the case, the response message is stopped, so the network bandwidth can be effectively saved.

In this embodiment, the multicast transmitting apparatus 10 can further define the identifier of the multicast confirmation method of the present invention in the multicast message, such as "ION" of step 5 in FIG. It is ensured that the observer server 20 adopts the multicast confirmation method of the present invention after receiving the multicast message, instead of using "NON" or "CON" supported in the prior art.

Please refer to FIG. 7. FIG. 7 is a data interaction diagram of a third embodiment of the message processing method according to the present invention. Compared with the first embodiment of the message processing method of the present invention, two observer servers 20 are provided, and two An observer client 30, thereby indicating that the multicast transmitting device multicast message is sent to the plurality of observer servers, and the plurality of observer clients respectively send the response message to the multicast transmitting device to cause the multicast transmitting device to confirm The case where multiple observer servers receive multicast messages respectively.

In the present embodiment, the viewer client 30 first establishes an observer mode relationship with the observer server 20, the observer client 30' first establishes an observer mode relationship with the observer server 20', and the multicast originating device 10 transmits the multicast mode. The message, the observer server 20 and the observer server 20' respectively receive the multicast message, the observer server 20 sends a status change message to the observer client 30, and the observer server 20' sends a status change message to the observer client 30' After receiving the status change message, the observer client 30 sends a response message to the multicast initiating device 10. After receiving the status change message, the observer client 30' sends a response message to the multicast initiating device 10 to cause the multicast initiating device. 10 Confirm that the observer server 20 and the observer server 20' acquire the multicast message. The following is a detailed description with reference to FIG. 7. As shown in FIG. 7, the second embodiment of the message processing method of the present invention specifically includes the following steps:

Step 1: The observer client 30' sends a standard COAP query message to the observer server 20'. In this embodiment, the standard COAP query message is specifically: COAP CON (GET, uri-path: light, Token: 0x3c, Observe: empty).

Step 2: The observer server 20' subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client 30'. In this embodiment, The standard COAP response message is specifically: COAP NON (2.05 Content Token: 0x3c Observe: 12 Payload: OFF).

Step 3: The observer client 30 sends a standard COAP query message to the observer server 20. In this embodiment, the standard COAP query message is specifically: COAP CON (GET, uri-path: light, Token: 0x4a, Observe: empty).

Step 4: The observer server 20 subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client 30. In this embodiment, the standard COAP response message is specifically: COAP. NON (2.05 Content Token: 0x4a Observe: 12 Payload: OFF).

Step 5: The multicast initiating device 10 sends a multicast message to the observer server 20 and the observer server 20'. In this embodiment, the multicast message is specifically: COAP ION Mcast(PUT, payload=lights ON) Mcast option: MI.

Step 6: After receiving the multicast message, the observer server 20 sends a status change message to the observer client 30. In this embodiment, the status change message is specifically: COAP. NON(2.05 Content Token: 0x4a Observe: 12 Payload: ON Mcast option: MI).

Step 7: After receiving the multicast message, the observer server 20' sends a status change message to the observer client 30'. In this embodiment, the status change message is specifically: COAP. NON(2.05 Content Token: 0x3c Observe: 12 Payload: ON Mcast option: MI).

Step 8: After receiving the status change message sent by the observer server 20, the observer client 30 sends a response message to the multicast originating device 10. In this embodiment, the response message sent by the observer client 30 is specifically: COAP NON (2.04 Changed) Mcast option: MR1.

Step 9: The observer client 30' receives the status change message sent by the observer server 20' and sends a response message to the multicast originating device 10. In this embodiment, the response message sent by the observer client 30' is specifically: COAP NON (2.04 Changed) Mcast option: MR2.

Therefore, the multicast originating apparatus 10 acquires the network address MR1 of the observer server 20 and the network address MR2 of the observer server 20', thereby confirming that the received observer server 20 and the observer server 20' respectively receive the multicast message.

The data structure of the above message is similar to the embodiment shown in FIG. 6, and details are not described herein.

In this embodiment, the multicast initiating device 10 acquires a response message including the network address MR1 of the observer server 20 from the observer client 30 after broadcasting the multicast message, and acquires an observation from the observer client 30'. The response message of the network address MR2 of the server 20' confirms that the received observer server 20 and the observer server 20' respectively receive the multicast message.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message. The observer client 30 sends a response message according to the latest confirmation time in the received status change message, before the latest confirmation time, and stops sending the response message when the current time is later than the latest latest confirmation time, due to the timeout In the case of the case, the response message is stopped, so the network bandwidth can be effectively saved.

In this embodiment, the multicast transmitting apparatus 10 can further define the identifier of the multicast confirmation method of the present invention in the multicast message, such as "ION" of step 5 in FIG. It is ensured that the observer server 20 adopts the multicast confirmation method of the present invention after receiving the multicast message, instead of using "NON" or "CON" supported in the prior art.

Referring to FIG. 8, FIG. 8 is a flowchart of a fourth embodiment of a message processing method according to the present invention. It should be noted that, in this embodiment, the multicast initiating device is used as the step execution subject. As shown in FIG. 8, the message processing method of the present invention includes the following steps:

Step 501: The multicast originating device sends a multicast message to the observer server. The multicast message includes a network address of the multicast originating device and an operation instruction for the resource of the observer server, so that the observer server updates the current state of the resource according to the operation instruction after receiving the multicast message.

Step 502: The multicast originating device receives the response message sent by the observer client. The response message includes the identity of the observer server.

Step 503: The multicast initiating device acquires the identifier of the observer server from the response message to confirm that the observer server acquires the multicast message. The response message is sent by the observer client after receiving the state change message sent by the observer server, and the observer server sends a state change message to the observer client after receiving the multicast message, and the state change message includes multicast. The network address of the originating device and the current state after the resource is updated.

Optionally, the network address of the multicast originating device in the multicast message is set in an option field in a standard COAP message.

Optionally, the identifier of the observer server is the network address of the observer server.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message is set in the option field in the standard COAP message.

In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is In the plural, since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it is not necessary to separately send the signaling to the multicast initiator and the observer client twice, so Save signaling bandwidth and power consumption of the observer client itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 9, FIG. 9 is a flowchart of a fifth embodiment of a message processing method according to the present invention. It should be noted that the embodiment is described by using the observer server as the step execution subject. As shown in FIG. 8, the message processing method of the present invention includes the following steps:

Step 601: The observer server receives the multicast message sent by the multicast originating device. The multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server.

Step 602: The observer server updates the current state of the resource according to the operation instruction.

Step 603: The observer server sends a status change message to the observer client, where the status change message includes the network address of the multicast originating device and the current status after the resource is updated.

Optionally, the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message and the status change message is set in the option field in the standard COAP message.

In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is In the plural, since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it is not necessary to separately send the signaling to the multicast initiator and the observer client twice, so Save signaling bandwidth and power consumption of the observer client itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 10, FIG. 10 is a flowchart of a sixth embodiment of a message processing method according to the present invention. It should be noted that, in this embodiment, the observer client is used as the step execution subject. As shown in FIG. 10, the message processing method of the present invention includes the following steps:

Step 601: The observer client acquires the identifier of the observer server.

Step 602: The observer client receives a state change message sent by the observer server. The status change message includes a network address of the multicast originating device and a current status after the resource is updated;

Step 603: The observer client sends a response message to the multicast originating device according to the network address of the multicast originating device, where the response message includes an identifier of the observer server, so that the multicast initiating device acquires the identifier of the observer server from the response message to confirm The observer server gets the multicast message.

Optionally, the identifier of the observer server is the network address of the observer server.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message and the status change message is set in the option field in the standard COAP message.

Optionally, the observer client sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

Optionally, the identifier of the observer server in the response message is set in an option field in the standard COAP message.

Optionally, before step 601, the method further comprises: the observer client establishing an observer mode relationship with the observer server, specifically, the observer client sends a standard COAP query message to the observer server, the standard COAP query message Include the resource identifier corresponding to the resource to be queried, so that the observer server subscribes the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client, where the standard COAP response message includes the resource. Current status.

In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is In the plural, since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it is not necessary to separately send the signaling to the multicast initiator and the observer client twice, so Save signaling bandwidth and power consumption of the observer client itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 11, FIG. 11 is a schematic structural diagram of a first embodiment of a multicast initiating apparatus according to the present invention. As shown in FIG. 10, the multicast initiating apparatus 10 of the present invention includes:

The first sending module 101 is configured to send a multicast message to the observer server, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server, so that the observer server according to the operation instruction Updating a current state of the resource, and sending a state change message to the observer client, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated;

The first receiving module 102 is configured to receive a response message sent by the observer client, where the response message includes an identifier of the observer server, where the response message is sent by the observer client after receiving the state change message sent by the observer server;

The confirmation module 104 is configured to obtain an identifier of the observer server from the response message to confirm that the observer server acquires the multicast message.

Optionally, the network address of the multicast originating device in the multicast message is set in an option field in a standard COAP message.

Optionally, the identifier of the observer server is the network address of the observer server.

Optionally, the multicast message and the status change message include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server has obtained the multicast message.

Optionally, the latest acknowledgement time in the multicast message is set in the option field in the standard COAP message. In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is For a larger number (such as hundreds), since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it does not need to send the multicast initiator and the observer client twice separately. Signaling, therefore, can greatly save the signaling transmission bandwidth and the power consumption of the observer server itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 12, FIG. 12 is a schematic structural diagram of a first embodiment of an observer server according to the present invention. As shown in FIG. 12, the observer server 20 of the present invention includes:

The second receiving module 204 is configured to receive a multicast message sent by the multicast originating device, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server;

The resource processing module 202 is configured to update a current state of the resource according to the operation instruction;

The state change message generating module 201 is configured to generate a state change message, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated;

The second sending module 203 is configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated.

Optionally, the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message.

In a second possible implementation manner of the fifth aspect, the multicast message and the state change message further include a latest acknowledgement time, where the latest acknowledgement time is used to indicate that the multicast originating device confirms that the observer server obtains the multicast message The latest time that can be accepted.

In conjunction with the second possible implementation of the fifth aspect, in a third possible implementation, the latest acknowledgement time in the multicast message and the state change message is set in an option field in the standard COAP message. In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is In the plural, since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it is not necessary to separately send the signaling to the multicast initiator and the observer client twice, so Save signaling bandwidth and power consumption of the observer server itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 13, FIG. 13 is a schematic structural diagram of a first embodiment of an observer server according to the present invention. As shown in FIG. 12, the viewer client 30 of the present invention includes:

An identifier obtaining module 301, configured to acquire an identifier of the observer server;

The third receiving module 304 is configured to receive a state change message sent by the observer server, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated;

The third sending module 303 is configured to send a response message to the multicast originating device according to the network address of the multicast initiating device, where the response message includes an identifier of the observer server, so that the multicast initiating device acquires the identifier of the observer server from the response message. Confirm that the Observer server gets the multicast message.

Optionally, the identifier of the observer server is the network address of the observer server.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message and the status change message is set in the option field in the standard COAP message.

Optionally, the third sending module sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

Optionally, the identifier of the observer server in the response message is set in an option field in the standard COAP message.

Optionally, the third sending module 303 is further configured to send a standard COAP query message to the observer server before the third receiving module 304 receives the state change message sent by the observer server, where the standard COAP query message includes the resource to be queried. The resource identifier is such that the observer server subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client 30, wherein the standard COAP response message includes the current state of the resource; Module 304 is further for receiving a standard COAP response message.

In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is In the plural, since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it is not necessary to separately send the signaling to the multicast initiator and the observer client twice, so Save signaling bandwidth and power consumption of the observer server itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 14, FIG. 14 is a schematic structural diagram of a second embodiment of a message processing system according to the present invention. As shown in FIG. 14, the message processing system of the present invention includes a multicast originating device 10, a viewer server 20, and an observer client. ,among them:

The multicast initiating device 10 includes:

The first sending module 101 is configured to send a multicast message to the observer server 20, where the multicast message includes a network address of the multicast originating device 10 and an operation instruction for the resource of the observer server 20;

 The observer server 20 includes:

The second receiving module 204 is configured to receive the multicast message sent by the multicast originating device 10;

The resource processing module 202 is configured to operate on the resource according to the operation instruction to update the current state of the resource;

The second sending module 203 is configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device 10 and a current status after the resource is updated;

The observer client 30 includes:

 An identifier obtaining module 301, configured to acquire an identifier of the observer server 20;

The third receiving module 304 is configured to receive a state change message sent by the observer server 20;

The third sending module 303 is configured to send a response message to the multicast initiating device 10 according to the network address of the multicast initiating device 10, where the response message includes an identifier of the observer server 20;

The multicast transmitting apparatus further includes a first receiving module 102 and a confirming module 104. The first receiving module 102 is configured to receive a response message, and the confirming module 104 is configured to acquire the identifier of the observer server 20 from the response message to confirm that the observer server 20 obtains Multicast message.

Optionally, the network address of the multicast originating device in the multicast message is set in an option field in the standard COAP message; the network address of the multicast originating device in the status change message is set in an option field in the standard COAP message; the response message The identity of the observer server in the setting is set in the option field in the standard COAP message.

Optionally, before the first sending module 101 sends the multicast message to the observer server 20, the third sending module 303 is configured to send a standard COAP query message to the observer server 20, where the standard COAP query message includes the resource corresponding to the query. The resource identifier module 202 is configured to perform subscription registration on the resource according to the resource identifier, and query the current state of the resource. The second sending module 203 is configured to send a standard COAP response message to the observer client, where the standard COAP response message is sent. Includes the current state of the resource.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message and the status change message is set in the option field in the standard COAP message.

Optionally, in a fifth possible implementation manner, the third sending module sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time. The third sending module stops sending the response message to the multicast initiating device after the latest acknowledgement time, and stops sending the response message when the timeout occurs, thereby effectively saving network bandwidth and reducing unnecessary information transmission, thereby improving system transmission efficiency.

In the present embodiment, only the case where the number of observer servers and observer clients is one is shown, but in an alternative embodiment of the present invention, the number of observer servers may be plural, and the number of observer clients The present invention is not limited thereto, but it is worth noting that when the number of observer servers is plural, since each observer server only needs to send signaling to the observer client (ie, status response) The message) does not need to separately send signaling to the multicast originating device and the observer client, so that the signaling transmission bandwidth and the power consumption of the observer server itself can be greatly saved.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 15, FIG. 15 is a schematic structural diagram of a second embodiment of a multicast initiating apparatus according to the present invention. As shown in FIG. 15, the multicast initiating apparatus 10 of the present invention includes a network interface 111, a memory 113, a processor 112, and a bus. 114. The network interface 111, the memory 113, and the processor 112 are connected to the bus 114, wherein:

The network interface 111 is configured to send a multicast message to the observer server, where the multicast message includes a network address of the multicast originating device and an operation instruction for the resource of the observer server, so that the observer server updates the resource according to the operation instruction. a current state, and sending a state change message to the observer client, the state change message including a network address of the multicast originating device and a current state after the resource is updated;

The network interface 11 is further configured to receive a response message sent by the observer client, where the response message includes an identifier of the observer server, where the response message is sent by the observer client after receiving the state change message sent by the observer server;

The memory 113 is configured to store a program, and the program is configured to acquire an identifier of the observer server from the response message to confirm that the observer server acquires the multicast message;

The processor 112 is used to run a program.

Optionally, the network address of the multicast originating device in the multicast message is set in an option field in a standard COAP message.

Optionally, the identifier of the observer server is the network address of the observer server.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message is set in the option field in the standard COAP message. In this embodiment, the number of observer servers may be one or plural, and the number of observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is When the number is large, since each observer server only needs to send signaling (ie, status response message) to the observer client, it is not necessary to separately send signaling to the multicast initiator and the observer client, so The earth saves signaling transmission bandwidth and the power consumption of the observer server itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 16, FIG. 16 is a schematic structural diagram of a second embodiment of an observer server according to the present invention. As shown in FIG. 16, the viewer server 20 of the present invention includes a network interface 211, a memory 213, a processor 212, and a bus 214. Network interface 211, memory 213, and processor 212 are coupled to bus 214, where:

The network interface 211 is configured to receive the multicast message sent by the multicast originating device 10, where the multicast message includes a network address of the multicast originating device 10 and an operation instruction for the resource of the observer server 20;

The memory 213 stores a program for updating a current state of the resource according to the operation instruction;

a processor 212, configured to run a program;

The network interface 211 is configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated.

Optionally, the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message and the status change message is set in the option field in the standard COAP message. In this embodiment, since each observer server 20 only needs to send signaling (ie, status response message) to the observer client, it is not necessary to separately send signaling to the multicast originating device and the observer client, respectively. The signaling transmission bandwidth and the power consumption of the observer server itself can be greatly saved.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

Referring to FIG. 17, FIG. 17 is a schematic structural diagram of a second embodiment of an observer client according to the present invention. As shown in FIG. 17, the viewer client 30 of the present invention includes a processor 312, a memory 313, a network interface 311, and a bus. 314, the memory 313 and the network interface 311 are respectively connected to the bus 314, wherein:

a memory 313, configured to store a program, where the program is used to obtain an identifier of the observer server;

The processor 312 runs the program;

The network interface 311 is configured to receive a state change message sent by the observer server, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated;

The network interface 311 is further configured to send a response message to the multicast originating device according to the network address of the multicast originating device, where the response message includes an identifier of the observer server, so that the multicast initiating device acquires the identifier of the observer server from the response message to confirm The observer server gets the multicast message.

Optionally, the identifier of the observer server is the network address of the observer server.

Optionally, the multicast message and the status change message further include a latest acknowledgement time, and the latest acknowledgement time is used to indicate the latest time that the multicast originating device can accept when confirming that the observer server acquires the multicast message.

Optionally, the latest acknowledgement time in the multicast message and the status change message is set in the option field in the standard COAP message.

Optionally, the third sending module sends a response message to the multicast originating device according to the network address of the multicast originating device before the latest acknowledgement time.

Optionally, the identifier of the observer server in the response message is set in an option field in the standard COAP message.

Optionally, the network interface 311 is further configured to send a standard COAP query message to the observer server before receiving the state change message sent by the observer server, where the standard COAP query message includes the resource identifier corresponding to the resource to be queried, so that the observer The server subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the observer client, where the standard COAP response message includes the current state of the resource; the network interface 311 is further configured to receive the standard COAP response message. . Observer client 30 establishes an observer mode relationship with the observer server after receiving the standard COAP response message.

In this embodiment, the number of the observer servers may be one or plural, and the number of the observer clients may be one or plural. The present invention does not limit this, but it is worth noting that when the number of observer servers is compared In large cases, since each observer server only needs to send a signaling (ie, a status response message) to the observer client, it is not necessary to separately send signaling to the multicast originating device and the observer client, thereby greatly saving Signaling transmission bandwidth and power consumption of the observer server itself.

After receiving the multicast message sent by the multicast transmitting device, the observer server only needs to send a status change message to the observer client, and the observer client sends a response message to the multicast transmitting device for confirmation, since the observer server does not need to The response message is respectively sent to the multicast transmitting apparatus, and the status change message is sent to the observer client, so that the signaling overhead can be reduced and the load of the observer server can be reduced.

The present invention further provides a message processing system including the multicast originating device, the viewer client, and the observer server described in FIGS. 15-17.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the foregoing embodiment of the device embodiment is merely illustrative. For example, the division of the module or unit is only a logical function division, and the actual implementation may have another division manner, such as multiple units or Components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. The instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only) Memory, random access memory (RAM), disk or optical disk, and other media that can store program code.

The above is only the embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformation of the present invention and the contents of the drawings may be directly or indirectly applied to other related technologies. The fields are all included in the scope of patent protection of the present invention.

Claims (55)

A message processing method, comprising: The multicast originating device transmits a multicast message to the observer server, wherein the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server, such that the observer server is configured according to the The operation instruction updates a current state of the resource, and sends a state change message to the observer client, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated; The multicast originating device receives a response message sent by the observer client, the response message including an identifier of the observer server, wherein the response message is that the observer client is receiving the observer Transmitted after the status change message sent by the server; The multicast originating device acquires an identifier of the observer server from the response message to confirm that the observer server acquires the multicast message. The method according to claim 1, wherein the network address of the multicast originating device in the multicast message is set in an option field in a standard COAP message. The method of claim 1 wherein the identity of the observer server is a network address of the observer server. The method of claim 1, wherein the multicast message and the status change message further comprise a latest acknowledgement time, the latest acknowledgement time being used to indicate that the multicast originating device is acknowledging the The latest time that the observer server can accept when the multicast message is obtained. The method of claim 4 wherein the latest acknowledgement time in the multicast message is set in an option field in a standard COAP message. A message processing method, comprising: The observer server receives the multicast message sent by the multicast originating device, wherein the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server; The observer server updates a current state of the resource according to the operation instruction; The observer server sends a status change message to the observer client, the status change message including a network address of the multicast originating device and a current status after the resource is updated. The method of claim 6, wherein the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message. The method of claim 6, wherein the multicast message and the status change message further comprise a latest acknowledgement time, the latest acknowledgement time being used to indicate that the multicast originating device is acknowledging the The latest time that the observer server can accept when the multicast message is obtained. The method of claim 8, wherein the latest acknowledgement time in the multicast message and the status change message is set in an option field in a standard COAP message. A message processing method, comprising: The observer client obtains the identity of the observer server; Receiving, by the observer client, a status change message sent by the observer server, where the status change message includes a network address of the multicast originating device and a current status of the resource of the observer server after updating; The observer client sends a response message to the multicast originating device according to the network address of the multicast originating device, wherein the response message includes an identifier of the observer server such that the multicast originating device receives the response The message acquires the identity of the observer server to confirm that the observer server obtained the multicast message. The method of claim 10 wherein the identity of the observer server is a network address of the observer server. The method of claim 10, wherein the multicast message and the status change message further comprise a latest acknowledgement time, the latest acknowledgement time being used to indicate that the multicast originating device is acknowledging the The latest time that the observer server can accept when the multicast message is obtained. The method of claim 12, wherein the latest acknowledgement time in the multicast message and the state change message is set in an option field in a standard COAP message. The method of claim 12 wherein said observer client transmits said response message to said multicast originating device in accordance with a network address of said multicast originating device prior to said latest acknowledgement time. The message processing method according to claim 10, wherein the identifier of the observer server in the response message is set in an option field in a standard COAP message. The method of claim 10, wherein before the observer client receives the status change message sent by the observer server, the method further comprises: The observer client establishes an observer mode relationship with the observer server, wherein the observer client establishes an observer mode relationship with the observer server, including: The observer client sends a standard COAP query message to the observer server, where the standard COAP query message includes a resource identifier corresponding to the resource to be queried, so that the observer server pairs the resource according to the resource identifier. A subscription registration is made, the current state of the resource is queried, and a standard COAP response message is sent to the observer client, wherein the standard COAP response message includes the current state of the resource. A multicast initiating device, comprising: a first sending module, configured to send a multicast message to an observer server, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server, so that the observation The server updates the current state of the resource according to the operation instruction, and sends a state change message to the observer client, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated. ; a first receiving module, configured to receive a response message sent by the observer client, where the response message includes an identifier of the observer server, where the response message is that the observer client receives the observation Sent by the server after the status change message is sent; And an acknowledgment module, configured to obtain an identifier of the observer server from the response message to confirm that the observer server acquires the multicast message. The multicast originating apparatus according to claim 17, wherein a network address of the multicast originating apparatus in the multicast message is set in an option field in a standard COAP message. The multicast originating apparatus according to claim 17, wherein the identifier of the observer server is a network address of the observer server. The multicast originating apparatus according to claim 17, wherein said multicast message and said status change message comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate that said multicast originating device is The latest time that the observer server can accept when the multicast message is obtained is confirmed. The multicast originating apparatus according to claim 20, wherein a latest acknowledgement time in said multicast message is set in an option field in a standard COAP message. An observer server, comprising: a second receiving module, configured to receive a multicast message sent by the multicast originating device, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server; a resource processing module, configured to update a current state of the resource according to the operation instruction; And a second sending module, configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated. The observer server of claim 22, wherein the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message. The observer server according to claim 22, wherein said multicast message and said status change message further comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate that said multicast originating device is confirming The latest time that the observer server can accept when the multicast message is obtained. The observer server according to claim 24, wherein said latest acknowledgement time in said multicast message and said state change message is set in an option field in a standard COAP message. An observer client, comprising: An identifier obtaining module, configured to acquire an identifier of the observer server; a third receiving module, configured to receive a state change message sent by the observer server, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated; a third sending module, configured to send a response message to the multicast originating device according to the network address of the multicast initiating device, where the response message includes an identifier of the observer server, so that the multicast initiating device is from the The response message acquires the identity of the observer server to confirm that the observer server acquires the multicast message. The viewer client of claim 26 wherein the identity of the viewer server is a network address of the observer server. The viewer client of claim 26, wherein said multicast message and said status change message further comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate that said multicast originating device is The latest time that the observer server can accept when the multicast message is obtained is confirmed. The viewer client of claim 28, wherein said latest acknowledgement time in said multicast message and said state change message is set in an option field in a standard COAP message. The observer client according to claim 28, wherein said third transmitting module transmits said response message to said multicast according to a network address of said multicast originating device before said latest acknowledgement time Initiate the device. The viewer client of claim 26, wherein the identity of the observer server in the response message is set in an option field in a standard COAP message. The viewer client according to claim 26, wherein said third transmitting module is further configured to send to said observer server before said third receiving module receives a state change message sent by the observer server a standard COAP query message, where the standard COAP query message includes a resource identifier corresponding to the resource to be queried, so that the observer server performs subscription registration on the resource according to the resource identifier, and queries the current state of the resource, and Transmitting a standard COAP response message to the observer client, wherein the standard COAP response message includes a current state of the resource; The third receiving module is further configured to receive the standard COAP response message. A message processing system, comprising: Multicast originating device, including: a first sending module, configured to send a multicast message to the observer server, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server;  Observer server, including: a second receiving module, configured to receive a multicast message sent by the multicast originating device; a resource processing module, configured to update a current state of the resource according to the operation instruction; a second sending module, configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated; Observer client, including:  An identifier obtaining module, configured to acquire an identifier of the observer server; a third receiving module, configured to receive a status change message sent by the observer server; a third sending module, configured to send a response message to the multicast originating device according to the network address of the multicast initiating device, where the response message includes an identifier of the observer server; The multicast sending apparatus further includes a first receiving module, configured to receive the response message, and a confirming module, where the confirming module is configured to acquire an identifier of the observer server from the response message. Confirming that the observer server acquires the multicast message. The system of claim 33, wherein The network address of the multicast originating device in the multicast message is set in an option field in a standard COAP message; The network address of the multicast originating device in the status change message is set in an option field in a standard COAP message; The identity of the observer server in the response message is set in an option field in a standard COAP message. The system of claim 33, prior to said first transmitting module transmitting a multicast message to an observer server, The third sending module is configured to send a standard COAP query message to the observer server, where the standard COAP query message includes a resource identifier corresponding to the resource to be queried; The resource processing module is configured to perform subscription registration on the resource according to the resource identifier, and query a current state of the resource; The second sending module is configured to send a standard COAP response message to the observer client, where the standard COAP response message includes a current state of the resource; The third receiving module is configured to receive the standard COAP response message. The system according to claim 33, wherein said multicast message and said status change message further comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate said multicast originating device is acknowledging said The latest time that the observer server can accept when the multicast message is obtained. The system of claim 33, wherein the latest acknowledgement time in the multicast message and the status change message is set in an option field in a standard COAP message. The system according to claim 36, wherein said third transmitting module transmits said response message to said multicast originating device according to a network address of said multicast originating device prior to said latest acknowledgement time. A multicast initiating device, comprising: a network interface, a memory, a processor, and a bus, wherein the network interface, the memory, and the processor are connected to the bus, wherein: The network interface, configured to send a multicast message to an observer server, where the multicast message includes a network address of the multicast originating device and an operation instruction for a resource of the observer server, such that the observation The server updates the current state of the resource according to the operation instruction, and sends a state change message to the observer client, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated. ; The network interface is further configured to receive a response message sent by the observer client, where the response message includes an identifier of the observer server, where the response message is that the observer client is receiving the observer Transmitted after the status change message sent by the server; The memory is configured to store a program, where the program is configured to acquire an identifier of the observer server from the response message to confirm that the observer server acquires the multicast message; The processor is configured to run the program. The multicast originating apparatus according to claim 39, wherein a network address of the multicast originating apparatus in the multicast message is set in an option field in a standard COAP message. The multicast originating apparatus according to claim 39, wherein the identifier of the observer server is a network address of the observer server. The multicast originating apparatus according to claim 39, wherein said multicast message and said status change message further comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate that said multicast originating device is The latest time that the observer server can accept when the multicast message is obtained is confirmed. The multicast originating apparatus according to claim 42, wherein the latest acknowledgement time in said multicast message is set in an option field in a standard COAP message. An observer server, comprising: a network interface, a memory, a processor, and a bus, wherein the network interface, the memory, and the processor are connected to the bus, wherein: The network interface is configured to receive a multicast message sent by a multicast originating device, where the multicast message includes an operation instruction of a network address of the multicast originating device and a resource for an observer server; The memory is configured to store a program, where the program is configured to update a current state of the resource according to the operation instruction; The processor is configured to run the program; The network interface is configured to send a status change message to the observer client, where the status change message includes a network address of the multicast originating device and a current status after the resource is updated. The viewer server of claim 44, wherein the network address of the multicast originating device in the status change message is set in an option field in a standard COAP message. The observer server according to claim 44, wherein said multicast message and said status change message further comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate that said multicast originating device is confirming The latest time that the observer server can accept when the multicast message is obtained. The observer server according to claim 44, wherein said latest acknowledgement time in said multicast message and said state change message is set in an option field in a standard COAP message. An observer client, comprising: a memory, a network interface, and a bus, wherein the memory and the network interface are respectively connected to the bus, wherein: The memory is configured to store a program, where the program is used to obtain an identifier of the observer server; The processor is configured to run the program; The network interface is configured to receive a state change message sent by the observer server, where the state change message includes a network address of the multicast originating device and a current state after the resource is updated; The network interface is further configured to send a response message to the multicast initiation device according to the network address of the multicast initiation device, where the response message includes an identifier of the observer server, so that the multicast initiation device The response message acquires an identifier of the observer server to confirm that the observer server acquires a multicast message. The viewer client of claim 48, wherein the identifier of the observer server is a network address of the observer server. The viewer client of claim 48, wherein said multicast message and said status change message further comprise a latest acknowledgement time, said latest acknowledgement time being used to indicate that said multicast originating device is The latest time that the observer server can accept when the multicast message is obtained is confirmed. The viewer client of claim 50 wherein said latest acknowledgement time in said multicast message and said state change message is set in an option field in a standard COAP message. The observer client according to claim 50, wherein said third transmitting module transmits said response message to said multicast according to a network address of said multicast originating device before said latest acknowledgement time Initiate the device. The viewer client of claim 48, wherein the identity of the observer server in the response message is set in an option field in a standard COAP message. The viewer client of claim 48, wherein said network interface is further for transmitting a standard COAP query message to said observer server prior to receiving a status change message sent by the observer server, said standard The COAP query message includes a resource identifier corresponding to the resource to be queried, so that the observer server subscribes to the resource according to the resource identifier, queries the current state of the resource, and sends a standard COAP response message to the An observer client, wherein the standard COAP response message includes a current state of the resource; The network interface is further for receiving the standard COAP response message. A message processing system comprising the multicast transmitting apparatus according to any one of claims 39-43, the observer server according to any one of claims 44-47, and any of claims 48-54 One of the described client clients.

Images