Internet-of-things equipment collaboration method and system based on open-source and wide-gap system

Abstract

The invention discloses an Internet of Things equipment collaboration method and system based on an open source gap system, and the method comprises the steps: building an Internet of Things equipment operation environment based on the open source gap system; designing a visual rule arrangement platform based on the operation environment of the Internet of Things equipment; receiving an editing operation of a user on the visual rule arrangement platform, editing a rule through the visual rule arrangement platform, and performing a simulation test on the rule; the rules passing the test are packaged into a business rule file, and the business rule file is distributed to a super device end side or a cloud side to be executed according to actual requirements; and continuously optimizing functions and performance of the visual rule arrangement platform according to user feedback and system operation conditions. According to the invention, the management and control of the Internet of Things equipment are more convenient and efficient by combining the open-source and wide-range system with the super equipment rule arrangement technology and simplifying the rule arrangement process, and efficient cooperation and intelligent control among the Internet of Things equipment are realized.

Description

Technical Field

[0001] The present invention relates to the field of intelligent Internet of Things technology, and in particular to an Internet of Things device collaboration method, system, terminal and computer-readable storage medium based on the open source Hongmeng system. Background Art

[0002] Traditional IoT devices lack a unified coordination mechanism, which leads to poor information exchange between devices and low coordination efficiency. The existing IoT platform rule arrangement mostly relies on professional programming, which has high barriers and difficulties and is not conducive to ordinary users. The existing IoT platform rule arrangement usually involves the following characteristics and problems:

[0003] (1) Professional programming requirements: Existing IoT platform rule orchestration often requires users to have certain programming skills, which usually means that users need to understand specific programming languages ​​or scripts, such as JavaScript, Python, or custom languages ​​for specific platforms, in order to define the interaction rules between devices.

[0004] (2) Complex workflow: Users need to write code to define logic such as device event triggering, condition judgment, and action execution. This process may include multiple steps, each of which requires precise configuration, which makes the entire rule orchestration process complicated.

[0005] (3) Limited graphical interface: Although some platforms provide graphical interfaces to help users arrange rules, these interfaces often have limited functions and can only support simple rule settings. For complex business logic, users still need to write code.

[0006] (4) Low flexibility: Once the rules are set and deployed, changing the rules usually requires rewriting and re-deploying, which can be cumbersome and lacks flexibility.

[0007] (5) Deployment difficulty: After the rules are written, they need to be deployed to the device. This process may involve issues such as version control and device compatibility, making the deployment process complex and prone to errors.

[0008] (6) Steep learning curve: For users with non-technical backgrounds, learning how to compile rules is a challenge because they need to understand the programming logic and platform-specific rule syntax.

[0009] Specifically, the existing IoT platform rule orchestration may include the following steps:

[0010] (1) Define triggers: Determine what events (such as button presses, temperature exceeding a threshold, etc.) will trigger the rules.

[0011] (2) Set conditions: Add conditional judgments to the rules. The rules will only be executed when the conditions are met.

[0012] (3) Specify actions: Define the actions that the system should perform when the trigger is triggered and the conditions are met (such as sending a notification, turning on the light, etc.).

[0013] (4) Write scripts: Use the scripting language provided by the platform to write the above logic.

[0014] (5) Testing and debugging: Test the rules in a simulated environment to ensure that they work as expected.

[0015] (6) Deployment: Deploy the rules to actual devices.

[0016] In summary, the existing IoT platform rule orchestration is usually a complex and technically demanding process, which limits the popularity and application scope of IoT technology.

[0017] The current distribution of IoT device rules often lacks flexibility and immediacy, and cannot quickly update or deploy business rules based on real-time needs, affecting the system's response speed and flexibility.

[0018] Current IoT device rules refer to the preset logic and instructions used to guide device behavior and interaction in traditional IoT systems. These rules usually have the following characteristics:

[0019] (1) Static: These rules are set when the device leaves the factory or through initial configuration. They are usually static and cannot be easily changed or updated except through a complex programming process.

[0020] (2) Uniformity: Rules are often customized for specific devices or scenarios, lack universality, and are difficult to reuse across different devices or scenarios.

[0021] (3) Hard-coded: Many rules are hard-coded directly in the device’s firmware or software, which means that changing the rules may require updating the device’s firmware or software.

[0022] Here are a few specific examples of current rules for IoT devices:

[0023] (1) Scheduled tasks: For example, the lighting system in a smart home may automatically turn off at night. This rule is triggered by a preset time.

[0024] (2) State trigger: For example, the temperature sensor automatically turns on the air conditioner when it detects that the indoor temperature exceeds a certain threshold.

[0025] (3) Event response: For example, in a security system, when an intrusion is detected, the camera automatically starts recording and sounds an alarm.

[0026] (4) Linkage control: In a smart home, when a user turns on the TV, the lights automatically dim and the speakers automatically turn on.

[0027] The current rules for IoT devices have the following problems:

[0028] (1) Difficult to update: Since rules are usually hard-coded, updating or modifying rules requires expertise and complex processes.

[0029] (2) Lack of flexibility: Rules are difficult to adjust quickly based on user needs or changes in the environment.

[0030] (3) Poor interoperability: Devices from different manufacturers may use different rule systems, which complicates interoperability between devices.

