Cascade adaptation method and device of Internet of Things platform, medium and equipment

Abstract

The invention discloses a cascading adaptation method and device of an Internet of Things platform, a medium and equipment. The method comprises the following steps: adding a plurality of subordinate nodes into a node management range of the same superior node to obtain a platform cascade network corresponding to the superior node of a district-level node; after a superior node of the district-level node obtains the event data, performing data synchronization with a corresponding subordinate node of the district-level node in the district-level node platform cascade network according to a node attribute corresponding to the event data of the district-level node; and after the superior node of the district-level node approves the service scheduling application of one subordinate node of the district-level node, pushing the district-level node event data corresponding to the service scheduling application of the district-level node from the source node to the target node. Through the method, data adaptation and business adaptation among different levels of Internet of Things platforms can be realized, so that the data processing efficiency and the business response speed of the whole Internet of Things system are improved, and business and data linkage of each level under the urban Internet of Things system is realized.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a cascade adaptation method, device, medium and equipment for an Internet of Things platform. Background Art

[0002] As a key infrastructure for the construction of new smart cities, the metropolitan IoT platform carries the important task of integrating IoT sensing infrastructure and data resources at all levels of the city. This integration process aims to promote the sharing and use of sensing devices and data across the city, thereby meeting the business needs of new smart city construction in the fields of urban management, public safety, and public services.

[0003] Under the current division of urban management functions in my country, the municipal government is responsible for the overall construction of the city's IoT perception platform, while each district, county and municipal unit is responsible for the construction of perception platforms in their respective regions and industries. These platforms need to provide basic capabilities such as unified access adaptation, equipment management, object models, data sharing, and collaborative support, and realize the linkage between the municipal IoT platform in terms of business and data.

[0004] However, in actual applications, the IoT platforms of various districts, counties and municipal units often have problems such as inconsistent data standards, uneven data quality, poor real-time reporting, and poor linkage between IoT platforms. These problems have brought huge challenges to the interconnection and interoperability of cross-platform data. Although the current industry has provided a cloud gateway solution, which parses the device data transferred from the third-party platform by creating a cloud gateway, this solution still requires users to manually configure the data transfer method and perform data parsing according to the device type, data provider platform, etc., which undoubtedly increases the complexity of user operations.

[0005] In addition, the metropolitan IoT platform managed by the government also faces the problem of cross-departmental, cross-level, and cross-node hierarchical data control. For example, data control between municipal departments requires data isolation based on industry lines, and cross-unit data use requires configuration of data application and approval related processes; the district and county-level platform needs to manage the IoT sensing data within the district and county, and the linkage of upper and lower data needs to be divided based on administrative divisions; and some dynamic sensing devices, such as bus GPS (Global Positioning System) terminals, may have routes across multiple equal administrative divisions, so they need to be shared in multiple district and county-level platform nodes. These problems are beyond the scope of traditional cloud gateway solutions. Summary of the invention

[0006] This application mainly provides a cascade adaptation method, device, medium and equipment for an Internet of Things platform, aiming to solve the technical problem of the linkage of Internet of Things platforms at various levels under the existing urban Internet of Things system.

[0007] In order to solve the above technical problems, the technical solution adopted in this application is: to provide a cascade adaptation method for an Internet of Things platform. The cascade adaptation method of the Internet of Things platform includes: adding several subordinate nodes to the node management scope of the same superior node to obtain the platform cascade network corresponding to the superior node; after the superior node obtains the event data, according to the node attributes corresponding to the event data, data synchronization is performed with the corresponding subordinate nodes in the platform cascade network; after the superior node approves the business scheduling application of one of the subordinate nodes, the event data corresponding to the business scheduling application is pushed from the source node to the target node; wherein, the node attributes of the superior node include municipal nodes, the node attributes of the subordinate nodes include regional nodes and / or industry nodes, and the source node and the target node are different subordinate nodes across regions and / or industries.

[0008] In some embodiments, adding several subordinate nodes to the node management scope of the same superior node to obtain the platform cascade network corresponding to the superior node includes: configuring the node attributes of each of the subordinate nodes; registering the subordinate nodes to the superior node, and obtaining a list of cascade nodes within the node management scope of the superior node; adding the subordinate nodes to the cascade node list, and incorporating the subordinate nodes into the node management scope of the superior node, so that the superior node can update the node topology based on the node management scope to obtain the platform cascade network corresponding to the superior node.

[0009] In some embodiments, after adding several lower-level nodes to the node management scope of the same upper-level node to obtain the platform cascade network corresponding to the upper-level node, the method further includes:

[0010] After the subordinate node receives the quality coordination request initiated by the superior node and performs data rectification based on the quality coordination request, the rectification information of the subordinate node is fed back to the superior node so that the superior node can confirm the rectification result based on the rectification information.

[0011] In some embodiments, the quality collaborative request includes at least one of a collaborative request for data indicators, a collaborative request for reporting frequency indicators, a collaborative request for data content quality, a collaborative request for node online rate, and a collaborative request for node data sharing value.

