Method and device for building operating system, operating system, equipment and medium

Abstract

The application discloses a system building method, a system building device, an operating system, equipment and a medium. The system building method comprises the following steps: obtaining a configuration file of an operating system to be built, and determining at least two function units to be implemented by the operating system to be built according to the configuration file; obtaining an OS element capability corresponding to each function unit in the at least two function units, and assembling all the obtained OS element capabilities to obtain the operating system to be built. According to the embodiment of the application, the operating system is decoupled from hardware, the operating system is built in the mode of assembling OS element capabilities, the operating system can be spliced, the existing OS element capabilities can be reused, the operating system can be built on demand, and therefore, the development of operating systems of various hardware devices can be completed conveniently, quickly and at low cost, and the development difficulty and cost of the operating system are greatly reduced.

Description

Technical Field

[0001] This application relates to the field of operating system technology, and in particular to a method for building an operating system, a building apparatus, an operating system, a device, and a medium. Background Technology

[0002] Operating systems are the foundational software for hardware devices and are indispensable to them. Different types of hardware devices require different operating systems for compatibility. For example, computers run Windows, while smartphones run Android, iOS, or HarmonyOS.

[0003] With the rapid development of the Internet of Things (IoT) era, there is a need to develop various hardware devices in different forms to meet the demands of IoT, and each type of hardware device requires a compatible operating system. However, operating systems, as foundational software, are technically challenging and costly to develop. This means that developing new hardware devices requires significant time and manpower costs, which in turn hinders the development of the IoT era.

[0004] Therefore, existing technologies still need to be improved and enhanced. Summary of the Invention

[0005] The technical problem to be solved by this application is to provide a method, apparatus, operating system, device and medium for building an operating system, in order to address the shortcomings of the prior art.

[0006] To address the aforementioned technical problems, the first aspect of this application provides an operating system, wherein the operating system includes at least two OS meta-capabilities, each of the at least two OS meta-capabilities being used to implement a functional unit of the system function corresponding to the operating system, and each OS meta-capability being assembled according to the business compilation chain of the operating system.

[0007] In some implementations, the OS meta-capabilities are formed by decoupling the entire operating system stack.

[0008] In some implementations, each of the at least two OS meta-capabilities is configured with a standard interface so that any two OS meta-capabilities can be assembled.

[0009] In some implementations, the OS meta-capabilities in the operating system are assembled in a modular fashion through their respective configured standard interfaces.

[0010] In some implementations, the operating system's business compilation chain is used to reflect the logical matching relationships between various OS meta-capabilities.

[0011] In some implementations, the OS meta-capabilities included in the operating system can be adjusted, wherein the adjustment operation is formed according to the adjustment of the system functions to be performed by the operating system, and the adjustment operation includes one or more of the following: adding OS meta-capabilities, deleting OS meta-capabilities, and replacing OS meta-capabilities.

[0012] The second aspect of this application provides a method for building an operating system, wherein the method for building the operating system specifically includes:

[0013] Obtain the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file;

[0014] Obtain the OS meta-capabilities corresponding to each of at least two functional units, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

[0015] In some implementations, determining the at least two functional units to be implemented by the operating system to be built based on the configuration file specifically includes:

[0016] According to the configuration file, obtain the business logic for implementing the entire process of the electronic device from startup to operation, wherein the electronic device is a hardware device that is to load the operating system to be built;

[0017] The entire process business logic is decoupled to obtain at least two functional units.

[0018] In some implementations, obtaining the OS meta-capabilities corresponding to each of the at least two functional units specifically includes:

[0019] Search for the OS meta-capabilities corresponding to each functional unit in a pre-established OS meta-capability market, wherein the OS meta-capability market includes at least two OS meta-capabilities;

[0020] For any unused functional unit for which no OS meta-capability was found, a prompt message will be generated asking for the corresponding OS meta-capability of the unused functional unit.

[0021] In some implementations, the OS meta-capability marketplace is deployed on the server and presented to the user as an application.

[0022] In some implementations, the step of searching for the corresponding OS meta-capabilities for each functional unit within a pre-established OS meta-capability market specifically includes:

[0023] Send a request to the server to obtain the OS meta-capabilities corresponding to each functional unit, so that the server responds to the request and searches for the OS meta-capabilities corresponding to each functional unit in the OS meta-capability market;

[0024] Receive feedback information generated by the server based on the acquisition request, wherein the feedback information includes all found OS meta-capabilities.

[0025] In some implementations, after generating a prompt message requesting the provision of the corresponding meta-capability for an unused functional unit for which no OS meta-capability was found, the method further includes:

[0026] Receive user input operations and extract the OS meta-capabilities carried by the input operations, wherein the OS meta-capabilities carried by the input operations are developed by the OS meta-capability developers for the idle functional unit.

[0027] In some implementations, the construction process of the OS meta-capability marketplace is as follows:

[0028] The default configuration builds a dataset for storing the OS meta-capability marketplace;

[0029] Respond to the release command of OS meta-capabilities and obtain the OS meta-capabilities corresponding to the release command;

[0030] The OS meta-capabilities corresponding to the release command are published, and the OS meta-capabilities corresponding to the release command are stored in the dataset.

[0031] In some implementations, the construction process of the OS meta-capability marketplace further includes:

[0032] In response to a control command for a preset OS meta-capability in the OS meta-capability market, the system executes a control operation corresponding to the control command on the preset OS meta-capability corresponding to the control command, wherein the control command includes a removal command or a version update command.

[0033] In some implementations, assembling all acquired OS meta-capabilities to obtain the operating system to be built specifically includes:

[0034] Obtain the business compilation chain between the at least two functional units, wherein the business compilation chain is used to reflect the logical matching relationship between the functional units;

[0035] Based on the business compilation chain, all acquired OS meta-capabilities are assembled to obtain the operating system to be built.

[0036] In some implementations, assembling all acquired OS meta-capabilities according to the business compilation chain to obtain the operating system to be built specifically includes:

[0037] The logical matching relationship between each OS meta-capability is determined based on the aforementioned business compilation chain;

[0038] Based on the logical matching relationship between each OS meta-capability, the OS meta-capabilities are assembled through the standard interface configured for each OS meta-capability to obtain the operating system to be built.

[0039] A third aspect of this application provides an operating system building apparatus, wherein the operating system building apparatus specifically includes:

[0040] The acquisition module is used to acquire the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file.