[0031] (4) Low distribution efficiency: When large-scale deployment of rules is required, manually configuring the rules for each device is inefficient and prone to errors.

[0032] Therefore, the prior art still needs to be improved and developed. Summary of the invention

[0033] The main purpose of the present invention is to provide an IoT device collaboration method, system, terminal and computer-readable storage medium based on the open source Hongmeng system, aiming to solve the problems in the prior art of low efficiency of collaboration between devices, high complexity of rule orchestration, and low efficiency of rule publishing and execution.

[0034] To achieve the above object, the present invention provides an IoT device collaboration method based on an open source Hongmeng system, and the IoT device collaboration method based on an open source Hongmeng system comprises the following steps:

[0035] Build an operating environment for IoT devices based on the open source Hongmeng system;

[0036] Based on the IoT device operating environment, a visual rule orchestration platform is designed;

[0037] Receiving editing operations of users on the visual rule orchestration platform, editing rules through the visual rule orchestration platform, and performing simulation tests on the rules;

[0038] Package the rules that pass the test into business rule files, and distribute the business rule files to the super device side or the cloud side for execution according to actual needs;

[0039] Based on user feedback and system operation status, the functions and performance of the visual rule orchestration platform are continuously optimized.

[0040] Optionally, the IoT device collaboration method based on the open source Hongmeng system, wherein the IoT device operating environment includes: hardware equipment, software framework, communication protocol, data storage and processing.

[0041] Optionally, the IoT device collaboration method based on the open source Hongmeng system, wherein the IoT device operating environment is built based on the open source Hongmeng system, specifically includes:

[0042] Develop or adapt device drivers to adapt the open source Hongmeng system to IoT devices, so that IoT devices can work normally on the open source Hongmeng system;

[0043] Configure network services in the open source Hongmeng system and set up network communication protocols to ensure that IoT devices can exchange data effectively over the network;

[0044] Deploy the open source Hongmeng system to IoT devices. For distributed systems, configure the distributed service framework of the open source Hongmeng system to support collaborative work between devices.

[0045] Build middleware and services on the open source Hongmeng system to achieve device discovery, registration, data reporting and command issuance;

[0046] Implement security mechanisms in the system, including device authentication, data encryption, and access control, to ensure system stability and data security;

[0047] Integrate the open source Hongmeng system with upper-level applications so that the system receives instructions from upper-level applications and performs corresponding operations.

[0048] Optionally, the IoT device collaboration method based on the open source Hongmeng system, wherein the design visualization rule orchestration platform specifically includes:

[0049] Conduct demand analysis and planning based on the target user groups to determine the functions that the platform needs to support;

[0050] Build a set of standardized UI component libraries to build rule arrangement interfaces;

[0051] The drag-and-drop component allows users to connect different devices or services by dragging, allows users to combine multiple rules into a business process, and designs clear status indications;

[0052] Define the data structure, rule parsing, verification and execution logic of the rules, design the database model, and store the rules created by users and device status information;

[0053] Design interfaces and interaction logic, develop API interfaces and conduct integration testing;

[0054] Develop a visual editor to support users to compose rules through a graphical interface, provide a simulation environment for users to test the effectiveness of rules before deployment, and design the packaging function of rule files;

[0055] Pass security and compatibility tests to ensure data security during rule editing and execution and to ensure platform compatibility with different devices and operating systems;

[0056] Collect user feedback on the platform, identify problems and areas for improvement, and optimize functions and improve performance based on the feedback.

[0057] Optionally, the IoT device collaboration method based on the open source Hongmeng system, wherein the rules include: event triggering rules, condition judgment rules, action execution rules, device linkage rules and data processing rules;

[0058] The editing of rules through the visual rule arrangement platform and the simulation test of the rules specifically include:

[0059] According to the user's selection operation, select the rule type to be created on the visual rule arrangement platform;

[0060] Drag pre-defined rule components to the workspace and use connecting lines to connect the components to form a logical flow;

[0061] Open the property configuration window and set the specific parameters of the rule in the property configuration;

[0062] Set the specific conditions for triggering the action and specify the action to be performed;

[0063] After the rule editing is completed, a test scenario is created on the visual rule orchestration platform, parameters are configured for the test scenario, and a simulation test is triggered, which will be executed in the test scenario according to the orchestrated rule logic;

[0064] During the test execution process, monitor the execution of each rule and check whether the output after the rule execution meets the expected results to ensure that the rule works as expected.

[0065] Optionally, the IoT device collaboration method based on the open source Hongmeng system, wherein the business rule file is distributed to the super device side or the cloud side for execution, specifically includes:

[0066] The business rule file is downloaded to the local storage of the super device side. The operating system or specific software on the super device side parses the rule file and executes the rules. The super device side performs corresponding actions according to the rules.

[0067] Or upload the business rule file to the cloud side, the application or service on the cloud side parses the rule file and executes the rules, and the cloud side communicates with the device to send instructions or collect data.

[0068] Optionally, the IoT device collaboration method based on the open source Hongmeng system, wherein the function and performance of the visual rule orchestration platform are continuously optimized according to user feedback and system operation status, specifically including:

[0069] Collect user experience and suggestions, and monitor system usage;

[0070] Analyze user feedback, identify common problems and user needs, and diagnose system bottlenecks and potential errors through system logs and performance monitoring data;

