WO2023193470A1

WO2023193470A1 - Service management method and system, and related device

Info

Publication number: WO2023193470A1
Application number: PCT/CN2022/139520
Authority: WO
Inventors: 董超伟; 杜娟
Original assignee: 华为云计算技术有限公司
Priority date: 2022-04-07
Filing date: 2022-12-16
Publication date: 2023-10-12
Also published as: CN116938988A

Abstract

A service management method and system, and a related device, which are used in the fields of information technology and cloud services. A service management server can communicate with a demand end and a destination end. On one hand, the service management server provides an orchestration function and an orchestration component of a service control logic to the demand end, so that a user of the demand end can visually develop an application on the basis of control requirements of the destination end, thereby lowering the development threshold, reducing the cost, and improving the application development efficiency; on the other hand, the service management server deploys the application orchestrated by the user in the destination end, so that there is no need to install and debug the application offline, the application can also be updated in time in a cloud, and the function of the device in the Internet can be conveniently controlled.

Description

A business management method, system and related devices

This application claims priority to the Chinese patent application submitted to the China Patent Office on April 7, 2022, with application number 202210360609.4 and the application title "A business management method, system and related devices", the entire content of which is incorporated by reference. in this application.

Technical field

This application relates to the fields of information technology and cloud services, and in particular, to a business management method, system and related devices.

Background technique

In recent years, with the advent of the Internet of Everything era and the popularization of wireless networks, the number of edge devices, terminals and other devices and the amount of data they generate have increased dramatically. According to the Internet Data Center (IDC) forecast, by 2025, the number of edge devices, terminals and other devices will reach approximately 40 billion, with industry, automobiles, smart homes, smart wearables, etc. leading the list. Among them, devices at the edge of the network provide powerful computing resources and provide real-time, flexible and fast decision-making based on industrial big data analysis for industrial Internet applications, which greatly promotes economic development.

As the functions of devices in the Industrial Internet become more and more diverse, the demand for remote control of device functions will continue to increase. At present, the control of devices on the Internet is generally implemented through applications. The application indicates the settings of the business logic of the device, so that the device can be controlled to complete the corresponding business. These applications are generally developed separately offline, with code development, compilation, packaging and deployment based on the terminal software and hardware platform. This method of generating applications has a complicated development process and a relatively high technical threshold. It requires R&D personnel to have various professional skills such as configuring software and hardware environments, development drivers, and everyone's development frameworks. It increases the cost of application development and does not meet the needs of users.

Therefore, in the industrial Internet scenario, how to conveniently control the functions of devices in the network is a hot issue being studied by those skilled in the art.

Contents of the invention

Embodiments of the present application provide a business management method, system and related devices, which can conveniently control the functions of devices on the Internet.

In the first aspect, embodiments of the present application provide a business management method, including:

Provide a component orchestration interface and control component resources. The component orchestration interface is used to orchestrate the control components that the target application depends on;

Generate metadata of the target application according to the control components arranged in the component arrangement interface;

providing metadata of the target application to the target device, the metadata of the target application being used to run the target application;

A control component on which the target application depends is provided to the target device, and the control component on which the target application depends is used to run the target application.

The above methods can be implemented by the cloud. The above method can be used to control the business functions of the device. Devices here include edge devices and/or end devices. When the device is a terminal device, it can include a Direct Digital Controller (DDC). Among them, DDC is a device that implements control logic based on a processor and controller. It can receive signals output by sensors, contacts or other instruments, process these signals, and output control signals to external devices. The output control signal can be used to start/stop the machine, open/close the valve, open/close the valve, or perform complex actions according to the program instructions, etc.

Metadata, also known as intermediary data and relay data, is used to describe information about data attributes. In this embodiment of the present application, metadata is used to describe the business process (or processing logic) of the application. For example, metadata can be used to describe the calling relationship and/or the transfer relationship between components.

A control component (node) is a code fragment or compiled binary file used to implement one or several functions. It is usually pre-defined or pre-encapsulated. Optionally, the component may be a function, algorithm (for example, a sorting algorithm), a framework, a software module, a packaged tool, a logic control component, or a sensor control component (for example, reading the temperature measured by a temperature sensor), etc. Optionally, the control component in the embodiment of the present application follows the development standard of electronic device logic control. Taking the electronic device including DDC as an example, the control component follows the DDC logic control standard and can be used to implement the control logic on the DDC.

In the embodiment of this application, the cloud can connect the demand side and the destination side. On the one hand, the cloud provides the orchestration function and orchestration components of business control logic to the demand side, so that users on the demand side can visually develop applications based on the control requirements for the destination side. Lowering the development threshold, reducing costs, and improving the efficiency of application development; on the other hand, the cloud deploys user-orchestrated applications on the destination (the aforementioned electronic devices, such as edge devices and terminal devices), without the need for offline installation and debugging of applications. It can also be deployed and applied in electronic devices in a timely manner to conveniently control the functions of devices on the Internet.

This solution can further be applied to cloud-edge-end collaboration systems. The cloud-edge-end collaboration system includes clouds, edge devices, and terminal devices. The terminal devices are connected to the cloud through edge devices. The edge device and the terminal device are the aforementioned electronic devices. Through the embodiments of the present application, the functions of the edge device and the terminal device can be conveniently controlled.

In addition, by providing control components to users, the reuse of control components can be achieved, preventing users from repeatedly developing codes for the same functions when developing applications, reducing costs and improving application development efficiency. Especially for DDC, computing resources and storage resources in DCC are usually limited, and DDC involves a variety of controls on sensors, logic gates, and electrical components. The security and professionalism requirements in the application development process are high. Through the embodiments of this application, the functional code blocks involved in DDC are encapsulated as control components, allowing users to flexibly generate applications safely and reasonably based on visual control components, improving code development efficiency. Without changing the hardware firmware, the control logic program in the field controller (DDC) can be downloaded and updated through the cloud, which improves the user experience.

In a possible implementation of the first aspect, the method further includes:

A running engine instance is provided to the target device, and the running engine instance is used to provide an isolation environment for running the target application.

The above explains the running mode of the application in this application. During the application running process, there is no need to deploy and run the application through the image package or installation package. Instead, the application is run based on the running engine instance and according to the metadata corresponding to the application and the components that the application depends on. . In this way, the device can realize component reuse by running engine instances, thereby further improving application operation efficiency and improving the service quality of the device. Running engine instances can form a relatively isolated environment to avoid interference from other environments within the device and improve system stability.

In yet another possible implementation of the first aspect, the method further includes:

Control the runtime engine instance. That is: the cloud can modify, restart, or synchronize the configuration of the running engine instance. In this way, the configuration of the running engine instance can be adjusted and the application running environment can be optimized without updating the hardware of the electronic device itself, thereby improving system stability and controlling the electronic device conveniently and safely.

In one possible design, the cloud can modify the configuration of the running engine instance. Consider a possible situation. Since different electronic devices may have different hardware facilities, there are differences in the resources they can provide to the running engine instances, which may cause the running engine instances deployed in different devices to malfunction. Through the embodiments of this application, You can modify the configuration of the running engine instance to solve faults, improve system flexibility and operability, and improve user experience.

In one possible design, the cloud restarts the running engine instance. Consider a possible situation where the running engine instance in the device fails or cannot be synchronized. The cloud can reload the running engine instance by restarting to improve the flexibility and operability of the system. In some scenarios, it can also avoid losing control of the device due to application lags or endless loops.

In one possible design, the cloud can perform a patch upgrade on the running engine instance to eliminate vulnerabilities in the running engine instance or improve the performance of the running engine instance.

In one possible design, the cloud can run applications in engine instances simultaneously. For example, the cloud deploys multiple applications to the running engine instance or the cloud upgrades the applications in the running engine instance.

Get the running status of the application in the running engine instance. In this way, the cloud can analyze useful information during application operation, monitor the application operation process, and facilitate monitoring of the implementation of the device's business functions.

Send application management information, where the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.

In the above embodiment, since the configuration modification, uninstallation and other operations of the application in the run engine instance can be controlled through messages, the control logic program of the target device can be updated without changing the hardware firmware, which facilitates the control of the target device. Take control.

Deploy the running application in the running engine instance in the target device.

In the embodiment of this application, the APP has multiple states, such as uninstalled, installed, and running. Among them, the running APP is an APP in a running state, and part of its process has been executed. In the above embodiment, the cloud provides a management function for running APPs, and running APPs can be deployed in batches in running engine instances by submitting tasks.

As a possible solution, you can first deploy the APP on a certain running engine instance, and then deploy the running engine instance to another running engine instance according to requirements. In this way, you can first verify the APP function through a certain (or several) running engine instance, and then migrate to other running engine instances when the operation meets expectations.

Optionally, the cloud can also record the engine list where a certain application is deployed, as well as the logs of the deployed application, to facilitate management and viewing, and improve the stability of the system.

A user interface for the running application is provided, and the user interface is used to display the running results of the running application. This makes it easy to analyze useful information during the application running process, monitor the application running process, and monitor the implementation of the business functions of the device.

In yet another possible implementation of the first aspect, the running engine instance includes a basic instruction process module, an uplink instruction module, a downlink instruction module and an engine core module. By dividing the services provided by the engine into different modules, each module can perform its own duties to complete the control and communication process, realize the interaction between electronic devices and the cloud, improve user experience, improve business implementation efficiency and system stability.

In yet another possible implementation of the first aspect, the basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink command module is used to send uplink commands;

A downlink instruction module is used to receive downlink instructions and call a communication interface to execute instructions. The communication interface is provided by the engine core module;

The engine core module includes one or more of the following modules: engine basic management module, executor, general service module and file system;

Among them, the engine basic management module is used to manage the communication interface of the running engine, manage the resources in the engine core module and configure engine parameters, the executor is used to perform operations related to application operation, and the general service The module is used to manage logs and messages, and the file system is responsible for persistent data storage and data reading.

In yet another possible implementation of the first aspect, the execution engine instance includes a context module, and the context module is used to store execution data of the current application.

In the above embodiments, the context module can be used to record application-related data, status, etc. For example, the context module can record the current data and status of the application when the application is interrupted. When the application resumes running, the previously saved data and status can be read from the context module, thereby continuing the previous business without reloading the application.

Receive uplink instructions from at least one running engine instance, where the uplink instructions include engine registration instructions, component installation request instructions, log upload instructions, heartbeat maintenance instructions, etc.

