Application software component method, apparatus, computer device and storage medium

Abstract

The application relates to an application software component method, device, computer equipment and storage medium. The method comprises the following steps: determining a component of to-be-loaded application software as a target component; the target component comprises a target component identifier and a target partition identifier; obtaining a platform identifier of the to-be-loaded application software; obtaining target component configuration information of the target component from a scattered loading component configuration parameter table according to the platform identifier, the target component identifier and the target partition identifier; and loading the target component into a memory of a corresponding partition to perform registration and running based on the target component configuration information. The method can realize that multiple platforms and multiple models share one application solidification image, reduce the workload of developers and testers, improve efficiency, and reduce the maintenance cost in the later period.

Description

Technical Field

[0001] This application relates to the field of embedded operating system technology, and in particular to an application software component method, apparatus, computer device, and storage medium. Background Technology

[0002] With the development of flight technology, more and more users are choosing airplanes as their mode of transportation, and airplanes have become integrated into people's lives and are closely related to them. Correspondingly, the demand for in-flight application software is also increasing.

[0003] Existing airborne application software is tightly coupled with system peripherals and hardware operating platforms. Airborne application software needs to be developed for various aircraft models and on multiple hardware operating platforms, resulting in a lot of repetitive development work and low efficiency. Summary of the Invention

[0004] Therefore, it is necessary to provide an application software component method, apparatus, computer device, and storage medium that can improve software utilization efficiency in response to the above-mentioned technical problems.

[0005] An application software component method, the method being applied in a partition operation processor, the method comprising:

[0006] The components of the application software to be loaded are identified as target components; the target components include a target component identifier and a target partition identifier;

[0007] Obtain the platform identifier of the application software to be loaded;

[0008] Based on the platform identifier, the target component identifier, and the target partition identifier, obtain the target component configuration information of the target component from the distributed loading component configuration parameter table;

[0009] Based on the target component configuration information, the target component is loaded into the memory of the corresponding partition for registration and operation.

[0010] In one embodiment, the method further includes:

[0011] Multiple application software programs are divided according to their functions, resulting in multiple components with different functions.

[0012] The components are run on the component runtime platform of the corresponding partition.

[0013] In one embodiment, the distributed loading component configuration parameter table includes a component solidification information table, a component configuration information offset address table, and component configuration information corresponding to multiple platforms;

[0014] The component curing information table includes the curing address of each component configuration information;

[0015] The component configuration information offset address table includes the offset address of each component configuration information;

[0016] The component configuration information includes the configuration data of each component in each of the partitions.

[0017] In one embodiment, loading the target component into the memory of the corresponding partition based on the target component configuration information includes:

[0018] Obtain the fixed address and runtime address of the target component from the target component configuration information;

[0019] The firmware program of the target component is read according to the firmware address, and the segment information of the firmware program is parsed to obtain the corresponding target code;

[0020] Move the target code to the memory corresponding to the execution address;

[0021] The initialization function is called to initialize the memory address of the target code.

[0022] In one embodiment, the registration step of the target component includes:

[0023] The system call interface is used to read the configuration information of the target component.

[0024] Obtain the component information of the target component from the target component configuration information. The component information includes the entry address, partition identifier, and rate.

[0025] Based on the entry address, partition identifier, and rate, the entry address of the relocated target component is registered to the corresponding partition and rate group.

[0026] In one embodiment, the method further includes:

[0027] The platform runs the component to read the target component's subscription and publish message configuration information.

[0028] The subscription and publish message configuration information is transmitted to the target component.

[0029] In one embodiment, after the registration of the target component is completed, the method further includes a component initialization process for the target component.

[0030] An application software component apparatus, the apparatus comprising:

[0031] The target component determination module is used to determine the components of the application software to be loaded as target components; the target components include a target component identifier and a target partition identifier;

[0032] The platform identifier acquisition module is used to acquire the platform identifier of the application software to be loaded.