[0071] Develop specific optimization plans based on the analysis results;

[0072] Develop and test software according to the optimization plan, update the system and deploy improved functions;

[0073] After the update is released, continue to collect user feedback and system operation data to verify the optimization effect.

[0074] In addition, to achieve the above-mentioned purpose, the present invention further provides an IoT device collaboration system based on the open source Hongmeng system, wherein the IoT device collaboration system based on the open source Hongmeng system includes:

[0075] System environment building module, used to build the operating environment of IoT devices based on the open source Hongmeng system;

[0076] A visualization platform development module, used to design a visualization rule orchestration platform based on the IoT device operating environment;

[0077] A rule editing and testing module, used to receive editing operations of users on the visual rule editing platform, edit rules through the visual rule editing platform, and perform simulation tests on the rules;

[0078] A business rule file packaging module is used to package the rules that have passed the test into a business rule file, and distribute the business rule file to the super device side or the cloud side for execution according to actual needs;

[0079] The continuous optimization and upgrade module is used to continuously optimize the functions and performance of the visual rule orchestration platform based on user feedback and system operation status.

[0080] In addition, to achieve the above-mentioned purpose, the present invention also provides a terminal, wherein the terminal includes: a memory, a processor, and an Internet of Things device collaboration program based on the open source Hongmeng system stored in the memory and runnable on the processor, and when the Internet of Things device collaboration program based on the open source Hongmeng system is executed by the processor, the steps of the Internet of Things device collaboration method based on the open source Hongmeng system as described above are implemented.

[0081] In addition, to achieve the above-mentioned purpose, the present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores an Internet of Things device collaboration program based on the open source Hongmeng system, and when the Internet of Things device collaboration program based on the open source Hongmeng system is executed by the processor, the steps of the Internet of Things device collaboration method based on the open source Hongmeng system as described above are implemented.

[0082] In the present invention, an IoT device operating environment is built based on the open source Hongmeng system; a visual rule orchestration platform is designed based on the IoT device operating environment; user editing operations on the visual rule orchestration platform are received, rules are edited through the visual rule orchestration platform, and simulation tests are performed on the rules; the rules that pass the test are packaged into business rule files, and the business rule files are distributed to the super device side or the cloud side for execution according to actual needs; the functions and performance of the visual rule orchestration platform are continuously optimized according to user feedback and system operation. The present invention combines the super device rule orchestration technology through the open source Hongmeng system, simplifies the rule orchestration process, makes the management and control of IoT devices more convenient and efficient, and realizes efficient collaboration and intelligent control between IoT devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] Figure 1 It is a flowchart of a preferred embodiment of the IoT device collaboration method based on the open source Hongmeng system of the present invention;

[0084] Figure 2 It is a structural diagram of a preferred embodiment of the Internet of Things device collaboration system based on the open source Hongmeng system of the present invention;

[0085] Figure 3 It is a structural diagram of a preferred embodiment of the terminal of the present invention. DETAILED DESCRIPTION

[0086] In order to make the purpose, technical solution and advantages of the present invention clearer and more specific, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0087] The IoT device collaboration method based on the open source Hongmeng system described in the preferred embodiment of the present invention is as follows: Figure 1As shown, the IoT device collaboration method based on the open source Hongmeng system includes the following steps:

[0088] Step S10: Build an IoT device operating environment based on the open source Hongmeng system.

[0089] Specifically, the IoT device operating environment refers to a collection of software and hardware infrastructure and communication protocols required to support the normal operation of IoT devices. Components of the IoT device operating environment:

[0090] (1) Hardware equipment: including physical devices such as sensors, actuators, gateways, and servers.

[0091] (2) Software framework: operating system, device driver, middleware and other software components.

[0092] (3) Communication protocols: such as Wi-Fi, Bluetooth, Zigbee, LoRa, etc., used for data transmission between devices.

[0093] (4) Data storage and processing: Databases and servers are used to store, process and analyze data.

[0094] Building an IoT device operating environment based on the open source Hongmeng system involves the following key steps:

[0095] (1) System adaptation: Ensure the hardware compatibility between the open source Hongmeng system and IoT devices. Develop or adapt device drivers so that hardware devices can work properly on the open source Hongmeng system.

[0096] (2) Network configuration: Configure network services in the open source Hongmeng system, including access to wireless or wired networks. Set up network communication protocols to ensure that devices can effectively exchange data through the network.

[0097] (3) System deployment: Deploy the open source Hongmeng system to IoT devices, which can be embedded devices, gateways or servers. For distributed systems, configure the distributed service framework of the open source Hongmeng system to support collaborative work between devices.

[0098] (4) Service construction: Build necessary middleware and services on the open source Hongmeng system, such as message queues, data storage services, device management services, etc. Implement basic functions such as device discovery, registration, data reporting, and command issuance.

[0099] (5) Security considerations: Implement security mechanisms in the system, including device authentication, data encryption, access control, etc. to ensure system stability and data security.

[0100] (6) System integration: Integrate the open source Hongmeng system with upper-level applications (such as a visual rule orchestration platform) so that the system can receive instructions from upper-level applications and perform corresponding operations.

[0101] The connection between the open source Hongmeng system and the operating environment of IoT devices:

[0102] (1) Cross-platform capability: The cross-platform capability of the open source Hongmeng system enables it to support a variety of hardware devices and operating systems, providing a unified operating environment for IoT devices.

[0103] (2) Distributed architecture: The distributed architecture of the open source Hongmeng system is naturally suitable for IoT applications and can support seamless connection and communication between devices.

[0104] (3) Resource management: The open source Hongmeng system provides an effective resource management mechanism, including memory, CPU, network, etc., to ensure the efficient operation of IoT devices.

[0105] Through the above steps, a stable, efficient and secure IoT device operating environment can be built on the basis of the open source Hongmeng system, laying a solid foundation for efficient collaboration and intelligent control among IoT devices. The IoT device operating environment provides a stable and operable underlying platform for all subsequent steps, ensuring the interconnection between devices, which is the prerequisite for achieving device collaboration and control.

[0106] Step S20: designing a visual rule arrangement platform based on the IoT device operating environment.

[0107] Specifically, the visual rule orchestration platform needs to run on the established IoT device operating environment. The development of the platform needs to consider compatibility with the existing device operating environment to ensure that the platform can communicate effectively with the device.

[0108] The following are the general steps and key points for designing a visual rule orchestration platform:

[0109] (1) Demand analysis and planning:

[0110] User research: Understand the technical background, operating habits and needs of the target user group.

[0111] Functional requirements: Determine the functions that the platform needs to support, such as device management, rule editing, simulation testing, etc.

[0112] Technology selection: Choose the appropriate technology stack, including front-end framework, back-end services, database, and middleware.

[0113] (2) Interface design:

[0114] User Interface (UI): Designing an intuitive, easy-to-use interface, including layout, colors, icons, and fonts.

[0115] User Experience (UX): Ensure smooth user operation process and reduce learning costs.

[0116] Component library: Build a standardized UI component library for building rule-based orchestration interfaces.

[0117] (3) Interaction logic design:

[0118] Drag-and-drop functionality: Implement drag-and-drop components, allowing users to connect different devices or services by dragging.

[0119] Combination function: allows users to combine multiple rules into a more complex business process.

[0120] Status feedback: Design clear status indications, such as the enabled / disabled status of the rule, execution results, etc.

[0121] (4) Data processing module:

[0122] Rule model: The data structure that defines the rules, including input, output, conditions, and actions.

[0123] Data processing: Implement rule parsing, validation, and execution logic.

[0124] Data storage: Design a database model to store user-created rules and device status information.

[0125] (5) Platform development:

[0126] Front-end implementation: Use HTML, CSS, JavaScript and other technologies to implement the interface and interaction logic.

[0127] Back-end implementation: developing API interfaces, processing front-end requests, communicating with devices, managing rules, etc.

[0128] Integration testing: Ensure that the front-end and back-end work together and meet the design requirements.

[0129] (6) Feature Implementation:

[0130] Visual editing: Develop a visual editor to support users in editing rules through a graphical interface.

[0131] Simulation test: Provides a simulation environment for users to test the effectiveness of rules before deployment.

[0132] Rule packaging: Implement the packaging function of rule files and support export in multiple formats.

[0133] (7) Safety and compatibility:

[0134] Security: Ensure data security during rule editing and execution to prevent unauthorized access.

[0135] Compatibility: Make sure the platform is compatible with different devices and operating systems.

[0136] (8) User feedback and iteration:

[0137] User Feedback: Collect feedback from users on the platform and identify issues and areas for improvement.

[0138] Continuous iteration: optimize functions and improve performance based on feedback.

[0139] Example of specific steps:

[0140] (1) Define rule components: Create draggable rule components such as "if", "then", "else", etc.

[0141] (2) Design rule flow: Allow users to define rule flow by connecting components.

[0142] (3) Implement attribute configuration: Provide an attribute configuration interface for each rule component, such as setting conditions, action parameters, etc.

[0143] (4) Integrated device management: allows users to manage devices directly from the platform, such as adding, deleting, and monitoring device status.

[0144] (5) Testing and debugging: Provide debugging tools to help users detect and fix errors in rules.

[0145] (6) Deployment and execution: Design the rule deployment process to ensure that the rules can be correctly distributed to the target devices and executed.

[0146] Through the above steps, a fully functional, user-friendly visual rule orchestration platform can be designed and implemented to provide support for efficient collaboration and intelligent control among IoT devices.

[0147] Step S30: receiving the editing operation of the user on the visual rule arrangement platform, editing the rules through the visual rule arrangement platform, and performing simulation tests on the rules.

[0148] Specifically, the rules compiled by users on the visualization platform need to be applied to actual devices, which requires that the devices are already in operation and able to respond to instructions issued by the platform; simulation tests also need to be performed in the device operating environment to verify the performance of the rules under actual operating conditions.

[0149] The rules that users edit through the visual rule orchestration platform are mainly to specify the logic and conditions of the interaction between devices. The following are some specific rule types and editing methods:

[0150] Specific rule types:

[0151] (1) Event triggering rules: define which events (such as button pressing, temperature exceeding a threshold, etc.) will trigger subsequent actions.

[0152] (2) Conditional judgment rules: Set conditions (such as presence, time range, etc.) and perform specific actions when the conditions are met.

[0153] (3) Action execution rules: specify the specific actions that the device should perform when the conditions are met (such as turning on the light, sending a notification, etc.).

