Primary embedded device, control system and method of configuring primary embedded device

Abstract

The invention provides a primary embedded device, and the device comprises a receiving module which is used for receiving an application file; the application analysis module is used for analyzing the application file; the logic execution module is used for processing the analyzed application file based on a preset logic engine so as to realize application logic of the application file in the primary embedded equipment; wherein the preset logic engine is preset in the primary embedded equipment, and the preset logic engine comprises logic elements and can be used for configuring the logic elements; the level embedded device is not configured with an operating system. A control system and a method of configuring a primary embedded device are also provided.

Description

Technical Field

[0001] The present application relates to embedded devices, and more particularly, to a primary embedded device configurable technology for field control. Background Art

[0002] For some low-end embedded devices—those without operating systems—application logic is essentially embedded in firmware. For example, for temperature control devices within buildings, the control terminal's GUI code and application logic are embedded in the firmware. Each piece of firmware corresponds to only one application logic and the user interface for that application. To adjust the temperature control device's control logic and / or display content, the original contents in the device's memory must be erased and the firmware corresponding to the new control logic and / or display content re-burned. This is cumbersome, and re-burning the firmware can easily damage the device. Summary of the Invention

[0003] According to one aspect of the present application, a primary embedded device is provided, comprising: a receiving module for receiving an application file; an application parsing module for parsing the application file received via the receiving module; and a logic execution module for processing the parsed application file based on a preset logic engine to implement the application logic of the application file in the primary embedded device; wherein the preset logic engine is pre-set in the primary embedded device, includes logic elements and can configure the logic elements; wherein the primary embedded device is not configured with an operating system.

[0004] According to the primary embedded device described in the present application, optionally, the receiving module further receives a user interface file related to the application file; and the device further includes a display module, a display parsing module, and a user interface programmable module. The display parsing module is configured to parse the user interface file; the logic execution module is further configured to process the parsed user interface file based on a preset logic engine to form a user interface logic file; and the user interface programmable module is configured to generate a user interface displayed by the display module based on the user interface logic file.

[0005] According to the primary embedded device described in the present application, optionally, the display parsing module is further used to parse the existing user interface in the primary embedded device to form display elements; the user interface programmable module is further used to call required elements from the display elements according to the user interface logic file to form a user interface that can be displayed by the display module.

[0006] According to the primary embedded device described in the present application, optionally, the display parsing module is further configured to parse the display parameters of the display module; the user interface programmable module is configured to form the user interface that can adapt to the display module according to the display parameters.

[0007] According to the primary embedded device described in the present application, optionally, the primary embedded device is configured as a device based on HTML, CSS and JS framework.

[0008] According to the primary embedded device described in the present application, optionally, the logic elements include one or more of logic operation function blocks, logic functions, conditional judgments, and logic variables.

[0009] According to the primary embedded device described in the present application, optionally, the preset logic engine sets and stores the logic elements in groups, and each group is configured with a unique identifier.

[0010] According to another aspect of the present application, a control system is also provided, which includes a computer device and a primary embedded device. The primary embedded device is directly or indirectly communicated with the computer device, and the computer device generates an application file for the primary embedded device and a user interface file for the application file; the primary embedded device is any one of the primary embedded devices described above.

[0011] According to another aspect of the present application, a method for configuring a primary embedded device is also provided. The method is executed by the primary embedded device, including receiving an application file; parsing the application file in the received file; processing the parsed application file based on the preset logic engine to implement the application logic of the application file in the primary embedded device; wherein the preset logic engine is pre-set in the primary embedded device, which includes logic elements and can configure the logic elements; wherein the primary embedded device is not configured with an operating system.

[0012] According to the method for configuring a primary embedded device described in the present application, optionally, the method further includes the primary embedded device: receiving a user interface file related to the application file; parsing the user interface file; processing the parsed user interface file based on a preset logic engine to form a user interface logic file; and forming a user interface displayed by the primary embedded device based on the user interface logic file.

