KR101809365B1 - Message Fragmentation Method using a MQTT Protocol in M2M/IoT Platforms - Google Patents

Abstract

A message delivery method using an MQTT protocol is provided in an M2M / IoT system. In the message delivery method according to the embodiment of the present invention, a message according to a specific standard is fragmented and recorded in a payload of an MQTT publication message, and fragmentation information of the fragmented message is specified in a topic name of an MQTT publication message. This allows the client to refer to the fragmentation information specified in the topic name to facilitate the reassembly of the message contained in the payload of the MQTT message

Description

{Message Fragmentation Method using a MQTT Protocol in M2M / IoT Platform}

The present invention relates to a M2M / IoT (Machine to Machine / Internet of Things) technology, and more particularly, to a method for transmitting a message using a Message Queue Telemetry Transport (MQTT) protocol in an M2M / IoT platform.

There is a need to utilize the MQTT protocol to convey M2M messages on the M2M platform.

The Message Queue Telemetry Transport (MQTT) protocol uses a publish-subscribe model for message delivery, and a broker relays messages for end-to-end data delivery. FIG. 1 shows a message transmission scheme according to the MQTT protocol.

In the MQTT protocol, all clients must be connected to the broker, which then subscribes with the topic name.

The topic name is used by the broker to forward published messages, which the broker delivers to a terminal subscribed to a topic in the published message.

On the other hand, M2M clients can also use the MQTT protocol to send data, and send a topic name explicitly when sending a message. The broker then sends the message to the client that matches the topic name and the client receives the message.

FIG. 2 shows the MQTT message format, and FIG. 3 shows the MQTT topic name format. As shown in FIG. 3, the MQTT topic name is hierarchically structured, and each hierarchy is divided into '/'.

In order for the M2M client to send data, the payload of the MQTT message contains M2M data. Theoretically, the MQTT payload supports 256MB.

However, in the IoT environment, sending a large amount of data at a time causes a situation in which a large amount of data is retransmitted when an error occurs in a transmission data packet or a data transmission failure occurs in a lossy network environment.

Therefore, sending a large amount of data at once is pointed out in an inefficient way, and a search for a method for reducing the payload size to be transmitted at once is requested.

SUMMARY OF THE INVENTION The present invention has been conceived to solve the above problems, and it is an object of the present invention to provide an MQTT message fragmentation method, an MQTT message fragmentation method, an MQTT message fragmentation method, And to issue an MQTT message.

According to an aspect of the present invention, there is provided a message delivery method including fragmenting a message according to a specific standard and storing it in a payload of a Message Queue Telemetry Transport (MQTT) issue message; And specifying fragmentation information of the fragmented message in the topic name of the MQTT issue message.

The fragmentation information may include a fragmentation number and an entire fragmentation number of the MQTT release message.

In addition, the topic name may include at least one of a parameter for specifying the specific standard, a parameter for specifying a request or a response, a parameter for specifying a sender and a parameter for specifying a receiver, and a data type of a message have.

The fragmentation information may be specified after the data type.

Further, in order to receive the MQTT issue message in which the data type is specified in the topic name, the data type may be specified using a wildcard in the topic name included in the MQTT subscription message.

And recording a parameter specifying a data type in a payload of the MQTT subscription message in order to specify a data type to be recorded in a payload of the MQTT message to be subscribed.

In addition, the specific standard may be an M2M related standard.

According to another aspect of the present invention, there is provided a message processing method comprising: receiving MQTT release messages fragmented in a payload according to a predetermined standard; And reassembling the MQTT release messages with reference to the fragmentation information specified in the topic name of the received MQTT release messages.

As described above, according to the embodiments of the present invention, the MQTT message is issued by specifying the fragmentation information of the message included in the payload in the topic name of the MQTT message, so that the client refers to the fragmentation information specified in the topic name, The reassembly of the messages stored in the payload of the mobile terminal can be facilitated.