[0012] In some embodiments, after the upper node obtains the event data, data synchronization is performed with the corresponding lower node in the platform cascade network according to the node attributes corresponding to the event data, including: when an event dispatching instruction triggered by the upper node is detected, or an event scheduling instruction triggered by the lower node is scheduled by the upper node, or an event reporting instruction triggered by the lower node is detected, the corresponding event data is obtained; determining that the node attribute corresponding to the event data is the municipal node, and synchronizing the event data to each of the lower nodes in the platform cascade network; determining that the node attribute corresponding to the event data is the regional node or the industry node, and synchronizing the event data to the upper node, so that the upper node can synchronize the event data to the corresponding lower node in the platform cascade network based on the target list corresponding to the event data.

[0013] In some embodiments, after the upper-level node acquires the event data, it performs data synchronization with the corresponding lower-level node in the platform cascade network according to the node attributes corresponding to the event data, and further includes: determining whether data information of the event data corresponding to the upper-level node and each lower-level node is consistent, wherein the data information includes at least one of a data start bit identifier, a data end bit identifier, a data size information, a data type information, and a record quantity information; confirming that the data information is consistent, and synchronizing event completion information to the corresponding upper-level node and the corresponding lower-level node in the platform cascade network.

[0014] In some embodiments, after the upper-level node approves the service scheduling application of one of the lower-level nodes, the event data corresponding to the service scheduling application is pushed from the source node to the target node, including: after the upper-level node receives the service scheduling application and the approval indication of the service scheduling application, determining the source node, the target node and the data list corresponding to the service scheduling application; determining that the upper-level node schedules the source node based on the data list and obtains the event data corresponding to the service scheduling application, and pushing the corresponding event data to the target node.

[0015] In order to solve the above technical problems, another technical solution adopted in the present application is: providing a storage medium on which program data is stored, characterized in that when the program data is executed by a processor, the steps of the cascade adaptation method of the Internet of Things platform as mentioned above are implemented.

[0016] In order to solve the above technical problems, another technical solution adopted in the present application is: to provide a computer device, which includes a processor and a memory connected to each other, the memory stores a computer program, and when the processor executes the computer program, it implements the steps of the cascade adaptation method of the Internet of Things platform as mentioned above.

[0017] The beneficial effects of the present application are as follows: Different from the prior art, the present application discloses a cascade adaptation method, device, medium and equipment for an Internet of Things platform. The present application includes subordinate nodes including regional nodes and industry nodes in the platform cascade network, and includes the management of superior nodes including municipal nodes. After acquiring event data, data synchronization is established between superior nodes and corresponding subordinate nodes. After the superior node approves the business application of the subordinate node, the relevant event data is pushed from the source node to the cross-regional or cross-industry target node, thereby realizing efficient interconnection and intercommunication of Internet of Things platform data across levels, departments and nodes, solving the problem of cross-platform data synchronization of device events between multiple Internet of Things platforms, and optimizing the shared business logic between municipal nodes and cross-regional and cross-industry nodes. On this basis, users only need to focus on the definition of their own levels and types, without the need to carry out related cross-platform data development and platform docking, which simplifies the process of data synchronization and business scheduling, reduces the complexity of operations, and realizes the linkage of various levels of business and data under the urban Internet of Things system. Through unified data standards and quality control, the real-time and accuracy of Internet of Things data are improved, which is conducive to improving the quality of perception data in various regions and industries, and promoting the data effectiveness of perception data in urban application fields. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0019] Figure 1 It is a flowchart of an embodiment of a cascade adaptation method of an Internet of Things platform provided by the present application;

[0020] Figure 2 yes Figure 1 A schematic flow chart of an embodiment of step 10 in the embodiment;

[0021] Figure 3 yes Figure 1 A schematic flow chart of an embodiment of step 20 in the embodiment;

[0022] Figure 4 yes Figure 1A schematic flow chart of an embodiment of step 30 in the embodiment.

[0023] Figure 5 It is a structural diagram of an embodiment of a cascade adapter device of an Internet of Things platform provided by the present application;

[0024] Figure 6 It is a structural schematic diagram of an embodiment of a storage medium provided by the present application;

[0025] Figure 7 It is a structural diagram of an embodiment of a computer device provided by the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] The terms "first", "second", "third" in the embodiments of the present application are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined as "first", "second", "third" can expressly or implicitly include at least one of the features. In the description of the present application, the meaning of "multiple" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.

[0028] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0029] This application provides a cascade adaptation method for an Internet of Things platform, see Figure 1 , Figure 1 1 is a flow chart of an embodiment of a cascade adaptation method of an Internet of Things platform provided by the present application. The cascade adaptation method of the Internet of Things platform includes:

[0030] Step 10: Add several subordinate nodes to the node management scope of the same superior node to obtain the platform cascade network corresponding to the superior node.

[0031] In this embodiment, the upper-level node is a node with a higher level and management functions, and can optionally perform data aggregation, processing, forwarding, storage, and network management and control, etc., while the lower-level node is a node at a lower level or managed by the upper-level node relative to the upper-level node, and can optionally perform data collection, preliminary processing and reporting.