[0013] The method for configuring a primary embedded device according to the present application may optionally further include: forming a user interface displayed by the primary embedded device according to the user interface logic file, including calling required elements from the display elements according to the user interface logic file to form a user interface displayed by the primary embedded device. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The present application will be more fully understood by referring to the following detailed description of specific embodiments in conjunction with the accompanying drawings, in which like reference numerals refer to like elements, wherein:

[0015] Figure 1 It illustrates an application scenario of a primary embedded device for field control;

[0016] Figure 2 is a schematic structural diagram of a primary embedded device 200 according to some examples of the present application;

[0017] Figure 3 is a structural diagram of a primary embedded device 200 according to some examples of the present application;

[0018] Figure 4 is a schematic diagram of the storage and loading of logic elements by a preset logic engine according to an example of this application;

[0019] Figure 5 is a structural diagram of a control system according to an example of this application;

[0020] Figure 6 is a flowchart of a method for configuring a primary embedded device according to some examples of the present application;

[0021] Figure 7 is a flowchart of a method for configuring a primary embedded device according to some further examples of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the following will be combined with the accompanying drawings to clearly and completely describe the implementation methods of the present application. It should be noted that the described implementation methods are only part of the implementation methods of the technical solution of the present application and not all of them. All other implementation methods obtained by ordinary technicians in this field based on the implementation methods described in this application document without paying creative work are covered by the scope of protection of this application.

[0023] Before elaborating on this application in detail, some terms are first explained. Cascading Style Sheets (CSS) is a computer language used to express the style of files such as HTML (Standard Generalized Markup Language) or XML (a subset of Standard Generalized Markup Language). CSS can not only modify web pages statically, but also dynamically format various elements of web pages in conjunction with various scripting languages. JavaScript (JS) is an object-based and event-driven client-side scripting language with relative security. It is also a scripting language widely used in client-side Web development and is often used to add dynamic functions to HTML web pages, such as responding to various user operations. Simply put, HTML or XML is responsible for the architecture of the web page; CSS is responsible for the style of the web page; JavaScript (JS) is responsible for the behavior of the web page. HTML or XML, CSS and JS constitute the three musketeers of the front end.

[0024] Depending on the operating environment, operating systems can be divided into desktop operating systems such as Windows and macOS, mobile phone / tablet operating systems such as Android and Hongmeng, and server operating systems such as embedded real-time operating systems, embedded Linux, Windows Embedded, VxWorks, and other embedded operating systems. The primary embedded devices mentioned in this application are not equipped with such operating systems. Furthermore, the primary embedded devices in this application refer to devices with a main frequency below a specific frequency and weak processing power, such as devices below Cortex M3 or microcontrollers with a main frequency below 300 MHz.

[0025] Figure 1 The following illustrates an application scenario of a primary embedded device for field control. Figure 1 As shown, the example application scenario is a part of the weak current control system in a building, specifically the lighting control part 10 and the temperature control part 12. The primary embedded device 100 included in the lighting control part 10 controls the lighting devices 101, 102, and 103 in the building. The primary embedded device 120 included in the temperature control part 12 controls the air conditioners 121 and 122. Hereinafter, the primary embedded device 100 and the primary embedded device 120 are also referred to as the lighting controller 100 and the thermostat 120, respectively. As needed, a control room 9 can be set up in the building to monitor and maintain the normal operation of the weak current control system in the building. The lighting controller 100 and the thermostat 120 are set in the control room or connected to the main control equipment such as the control cabinet in the control room.

[0026] It should be noted that the use of "buildings" as an application scenario is merely an example and not a limitation. The examples in this application can also be used in airports, factory buildings, apartment buildings, and the like. Similarly, light controllers, lighting devices, thermostats, and air conditioners are examples and not limitations. In actual applications, they can be other controlled systems and devices, such as ventilation systems and ventilation devices.