[0154] (4) Device linkage rules: Set the linkage logic between multiple devices, for example, the action of one device triggers the response of another device.

[0155] (5) Data processing rules: define how to process the data collected by the device, such as filtering, aggregation, or forwarding.

[0156] The process of editing rules is as follows:

[0157] (1) Select the rule type: The user selects the rule type to be created on the visualization platform, such as event triggering, condition judgment, etc.

[0158] (2) Drag and connect components: Users drag pre-defined rule components (such as "if", "then", "else", etc.) to the workspace and use connecting lines to connect components to form a logical flow.

[0159] (3) Configure rule properties: Double-click or right-click the component to open the property configuration window. In the property configuration, users can set specific parameters of the rule, such as the specific conditions for triggering events, the specific content of actions, etc.

[0160] (4) Setting conditions: For conditional judgment rules, users need to set specific conditions for triggering actions, such as the temperature being greater than a certain value, the door magnetic sensor being triggered, etc.

[0161] (5) Define actions: For action execution rules, users need to specify the actions to be executed, such as turning on lights, adjusting air conditioning temperature, etc.

[0162] (6) Testing rules: After editing is completed, users can perform simulation tests on the visualization platform to ensure that the rules work as expected.

[0163] For example, the rule editing process:

[0164] Create an event trigger rule:

[0165] (1) The user selects the “Event Trigger” rule type.

[0166] (2) Drag the "If" component to the workspace and set the trigger event (for example, "Door Opens").

[0167] (3) Drag the "Then" component and connect it to the "If" component, and set the action (for example, "Turn on the living room lights").

[0168] Create a conditional judgment rule:

[0169] (1) The user selects the “Conditional Judgment” rule type.

[0170] (2) Drag the "If" component and set the conditions (for example, "temperature is higher than 25 degrees").

[0171] (3) Drag the "Then" component and connect it to the "If" component, and set the action (for example, "Start the air conditioner").

[0172] Through this editing process, users can create complex rules without writing code, achieving efficient collaboration and intelligent control among IoT devices.

[0173] Simulation testing is a key step to ensure the correctness and effectiveness of rules. The following are the specific steps and methods for conducting simulation testing:

[0174] How to take the mock test:

[0175] (1) Create test scenarios: On the visual rule orchestration platform, users first need to create one or more test scenarios that should simulate the actual application environment as much as possible. Test scenarios can include virtual devices or actual devices, as well as the interaction logic between them.

[0176] (2) Configure test parameters: Users need to configure parameters for test scenarios, such as device status, environmental variables, timestamps, etc., to simulate real-world conditions.

[0177] (3) Execution rule simulation: When the user triggers a simulation test, the platform will execute the rules in the test scenario according to the arranged rule logic. During the simulation, the platform will simulate event triggering, condition judgment, and action execution.

[0178] (4) Monitoring the test process: During the test execution, users can monitor the execution of each rule through the platform, including event triggering, condition satisfaction, action execution results, etc.

[0179] (5) Verify rule output: Users need to check whether the output after rule execution meets expectations, for example, whether the device performs corresponding actions according to the rule settings.

[0180] Verify the correctness and effectiveness of the rules:

[0181] (1) Result comparison: Compare the results of the simulation test with the expected results to ensure that each action and decision complies with the definition of the rules.

[0182] (2) Boundary condition testing: Testing the performance of the rules under boundary conditions, such as the response of the equipment under extreme temperatures, extreme time points, etc.

[0183] (3) Abnormal situation handling: Check the rules' handling capabilities under abnormal situations, such as network interruptions and equipment failures, to ensure that the system can properly handle these situations.

[0184] (4) Performance evaluation: Evaluate the impact of rule execution on system performance, including response time, resource consumption, etc.

[0185] (5) User feedback: Collect user feedback during the testing process to understand the usability and effectiveness of the rules in actual operations.

[0186] (6) Log analysis: Analyze the log files generated by the simulation test to find possible errors or abnormal behaviors.

[0187] Through the above steps, users can ensure that the rules have been fully tested and verified before actual deployment, thereby improving the reliability and stability of the system. Simulation testing can not only verify the correctness and effectiveness of the rules, but also help users discover and fix potential problems in the rules, ensuring efficient and stable operation in actual applications.

[0188] Step S40: Pack the rules that pass the test into a business rule file, and distribute the business rule file to the super device side or the cloud side for execution according to actual needs.

[0189] Specifically, the packaged business rule files are to be deployed and executed in the device operating environment. The file format selection and packaging method need to be compatible with the device operating environment. The distribution and execution of business rule files directly depend on the device operating environment. Only in the device operating environment can the business rules be correctly executed to achieve coordination and control between devices.

[0190] The super device side or cloud side refers to two different computing environments where IoT devices execute business rules.

[0191] Super device side: Super device side usually refers to the smart devices themselves in the Internet of Things, which have enough computing power and storage space to run local business rules. Execution on the side means that the rules run directly on the device without going through an external server or cloud platform. This usually involves the following steps:

[0192] (1) Download the business rule file to the local storage of the device.

[0193] (2) The device's operating system or specific software parses the rule file and executes the rules.

[0194] (3) The device performs corresponding actions according to the rules, such as controlling sensors, sending notifications, etc.