[0032] In this embodiment, the upper-level nodes may include municipal nodes, while the lower-level nodes include regional nodes and industry nodes. The municipal nodes are responsible for coordinating the IoT perception platform of the entire city, the regional nodes are responsible for managing the IoT perception data within the region, and the industry nodes are responsible for managing the IoT perception data within a specific industry. Specifically, regional nodes and industry nodes have different processing methods for data cascading. Regional nodes automatically obtain the perception data belonging to the corresponding regional nodes in the nodes according to the administrative divisions of the corresponding regions. These perception data are mainly the perception device data built by the municipal units. These device data will eventually belong to a certain region according to the deployment location. Industry nodes are nodes built by industry departments such as transportation, water conservancy, meteorology, and fire protection. When performing specific business processing, it is usually necessary to share data from other industries or regions. It is necessary to apply for data in the platform and distribute data according to the nodes built by the applicant unit.

[0033] In this embodiment, the node management scope of the upper node refers to the set of lower-level nodes that the upper node can manage, including but not limited to directly connected nodes and nodes indirectly connected through other lower-level nodes. In actual operation, the upper node manages all nodes within its node management scope through the network topology structure to ensure efficient execution of data synchronization and business scheduling. Therefore, adding several lower-level nodes to the node management scope of the same upper node can update the network topology structure corresponding to the upper node accordingly, so that the upper node can manage all nodes within its node management scope through the platform cascade network of the network topology structure, ensuring efficient execution of subsequent data adaptation and business adaptation.

[0034] Optional, see Figure 2 In one embodiment, adding several subordinate nodes to the node management scope of the same superior node to obtain the platform cascade network corresponding to the superior node can be performed as follows:

[0035] Step 11: Configure the node properties of each subordinate node.

[0036] Step 12: Register the subordinate node with the superior node, and obtain the list of cascade nodes within the node management range of the superior node.

[0037] Step 13: Add the subordinate node to the cascade node list, and include the subordinate node in the node management scope of the superior node, so that the superior node can update the node topology based on the node management scope to obtain the platform cascade network corresponding to the superior node.

[0038] In this optional embodiment, before adding the subordinate node to the node range of the same superior node, the node attributes of the subordinate node can be configured first, wherein the node attributes are some attributes that reflect the type, business characteristics and data characteristics of the node. Usually, it is only necessary to distinguish the types of the corresponding nodes, and one or more specific identifiers are assigned to each subordinate node to reflect the node's level, function and role in the Internet of Things platform. For example, for a regional node, its specific regional identifier can be configured, such as geographical location, administrative area code, authority level, etc., and for an industry node, its specific business field, industry department number, node location, etc. can be configured. By configuring the node attributes of each subordinate node, it is ensured that each subordinate node can be correctly identified and managed and scheduled when it is added to the node management scope of the superior node.

[0039] In this optional embodiment, after the above configuration, the corresponding subordinate node can be registered with the superior node. During the registration process, the subordinate node needs to provide its node attribute information and request to join the node management scope of the superior node. After receiving the registration request, the superior node will review the subordinate node according to the policies and rules within its node management scope. The review process may involve verifying the legitimacy and security of the subordinate node and whether it meets the conditions for joining the node management scope. After the review is passed, the subordinate node can be registered with the superior node and access the cascade node list within the node management scope of the superior node. The cascade node list can include the names, divisions, competent units, addresses and authentication information of the industry nodes and regional nodes that are online within the node scope of the superior node, which is used for cross-regional and cross-industry data scheduling to ensure that the superior node can quickly identify and manage the corresponding subordinate nodes according to the cascade node list.

[0040] In this optional embodiment, after obtaining the cascade node list, the subordinate node can be added to the cascade node list to include the subordinate node in the node management scope of the superior node, so that the subordinate node becomes part of the node management scope of the superior node. On this basis, when the superior node updates its node topology structure, a new platform cascade network including the subordinate node can be obtained, and other nodes in the network, which are usually designated segments of the government external network, can be traversed and retrieved to reflect the new node relationship. Among them, the superior node updating its node topology structure can be triggered by the superior node sending a node update instruction to each subordinate node within its node management scope, or it can be triggered by the superior node and the subordinate node according to the topological relationship at a fixed time or fixed frequency. Through the processing of the cascade node configuration, the upper-level node can effectively manage and schedule all lower-level nodes based on the platform cascade network of the updated node topology structure, thereby improving the linkage and efficiency of the entire Internet of Things platform, enabling Internet of Things platforms at all levels to achieve more efficient data synchronization and business scheduling, ensuring the subsequent cross-level, cross-departmental, and cross-node data interconnection, optimizing the linkage of various levels of business and data under the urban Internet of Things system, and improving the real-time and accuracy of Internet of Things data.

[0041] Step 20: After the upper-level node obtains the event data, it synchronizes data with the corresponding lower-level node in the platform cascade network according to the node attributes corresponding to the event data.

[0042] In this embodiment, event data is data generated by a node under actions such as device status changes, abnormal alarms, and business scheduling requests. Each event data corresponds to a specific event action. The properties of the corresponding node can be judged according to the corresponding node action. For example, the corresponding node can be judged according to the node action as being a superior municipal node, a subordinate regional node, or an industry node, etc. The specific device corresponding to the corresponding node, the specific events that need to be processed, the indicator requirements for related events, and the event handling results, etc. can also be judged according to the node action. Among them, the equipment, events, and indicators are triggered in real time, that is, they need to be known during the event processing process, and the processing results are obtained after the event processing is completed.