In the above implementation, the server can receive uplink instructions from the running engine instance. For example, through the engine registration directive of a running engine instance, the server can subscribe to record the registration information of the running engine. For another example, through the component installation request command, the server can deliver the corresponding component to the running engine instance. For another example, through the log upload command, the server can record the running log of the running engine instance to facilitate fault checking, version backtracking, etc. Similarly, through the heartbeat keep command, the server can maintain a connection with the running engine instance and record the online status of the running engine instance.

In yet another possible implementation of the first aspect, the engine registration instruction includes one or more of the following information: a license, a hardware platform instruction set, and a central processing unit (CPU) of the at least one running engine instance. Architecture, operating system properties, or kernel version, etc.

In yet another possible implementation of the first aspect, the heartbeat maintenance instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the at least one running engine instance space usage, etc.

In yet another possible implementation of the first aspect, the target device includes a direct digital controller DDC.

In yet another possible implementation of the first aspect, the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-differential (PID) controller component, a thermodynamic component, an optical component One or more of the components or air quality detection components.

The above describes some types of components provided by the embodiments of the present application. Since the target device may involve a variety of controls on sensors, logic gates, and electrical components, the application development process requires high security and professionalism. The embodiment of the present application encapsulates functional code blocks related to functions and thermodynamic devices into control components, allowing users to flexibly generate applications safely and reasonably based on visual control components.

In yet another possible implementation of the first aspect, the target device is used to complete one or more of the following business functions:

Variable air volume VAV system control, refrigeration unit control, air conditioning water circulation system control, air conditioning box frequency conversion automatic air volume adjustment, cooling tower cooling fan control, lighting control, or electrical equipment control, etc.

In yet another possible implementation of the first aspect, communication with the target electronic device is performed through wireless communication technology. For example: global system for mobile communications (GSM), general packet radio service (GPRS), universal mobile telecommunications system (UMTS), LTE, hypertext transfer protocol (hypertext wireless access type technologies such as transfer protocol, HTTP), vehicle Ethernet (scalable service-oriented middleware over IP, SOME/IP) or 5G.

Communicate with the runtime engine instance through the MQTT protocol. Among them, MQTT is a lightweight communication protocol based on Transmission Control Protocol/Internet Protocol (TCP/IP) protocol. During the MQTT communication process, the MQTT broker (or server) and the client are used. The MQTT Broker is responsible for receiving the network connection from the client and processing the client's subscription/unsubscription and message publishing (Publish) requests. When there are multiple subscribers, messages published by the client can also be forwarded to other subscribers.

Since MQTT is a lightweight protocol and the client is relatively small, it does not need to consume too much storage space and computing resources when deployed in the target device, which can improve the deployment and communication efficiency of running engine instances.

Communicates with the running engine instance through the COAP protocol.

COAP is used on devices with limited resources. It simplifies the message format of communication and has the advantages of lightweight and low power consumption. When deployed in the target device (especially devices with limited storage and computing resources such as DDC) There is no need to consume too much storage space and computing resources, thereby improving the efficiency of controlling the target device.

In the second aspect, embodiments of the present application provide a business management system. The business management system includes a server deployed in the cloud and a target device, wherein:

The cloud is used to provide a component orchestration interface and control component resources, and the component orchestration interface is used to orchestrate control components that the target application depends on;

The cloud is also configured to generate metadata of the target application according to the control components arranged in the component arrangement interface;

The cloud is further configured to provide metadata of the target application to the target device, and the metadata of the target application is used to run the target application;

The cloud is further configured to provide the target device with a control component that the target application depends on, and the control component that the target application depends on is used to run the target application;

The electronic device is configured to run the target application according to the metadata of the target application and the target application dependency control component.

Wherein, the cloud is used to control the business functions of the target device. Specifically, on the one hand, the cloud provides the orchestration function and orchestration components of business control logic to the demand side, so that users on the demand side can visually develop applications based on the control requirements for the destination side, lowering the development threshold, reducing costs, and improving the efficiency of application development. Efficiency; on the other hand, the cloud deploys user-orchestrated applications on the destination (the aforementioned electronic devices, such as edge devices and terminal devices). There is no need to install and debug applications offline, and applications can be deployed in electronic devices in a timely manner. This allows you to conveniently control the functions of devices on the Internet.

In a possible implementation of the second aspect, the cloud is further configured to provide a running engine instance to the target device, and the running engine instance is used to provide an isolation environment for running the target application.

In yet another possible implementation of the second aspect, the cloud is also used for:

Control the running engine instance, wherein controlling the running engine instance includes one or more of the following operations:

Modify the configuration of the running engine instance, restart the running engine instance, perform patch upgrades on the running engine instance, and synchronize applications in the running engine instance.

Get the running status of the application in the running engine instance.

A user interface for the running application is provided, and the user interface is used to display the running results of the running application.

In yet another possible implementation of the second aspect, the running engine instance includes a basic instruction process module, an uplink instruction module, a downlink instruction module and an engine core module.

In yet another possible implementation of the second aspect, the basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink command module is used to send uplink commands;

In yet another possible implementation of the second aspect, the execution engine instance includes a context module, and the context module is used to store execution data of the current application.

Receive uplink instructions from at least one running engine instance, where the uplink instructions include engine registration instructions, component installation request instructions, log upload instructions, and heartbeat maintenance instructions.

In yet another possible implementation of the second aspect, the engine registration instruction includes one or more of the following information: a license, a hardware platform instruction set, and a central processing unit (CPU) of the at least one running engine instance. Architecture, operating system properties, or kernel version, etc.

In yet another possible implementation of the second aspect, the heartbeat maintenance instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the at least one running engine instance space usage, etc.

In yet another possible implementation manner of the second aspect, the target device includes a direct digital controller DDC.

In yet another possible implementation of the second aspect, the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-differential (PID) controller component, a thermodynamic component, an optical component One or more of the components or air quality detection components.

In yet another possible implementation of the second aspect, the target device is used to complete one or more of the following business functions:

In yet another possible implementation of the second aspect, the cloud includes message middleware, and the message middleware is used to implement communication with the target device.

In yet another possible implementation of the second aspect, the cloud communicates with the target electronic device through wireless communication technology.

In yet another possible implementation of the second aspect, the cloud communicates with the running engine instance through the MQTT protocol.

In yet another possible implementation of the second aspect, the cloud communicates with the running engine instance through the COAP protocol.

In a third aspect, embodiments of the present application provide a service management device. The service management device includes a processing unit and a communication unit. The service management device is used to implement the first aspect or any possible implementation manner of the first aspect. method described.

In a possible implementation of the third aspect, the communication unit is used to provide a component orchestration interface and control component resources, and the component orchestration interface is used to orchestrate control components that the target application depends on;

The processing unit is configured to generate metadata of the target application according to the control components arranged in the component arrangement interface;

The communication unit is further configured to provide metadata of the target application to the target device, and the metadata of the target application is used to run the target application;

The communication unit is further configured to provide the control component that the target application depends on to the target device, and the control component that the target application depends on is used to run the target application.

In yet another possible implementation of the third aspect, the communication unit is also used to:

In yet another possible implementation of the third aspect, the processing unit is also used to:

Control the runtime engine instance. Optionally, controlling the running engine instance includes one or more of the following operations:

Get the running status of the application in the running engine instance.

In yet another possible implementation of the third aspect, the running engine instance includes a basic instruction flow module, an uplink instruction module, a downlink instruction module and an engine core module.

In yet another possible implementation of the third aspect, the basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink command module is used to send uplink commands;

In yet another possible implementation of the third aspect, the execution engine instance includes a context module, and the context module is used to store execution data of the current application.

In yet another possible implementation of the third aspect, the engine registration instruction includes one or more of the following information: a license, a hardware platform instruction set, and a central processing unit (CPU) of the at least one running engine instance. Architecture, operating system properties, kernel version.

In yet another possible implementation of the third aspect, the heartbeat maintenance instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the at least one running engine instance space usage in .

In yet another possible implementation manner of the third aspect, the target device includes a direct digital controller DDC.

In yet another possible implementation of the third aspect, the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-derivative PID controller component, a thermodynamic component, an optical component or an air quality detection component. one or more of them.

In yet another possible implementation of the third aspect, the target device is used to complete one or more of the following business functions:

Variable air volume VAV system control, refrigeration unit control, air conditioning water circulation system control, air conditioning box frequency conversion automatic air volume adjustment, cooling tower cooling fan control, lighting control, and electrical equipment control.

In yet another possible implementation manner of the third aspect, the service management apparatus includes message middleware, and the message middleware is used to implement communication with the target device.

In yet another possible implementation of the third aspect, the communication unit is also configured to communicate with the target electronic device through wireless communication technology.

In yet another possible implementation of the third aspect, the communication unit is also configured to communicate with the running engine instance through the MQTT protocol.

In yet another possible implementation of the third aspect, the communication unit is further configured to communicate with the running engine instance through the COAP protocol.

In a fourth aspect, embodiments of the present application provide a computing device, where the computing device includes a processor and a memory. The processor is configured to execute the computer program stored in the memory, so that the computing device implements the method described in any one of the first aspects.

In a possible implementation of the fourth aspect, the processor is configured to execute the computer program stored in the memory to implement the following operations:

In yet another possible implementation of the fourth aspect, the processor is also used to:

Get the running status of the application in the running engine instance.

In yet another possible implementation manner of the fourth aspect, the computing device further includes a communication interface. The processor is also used for:

Application management information is sent through the communication interface, and the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.

In yet another possible implementation of the fourth aspect, the running engine instance includes a basic instruction flow module, an uplink instruction module, a downlink instruction module and an engine core module.

In yet another possible implementation of the fourth aspect, the basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink command module is used to send uplink commands;

In yet another possible implementation of the fourth aspect, the execution engine instance includes a context module, and the context module is used to store execution data of the current application.

Uplink instructions from at least one running engine instance are received through the communication interface, and the uplink instructions include engine registration instructions, component installation request instructions, log upload instructions, and heartbeat maintenance instructions.

In yet another possible implementation of the fourth aspect, the engine registration instruction includes one or more of the following information: a license, a hardware platform instruction set, and a central processing unit (CPU) of the at least one running engine instance. Architecture, operating system properties, kernel version.

In yet another possible implementation manner of the fourth aspect, the heartbeat maintenance instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the at least one running engine instance space usage in .

In yet another possible implementation manner of the fourth aspect, the target device includes a direct digital controller DDC.

In yet another possible implementation of the fourth aspect, the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-derivative PID controller component, a thermodynamic component, an optical component or an air quality detection component. one or more of them.

In yet another possible implementation of the fourth aspect, the target device is used to complete one or more of the following business functions:

In yet another possible implementation manner of the fourth aspect, the computing device includes message middleware, and the message middleware is used to implement communication with the target device.

Communicate with the target electronic device through the communication interface through wireless communication technology.

Communicate with the running engine instance through the MQTT protocol through the communication interface.

Communicate with the running engine instance through the COAP protocol through the communication interface.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium in which instructions are stored, and the instructions are used to implement the method described in any one of the foregoing first aspects.

In a sixth aspect, the present application provides a computer program product. The computer program product includes computer instructions, and the instructions are used to implement the method described in any one of the foregoing first aspects.

For the beneficial effects of the technical solutions provided in the second to sixth aspects of the present application, reference can be made to the beneficial effects of the technical solutions of the first aspect, and will not be described again here.

Description of the drawings

The drawings needed to be used in describing the embodiments will be briefly introduced below.

Figure 1 is a schematic architectural diagram of a business management system provided by an embodiment of the present application;

Figure 2A is a schematic diagram of the system architecture in a cloud-edge collaboration scenario provided by an embodiment of the present application;

Figure 2B is a schematic diagram of the system architecture in another cloud-edge collaboration scenario provided by the embodiment of the present application;

Figure 3 is a schematic structural diagram of an example of an operating engine provided by an embodiment of the present application;

Figure 4 is a schematic architectural diagram of yet another business management system provided by an embodiment of the present application;

Figure 5 is a schematic architectural diagram of a service management device provided by an embodiment of the present application;

Figure 6 is a schematic architectural diagram of yet another business management system provided by an embodiment of the present application;

Figure 7 is a schematic flow chart of a business management method provided by an embodiment of the present application;

Figure 8 is a schematic diagram of an interface provided by an embodiment of the present application;

Figure 9 is a schematic diagram of the format of metadata of an application provided by an embodiment of the present application;

Figure 10 is a schematic flow chart of a business management method provided by an embodiment of the present application;

Figure 11 is a schematic structural diagram of a service management device provided by an embodiment of the present application;

Figure 12 is a schematic structural diagram of a computing device provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

To facilitate understanding, the following exemplarily provides a description of some concepts related to the embodiments of the present application for reference. As stated below:

Metadata: A type of information used to describe data attributes, also known as intermediary data and relay data. In this embodiment of the present application, metadata is used to describe the business process (or processing logic) of the application. For example, metadata can be used to describe the calling relationship and/or delivery relationship between components. As another example, metadata can be used to describe the execution sequence of components that the application depends on.

Component (node): a code fragment or compiled binary file used to implement one or several functions, usually pre-defined or pre-encapsulated. Optionally, components can be functions, algorithms, frameworks, software modules, packaged tools, etc. For example, applications based on node.js (a JavaScript runtime environment) rely on some nonde.js components to run. For example, they rely on the Express framework (a framework for quickly building websites) and the Path module (which provides conversion file paths). tools) and other components.

Application business process: A series of activities completed by different functional modules in order to complete business functions. The functional modules here include components, and may further include code, binary files, etc. that are not encapsulated as components. The business process of the application describes one or more of the component's calling relationship, transfer relationship, data flow relationship, or which code fragment of the component needs to be executed.

Container: A virtualization technology in computer operating systems. This technology allows processes to run in relatively independent and isolated environments (including independent file systems, namespaces, resource views, etc.). Container technology is widely used in service scenarios in the field of cloud computing.

Runtime engine instance: A runtime engine instance is one or more instantiated runtime engines obtained based on the runtime engine template or the runtime engine design. The running engine instance provides the software environment required for application (application, APP) to run. The running engine instance provides basic running capabilities independent of specific hardware and protocols, and can run the APP according to the business process corresponding to the APP and the components that the APP depends on.

Optionally, the running environment provided by the running engine instance includes a Node.js-based environment. Alternatively, the environment provided by the running engine instance can also include environments based on development languages such as java, python, and go. The platform it is based on can be a Linux platform, Windows or other platforms. The embodiments of this application are applicable to various platforms, various development environments, and development languages.

Message queuing telemetry transport (MQTT) protocol: a lightweight communication protocol based on the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol. During the MQTT communication process, the MQTT broker (or server) and the client are used. The MQTT Broker is responsible for receiving the network connection from the client and processing the client's subscription/unsubscription and message publishing (Publish) requests. In some multi-server scenarios, MQTT Broker will forward messages published by the client to other subscribers.

Constrained application protocol (COAP): It is a lightweight communication protocol that is usually used on devices with limited resources. It simplifies the message format of communication and has the advantages of lightweight and low power consumption. .

Middleware: A type of software between application systems and system software. It uses the basic services (functions) provided by system software to connect various parts of the application system or different applications on the network. That is: software that provides common services and functions for applications. Data management, application services, messaging, authentication, and application programming interface (API) management usually go through middleware.

Please refer to Table 1. Table 1 is information about possible middleware provided by the embodiment of this application. For example, in the embodiment of this application, the cloud may contain the middleware of the Euler OS (EulerOS), thereby providing a running engine instance based on EulerOS, or may be used to develop EulerOS-based applications, thereby being suitable for EulerOS-based devices. business control.

For another example, in this embodiment of the present application, the cloud may include remote dictionary service (remote dictionary server, Redis) middleware, thereby enabling storage of data in key-value (key-value, KV) format.

For another example, in the embodiment of this application, the cloud may include cloud container engine (cloud container engine, CCE) middleware. CCE is used to provide a highly scalable, high-performance enterprise-level Kubernetes cluster and support running Docker containers.

Table 1 Middleware information

Among them, the above-mentioned middleware can be used to implement the technical solutions of the embodiments of this application. Of course, the above middleware is only an example, and the specific implementation process may also include more or less middleware, or other versions of middleware. The embodiments of this application are also applicable to situations where other middleware is included.

Embodiments of the present application provide a business management server and a business management system. The business management server can connect the demand side and the destination side. On the one hand, the business management server provides the orchestration function and orchestration components of the business control logic to the demand side, so that the demand side Users can visually develop applications based on the control requirements for the destination end, lowering the development threshold, reducing costs, and improving the efficiency of application development; on the other hand, the business management server deploys the user-orchestrated applications on the destination end (the aforementioned electronic equipment, For example, in edge devices and terminal devices), there is no need to install and debug applications offline. Applications can also be updated in the cloud in a timely manner, and the functions of devices on the Internet can be easily controlled.

The system architecture applied in the embodiments of this application is introduced below. It should be noted that the system architecture and business scenarios described in this application are for the purpose of explaining the technical solution of this application more clearly and do not constitute a limitation on the technical solution provided by this application. Those of ordinary skill in the art will know that with the system architecture With the evolution of the Internet and the emergence of new business scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

Please refer to Figure 1. Figure 1 is a schematic architectural diagram of a business management system 10 provided by an embodiment of the present application. The business management system 10 includes a cloud 101 and devices.

Cloud 101, also known as server, cloud platform, etc., is a device with computing capabilities and communication capabilities. It usually concentrates more computing resources, which can include physical devices or virtual devices. For example, the cloud 101 can be deployed in one or more servers (such as blade servers, rack servers, etc.). For another example, the cloud 101 may include one or more virtual machines, containers, etc. Cloud 101 can provide a variety of services for electronic devices, such as APP installation services, APP upgrade services, component download services, etc. It is a device with computing and communication capabilities. In the embodiment of this application, the cloud 101 can externally provide a component orchestration interface and control component resources, and receive control components and generate applications arranged by users on the component orchestration interface. Applications generated by the cloud 101 can be deployed and run in electronic devices to achieve the purpose of controlling the functions of the electronic devices.

A device is a device with computing and communication capabilities that is used to complete several business functions or control logic. The number of devices can be one or multiple. For convenience of description, device 102 is used as an example to describe the device below. It should be understood that in certain application scenarios or certain network types, the names of devices with similar functions may not be called devices. The solutions provided by the embodiments of this application are applicable to devices that can deploy applications. In addition, the target device below in this application includes one or more devices. For example, the target device may be device 102. Optionally, the target device can also be a device in the system that meets a certain condition, for example, a device managed by a certain tenant, a device selected by the user, or a device located at a certain location.

For example, device 102 may be located at the edge of a network or at an endpoint of a network. The two options are introduced below:

As a possible solution, the device 102 may include an edge device in the network. Edge devices are devices that provide an entry point into a network. For example, electronic equipment may include routers, routing switches, integrated access devices (IADs), multiplexers, metropolitan area network (MAN) access devices, or wide area networks (WAN) ) one or more of the access devices, etc.

As another possible solution, the device 102 may include a terminal device in the network. Terminals can be thought of as endpoints of a network, typically acting as input and/or output devices. The electronic devices in the embodiments of this application can be used in a variety of application scenarios, such as the following application scenarios: smart buildings, smart cities, smart homes, industrial Internet, Internet of Vehicles, industrial control, driverless driving, transportation safety, or the Internet of Things (Internet of things, IoT), etc. For example, electronic devices include but are not limited to home devices (smart TVs, smart refrigerators, or smart security devices, etc.), computers, handheld devices (such as tablets, or mobile phones, etc.), wearable devices (smart eyes, or smart watches, etc.), Sensors (such as cameras, lidar, or millimeter-wave radar, etc.), entertainment equipment (karaoke equipment, virtual reality equipment, or game consoles, etc.), mobile tools (vehicles, aircraft, ships, or drones, etc.), etc.

As a possible implementation, the device 102 can be used for one or more of the following business functions:

Variable air volume (VAV) system control, refrigeration unit control, air conditioning water circulation system control, air conditioning box frequency conversion automatic air volume adjustment, cooling tower cooling fan control, lighting control, or electrical equipment control, etc.

Optionally, the service management system 10 may also include user equipment 103. The user device 103 is a device that interacts with the user, has output/output capabilities, computing capabilities, can present an interface, and receive data input by the user. For example, the user device 103 can present a component arrangement interface to the user, in which the user can select control components, arrange control components, etc. The user device 103 receives the arrangement of control components input by the user, and provides the control components arranged in the component arrangement interface to the cloud 101 .

Optionally, the user equipment 102 may include, for example, a handheld terminal, a wearable device, a vehicle, a robot, and other independent devices, or may be a component (such as a chip or an integrated circuit) included in an independent device. For example, when the terminal device is a handheld terminal, it may be a mobile phone (mobile phone), a tablet computer (pad), a computer (such as a notebook computer, a handheld computer, etc.). Optionally, the number of user equipment may be one or multiple. This application does not limit the number of user equipment.