[0041] An assembly module is used to acquire the OS meta-capabilities corresponding to each of at least two functional units, and to assemble all the acquired OS meta-capabilities to obtain the operating system to be built.

[0042] A fourth aspect of this application provides an operating system building system, wherein the operating system building system includes a building device and a server, the server storing an OS meta-capability market; the building device is used to obtain the configuration file of the operating system to be built, determine at least two functional units to be implemented by the operating system to be built according to the configuration file, obtain the OS meta-capabilities corresponding to each functional unit through the server storing the OS meta-capability market, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

[0043] A fifth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement the operating system construction method described above.

[0044] A sixth aspect of this application provides a construction device, wherein the construction device includes a memory and a processor;

[0045] The memory is used to store computer programs;

[0046] The processor is used to execute the computer program and, when executing the computer program, implement the operating system construction method described above.

[0047] A seventh aspect of this application provides an electronic device, wherein the electronic device is equipped with an operating system as described above.

[0048] Beneficial Effects: Compared with existing technologies, this application provides a method, apparatus, operating system, device, and medium for building an operating system. The method involves obtaining a configuration file of the operating system to be built, determining at least two functional units to be implemented by the operating system based on the configuration file, obtaining OS meta-capabilities corresponding to each of the at least two functional units, and assembling all the obtained OS meta-capabilities to obtain the operating system to be built. This application's embodiments decouple the operating system from the hardware and build the operating system by assembling OS meta-capabilities, making the operating system modular. This not only allows for the reuse of existing OS meta-capabilities but also enables on-demand building of the operating system, thereby facilitating the convenient, fast, and low-cost development of operating systems for various types of hardware devices, greatly reducing the difficulty and cost of operating system development. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 This is a schematic diagram of an operating system construction system provided in an embodiment of this application.

[0051] Figure 2 This is a schematic block diagram of a construction device provided in an embodiment of this application.

[0052] Figure 3 This is a schematic flowchart illustrating a method for building an operating system, as provided in an embodiment of this application.

[0053] Figure 4 This is a schematic flowchart illustrating the process of acquiring functional units in an operating system construction method provided in this application embodiment.

[0054] Figure 5 This is a schematic flowchart illustrating the process of searching for OS meta-capabilities in an OS meta-capability market in an operating system construction method provided in an embodiment of this application.

[0055] Figure 6 This is a schematic diagram illustrating the construction process of the OS meta-capability market.

[0056] Figure 7This is a schematic diagram illustrating the OS meta-capability marketplace on client devices.

[0057] Figure 8 A diagram illustrating how to enable devices to download OS metadata from a server.

[0058] Figure 9 This is a schematic diagram of an operating system provided in an embodiment of this application.

[0059] Figure 10 This is a schematic block diagram illustrating the structure of an operating system installation and loading, provided as an embodiment of this application. Detailed Implementation

[0060] This application provides a method, apparatus, operating system, device, and medium for building an operating system. To make the objectives, technical solutions, and effects of this application clearer and more explicit, the following detailed description is provided with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this application.

[0061] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0062] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0063] It should be understood that the sequence number and size of each step in this embodiment do not imply the order of execution. The execution order of each process is determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment.

[0064] Currently, all existing operating systems, whether Windows, macOS, Linux, Android, iOS, or HarmonyOS, are single-device operating systems, integrated as a whole onto the hardware device to be compatible with its form factor. For example, computers run Windows, while smartphones run Android, iOS, or HarmonyOS.

[0065] However, with the rapid development of the Internet of Things (IoT) era, there is a need to develop various hardware devices in different forms to meet the demands of IoT. Each type of hardware device requires a compatible operating system, which means that an operating system needs to be developed for each new type of hardware device. However, as the foundational software of hardware devices, operating systems are technically challenging and costly to develop. This means that developing an operating system for a new type of hardware device requires significant investment of resources, increasing the overall development cost of the new hardware device.

[0066] To reduce the development costs of developing operating systems for hardware devices, embodiments of this application can form an operating system by splicing together multiple OS meta-capabilities. When developing a new operating system, OS meta-capabilities from existing operating systems can be reused, while OS meta-capabilities that cannot be reused can be redeveloped. This can reduce the workload of operating system development and thus lower the development cost of the operating system.

[0067] Therefore, this application provides an operating system construction method, construction device, operating system, equipment, and medium to solve the problem of high development costs required for existing operating system development, and enables rapid construction of operating systems for hardware devices, thus promoting the rapid development of the era of everything.

[0068] The application content will be further explained below with reference to the accompanying drawings and the description of the embodiments.

[0069] Please see Figure 1 , Figure 1 This is a schematic diagram of an operating system setup system provided in an embodiment of this application. For example... Figure 1As shown, the operating system setup system includes setup device 1000 and server 2000. Setup device 1000 communicates with server 2000. Setup device 1000 includes, but is not limited to, personal computers such as tablets, laptops, and desktop computers, as well as mobile devices such as smartphones or tablets. Server includes, but is not limited to, backend servers and cloud computing, or storage components built into the setup device itself, or other electronic devices with storage functions (e.g., portable hard drives).

[0070] In some embodiments, the setup device 1000 can be used to obtain the configuration file of the operating system to be built, determine at least two functional units to be implemented by the operating system to be built according to the configuration file, obtain the OS meta-capabilities corresponding to each functional unit through a server storing the OS meta-capability market, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

[0071] Server 2000 stores an OS meta-capability marketplace, used to provide OS meta-capabilities to deployment device 1000. Understandably, when deployment device 1000 needs to obtain OS meta-capabilities from the marketplace, it sends a request to the server. Server 2000 responds to the request, searches the marketplace for the required OS meta-capabilities, and sends all found OS meta-capabilities back to deployment device as feedback information. Deployment device 1000 then receives the feedback information from server 2000 and parses it to obtain the corresponding OS meta-capabilities for its functional units.

[0072] The setup device 1000 may be equipped with a first communication module, which sends an acquisition request to the server. The server 2000 may be equipped with a second communication module compatible with the setup device, which establishes a connection with the first communication module to receive the acquisition request sent by the setup device. Both the first and second communication modules include modules such as Wi-Fi, Bluetooth, NFC, and USB.

[0073] For example, when the server 2000 is a storage component built into the setup device 1000 itself, such as a hard drive or memory, the setup device 1000 can pre-back up the OS meta-capabilities in the OS meta-capability market to the storage component built into the setup device 1000 itself. When the setup device performs operating system setup, it can directly search for OS meta-capabilities from the OS meta-capability market stored in the storage component built into the setup device 1000 itself. This allows the setup device 1000 to set up an operating system even when it does not have a communication module, the communication module is damaged, or the communication network fails.

