Internet of Things management system and method

Abstract

The invention discloses an Internet of Things management system and method, and belongs to the technical field of Internet of Things. The Internet of Things management system comprises a device access layer used for respectively storing original data uploaded by a device group in a plurality of first-level message queues in the form of first messages; the analysis service layer is used for analyzing the first message according to the type of the Internet of Things equipment corresponding to each first message in each first-level message queue, and storing the analyzed first message in a second-level message queue corresponding to the type in the form of a second message; and the distribution application layer is used for distributing each second message in each second-level message queue to a target service system corresponding to the second message. According to the Internet of Things management system and method provided by the invention, through a multi-stage message queue cache mechanism, the data is subjected to peak clipping and decoupling based on the message queue at each stage, and the risk of system avalanche and data loss when the Internet of Things uploads a large number of data can be solved.

Description

Technical Field

[0001] The present application belongs to the technical field of Internet of Things, and in particular, relates to an Internet of Things management system and method. Background Art

[0002] The Internet of Things management system is used to distribute the data generated by multiple Internet of Things devices to the corresponding business system for processing. The existing Internet of Things management system generally includes an access unit cluster and a data forwarding cluster. The access unit cluster is used to receive the data generated by multiple Internet of Things devices. The data forwarding cluster is used to distribute the above data to the corresponding business system for processing. In the case of a large amount of data, the existing Internet of Things management system is prone to avalanche phenomenon and the risk of data loss, and the operation stability and data security are poor. Summary of the invention

[0003] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes an Internet of Things management system and method, which can improve the stability of operation and the security of data.

[0004] In a first aspect, the present application provides an Internet of Things management system, the system comprising:

[0005] The device access layer is used to store the original data uploaded by the device group in the form of a first message into a plurality of first-level message queues; the device group includes a plurality of IoT devices;

[0006] A parsing service layer, configured to parse the first message according to the type of the IoT device corresponding to each first message in each first-level message queue, and store the parsed first message in the form of a second message in a second-level message queue corresponding to the type;

[0007] The distribution application layer is used to distribute each of the second messages in each of the second-level message queues to a target business system corresponding to the second message.

[0008] According to the Internet of Things management system of the present application, through a multi-level message queue caching mechanism, data is peak-shaving and decoupled based on the message queue at each level. The next level will consume new messages in the previous level message queue only after processing the current message. This can solve the risk of system avalanche and data loss when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0009] According to one embodiment of the present application, the distribution application layer includes:

[0010] A data distribution module, used to determine the target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message;

[0011] a format conversion module, used to convert the second message into a data format corresponding to each of the target business systems, and store the third message in a third-level message queue corresponding to the target business system in the form of a third message;

[0012] The first message queue module is used to distribute the third message in each of the third-level message queues to the business system corresponding to the third-level message queue.

[0013] According to the Internet of Things management system of the present application, the original data generated by Internet of Things devices of different types and different data formats can be parsed, the data can be processed into a data format recognizable by the business system, and distributed to different business systems. It can be compatible with original data of different data formats uploaded by different types of Internet of Things devices, so that the business system can seamlessly connect different types of original data without format conversion, which can improve the efficiency of business system development and maintenance.

[0014] According to one embodiment of the present application, the distribution application layer includes:

[0015] A data distribution module, used to determine the target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message, and store the second message in a third-level message queue corresponding to the target business system;

[0016] The first message queue module is used to distribute the second message in each of the third-level message queues to the business system corresponding to the third-level message queue.

[0017] According to one embodiment of the present application, the Internet of Things management system further includes: a storage layer;

[0018] The device access layer is also used to send the original data to the storage layer for storage.

[0019] According to one embodiment of the present application, the device access layer includes:

[0020] The second message queue module is used to store the original data in the form of first messages in a balanced manner in the multiple first-level message queues.

[0021] According to one embodiment of the present application, the parsing service layer includes:

[0022] A data parsing module, configured to call a data parsing service corresponding to each first message in each first-level message queue according to the type of the IoT device corresponding to the type, and parse the first message;