[0027] Figure 2 2 is a schematic diagram of the structure of a primary embedded device 200 according to some examples of the present application. Figure 2 As shown, the primary embedded device 200 includes a receiving module 20, an application parsing module 22, and a logic execution module 24. The primary embedded device 200 is not configured with an operating system, and has been configured with an initial application before being put into use for the first time.

[0028] The primary embedded device 200 according to the present application can be configured with new applications after it is put into use. Specifically, the receiving module 20 receives a file, such as an application file, input to the primary embedded device 200. The application parsing module 22 parses the input application file to convert it into data that can be subsequently processed by the primary embedded device 200. The logic execution module 24 processes the parsed application file based on a preset logic engine to implement the application logic of the application file in the primary embedded device 200.

[0029] A preset logic engine is pre-installed in the entry-level embedded device 200. The preset logic engine includes logic elements and can configure these logic elements. By way of example, and not limitation, the logic elements may include one or more of logic operation blocks, logic functions, conditional judgments, and logic variables. For example, logic operation blocks may include logical operations such as AND, OR, and NOT; arithmetic operations such as addition, subtraction, multiplication, division, and modulus; and bitwise operations such as left shift, right shift, and inversion. Conditional judgments may include greater than, equal to, less than, and not equal to. Logical variables may be pre-defined variables, such as current and voltage in lighting control. Logical variables may vary depending on the application scenario. Logic functions may include sine functions and delay functions. Furthermore, according to examples of the present application, the preset logic engine can also configure the logic elements it includes, such as selecting and releasing logic elements, and connecting related logic elements as needed. Connection, for example, refers to connecting electronic circuit components and / or functional modules in the low-end embedded device 200 based on the relationships between the logic elements.

[0030] In a specific example of the present application, the preset logic engine implements the logic elements in the form of files loaded and executed by the primary embedded device 200 to implement different logic application processing and timing, thereby separating the application logic from the main firmware of the primary embedded device 200 so that the device can be reprogrammed via an application input to the primary embedded device 200 to enable the device to have new application functions.

[0031] According to the examples of the present application, the receiving module 20 may include any one or more of various data transmission interfaces / modules such as USB, Mini USB, Micro USB, Thunderbolt interface, USB-C interface, etc. The receiving module 20 may also include a wireless transmission interface, such as a data interface based on the Bluetooth protocol or a wireless communication protocol. The receiving module 20 may also be configured to include a communication interface for a wired network, etc. The receiving module 20 may be configured as needed, as long as it can receive files transmitted from an external source to the primary embedded device.

[0032] For example, the initial application in the primary embedded device 200 is a temperature control application, such as Figure 1 The thermostat 120 in the. The initial application includes turning the air conditioner on and off according to the user's key operation. After the primary embedded device 200 receives the application file (the application file is a new application file relative to the initial application) through its receiving module 20, the application parsing module 22 parses the received new application file to obtain the application logic of the new application file. For example, the new application file is intended to add an air conditioner wind speed control function to the device 200 on top of the original function. After the application parsing module 22 parses the new application file, the application logic of each program (function) block of the new application file can be known. Further, the logic execution module 24 calls the logic element according to the application logic parsed by the parsing module 22 to implement the new application logic. The new application logic not only provides the on and off functions, but also provides the control of the air conditioner wind speed through the device 200. In this way, the user can implement the turning on and off of the air conditioner and the wind speed control through the user interface (not marked) of the device 200, such as a physical button. According to the primary embedded device 200 of the example of this application, the setting of the application parsing module 22 and the logic execution module 24 enables the device 200 to directly parse and reprogram the received new application to implement the application logic of the new application without having to implement the process of erasing the initial application and re-burning the new application on the device 200, thereby realizing the programmable characteristics of the device 200.