It should be noted that the above-mentioned communication between the cloud and the device, between the device and the device, and between the cloud and the user device can be carried out through wired, wireless or a combination of wired and wireless.

For example, cloud 101 may communicate with device 102 through wireless communication technology. Wireless communication technologies include but are not limited to global system for mobile communications (GSM), general packet radio service (GPRS), universal mobile telecommunications system (UMTS), LTE, Wireless access type technologies such as hypertext transfer protocol (HTTP), vehicle Ethernet (scalable service-oriented middleware over IP, SOME/IP) or 5G.

In the embodiment of this application, the cloud 101 can be used to control the business functions of the device, and the cloud 101 can connect the demand end (such as the user equipment 103) and the destination end (such as the device 102). On the one hand, Cloud 101 provides the orchestration function and orchestration components of business control logic to the demand side, so that users on the demand side can visually develop applications based on the control requirements of the destination side, lowering the development threshold, reducing costs, and improving the efficiency of application development; On the other hand, Cloud 101 deploys user-orchestrated applications on the destination, eliminating the need to install and debug applications offline. It can also deploy applications in electronic devices in the cloud in a timely manner, thereby conveniently controlling the functions of devices on the Internet.

To facilitate understanding, two application scenarios of the embodiments of the present application are exemplarily described below.

Figure 2A shows a schematic diagram of the system architecture in a cloud-edge collaboration scenario according to the embodiment of the present application. The router in the network is the aforementioned device. Routers can provide routing and forwarding functions for the network, and the functions of the router can be realized through applications. The convenience of deploying applications in routers will directly affect the service quality of the network. Through the solution provided by the embodiments of this application, the cloud can obtain the application that needs to be deployed in the router based on the orchestration component, and provide the metadata and components of the application to the router, thus completing the deployment of the application. This deployment method does not require offline installation and debugging of applications, nor does it require replacement of the router's hardware firmware. It enables convenient control of the router's business functions and ensures network service quality.

Figure 2B shows a schematic diagram of the system architecture in another cloud-edge-device collaboration scenario according to the embodiment of the present application. Edge devices and terminals in the network are the aforementioned devices. The building contains multiple terminals, and these terminals complete their business functions in multiple spaces. When completing business functions, the terminal involves a variety of controls on sensors, logic gates, and electrical components. The application development process requires high security and professionalism. Through the embodiments of this application, functional code blocks involved in the terminal are encapsulated as control components, allowing users to flexibly generate applications safely and reasonably based on visual control components, improving code development efficiency. Without changing the hardware firmware, the control logic program in the field controller (DDC) can be downloaded and updated through the cloud, which improves the user experience.

Some possible designs are described below based on the embodiment shown in Figure 1 .

In one possible design, the cloud can provide a running engine instance to the device, and the running engine instance is used to provide an isolation environment for application running. A runtime engine instance can run an application through the business processes and components on which the application depends. In this way, components are reused between different applications through running engine instances. For applications that rely on the same components, the device does not need to obtain multiple identical components, thereby further improving application operating efficiency and improving the service quality of the device.

An exemplary architecture for running an engine instance is provided below. Figure 3 shows a schematic structural diagram of a possible running engine example provided by the embodiment of the present application. A running engine instance can include a basic instruction module, an uplink instruction module, a downlink instruction module, an engine core module, etc. The embodiment of this application divides the services provided by the engine into different modules, allowing each module to perform its own duties to complete the control and communication process, realize the interaction between the target device and the cloud, improve user experience, and improve business implementation efficiency and system stability.

The functions of each module in the running engine instance are introduced below:

(1) The basic command module is used to control the installation of the upstream command flow and the downstream command flow. For example, the basic command module contains the command management process, and the command flow is controlled through the command management process. Optionally, the basic instruction process can be a solidified process. For example, it cannot be updated after the running engine instance is released (or registered).

(2) The uplink command module is used to process uplink commands, such as packaging and sending of uplink commands.

For example, the uplink command may include one or more of an engine registration command, a component request command (or a component installation command), a log upload command, a heartbeat maintenance command, and the like. The cloud can obtain the current status of the target device through uplink commands, making it easier for the cloud to manage the target device. For example, through the engine registration directive of a running engine instance, the server can subscribe to record the registration information of the running engine. For another example, through the component installation request command, the server can deliver the corresponding component to the running engine instance. For another example, through the log upload command, the server can record the running log of the running engine instance to facilitate fault checking, version backtracking, etc. Similarly, through the heartbeat keep command, the server can maintain a connection with the running engine instance and record the online status of the running engine instance.

Optionally, the engine registration instruction includes one or more of the following information: license, hardware platform instruction set, CPU architecture of the at least one central processor running the engine instance, attributes of the operating system, or kernel version, etc.

Optionally, the heartbeat retention instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the space usage in the at least one running engine instance, or the local available node installation and the space size for process installation, etc.

(3) Downlink instruction module, used to process downlink instructions. Furthermore, the downstream instruction module can also call the communication interface to execute instructions. The communication interface here is provided by the engine core module.

For ease of understanding, some possible downward instructions are exemplarily listed below:

a. Component management instructions. For example, instructions used to implement the following functions: modify the content of the component, update the component version, install the component, uninstall the component, etc.

b.APP management instructions. For example, instructions used to implement the following functions: edit the business process of the APP, set the components that the APP depends on, install the APP, uninstall the APP, query the installed APP, modify the properties of the APP, obtain the running status of the APP, etc.

c. Engine management instructions. For example, instructions used to implement the following functions: modify the configuration parameters of the running engine instance, restart the running engine instance, etc.

d. Process management instructions. For example, instructions used to implement the following functions: modify the process of sending uplink instructions, modify the process of downlink instructions, add, delete, modify, check, stop, start, or restart the corresponding business process of the application, etc.

e. Heartbeat interval setting instructions. For example, the running engine instance is originally set to send heartbeat keep messages once every minute. The cloud can use the heartbeat interval setting instructions to modify the frequency of sending heartbeat keep messages to adapt to the current load of the running engine instance.

f. Uplink channel configuration parameter management instructions are used to configure channel-related parameters. For example, instructions used to implement the following functions: modify the frequency domain, time domain, etc. of the wireless channel.

(4) Engine core module, used to implement the core functions of running the engine. The engine core module includes one or more of the basic management module (or engine basic management module), executor, general service module and file system.

The basic management module is used to manage the communication interface of the running engine, manage the resources in the engine core module, or configure engine parameters, etc. As a possible solution, the basic management module may include one or more of engine configuration parameter management, component management, license management, process (Flow) management, engine communication interface management, or APP management. Among them, the engine configuration parameters include configuration parameters in the running engine instance, such as: log level, etc. The engine configuration parameter management module is used to configure various parameters of the engine. Component management is used to manage component resources available to the runtime engine. The license manages the permissions, licenses, etc. to run the engine. Process management is used to support the running process of the running engine. APP management is used to manage the applications available to the running engine instance. Optional, the engine communication interface can only be called locally.

Executors are used to perform operations related to application running. For example, metadata loading, component instantiation, process instantiation, and APP parsing execution. Optionally, the control component has an API registration interface corresponding to it, so that the control component can register component information with the running engine instance when loading.

Optionally, the executor can also include a context module, which is used to record application-related data, status, etc. In one possible solution, the context module can record (or store) the current data and status of the application. When the application resumes running, the previously saved data and status can be read from the context module, thereby continuing the previous business without restarting. Load the application.

As a possible solution, when the running engine instance runs the application, the executor loads the metadata corresponding to the application, instantiates the components the application depends on, and instantiates the business process corresponding to the application, thereby realizing parsing and execution of the application. During the application running process, the context module records the application running status to facilitate saving of the current application running status.

The running environment parameters provide the function of instantiating configuration parameters for engine initialization.

The general service module is used to provide general functions required by each module in the engine, such as logging, general processing functions for messages, etc. For example, a common service module can manage logs and messages.

The file system is responsible for persistent data storage and data reading.

In one possible design, when compiling and running an engine instance, different compilation scripts can be selected to compile and generate engines based on different basic libraries.

The following describes the deployment environment of the application engine instance. In one possible design, the runtime engine instance is deployed in a container of the device. Figure 4 shows an architectural schematic diagram of yet another possible business management system provided by an embodiment of the present application. The device is configured with one or more containers, such as virtualization container 1 and virtualization container 2. Among them, the running engine instance is deployed in virtualization container 1.

As shown in Figure 4, virtualization container 1 has computing resources and storage resources isolated from other environments. For example, virtualization container 1 has an independent central processing unit (CPU, a computing resource), memory One or more of (a storage resource), storage (a storage resource), and component resources (such as component libraries).

It can be seen that by virtualizing containers, you can configure applications in the device without being affected by other environments. For example, operations such as deployment and uninstallation of APP3 (or APP4) in virtualized container 2 are difficult to affect virtualized container 1, thereby enhancing the portability and security of the running engine instance and the applications in it, and improving system resource utilization. .

As a possible solution, the running engine instance can run the application based on the business process of the APP and the components that the APP depends on. For example, APP1 shown in Figure 4 depends on component a, component b, and component c. The running engine can run APP1 based on the business process of APP1 and components a, component b, and component c. Similarly, APP2 shown in Figure 4 depends on component b, component c, and component d, then the running engine can run APP1 based on the business process of APP2 and components b, component c, and component d. It can be seen that component b and component c can be reused between different APPs, thereby reducing the space occupied by the APP, suitable for nodes with limited resources, and improving application deployment efficiency.

Optionally, the device may also contain one or more management processes related to business functions. For example, Figure 4 exemplarily shows the field area network (FAN) network management and wide area network (wide area) included in the device. network, WAN) network management, firmware management, container management.

As a possible solution, when runtime engine instances are deployed on different devices, they may have different characteristics. For example, the edge engine runs in the edge device and is the operating environment of the edge device's App, providing APP deployment, upgrade, operation and maintenance support and other capabilities; the edge engine supports Linux and Windows operating systems, and supports deployment in virtual machines (Virtual machines). Machine, VM) and containers. For another example, the terminal-side engine runs in the terminal (such as a microcontroller or an embedded system, etc.) and is the operating environment of the terminal's App. It provides capabilities such as deployment, upgrade and operation and maintenance support of the App, and supports LiteOS and embedded Linux operations. system.

In some possible implementations, the cloud can control the running engine instance. Exemplarily, controlling the running engine instance includes one or more of the following operations: modifying the configuration of the running engine instance, restarting the running engine instance, performing patch upgrades on the running engine instance, synchronizing applications in the running engine instance, etc. . The following is an introduction to the case of cloud control running engine instance:

Case 1, the cloud can modify the configuration of the running engine instance. Consider a possible situation. Since different electronic devices may have different hardware facilities, there are differences in the resources they can provide to running engine instances, which may cause inconsistent loads of running engine instances deployed in different devices. Through the embodiments of this application, You can improve the flexibility and operability of the system and improve user experience by modifying the configuration of the running engine instance.

Case 2, the cloud can restart the running engine instance. For example, the cloud sends a restart command to the target device, and accordingly, the target device receives the restart command and restarts the running engine instance of the target device. Consider a possible situation where the running engine instance in the device fails or cannot be synchronized. The cloud can reload the running engine instance by restarting to improve the flexibility and operability of the system. In some scenarios, it can also avoid losing control of the device due to application lags or endless loops.

Case 3: The cloud can perform patch upgrades on the running engine instance. For example, the cloud sends a patch for the running engine instance to the target device. Correspondingly, the target device receives the patch for the running engine instance, and uses the patch to eliminate vulnerabilities in the running engine instance or improve the performance of the running engine instance.

Case 4, the cloud can synchronize the applications in the engine instance. For example, the cloud deploys multiple applications to the running engine instance or the cloud upgrades the applications in the running engine instance.

In one possible implementation, the cloud can manage applications in the running engine instance. For example, the cloud obtains the running status of the application in the running engine instance. In this way, the cloud can analyze useful information during application operation, monitor the application operation process, and facilitate monitoring of the implementation of the device's business functions. For another example, the cloud can send application management information to the device, and the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.

In a possible implementation, the cloud can deploy the running application in the running engine instance in the target device. In this way, the cloud can deploy running APPs in batches in the running engine instance by submitting tasks.

Specifically, the APP has multiple states, such as not installed, installed, and running. Among them, the running APP is an APP in a running state, and part of its process has been executed. In the above embodiment, the cloud provides a management function for running APPs, and running APPs can be deployed in batches in running engine instances by submitting tasks.

Further, the cloud can provide a user interface for the running application, and the user interface is used to display the running results of the running application. This makes it easy to analyze useful information during the application running process, monitor the application running process, and monitor the implementation of the business functions of the device.

The architecture of the running engine instance and the management of the running engine in the cloud are introduced above. The following introduces some possible cloud architectures.

In one possible design, the cloud can include multiple functional layers, and the multiple functional layers are used to provide multiple services respectively, so that the cloud supports business function control of the device. Figure 5 shows an architectural schematic diagram of a possible service management device provided by this application. The service management device may include the aforementioned cloud, or the service management device may be included in the cloud.

The business management device as shown in Figure 5 has multiple functional layers, among which the development and design layer is used to provide component orchestration interfaces and control component resources, the service layer is used to deploy applications in target devices, and the operation and maintenance layer is used to manage the The running environment and running status of the application on the target device.

As a possible implementation, the development and design layer can include APP development, component development and application management modules, where the APP development module can implement the APP's business process design, service component design, business rules, UI blocks, or Business variable configuration and other functions. Among them, business process design can be used to design the calling relationship, transfer relationship, data flow direction between the control components of the APP, or which code fragment of the control component needs to be executed, etc. The component development module can obtain metadata or native code, etc., and generate components through possible component development services. Of course, the component development module can also provide component design tools, open source components, etc. to facilitate users to obtain and generate control components. The component development module also provides the function of installation and upgrade, allowing users to update and configure components according to their own needs. The application management module is used to manage designed and developed applications. It can optionally manage development resources and assist in the engine operation and maintenance process.

The service layer can provide one or more of the following services: business process management services, edge-cloud collaboration services, and component development services.

Among them, business process management services include one or more services in process management, process testing, and metadata obfuscation. Process management can be used to manage the business processes corresponding to applications. For example, an APP can contain multiple processes, and the process management module can support process addition, deletion, modification, check, restart, stop, etc. The process testing module is used to test whether the application's business process meets expectations. The metadata obfuscation module is used to disrupt metadata, avoid source code leakage, and improve security.

Edge-cloud collaborative services can be used to implement engine registration, engine operation and maintenance, process delivery, license management, access authentication and other functions.

Component development services can implement one or more of the following functions: generating components based on metadata or native code (the "metadata generation component" service and the "native code generation component" service shown in Figure 5), through online Tool component building services, component testing, etc. Optionally, the component development service also includes a component warehouse, or the component development service can establish a connection with the component warehouse, and the component warehouse is used to store control components.

The operation and maintenance layer can provide one or more of the following services: basic command process, engine registration, component synchronization download, heartbeat maintenance, log upload, or running engine core and other modules. Among them, the core module of the run engine includes executors, process management, component management, or file systems, etc. Optionally, the core module of the running engine can be regarded as a running engine instance in the cloud. The running engine can be tested in the cloud or the application in the running engine example can be tested. For further optional modules included in the running engine core module, please refer to the functions of the running engine core module shown in Figure 3 .

Optionally, the cloud can provide running engine instances based on multiple hardware architectures or operating systems. For example, the cloud supports the management of devices with the following operating systems: Windows, Fedora, EluerOS, Ubuntu, LiteOS, x86, x64, arm64, armv7 wait.

It should be understood that what is shown in Figure 5 is an exemplary architectural description and is not intended to limit the functions of the cloud. During the specific implementation process, the cloud can contain more or fewer modules, or can provide more or fewer services.

As a possible solution, the cloud can also include message middleware, which is used to support wireless communication between the cloud and other devices.

Figure 6 shows an architectural schematic diagram of another possible business management system provided by an embodiment of the present application, including external resources, clouds, edge devices and terminals. Among them, the cloud can communicate with edge devices and/or terminals through message middleware. Optionally, when the cloud communicates with the terminal, it passes through the edge device.

In the system shown in Figure 6, the cloud can also provide one or more of the following services: component management, APP management, component graphical orchestration, application deployment and upgrade, engine instance management, online debugging, operation and maintenance management, etc. One or more items. Optionally, the cloud can also provide the above services through the container management tool kubernetes (k8s for short). For example, the cloud can implement its services based on k8s clusters, storage resources, network resources, and public cloud and/or private cloud infrastructure.

Further optionally, the cloud as shown in Figure 6 can be connected to external resources. For example, the cloud can provide access to the following resources (or services): external component warehouse, external application warehouse, external public services, or third-party docking services, etc. one or more of them.

The cloud as shown in Figure 6 can also provide running engine instances to edge devices or terminals. For example, the running engine instance of the edge node may include an APP management module, a debugging module and an upgrade module, which are used to run and manage applications. Edge devices also include software platforms, such as operating systems (such as Linux), communication protocol software (such as TCP/IP, MQTT, or COAP, etc.), and containers (docker). Edge devices also include various hardware infrastructure, such as processors (such as CPUs), memory, storage, networks and other hardware facilities.

The cloud as shown in Figure 6 can send messages or instructions to edge nodes through management channels. Similarly, edge nodes can send messages or instructions to the cloud through business channels. Optionally, the communication channel can be established through the data channel module in the edge node.

The terminal shown in Figure 6 can contain data channel modules, runtime engine instances, operating systems, and hardware. The running engine instance can include APP management parsing modules and executors, which are used to run and manage applications. Edge devices also include software platforms, such as operating systems (such as Lite OS), communication protocol software (such as TCP/IP, MQTT, or COAP, etc.), and containers (docker). Edge devices also include various hardware infrastructure, such as processors (such as CPUs), memory, storage, networks, sensors, valves, switches and other hardware facilities.

When communicating between the cloud and the terminal, messages or instructions sent from the cloud to the terminal can be sent to the edge node first, and then forwarded to the terminal by the edge node. Similarly, messages or instructions sent from the terminal to the cloud can be sent to the edge node first, and then forwarded to the cloud by the edge node.

Further, the communication between the terminal and the edge device can be connected through the data module in the terminal. For example, the data module in the terminal can be used to establish wired or wireless communication links. For example, it can include links based on the following communication technologies: home smart gateway Elink, power broadband (power line communication, PLC), wireless network communication technology ( Such as Wi-Fi, etc.).

In a possible implementation, the cloud provides a method for controlling the device, which can form a cloud service provided to the user. For example, after a user provides cloud services, the cloud responds to the user's request and provides the user with an orchestration interface. Correspondingly, the user device used by the user can present an editing interface. After the user device submits its own design, the cloud can control the business performed by the device based on the user's needs.

The method flow of the embodiments of the present application will be described in detail below with reference to the accompanying drawings. Please refer to Figure 7, which is a schematic flowchart of a possible service management method provided by an embodiment of the present application. Optionally, the service management method can be applied to the aforementioned embodiments, such as the embodiments shown in Figure 1, Figure 2A, Figure 2B, Figure 3, Figure 4, Figure 5 or Figure 6 .

The above-mentioned business management method includes one or more steps from step 701 to step S704. It should be understood that this application describes the sequence of S701 to S704 for convenience of description, and is not intended to limit execution to the above sequence. The embodiments of the present application do not limit the execution sequence, execution time, number of executions, etc. of one or more of the above steps. The details of steps S701 to S704 are as follows:

Step S701: The cloud provides a component orchestration interface and controls component resources.

Among them, the component orchestration interface is used to design the components that the application depends on, while the control component resources are used for users to select the components that the application depends on. Among them, when designing the components that the application depends on, users can perform the following operations in the component arrangement interface: add components, delete components, move the position of components, edit the properties of components, set the relationship between components, define parameters of components, and reduce the display One or more of the content, enlarged display content, sliding interface, etc.

For example, please refer to FIG. 8 , which is a schematic diagram of a possible interface provided by an embodiment of the present application. Among them, area 801 exemplarily shows a component orchestration interface provided by the cloud. The component orchestration interface can be presented on the user device. The user can arrange the components in area 801, for example, the control component shown in area 803. 1 is a control component placed by the user on the orchestration interface. For example, the user can select a certain component in the component library shown in area 802 and add it to area 801. For another example, the user can delete a certain control component. For another example, the user can update one or more of the position, inclusion relationship, or execution order of the control component through a movement operation. For another example, the user can set the data flow direction between components. One possible data flow direction is from control component 1 to control component 2.

Control component resources are used for users to select the control components they need to use.

Among them, the control component (node) is a code fragment or a compiled binary file used to implement one or several functions, and is usually pre-defined or pre-encapsulated. For example, applications usually require user registration. Since the function of user registration is similar in most applications, the code of the registration process can be encapsulated as a control (register) component. In this way, multiple applications can complete the registration function through the same control component without wrapping a registration component in each application.