[0043] In this embodiment, after the upper node obtains the event data, different data synchronization methods can be used according to the node attributes corresponding to the event data. For example, if the event only occurs in the lower node, for example, if the lower node determines that water resources and fire protection resources need to be called according to the abnormal situation, the data can be synchronized with the corresponding upper node and the water conservancy nodes and fire protection nodes of the same level related to water conservancy and fire protection through the platform cascade network, and then receive the corresponding data scheduling; and if the upper node needs to set the status, such as updating the area or industry under its jurisdiction, the corresponding event data can be synchronized to each lower node under its jurisdiction. All these methods require the knowledge of the upper node, and the upper node performs data synchronization processing according to the node data. It should be noted that if a sensor device connected to a lower node has an abnormal alarm, the corresponding event is usually solved by the closed loop inside the lower node. If the upper node only processes the event of its directly connected device, it only needs to be solved in the closed loop inside the Internet of Things of the upper node. These two methods usually do not involve the use of the platform cascade network, which is an existing common internal processing method, and this application does not make specific restrictions on this.

[0044] This embodiment can ensure the accurate transmission and timely response of event data in the Internet of Things platform through the above-mentioned data synchronization processing based on node attributes. When synchronizing data and nodes, everything is carried out around the superior platform, and the use is also centered on the superior platform. For example, if the municipal node is the superior platform, when the municipal platform receives abnormal alarm event data about traffic conditions, it will synchronize the event data to relevant regional nodes and industry nodes, such as traffic management nodes, according to the node attributes of the event data, so as to carry out corresponding traffic scheduling and emergency response. Such a data synchronization mechanism not only improves the efficiency of event processing, but also ensures the consistency and real-time nature of data between nodes at different levels. In this way, users only need to pay attention to the definition of their own level and type, without the need to carry out relevant cross-platform data development and platform docking, and optimize the various levels of business and data linkage under the urban Internet of Things system through subsequent processing.

[0045] Optional, see Figure 3 In one embodiment, after the upper node obtains the event data, data synchronization is performed with the corresponding lower node in the platform cascade network according to the node attribute corresponding to the event data, including:

[0046] Step 21: When an event issuing instruction triggered by an upper node is detected, or an event scheduling instruction triggered by an upper node is scheduled by a lower node, or an event reporting instruction triggered by a lower node is detected, corresponding event data is obtained.

[0047] Step 22: Determine that the node attribute corresponding to the event data is a city-level node, and synchronize the event data to each lower-level node in the platform cascade network.

[0048] Step 23: Determine that the node attribute corresponding to the event data is a regional node or an industry node, and synchronize the event data to the upper-level node, so that the upper-level node can synchronize the event data to the corresponding lower-level node in the platform cascade network based on the target list corresponding to the event data.

[0049] In this optional embodiment, event data can be triggered by nodes at each level in the cascade network of the platform. The upper node is the active trigger, and the lower node can be the active trigger, or it can accept the mobilization trigger of the upper node. Among them, the event sending instruction is a synchronization instruction triggered by the upper node when it detects a specific event or the condition is met and sends event data to the relevant lower node; the event scheduling instruction is an instruction issued when the upper node needs to coordinate multiple lower nodes to jointly handle an event; and the event reporting instruction is usually issued by the lower node when an abnormality is detected or an event that requires the intervention of the upper node. Through the interaction of these instructions, the accurate generation, transmission and timely response of event data in the Internet of Things platform can be ensured.

[0050] In this optional embodiment, after the corresponding event data is obtained, data synchronization can be performed according to the corresponding node data. When the node attribute corresponding to the event data is a municipal node, the event data will be synchronized to all subordinate nodes in the platform cascade network, including regional nodes and industry nodes. In this way, the municipal node can pass the event information to all relevant subordinate nodes in a timely manner to ensure comprehensive coverage and rapid response of information. For example, if the municipal node receives a report on a public health emergency, it will synchronize the event data to relevant regional nodes and industry nodes, such as hospitals, disease control centers, etc., according to the node attributes of the event data, so as to carry out corresponding epidemic control and resource allocation. In the case where the node attribute corresponding to the event data is a regional node or an industry node, the event data will be synchronized to the upper node, and then the upper node will synchronize the event data to the corresponding lower node in the platform cascade network according to the target list corresponding to the event data. For example, if a regional node detects traffic congestion in the area, it will send the event data to the municipal node through an event reporting instruction. After receiving the data, the municipal node will synchronize the traffic congestion information to relevant traffic management nodes and industry nodes, such as the traffic police department, based on the content of the event data, so as to take corresponding traffic control measures.

[0051] In this optional embodiment, through the above steps, it is possible to ensure that event data is accurately and efficiently synchronized between nodes at different levels, thereby improving the linkage and efficiency of the entire Internet of Things platform, ensuring subsequent cross-level, cross-departmental, and cross-node data interconnection, which is conducive to optimizing the linkage of various levels of business and data under the urban Internet of Things system, and improving the real-time and accuracy of Internet of Things data.