[0033] Figure 3 3 is a structural diagram of a primary embedded device 300 according to some examples of the present application. Figure 2Compared with the primary embedded device 200 in the example, the primary embedded device 300 in this example includes a receiving module 30 , an application parsing module 32 and a logic execution module 34 , and further includes a display module 38 , a display parsing module 31 and a user interface programmable module 35 .

[0034] Reference Figure 3 Receiving module 30 receives files, including application files and, in some examples, user interface (UI) files related to the application files, to implement an interface display for the application files on primary embedded device 300. UI files include static images such as buttons and menus, dynamic data related to the original application of device 300, and HTML files that store dynamic element data. HTML files serve as a bridge for information exchange between the interface display and the specific services of the device application.

[0035] The following description will be made by taking the initial embedded device 300 including the initial user interface file related to the initial application file as an example.

[0036] The application parsing module 32 is used to parse the application file received by the receiving module 30. Figure 2 The analysis of the application parsing module 22 described above is consistent and will not be repeated here. The display parsing module 31 parses the user interface file received via the receiving module 30 to obtain the display logic to be achieved by the user interface file. It should be understood that the user interface file received by the receiving module 30 is applied to the application file received by the receiving module 30 this time, that is, to realize the function of interacting with the user in the application file. Therefore, there is a correlation between the display logic to be achieved by the parsed user interface file and the application logic parsed by the application parsing module 32. The display parsing module 31 is also configured to parse the original user interface in the primary embedded device 300 to form display elements. By way of example and not limitation, these display elements include static images such as buttons and menus parsed from the original interface, dynamic data information related to the original application, and the original HTML file, and may also include the logical relationship of the original user interface file. In some cases, the display parsing module 31 can also parse the display parameters of the display module 30.

[0037] The logic execution module 34 is configured to process the parsed application file based on a preset logic engine to implement the application logic of the application file in the primary embedded device 300. The logic execution module 34 is also configured to process the parsed user interface file based on the preset logic engine to form a user interface logic file. It should be noted that, as mentioned above, the user interface file is used for the application file, and the display logic is therefore associated with the application logic. Therefore, when the logic execution module 34 forms the display logic file, it is not formed in isolation from the application logic, but rather is formed based on both.

[0038] The user interface programmable module 35 calls the required display elements from the parsed display elements according to the user interface logic file to form a user interface that can be displayed on the display module 38. During this process, the user interface programmable module 35 can also optionally adapt the user interface to the primary embedded device 300 based on display parameters, such as display size, display pixels, and other parameters.

[0039] As an example, the application loading module and user interface loading module (not shown) of the primary embedded device 300 load the application logic implemented by the logic execution model 34 and the interface display file, respectively, for display by the display module 38. It should be understood that for the sake of brevity, not all components and modules of the device 300 are shown here, for example, the buffer is not shown. In addition, the display module 38 is, for example, a display screen.

[0040] In some other examples, the user interface file received by the initial embedded device 300 includes the interface elements required by it, and the user interface programmable module 35 of the initial embedded device 300 can obtain the interface elements from the user interface file. In this case, the embedded device 300 may or may not include the initial user interface file.

