WO2011131066A1

WO2011131066A1 - Internet of things system and buffer control method thereof

Info

Publication number: WO2011131066A1
Application number: PCT/CN2011/071883
Authority: WO
Inventors: 宋亚宁
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-04-19
Filing date: 2011-03-16
Publication date: 2011-10-27
Also published as: CN102223681B; CN102223681A

Abstract

A method for controlling the buffer in the internet of things system is disclosed in the present invention. The method includes: the internet of things system creates a Machine-To-Machine (M2M) terminal message buffer queue, and adds the generated information of the M2M terminal message buffer queue in the buffer queue management information (100); according to the buffer queue management information, the system stores the message reported by the M2M terminal in the corresponding M2M terminal message buffer queue by the memory buffer mode and the file buffer mode, or extracts the message of the M2M terminal from the corresponding M2M terminal message buffer queue (200). Accordingly, the internet of things system is also disclosed in the present invention. The application of the present invention can provide the high efficiency and the unrestricted buffer space and also improve the memory utilization rate.

Description

IoT system and control method thereof in cache

The invention relates to the field of application of the Internet of Things, and particularly relates to an Internet of Things system and a control method thereof. Background technique

Today, with the rapid development of computer technology, the Internet of Things has become a direction of future Internet development. In M2M (Internet of Things) applications, M2M servers often connect tens of thousands of terminals at the same time. At the same time, there are a large number of messages requiring M2M. The server processes. At this time, the M2M server cannot process one message and receive the next message. This may cause the message to be lost or blocked. Therefore, the message needs to be received first, cached, and then processed from the cache.

In the traditional M2M server, the cache mode of the message is memory cache and file cache. The memory cache can be divided into a fixed-length memory space cache and a temporary allocated memory space cache according to the processing manner.

For a fixed-length memory space cache, the M2M server allocates a fixed-length cache at startup. After receiving various messages from the terminal, the M2M server directly puts the message into an idle location in the previously allocated cache. However, during the operation of the M2M server, two extreme situations may occur. When the message volume of the M2M terminal is small, most of the memory in the cache space on the M2M server is idle, which easily causes waste of physical memory; and when M2M When the amount of terminal messages is extremely large, there may be a problem that the buffer space is occupied and the message cannot be continuously cached;

For the mode of temporarily allocating the memory space cache, the M2M server does not allocate the cache space at the time of startup. When the interface layer of the M2M server receives the message of the M2M terminal, it temporarily operates. The system applies for the memory. After the application is successful, the message of the M2M terminal is stored in the memory space of the temporary application. When the M2M server processes the message reported by the M2M terminal, the corresponding memory space is released. The M2M server uses the M2M server to cache the memory space that can be avoided by the M2M terminal message. However, the M2M server performs the memory application and release operation of the operating system for each M2M terminal, which consumes more system resources. And the maximum cache size that the entire M2M server can use is also limited by the size of the physical memory;

For the pure file cache mode, the M2M server saves the message reported by the M2M terminal in a file for caching. In this method, the M2M server can save a large number of M2M terminal reporting messages. In theory, only the size of the hard disk of the host installed by the M2M server is limited, but the efficiency of the disk 10 is very low, which easily causes a large processing time of the M2M server to be used. Read and write disks, which will reduce the message processing performance of the M2M server.

It can be seen that there is a need for a new cache mode in the M2M system, which provides high efficiency and unlimited cache space while improving memory utilization without causing waste of physical memory space. Summary of the invention

The technical problem to be solved by the present invention is to provide an Internet of Things system and a cache control method thereof, which can provide high efficiency and unlimited cache space while improving memory utilization.

In order to solve the above problem, an embodiment of the present invention provides a method for controlling a cache in an Internet of Things system, including:

The system creates an IoT M2M terminal message cache queue, and adds the generated information of the M2M terminal message cache queue to the cache queue management information;

According to the cache queue management information, the system stores the message on the M2M terminal in the corresponding M2M terminal message cache queue through the memory cache mode and the file cache mode, or caches the message of the M2M terminal from the corresponding M2M terminal message. Take it out of the queue. Preferably, the method may further include: the system creating an M2M terminal message buffer queue, and adding the generated information of the M2M terminal message buffer queue to the cache queue management information, including the following steps:

The system initiates a request to create an M2M terminal message cache queue, which includes an M2M terminal message cache queue id;

If the system determines that the M2M terminal message cache queue id does not exist, it scans whether there is already a cache file of the M2M terminal message cache queue id, and if so, obtains a start and end number of the cache file, and generates a newly created M2M. The information of the terminal message cache queue, which fills in the start and end numbers of the cache file;

The system adds the newly created information of the M2M terminal message cache queue to the cache queue management information.

Preferably, the method may further include: the system, according to the cache queue management information, storing the message reported by the M2M terminal in the corresponding M2M terminal message cache queue by using the memory cache mode and the file cache manner, including the following steps:

The system receives the message reported by the M2M terminal, determines that the M2M terminal message cache queue to be inserted is legal, and determines whether the cache file exists in the M2M terminal message cache queue. If yes, step a2 is performed; otherwise, step a1 is performed;

Step a, the system determines whether there is a free memory block in the M2M terminal message cache queue, if yes, step a3 is performed; otherwise, step a4 is performed;

Step a2, the system determines, according to the cache queue management information, whether the current cache file needs to create a new cache file, and if so, generates a new cache file according to the cache queue management information, and the M2M terminal is used. The message is written to the free space header of the generated new cache file, and the process is exited; otherwise, the message on the M2M terminal is written into the free space header of the cache file, and the process is exited;

Step a3: The system copies the message reported by the M2M terminal to the memory block team End save, exit process;

Step a4: The system determines, according to the cache queue management information, whether the M2M terminal message cache queue can create a new memory block. If yes, apply for a memory block, add the memory address to the cache queue management information, and The message reported by the M2M terminal is copied to the memory block for saving, and the process is exited; otherwise, step a2 is performed.

Preferably, the method may further include: the system, according to the cache queue management information, extracting, by using an in-memory cache mode and a file cache manner, the message of the M2M terminal from the corresponding M2M terminal message cache queue, including the following steps:

If the system determines that the M2M terminal message cache queue to be extracted is legal, step b0 is performed;

Step b0, the system determines whether there is a cache of the memory block in the current M2M terminal message cache queue, and if yes, step b3 is performed; otherwise, step bl is performed;

Step bl, the system determines whether the cache file exists in the M2M terminal message cache queue, and if yes, executes step b2, otherwise exits the process;

Step b2: The system opens a cache file with the smallest file number, reads the cache file content, and copies the cache file content into the first memory block of the M2M terminal message cache queue;

Step b3: The system extracts the message of the M2M terminal from the memory block, and determines whether the message of the extracted M2M terminal reaches the preset number of messages of the M2M terminal, and if yes, exits the process, otherwise determines the M2M terminal message cache. Whether there is no message in the queue, if yes, exit the process, otherwise go to step b0.

Preferably, the foregoing method may further include: the cache queue management information, including: M2M cache configuration information of the M2M system application, information of all M2M terminal message cache queues being used in the M2M system, and first M2M message cache queue list first address Information; where M2M cache configuration information includes the maximum allowable memory usage of all cache queues, the maximum record per queue The number of bars, the number of memory blocks allowed by the same type of cache, the memory block release rules, and the cache file save path information.

The embodiment of the present invention further provides an Internet of Things system, including: creating a management information module, a message storage module, and a message extraction module, where

The creating a management information module is configured to create an IoT M2M terminal message cache queue, and add the generated information of the M2M terminal message cache queue to the cache queue management information, and send the information to the message storage module and the Message extraction module

The message storage module is configured to store the message on the M2M terminal into the corresponding M2M terminal message cache queue according to the received cache queue management information by using a cache mode and a file cache mode;

The message extraction module is configured to: according to the received cache queue management information, the M2M terminal message is taken out from the corresponding M2M terminal message cache queue by using a cache mode and a file cache mode.

Preferably, the system may further include: creating a management information module to create an M2M terminal message cache queue, and adding the generated information of the M2M terminal message cache queue to the cache queue management information, specifically:

The create and generate management information module initiates a request to create an M2M terminal message cache queue, which includes an M2M terminal message cache queue id; and determines whether the M2M terminal message cache queue id does not exist, and then scans whether the M2M terminal message cache queue id is already present. The cache file, if any, obtains the start and end numbers of the cache file, generates the newly created information of the M2M terminal message cache queue, and fills in the start and end numbers of the cache file; the newly created M2M terminal message cache The information of the queue is added to the cache queue management information.

Preferably, the system may further include: the message storage module, according to the received cache queue management information, storing the message on the M2M terminal into the corresponding M2M terminal message cache queue by using a memory cache mode and a file cache manner, specifically Means: The message storage module receives the message on the M2M terminal, and determines that the M2M terminal message cache queue to be inserted is legal, if it is determined that the cache file exists in the M2M terminal message cache queue, the current cache is determined according to the cache queue management information. Whether the file needs to create a new cache file, if yes, generate a new cache file according to the cache queue management information, and write the message reported by the M2M terminal to the free space header of the generated new cache file. Otherwise, the message reported by the M2M terminal is written to the free space header of the cache file;

Determining, if there is no cache file in the M2M terminal message cache queue, determining whether there is a free memory block in the M2M terminal message cache queue, and if yes, copying the message reported by the M2M terminal to the end of the memory block If the cache queue management information is used, it is determined whether the M2M terminal message cache queue can create a new memory block. If yes, apply for a memory block, add the memory address to the cache queue management information, and report the M2M terminal. The message is copied to the memory block and saved.

Preferably, the system may further include: the message extraction module, according to the received cache queue management information, the M2M terminal message is taken out from the corresponding M2M terminal message cache queue by using a memory cache mode and a file cache mode, specifically Means:

If the message extraction module determines that the M2M terminal message cache queue to be extracted is legal, it determines that the extracted current M2M terminal message cache queue has a memory block cache, and then extracts the M2M terminal message from the memory block to determine the extracted M2M. If the message of the terminal has reached the preset number of messages of the M2M terminal, exit, otherwise, if the M2M terminal message cache queue has no message, exit;

Determining, if there is no cache of the memory block in the current M2M terminal message cache queue, determining that the cache file exists in the M2M terminal message cache queue, opening a cache file with the smallest file number, reading the cache file content, and copying The content of the cache file is sent to the first memory block of the M2M terminal message cache queue. The message of the M2M terminal is extracted from the memory block, and the number of messages of the M2M terminal that has been reached by the preset M2M terminal is determined. Retreat If yes, it is judged that if there is no message in the M2M terminal message buffer queue, it will exit.

Preferably, the system may further include: the cache queue management information in the creating and generating management information module, including: M2M cache configuration information of the M2M system application, information of all M2M terminal message cache queues being used in the M2M system, and All M2M message cache queue list first address information; wherein, M2M cache configuration information includes the maximum allowable memory size of all cache queues, the maximum number of records per queue, the number of memory blocks allowed by the same type of cache, the memory block release rules, and the cache. File save path information.

Compared with the prior art, the embodiment of the present invention combines the memory and the file storage cache in two ways, and uses the memory block as a basic unit to apply and release the memory, and on the one hand, provides the high-speed access capability of the memory, and It avoids the system consumption caused by frequent memory application and release, and uses the file as an extended storage method, so that the method can theoretically save unlimited messages interacting with the M2M terminal, and the storage capacity is only related to the size of the physical hard disk. It provides high efficiency and unlimited cache space while improving memory utilization without wasting physical memory space. . DRAWINGS

1 is a schematic diagram of a storage location cached in an M2M system according to an embodiment of the present invention; FIG. 2 is a flowchart of a method for controlling a cache in an Internet of Things system according to an embodiment of the present invention; Figure 2 is a flow chart of the M2M terminal message buffer queue; Figure 4 is a flowchart of the M2M terminal message entering the queue in the embodiment of the present invention;

5 is a flowchart of a M2M terminal message out queue in the embodiment of the present invention;

FIG. 6 is a schematic structural diagram of an Internet of Things system according to an embodiment of the present invention. detailed description