[0023] The third message queue module is used to store the parsed first message in the form of a second message into a second-level message queue corresponding to the type.

[0024] In a second aspect, the present application provides an Internet of Things management method, the method comprising:

[0025] The original data uploaded by the device group is stored in a plurality of first-level message queues in the form of a first message; the device group includes a plurality of IoT devices;

[0026] Parse the first message according to the type of the IoT device corresponding to each first message in each first-level message queue, and store the parsed first message in the second-level message queue corresponding to the type in the form of a second message;

[0027] Distribute each of the second messages in each of the second-level message queues to a target business system corresponding to the second message.

[0028] According to the Internet of Things management method of the present application, through a multi-level message queue caching mechanism, data is peak-shaving and decoupled based on the message queue at each level. The next level will consume new messages in the previous level message queue only after processing the current message. This can solve the risk of system avalanche and data loss when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0029] According to an embodiment of the present application, the distributing each second message in each second-level message queue to a target business system corresponding to the second message includes:

[0030] Determining the target service system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message;

[0031] Converting the second message into a data format corresponding to each of the target business systems, and storing the third message in a third-level message queue corresponding to the target business system in the form of a third message;

[0032] The third message in each of the third-level message queues is distributed to the business system corresponding to the third-level message queue.

[0033] According to the Internet of Things management method of the present application, the original data generated by Internet of Things devices of different types and different data formats can be parsed, the data can be processed into a data format recognizable by the business system, and distributed to different business systems. It can be compatible with original data of different data formats uploaded by different types of Internet of Things devices, so that the business system can seamlessly connect different types of original data without format conversion, which can improve the efficiency of business system development and maintenance.

[0034] In a third aspect, the present application provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the Internet of Things management method as described in the first aspect above is implemented.

[0035] In a fourth aspect, the present application provides a non-transitory computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the Internet of Things management method as described in the first aspect above is implemented.

[0036] In a fifth aspect, the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the Internet of Things management method as described in the first aspect.

[0037] In a sixth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the Internet of Things management method as described in the first aspect above.

[0038] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0040] Figure 1 It is a structural diagram of the Internet of Things management system provided by an embodiment of the present application;

[0041] Figure 2 It is a structural diagram of the distribution application layer in the Internet of Things management system provided by the embodiment of the present application;

[0042] Figure 3 This is a schematic diagram of the structure of the device access layer of the Internet of Things management system provided by the embodiment of the present application;

[0043] Figure 4 It is a structural diagram of the parsing service layer of the Internet of Things management system provided in an embodiment of the present application;

[0044] Figure 5 It is a schematic diagram of the operation process of the Internet of Things management system provided by the embodiment of the present application;

[0045] Figure 6 It is a flowchart of the Internet of Things management method provided by the embodiment of the present application;

[0046] Figure 7It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0048] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0049] In the related technologies, in addition to being prone to avalanche phenomena and the risk of data loss, the IoT management system has poor operational stability and data security. In addition, the data formats uploaded by IoT devices of different device types are different, and the data formats received by different business systems are different. Each business system needs to convert the received data into a data format that it can process, which makes the development and update of the business system very complicated and inefficient.

[0050] The Internet of Things management system and method provided by the embodiments of the present application are described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0051] like Figure 1 As shown, the Internet of Things management system includes: a device access layer 110, a resolution service layer 120 and a distribution application layer 130.

[0052] The device access layer 110 is used to store the original data uploaded by the device group in the form of first messages in multiple first-level message queues; the device group includes multiple Internet of Things devices.

[0053] In actual execution, the device access layer 110 can receive the original data uploaded by the device group. The device group may include multiple IoT devices. Each IoT device can upload the original data generated by itself to the IoT management system. The device access layer 110 can use multiple message queues to store the above original data. According to the process of the IoT management system for processing the above original data, the message queue of the device access layer 110 is a first-level message queue. The first message in each first-level message queue can be used to store the original data uploaded by an IoT device at a certain time, thereby realizing the storage of the above original data in the form of a first message. The number of first-level message queues can be one or more.