[0074] For example, when the server 2000 is another electronic device, when it is necessary to search for OS components from the OS meta-capability market, the electronic device can be connected to the setup device 1000 via a USB module, Bluetooth module, or NFC module to search for OS components from the OS meta-capability market.

[0075] For example, when the server 2000 is a cloud or backend server, when it is necessary to search for OS components from the OS meta-capability market, a device 1000 can be set up to connect to the server 2000 via WiFi to search for OS components from the OS meta-capability market.

[0076] Please see Figure 2 , Figure 2 This is a schematic block diagram of a construction device provided in an embodiment of this application. For example... Figure 2 As shown, the device includes a processor 1001 and a memory 1002, wherein the processor 1001 and the memory 1002 are connected by a bus, such as an I2C (Inter-integrated Circuit) bus or a distributed soft bus.

[0077] The memory 1002 may include a non-volatile storage medium and internal memory. The non-volatile storage medium may store an operating system and a computer program. The computer program includes program instructions that, when executed, cause the processor to execute any method for building an operating system.

[0078] For example, the memory 1002 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 1002 may include high-speed random access memory (RAM) and may also include non-volatile memory. For example, various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, may be used, or they may be transient storage media.

[0079] The processor 1001 provides computing and control capabilities to support the operation of the entire assembly.

[0080] For example, processor 1001 may be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0081] Specifically, the processor 1001 is used to run a computer program stored in memory, and when executing the computer program, it performs the following steps:

[0082] Obtain the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file;

[0083] Obtain the OS meta-capabilities corresponding to each of at least two functional units, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

[0084] In some embodiments, when the processor 1001 implements at least two functional units to be implemented by the operating system to be built, as determined according to the configuration file, it is specifically used to implement:

[0085] According to the configuration file, obtain the business logic for implementing the entire process of the electronic device from startup to operation, wherein the electronic device is a hardware device that is to load the operating system to be built;

[0086] The entire process business logic is decoupled to obtain at least two functional units.

[0087] In some implementations, when the processor 1001 acquires the OS meta-capabilities corresponding to each of the at least two functional units, it is specifically used to implement:

[0088] Search for the OS meta-capabilities corresponding to each functional unit in a pre-established OS meta-capability market, wherein the OS meta-capability market includes at least two OS meta-capabilities;

[0089] For any unused functional unit for which no OS meta-capability was found, a prompt message will be generated asking for the corresponding OS meta-capability of the unused functional unit.

[0090] In some implementations, when the processor 1001 acquires the OS meta-capabilities corresponding to each of the at least two functional units, the OS meta-capability marketplace is deployed on the server and presented to the user in the form of an application.

[0091] In some implementations, when the processor 1001 searches for the OS meta-capabilities corresponding to each functional unit in a pre-established OS meta-capability market, it specifically performs the following:

[0092] Send a request to the server to obtain the OS meta-capabilities corresponding to each functional unit, so that the server responds to the request and searches for the OS meta-capabilities corresponding to each functional unit in the OS meta-capability market;

[0093] Receive feedback information generated by the server based on the acquisition request, wherein the feedback information includes all found OS meta-capabilities.

[0094] In some implementations, after generating a prompt message requesting the provision of the corresponding meta-capability for a vacant functional unit for which no OS meta-capability is found, the processor 1001 is further configured to:

[0095] Receive user input operations and extract the OS meta-capabilities carried by the input operations, wherein the OS meta-capabilities carried by the input operations are developed by the OS meta-capability developers for the idle functional unit.

[0096] In some implementations, the processor 1001 is further configured to construct an OS meta-capability market, wherein the construction process of the OS meta-capability market specifically includes:

[0097] The default configuration builds a dataset for storing the OS meta-capability marketplace;

[0098] Respond to the release command of OS meta-capabilities and obtain the OS meta-capabilities corresponding to the release command;

[0099] The OS meta-capabilities corresponding to the release command are published, and the OS meta-capabilities corresponding to the release command are stored in the dataset.

[0100] In some implementations, the processor 1001, when implementing the construction of the OS meta-capability market, is also used to implement:

[0101] In response to a control command for a preset OS meta-capability in the OS meta-capability market, the system executes a control operation corresponding to the control command on the preset OS meta-capability corresponding to the control command, wherein the control command includes a removal command or a version update command.

[0102] In some implementations, when the processor 1001 assembles all the acquired OS meta-capabilities to obtain the operating system to be built, it is specifically used to:

[0103] Obtain the business compilation chain between the at least two functional units, wherein the business compilation chain is used to reflect the logical matching relationship between the functional units;

[0104] Based on the business compilation chain, all acquired OS meta-capabilities are assembled to obtain the operating system to be built.

[0105] In some implementations, when the processor 1001 assembles all the acquired OS meta-capabilities according to the business compilation chain to obtain the operating system to be built, it is specifically used to implement:

[0106] The logical matching relationship between each OS meta-capability is determined based on the aforementioned business compilation chain;

[0107] Based on the logical matching relationship between each OS meta-capability, the OS meta-capabilities are assembled through the standard interface configured for each OS meta-capability to obtain the operating system to be built.

[0108] Please see Figure 3 , Figure 3 This is a schematic flowchart illustrating a method for building an operating system, provided in an embodiment of this application. This method can be applied to device construction. It involves dividing the operating system into functional units, acquiring the OS meta-capabilities corresponding to each completed function, and then assembling all acquired OS meta-capabilities to form the operating system. This allows for the reuse of some meta-capabilities from existing operating systems, requiring only the development of non-reusable meta-capabilities, thus reducing the workload and development cost of the operating system.

[0109] like Figure 3 As shown, the method for building this operating system includes steps S10 to S20.

[0110] Step S10: Obtain the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file.

[0111] Specifically, the operating system to be built is used on electronic devices to implement their basic functions. These electronic devices can be computers, mobile terminals, smart wearable devices, or virtual reality devices, etc. The configuration file reflects the system functions that the operating system to be built will implement. These system functions are the basic functions that the electronic device needs to perform. For example, system functions may include, but are not limited to, power-on, power-off, displaying the user interface, and implementing control functions based on the user interface (such as volume adjustment and brightness adjustment).