The invention is further described below in conjunction with the drawings and specific embodiments.

In the Internet of Things system of the embodiment of the present invention, multiple M2M terminal message buffer queues are allowed to be established. The information of all M2M terminal message buffer queues is managed by a doubly linked list. Each queue corresponds to a M2M terminal reporting message. Each queue can store M2M terminal reporting messages by using memory + file. The system uses memory blocks as memory. The unit manages, and the application and release of the memory are all in a single memory block, which effectively improves the memory utilization; the size of the cache file is consistent with the size of the memory block, and when the message needs to be obtained from the file, the entire file is mapped. When it is processed into memory, when the message in the file is obtained again in the future, it is processed from the memory, and the cache file is no longer operated, thereby improving the access efficiency. The system designs the cache file size and the memory block size to be consistent, which can effectively improve the mapping copy from file to memory. When the M2M cache file needs to be copied to the M2M cache memory block, only one binary read of the file is required. Take, and then copy to the memory block, improve the file-to-memory content replication efficiency; the file naming rules in the system is through the M2M message cache queue id file number, the file number is accumulated from 0, thus ensuring the system to the file Save in FIFO order.

The cache queue management information includes: M2M cache configuration information of the M2M system application, information of all M2M terminal message cache queues used in the M2M system, and first M2M message cache queue list first address information. The M2M cache configuration information includes the maximum allowed memory size of all cache queues, the maximum number of records per queue, the number of memory blocks allowed by the same type of cache, the memory block release rule, and the cache file save path information. The above information is set when the system is initialized.

The process of creating an M2M terminal message buffer queue mainly includes setting configuration information of the following queues: M2M terminal message queue id, single message length in the M2M terminal message queue, and M2M terminal message memory usage related information, that is, the maximum useable How many M2M servers cache memory blocks, M2M terminal message files use related information, that is, the start number of the file, the pointer of the M2M terminal message, the pointer of the current queue before and after the queue, and so on. Each message in a single queue of M2M terminal messages is stored at a fixed length. Each queue can contain a memory cache of 1 to N memory blocks and a file cache of unlimited files. Caching, queues, memory, The relationship between the memory block and the file can be as shown in Figure 1. There is a cache module in the M2M server. There can be multiple cache queues in one cache module. Each cache queue stores M2M in memory cache mode + file cache mode. The message reported by the terminal, wherein the memory portion is managed in blocks.

The message in-cache queue processing flow controls the M2M server interface layer to store the message received from the M2M terminal in the corresponding M2M terminal message queue, and selects the queue id corresponding to the M2M terminal reporting message, according to the cache queue management information, The message reported by the M2M terminal is inserted into the memory of the corresponding queue or the end of the file cache, which involves operations such as requesting a memory block and generating a cache file.

The message out cache queue processing flow controls the M2M server message processing application to take the message out of the M2M terminal message queue of the system, select the queue id corresponding to the M2M terminal report message, and according to the cache queue management information, from the currently operating The memory block front end of the M2M terminal message queue takes out the message and returns it to the M2M server message processing application. The message out cache queue processing process involves operations such as copying the cache file of the M2M terminal message queue to the cache memory block and releasing the memory block in the system.

FIG. 2 is a schematic flowchart of a method for controlling a cache in an Internet of Things system according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps:

Step 100: The IoT system creates a M2M terminal message cache queue, and adds the generated information of the M2M terminal message cache queue to the cache queue management information.

FIG. 3 is a flowchart of creating a M2M terminal message cache queue according to an embodiment of the present invention. As shown in FIG. 3, creating a M2M terminal message cache queue specifically includes the following steps:

Step 301: The system initiates an M2M terminal message cache queue request by using an interface layer application, where the M2M terminal message cache queue id is included;

Step 302, the system determines whether the M2M terminal message cache queue id exists, and if so, the process ends; otherwise, step 303 is performed; Step 303: Scan whether there is already a cache file of the M2M terminal message cache queue id, and if yes, obtain the start and end numbers of the cache file, and generate information of the newly created M2M terminal message cache queue, where the cache file is filled. Start and end numbers;