[0195] Execution purpose: The purpose of edge execution is to reduce dependence on cloud resources, reduce latency, improve responsiveness, and maintain device autonomy when the network is unstable or unavailable.

[0196] Cloud side: The cloud side refers to remote servers or cloud service platforms that provide powerful computing resources and services that can handle complex business logic and data analysis. Executing rules on the cloud side usually involves the following steps:

[0197] (1) Upload the business rule file to the cloud server.

[0198] (2) The application or service on the cloud server parses the rule file and executes the rules.

[0199] (3) The cloud server communicates with the device to send instructions or collect data.

[0200] Execution purpose: The purpose of cloud-side execution is to use the powerful processing capabilities of the cloud platform to perform large-scale data processing and analysis, achieve cross-device service coordination, and provide high-availability and scalability solutions.

[0201] The purpose of the two execution modes:

[0202] (1) Improve efficiency: By executing rules in the most suitable environment (end or cloud), resource usage can be optimized and the overall operating efficiency of the system can be improved.

[0203] (2) Ensure reliability: Cloud-side execution can provide backup and failover mechanisms to ensure high reliability of the system.

[0204] (3) Flexibility: Based on actual needs and environmental conditions, the execution location of rules can be flexibly switched between the end side and the cloud side to adapt to different business scenarios and performance requirements.

[0205] By executing business rules on the super device side or the cloud side, the present invention can achieve efficient collaboration and intelligent control among IoT devices, ensure that the system can respond quickly according to real-time needs, and optimize the performance and user experience of the overall system.

[0206] Step S50: Continuously optimize the functions and performance of the visual rule orchestration platform according to user feedback and system operation status.

[0207] Specifically, optimization and upgrades based on user feedback and system operation are to improve the performance and stability of the device operating environment. The purpose of optimization and upgrades is to ensure that IoT devices can work more efficiently in the operating environment. Continuously optimizing the functions and performance of the visualization platform is an iterative process that relies on the collection and analysis of user feedback and system operation. Specific steps for optimization:

[0208] (1) Collect feedback: Collect user experience and suggestions through user surveys, online feedback forms, user forums, etc. Monitor system usage, including user operation logs, system error reports, performance indicators, etc.

[0209] (2) Analyze data: Analyze user feedback, identify common problems and user needs, and diagnose system bottlenecks and potential errors through system logs and performance monitoring data.

[0210] (3) Develop an optimization plan: Based on the analysis results, develop a specific optimization plan, including functional updates, performance improvements, user interface improvements, etc.

[0211] (4) Implementation of optimization: The development team develops and tests software according to the optimization plan, updates the system and deploys improved functions.

[0212] (5) Verify the effect: After the update is released, continue to collect user feedback and system operation data to verify the optimization effect.

[0213] For example, user feedback, problem: Users reported that when creating rules on the visual rule orchestration platform, dragging components is not smooth enough and sometimes there is a freeze. Optimization: To address this problem, the development team can optimize the platform's graphical user interface (GUI) engine to improve the response speed and stability of drag operations. For example, the following methods can be used:

[0214] (1) Optimize event processing logic to reduce unnecessary calculations and rendering.

[0215] (2) Use more efficient data structures to manage component status.

[0216] (3) Increase hardware acceleration support, such as using GPU for graphics rendering.

[0217] System operation status, Problem: System monitoring shows that when editing multiple rules at the same time, the platform's response time increases significantly, sometimes causing the system to crash. Optimization: To address this issue, the development team can take the following measures:

[0218] (1) Optimize the background data processing process and improve multi-tasking capabilities.

[0219] (2) Increase the efficiency of memory management and resource allocation and prevent memory leaks.

[0220] (3) Implement load balancing to ensure that system resources are properly allocated and to prevent a single user from overloading the system and affecting overall performance.

[0221] Through such an optimization process, the functions and performance of the visualization platform can be continuously improved, thereby enhancing the user experience and system stability. This process is cyclical, and as user needs and technology develop, the platform will continue to evolve to adapt to the dynamic changes in the IoT field.

[0222] The improvements of the present invention are as follows:

[0223] (1) Underlying support based on the open source Hongmeng system: Utilizing the powerful cross-platform capabilities and distributed architecture of the open source Hongmeng system, a unified operating system foundation is provided for IoT devices to achieve seamless connection and communication between devices.

[0224] (2) Visual rule orchestration platform: Develop a user-friendly platform editor that supports users to easily orchestrate linkage rules or process business flows between devices, devices and services, services and services within or between super devices through visual methods such as dragging and dropping and combining.

[0225] (3) Business rule file packaging and distribution: The compiled rules are packaged into business rule files, which can be distributed and deployed on demand to the super device side or cloud side for execution. Through the collaborative work between the cloud and the side, efficient coordination and control of IoT devices can be achieved.

[0226] Beneficial effects of the present invention:

[0227] (1) Improve device collaboration efficiency: Through the unified open source Hongmeng system and visual rule orchestration platform, efficient collaboration and intelligent control among IoT devices can be achieved, thereby improving overall system performance.

[0228] (2) Lowering the operational threshold: Visual orchestration simplifies the complexity of rule-making, making it easy for non-professionals to get started, thus reducing the difficulty of promoting IoT applications.