1 is a diagram illustrating a message delivery method according to an MQTT protocol,
Figure 2 shows the MQTT message format,
Figure 3 shows the MQTT topic name format,
FIG. 4 is a diagram illustrating a message delivery method using an MQTT protocol in an M2M / IoT system; FIG.
5 illustrates a technique of fragmenting data of an M2M message into a plurality of MQTT messages,
FIG. 6 is a view showing a fragmented information providing / explaining method of specifying / providing fragmentation information using an MQTT topic name;
7 is a diagram illustrating a topic name included in an MQTT subscription request message,
8 is a detailed block diagram of a client (issuer) device.

Hereinafter, the present invention will be described in detail with reference to the drawings.

FIG. 4 is a diagram illustrating a method of transmitting a message using an MQTT (Message Queue Telemetry Transport) protocol in an M2M / IoT (Machine to Machine / Internet of Things) system.

4, when the client (subscriber) 300 subscribes to the broker 200, the MQTT issuance message of the client (issuer) 100 is relayed to the broker 200 To the client (subscriber)

A message according to the M2M standard (hereinafter abbreviated as 'M2M message') can be recorded in the payload of the MQTT issue message. When the size of the M2M message is large, the message is fragmented into a plurality of messages, Lt; RTI ID = 0.0 > MQTT < / RTI >

FIG. 5 illustrates a technique of fragmenting a plurality of pieces of data of an M2M message into a plurality of MQTT messages. In FIG. 5, one M2M message is fragmented into 9 pieces and recorded in 9 MQTT messages, which is merely an example. There is no restriction on the number of fragmentation.

Fragmentation information is necessary for the client (subscriber) 300, which is the receiving end, to reconstruct the M2M message by recombining a plurality of fragmented MQTT release messages. Here, the fragmentation information is information indicating how many pieces of data included in the payload of the MQTT issue message are fragmented from the M2M message.

In the embodiment of the present invention, fragmentation information is specified / provided by using the topic name included in the header of the MQTT message, which will be described in detail below.

FIG. 6 is a diagram provided for explaining a method of specifying / providing fragmentation information using an MQTT topic name; FIG. Quot ;, " 1/9 ", " 2/9 ", "3/9 "," 4/9 ", etc. recorded in the rear portion of the topic name, specifically, "1/10", "2/10", "3/10", and "4/10" are fragmentation information.

6, " oneM2M "is a parameter specifying the standard specification of the original message," req "and" resp "are parameters specifying respective requests and responses, 'Xml' and 'json' are parameters specifying the data type of the message.

As shown in FIG. 6, the format of the fragmentation information is 'current fragmentation number' / 'total fragmentation number'. Accordingly,

1) "1/9" indicates that the message is the first message among 9 fragmented messages,

2) "2/9" indicates the second message among 9 fragmented messages,

3) "3/9" indicates the third message among the nine fragmented messages,

4) "4/9" indicates the fourth message among 9 fragmented messages.

As described above, the client (issuer) 100 issuing the MQTT message issues fragmentation information of the message included in the payload to the topic name included in the header of the MQTT message, and issues the MQTT message.

The client (subscriber) 300 receiving the MQTT issue message from the client (sender) 100 through the broker 200 grasps the fragmentation information of the message recorded in the payload through the topic name, .

On the other hand, the topic name of the MQTT message also specifies the data type (JSON, XML, etc.) of the message included in the payload. Therefore, the client (subscriber) 300 can recognize the encoding method of the message stored in the payload through the topic name, and can decode the message based on the encoding method.

The data type in the topic name may be optional. That is, even if the data type is not specified in the topic name, the technical idea of the present invention can be applied.

To subscribe to an MQTT publish message with a data type specified in the topic name, the client (subscriber) 300 can generate an MQTT subscription message using a wildcard "#" supported in the MQTT.

Specifically, the data type is specified as "#" in the topic name included in the MQTT subscription message. The topic name contained in the MQTT subscription message is illustrated in FIG. 7, which means that it is possible to receive an MQTT publish message with a data type specified in the topic name.