[0052] Optionally, in one embodiment, after the upper-level node obtains the event data, after synchronizing the data with the corresponding lower-level node in the platform cascade network according to the node attributes corresponding to the event data, it also includes: determining whether the data information of the corresponding event data in the upper-level node and each lower-level node is consistent, wherein the data information includes at least one of a data start bit identifier, a data end bit identifier, a data size information, a data type information and a record quantity information; confirming that the data information is consistent, synchronizing the event completion information to the corresponding upper-level node and the corresponding lower-level node in the platform cascade network.

[0053] In this optional embodiment, a method of data synchronization verification is provided to ensure the consistency of data information to ensure the integrity and accuracy of event processing. Specifically, this optional embodiment can verify whether the event data maintains integrity during the transmission process without loss or error by comparing key data information such as data start bit identification, data end bit identification, data size information, data type information and record quantity information. If the data information is inconsistent, the system will trigger the error handling mechanism, resynchronize the data or notify the relevant nodes to check and correct to ensure the accuracy of data synchronization. Among them, the data start bit identification and data end bit identification are used to determine the boundaries of the data packet to ensure the complete transmission of the data packet; the data size information is used to check whether the data packet is truncated or damaged during the transmission process; the data type information is used to confirm whether the format of the data packet is correct to ensure that the data is correctly parsed; the record quantity information is used to check whether the number of records contained in the data packet is consistent with expectations. Through these verification steps, errors and inconsistencies that may occur during data synchronization can be effectively avoided, thereby ensuring the accuracy and reliability of event data in the Internet of Things platform.

[0054] In this optional embodiment, after confirming that the data information is consistent, the event completion information can be synchronized to the corresponding upper node and the corresponding lower node in the platform cascade network. This process not only marks the end of event processing, but also provides a feedback mechanism for the entire Internet of Things platform to ensure that all relevant nodes are aware that the event has been properly handled. This synchronous transmission of completion information helps to maintain the stable operation of the Internet of Things platform, builds an efficient, stable and reliable cascade data adaptation method for the Internet of Things platform, solves the problem of cross-platform data synchronization of device events between multiple Internet of Things platforms, improves the efficiency of data processing, and enhances the linkage of the Internet of Things platform and the accuracy of data processing, and also provides reliable data support for subsequent event monitoring and analysis.

[0055] Step 30: After the upper-level node approves the service scheduling application of one of the lower-level nodes, the event data corresponding to the service scheduling application is pushed from the source node to the target node.

[0056] In this embodiment, in addition to performing data adaptation as described above, the business logic is also adapted to optimize the shared business logic between the upper node and the lower nodes with different node attributes. Specifically, when the upper node receives the business scheduling application of the lower node, it will first review the application to ensure the rationality and feasibility of the business scheduling. Among them, the business scheduling application is a request made by the lower node based on its business needs and resource conditions to request the upper node to allocate resources or adjust the business process. The review of the business scheduling application can be specifically forwarded by the upper node to the data providing node, that is, the competent department of the source node described later, and then confirmed after approval, or it can be directly approved by the competent department of the upper node. The review process may include an evaluation of the type of business applied, business volume, business priority, and necessary conditions for business execution.

[0057] In this embodiment, after passing the review, the superior node will approve the business scheduling application, and push the corresponding event data from the source node to the target node according to the source node and target node specified in the business scheduling application. Among them, the source node is the initiation point of the event data, and the target node is the receiving point of the event data. The source node and the target node are different subordinate nodes across regions and / or industries. For example, the source node is region A1, and the target node is region A2; the source node is industry B1, and the target node is industry B2; the source node is industry B3, and the target node is region A3, etc. Such a business scheduling mechanism ensures the efficient execution of business logic, and can respond quickly according to actual needs, further improving the linkage and business processing efficiency of the Internet of Things platform. In this way, the Internet of Things platform can realize cross-level and cross-departmental business scheduling, optimize resource allocation, and improve overall business processing capabilities.

[0058] In this embodiment, during the push process, the security and integrity of data transmission can be ensured through encrypted transmission, data verification and other measures. Once the data reaches the target node, the target node will process the event data according to the specific content of the business scheduling application, such as updating the status, performing specific operations or conducting further data analysis. This process not only realizes the automation of business processes, but also improves the efficiency and accuracy of business processing, allowing the Internet of Things platform to flexibly adapt to various business scenarios, realize cross-node and cross-departmental business collaboration and data sharing, thereby providing strong technical support for business operations under the urban Internet of Things system.

[0059] Optional, see Figure 4 After the upper node approves the service scheduling application of one of the lower nodes, the event data corresponding to the service scheduling application is pushed from the source node to the target node, including:

[0060] Step 31: After the upper node receives the service scheduling application and the approval indication of the service scheduling application, it determines the source node, target node and data list corresponding to the service scheduling application.

[0061] Step 32: Determine that the upper-level node schedules the source node based on the data list, obtain the event data corresponding to the business scheduling application, and push the corresponding event data to the target node.