[0033] The target component configuration information acquisition module is used to acquire the target component configuration information of the target component from the distributed loading component configuration parameter table based on the platform identifier, the target component identifier, and the target partition identifier;

[0034] The target component execution module is used to load the target component into the memory of the corresponding partition based on the target component configuration information and perform registration and execution.

[0035] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the application software component method described in the above embodiments.

[0036] A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the application software component method described in the above embodiments.

[0037] The aforementioned application software component method, apparatus, computer device, and storage medium divide multiple application software programs according to their functions through a partitioning operation processor, resulting in multiple components with different functions. These components then run on the component runtime platform of their respective partitions. When loading a target component of an application software to be loaded, the component runtime platform determines the target component configuration information from a distributed loading component configuration parameter table based on the platform identifier, target component identifier, and target partition identifier of the application software to be loaded. Based on this configuration information, the target component is loaded into the memory of the corresponding partition for registration and execution. This achieves a method for directly loading components of application software to be loaded on different platforms to run the application. A single application software component method can adapt to multiple different platforms, improving application software development efficiency and saving development costs.

[0038] The application software component approach provided in this solution is based on a component runtime framework structure. Developing application software on this framework enables multiple platforms and models to share the same application image, reducing the workload of developers and testers and improving the efficiency of application software development. Attached Figure Description

[0039] Figure 1 This is an application scenario diagram of the application software component method in one embodiment;

[0040] Figure 2 This is a schematic diagram of executable firmware for a system in one embodiment;

[0041] Figure 3 This is a flowchart illustrating the application of a software component method in one embodiment;

[0042] Figure 4 This is a flowchart illustrating the steps of applying software components in one embodiment;

[0043] Figure 5 This is a flowchart illustrating the application of a software component method in another embodiment;

[0044] Figure 6 This is a structural block diagram of an application software component device in one embodiment;

[0045] Figure 7 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] The application software component method provided in this application can be applied to, for example... Figure 1 The application environment shown is illustrated. This application software component method is applied within an application software component runtime framework, which includes a partition operation processor 102, a component runtime platform 104 corresponding to at least one partition, two components 106 corresponding to at least one partition, a distributed loading component configuration parameter table 108, and hardware 110. That is, the system includes multiple partitions, each partition comprising two components and a component runtime platform.

[0048] The firmware related to the partition operation processor 102 and application software includes system executable firmware and distributed loading component configuration parameter firmware. For example... Figure 2 The diagram illustrates the executable firmware of the system. As shown, each partition includes two component images, corresponding to the two components within that partition. The executable firmware includes component images for partitions 1 to n, where each partition includes partition 1 component image 1 and partition 1 component image 2; and each component image for a partition includes an application program. The executable firmware also includes partition operation processor images and application partition images; each partition corresponds to one application partition image, namely application partition image 1 to application partition image n; each application partition image has a partition runtime framework program.

[0049] like Figure 3 The diagram illustrates a schematic of the distributed loading component configuration parameter firmware. As shown, this distributed loading component configuration parameter firmware includes a component firmware information table, a component configuration information offset address table, and component configuration information corresponding to each platform. The component firmware information table includes the firmware space information for each component, from component 1 to component n; the firmware space information includes the firmware address of the component configuration information. The component configuration information offset address table (i.e., the configuration information offset address table corresponding to the platform ID in the diagram) includes the component configuration information offset address corresponding to each platform identifier. The component configuration information corresponding to each platform identifier includes the corresponding partition configuration image, where the partition configuration image includes the configuration data of each component within each partition, for example, the configuration data of component 0 in partition 1 to component n in partition n.

[0050] Component 106 for a given partition runs on a corresponding component runtime platform 104. The partition operation processor 102 can call the component runtime platform 104 to load and run component 106. Component 106 is an executable file with specific functions.

[0051] In one embodiment, such as Figure 4 As shown, an application software component method is provided, which is applied to... Figure 1 The partition operation processor 102 in the example is used as an example, including the following steps:

[0052] Step S402: Determine the components of the application software to be loaded as target components; the target components include target component identifiers and target partition identifiers.

[0053] In one embodiment, before determining the component of the application software to be loaded as the target component, the method further includes: dividing the multiple application software according to the functions of the application software to obtain multiple components with different functions; and running the multiple components on the component runtime platform of the corresponding partition.

[0054] For example, in a serial port-based remote multi-functional control system (assuming there are 8 function points, coded as F1 to F8), each function can be broken down into a component, resulting in 8 components (i.e., executable files). If the application software component approach proposed in this solution is not used, the conventional approach is to integrate all functions into a single program (i.e., executable file).

[0055] Step S404: Obtain the platform identifier of the application software to be loaded.

[0056] Among them, the component identifier is used to distinguish each component, and can be formed by any one or more combinations of text, numbers and characters; the partition identifier is used to distinguish each partition; and the platform identifier is used to distinguish the platform on which each application software is loaded.

[0057] Specifically, when loading application software, the partition operation processor determines one or more corresponding components as target components based on the application software, where each component has a corresponding component identifier and partition identifier. The partition operation processor also needs to obtain the platform identifier of the application software and then load the target components corresponding to the platform based on the platform identifier.

[0058] Step S406: Obtain the target component configuration information of the target component from the distributed loading component configuration parameter table based on the platform identifier, the target component identifier, and the target partition identifier.

[0059] In one embodiment, the distributed loading component configuration parameter table includes a component solidification information table, a component configuration information offset address table, and component configuration information corresponding to multiple platforms. The component solidification information table includes the solidification address of each component configuration information; the component configuration information offset address table includes the offset address of each component configuration information; and the component configuration information includes the configuration data of each component in each partition.

[0060] The distributed loading component configuration parameter table is mainly used to manage component embedding, loading, runtime address configuration, component attribute configuration, component subscription / publishing message configuration, and Interface Control Document (ICD) message configuration. The ICD specifies the exact communication protocol format within the document.

[0061] The fixed address refers to the address of non-volatile memory such as flash memory. Component configuration information includes data such as the component's corresponding runtime address, firmware, component information, and subscription / publish message configuration information; among which, the component information includes the component's corresponding entry address, partition identifier, and speed.

[0062] Specifically, the component runtime platform obtains the corresponding target component configuration information from the distributed loading component configuration parameter table based on the platform identifier, target component identifier, and target partition identifier.

[0063] Step S408: Based on the target component configuration information, load the target component into the memory of the corresponding partition and perform registration and operation.

[0064] When the partition operation processor loads the application software to be loaded, it first determines one or more target components, then loads the target components into the memory of the corresponding partition, and then performs component registration. After registration is completed, the target components can be scheduled to run.

[0065] In one embodiment, loading the target component into the memory of the corresponding partition based on the target component configuration information includes: obtaining the firmware address and runtime address of the target component from the target component configuration information; reading the firmware program of the target component according to the firmware address through the component runtime platform, and parsing the segment information of the firmware program to obtain the corresponding target code; moving the target code to the memory corresponding to the runtime address; and calling the initialization function to initialize the memory address of the target code.

[0066] The runtime address refers to the address in memory where the program runs, that is, the address where the target component is moved or loaded into memory. Initialization functions include GOT and PLT initialization.

[0067] In one embodiment, initializing the memory address of the target code by calling the initialization function includes: calling the GOT and PLT to correct the relative memory address of the target code to the absolute memory address that the program can execute. The GOT (Global Offset Table) stores the address information of all external symbols. The PLT (Procedure Linkage Table) includes the process code.

[0068] In one embodiment, loading the target component into the memory of the corresponding partition based on the target component configuration information to perform registration and operation includes: loading the target component into the memory of the partition corresponding to the target partition identifier based on the target component configuration information to perform registration and operation.