[0112] After obtaining the configuration file, a full-process business logic analysis can be performed to determine the basic business functions required to implement the entire business logic. Each basic business function is a single, complete function. Therefore, each basic business function can be considered a functional unit to obtain all the functional units that the operating system to be built must implement. Each operating system to be built includes at least two functional units, which cooperate according to the full-process business logic to achieve the basic functions required by the operating system. Each of the at least two functional units is the smallest functional unit among the system functions to be implemented by the operating system to be built, and cannot be further decomposed. Furthermore, each functional unit can and can only independently implement one complete function.

[0113] It should be noted that the functional units are determined by fully clarifying the business logic of the entire process from startup to operation of the system functions to be implemented by the operating system to be built. This is achieved through a full-stack analysis of the operating system, making the OS meta-capabilities corresponding to the functional units the basic capability units of the operating system to be built. After obtaining these OS meta-capabilities, an operating system can be assembled. When some system functions of the assembled operating system need to be changed, this can be achieved by replacing the OS meta-capabilities corresponding to those system functions. Furthermore, since each OS meta-capability corresponds to a minimum functional unit, all changes to the corresponding system functions of the operating system can be achieved by adjusting the OS meta-capabilities included in the operating system.

[0114] Please see Figure 4 , Figure 4 This is a schematic flowchart illustrating the process of acquiring functional units in an operating system construction method provided in this application embodiment.

[0115] like Figure 4 As shown, determining the at least two functional units to be implemented by the operating system to be built based on the configuration file specifically includes:

[0116] S11. Obtain the business logic for implementing the entire process of the electronic device from startup to operation according to the configuration file, wherein the electronic device is a hardware device to be loaded with the operating system to be built;

[0117] S12. Decouple the entire process business logic to obtain at least two functional units.

[0118] Specifically, the configuration file includes a description of the system functions of the operating system to be built. By parsing the configuration file, the system functions that the operating system needs to implement can be determined, i.e., the complete business logic for implementing the electronic device from startup to operation can be obtained. After obtaining the complete business logic, it is decoupled to divide it into at least two sub-business logics, each of which is treated as a functional unit. OS meta-capabilities are then configured independently for each sub-business logic (i.e., functional unit). Finally, all the configured OS meta-capabilities are assembled to form a modular operating system. This allows the electronic device to call and combine different OS meta-capabilities as needed, based on the complete business process it needs to implement. On the one hand, this allows the electronic device to be equipped with an operating system most suitable for its use; on the other hand, it reduces the development difficulty and cost of the operating system by utilizing OS meta-capabilities.

[0119] In one implementation, when obtaining functional units, the entire business logic can be retrieved from the configuration file using a compilation chain. This entire business logic is then parsed to obtain at least two functional units. Specifically, the configuration file can be used as input to the compilation chain. Parsing the configuration file using the compilation chain determines all the functional units required by the operating system to be built, as well as the business compilation chains between these functional units. These business compilation chains reflect the logical matching relationships between the functional units.

[0120] Furthermore, it should be noted that before obtaining the business logic for implementing the entire process of the electronic device from startup to operation according to the configuration file, the hardware configuration of the electronic device can be obtained first, and it can be checked whether the obtained hardware configuration is a known hardware configuration. If it is a known hardware configuration, it means that the operating system required by the electronic device already exists. In this case, the operating system corresponding to the known hardware configuration can be obtained directly, or at least two units corresponding to the known hardware configuration can be obtained directly without decoupling the entire process of business logic. Conversely, if the hardware configuration is an unknown hardware configuration, it means that the operating system required by the electronic device does not exist. In this case, the step of determining at least two functional units to be implemented by the operating system to be built according to the configuration file is executed.

[0121] S20. Obtain the OS meta-capabilities corresponding to each of the at least two functional units, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

[0122] Specifically, an OS meta-capability is the smallest unit of an operating system, capable of performing an independent function, i.e., a functional unit. An operating system can include multiple OS meta-capabilities, each of which is a development package used to implement a functional unit. Multiple development packages are assembled to obtain the operating system to be built. All OS meta-capabilities use the same programming language, such as, but not limited to, JavaScript and C / C++. For example, at least two functional units include functional unit a, functional unit b, and functional unit c. Functional unit a corresponds to meta-capability A, functional unit b corresponds to meta-capability B, and functional unit c corresponds to meta-capability C. Then, assembling meta-capabilities A, B, and C yields the operating system that the electronic device needs to run.

[0123] It should be noted that the operating system to be built is a patchwork operating system. Each OS meta-capability in this operating system can be adjusted according to changes in the system functions of the operating system. These adjustments can include, but are not limited to, adding new OS meta-capabilities, deleting OS meta-capabilities, and replacing OS meta-capabilities. This allows for rapid adjustment of the operating system when the system functions required by the electronic device undergo minor changes, thus quickly adapting the operating system to the electronic device and reducing the difficulty and cost of building the operating system. For example, if the operating system includes meta-capabilities A, B, and C, and the business logic required by the electronic device running this operating system changes, removing functional unit b (which was used to implement functional unit b), then meta-capability B can be deleted first, and then meta-capabilities A and C can be reassembled to obtain the operating system required by the changed electronic device.

[0124] In some implementations, after identifying at least two functional units, OS meta-capabilities can be developed for each functional unit; alternatively, OS meta-capabilities can be searched for for each functional unit in a pre-built OS meta-capability marketplace. It should be noted that when searching for OS meta-capabilities for each functional unit in a pre-built OS meta-capability marketplace, it's possible that all functional units will find OS meta-capabilities, while some may not. For functional units where no OS meta-capabilities are found, the OS meta-capability developer can be prompted to develop OS meta-capabilities for that functional unit.

[0125] For example, when developing OS meta-capabilities for each functional unit, after determining at least two functional units required by the terminal device according to the configuration file, indication information is generated to indicate the development of OS meta-capabilities corresponding to the functional units, and the indication information is displayed so that OS meta-capability developers can develop OS meta-capabilities for the functional units. This application embodiment, by directly developing OS meta-capabilities for each functional unit, can accurately obtain the OS meta-capabilities corresponding to each functional unit.

[0126] For example, when searching for OS meta-capabilities for each functional unit in a pre-built OS meta-capability marketplace, after determining at least two functional units required by the terminal device based on the configuration file, the pre-built OS meta-capability marketplace is accessed to find the OS meta-capabilities corresponding to each functional unit. For functional units where OS meta-capabilities are found, the found OS meta-capabilities are directly used as the corresponding OS meta-capabilities for the functional unit. For functional units where no OS meta-capabilities are found, a prompt is made to develop OS meta-capabilities for that functional unit. This example provides OS meta-capabilities for functional units through a pre-built OS meta-capability marketplace, which can reuse already developed OS meta-capabilities, reduce the cost of building the operating system, and improve the speed of operating system construction.