Further, the client (subscriber) 300 can use the wildcard "#" supported in the MQTT to subscribe to the MQTT issue message in which the data type and / or fragmentation information is specified in the topic name, Message can be generated.

The format of the MQTT subscription message for this purpose can also be implemented as illustrated in FIG.

8 is a detailed block diagram of the client (issuer) 100 device. 8, the client (issuer) 100 includes a communication unit 110, a processor 120, and a storage unit 130. As shown in FIG.

The communication unit 110 establishes and maintains a communication connection with the broker 200. The processor 120 generates an MQTT issuance message and transmits the MQTT issuance message to the broker 200 through the communication unit 110. [

The storage unit 130 provides necessary storage space for the processor 120 to generate and send a message.

It is also possible to send an M2M message as an MQTT issue message. If the size of the M2M message is large, the processor 120 fragment it into a plurality of MQTT issue messages. At this time, the processor 120 specifies fragmentation information in the topic name.

Up to now, a preferred embodiment of a message delivery method using the MQTT protocol in the M2M / IoT system has been described in detail.

OneM2M mentioned in the above embodiment is referred to as a kind of M2M related standard. The method shown in the above embodiment may be applied to the case where a message for another type of M2M related standard is recorded in the MQTT issue message.

The xml and json referred to as data types in the above embodiment are merely illustrative. It goes without saying that the technical idea of the present invention can be applied to other types of data types.

The wildcard "#" used to designate the MQTT issue message with the data type specified in the topic name may be replaced with another wildcard, or may be replaced with another indicator.

It goes without saying that the technical idea of the present invention can also be applied to a computer-readable recording medium having a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical idea according to various embodiments of the present invention may be embodied in computer-readable code form recorded on a computer-readable recording medium. The computer-readable recording medium is any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like. In addition, the computer readable code or program stored in the computer readable recording medium may be transmitted through a network connected between the computers.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present invention.

100: Publisher (Publisher)
200: Broker
300: Subscriber

Claims (8)

Fragmenting a message according to a specific standard and storing it in a payload of a Message Queue Telemetry Transport (MQTT) issued message; And
And specifying fragmentation information of the fragmented message in a topic name of the MQTT issue message,
The topic name,
A parameter for specifying a specific standard, a parameter for specifying a request or a response, a parameter for specifying a sender and a parameter for specifying a receiver, and a data type of a message,
Wherein the fragmentation information comprises:
Specified after the data type,
Wherein the fragmentation information comprises:
The fragmentation number of the MQTT release message and the total fragmentation number,
The fragmentation number and the total fragmentation number of the MQTT-
A parameter for specifying a specific standard, a parameter for specifying a request or a response, a parameter for specifying a sender, a parameter for specifying a receiver, and a delimiter for identifying a data type of a message ≪ / RTI >
delete delete delete The method according to claim 1,
Specifying a data type in a topic name included in an MQTT subscription message using a wildcard to receive an MQTT issue message having a data type specified in the topic name.
The method according to claim 1,
Further comprising: storing a parameter specifying a data type in a payload of an MQTT subscription message to specify a data type to be recorded in a payload of an MQTT message to be subscribed.
The method according to claim 1,
The above-
M2M-related standard.
Receiving MQTT publish messages in a payload that are fragmented in accordance with a particular standard; And
And reconfiguring the MQTT issue messages with reference to the fragmentation information specified in the topic name of the received MQTT issue messages,
The topic name,
A parameter for specifying a specific standard, a parameter for specifying a request or a response, a parameter for specifying a sender and a parameter for specifying a receiver, and a data type of a message,
Wherein the fragmentation information comprises:
Specified after the data type,
Wherein the fragmentation information comprises:
The fragmentation number of the MQTT release message and the total fragmentation number,
The fragmentation number and the total fragmentation number of the MQTT-
A parameter for specifying a specific standard, a parameter for specifying a request or a response, a parameter for specifying a sender, a parameter for specifying a receiver, and a delimiter for identifying a data type of a message Gt;

Images