[0069] In one embodiment, after the target component is loaded into the memory of the corresponding partition, it is also necessary to register the target component. The registration steps of the target component include: reading the target component configuration information through a system call interface; obtaining the component information of the target component from the target component configuration information, the component information including the entry address, partition identifier, and rate; and registering the entry address of the relocated target component to the corresponding partition and rate group based on the entry address, partition identifier, and rate.

[0070] The entry address refers to the starting address of the target component, that is, the address of the first line of code in the target code. Rate refers to the component's execution speed. The registration order of components in the rate group indicates the order in which components are called and executed; that is, if the target component is registered first in the rate group, it will run first when called.

[0071] In one embodiment, registering the entry address of the relocated target component to the corresponding partition and rate group based on the entry address, partition identifier, and rate includes: registering the entry address of the relocated target component to the partition and rate group corresponding to the target partition identifier based on the entry address, partition identifier, and rate.

[0072] In one embodiment, the method further includes: reading the subscription and publication message configuration information of the target component through the component runtime platform; and transmitting the subscription and publication message configuration information to the target component.

[0073] In one embodiment, after the registration of the target component is completed, the method further includes a component initialization process for the target component.

[0074] The requirements for component initialization are as follows:

[0075] (1) Select the system configuration table according to the platform identifier and confirm the functions of the components required by the current device (e.g., an aircraft) in the current state;

[0076] (2) Provides functions for establishing a partitioned basic operating environment, including CPU-related register initialization, stack space clearing, C language execution stack establishment, BSS segment space clearing, and stack protection settings;

[0077] (3) Provide a function to check the correctness of component configuration information of application software;

[0078] (4) Provide initialization functionality for the periodic scheduling control block management structure of application software components;

[0079] (5) Provide initialization functionality for the component's aperiodic scheduling control block management structure;

[0080] (6) Provides initialization functionality for the component's message communication module management structure;

[0081] (7) Provides the function of establishing the component runtime environment, mainly including clearing the component BSS segment and executing the component initialization task.

[0082] In one embodiment, such as Figure 5The diagram illustrates a process of calling the distributed loading component configuration parameter table. As shown, the process begins with loading the partition operation processor. After loading, once the target component is identified, it is loaded via the partition operation processor. This primarily involves reading the target component configuration information from the distributed loading component configuration parameter table through the component runtime platform, then obtaining the target component's fixed address and runtime address from the configuration information. The fixed program of the target component is read based on the fixed address, and the segment information of the fixed program is parsed to obtain the corresponding target code. The target code is moved to the memory corresponding to the runtime address, achieving component image relocation. An initialization function is then called to initialize the memory address of the target code. Next, the component runtime platform is initialized. Then, the target component is registered and initialized, including reading the target component configuration information through a system call interface; obtaining the target component's component information from the configuration information, including the entry address, partition identifier, and rate; and registering the relocated target component's entry address to the corresponding partition and rate group based on the entry address, partition identifier, and rate. Furthermore, the component runtime platform reads the subscription-publish message configuration information and ICD message configuration information of the target component, and transmits the subscription-publish message configuration information to the target component.

[0083] In other words, the invocation of the distributed loading component configuration parameter table mainly includes: loading the partition operation processor; reading the target component configuration information corresponding to the target component from the distributed loading component configuration parameter table through the component runtime platform, thereby realizing the component image migration of the target component; initialization of the component runtime platform; reading the target component configuration information through the system call interface; obtaining the component information of the target component from the target component configuration information, and performing the registration and initialization of the target component; and reading the target component's subscription and publication message configuration information and ICD message configuration information.

[0084] In the aforementioned application software component method, multiple application software programs are divided into components with different functions through a partitioning operation processor. These components then run on the corresponding partition's component runtime platform. When loading a target component of an application software to be loaded, the component runtime platform determines the target component configuration information from a distributed loading component configuration parameter table based on the application software's platform identifier, the target component identifier, and the target partition identifier. Based on this configuration information, the target component is loaded into the memory of the corresponding partition for registration and execution. This method allows for the direct loading of components from application software on different platforms to enable application execution. A single application software component method can adapt to multiple platforms, improving application software development efficiency and saving development costs. The application software component method provided in this solution is based on a component runtime framework structure. Developing application software on this framework allows multiple platforms and models to share the same application image, reducing the workload of developers and testers and improving application software development efficiency.