[0054] In some embodiments, the device access layer 110 may use an MQ (Message Queue) cluster. The device access layer 110 may dynamically expand capacity according to the number of the IoT devices connected to the device access layer 110 and the amount of raw data uploaded by the device group, that is, dynamically increase the number of first-level message queues to enhance the robustness of the IoT management system.

[0055] The device access layer 110 uses a first-level message queue to ensure the upload of massive raw data from the device group, achieve soft landing of data, and reduce or even avoid data loss. It should be noted that reducing data loss can improve the robustness of the Internet of Things management system and reduce the misjudgment of the Internet of Things management system on the available status of the Internet of Things devices.

[0056] Furthermore, the device access layer 110 uses the first-level message queue, which can also realize peak shaving and decoupling of the massive requests from the device group to avoid the avalanche phenomenon of the device access layer 110. The massive requests may include requests from each IoT device for uploading raw data. It is understandable that the number of requests from each IoT device may be one or more.

[0057] The parsing service layer 120 is used to parse the first message according to the type of the IoT device corresponding to each first message in each first-level message queue, and store the parsed first message in the second-level message queue corresponding to the type in the form of a second message.

[0058] In actual execution, the parsing service layer 120 can consume the first-level messages in the first-level message queue according to its own message consumption capability. The parsing service layer 120 consumes each first message in the first-level message queue, which may include parsing the first message according to the type of IoT device corresponding to the first message, and extracting the target data therein for the business system to process.

[0059] The IoT device corresponding to the first message is the IoT device that uploaded the original data stored in the first message. The data format of the original data uploaded by each type of IoT device may be different. Through parsing, support for original data of different formats uploaded by different types of IoT devices can be achieved.

[0060] The parsing service layer 120 may use multiple message queues to store the target data. According to the process of the IoT management system for processing the raw data, the message queue of the parsing service layer 120 is a second-level message queue. The second message in each second-level message queue may be used to store the target data obtained after parsing the first message corresponding to a type of IoT device, thereby storing the parsed first message in the form of a second message. The number of second-level message queues may be one or more.

[0061] The parsing service layer 120 consumes the first message in the first-level message queue, and can also include: after the parsing service layer 120 parses the first message and obtains the target data, the target data can be stored in the target second-level message queue. The target second-level message queue is the second-level message queue corresponding to the IoT device corresponding to the first message.

[0062] In some embodiments, the second-level message queues may correspond to the types of IoT devices one by one, that is, the number of second-level message queues may be equal to the number of types of IoT devices. Alternatively, one type of IoT device may correspond to multiple second-level message queues.

[0063] In some embodiments, the resolution service layer 120 may also adopt an MQ cluster.

[0064] The resolution service layer 120 uses a second-level message queue to ensure that data will not be lost during the processing of the resolution service layer 120 .

[0065] It is understandable that the parsing service layer 120 consumes the new first message in the first-level message queue only after processing the current first message.

[0066] The distribution application layer 130 is used to distribute each second message in each second-level message queue to a target business system corresponding to the second message.

[0067] In actual execution, the distribution application layer 130 can consume the second message in the second-level message queue according to its own message consumption capability. The distribution application layer 130 consumes the second message in the second-level message queue, which may include, for each second message, distributing the second message to a target business system corresponding to the second message. The target business system may process the received second message.

[0068] The target business system corresponding to the second message can be determined according to the type of the IoT device corresponding to the second message. The type of the IoT device corresponding to the second message is the type of the IoT device corresponding to the first message corresponding to the second message. If the second message is obtained by parsing a first message, then the first message is the first message corresponding to the second message.

[0069] It is understandable that the distribution application layer 130 consumes the new second message in the second-level message queue only after processing the current second message.

[0070] It should be noted that, depending on the type of IoT device, the data generated by it needs to be distributed by the IoT management system to different business systems for processing. Therefore, the target business system corresponding to the second message can be determined based on the type of IoT device corresponding to the second message. In addition, one or more business systems that process the original data generated by a certain type of IoT device are the target business systems corresponding to the second message corresponding to the IoT device of that type. The specific functions of each business system are not limited in the embodiments of the present application.