[0229] (3) Improve system operation efficiency: Flexible updating and instant application of business rules ensure that the equipment can quickly respond to real-time changing business needs, thereby improving the overall operation efficiency of the system.

[0230] This invention aims to achieve efficient collaboration and intelligent control among IoT devices through the open source Hongmeng system combined with super device rule orchestration technology. It can be widely used in smart homes, smart cities, industrial automation, telemedicine and other fields, and promote the development of the Internet of Things towards a more intelligent, automated and efficient direction.

[0231] Furthermore, if Figure 2 As shown, based on the above-mentioned IoT device collaboration method based on the open source Hongmeng system, the present invention also provides an IoT device collaboration system based on the open source Hongmeng system, wherein the IoT device collaboration system based on the open source Hongmeng system includes:

[0232] The system environment building module 51 is used to build an IoT device operating environment based on the open source Hongmeng system;

[0233] A visualization platform development module 52 is used to design a visualization rule arrangement platform based on the IoT device operating environment;

[0234] A rule editing and testing module 53 is used to receive editing operations of users on the visual rule editing platform, edit rules through the visual rule editing platform, and perform simulation tests on the rules;

[0235] The business rule file packaging module 54 is used to package the rules that have passed the test into a business rule file, and distribute the business rule file to the super device side or the cloud side for execution according to actual needs;

[0236] The continuous optimization and upgrade module 55 is used to continuously optimize the functions and performance of the visual rule orchestration platform according to user feedback and system operation status.

[0237] Furthermore, if Figure 3 As shown, based on the above-mentioned IoT device collaboration method and system based on the open source Hongmeng system, the present invention also provides a terminal accordingly, and the terminal includes a processor 10, a memory 20 and a display 30. Figure 3 Only some components of the terminal are shown, but it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0238] In some embodiments, the memory 20 may be an internal storage unit of the terminal, such as a hard disk or memory of the terminal. In other embodiments, the memory 20 may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the terminal. Furthermore, the memory 20 may also include both an internal storage unit of the terminal and an external storage device. The memory 20 is used to store application software and various types of data installed on the terminal, such as program code of the installation terminal. The memory 20 may also be used to temporarily store data that has been output or is to be output. In one embodiment, an IoT device collaboration program 40 based on an open source Hongmeng system is stored on the memory 20, and the IoT device collaboration program 40 based on an open source Hongmeng system can be executed by the processor 10, thereby realizing the IoT device collaboration method based on an open source Hongmeng system in this application.

[0239] In some embodiments, the processor 10 can be a central processing unit (CPU), a microprocessor or other data processing chip, used to run the program code or process data stored in the memory 20, such as executing the IoT device collaboration method based on the open source Hongmeng system.

[0240] In some embodiments, the display 30 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, etc. The display 30 is used to display information on the terminal and to display a visual user interface. The components 10-30 of the terminal communicate with each other via a system bus.

[0241] In one embodiment, when the processor 10 executes the IoT device collaboration program 40 based on the open source Hongmeng system in the memory 20, the steps of the IoT device collaboration method based on the open source Hongmeng system as described above are implemented.

[0242] The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores an Internet of Things device collaboration program based on the open source Hongmeng system, and when the Internet of Things device collaboration program based on the open source Hongmeng system is executed by a processor, the steps of the Internet of Things device collaboration method based on the open source Hongmeng system as described above are implemented.

[0243] In summary, the present invention provides an IoT device collaboration method, system, terminal and computer-readable storage medium based on the open source Hongmeng system, the method comprising: building an IoT device operating environment based on the open source Hongmeng system; designing a visual rule orchestration platform based on the IoT device operating environment; receiving user editing operations on the visual rule orchestration platform, editing rules through the visual rule orchestration platform, and performing simulation tests on the rules; packaging the rules that pass the test into business rule files, and distributing the business rule files to the super device side or cloud side for execution according to actual needs; and continuously optimizing the functions and performance of the visual rule orchestration platform according to user feedback and system operation. The present invention combines the open source Hongmeng system with super device rule orchestration technology, simplifies the rule orchestration process, makes the management and control of IoT devices more convenient and efficient, and realizes efficient collaboration and intelligent control between IoT devices.

[0244] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or terminal including the element.

[0245] Of course, those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware (such as a processor, a controller, etc.) through a computer program, and the program can be stored in a computer-readable storage medium that can be read by a computer, and the program can include the processes of the above-mentioned method embodiments when executed. The computer-readable storage medium can be a memory, a disk, an optical disk, etc.

[0246] It should be understood that the application of the present invention is not limited to the above examples. For ordinary technicians in this field, improvements or changes can be made based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to the present invention.

Claims

1. A method for coordinating IoT devices based on the open source Hongmeng system, characterized in that: The IoT device collaboration method based on the open source Hongmeng system includes: Build an operating environment for IoT devices based on the open source Hongmeng system; Based on the IoT device operating environment, a visual rule orchestration platform is designed; Receiving editing operations of users on the visual rule orchestration platform, editing rules through the visual rule orchestration platform, and performing simulation tests on the rules; Package the rules that pass the test into business rule files, and distribute the business rule files to the super device side or the cloud side for execution according to actual needs; Based on user feedback and system operation status, the functions and performance of the visual rule orchestration platform are continuously optimized.