[0085] It should be understood that, although Figure 4-5 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 4-5 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0086] In one embodiment, such as Figure 6 As shown, an application software component device 600 is provided, including: a target component determination module 602, a platform identifier acquisition module 604, a target component configuration information acquisition module 606, and a target component running module 608; wherein:

[0087] The target component determination module 602 is used to determine the components of the application software to be loaded as target components; the target components include target component identifiers and target partition identifiers.

[0088] The platform identifier acquisition module 604 is used to acquire the platform identifier of the application software to be loaded.

[0089] The target component configuration information acquisition module 606 is used to acquire the target component configuration information of the target component from the distributed loading component configuration parameter table based on the platform identifier, the target component identifier, and the target partition identifier.

[0090] The target component running module 608 is used to load the target component into the memory of the corresponding partition based on the target component configuration information and perform registration and running.

[0091] In one embodiment, the apparatus further includes a component partitioning module, used to partition multiple application software according to the functions of the application software to obtain multiple components with different functions; and to run the multiple components on the component runtime platform of the corresponding partition.

[0092] In one embodiment, the distributed loading component configuration parameter table includes a component solidification information table, a component configuration information offset address table, and component configuration information corresponding to multiple platforms; the component solidification information table includes the solidification address of each component configuration information; the component configuration information offset address table includes the offset address of each component configuration information; the component configuration information includes the configuration data of each component in each partition.

[0093] In one embodiment, the target component execution module 608 is further configured to obtain the firmware address and execution address of the target component from the target component configuration information; read the firmware program of the target component according to the firmware address, and parse the segment information of the firmware program to obtain the corresponding target code; move the target code to the memory corresponding to the execution address; and call the initialization function to initialize the memory address of the target code.

[0094] In one embodiment, the target component running module 608 is further configured to read the target component configuration information through a system call interface; obtain the component information of the target component from the target component configuration information, the component information including an entry address, a partition identifier, and a rate; and register the entry address of the relocated target component to the corresponding partition and rate group based on the entry address, the partition identifier, and the rate.

[0095] In one embodiment, the target component runtime module 608 is further configured to read the subscription and publication message configuration information of the target component through the component runtime platform; and transmit the subscription and publication message configuration information to the target component.

[0096] In one embodiment, the target component running module 608 is further configured to, after the registration of the target component is completed, include a component initialization process for the target component.

[0097] In the aforementioned application software component device, multiple application software programs are divided into components with different functions by a partitioning operation processor. These components then run on the component runtime platform of their respective partitions. When loading a target component of an application software to be loaded, the component runtime platform determines the target component configuration information from a distributed loading component configuration parameter table based on the platform identifier, target component identifier, and target partition identifier of the application software to be loaded. Based on this configuration information, the target component is loaded into the memory of the corresponding partition for registration and execution. This achieves a method for directly loading components of application software for different platforms to run the application. A single application software component method can adapt to multiple different platforms, improving application software development efficiency and saving development costs. The application software component method provided in this solution is based on a component runtime framework structure. Developing application software on this framework allows multiple platforms and models to share the same application image, reducing the workload of developers and testers and improving application software development efficiency.

[0098] Specific limitations regarding the application software component device can be found in the limitations of the application software component method above, and will not be repeated here. Each module in the aforementioned application software component device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0099] In one embodiment, a computer device is provided, which may be a partitioning processor, and its internal structure diagram may be as follows: Figure 7 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores application software component data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements an application software component method.