[0071] According to the Internet of Things management system provided in the embodiment of the present application, through a multi-level message queue caching mechanism, data is peak-shaving and decoupled based on the message queue at each level. The next level will consume new messages in the previous level message queue only after processing the current message. This can solve the risk of system avalanche and data loss when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0072] In some embodiments, Figure 2 As shown, the distribution application layer 130 includes: a data distribution module 131, a format conversion module 132 and a first message queue module 133.

[0073] The data distribution module 131 is used to determine the target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message.

[0074] In actual execution, the data distribution module 131 can consume the second message in the second-level message queue according to its own message consumption capability. The data distribution module 131 consumes the second message in the second-level message queue, which may include: for each second message, according to the type of the IoT device corresponding to the second message, determining the target business system corresponding to the second message;

[0075] The format conversion module 132 is used to convert the second message into a data format corresponding to each target business system, and store it in the third-level message queue corresponding to the target business system in the form of a third message.

[0076] In actual execution, after determining the target business system corresponding to the second message, the format conversion module 132 can convert the second message into a data format corresponding to each target business system to obtain one or more third messages; each third message is placed in a third-level message queue corresponding to the third message. The number of third-level message queues can be one or more. The data format corresponding to the target business system can be a data format recognizable by the target business system.

[0077] The third-level message queue can correspond to the business system one by one. There are multiple third-level message queues. If the data format of a third message is a data format that can be processed by a target business system, then the target business system is the third-level message queue corresponding to the third message.

[0078] The distribution application layer 130 may use multiple message queues to store the third message. According to the process of the Internet of Things management system processing the above raw data, the message queue of the distribution application layer 130 is a third-level message queue. The third message in each third-level message queue may be obtained by converting the second message into a data format corresponding to a target business system.

[0079] The first message queue module 133 is used to distribute the third message in each third-level message queue to the business system corresponding to the third-level message queue.

[0080] In actual implementation, the first message queue module 133 may adopt an MQ cluster. The first message queue module 133 may be used to maintain all third-level message queues.

[0081] In some embodiments, the third message is stored in the third-level message queue corresponding to each business system for consumption by the business system, thereby distributing the third message. Since the third message is obtained by format conversion of the second message, distributing the third message is equivalent to distributing the second message after format conversion.

[0082] It is understandable that each business system consumes the new third message in the third-level message queue only after processing the current third message.

[0083] According to the Internet of Things management system provided by the embodiment of the present application, the original data generated by Internet of Things devices of different types and different data formats can be parsed, the data can be processed into a data format recognizable by the business system, and distributed to different business systems. It can be compatible with the original data of different data formats uploaded by different types of Internet of Things devices, so that the business system can seamlessly connect different types of original data without format conversion, which can improve the efficiency of business system development and maintenance. In addition, through the multi-level message queue caching mechanism, the data is peak-cut and decoupled based on the message queue at each level. The next level will consume the new message in the previous level message queue only after processing the current message. This can solve the risk of avalanche and data loss in the system when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0084] In some embodiments, the distribution application layer 130 includes: a data distribution module 131 and a first message queue module 133 .

[0085] The data distribution module 131 is used to determine the target business system corresponding to the second message according to the type of the IoT device corresponding to the second message, and store the second message in the third-level message queue corresponding to the target business system;

[0086] The first message queue module 133 is used to distribute the second message in each third-level message queue to the business system corresponding to the third-level message queue.

[0087] In actual implementation, the distribution application layer 130 may not include the format conversion module 132, and the business system may perform data format conversion by itself as in the related art.

[0088] The distribution application layer 130 may use multiple message queues to store the second message. According to the process of the Internet of Things management system processing the above raw data, the message queue of the distribution application layer 130 is a third-level message queue. Each third-level message queue can store the second message.

[0089] After determining the target business system corresponding to the second message, the data distribution module 131 may store the second message in a third-level message queue corresponding to each target business system.