[0062] In this optional embodiment, the processing flow of business scheduling is specified. After the upper node receives the business scheduling application and the approval indication of the business scheduling application, the source node, target node and data list corresponding to the business scheduling application are determined. Among them, the data list includes all relevant data items involved in the business scheduling application, for example, the data type, data volume, data format and other information of the data that the source node needs to provide. Once the source node and the target node are determined, the upper node will schedule the source node according to the data list to ensure the accuracy and completeness of the required data. Subsequently, the upper node pushes the acquired event data to the target node to complete the execution of the business scheduling application.

[0063] Optionally, in one embodiment, after adding several subordinate nodes to the node management scope of the same superior node and obtaining the platform cascade network corresponding to the superior node, it also includes: after the subordinate node receives the quality collaboration request initiated by the superior node and performs data rectification based on the quality collaboration request, the rectification information of the subordinate node is fed back to the superior node, so that the superior node can confirm the rectification result based on the rectification information.

[0064] In this optional embodiment, a cascaded business adaptation process of data quality collaboration is specifically provided to optimize the linkage handling logic of platform data quality issues. Among them, the quality collaboration request is a request issued by the upper node to the relevant lower node according to business requirements and data quality standards. After the lower node receives the quality collaboration request, it will check and correct the data managed by itself according to the request content to ensure the accuracy and consistency of the data. After the rectification is completed, the lower node will feedback the rectification information to the upper node, and the upper node will evaluate the rectification effect based on the feedback information and confirm the rectification result. For example, the Internet of Things platform of the municipal node will regularly inspect the data quality of the district, county and industry nodes and issue data quality problem work orders to require the lower node to verify and rectify the data. After the rectification, the lower node can obtain the rectification information fed back to the upper node through rectification feedback, self-inspection feedback or data quality report release, so that the upper node can confirm the rectification result based on the rectification information.

[0065] This optional embodiment helps improve the data quality of the entire IoT platform through the collaborative processing of data quality, ensures the reliability of data, and provides accurate data support for decision-making. Through the quality collaborative request and rectification feedback mechanism, the IoT platform can promptly discover and solve data problems, ensure the efficiency and accuracy of data processing, and thus gradually improve the quality of perception data of various regions and industry units, promote the data effectiveness of perception data in the field of urban applications, and further enhance the business processing and data management capabilities of the IoT platform.

[0066] Optionally, in one embodiment, the quality collaboration request includes at least one of a collaborative request for data indicators, a collaborative request for reporting frequency indicators, a collaborative request for data content quality, a collaborative request for node online rate, and a collaborative request for node data sharing value.

[0067] In this optional embodiment, the quality of data may include multiple dimensions, among which data indicators are used to evaluate how many types and how much device data the region or industry corresponding to the node can provide, which is usually derived from a data asset census; the reporting frequency is used to evaluate the frequency of reporting data content by IoT devices in the region or industry corresponding to the node within a preset event segment, which is usually derived from the definition of the product; the data content quality is used to evaluate whether the alarms and event content reported by the corresponding IoT devices are true and valid; the node online rate is used to evaluate the stable and effective operation of the IoT devices in the corresponding region or industry, which can be judged by the reporting frequency or the heartbeat packets of the relevant equipment; and the shared value is evaluated by other data users to evaluate the utilization efficiency and use value of the data.

[0068] In this optional embodiment, accordingly, the collaborative request for data indicators requires the subordinate node to check whether its equipment and type meet the standards, and make rectifications if they do not meet the standards; the collaborative request for reporting frequency indicators requires the subordinate node to adjust the reporting frequency of its equipment to meet the requirements of the upper node for data real-time; the collaborative request for data content quality requires the subordinate node to ensure the accuracy and completeness of the reported data to avoid the generation of false or erroneous data; the collaborative request for node online rate requires the subordinate node to ensure the stable operation of the Internet of Things equipment and reduce the data loss caused by equipment failure; the collaborative request for node data sharing value encourages the subordinate node to share data with other nodes, and improves the referenceability and credibility of related data to improve the efficiency and value of data use. Through these collaborative requests, the upper node can effectively manage the data quality of the subordinate node, ensure that the data quality of the entire Internet of Things platform meets the expected standards, and provide accurate and reliable data support for business operations under the urban Internet of Things system.

[0069] See also Figure 5 , Figure 5It is a structural diagram of an embodiment of a cascade adapter device of an Internet of Things platform provided by the present application.

[0070] The cascade adaptation device 40 includes: a platform cascade node configuration module 41, which is used to add several subordinate nodes to the node management scope of the same upper node to obtain a platform cascade network corresponding to the upper node; a data adaptation module 42, which is used to synchronize data with the corresponding subordinate nodes in the platform cascade network according to the node attributes corresponding to the event data after the upper node obtains the event data; a business adaptation module 43, which is used to push the event data corresponding to the business scheduling application from the source node to the target node after the upper node approves the business scheduling application of one of the lower nodes; wherein the node attributes of the upper node include municipal nodes, the node attributes of the lower node include regional nodes and / or industry nodes, and the source node and the target node are different subordinate nodes across regions and / or industries.