As a possible solution, the components may include mathematical function components, statistical components, timer components, proportional-integral-differential (PID) controller components, thermodynamic components, optical components or air quality detection components, etc. One or more items. For example, area 801 shown in Figure 8 exemplarily describes function components, statistical components, electrical components, PID components, etc. provided by the cloud.

Since the device may involve a variety of controls on sensors, logic gates, and electrical components, the security and professionalism requirements in the application development process are high. In this embodiment of the present application, the functional code blocks involved in the target device are encapsulated into control components, so that users can Flexibly build applications safely and rationally based on visual control components.

Optionally, the control component has an API registration interface corresponding to it, so that the control component can register component information when loading.

In a possible implementation, the embodiments of the present application can be used to control the business functions of the target device, and the above control components include control components that comply with the development standards of the target device. Taking the target device as DDC as an example, the development standards of DDC include the operating system, computer language and communication protocol used by it. Therefore, the cloud can provide control components suitable for the development standards of DDC, so that applications can be orchestrated through control components. Applications deployed in DDC.

Step S702: The cloud generates metadata of the target application based on the control components arranged in the component arrangement interface.

Metadata is information that describes the properties of data. The metadata of the target application indicates the properties of the target application, and the data here contains the business process of the target application.

As a possible solution, metadata can be used to describe one or more of the calling relationships, transfer relationships, data flow relationships between control components, or which code fragment of the component needs to be executed. For example, an application relies on components to run, and the application's metadata can contain the calling logic between components. Another example is that an application depends on components to run, and the metadata of the application describes the order in which components are combined, etc.

In one possible design, the metadata may include component indication information and process information, where the component indication information is used to indicate multiple components that the application depends on, and the process information is used to indicate the business process.

Optionally, the component indication information is used to indicate the identification of the component (such as ID, name, or number, etc.). Optionally, the component indication information may include the identification of the component (such as ID, name, or number, etc.). Furthermore, the component indication information may also include component version information.

Optionally, metadata can be in a variety of formats, such as JavaScript object notation (JSON) format, extensible markup language (XML), or key-value (key-value, KV) format, etc. .

Figure 9 shows a schematic diagram of the format of metadata of a possible application provided by the embodiment of the present application. The metadata is stored and transmitted in JSON format. The data in area 901 is used to represent the application version (version) and the application ID. It can be seen that the application version can be, for example, "1.0.0", and the application ID, for example, can be "b0f629b2. a14ea8". Area 902 is used to represent information on components (nodes) on which the application depends. In the metadata of the application shown in Figure 9, there are two components that the application depends on, as follows: the ID of the first component is "354d1ebb.a294f4", and the type of the component is a registration type component. Its additional information (info) describes the description of the component. The version of the component is "1.0.0"; the ID of the first component is "98f67943.f4d2e", and the type of the component is an application (app) component. Additional information (info) is empty. It should be understood that Figure 9 is only an exemplary metadata provided for the convenience of describing the metadata format, and is not intended to limit the content and number of fields of the metadata. During specific implementation, the metadata may include more fields or more fields. For small fields, the data content contained in them can also have other designs.

Step S703: The cloud provides metadata of the target application to the target device.

It can be understood that the cloud provides the metadata of the target application to the target device, and in response, the target device receives the metadata of the target application provided by the cloud.

Among them, the target device is the device where the target application is deployed. For example, the target device may be an edge device or a terminal device, etc. For related description, please refer to the description in the foregoing architecture part.

By deploying applications to the target device, the cloud can control the business functions of the target device.

Step S704: The cloud provides the target device with control components that the target application depends on.

Specifically, the target application runs according to the business process of the target application and the components that the target application depends on, and the metadata of the target application indicates the business process of the target application. Therefore, the cloud can provide the control components that the target application depends on to the target device. The control components that the application depends on are used on the target device to run the application.

In a possible implementation, the target application depends on multiple components, and some of the components may have been configured in the target device. At this time, the cloud can provide the missing target components to the target device, so that the target device can run the target application based on multiple control components. As shown in Figure 4, when the cloud deploys APP2 to the target device, since component b and component c already exist in the target device, the cloud can provide the missing component d to the device, so that the target device can run APP2. In this way, through the reuse of components, the size of data that needs to be obtained during application deployment is greatly reduced, and the efficiency of application deployment is improved, thereby improving the efficiency of device control.

In the embodiment shown in Figure 7, on the one hand, the cloud provides the orchestration function and orchestration components of business control logic to the demand side, so that users on the demand side can visually develop applications based on the control requirements for the destination side, lowering the development threshold and reducing cost and improve the efficiency of application development; on the other hand, the cloud deploys user-orchestrated applications on the destination (the aforementioned electronic devices, such as edge devices and terminal devices). There is no need to install and debug the application offline, and it can also be deployed on the electronic device in a timely manner. Deploy applications in devices to conveniently control the functions of devices on the Internet.

For example, taking DDC as an example, DDC can execute actions such as starting/stopping machines, opening/closing valves, opening/closing valves, etc. by running the application and following the instructions of the application. The embodiment of the present application generates the business process of the target application by arranging control components, and provides the business process and control components to the DDC, so that the DDC executes actions according to the target application. In this way, users can flexibly generate applications safely and reasonably based on visual control components, improving code development efficiency. It is possible to download and update the control logic program in the field controller (DDC) through the cloud without changing the hardware firmware, which improves the user experience.

Some optional solutions in the embodiments of this application are further described below. It should be understood that for relevant concepts, operations or logical relationships that are not explained in the following solutions, refer to the corresponding descriptions in the embodiment shown in FIG. 7 .

In a possible implementation, the cloud can provide application testing services. The application testing service can test whether the application runs as expected based on the application's business process. In this way, the embodiments of the present application can realize application cloud development, cloud testing, and convenient deployment, and improve the service quality of the application deployment process.

In a possible implementation, the cloud can provide a running engine instance to the target device. Among them, the running engine instance is an instantiated running engine, which provides the software environment required for application running. The running engine instance is used to run the application based on the metadata corresponding to the application and the components that the application depends on, which can realize the reuse of control components and reduce the storage space occupied by the application. As shown in Figure 4, component b and component c can be reused between different APPs, thereby reducing the space occupied by the APP, suitable for nodes with limited resources, and reducing the need for each component during application deployment. The size of the application's installation package, thereby improving application deployment efficiency. In addition, for application developers, by reusing existing components, they can avoid repeated development of the same functional modules, avoid waste of manpower, and shorten the development cycle.

In a possible implementation, the cloud can control the running engine instance in the device. Figure 10 shows a schematic flowchart of a possible service management method provided by an embodiment of the present application. Optionally, the service management method can be applied to the aforementioned embodiments, such as the embodiments shown in Figure 1, Figure 2A, Figure 2B, Figure 3, Figure 4, Figure 5 or Figure 6 . The service management method shown in Figure 10 includes one or more steps from step S1001 to step S1006. It should be understood that this application describes the sequence of S1001 to S1006 for convenience of description, and is not intended to limit execution to the above sequence. The embodiments of the present application do not limit the execution sequence, execution time, number of executions, etc. of one or more of the above steps. The details of steps S1001 to S1006 are as follows:

Step S1001: The cloud provides a running engine instance to the target device. Accordingly, the target device accepts the runtime engine instance provided by the cloud.

Step S1002: The target device sends a registration message for the running engine instance to the cloud. Accordingly, the cloud receives the registration message of the running engine instance.

Among them, the registration message may contain one or more of the following information: license, hardware platform instruction set, CPU architecture, operating system, kernel version, and glibc version.

Optionally, the target device can install a runtime engine instance and start it, and then register the runtime engine instance to the cloud after startup.

Optionally, the cloud can assign an identifier to the running engine instance in the target device and record the running engine identifier to facilitate management of the running engine instance. Further, the cloud can send a registration return message to the target device, and the registration return message contains the identification of the running engine instance (such as ID, number, etc.).

Step S1003 (optional): Subscribe to the cloud to run the engine instance.

Among them, subscribing to the running engine instance is used to indicate that the cloud pays attention to changes in the running engine instance, and the running engine instance can send messages to the running engine within a certain period of time.

In a possible implementation, the cloud can maintain a long communication connection with the running engine instance. For example, the target device sends a heartbeat hold command to the cloud to maintain a long connection between the running engine instance and the cloud.

Optionally, the heartbeat maintenance instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the space usage in the at least one running engine instance, etc.

Optionally, communication between the cloud and the target device can be achieved through wireless communication technologies such as MQTT and COAP. For example, the cloud acts as an MQTT Broker and the target device acts as an MQTT client. The MQTT Broker is responsible for receiving network connections from the client and processing the client's subscription/unsubscription and message publishing (Publish) requests.

Step S1004: The cloud provides management services for running engine instances.

As a possible solution, the cloud provides full life cycle management of running engine instances.

Optionally, the cloud can provide online control functions for running engine instances, supporting one or more of the following: editing, restarting, synchronizing APPs, or engine patch upgrades on the running engine instances in the cloud.

Furthermore, the cloud can also provide management functions for APPs running engine instances, and can manage APPs currently running engine instances. For example: one or more of the following: obtaining the running status of the APP, remotely uninstalling the APP, or remotely delivering the configuration of the APP.

Here are several designs for cloud application management:

Design 1, the cloud can obtain the running status of the application. When an application is deployed on a running engine instance, the cloud correspondingly obtains the running status of the application in the running engine instance. In this way, the cloud can analyze useful information during application operation, monitor the application operation process, and facilitate monitoring of the implementation of the device's business functions.

Design 2, the cloud can send application management information (the management information can optionally be carried through messages), and the application management information is used to modify the configuration of the application, or to uninstall the application in the running engine instance. Since the application configuration modification, uninstallation and other operations can be controlled through messages, the control logic program of the target device can be updated without changing the hardware firmware, making it easier to control the target device. Of course, the two designs listed above are to facilitate understanding of the cloud's management of applications. During the specific implementation process, the cloud can also manage applications in the target device in other ways.

As a possible solution, the management service of the running engine can be implemented in the form of instructions. As shown in step S1005-step S1006:

Step S1005: The cloud sends control instructions to the target device.

This control instruction is used to control the running engine instance. For example, instructs you to modify the configuration of the running engine. Another example is to instruct the target device to report the running status of the APP in the running engine instance.

Step S1006: The target device performs operations according to the control instructions.

For example, modify the configuration of the running engine according to the control instructions.