2. The IoT device collaboration method based on the open source Hongmeng system according to claim 1 is characterized in that: The IoT device operating environment includes: hardware equipment, software framework, communication protocol, data storage and processing.

3. The IoT device collaboration method based on the open source Hongmeng system according to claim 1 or 2 is characterized in that: The IoT device operating environment is built based on the open source Hongmeng system, specifically including: Develop or adapt device drivers to adapt the open source Hongmeng system to IoT devices, so that IoT devices can work normally on the open source Hongmeng system; Configure network services in the open source Hongmeng system and set up network communication protocols to ensure that IoT devices can exchange data effectively over the network; Deploy the open source Hongmeng system to IoT devices. For distributed systems, configure the distributed service framework of the open source Hongmeng system to support collaborative work between devices. Build middleware and services on the open source Hongmeng system to achieve device discovery, registration, data reporting and command issuance; Implement security mechanisms in the system, including device authentication, data encryption, and access control, to ensure system stability and data security; Integrate the open source Hongmeng system with upper-level applications so that the system receives instructions from upper-level applications and performs corresponding operations.

4. The IoT device collaboration method based on the open source Hongmeng system according to claim 1 is characterized in that: The design visualization rule arrangement platform specifically includes: Conduct demand analysis and planning based on the target user groups to determine the functions that the platform needs to support; Build a set of standardized UI component libraries to build rule arrangement interfaces; The drag-and-drop component allows users to connect different devices or services by dragging, allows users to combine multiple rules into a business process, and designs clear status indications; Define the data structure, rule parsing, verification and execution logic of the rules, design the database model, and store the rules created by users and device status information; Design interfaces and interaction logic, develop API interfaces and conduct integration testing; Develop a visual editor to support users to compose rules through a graphical interface, provide a simulation environment for users to test the effectiveness of rules before deployment, and design the packaging function of rule files; Pass security and compatibility tests to ensure data security during rule editing and execution and to ensure platform compatibility with different devices and operating systems; Collect user feedback on the platform, identify problems and areas for improvement, and optimize functions and improve performance based on the feedback.

5. The IoT device collaboration method based on the open source Hongmeng system according to claim 1 is characterized in that: The rules include: event triggering rules, condition judgment rules, action execution rules, device linkage rules and data processing rules; The editing of rules through the visual rule arrangement platform and the simulation test of the rules specifically include: According to the user's selection operation, select the rule type to be created on the visual rule arrangement platform; Drag pre-defined rule components to the workspace and use connecting lines to connect the components to form a logical flow; Open the property configuration window and set the specific parameters of the rule in the property configuration; Set the specific conditions for triggering the action and specify the action to be performed; After the rule editing is completed, a test scenario is created on the visual rule orchestration platform, parameters are configured for the test scenario, and a simulation test is triggered, which will be executed in the test scenario according to the orchestrated rule logic; During the test execution process, monitor the execution of each rule and check whether the output after the rule execution meets the expected results to ensure that the rule works as expected.

6. The IoT device collaboration method based on the open source Hongmeng system according to claim 1 is characterized in that: The distributing the business rule file to the super device side or the cloud side for execution specifically includes: The business rule file is downloaded to the local storage of the super device side. The operating system or specific software on the super device side parses the rule file and executes the rules. The super device side performs corresponding actions according to the rules. Or upload the business rule file to the cloud side, the application or service on the cloud side parses the rule file and executes the rules, and the cloud side communicates with the device to send instructions or collect data.

7. The IoT device collaboration method based on the open source Hongmeng system according to claim 1 is characterized in that: The functions and performance of the visual rule orchestration platform are continuously optimized based on user feedback and system operation status, specifically including: Collect user experience and suggestions, and monitor system usage; Analyze user feedback, identify common problems and user needs, and diagnose system bottlenecks and potential errors through system logs and performance monitoring data; Develop specific optimization plans based on the analysis results; Develop and test software according to the optimization plan, update the system and deploy improved functions; After the update is released, continue to collect user feedback and system operation data to verify the optimization effect.

8. An IoT device collaboration system based on the open source Hongmeng system, characterized in that: The IoT device collaboration system based on the open source Hongmeng system includes: System environment building module, used to build the operating environment of IoT devices based on the open source Hongmeng system; A visualization platform development module, used to design a visualization rule orchestration platform based on the IoT device operating environment; A rule editing and testing module, used to receive editing operations of users on the visual rule editing platform, edit rules through the visual rule editing platform, and perform simulation tests on the rules; A business rule file packaging module is used to package the rules that have passed the test into a business rule file, and distribute the business rule file to the super device side or the cloud side for execution according to actual needs; The continuous optimization and upgrade module is used to continuously optimize the functions and performance of the visual rule orchestration platform based on user feedback and system operation status.

9. A terminal, characterized in that: The terminal includes: a memory, a processor, and an IoT device collaboration program based on the open source Hongmeng system stored in the memory and executable on the processor. When the IoT device collaboration program based on the open source Hongmeng system is executed by the processor, the steps of the IoT device collaboration method based on the open source Hongmeng system as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores an IoT device collaboration program based on the open source Hongmeng system. When the IoT device collaboration program based on the open source Hongmeng system is executed by the processor, the steps of the IoT device collaboration method based on the open source Hongmeng system as described in any one of claims 1 to 7 are implemented.

Images