[0090] The first message queue module 133 may adopt an MQ cluster. The first message queue module 133 may be used to maintain all third-level message queues.

[0091] It is understandable that each business system consumes the new second message in the third-level message queue only after processing the current second message.

[0092] According to the Internet of Things management system provided in the embodiment of the present application, through a multi-level message queue caching mechanism, data is peak-shaving and decoupled based on the message queue at each level. The next level will consume new messages in the previous level message queue only after processing the current message. This can solve the risk of system avalanche and data loss when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0093] In some embodiments, the Internet of Things management system further includes: a storage layer; and a device access layer 110, which is also used to send original data to the storage layer for storage.

[0094] In actual implementation, the Internet of Things management system may further include a storage layer. The storage layer may be used to store the original data uploaded by the device group. After receiving the original data uploaded by the device group, the device access layer 110 may store the original data in the storage layer.

[0095] In some embodiments, the storage layer may use at least one of a relational database and a time series database to store the original data.

[0096] According to the Internet of Things management system provided in the embodiment of the present application, the original data is sent to the storage layer for storage through the device access layer, and a two-layer protection measure is taken for the security of the original data, namely, the message queue + storage layer, which can lay the foundation for subsequent tracing and investigation.

[0097] In some embodiments, Figure 3 As shown, the device access layer 110 includes: a second message queue module 111, which is used to store the original data in a balanced manner in a plurality of first-level message queues in the form of first messages.

[0098] In actual execution, the second message queue module 111 can determine the number of first-level message queues based on the number of the above-mentioned IoT devices that are communicatively connected to the device access layer 110 and the amount of original data uploaded by the device group, and put the original data into each first-level message queue in a preset order.

[0099] For example, when the first-level message queues are numbered 1 to 100, the 1st to 100th original data can be stored in the first-level message queues numbered 1 to 100 in sequence, and the 101st to 200th original data can also be stored in the first-level message queues numbered 1 to 100 in sequence, and so on.

[0100] In some embodiments, the second message queue module 111 may use an MQ cluster. The second message queue module 111 may be used to maintain all first-level message queues.

[0101] According to the Internet of Things management system provided by the embodiment of the present application, by storing the original data in the form of the first message in a balanced manner in multiple first-level message queues, the stability of the system operation can be improved. In addition, through the multi-level message queue caching mechanism, the data is peak-cut and decoupled based on the message queue at each level. The next level will consume the new message in the previous level message queue only after processing the current message. This can solve the risk of avalanche and data loss in the system when the Internet of Things uploads a large amount of data, and can improve the stability of the system operation and the security of the data.

[0102] In some embodiments, Figure 4 As shown, the parsing service layer 120 includes: a data parsing module 121 and a third message queue module 122 .

[0103] The data parsing module 121 is used to call a data parsing service corresponding to a type of IoT device corresponding to each first message in each first-level message queue to parse the first message.

[0104] In actual execution, the data parsing module 121 can consume the first-level messages in the first-level message queue according to its own message consumption capability. The data parsing module 121 consumes each first message in the first-level message queue, which may include calling the data parsing service corresponding to the type of IoT device corresponding to the first message, parsing the first message, and extracting the target data for the business system to process.

[0105] In some embodiments, parsing the first message may include parsing the first message according to an IoT protocol corresponding to the type of IoT device. It is understandable that different types of IoT devices may use different IoT protocols to transmit data, and thus the first message may be parsed according to the IoT protocol corresponding to the type of IoT device to extract the target data.

[0106] In some embodiments, the original data may be encrypted data, and parsing the first message may include decrypting the first message, etc.

[0107] The third message queue module 122 is used to store the parsed first message in the form of a second message into a second-level message queue corresponding to the type.

[0108] In actual implementation, the third message queue module 122 may adopt an MQ cluster. The third message queue module 122 may be used to maintain all second-level message queues.

[0109] The third message queue module 122 may encapsulate the target data into a second message and put it into a second-level message queue corresponding to the type.