[0127] Based on this, such as Figure 5 As shown, the acquisition of the OS meta-capabilities corresponding to each of the at least two functional units specifically includes:

[0128] S21. Search for the OS meta-capabilities corresponding to each functional unit in the pre-established OS meta-capability market, wherein the OS meta-capability market includes at least two OS meta-capabilities.

[0129] S22. For vacant functional units for which no OS meta-capabilities are found, generate a prompt message asking for the corresponding OS meta-capabilities of the vacant functional unit.

[0130] Specifically, in step S21, the OS meta-capability market is used to deploy pre-developed OS meta-capabilities. That is, the OS meta-capability market deploys multiple preset OS meta-capabilities. These multiple preset OS meta-capabilities may be developed by the same OS meta-capability developer or by different OS meta-capability developers. Furthermore, among these multiple preset OS meta-capabilities, there may be two or more preset OS meta-capabilities that implement the same functional unit.

[0131] The OS meta-capability market can include preset OS meta-capabilities developed using the same programming language, or preset OS meta-capabilities developed using different programming languages. For example, the OS meta-capability market includes preset OS meta-capability 1, preset OS meta-capability 2, preset OS meta-capability 3, preset OS meta-capability 4, ..., preset OS meta-capability N, where N is a positive integer; the programming language for preset OS meta-capabilities 1 through M is JavaScript, and the programming language for preset OS meta-capabilities M+1 through N is C++, where preset OS meta-capability 1 and preset OS meta-capability M+1 correspond to the same functional unit.

[0132] In some implementations, such as Figure 6 As shown, the construction process of the OS meta-capability market specifically includes:

[0133] The default configuration builds a dataset for storing the OS meta-capability marketplace;

[0134] Respond to the release command of OS meta-capabilities and obtain the OS meta-capabilities corresponding to the release command;

[0135] The OS meta-capabilities corresponding to the release command are published, and the OS meta-capabilities corresponding to the release command are stored in the dataset.

[0136] Specifically, the dataset stores the preset OS meta-capabilities included in the OS meta-capability marketplace. The dataset can be divided into several subsets, each corresponding to a programming language. This allows OS meta-capabilities developed using different programming languages ​​to be stored in different subsets, facilitating the search for OS meta-capabilities in the marketplace. Furthermore, correlations can be set between preset OS meta-capabilities, reflecting the probability that two OS meta-capabilities are used to build the same operating system. When searching for OS meta-capabilities in the marketplace, if a meta-capability is found, a notification message can be generated based on its correlation with other OS meta-capabilities. This notification message reminds the builder whether any OS meta-capabilities have been overlooked, providing convenience. Specifically, when determining whether to generate a notification message based on the correlation between a meta-capability and other OS meta-capabilities, a preset correlation threshold can be used. If an OS meta-capability has a correlation greater than the preset correlation threshold, a notification message is generated, and the meta-capability name of the missing meta-capability is added to the notification message.

[0137] Release commands are generated based on release operations performed by OS meta-capability developers and are used to release OS meta-capabilities to the OS meta-capability marketplace. For example, ... Figure 6As shown, OS meta-capability developers send a release command to the server. The server receives and responds to the release command, retrieves the OS meta-capability the developer wants to release, adds the releaseable OS meta-capability to the OS meta-capability marketplace, and then publishes the releaseable OS meta-capability to the client device to update the meta-capability marketplace installed on the client device. Before responding to the release command, the server can also verify the releaseable OS meta-capability corresponding to the release command to ensure its security, thereby improving the security of the OS meta-capability marketplace.

[0138] Furthermore, the preset OS meta-capabilities in the OS meta-capability marketplace can be updated or removed. Correspondingly, the construction process of the OS meta-capability marketplace may also include:

[0139] In response to a control command for a preset OS capability in the OS capability market, the control operation corresponding to the control command is executed on the preset OS capability corresponding to the control command.

[0140] Specifically, control commands may include, but are not limited to, removal commands and version update commands. The control operation corresponding to the removal command is to remove the preset OS meta-capabilities, and the control operation corresponding to the version update command is to upgrade the preset OS meta-capabilities.

[0141] Control commands can be sent by the developers of the OS meta-capabilities corresponding to the preset OS meta-capabilities, or they can be automatically generated by the server based on the current state of the preset OS meta-capabilities.

[0142] For example, when the control command is a version update command, the control command can be sent directly from the OS meta-capability developer to the server, and the control command can include the updated preset OS meta-capability; or the server can generate the control command based on the received updated preset OS meta-capability. That is, the OS meta-capability developer will send the updated preset OS meta-capability to the server, and the server will compare the received updated preset OS meta-capability with the currently stored preset OS meta-capability. When the version of the updated preset OS meta-capability is higher than the version of the currently stored preset OS meta-capability, the server will generate a version update command to obtain the control command.

[0143] For example, when the control command is a delisting command, the control command can be sent directly to the server by the OS meta-capability developer, or it can be automatically generated by the server for the preset OS meta-capability based on the current state of the preset OS meta-capability. The current state that triggers the server to automatically generate the delisting command may include, but is not limited to, an insecure state, an illegal state, and a state that violates the preset release agreement.

[0144] In some implementations, the deployment device can request OS meta-capabilities from the OS meta-capability marketplace via the Internet, or it can pre-back up the OS meta-capabilities included in the OS meta-capability marketplace to the deployment device's local storage, or it can back them up to an external device (e.g., a portable hard drive, an electronic device with storage capabilities, etc.). In a specific implementation of this application embodiment, as follows... Figure 7 As shown, the OS meta-capability marketplace is deployed on the server side and presented to users in the form of an application. The client device will have an application named Meta-capability marketplace deployed, which presents all the OS meta-capabilities in the OS meta-capability marketplace, so that users can quickly find all the OS meta-capabilities that can be directly obtained through the meta-capability marketplace.

[0145] For example, each preset OS meta-capability in the OS meta-capability marketplace is configured with an OS meta-capability name. Each OS meta-capability name is presented in the meta-capability marketplace application. The device can learn about the OS meta-capabilities contained in the OS meta-capability marketplace by loading the meta-capability marketplace application, and then download the OS meta-capability corresponding to the OS meta-capability name by selecting an OS meta-capability in the meta-capability marketplace application.