Step 304: The system adds the newly added information of the M2M terminal message cache queue to the cache queue management information.

The system adds the newly added information of the M2M terminal message cache queue to the M2M terminal message buffer queue doubly linked list in the cache queue management information.

Step 200: The system stores the message on the M2M terminal in the corresponding M2M terminal message cache queue, or the M2M terminal message from the corresponding M2M terminal message, according to the cache queue management information, by using the memory cache mode and the file cache mode. Take it out of the cache queue.

As shown in FIG. 4, the system saves the message of the M2M terminal to the corresponding M2M terminal message cache queue by using the memory cache mode and the file cache mode according to the cache queue management information, and specifically includes the following steps:

Step 400: The system receives the message reported by the M2M terminal, determines that the M2M terminal message cache queue to be inserted is legal, and further determines whether the cache file exists in the M2M terminal message cache queue. If yes, step 402 is performed; Step 401;

Step 401: The system determines whether there is a free memory block in the M2M terminal message cache queue, if yes, step 403 is performed; otherwise, step 404 is performed;

Step 402: The system determines, according to the cache queue management information, whether a current cache file needs to create a new cache file, and if yes, generates a new cache file according to the cache queue management information, where the M2M terminal is The message is written to the free space header of the generated new cache file, and the process is exited; otherwise, the message on the M2M terminal is written into the free space header of the cache file, and the process is exited;

Step 403: The system copies the message reported by the M2M terminal to the end of the memory block, and exits the process. Step 404: The system determines, according to the cache queue management information, whether the M2M terminal message cache queue is a new memory block. If yes, apply for a memory block, and add the memory address to the cache queue management information in the M2M terminal message cache. Queue the doubly linked list, and copy the message reported by the M2M terminal to the memory block to save, and exit the process; otherwise, go to step 402.

As shown in FIG. 5, the process of taking the M2M terminal message from the corresponding M2M terminal message cache queue by using the memory cache mode and the file cache mode according to the cache queue management information includes the following steps:

Step 500: If the system determines that the M2M terminal message cache queue to be extracted is legal, step 501 is performed;

Step 501: The system determines whether there is a cache of a memory block in the current M2M terminal message cache queue, and if yes, step 504 is performed, otherwise step 502 is performed;

Step 502: The system determines whether the cache file exists in the M2M terminal message cache queue. If yes, step 503 is performed; otherwise, the process is exited;

Step 503: The system opens a cache file with the smallest file number in a binary manner, reads the cache file content, and copies the cache file content into the first memory block of the M2M terminal message cache queue.

Step 504: The system extracts the message of the M2M terminal from the memory block, and determines whether the message of the extracted M2M terminal reaches the preset number of M2M terminal messages, and if yes, exits the process, otherwise step 505 is performed;

Step 505: The system determines whether there is no message in the M2M terminal message buffer queue. If yes, the process is exited. Otherwise, step 501 is performed.

6 is a schematic structural diagram of an Internet of Things system according to an embodiment of the present invention. As shown in FIG. 6, an Internet of Things system includes: creating a generation management information module, a message storage module, and a message extraction module, where

The creating a management information module is used to create an Internet of Things M2M terminal message cache team Columns, and the information of the generated M2M terminal message buffer queue is added to the cache queue management information, and sent to the message storage module and the message extraction module;

The creating a management information module creates an M2M terminal message cache queue, and adds the generated information of the M2M terminal message cache queue to the cache queue management information, specifically: the creating and generating a management information module initiates a creation of an M2M terminal. a message cache queue request, which includes an M2M terminal message cache queue id; determining that the M2M terminal message cache queue id does not exist, then scanning whether the M2M terminal message cache queue id cache file exists, and if so, acquiring the cache file The start and end numbers are generated, and the newly created information of the M2M terminal message cache queue is filled in, and the start and end numbers of the cache file are filled in; the newly added information of the M2M terminal message cache queue is added to the cache queue management information.

The message storage module stores the message on the M2M terminal in the corresponding M2M terminal message cache queue according to the received cache queue management information, by means of a memory cache mode and a file cache mode, specifically:

The message storage module receives the message on the M2M terminal, and determines that the M2M terminal message cache queue to be inserted is legal, if it is determined that the cache file exists in the M2M terminal message cache queue, the current cache is determined according to the cache queue management information. Whether the file needs to create a new cache file, if yes, generate a new cache file according to the cache queue management information, and write the message reported by the M2M terminal to the free space header of the generated new cache file. Otherwise, the message reported by the M2M terminal is written to the free space header of the cache file; Determining, if there is no cache file in the M2M terminal message cache queue, determining whether there is a free memory block in the M2M terminal message cache queue, and if yes, copying the message reported by the M2M terminal to the end of the memory block If the M2M terminal message cache queue is newly created, the memory module is requested to be added to the cache queue management information, and the memory address is added to the cache queue management information, and the M2M terminal is reported. The message is copied to the memory block and saved.

The message extraction module extracts the message of the M2M terminal from the corresponding M2M terminal message cache queue according to the received cache queue management information by using the memory cache mode and the file cache mode, which specifically refers to:

Determining, if there is no cache of the memory block in the current M2M terminal message cache queue, determining that the cache file exists in the M2M terminal message cache queue, opening a cache file with the smallest file number, reading the cache file content, and copying The content of the cache file is sent to the first memory block of the M2M terminal message cache queue. The message of the M2M terminal is extracted from the memory block, and the number of messages of the M2M terminal that has been reached by the preset M2M terminal is determined. , then exit, otherwise it is judged that if there is no message in the M2M terminal message buffer queue, it will exit.

The cache queue management information in the creation and management information module includes: M2M cache configuration information of the M2M system application, information of all M2M terminal message cache queues used in the M2M system, and first address information of all M2M message cache queue list entries. The M2M cache configuration information includes the maximum allowed memory size of all cache queues, the maximum number of records per queue, the number of memory blocks allowed by the same type of cache, the memory block release rules, and the cache file save. Path information.

The cache method for processing massive messages in an M2M server application according to an embodiment of the present invention combines two methods of memory and file storage cache, and uses a memory block as a basic unit for memory application and release, which is provided on the one hand The high-speed access capability of memory avoids the system consumption caused by frequent memory application and release. In addition, the file is used as an extended storage method, so that the method can theoretically save unlimited messages interacting with the M2M terminal. The storage capacity is only related to the physical hard disk size.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope of the present invention. All should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Claim

A method for controlling a cache in an Internet of Things system, the method comprising: the Internet of Things system creates an Internet of Things M2M terminal message cache queue, and generates the generated

The information of the M2M terminal message buffer queue is added to the cache queue management information;

The system stores the message reported by the M2M terminal in the corresponding M2M terminal message buffer queue according to the cache queue management information, or the M2M terminal message cache queue from the corresponding M2M terminal message cache queue. Take out.

The control method according to claim 1, wherein the system creates an M2M terminal message buffer queue, and adds the generated information of the M2M terminal message buffer queue to the cache queue management information as:

The system determines that the M2M terminal message cache queue id does not exist, and scans whether there is already a cache file of the M2M terminal message cache queue id, and if the M2M terminal message cache queue id has a cache file, the start of the cache file is obtained. And ending the number, generating the newly created information of the M2M terminal message cache queue, and filling in the start and end numbers of the cache file; the system adds the newly added information of the M2M terminal message cache queue to the cache queue management information.

The control method according to claim 2, wherein the system stores the message on the M2M terminal into the corresponding M2M terminal message buffer queue by using the memory cache mode and the file cache mode according to the cache queue management information. For:

The system receives the message reported by the M2M terminal, determines that the M2M terminal message cache queue to be inserted is legal, and further determines whether the cache file exists in the M2M terminal message cache queue, and the cache file exists in the M2M terminal message cache queue. Then perform step a2; otherwise, perform step a1; Step a, the system determines whether there is a free memory block in the M2M terminal message buffer queue, and there is a free memory block in the M2M terminal message buffer queue, then step a3 is performed; otherwise, step a4 is performed;