For another example, corresponding to the control instruction, the running status of the APP in the running engine instance is reported.

It should be understood that the embodiment shown in Figure 10 is an exemplary description of the process of cloud management of the running engine. For related descriptions, reference can also be made to the case of cloud controlling the running engine instance listed in the architecture section.

In a possible implementation, the cloud can host (or save) the designed application in a version management platform or a third-party device. For example, in the application deployment system shown in Figure 6, the cloud can host applications in an external application warehouse to improve the scalability and flexibility of the system.

In a possible implementation, the cloud provides component development services and can receive component designs submitted by user devices. Optionally, the user device can submit component design data, where the design data includes but is not limited to one or more of component metadata, component source code, etc. Correspondingly, the cloud receives the component design data submitted by the user device and generates the control component. As a possible solution, the cloud can provide component development tools to facilitate the development of components based on the component development tools.

In a possible implementation, the control component corresponds to a certain field, and the cloud can provide control components in one or more fields. As a possible solution, the cloud can receive instruction information about the target field and provide the user device with control components corresponding to the target field. For example, when users need to design applications for use in DDC, the cloud can provide users with control components suitable for DDC.

In a possible implementation, the cloud can provide a device topology design function to facilitate users to design the distribution of devices, select devices on which applications need to be deployed, and so on. As a possible solution, the cloud can provide device materials, location materials, and network materials for designing topological connections between devices. For example, through the topology design function, you can design the device topology as shown in Figure 2A or Figure 2B.

The method of the embodiment of the present application is described in detail above, and the device of the embodiment of the present application is provided below.

It can be understood that the multiple devices provided by the embodiments of the present application, such as the business management device, in order to implement the functions in the above method embodiments, include corresponding hardware structures, software units, or hardware structures and software structures that perform each function. combinations, etc. Persons skilled in the art should easily realize that, in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different device implementations to implement the foregoing method embodiments in different usage scenarios, and different device implementations should not be considered to be beyond the scope of the embodiments of this application.

The embodiment of the present application can divide the device into functional units. For example, each functional unit can be divided corresponding to each function, or two or more functions can be integrated into one functional unit. The above integrated modules can be implemented in the form of hardware or software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.

Several possible devices are listed below. Please refer to Figure 11, which is a schematic structural diagram of a service management device 110 provided by an embodiment of the present application. Optionally, the service management device 110 may be an independent device or a component included in an independent device, such as a chip, software module, or integrated circuit. The service management device 110 is used to implement the aforementioned application deployment method. For example, the service management device 110 is used to implement the method on the cloud side in the embodiment shown in FIG. 7 or FIG. 10 .

In a possible implementation, the service management device 110 may include a communication unit 1101 and a processing unit 1102. The communication unit 1101 may be used to implement the aforementioned functions of receiving, sending, requesting or responding, and/or to support other processes of the aforementioned embodiments. In some possible implementation scenarios, the communication unit 1101 can also be replaced by a communication interface module and/or a transceiver module, and the interface module and/or transceiver module can be used to support the foregoing method embodiments.

The processing unit 1102 may be used to perform operations such as determination, calculation, generation, and execution in the foregoing embodiments, and/or to support other processes of the foregoing embodiments, such as outputting messages, outputting instructions, and other processes.

In a possible implementation, the communication unit 1101 is used to provide a component orchestration interface and control component resources, and the component orchestration interface is used to orchestrate control components that the target application depends on;

The processing unit 1102 is configured to generate metadata of the target application according to the control components arranged in the component arrangement interface;

The communication unit 1101 is also configured to provide metadata of the target application to the target device, and the metadata of the target application is used to run the target application;

The communication unit 1101 is further configured to provide the target device with a control component that the target application depends on, and the control component that the target application depends on is used to run the target application.

In yet another possible implementation, the communication unit 1101 is also used to:

In yet another possible implementation, the processing unit 1102 is also used to:

Get the running status of the application in the running engine instance.

In yet another possible implementation, the running engine instance includes a basic instruction flow module, an uplink instruction module, a downlink instruction module and an engine core module.

In yet another possible implementation, the basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink command module is used to send uplink commands;

In yet another possible implementation, the running engine instance includes a context module, and the context module is used to store running data of the current application.

In another possible implementation, the engine registration instruction includes one or more of the following information: license, hardware platform instruction set, central processor CPU architecture of the at least one running engine instance, operating system Properties, kernel version.

In another possible implementation, the heartbeat maintenance instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, the space usage in the at least one running engine instance Condition.

In yet another possible implementation, the target device includes a direct digital controller DDC.

In yet another possible implementation, the control component includes one of a mathematical function component, a statistical component, a timer component, a proportional-integral-derivative PID controller component, a thermodynamic component, an optical component or an air quality detection component. Or multiple items.

In yet another possible implementation, the target device is used to complete one or more of the following business functions:

In another possible implementation, the service management device 110 includes message middleware, and the message middleware is used to implement communication with the target device.

In yet another possible implementation, the communication unit 1101 is also configured to communicate with the target electronic device through wireless communication technology.

In yet another possible implementation, the communication unit 1101 is also configured to communicate with the running engine instance through the MQTT protocol.

In yet another possible implementation, the communication unit 1101 is also configured to communicate with the running engine instance through the COAP protocol.

For relevant descriptions, reference may be made to the descriptions in the foregoing embodiments, which will not be described again here.

Please refer to Figure 12, which is a schematic structural diagram of a computing device 120 provided by an embodiment of the present application.

The computing device 120 may be an independent device such as a server, a host, or an edge device, or may be a device included in an independent device, such as a chip, software module, or integrated circuit. The computing device 120 may include at least one processor 1201 and at least one memory 1202. Optionally, a communication interface 1203 may also be included. Further optionally, a connection line 1204 may also be included, wherein the processor 1201 and the memory 1202 are connected through the connection line 1204, and communicate with each other and transfer control and/or data signals through the connection line 1204.

in:

(1) The processor 1201 is a module that performs arithmetic operations and/or logical operations, and may specifically include one or more of the following devices: central processing unit (CPU), graphics processor (graphics processing unit, GPU), microprocessor unit (MPU), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Complex programmable logic device , CPLD), coprocessor (assist the central processor to complete corresponding processing and applications), or microcontroller unit (Microcontroller Unit, MCU), etc.

(2) The memory 1202 is used to provide storage space, and data such as operating systems and computer programs can be stored in the storage space. The memory 1202 may be random access memory (RAM), read-only memory (ROM), erasable programmable read only memory (EPROM), or portable read-only memory. One or more combinations of memory (compact disc read-only memory, CD-ROM), etc.

(3) The communication interface 1203 can be used to provide information input or output to the at least one processor. In some possible scenarios, communication interface 1203 may include interface circuitry. And/or, the communication interface 1203 may be used to receive data sent from the outside and/or send data to the outside. For example, the communication interface 1203 may include a wired link interface such as an Ethernet cable, or a wireless link (MQTT, COAP, Wi-Fi, Bluetooth, universal wireless transmission and other wireless communication technologies, etc.) interface. Optionally, the communication interface 1203 may also include a transmitter (such as a radio frequency transmitter, an antenna, etc.) or a receiver coupled to the interface.

Optionally, if the computing device 120 is an independent device, the communication interface 1203 may include a receiver and a transmitter. The receiver and transmitter may be the same component or different components. When the receiver and transmitter are the same component, the component can be called a transceiver.

Optionally, if the computing device 120 is a chip or a circuit, the communication interface 1203 may include an input interface and an output interface, and the input interface and the output interface may be the same interface, or may be different interfaces respectively. Optionally, the function of the communication interface 1203 can be implemented through a transceiver circuit or a dedicated chip for transceiver. The processor 1201 can be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

Optionally, the processor 1201 can be a processor specially designed to perform the foregoing method (for convenience, it is called a special-purpose processor), or it can be a processor that calls a computer program to perform the foregoing method (for convenience, it is called a special-purpose processor). device). Optionally, at least one processor may also include both a special-purpose processor and a general-purpose processor.

Optionally, in the case where the computing device includes at least one memory 1202, if the processor 1201 implements the aforementioned business management method by calling a computer program, the computer program can be stored in the memory 1202.

In this embodiment of the present application, each functional unit in the computing device 120 can be used to implement the aforementioned service management method. For example, the communication device can be the device and/or cloud in the embodiment shown in Figure 7 or Figure 10. For details, please refer to the aforementioned .

In a possible implementation, the processor 1201 is configured to execute a computer program stored in the memory to implement the following operations:

In yet another possible implementation, the processor 1201 is also used to:

Get the running status of the application in the running engine instance.

In yet another possible implementation, the computing device 120 further includes a communication interface 1203. The processor 1201 is also used to:

Application management information is sent through the communication interface 1203, and the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.

In yet another possible implementation, the processor 1201 is also used to:

The uplink command module is used to send uplink commands;

In another possible implementation, the computing device 120 includes message middleware, and the message middleware is used to implement communication with the target device.

Communicate with the target electronic device through the communication interface 1203 through wireless communication technology.

Communicate with the running engine instance through the communication interface 1203 through the MQTT protocol.

Communicate with the running engine instance through the communication interface 1203 through the COAP protocol.

For relevant descriptions, reference may be made to the descriptions in the foregoing embodiments and will not be described again here.

Embodiments of the present application also provide a chip system. The chip system includes a processor and a communication interface. The communication interface is used to receive and/or send data, and/or the communication interface is used to provide data for the processor. Provide input and/or output. The chip system is used to implement the aforementioned business management method, such as the method described in Figure 7 or Figure 10 .

Embodiments of the present application also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium. The instructions are used to implement the aforementioned business management method, such as the method described in Figure 7 or Figure 10 .

An embodiment of the present application also provides a computer program product. The computer program product includes computer instructions, and the computer instructions are used to implement the aforementioned business management method, such as the method described in Figure 7 or Figure 10 .

In the description of this application, the terms "center", "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "top", " The orientation or positional relationship indicated by "bottom", "inside", "outer", etc. is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply the device or device referred to. Elements must have a specific orientation, be constructed and operate in a specific orientation and therefore are not to be construed as limitations on the application.

In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "such as" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words "exemplary" or "such as" is intended to present the concept in a concrete manner.

"At least one" mentioned in the embodiments of this application means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b, or c can represent: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, c can be single or multiple. "And/or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and/or B can mean: A alone exists, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship.