[0110] According to the Internet of Things management system provided by the embodiment of the present application, by invoking the data parsing service corresponding to the type of the Internet of Things device corresponding to the first message and parsing the first message, it is possible to support the original data of different formats uploaded by different types of Internet of Things devices. In addition, through the multi-level message queue caching mechanism, the data is peak-cut and decoupled based on the message queue at each level. The next level will consume the new message in the previous level message queue only after processing the current message. This can solve the risk of system avalanche and data loss when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0111] The operation process of the Internet of Things management system provided by the above-mentioned embodiments of this application can be as follows: Figure 5 As shown. Figure 5 As shown, the device group may include P IoT devices, which are respectively recorded as IoT device 1, IoT device 2, ..., IoT device P. Wherein, P is a positive integer. The P IoT devices may upload raw data to the IoT management system.

[0112] After the device access layer 110 of the Internet of Things management system receives the above-mentioned original data, multiple message queues can be used to store the above-mentioned original data. The second message queue module 111 can use an MQ cluster to maintain M first-level message queues according to the number of Internet of Things devices connected to the device access layer 110 for communication (taking into account situations such as disconnection, it can be less than or equal to P) and the amount of original data uploaded by the device group. Among them, M is a positive integer. The M first-level message queues can be respectively recorded as MQ1-1, MQ1-2,..., MQ1-M. Each first-level message queue can contain at least one first message.

[0113] The data parsing module 121 of the parsing service layer 120 of the Internet of Things management system can pre-store Internet of Things protocols used by various types of Internet of Things devices, which are recorded as Internet of Things Protocol 1, Internet of Things Protocol 2, and Internet of Things Protocol 3, etc. The data parsing module 121 of the parsing service layer 120 can consume the first message in the first-level message queue, call the data parsing service corresponding to the type according to the type of Internet of Things device corresponding to the first message, and parse the first message based on the Internet of Things protocol used by the type of Internet of Things device (such as Internet of Things Protocol 2 or Internet of Things Protocol 3, etc.). The second message obtained by parsing the first message can be put into the second-level message queue. The second-level message queue can be called a parsing consumption queue.

[0114] The third message queue module 122 of the resolution service layer 120 can use an MQ cluster to maintain N second-level message queues. Wherein, N is a positive integer. The N second-level message queues can be respectively recorded as MQ2-1, MQ2-2, ..., MQ2-N. Each second-level message queue can contain at least one second message.

[0115] The data distribution module 131 of the distribution application layer 130 of the Internet of Things management system can consume the second message in the second-level message queue, and determine the target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message. The format conversion module 132 of the distribution application layer 130 is used to process the data, that is, process the second message, convert the second message into the data format corresponding to each target business system, and store it in the third-level message queue corresponding to the target business system in the form of a third message. The data format corresponding to the target business system is a format recognizable by the business system, so the target business system can identify the data in its corresponding data format and process it.

[0116] The first message queue module 133 of the distribution application layer 130 can use an MQ cluster to maintain L third-level message queues. Wherein, L is a positive integer. The L third-level message queues can be respectively recorded as MQ3-1, MQ3-2, ..., MQ3-L. Each second-level message queue can contain at least one third message. Since the third message is data for processing by the business system, the third-level message queue can be called a business data queue.

[0117] The business system side may include K business systems, which are respectively recorded as business system 1, business system 2, ..., physical business system K. Wherein, K is a positive integer. Any of the above K business systems can consume the third message in the third-level message queue corresponding to itself. It can be understood that the third message obtained by the distribution application layer 130 is a data format that can be recognized by the business system, so the above third message can be recognized, parsed and processed by the business system.

[0118] The embodiment of the present application also provides an Internet of Things management method based on any of the above-mentioned Internet of Things management systems.

[0119] Among them, the Internet of Things management method can be applied to a terminal, and can be specifically executed by hardware or software in the terminal.

[0120] The terminal includes, but is not limited to, a portable communication device such as a mobile phone or tablet computer with a touch-sensitive surface (e.g., a touch screen display and / or a touch pad). It should also be understood that in some embodiments, the terminal may not be a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., a touch screen display and / or a touch pad).