[0100] Those skilled in the art will understand that Figure 7The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0101] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps: determining a component of application software to be loaded as a target component; the target component includes a target component identifier and a target partition identifier; obtaining a platform identifier of the application software to be loaded; obtaining target component configuration information of the target component from a distributed loading component configuration parameter table based on the platform identifier, the target component identifier, and the target partition identifier; and loading the target component into the memory of the corresponding partition based on the target component configuration information to perform registration and operation.

[0102] In one embodiment, when the processor executes the computer program, it further performs the following steps: dividing multiple application software according to the functions of the application software to obtain multiple components with different functions; and running the multiple components on the component running platform of the corresponding partition.

[0103] In one embodiment, when the processor executes the computer program, it further implements the following steps: the component firmware information table includes the firmware address of each component configuration information; the component configuration information offset address table includes the offset address of each component configuration information; the component configuration information includes the configuration data of each component in each partition.

[0104] In one embodiment, when the processor executes the computer program, it further performs the following steps: obtaining the firmware address and runtime address of the target component from the target component configuration information; reading the firmware program of the target component according to the firmware address, and parsing the segment information of the firmware program to obtain the corresponding target code; moving the target code to the memory corresponding to the runtime address; and calling an initialization function to initialize the memory address of the target code.

[0105] In one embodiment, when the processor executes the computer program, it further performs the following steps: reading the target component configuration information through a system call interface; obtaining the component information of the target component from the target component configuration information, the component information including an entry address, a partition identifier, and a rate; and registering the entry address of the relocated target component to the corresponding partition and rate group based on the entry address, the partition identifier, and the rate.

[0106] In one embodiment, when the processor executes the computer program, it further performs the following steps: reading the subscription and publication message configuration information of the target component through the component runtime platform; and transmitting the subscription and publication message configuration information to the target component.

[0107] In one embodiment, when the processor executes the computer program, it further implements the following steps: after the registration of the target component is completed, the method further includes a component initialization process for the target component.

[0108] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it performs the following steps: determining a component of an application software to be loaded as a target component; the target component includes a target component identifier and a target partition identifier; obtaining a platform identifier of the application software to be loaded; obtaining target component configuration information of the target component from a distributed loading component configuration parameter table based on the platform identifier, the target component identifier, and the target partition identifier; and loading the target component into the memory of the corresponding partition based on the target component configuration information to perform registration and operation.

[0109] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: dividing multiple application software according to the functions of the application software to obtain multiple components with different functions; running the multiple components on the component running platform of the corresponding partition.

[0110] In one embodiment, when the computer program is executed by a processor, it further implements the following steps: the component firmware information table includes the firmware address of each component configuration information; the component configuration information offset address table includes the offset address of each component configuration information; the component configuration information includes the configuration data of each component in each partition.

[0111] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining the firmware address and runtime address of the target component from the target component configuration information; reading the firmware program of the target component according to the firmware address, and parsing the segment information of the firmware program to obtain the corresponding target code; moving the target code to the memory corresponding to the runtime address; and calling the initialization function to initialize the memory address of the target code.

[0112] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: reading the target component configuration information through a system call interface; obtaining the component information of the target component from the target component configuration information, the component information including an entry address, a partition identifier, and a rate; and registering the entry address of the relocated target component to the corresponding partition and rate group based on the entry address, the partition identifier, and the rate.

[0113] In one embodiment, when the computer program is executed by a processor, it further performs the following steps: reading the subscription and publication message configuration information of the target component through the component runtime platform; and transmitting the subscription and publication message configuration information to the target component.

[0114] In one embodiment, when the computer program is executed by a processor, it further implements the following steps: after the registration of the target component is completed, the method further includes a component initialization process for the target component.