Step a2: The system determines, according to the cache queue management information, whether the current cache file needs to create a new cache file, and the current cache file needs to create a new cache file, and generates a new cache file according to the cache queue management information. The message reported by the M2M terminal is written to the free space header of the generated new cache file, and the process is exited; otherwise, the message reported by the M2M terminal is written into the free space header of the cache file, and the process is exited. ;

Step a3: The system copies the message reported by the M2M terminal to the end of the memory block, and exits the process;

Step a4: The system determines, according to the cache queue management information, whether the M2M terminal message cache queue can create a new memory block, and the M2M terminal message cache queue can create a new memory block, and then apply for a memory block, and add the memory address to the The queue management information is cached, and the message reported by the M2M terminal is copied to the memory block to be saved, and the process is exited; otherwise, step a2 is performed.

The control method according to claim 2, wherein the system extracts the M2M terminal message from the corresponding M2M terminal message cache queue by using the memory cache mode and the file cache mode according to the cache queue management information. For:

The system determines that the M2M terminal message buffer queue to be extracted is legal, and then performs step b0;

Step b0: The system determines whether there is a cache of the memory block in the current M2M terminal message cache queue. If there is a memory block cache in the current M2M terminal message cache queue, step b3 is performed, otherwise step bl is performed;

Step bl, the system determines whether the cache file exists in the M2M terminal message cache queue. If yes, the M2M terminal message cache queue has a cache file, and step b2 is performed; otherwise, the process is exited; Step b2: The system opens a cache file with the smallest file number, reads the cache file content, and copies the cache file content into the first memory block of the M2M terminal message cache queue;

Step b3: The system extracts a message of the M2M terminal from the memory block, and determines whether the message of the extracted M2M terminal reaches the preset number of messages of the M2M terminal, and the message of the M2M terminal reaches the message of the preset M2M terminal. If the number is exceeded, the process is exited. Otherwise, it is further determined whether there is no message in the M2M terminal message buffer queue. If there is no message in the M2M terminal message buffer queue, the process is exited, otherwise step b0 is performed.

The control method according to any one of claims 1 to 4, wherein the cache queue management information comprises: M2M cache configuration information of an M2M system application, and all M2M terminal message cache queues being used in the M2M system. Information and the first address information of all M2M message cache queues; wherein the M2M cache configuration information includes the maximum allowed memory size of all cache queues, the maximum number of records per queue, the number of memory blocks allowed by the same type of cache, and the release of memory blocks. Rules and cache files save path information.

An Internet of Things system, the system comprising: creating a management information module, a message storage module, and a message extraction module, wherein

The message extraction module is configured to: according to the received cache queue management information, the M2M terminal message is taken out from the corresponding M2M terminal message cache queue by using an in-memory cache mode and a file cache manner.

The IoT system according to claim 6, wherein the creation and generation management information module creates an M2M terminal message buffer queue, and adds the generated information of the M2M terminal message buffer queue to the cache queue management information. For:

The object-to-network system of claim 7, wherein the message storage module stores the message on the M2M terminal through the memory buffer mode and the file cache mode according to the received cache queue management information. The corresponding M2M terminal message cache queue is:

The message storage module receives the message on the M2M terminal, and determines that the M2M terminal message cache queue to be inserted is legal, if it is determined that the cache file exists in the M2M terminal message cache queue, the current cache is determined according to the cache queue management information. Whether the file needs to create a new cache file, if yes, generate a new cache file according to the cache queue management information, and write the message reported by the M2M terminal to the free space header of the generated new cache file. Otherwise, the message reported by the M2M terminal is written to the free space header of the cache file;

9. The Internet of Things system of claim 7, wherein the message extraction module According to the received cache queue management information, through the memory cache mode and the file cache mode

The message of the M2M terminal is taken out from the corresponding M2M terminal message buffer queue as:

The IoT system according to any one of claims 6 to 9, wherein the cache queue management information in the create and generate management information module includes: M2M cache configuration information of the M2M system application, and all in the M2M system. The M2M terminal message cache queue information and the M2M message cache queue list first address information are used. The M2M cache configuration information includes the maximum allowable memory size of all cache queues, the maximum number of records per queue, and the same type of cache allowable. Number of memory blocks, memory block release rules, and cache file save path information.