And, unless otherwise stated, the use of ordinal numbers such as "first" and "second" in the embodiments of this application is used to distinguish multiple objects and is not used to limit the order, timing, priority or importance of multiple objects. degree. For example, the first device and the second device are just for convenience of description and do not indicate the difference in structure, importance, etc. of the first device and the second device. In some embodiments, the first device and the second device It can also be the same device.

As used in the above embodiments, depending on the context, the term "when" may be interpreted to mean "if..." or "after" or "in response to determining..." or "in response to detecting... ". The above are only optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the concepts and principles of the present application shall be included in the protection of the present application. within the range.

Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage media mentioned can be read-only memory, magnetic disks or optical disks, etc.

Claims

A service management method, characterized in that the service management method is used to control the service functions of a target device, and the target device includes an edge device and/or a terminal device; the method includes:

Provide a component orchestration interface and control component resources. The component orchestration interface is used to orchestrate the control components that the target application depends on;

Generate metadata of the target application according to the control components arranged in the component arrangement interface;

providing metadata of the target application to the target device, the metadata of the target application being used to run the target application;

A control component on which the target application depends is provided to the target device, and the control component on which the target application depends is used to run the target application.
The method of claim 1, further comprising:

A running engine instance is provided to the target device, and the running engine instance is used to provide an isolation environment for running the target application.
The method of claim 2, further comprising:

Control the running engine instance, wherein controlling the running engine instance includes one or more of the following operations:

Modify the configuration of the running engine instance, restart the running engine instance, perform patch upgrades on the running engine instance, and synchronize applications in the running engine instance.
The method according to claim 2 or 3, characterized in that, the method further includes:

Get the running status of the application in the running engine instance;

Send application management information, where the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.
The method according to any one of claims 2-4, characterized in that the method further includes:

Deploy the running application in the running engine instance in the target device;

A user interface for the running application is provided, and the user interface is used to display the running results of the running application.
The method according to any one of claims 2 to 5, characterized in that the running engine instance includes a basic instruction process module, an uplink instruction module, a downlink instruction module and an engine core module, wherein:

The basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink instruction module is used to send uplink instructions;

The downlink instruction module is used to receive downlink instructions and call a communication interface to execute instructions. The communication interface is provided by the engine core module;

The engine core module includes one or more of the following modules: engine basic management module, executor, general service module and file system;

Among them, the engine basic management module is used to manage the communication interface of the running engine, manage the resources in the engine core module and configure engine parameters, the executor is used to perform operations related to application operation, and the general service The module is used to manage logs and messages, and the file system is responsible for persistent data storage and data reading.
The method according to claim 6, characterized in that the running engine instance includes a context module, and the context module is used to store running data of the current application.
The method according to claim 6 or 7, characterized in that, the method further includes:

Receive uplink instructions from at least one running engine instance, where the uplink instructions include engine registration instructions, component installation request instructions, log upload instructions, and heartbeat maintenance instructions.
The method according to any one of claims 6-8, characterized in that the engine registration instruction includes one or more of the following information: license, hardware platform instruction set, at least one running engine instance Central processing unit CPU architecture, operating system attributes, and kernel version;

The heartbeat holding instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, and the space usage in the at least one running engine instance.
The method according to any one of claims 1-9, characterized in that the target device includes a direct digital controller DDC.
The method according to claim 10, characterized in that the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-derivative PID controller component, a thermodynamic component, an optical component or an air quality detection component. one or more items.
The method according to claim 10 or 11, characterized in that the target device is used to complete one or more of the following business functions:

Variable air volume VAV system control, refrigeration unit control, air conditioning water circulation system control, air conditioning box frequency conversion automatic air volume adjustment, cooling tower cooling fan control, lighting control, and electrical equipment control.
A business management system, characterized in that the business management system includes a server deployed in the cloud and a target device, the target device includes an edge device and/or a terminal device, and the cloud is used to control the business functions of the target device ,in;

The cloud is used to provide a component orchestration interface and control component resources, and the component orchestration interface is used to orchestrate control components that the target application depends on;

The cloud is also configured to generate metadata of the target application according to the control components arranged in the component arrangement interface;

The cloud is further configured to provide metadata of the target application to the target device, and the metadata of the target application is used to run the target application;

The cloud is further configured to provide the target device with a control component that the target application depends on, and the control component that the target application depends on is used to run the target application;

The electronic device is configured to run the target application according to the metadata of the target application and the target application dependency control component.
The business management system according to claim 13, characterized in that the cloud is further used to provide a running engine instance to the target device, and the running engine instance is used to provide an isolation environment for the target application to run.
The business management system according to claim 14, characterized in that the cloud is also used for:

Control the running engine instance, wherein controlling the running engine instance includes one or more of the following operations:

Modify the configuration of the running engine instance, restart the running engine instance, perform patch upgrades on the running engine instance, and synchronize applications in the running engine instance.
The business management system according to claim 14 or 15, characterized in that the cloud is also used for:

Get the running status of the application in the running engine instance;

Send application management information, where the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.
The business management system according to any one of claims 14-15, characterized in that the cloud is also used for:

Deploy the running application in the running engine instance in the target device;

A user interface for the running application is provided, and the user interface is used to display the running results of the running application.
The business management system according to any one of claims 14 to 16, characterized in that the running engine instance includes a basic instruction process module, an uplink instruction module, a downlink instruction module and an engine core module, wherein:

The basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink instruction module is used to send uplink instructions;

The downlink instruction module is used to receive downlink instructions and call a communication interface to execute instructions. The communication interface is provided by the engine core module;

The engine core module includes one or more of the following modules: engine basic management module, executor, general service module and file system;

Among them, the engine basic management module is used to manage the communication interface of the running engine, manage the resources in the engine core module and configure engine parameters, the executor is used to perform operations related to application operation, and the general service The module is used to manage logs and messages, and the file system is responsible for persistent data storage and data reading.
The business management system according to claim 18, characterized in that the running engine instance includes a context module, and the context module is used to store running data of the current application.
The business management system according to claim 18 or 19, characterized in that the cloud is also used for:

Receive uplink instructions from at least one running engine instance, where the uplink instructions include engine registration instructions, component installation request instructions, log upload instructions, and heartbeat maintenance instructions.
The business management system according to any one of claims 18 to 20, characterized in that the engine registration instruction includes one or more of the following information: license, hardware platform instruction set, the at least one running engine The instance’s central processing unit CPU architecture, operating system attributes, and kernel version;

The heartbeat holding instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, and the space usage in the at least one running engine instance.
The service management system according to any one of claims 13-21, characterized in that the target device includes a direct digital controller DDC.
The business management system according to claim 22, characterized in that the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-derivative PID controller component, a thermodynamic component, an optical component or an air quality detection component. One or more components.
The business management system according to claim 22 or 23, characterized in that the target device is used to complete one or more of the following business functions:

Variable air volume VAV system control, refrigeration unit control, air conditioning water circulation system control, air conditioning box frequency conversion automatic air volume adjustment, cooling tower cooling fan control, lighting control, and electrical equipment control.
A service management device, characterized in that the service management device includes a processing unit and a communication unit, wherein:

The communication unit is used to provide a component orchestration interface and control component resources, and the component orchestration interface is used to orchestrate control components that the target application depends on;

The processing unit is configured to generate metadata of the target application according to the control components arranged in the component arrangement interface;

The communication unit is further configured to provide metadata of the target application to the target device, and the metadata of the target application is used to run the target application;

The communication unit is further configured to provide the control component that the target application depends on to the target device, and the control component that the target application depends on is used to run the target application.
The device according to claim 25, characterized in that the communication unit is also used to:

A running engine instance is provided to the target device, and the running engine instance is used to provide an isolation environment for running the target application.
The device according to claim 26, characterized in that the processing unit is also used to:

Control the running engine instance, wherein controlling the running engine instance includes one or more of the following operations:

Modify the configuration of the running engine instance, restart the running engine instance, perform patch upgrades on the running engine instance, and synchronize applications in the running engine instance.
The device according to claim 26 or 27, characterized in that the communication unit is also used to:

Get the running status of the application in the running engine instance;

Send application management information, where the application management information is used to modify the configuration of the application in the running engine instance, or to uninstall the application in the running engine instance.
The device according to any one of claims 26 to 28, characterized in that the communication unit is also used to:

Deploy the running application in the running engine instance in the target device;

A user interface for the running application is provided, and the user interface is used to display the running results of the running application.
The device according to any one of claims 26 to 29, characterized in that the running engine instance includes a basic instruction process module, an uplink instruction module, a downlink instruction module and an engine core module, wherein:

The basic instruction flow module is used to control the installation of the uplink instruction flow and the downlink instruction flow;

The uplink instruction module is used to send uplink instructions;

The downlink instruction module is used to receive downlink instructions and call a communication interface to execute instructions. The communication interface is provided by the engine core module;

The engine core module includes one or more of the following modules: engine basic management module, executor, general service module and file system;

Among them, the engine basic management module is used to manage the communication interface of the running engine, manage the resources in the engine core module and configure engine parameters, the executor is used to perform operations related to application operation, and the general service The module is used to manage logs and messages, and the file system is responsible for persistent data storage and data reading.
The apparatus according to claim 30, wherein the execution engine instance includes a context module, and the context module is used to store execution data of the current application.
The device according to claim 30 or 31, characterized in that the communication unit is also used to:

Receive uplink instructions from at least one running engine instance, where the uplink instructions include engine registration instructions, component installation request instructions, log upload instructions, and heartbeat maintenance instructions.
The device according to any one of claims 30 to 31, characterized in that the engine registration instruction includes one or more of the following information: a license, a hardware platform instruction set, and the at least one running engine instance. Central processing unit CPU architecture, operating system attributes, and kernel version;

The heartbeat holding instruction includes one or more of the following information: the running status of the application in the at least one running engine instance, and the space usage in the at least one running engine instance.
The apparatus according to any one of claims 25-33, characterized in that the target device includes a direct digital controller DDC.
The device according to claim 34, wherein the control component includes a mathematical function component, a statistical component, a timer component, a proportional-integral-derivative PID controller component, a thermodynamic component, an optical component or an air quality detection component. one or more items.
The device according to claim 34 or 35, characterized in that the target device is used to complete one or more of the following business functions:

Variable air volume VAV system control, refrigeration unit control, air conditioning water circulation system control, air conditioning box frequency conversion automatic air volume adjustment, cooling tower cooling fan control, lighting control, and electrical equipment control.
A computing device, characterized in that the computing device includes a processor and a memory;

The processor is configured to execute the computer program stored in the memory, so that the computing device implements the method according to any one of claims 1-12.
A computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, and the instructions are used to implement the method described in any one of claims 1-12.