[0115] The aforementioned application software components, computer devices, and storage media, use a partitioning processor to divide multiple application software programs according to their functions, resulting in multiple components with different functions. These components then run on their respective partition's component runtime platform. When loading a target component of an application software to be loaded, the component runtime platform determines the target component configuration information from a distributed loading component configuration parameter table based on the application software's platform identifier, the target component identifier, and the target partition identifier. Based on this configuration information, the target component is loaded into the memory of the corresponding partition for registration and execution. This achieves a method for directly loading components of application software for different platforms to run the application. A single application software component method can adapt to multiple different platforms, improving application software development efficiency and saving development costs. The application software component method provided in this solution is based on a component runtime framework structure. Developing application software on this framework allows multiple platforms and models to share the same application image, reducing the workload of developers and testers and improving application software development efficiency.

[0116] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0117] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0118] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. An application software component method, the method being applied in a partitioning operation processor, characterized in that, The method includes: The components of the application software to be loaded are identified as target components; the target components include a target component identifier and a target partition identifier; Obtain the platform identifier of the application software to be loaded; Based on the platform identifier, the target component identifier, and the target partition identifier, the target component configuration information of the target component is obtained from the distributed loading component configuration parameter table; wherein, the distributed loading component configuration parameter table includes a component solidification information table, a component configuration information offset address table, and component configuration information corresponding to multiple platforms; the component solidification information table includes the solidification address of each component configuration information; the component configuration information offset address table includes the offset address of each component configuration information; the component configuration information includes the configuration data of each component in each partition; Based on the target component configuration information, the target component is loaded into the memory of the corresponding partition for registration and execution; The registration step of the target component includes: reading the target component configuration information through a system call interface; obtaining the component information of the target component from the target component configuration information, the component information including an entry address, a partition identifier, and a rate; and registering the entry address of the relocated target component to the corresponding partition and rate group based on the entry address, partition identifier, and rate. Wherein, the fixed address refers to the address of the flash non-volatile memory, the entry address refers to the starting address of the target component, and the rate refers to the operating rate of the component.

2. The method according to claim 1, characterized in that, The method further includes: Multiple application software programs are divided according to their functions, resulting in multiple components with different functions. The components are run on the component runtime platform of the corresponding partition.

3. The method according to claim 1, characterized in that, The step of loading the target component into the memory of the corresponding partition based on the target component configuration information includes: Obtain the fixed address and runtime address of the target component from the target component configuration information; The firmware program of the target component is read according to the firmware address, and the segment information of the firmware program is parsed to obtain the corresponding target code; Move the target code to the memory corresponding to the execution address; The initialization function is called to initialize the memory address of the target code.

4. The method according to claim 1, characterized in that, The method further includes: The platform runs the component to read the target component's subscription and publish message configuration information. The subscription and publish message configuration information is transmitted to the target component.

5. The method according to any one of claims 1 to 4, characterized in that, After the target component is registered, the method further includes a component initialization process for the target component.

6. An application software component device, characterized in that, The device includes: The target component determination module is used to determine the components of the application software to be loaded as target components; the target components include a target component identifier and a target partition identifier; The platform identifier acquisition module is used to acquire the platform identifier of the application software to be loaded. The target component configuration information acquisition module is used to acquire target component configuration information of the target component from the distributed loading component configuration parameter table based on the platform identifier, the target component identifier, and the target partition identifier; wherein, the distributed loading component configuration parameter table includes a component solidification information table, a component configuration information offset address table, and component configuration information corresponding to multiple platforms; the component solidification information table includes the solidification address of each component configuration information; the component configuration information offset address table includes the offset address of each component configuration information; the component configuration information includes the configuration data of each component in each partition; A target component execution module is used to load the target component into the memory of the corresponding partition based on the target component configuration information and perform registration and execution. The registration step of the target component includes: reading the target component configuration information through a system call interface; obtaining the component information of the target component from the target component configuration information, the component information including an entry address, partition identifier, and speed; and registering the entry address of the relocated target component to the corresponding partition and speed group based on the entry address, partition identifier, and speed. Wherein, the fixed address refers to the address of the flash non-volatile memory, the entry address refers to the starting address of the target component, and the rate refers to the operating rate of the component.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images