[0071] Optionally, in one embodiment, the platform cascade node configuration module 41 is also specifically used to configure the node attributes of each subordinate node; register the subordinate node with the superior node, and obtain the cascade node list within the node management scope of the superior node; add the subordinate node to the cascade node list, and include the subordinate node in the node management scope of the superior node, so that the superior node can update the node topology based on the node management scope to obtain the platform cascade network corresponding to the superior node; wherein the node attributes of the superior node include city-level nodes, the node attributes of the subordinate node include regional nodes and / or industry nodes, and the source node and the target node are different subordinate nodes across regions and / or industries.

[0072] Optionally, in one embodiment, the data adaptation module 42 is also specifically used to obtain corresponding event data when an event issuing instruction triggered by an upper-level node is detected, or an event scheduling instruction triggered by a lower-level node is dispatched by the upper-level node, or an event reporting instruction triggered by a lower-level node is detected; determine that the node attribute corresponding to the event data is a municipal node, and synchronize the event data to each lower-level node in the platform cascade network; determine that the node attribute corresponding to the event data is a regional node or an industry node, and synchronize the event data to the upper-level node, so that the upper-level node can synchronize the event data to the corresponding lower-level node in the platform cascade network based on the target list corresponding to the event data.

[0073] Optionally, in one embodiment, the data adaptation module 42 is also specifically used to determine whether the data information of the corresponding event data in the upper node and each lower node is consistent, wherein the data information includes at least one of a data start bit identifier, a data end bit identifier, a data size information, a data type information and a record quantity information; confirming that the data information is consistent, and synchronizing the event completion information to the corresponding upper node and the corresponding lower node in the platform cascade network.

[0074] Optionally, in one embodiment, the service adaptation module 43 is also specifically used to: determine the source node, target node and data list corresponding to the service scheduling application after the upper node receives the service scheduling application and the approval indication of the service scheduling application; determine that the upper node schedules the source node based on the data list, and obtains the event data corresponding to the service scheduling application, and pushes the corresponding event data to the target node.

[0075] Optionally, in one embodiment, the business adaptation module 43 is also specifically used to: after the subordinate node receives the quality collaboration request initiated by the superior node and performs data rectification based on the quality collaboration request, feedback the rectification information of the subordinate node to the superior node, so that the superior node can confirm the rectification result based on the rectification information.

[0076] Optionally, in one embodiment, the quality collaboration request includes at least one of a collaborative request for data indicators, a collaborative request for reporting frequency indicators, a collaborative request for data content quality, a collaborative request for node online rate, and a collaborative request for node data sharing value.

[0077] Since the embodiments of the device part correspond to the embodiments of the above-mentioned method, please refer to the above-mentioned method embodiment for the introduction of the cascade adaptation device 40 of the Internet of Things platform provided by the embodiment of the present invention. The embodiment of the present invention will not be repeated here, and it has the same beneficial effects as the cascade adaptation method of the above-mentioned Internet of Things platform.

[0078] See also Figure 6 , Figure 6 It is a structural diagram of an embodiment of the storage medium provided by the present application.

[0079] The storage medium 50 stores program data 51. When the program data 51 is executed by the processor, the following is achieved: Figures 1 to 4 The described cascading adaptation approach for IoT platforms.

[0080] The program data 51 is stored in a storage medium 50, and includes a number of instructions for enabling a network device (such as a router, a personal computer, a server, or other network device) or a processor to execute all or part of the steps of the methods of the various embodiments of the present application.

[0081] Optionally, the storage medium 50 may be a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disk, or other medium that can store the program data 51 .

[0082] See also Figure 7 , Figure 7 It is a structural schematic diagram of an embodiment of a computer device provided by the present application.

[0083] The computer device 60 includes a processor 62 and a memory 61 connected to each other. The memory 61 stores a computer program. When the processor 62 executes the computer program, the following is achieved: Figures 1 to 4 The described cascade adaptation method of the Internet of Things platform. The memory 61 may include a storage medium 60, or may be other independently developed memory.

[0084] Different from the prior art, the present application discloses a cascade adaptation method, device, medium and equipment for an Internet of Things platform. In the platform cascade network, subordinate nodes including regional nodes and industry nodes are included in the management of superior nodes including municipal nodes, and data synchronization between superior nodes and corresponding subordinate nodes is established after obtaining event data, and after the superior node approves the business application of the subordinate node, the relevant event data is pushed from the source node to the cross-regional or cross-industry target node, so as to realize the efficient interconnection and intercommunication of Internet of Things platform data across levels, departments and nodes, solve the problem of cross-platform data synchronization of device events between multiple Internet of Things platforms, and optimize the shared business logic of municipal nodes and cross-regional and cross-industry nodes. On this basis, users only need to focus on the definition of their own levels and types, without the need to carry out related cross-platform data development and platform docking, which simplifies the process of data synchronization and business scheduling, reduces the complexity of operations, and realizes the linkage of various levels of business and data under the urban Internet of Things system. Through unified data standards and quality control, the real-time and accuracy of Internet of Things data are improved, which is conducive to improving the quality of perception data in various regions and industries, and promoting the data effectiveness of perception data in urban application fields.