[0121] In the following various embodiments, a terminal including a display and a touch-sensitive surface is described. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, a mouse and a joystick.

[0122] The Internet of Things management method provided in the embodiment of the present application may be executed by an electronic device or a functional module or functional entity in the electronic device that can implement the Internet of Things management method. The electronic devices mentioned in the embodiment of the present application include but are not limited to mobile phones, tablet computers, computers, cameras, and wearable devices. The Internet of Things management method provided in the embodiment of the present application is described below using the electronic device as an example of the execution subject.

[0123] like Figure 6 As shown, the Internet of Things management method includes: step 610, step 620 and step 630.

[0124] Step 610: The original data uploaded by the device group is stored in a plurality of first-level message queues in the form of a first message; the device group includes a plurality of IoT devices.

[0125] In actual implementation, the device access layer 110 can receive the original data uploaded by the device group and use multiple message queues to store the original data. The message queue of the device access layer 110 is a first-level message queue. The first message in each first-level message queue can be used to store the original data uploaded by an IoT device at a certain time, thereby storing the original data in the form of the first message. The number of first-level message queues can be one or more.

[0126] Step 620: parse the first message according to the type of IoT device corresponding to each first message in each first-level message queue, and store the parsed first message in the second-level message queue corresponding to the type in the form of a second message.

[0127] In actual execution, the parsing service layer 120 can consume the first-level messages in the first-level message queue according to its own ability to consume messages. The parsing service layer 120 consumes each first message in the first-level message queue, which may include parsing the first message according to the type of IoT device corresponding to the first message, and extracting the target data for processing by the business system. After the parsing service layer 120 parses the first message and obtains the target data, it can store the target data in the target second-level message queue. The target second-level message queue is the second-level message queue corresponding to the IoT device corresponding to the first message.

[0128] Step 630: Distribute each second message in each second-level message queue to a target business system corresponding to the second message.

[0129] In actual execution, the distribution application layer 130 can consume the second message in the second-level message queue according to its own message consumption capability. The distribution application layer 130 consumes the second message in the second-level message queue, which may include, for each second message, distributing the second message to a target business system corresponding to the second message. The target business system may process the received second message.

[0130] The detailed implementation process of the above-mentioned Internet of Things management method can be found in any of the above-mentioned embodiments of the Internet of Things management system, which will not be repeated here.

[0131] According to the Internet of Things management method provided in the embodiment of the present application, through a multi-level message queue caching mechanism, data is peak-shaving and decoupled based on the message queue at each level. The next level will consume new messages in the previous level message queue only after processing the current message. This can solve the risk of system avalanche and data loss when the Internet of Things uploads a large amount of data, and can improve the stability of system operation and data security.

[0132] In some embodiments, distributing each second message in each second-level message queue to a target business system corresponding to the second message may include:

[0133] Determining a target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message;

[0134] Convert the second message into a data format corresponding to each target business system, and store it in a third-level message queue corresponding to the target business system in the form of a third message;

[0135] The third message in each third-level message queue is distributed to the business system corresponding to the third-level message queue.

[0136] In some embodiments, distributing each second message in each second-level message queue to a target business system corresponding to the second message may include:

[0137] A data distribution module, used to determine a target business system corresponding to the second message according to the type of the IoT device corresponding to the second message, and store the second message in a third-level message queue corresponding to the target business system;

[0138] The first message queue module is used to distribute the second message in each third-level message queue to the business system corresponding to the third-level message queue.

[0139] In some embodiments, the method may further include:

[0140] Send the original data to the storage layer for storage.

[0141] In some embodiments, storing the original data uploaded by the device group in the form of first messages in a plurality of first-level message queues may include:

[0142] The original data is evenly stored in a plurality of first-level message queues in the form of first messages.

[0143] In some embodiments, according to the type of IoT device corresponding to each first message in each first-level message queue, parsing the first message, and storing the parsed first message in the form of a second message in a second-level message queue corresponding to the type may include:

[0144] According to the type of the IoT device corresponding to each first message in each first-level message queue, calling the data parsing service corresponding to the type to parse the first message;

[0145] The parsed first message is stored in the second-level message queue corresponding to the type in the form of a second message.

[0146] The storage device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0147] The storage device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0148] The storage device provided in the embodiment of the present application can achieve Figure 6 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0149] In some embodiments, Figure 7 As shown, the embodiment of the present application also provides an electronic device 700, including a processor 710, a memory 720, and a computer program stored in the memory 720 and executable on the processor 710. When the program is executed by the processor 710, each process of the above-mentioned Internet of Things management method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0150] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0151] The embodiment of the present application also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned Internet of Things management method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0152] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0153] An embodiment of the present application also provides a computer program product, including a computer program, which implements the above-mentioned Internet of Things management method when executed by a processor.

[0154] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0155] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned Internet of Things management method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0156] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0157] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0158] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0159] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0160] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0161] Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present application, and that the scope of the present application is defined by the claims and their equivalents.

Claims

1. An Internet of Things management system, characterized in that: include: The device access layer is used to store the original data uploaded by the device group in the form of first messages into multiple first-level message queues respectively; The device group includes a plurality of IoT devices; A parsing service layer, configured to parse the first message according to the type of the IoT device corresponding to each first message in each first-level message queue, and store the parsed first message in the form of a second message in a second-level message queue corresponding to the type; The distribution application layer is used to distribute each of the second messages in each of the second-level message queues to a target business system corresponding to the second message.

2. The Internet of Things management system according to claim 1, characterized in that: The distribution application layer includes: A data distribution module, used to determine the target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message; a format conversion module, used to convert the second message into a data format corresponding to each of the target business systems, and store the third message in a third-level message queue corresponding to the target business system in the form of a third message; The first message queue module is used to distribute the third message in each of the third-level message queues to the business system corresponding to the third-level message queue.

3. The Internet of Things management system according to claim 1, characterized in that: The distribution application layer includes: A data distribution module, used to determine the target business system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message, and store the second message in a third-level message queue corresponding to the target business system; The first message queue module is used to distribute the second message in each of the third-level message queues to the business system corresponding to the third-level message queue.

4. The Internet of Things management system according to claim 1, characterized in that: Also includes: Storage layer; The device access layer is also used to send the original data to the storage layer for storage.

5. The Internet of Things management system according to claim 1, characterized in that: The device access layer includes: The second message queue module is used to store the original data in the form of first messages in a balanced manner in the multiple first-level message queues.

6. The Internet of Things management system according to any one of claims 1 to 5, characterized in that: The analysis service layer includes: A data parsing module, configured to call a data parsing service corresponding to each first message in each first-level message queue according to the type of the IoT device corresponding to the type, and parse the first message; The third message queue module is used to store the parsed first message in the form of a second message into a second-level message queue corresponding to the type.

7. A method for managing the Internet of Things, characterized in that: include: The original data uploaded by the device group is stored in a plurality of first-level message queues in the form of first messages; The device group includes a plurality of IoT devices; Parse the first message according to the type of the IoT device corresponding to each first message in each first-level message queue, and store the parsed first message in the second-level message queue corresponding to the type in the form of a second message; Distribute each of the second messages in each of the second-level message queues to a target business system corresponding to the second message.

8. The Internet of Things management method according to claim 7, characterized in that: The step of distributing each second message in each second-level message queue to a target business system corresponding to the second message includes: Determining the target service system corresponding to the second message according to the type of the Internet of Things device corresponding to the second message; Converting the second message into a data format corresponding to each of the target business systems, and storing the third message in a third-level message queue corresponding to the target business system in the form of a third message; The third message in each of the third-level message queues is distributed to the business system corresponding to the third-level message queue.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the Internet of Things management method as described in claim 7 or 8 is implemented.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the Internet of Things management method as claimed in claim 7 or 8 is implemented.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the Internet of Things management method as claimed in claim 7 or 8 is implemented.

Images