[0146] Based on this, such as Figure 8 As shown, the step of searching for the corresponding OS meta-capabilities for each functional unit within the pre-established OS meta-capability market specifically includes:

[0147] S211. Send a request to the server to obtain the OS meta-capabilities corresponding to each functional unit, so that the server responds to the request and searches for the OS meta-capabilities corresponding to each functional unit in the OS meta-capability market.

[0148] S212. Receive feedback information generated by the server based on the acquisition request.

[0149] Specifically, the server can be a backend server or the cloud, etc. The preset OS meta-capabilities in the OS meta-capability market are stored on the server. The server provides OS meta-capabilities to each built device and receives OS meta-capabilities published by each OS meta-capability developer.

[0150] The request can include the name of the OS meta-capability. Upon receiving the request, the server can search for the corresponding OS meta-capability in the OS meta-capability marketplace based on the name included in the request. However, in practical applications, when the server presents the OS meta-capability marketplace to the deployment device, the deployment device can first search for the OS meta-capability corresponding to the functional unit in the marketplace. Once found, the device requests the server to download the OS meta-capability. For example, if the deployment device needs to obtain an OS meta-capability named OS meta-capability A, it sends a request containing "OS meta-capability A" to the server. The server finds the OS meta-capability corresponding to OS meta-capability A in the OS meta-capability marketplace and transmits it to the deployment device, allowing the device to download the corresponding OS meta-capability.

[0151] The feedback information is generated by the server and is used to provide OS meta-capabilities to the deployment device. In other words, the feedback information includes all found OS meta-capabilities, enabling the deployment device to download OS meta-capabilities from the OS meta-capability marketplace. Of course, in practical applications, the server can generate a separate feedback message for each OS meta-capability. That is, when an OS meta-capability is found, a feedback message is generated for that OS meta-capability, and this feedback message is used to send that OS meta-capability back to the deployment device. This allows multiple OS meta-capabilities to be sent back to the deployment device in parallel, improving the efficiency of OS meta-capability acquisition and thus increasing the speed of operating system deployment.

[0152] Furthermore, in step S22, the OS meta-capability market includes pre-developed OS meta-capabilities. This means that each preset OS meta-capability in the market corresponds to a functional unit that was known before the operating system was built. However, the operating system to be built may include functional units that were not known before its construction. Therefore, when searching for OS meta-capabilities corresponding to functional units in the OS meta-capability market, it's possible that no OS meta-capability is found for a given functional unit. This means that the operating system to be built may contain vacant functional units for which no OS meta-capabilities have been found. To address this, when a vacant functional unit for which no OS meta-capability is found is encountered, a prompt message requesting the provision of the corresponding OS meta-capability can be generated. This allows the operating system builder to be aware of the prompt and develop OS meta-capabilities for the vacant functional unit. This maximizes the reuse of existing OS meta-capabilities while ensuring the availability of OS meta-capabilities for each functional unit, thus guaranteeing a high success rate for operating system construction.

[0153] For example, after generating a prompt message asking for the corresponding meta-capability for an unused functional unit for which no OS meta-capability was found, the method further includes:

[0154] Receive user input operations and extract the OS meta-capabilities carried by the input operations.

[0155] Specifically, the input operation can be formed by the user based on the input interface, through which the user inputs OS meta-capabilities to the setup device, enabling the setup device to obtain the OS meta-capabilities corresponding to the vacant functional unit. The OS meta-capabilities corresponding to the vacant functional unit can be developed by an OS meta-capability developer for the vacant functional unit, or they can be selected by the setup device from an external device, etc. Furthermore, after obtaining the OS meta-capabilities corresponding to the vacant functional unit, the OS meta-capabilities can be associated with the vacant functional unit (e.g., using the function to be implemented by the vacant functional unit as the meta-capability name), and then the OS meta-capabilities corresponding to the vacant functional unit are published to the server. This publication of the OS meta-capabilities corresponding to the vacant functional unit to the server can be done by the OS meta-capability developer through other electronic devices, or it can be done by the setup device after obtaining the OS meta-capabilities corresponding to the vacant functional unit, etc.

[0156] Furthermore, in step S22, after obtaining all OS meta-capabilities, the logical matching relationship between OS meta-capabilities can be known, and then the OS meta-capabilities are assembled according to the logical matching relationship.

[0157] For example, assembling all the acquired OS meta-capabilities to obtain the operating system to be built specifically includes:

[0158] Obtain the business compilation chain between the at least two functional units;

[0159] Based on the business compilation chain, all acquired OS meta-capabilities are assembled to obtain the operating system to be built.

[0160] Specifically, the service compilation chain serves as the basis for assembling OS meta-capabilities corresponding to functional units. This service compilation chain reflects the logical matching relationships between functional units. Therefore, based on the service compilation chain, the logical matching relationships between OS meta-capabilities can be determined. For each OS meta-capability, OS meta-capabilities connected to it can be identified according to the logical matching relationships. This process of assembling each OS meta-capability and its connected OS meta-capabilities is then repeated until all OS meta-capabilities and their connected OS meta-capabilities are assembled, resulting in the operating system.

[0161] To assemble various OS meta-capabilities, an assembly interface needs to be pre-configured for each OS meta-capability. This assembly interface can be an I / O interface, SPI interface, TCP / IP protocol interface, etc. In one specific implementation of this application, to facilitate the interoperability of OS meta-capabilities developed by different developers, a standard interface can be pre-set for each OS meta-capability. Each OS meta-capability in the OS meta-capability marketplace is configured with this standard interface, allowing any two OS meta-capabilities in the marketplace to be assembled through their respective configured standard interfaces. This facilitates the combination and replacement of OS meta-capabilities developed by different developers. It should be noted that the standard interface conforms to telecommunications industry standards.

[0162] Based on this, in one implementation, assembling all the acquired OS meta-capabilities according to the business compilation chain to obtain the operating system to be built specifically includes:

[0163] The logical matching relationship between each OS meta-capability is determined based on the aforementioned business compilation chain;

[0164] Based on the logical matching relationship between each OS meta-capability, the OS meta-capabilities are assembled through the standard interface configured for each OS meta-capability to obtain the operating system to be built.