[0085] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, medium embodiment and equipment embodiment, since they are basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0086] The present application can be used in many general or special computing system environments or configurations, such as personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0087] In the several implementations provided in this application, it should be understood that the disclosed methods, devices, storage media, and computer equipment can be implemented in other ways. For example, the implementation of the cascade adapter device of the Internet of Things platform described above is only illustrative. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0088] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0089] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0090] The above descriptions are merely embodiments of the present application and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A cascade adaptation method for an Internet of Things platform, characterized in that: include: Adding several subordinate nodes to the node management scope of the same superior node to obtain a platform cascade network corresponding to the superior node; After the upper-level node acquires the event data, data synchronization is performed with the corresponding lower-level node in the platform cascade network according to the node attributes corresponding to the event data; After the upper node approves the service scheduling application of one of the lower nodes, the event data corresponding to the service scheduling application is pushed from the source node to the target node; Among them, the node attributes of the upper-level node include city-level nodes, the node attributes of the lower-level node include regional nodes and / or industry nodes, and the source node and the target node are different lower-level nodes across regions and / or industries.

2. The cascade adaptation method of the Internet of Things platform according to claim 1, characterized in that: The step of adding a plurality of subordinate nodes to the node management scope of the same superior node to obtain a platform cascade network corresponding to the superior node includes: Configuring the node attributes of each of the subordinate nodes; Registering the subordinate node with the superior node, and obtaining a list of cascade nodes within the node management range of the superior node; The subordinate node is added to the cascade node list, and the subordinate node is included in the node management scope of the superior node, so that the superior node updates the node topology based on the node management scope to obtain the platform cascade network corresponding to the superior node.

3. The cascade adaptation method of the Internet of Things platform according to claim 1, characterized in that: After adding a plurality of lower-level nodes to the node management scope of the same upper-level node to obtain the platform cascade network corresponding to the upper-level node, the method further includes: After the subordinate node receives the quality coordination request initiated by the superior node and performs data rectification based on the quality coordination request, the rectification information of the subordinate node is fed back to the superior node so that the superior node can confirm the rectification result based on the rectification information.

4. The cascade adaptation method of the Internet of Things platform according to claim 3, characterized in that: The quality collaborative request includes at least one of a collaborative request for data indicators, a collaborative request for reporting frequency indicators, a collaborative request for data content quality, a collaborative request for node online rate, and a collaborative request for node data sharing value.

5. The cascade adaptation method of the Internet of Things platform according to claim 1, characterized in that: After the upper node acquires the event data, data synchronization is performed with the corresponding lower node in the platform cascade network according to the node attribute corresponding to the event data, including: When an event dispatching instruction triggered by the upper node is detected, or an event scheduling instruction triggered by the lower node is scheduled by the upper node, or an event reporting instruction triggered by the lower node is detected, the corresponding event data is acquired; Determine that the node attribute corresponding to the event data is the city-level node, and synchronize the event data to each of the lower-level nodes in the platform cascade network; Determine that the node attribute corresponding to the event data is the regional node or the industry node, and synchronize the event data to the upper-level node, so that the upper-level node can synchronize the event data to the corresponding lower-level node in the platform cascade network based on the target list corresponding to the event data.

6. The cascade adaptation method of the Internet of Things platform according to claim 1, characterized in that: After the upper node acquires the event data, according to the node attribute corresponding to the event data, data synchronization is performed with the corresponding lower node in the platform cascade network, further comprising: Determine whether the data information of the event data corresponding to the upper node and each of the lower nodes is consistent, wherein the data information includes at least one of a data start bit identifier, a data end bit identifier, data size information, data type information, and record quantity information; Confirm that the data information is consistent, and synchronize event completion information to the corresponding upper node and the corresponding lower node in the platform cascade network.

7. The cascade adaptation method of the Internet of Things platform according to claim 1, characterized in that: After the upper node approves the service scheduling application of one of the lower nodes, the event data corresponding to the service scheduling application is pushed from the source node to the target node, including: After the upper node receives the service scheduling application and an approval indication of the service scheduling application, determining the source node, the target node and the data list corresponding to the service scheduling application; Determine that the upper-level node schedules the source node based on the data list, obtain the event data corresponding to the service scheduling application, and push the corresponding event data to the target node.

8. A cascade adapter device for an Internet of Things platform, characterized in that: include: A platform cascade node configuration module, used to add several subordinate nodes to the node management scope of the same superior node to obtain a platform cascade network corresponding to the superior node; A data adaptation module, for synchronizing data with the corresponding lower-level node in the platform cascade network according to the node attributes corresponding to the event data after the upper-level node acquires the event data; A service adaptation module, configured to push the event data corresponding to the service scheduling application from the source node to the target node after the upper node approves the service scheduling application of one of the lower nodes; Among them, the node attributes of the upper-level node include city-level nodes, the node attributes of the lower-level node include regional nodes and / or industry nodes, and the source node and the target node are different lower-level nodes across regions and / or industries.

9. A storage medium having program data stored thereon, characterized in that: When the program data is executed by a processor, the steps of the cascade adaptation method of the Internet of Things platform as described in any one of claims 1 to 7 are implemented.

10. A computer device, characterized in that: The method comprises a processor and a memory connected to each other, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the cascade adaptation method of the Internet of Things platform as claimed in any one of claims 1 to 7 are implemented.

Images