[0041] According to the example that can be used for UI display in the embodiment of the present application, the primary embedded device (such as Figure 3 The device 300 in the example is configured as a device based on an HTML, CSS, and JS (HTML / CSS / JS) framework. In other words, the user interface programmable module can configure the user display of the embedded device similarly to configuring a web page based on the HTML, CSS, and JS framework settings. In this way, the primary embedded device can load and parse HTML / CSS / JS display files.

[0042] According to a further example of the present application, each primary embedded device is configured to load and parse specific HTML / CSS / JS display files. For example, a primary embedded device for a thermostat can parse various HTML / CSS / JS display files related to temperature control, but may not be able to parse HTML / CSS / JS display files related to lighting control; a primary embedded device for lighting control is configured to parse various HTML / CSS / JS display files related to lighting, but may not be able to parse HTML / CSS / JS display files related to ventilation control, and so on. Configuring HTML / CSS / JS in the primary embedded devices in this manner can conserve storage and processing resources of device 200.

[0043] Primary embedded devices are Figure 1 For example, the initial application is used to control the lighting device, and the user interface is the UI display that serves this application. For example, the UI may include on / off buttons, dimming / brightening buttons, and information such as the time. To configure a new light controller built on an existing primary embedded device to replace the initial light controller application, you need to replace the existing light controller with one that has the new light controller application already burned in, or erase the initial light controller application in the existing device and try burning the new light controller application.

[0044] However, if the primary embedded device 300 according to the example of this application is used as a lighting controller, secondary configuration can be performed directly. Specifically, the receiving module 30 receives a new lighting control application file and a UI file for the application. The application parsing module 32 parses the lighting control application file to form a new lighting control application logic. The display parsing module 31 parses the UI file of the application to form a new UI logic, which is used to serve the application logic to present the user interaction to be implemented by the application. Further, the display parsing module 31 parses the existing user interface of the existing lighting control application to obtain multiple display elements. The logic execution module 34 implements the application logic through a preset logic file and forms a user interface logic file based on the display logic. The user interface programmable module 35 performs secondary programming based on the user interface logic file, for example, selecting and calling the required display elements from the display elements according to the new display logic to form a new user interface logic file. In this process, the display parameters of the display module 38 can also be referenced at the same time, which can be parsed and obtained by the display parsing module 31.

[0045] It should be noted that the existing user interface, also referred to as the existing user interface, can be the initial user interface for the primary embedded device 300. The display parsing module 31 parses the existing lighting control application's user interface to obtain multiple display elements, which can then be used by the user interface programmable module 35 when subsequently creating a new user interface. In some cases, the parsed multiple display elements can be stored so that when the device 300 receives a new user interface file again through the receiving module 30, the previously parsed display elements can be directly used.

[0046] In some other examples, the existing user interface is not the initial user interface of the primary embedded device 300, but a user interface that has been implemented in the device 300 according to, for example, the examples of this application. Assume that the initial application is A, and the interface of the initial application is displayed as AU I. In this example, a new application A' is implemented in the device 300, and the interface for A' is displayed as AU I'. According to these examples, the interface display AU I' is parsed as an existing user interface.

[0047] The primary embedded device uses the HTML / CSS / JS framework as its basis, and implements UI programming based on the received UI file, the UI controls parsed by the display parsing module, and the display parameters of the display screen, etc., in combination with the user interface programmable module, so as to display the display associated with the application on the embedded device 300. Specifically, the primary embedded device uses HTML to implement the web page structure to be displayed by the application file, CSS to implement the style of the web page, and JS to implement the behavior to be implemented by each web page, so as to implement a web-based display on the device. In this process, the display parsing module parses the display elements from the original interface display, the logic execution module implements the user interface logic application file, and the user interface programmable module calls the display elements according to the user interface logic application file to realize the UI display. The entire process is completed in a programmable manner within the embedded device, without the need for erasing and burning, and without replacing a new device to implement new applications and display functions.

[0048] Figure 4 This is a schematic diagram of the storage and loading of logic elements by the preset logic engine according to the example of this application. Figure 4 In the example shown, the logic chain array 40 includes a plurality of folders, each folder includes a set of configurable logic elements, and each folder is configured with its own unique identifier UU ID. For the sake of simplicity, Figure 4 Folder 401 and folder 402 are shown. The folders in the logical chain array 40 are stored in the primary embedded device 300 (see Figure 3) in the RAM of the device 300. In this example, folder 401 includes logic elements 1, 0, 6, and 4, and folder 402 includes logic elements 0 and 1. When the logic execution module 34 programs the received application file in the device 300, it can call the required logic from the stored logic chain array 40 according to the application file description obtained by parsing. For example, according to the application file, it needs to use logic elements 0 and 1 in sequence during runtime, so it calls logic elements 0 and 1 from folder 401, and then calls logic elements 2 and 3 in sequence from an unillustrated folder, then calls logic element 4 from folder 401, and then calls logic elements 5 and 6 from folder 402, and calls logic elements 7 and 8 in sequence from an unillustrated folder, and finally calls logic element 9 from folder 401. In this way, the application logic of the received application is implemented by the logic execution module 34. Similarly, the logic execution module 34 can form a user interface logic file based on the parsed user interface file.

[0049] In summary, after the primary embedded device according to the example of this application is put into use, new application files and UI files can be input into the receiving module remotely, or transmitted on-site through, for example, a USB port or Bluetooth interface. The transmitted new files can be parsed separately by the parsing module in the device, and the logic execution module can form application logic and user interface logic display files, and then the user interface programmable module can realize the new user interface display. In this way, there is no need to replace the device or re-burn as in the prior art, but new applications can be configured multiple times, safely and conveniently.

[0050] Figure 5 This is a schematic diagram of the structure of the control system according to the example of this application. Figure 5 As shown, the control system includes a computer device 50 and a primary embedded device 52. The computer device 50 and the primary embedded device 52 can be directly or indirectly connected. Here, a direct connection means that the computer device 50 can directly communicate and transfer data with the primary embedded device 52. An indirect connection means that the computer device 50 and the primary embedded device 52 transfer data through a third party. For example, the computer device 50 copies data to a device such as a removable disk, which then transfers the data to the device 52 via an interface of the primary embedded device 52.

[0051] The computer device 50 is configured to develop application files and UI files for the application files, and convert them into a transmittable file format for direct or indirect transmission to the primary embedded device 52. The primary embedded device 52 is any of the primary embedded devices described above in conjunction with the examples. It should be noted that only one primary embedded device 52 is illustrated here, but in actual applications, the system may include multiple primary embedded devices.

[0052] Figure 6 This is a flow chart of a method for configuring a primary embedded device according to some examples of the present application. The primary embedded device is provided with a preset logic engine. Figure 6 As shown, in step S500, a primary embedded device receives a file. In step S502, the primary embedded device parses the application file in the received file. In step S504, the primary embedded device processes the parsed application file based on the preset logic engine to implement the application logic of the application file in the primary embedded device. Figure 6 The method shown can be implemented, for example, in combination with Figure 2 and Figure 3 The primary embedded devices 200 and 300 are described respectively.

[0053] For example, Figure 6 The method shown is Figure 2 The primary embedded device 200 described herein is executed. A file is received (S500) by the receiving module 20 of the primary embedded device 200. The application parsing module 22 of the primary embedded device 200 parses (S502) the application file. The logic executable module 24 of the primary embedded device 200 processes (S504) the received application file using a preset logic engine to implement the application logic of the application file in the primary embedded device 200.

[0054] Figure 7 This is a flowchart of a method for configuring a primary embedded device according to a further example of the present application, wherein the primary embedded device includes a display module and a preset logic engine is provided in the primary embedded device. Figure 3 The primary embedded device shown performs Figure 7 The method shown is used as an example for explanation.

[0055] Please also refer to Figure 7 and Figure 3In step S600, the receiving module 30 of the primary embedded device 300 receives an application file and a user interface file for the application file. In step S602, the application parsing module 32 of the primary embedded device 300 parses the received application file. In step S604, the display parsing module 31 of the device 300 parses the original user interface of the primary embedded device and the received user interface file. In step S606, the logic execution module 34 of the device 300, based on a preset logic engine and the parsed application file and user interface file, respectively generates application logic and user interface display logic. In step S608, the user interface programmable module 35 of the device 300 calls elements of the parsed display elements according to the user interface display logic, thereby realizing a user interface that can be displayed by the display module 38. Step S604 may also include parsing display parameters of the display module 38. When implementing the user interface in step S608, the display parameters may be used to generate a user display adapted to the display module 38. Here, the steps are not intended to limit the order of execution. For example, step S604 can be executed simultaneously with step S602, or they can be executed one after the other.

[0056] The technical features in the various embodiments of the present application may be combined with each other to form new implementations without departing from the spirit of the present application and without conflicting with each other. Although specific embodiments of the present application have been shown and described in detail to illustrate the principles of the present application, it should be understood that the present application can be implemented in other ways without departing from such principles.

Claims

1. A primary embedded device, characterized in that: The primary embedded device includes: A receiving module, used for receiving application files; An application parsing module, configured to parse the application file; a logic execution module, configured to process the parsed application file based on a preset logic engine, so as to implement the application logic of the application file in the primary embedded device; The preset logic engine is pre-set in the primary embedded device, and includes logic elements, and the logic elements are configurable; The embedded device is not equipped with an operating system.

2. The primary embedded device according to claim 1, characterized in that The receiving module is further configured to receive a user interface file related to the application file, and the primary embedded device further comprises: Display module; A display parsing module, used for parsing the user interface file; The logic execution module is further configured to process the parsed user interface file based on a preset logic engine to form a user interface logic file; A user interface programmable module is used to form a user interface displayed by the display module according to the user interface logic file.

3. The primary embedded device according to claim 2, characterized in that: The display parsing module is further used to parse the existing user interface in the primary embedded device to form display elements; The user interface programmable module is further used to call required elements from the display elements according to the user interface logic file to form a user interface displayed by the display module.

4. The primary embedded device according to claim 2, characterized in that The display parsing module is further used to parse the display parameters of the display module; the user interface programmable module forms the user interface adapted to the display module according to the display parameters.

5. The primary embedded device according to claim 2, characterized in that: The primary embedded device is configured as a device based on HTML, CSS and JS framework.

6. The primary embedded device according to any one of claims 1 to 5, characterized in that: The logic elements include one or more of logic operation function blocks, logic functions, conditional judgments, and logic variables.

7. The primary embedded device according to claim 6, characterized in that: The preset logic engine sets and stores the logic elements in groups, and each group is configured with a unique identifier.

8. A control system comprising a computer device and a primary embedded device, wherein the primary embedded device is directly or indirectly connected to the computer device for communication, characterized in that: The computer device is configured to generate a file for the primary embedded device; the primary embedded device is the primary embedded device according to any one of claims 1 to 7.

9. A method for configuring a primary embedded device, characterized in that: The primary embedded device includes a preset logic engine, and the method includes: Receive application files; Parsing the application file; Processing the parsed application file based on the preset logic engine to implement application logic of the application file in the primary embedded device; The preset logic engine is pre-set in the primary embedded device, and includes logic elements, and the logic elements are configurable; The embedded device is not equipped with an operating system.

10. The method according to claim 9, characterized in that The method further comprises, by the primary embedded device: receiving a user interface file related to the application file; Parsing the user interface file; Processing the parsed user interface file based on a preset logic engine to form a user interface logic file; A user interface displayed by the primary embedded device is formed according to the user interface logic file.

11. The method according to claim 10, characterized in that The method further comprises: Parsing an existing user interface in the primary embedded device to form display elements; and The forming of the user interface displayed by the primary embedded device according to the user interface logic file includes calling required elements from the display elements according to the user interface logic file to form the user interface displayed by the primary embedded device.

12. The method according to claim 11, characterized in that The method further comprises: parsing display parameters of the primary embedded device; The user interface adapted to the primary embedded device is formed according to the display parameters.

13. The method according to claim 10, characterized in that The primary embedded device is configured as a device based on HTML, CSS and JS framework.

14. The method according to any one of claims 9 to 13, characterized in that The logic elements include one or more of logic operations, logic functions, and logic processes.

15. The method according to claim 14, characterized in that The preset logic engine sets and stores the logic elements in groups, and each group is configured with a unique identifier.

Images