[0165] Specifically, when assembling OS meta-capabilities through standard interfaces configured for each OS meta-capability, communication relationships can be established between two logically matched OS meta-capabilities through these standard interfaces to assemble them. The assembly process can follow a building block principle: first, OS meta-capabilities are assembled into several software modules, and then these software modules are assembled. This layer-by-layer assembly not only improves assembly efficiency but also reduces the error rate. These software modules can contain one or more OS meta-capabilities. For example, the OS meta-capabilities can be categorized by their operating system layer (e.g., user layer and system layer), and then the OS meta-capabilities within each operating system layer can be further divided into several software modules based on their functionalities. Finally, the OS meta-capabilities within each software module can be assembled. Furthermore, after the operating system is built, it can be installed on electronic devices to enable them to perform their required basic functions.

[0166] In some implementations, after the operating system is built, its OS meta-capabilities can be adjusted according to changes in the corresponding system functions. This allows the adjusted operating system to adapt to the adjusted system functions. Adjusting OS meta-capabilities can include adding, deleting, or replacing OS meta-capabilities. This allows for adjustments to only a portion of the OS meta-capabilities to create an operating system compatible with the adjusted system functions, without requiring the entire operating system to be redeveloped. This reduces the workload, improves development efficiency, and saves on development costs.

[0167] In summary, the operating system construction method provided in this application involves obtaining the configuration file of the operating system to be constructed, determining at least two functional units to be implemented by the operating system based on the configuration file, obtaining the OS meta-capabilities corresponding to each of the at least two functional units, and assembling all the obtained OS meta-capabilities to obtain the operating system to be constructed. This application decouples the operating system from the hardware and uses OS meta-capability assembly to construct the operating system. This not only allows for the reuse of existing OS meta-capabilities but also enables on-demand construction of the operating system, thereby facilitating the convenient, fast, and low-cost development of operating systems for various hardware devices, significantly reducing the difficulty and cost of operating system development. Furthermore, this application configures standard interfaces for each OS meta-capability, allowing for the assembly of OS meta-capabilities released by different developers. This avoids repeated development of OS meta-capabilities for implementing the same functional units and allows for the selection of the lowest-cost OS meta-capability when multiple versions exist, further reducing the operating system development cost. In addition, this application embodiment provides OS meta-capabilities to builders through an OS meta-capability marketplace, enabling builders to quickly and easily obtain developed OS meta-capabilities and providing download channels, further improving the convenience of operating system construction.

[0168] Please see Figure 9 , Figure 9 An embodiment of this application also provides a schematic block diagram of an operating system building apparatus, which is used to execute the aforementioned operating system building method.

[0169] like Figure 9 As shown, the device for building the operating system specifically includes an acquisition module and an assembly module.

[0170] The acquisition module 100 is used to acquire the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file.

[0171] Assembly module 200 is used to acquire the OS meta-capabilities corresponding to each of the at least two functional units, and assemble all the acquired OS meta-capabilities to obtain the operating system to be built.

[0172] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the above-described apparatus and modules can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0173] The aforementioned device can be implemented as a computer program that can run on the installation equipment.

[0174] This application also provides a computer-readable storage medium storing a computer program, which includes program instructions. The processor executes these program instructions to implement any of the operating system construction methods provided in this application. For example, when the computer program is loaded by the processor, it can perform the following steps: obtaining a configuration file of the operating system to be built, and determining at least two functional units to be implemented by the operating system based on the configuration file; obtaining OS meta-capabilities corresponding to each of the at least two functional units, and assembling all the obtained OS meta-capabilities to obtain the operating system to be built.

[0175] The computer-readable storage medium can be an internal storage unit of the setup device described in the foregoing embodiments, such as the hard drive or memory of the setup device. Alternatively, the computer-readable storage medium can be an external storage device of the setup device, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital Card (SD), or Flash Card equipped on the setup device.

[0176] This application also provides an operating system, such as... Figure 10 As shown, the operating system includes at least two OS meta-capabilities. Each of the at least two OS meta-capabilities is used to implement a functional unit of the system function corresponding to the operating system. Each OS meta-capability is assembled according to the business compilation chain of the operating system.

[0177] In some implementations, the OS meta-capabilities are formed by decoupling the entire operating system stack.

[0178] In some implementations, each of the at least two OS meta-capabilities is configured with a standard interface so that any two OS meta-capabilities can be assembled.

[0179] In some implementations, the OS meta-capabilities in the operating system are assembled in a modular fashion through their respective configured standard interfaces.

[0180] In some implementations, the operating system's business compilation chain is used to reflect the logical matching relationships between various OS meta-capabilities.

[0181] In some implementations, the OS meta-capabilities included in the operating system can be adjusted, wherein the adjustment operation is formed according to the adjustment of the system functions to be performed by the operating system, and the adjustment operation includes one or more of the following: adding OS meta-capabilities, deleting OS meta-capabilities, and replacing OS meta-capabilities.

[0182] In summary, the embodiments of this application provide an operating system that is assembled from at least two OS meta-capabilities. The OS meta-capabilities in the operating system can be adjusted according to the system functions to be implemented. This allows the operating system to flexibly adapt to the basic functions required by electronic devices and enables the rapid installation of an operating system on electronic devices.

[0183] It should be noted that the above-mentioned operating system can be built using the above-mentioned operating system construction method, and the OS meta-capabilities included in the operating system and the assembly method between OS meta-capabilities can all be understood from the above-mentioned operating system construction method. For the sake of convenience and brevity, the OS meta-capabilities in the operating system and the assembly method between OS meta-capabilities described above can be referred to the corresponding descriptions in the foregoing method embodiments, and will not be repeated here.

[0184] This application also provides an electronic device equipped with the operating system described above. In other words, the operating system equipped with the electronic device is a modular operating system as described above.

[0185] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. An operating system, characterized in that, An operating system is installed on an electronic device, serving as the operating system for that device and implementing its basic functions. The operating system includes at least two OS meta-capabilities, each configured with a standard interface to allow assembly of any two OS meta-capabilities. Each of the at least two OS meta-capabilities is used to implement a functional unit within the system functions corresponding to the operating system. Each OS meta-capability is assembled according to the business compilation chain of the operating system. The functional unit is the smallest functional unit within the system functions to be implemented by the operating system, and each functional unit independently implements only one complete function. The functional unit is determined by fully clarifying the business logic of the entire process from startup to operation of the system functions to be implemented by the operating system, using a full-stack analysis method. S-meta-capabilities originate from the OS meta-capability marketplace and / or user-inputted OS meta-capabilities. The dataset corresponding to the OS meta-capability marketplace includes several sub-datasets, each corresponding to a programming language. The OS meta-capabilities within each sub-dataset are correlated, reflecting the probability that two OS meta-capabilities are used to build the same operating system. When an OS meta-capability is found, a reminder is generated based on its correlation with other OS meta-capabilities. This reminder alerts the builder whether any OS meta-capabilities have been overlooked. The OS meta-capabilities in the OS meta-capability marketplace are published by OS meta-capability developers. Before publishing OS meta-capabilities published by developers in the OS meta-capability marketplace, the published OS meta-capabilities are verified to ensure their security. Before acquiring the business logic for implementing the entire process from startup to operation of the electronic device, the hardware configuration of the electronic device is acquired first, and it is checked whether the acquired hardware configuration is a known hardware configuration. If it is a known hardware configuration, at least two units corresponding to the known hardware configuration are acquired, and there is no need to decouple the entire process business logic. If the hardware configuration is an unknown hardware configuration, at least two functional units to be implemented by the operating system to be built are determined according to the configuration file.

2. The operating system according to claim 1, characterized in that, The OS meta-capabilities are formed by decoupling the entire operating system stack.

3. The operating system according to claim 1, characterized in that, The OS meta-capabilities are assembled using standard interfaces configured in a modular fashion.

4. The operating system according to claim 1, characterized in that, The business compilation chain is used to reflect the logical matching relationship between various OS meta-capabilities.

5. The operating system according to claim 1, characterized in that, The OS meta-capabilities included in the operating system can be adjusted, wherein the adjustment operation is formed according to the adjustment of the system functions to be performed by the operating system, and the adjustment operation includes one or more of the following: adding OS meta-capabilities, deleting OS meta-capabilities, and replacing OS meta-capabilities.

6. A method for building an operating system, characterized in that, The method for building an operating system as described in any one of claims 1-5 specifically includes: Obtain the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file; Obtain the OS meta-capabilities corresponding to each of at least two functional units, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

7. The method for building an operating system according to claim 6, characterized in that, The determination of at least two functional units to be implemented by the operating system to be built based on the configuration file specifically includes: According to the configuration file, obtain the business logic for implementing the entire process of the electronic device from startup to operation, wherein the electronic device is a hardware device that is to load the operating system to be built; The entire process business logic is decoupled to obtain at least two functional units.

8. The method for building an operating system according to claim 7, characterized in that, The acquisition of the OS meta-capabilities corresponding to each of the at least two functional units specifically includes: Search for the OS meta-capabilities corresponding to each functional unit in a pre-established OS meta-capability market, wherein the OS meta-capability market includes at least two OS meta-capabilities; For any unused functional unit for which no OS meta-capability was found, a prompt message will be generated asking for the corresponding OS meta-capability of the unused functional unit.

9. The method for building an operating system according to claim 8, characterized in that, The OS meta-capability marketplace is deployed on the server and presented to users in the form of an application.

10. The method for building an operating system according to claim 9, characterized in that, The process of searching for the corresponding OS meta-capabilities for each functional unit within a pre-established OS meta-capability market specifically includes: Send a request to the server to obtain the OS meta-capabilities corresponding to each functional unit, so that the server responds to the request and searches for the OS meta-capabilities corresponding to each functional unit in the OS meta-capability market; Receive feedback information generated by the server based on the acquisition request, wherein the feedback information includes the found OS meta-capabilities.

11. The method for building an operating system according to claim 8, characterized in that, After generating a prompt message requesting the provision of the corresponding meta-capability for a vacant functional unit for which no OS meta-capability was found, the method further includes: Receive user input operations and extract the OS meta-capabilities carried by the input operations, wherein the OS meta-capabilities carried by the input operations are developed by the OS meta-capability developers for the idle functional unit.

12. The method for building an operating system according to claim 7, characterized in that, The process of building the OS meta-capability market is as follows: Build a dataset for storing the OS meta-capability marketplace; Respond to the release command of OS meta-capabilities and obtain the OS meta-capabilities corresponding to the release command; The OS meta-capabilities corresponding to the release command are published, and the OS meta-capabilities corresponding to the release command are stored in the dataset.

13. The method for building an operating system according to claim 12, characterized in that, The process of building the OS meta-capability market also includes: In response to a control command for a preset OS meta-capability in the OS meta-capability market, the system executes a control operation corresponding to the control command on the preset OS meta-capability corresponding to the control command, wherein the control command includes a removal command or a version update command.

14. The method for building an operating system according to claim 6, characterized in that, The process of assembling all acquired OS meta-capabilities to obtain the operating system to be built specifically includes: Obtain the business compilation chain between the at least two functional units, wherein the business compilation chain is used to reflect the logical matching relationship between the functional units; Based on the business compilation chain, all acquired OS meta-capabilities are assembled to obtain the operating system to be built.

15. The method for building an operating system according to claim 14, characterized in that, The step of assembling all the acquired OS meta-capabilities according to the business compilation chain to obtain the operating system to be built specifically includes: The logical matching relationship between each OS meta-capability is determined based on the aforementioned business compilation chain; Based on the logical matching relationship between each OS meta-capability, the OS meta-capabilities are assembled through the standard interface configured for each OS meta-capability to obtain the operating system to be built.

16. An operating system setup device, characterized in that, The apparatus for building an operating system as described in any one of claims 1-5 specifically includes: The acquisition module is used to acquire the configuration file of the operating system to be built, and determine at least two functional units to be implemented by the operating system to be built based on the configuration file. An assembly module is used to acquire the OS meta-capabilities corresponding to each of at least two functional units, and to assemble all the acquired OS meta-capabilities to obtain the operating system to be built.

17. A system for building an operating system, characterized in that, The system is used to build an operating system as described in any one of claims 1-5. The system includes a building device and a server. The server stores an OS meta-capability marketplace. The building device is used to obtain the configuration file of the operating system to be built, determine at least two functional units to be implemented by the operating system to be built according to the configuration file, obtain the OS meta-capabilities corresponding to each functional unit through the server storing the OS meta-capability marketplace, and assemble all the obtained OS meta-capabilities to obtain the operating system to be built.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to implement the method for building an operating system as described in any one of claims 6 to 15.

19. A construction device, characterized in that, The assembly equipment includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the computer program and, when executing the computer program, implement the method for building an operating system as described in any one of claims 6 to 15.

20. An electronic device, characterized in that, The electronic device is equipped with the operating system described in any one of claims 1-5.

Images