Software platform construction methods, devices, equipment, and storage media

Abstract

This disclosure relates to a method, apparatus, device, and storage medium for building a software platform. The method includes: displaying a first page on a local server, the first page including at least one element for identifying a software platform file; obtaining a target element selected on the first page, the target element being selected from the at least one element; upon receiving a platform building instruction, obtaining a target software platform file corresponding to the target element from a storage server; and building the software platform based on the target software platform file. According to embodiments of this disclosure, users do not need to understand the underlying logic of the software platform, nor do they need extensive coding experience. Users can build the software platform simply by selecting elements on the first page, simplifying the software platform building process and shortening the software platform building time.

Description

Technical Field

[0001] This disclosure relates to the field of software platform development technology, and in particular to methods, apparatus, devices and storage media for building software platforms. Background Technology

[0002] The automotive software platform is a container that includes operating system images, compilation and linking toolchains, vendor-provided binary artifacts, middleware software module binary artifacts, autonomous driving algorithm module binary artifacts, etc., for R&D engineers to compile and build software installation packages for vehicles.

[0003] However, due to the abundance of optional content on automotive software platforms, the requirements for these platforms vary significantly among R&D engineers due to differences in car manufacturers, vehicle models, domain control platform architectures, and the countries / regions where the cars are sold. Consequently, building such platforms requires engineers with advanced programming skills to write scripts for each testing requirement. However, because these requirements are rarely identical, the scripts are difficult to reuse and maintain, making the process extremely challenging, time-consuming, and tedious. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this disclosure provides a method, apparatus, device and storage medium for building a software platform.

[0005] According to a first aspect of the present disclosure, a method for building a software platform is provided, comprising:

[0006] Display a first page on a local server. The first page includes at least one element that identifies a software platform file.

[0007] Obtain the target element selected on the first page, wherein the target element is obtained by filtering from the at least one element;

[0008] Upon receiving a platform setup instruction, the system retrieves the target software platform file corresponding to the target element from the storage server and builds the software platform based on the target software platform file.

[0009] As an optional embodiment, obtaining the target element selected on the first page includes:

[0010] Upon receiving a selection instruction for the first element, the display state of the first element is updated from the pending state to the selected state, and the first element is determined as the target element.

[0011] As an optional embodiment, the first page includes at least two levels, each of the at least two levels includes at least one element, each element in the first level is associated with at least one element in the next level of the first level, the first level is any level other than the last level of the at least two levels, the second element is the element in the next level of the first level that is associated with the first element, and the third element is the target element in the second element;

[0012] After updating the display state of the first element from a pending state to a selected state, the method further includes:

[0013] When the first element is at the first level, a second element that is associated with the first element is displayed on the first page;

[0014] Upon receiving a selection instruction for a third element, the third element is determined as the target element, and the second element includes the third element.

[0015] As an optional embodiment, the target software platform file includes a target container image, a target hardware module, and a target software module, and the storage server includes an image server and a software server;

[0016] The step of retrieving the target software platform file corresponding to the target element from the storage server includes:

[0017] Obtain the target container image from the image server;

[0018] Obtain a first software module that is bound to the target hardware module from the software server, and install the first software module into the target container image;

[0019] The target software module is obtained from the software server and installed on the local server to build the software platform.

[0020] As an optional embodiment, the step of obtaining the target software module from the software server and installing the target software module into the local server includes:

[0021] The target software module is installed from the software server into the target container image.

[0022] As an optional embodiment, the step of obtaining the target software module from the software server and installing the target software module into the local server includes:

[0023] The target software module is installed from the software server to the local server, and the target software module in the local server is mapped to the target container image.

[0024] According to a second aspect of the present disclosure, a software platform construction apparatus is provided, comprising:

[0025] A display module is used to display a first page on a local server, the first page including at least one element, the element being used to identify a software platform file;

[0026] The acquisition module is used to acquire a target element selected on the first page, wherein the target element is obtained by filtering from the at least one element;

[0027] The building module is used to obtain the target software platform file corresponding to the target element from the storage server when a platform building instruction is received, and to build the software platform based on the target software platform file.

[0028] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor; a memory for storing executable instructions of the processor; the processor being configured to read the executable instructions from the memory and execute the instructions to implement the software platform construction method provided by the software platform construction aspect of the present disclosure.

[0029] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of the software platform construction method provided by the software platform construction aspect of the present disclosure.

[0030] The technical solutions provided by the embodiments of this disclosure can include the following beneficial effects: A first page is set up, where each element identifies a file in the software platform construction. When a user selects a target element on the first page and issues a platform construction command, the local server automatically retrieves the target software platform file corresponding to the target element from the storage server and automatically generates a software platform. In the prior art, users need to perform complex program editing when building a software platform. Compared with the prior art, this application simplifies the software platform construction process through a single page. Users developing the software platform only need to log in to the aforementioned page and select the desired elements to build the desired software platform. Users do not need to understand the underlying logic of the software platform or have extensive coding experience, thus simplifying the software platform construction process and shortening the construction time.

[0031] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0032] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0033] Figure 1 This is a flowchart illustrating a method for building a software platform according to an exemplary embodiment.

[0034] Figure 2 This is a flowchart illustrating a method for building a software platform according to another exemplary embodiment.

[0035] Figure 3 This is a flowchart illustrating a method for building a software platform according to yet another exemplary embodiment.

[0036] Figure 4 It is an element hierarchy display interface.

[0037] Figure 5 This is a flowchart illustrating a method for building a software platform according to another exemplary embodiment.

[0038] Figure 6 This is a block diagram illustrating a software platform building apparatus according to an exemplary embodiment.

[0039] Figure 7 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0040] The exemplary embodiments will now be described in detail with reference to the accompanying drawings.

[0041] It should be noted that the relevant embodiments and accompanying drawings are only for describing and illustrating exemplary embodiments provided by this disclosure, and not all embodiments of this disclosure, nor should this disclosure be understood to be limited to the relevant exemplary embodiments.

[0042] It should be noted that the terms "first," "second," etc., used in this disclosure are only used to distinguish different steps, devices, or modules. These terms do not represent any specific technical meaning, nor do they indicate any order or interdependence between them.

[0043] It should be noted that the terms “a,” “a plurality of,” and “at least one” used in this disclosure are illustrative rather than restrictive. Unless otherwise expressly indicated in the context, they should be understood as “one or more.”

[0044] It should be noted that the term "and / or" used in this disclosure is used to describe the relationship between related objects, and generally indicates that there are at least three relationships. For example, A and / or B can at least indicate: the existence of A alone, the existence of both A and B, and the existence of B alone.

[0045] It should be noted that the various steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Unless otherwise specified, the scope of this disclosure is not limited by the order in which the steps are described in the relevant embodiments.

[0046] It should be noted that all actions involving the acquisition of signals, information, or data in this disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the location is situated, and with authorization from the owner of the relevant device.

[0047] Exemplary methods

[0048] Figure 1 This is a flowchart illustrating a method for building a software platform according to an exemplary embodiment, such as... Figure 1 As shown, the method for building a software platform includes the following steps:

[0049] In step S110, a first page is displayed on a local server. The first page includes at least one element used to identify a software platform file.

[0050] In this embodiment, the first page can be a webpage displayed on a local server interface or an application page. Users can operate on the first page to select the files included in the software platform they want to build, and the corresponding software platform will be generated based on the user's selection. These software platforms may include at least: container images, compilers, linkers, and software modules.

[0051] The first page includes at least one element, which can be an icon or symbol on the page. Each element identifies a software platform file used to build the software platform. For example, elements identifying different types of software platform files use different icons or symbols. For instance, the icon for an element identifying a container image is a circle, the icon for an element identifying a domain controller is a rectangle, and the icon for an element identifying a software module is a trapezoid.

[0052] In addition, each element has two different states: selected and unselected. The state of each element can be switched based on the user's actions on the first page.

[0053] If an element is selected, it means that the software platform file identified by that element will be retrieved when building the target platform; if an element is pending, it means that the software platform file identified by that element will not be retrieved when building the target platform.

[0054] In step S120, the target element selected on the first page is obtained, wherein the target element is obtained by filtering from the at least one element.

[0055] In this embodiment, the target element is the software platform file it identifies, which is selected by the user and used to build the software platform. The user can select some or all of the elements as target elements from at least one element on the first page through voice interaction or by touching the display screen on the local server to display the first page.

[0056] Specifically, since a software platform only needs one container image and one domain controller, but can have multiple software modules, the target element contains only one element that identifies the container image and one element that identifies the domain controller, but can contain multiple elements that identify the software modules.

[0057] In step S130, upon receiving a platform building instruction, the target software platform file corresponding to the target element is obtained from the storage server, and the software platform is built based on the target software platform file.

[0058] In this embodiment, on the first page, each element is bound to a pull command. The pull command records the address and name of the software platform file identified by the element. When the pull command is executed, the software platform file identified by the element will be pulled from the storage server. The storage server is a server that stores the target software platform file.

[0059] Upon receiving the platform setup instruction, execute the pull instructions bound to all target elements on the first page. Pull the software platform files identified by all target elements to the local server for use in setting up the target platform on the local server.

[0060] In one embodiment, upon receiving a platform setup instruction, the pull instructions bound to all target elements are obtained. These pull instructions are then input into a pre-set code generator to generate a customized platform setup script. Running this platform setup script will pull the software platform files identified by all target elements to the local server.

[0061] For example, if the target element identifies a software platform file including a container (Docker) image, a domain controller, and software modules, then the above platform setup script would include: pulling the Docker image from the Docker image storage server; pulling the required software modules associated with the domain controller from the artifact repository; and pulling the user-selected optional software modules from the artifact repository, with each software module specified to its version number. Each software module would then be either placed inside the Docker image or on the host machine. Finally, the software platform would be set up by mounting the host machine directory into the container.

[0062] This disclosure establishes a primary page where each element identifies a file in the software platform construction process. When a user selects a target element on this page and issues a platform construction command, the local server automatically retrieves the target software platform file corresponding to the target element from the storage server and automatically generates a software platform. In contrast, existing technologies require users to perform complex programming during software platform construction. Compared to existing technologies, this application simplifies the software platform construction process with a single page. Users developing the software platform only need to log in to the aforementioned page and select the desired elements to build the desired software platform. Users do not need to understand the underlying logic of the software platform or have extensive coding experience, thus simplifying the construction process and shortening the construction time.

[0063] As an optional embodiment, such as Figure 2 As shown, the above-mentioned S120 may further include:

[0064] In step S210, upon receiving a selection instruction for the first element, the display state of the first element is updated from a pending state to a selected state, and the first element is determined as the target element.

[0065] In this embodiment, each element has two different states: selected and unselected. The state of each element can be switched based on the user's actions on the first page. The first page can display not only the content of the elements but also their current state.

[0066] For example, each element has a corresponding checkbox on the first page. When the checkbox for an element is checked, it means that the element is selected; otherwise, the element is in a pending state. Another example is that the color of the icon corresponding to an element varies depending on its state. When the icon for an element is red, it means that the element is selected; when the icon for an element is green, it means that the element is in a pending state.

[0067] When the first page is opened or refreshed, all elements on the first page are in a pending state. So whenever a selection instruction is received for an element, the display state of that element is updated from the pending state to the selected state, and at this time, that element is the target element.

[0068] The selection command can be sent by the user speaking the name of the first element to the local server, or by the user clicking the icon corresponding to the first element on the first page.

[0069] In this embodiment, by receiving user instructions, the display state of elements on the display page can be changed, which can accurately respond to the user's selection instructions and clearly display the state of each element.

[0070] As an optional embodiment, the first page includes at least two levels, each of the at least two levels includes at least one element, each element in the first level is associated with at least one element in the next level of the first level, the first level is any level other than the last level of the at least two levels, the second element is the element in the next level of the first level that is associated with the first element, and the third element is the target element in the second element;

[0071] like Figure 3 As shown, after S210 above, it also includes:

[0072] In step S310, when the first element is at the first level, a second element that is associated with the first element is displayed on the first page, wherein the second element belongs to the next level below the first level;

[0073] In this embodiment, the elements on the first page are divided into multiple levels, with elements at the same level identifying the same type of software platform file. Because during the software platform setup process, the container image needs to be determined first before the hardware can be further determined, and finally, software modules adapted to the hardware are selected.

[0074] Once the container image is determined, only hardware associated with that container image can be selected; similarly, once the hardware is determined, only software modules associated with that hardware can be selected. Compatibility can be determined by the attributes of the software platform files, or it can be configured in advance by the user according to their own needs.

[0075] Based on the selection rules described above, not all elements can be displayed on the first page simultaneously; instead, elements can be displayed hierarchically. After the user opens the first page, the first level is displayed first. Once the user selects the first element in the first level, at least one second element related to the first element is displayed, allowing the user to make further selections from the second elements. This method facilitates hierarchical selection for the user.

[0076] In step S320, upon receiving a selection instruction for a third element, the third element is determined as the target element, and the second element includes the third element.

[0077] In this embodiment, once the second element is displayed on the first page, it means that the user can make a selection at the next level below the first level. The user can select the desired third element from the second elements at that level. After selection, other elements at the next level that are related to the third element will be displayed on the first page, and this process continues until the user has selected elements at all levels on the first page.

[0078] In one embodiment, the first page includes three levels, namely level A, level B, and level C. Each element in level A identifies a type of container image, each element in level B identifies a type of hardware module, and each element in level C identifies a software module.

[0079] like Figure 4As shown, level A offers four selectable images: x86_64-docker, x86-docker, aarch64-docker, and xxx-docker. Level A initially displays elements corresponding to these four images. Users can select the x86_64-docker image in level A, and the first page will then display elements from level B, which are associated with the x86_64-docker image. The elements in level B correspond to the following five hardware modules: Orin-based domain controller, S32G-based domain controller, J5-based domain controller, x86_64 industrial PC, and xxx-based domain controller. If a user selects an Orin-based domain controller in level B, the first page will then display elements from level C, which are associated with the Orin-based domain controller, namely: localization module, perception module, planning module, prediction module, fast-rtps module, CyberRT module, ProtoBuf module, and OpenCV module. Users can further select four modules—location, perception, ProtoBuf, and OpenCV—in level C based on their needs. At this point, by selecting elements across three levels on the first page, users have completed the setup of a software platform.

[0080] The step-by-step selection method in this embodiment helps to filter out some irrelevant files after each level of selection, making it convenient for users to filter.

[0081] As an optional embodiment, the target software platform file includes a target container image, a target hardware module, and a target software module, and the storage server includes an image server and a software server;

[0082] like Figure 5 As shown, obtaining the target software platform file corresponding to the target element from the storage server includes:

[0083] In step S510, the target container image is obtained from the image server;

[0084] In this embodiment, once the user identifies target elements on the first page and builds a software platform based on these target elements, a customized script will be generated. Specifically, each target element corresponds to a keyword, which can be the name or address of the software platform file identified by the target element. These keywords can be input into a pre-compiled code generator to automatically generate the aforementioned script.

[0085] Custom scripts are used to retrieve the target software platform file corresponding to the target element from the storage server.

[0086] The storage server includes an image server, which stores various types and versions of container images. When the script runs, it can pull the target container image selected by the user from the image server to the local server.

[0087] In step S520, a first software module that is bound to the target hardware module is obtained from the software server, and the first software module is installed into the target container image;

[0088] In this embodiment, each hardware module is bound to certain software modules, and the operation of the hardware module requires the support of these bound software modules. Therefore, after selecting the target hardware module, the customized script is also used to pull the first software module from the software server to the local server and install the first software module into the target container image.

[0089] In step S530, the target software module is obtained from the software server and installed on the local server to build the software platform.

[0090] In this embodiment, the target software module is a software module that is not bound to the target hardware module and is identified by the target element. After the target software module is selected, the customized script is also used to pull the target software module from the software server to the local server and install the target software module into the target container image.

[0091] In this embodiment, after the user selects an element on the page, the system can automatically retrieve a first software module that is bound to the target hardware module from the software server based on the user's selection, and retrieve the target software module from the software server. This can automatically and quickly complete the construction of the software platform, reducing the technical threshold for users to complete the construction of the software platform.

[0092] As an optional embodiment, obtaining the target software module from the software server includes:

[0093] The target software module is installed from the software server into the target container image.

[0094] In this embodiment, the software platform is composed of a container image selected by the user, a target platform, and software modules. The container image serves as a carrier, and the software modules need to function within the container image. Therefore, the target software modules can be directly pulled and installed into the target container image so that they can be called by the user at any time.

[0095] As an optional embodiment, obtaining the target software module from the software server includes:

[0096] The target software module is installed from the software server to the local server, and the target software module in the local server is mapped to the target container image.

[0097] In this embodiment, the target software modules in the software server can also be pulled to the local server and not installed in the target image container. Instead, the target software modules in the local server are mapped into the target container image. In this way, users can call these target software modules at any time in the software platform.

[0098] Exemplary device

[0099] Figure 6 This is a block diagram of a software platform construction apparatus 600 according to an exemplary embodiment. (Refer to...) Figure 6 The device 600 includes a display module 610, an acquisition module 620, and a construction module 630.

[0100] The display module 610 is used to display a first page on a local server, the first page including at least one element, the element being used to identify a software platform file;

[0101] The acquisition module 620 is used to acquire a target element selected on the first page, wherein the target element is obtained by filtering from the at least one element;

[0102] The building module 630 is used to obtain the target software platform file corresponding to the target element from the storage server when a platform building instruction is received, and to build the software platform based on the target software platform file.

[0103] As an optional embodiment, the acquisition module 620 is further configured to:

[0104] Upon receiving a selection instruction for the first element, the display state of the first element is updated from the pending state to the selected state, and the first element is determined as the target element.

[0105] As an optional embodiment, the first page includes at least two levels, each of the at least two levels including at least one element, each element in the first level being associated with at least one element in the next level below the first level, the first level being any level other than the last of the at least two levels, the second element being an element in the next level below the first level that is associated with the first element, the third element being a target element in the second element, and the fourth module 640 is further configured to:

[0106] When the first element is at the first level, a second element that is associated with the first element is displayed on the first page;

[0107] Upon receiving a selection instruction for a third element, the third element is determined as the target element, and the second element includes the third element.

[0108] As an optional embodiment, the target software platform file includes a target container image, a target hardware module, and a target software module; the storage server includes an image server and a software server; and the aforementioned setup module 630 is further used for:

[0109] Obtain the target container image from the image server;

[0110] Obtain a first software module that is bound to the target hardware module from the software server, and install the first software module into the target container image;

[0111] The target software module is obtained from the software server and installed on the local server to build the software platform.

[0112] As an optional embodiment, the above-described assembly module 630 is also used for:

[0113] The target software module is installed from the software server into the target container image.

[0114] As an optional embodiment, the above-described assembly module 630 is also used for:

[0115] The target software module is installed from the software server to the local server, and the target software module in the local server is mapped to the target container image.

[0116] The software platform building apparatus provided in this embodiment of the invention can implement the various steps in the above method embodiments, and will not be repeated here to avoid repetition.

[0117] Exemplary electronic devices

[0118] Figure 7 This is a block diagram illustrating an electronic device 700 according to an exemplary embodiment. The electronic device 700 may be a vehicle controller, an in-vehicle terminal, an in-vehicle computer, or other types of electronic devices.

[0119] Reference Figure 7The electronic device 700 may include at least one processor 710 and a memory 720. The processor 710 can execute instructions stored in the memory 720. The processor 710 is communicatively connected to the memory 720 via a data bus. In addition to the memory 720, the processor 710 can also be communicatively connected to an input device 730, an output device 740, and a communication device 750 via the data bus.

[0120] The processor 710 can be any conventional processor, such as a commercially available CPU. The processor may also include graphics processing units (GPUs), field-programmable gate arrays (FPGAs), systems on chips (SoCs), application-specific integrated circuits (ASICs), or combinations thereof.

[0121] The memory 720 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0122] In this embodiment of the present disclosure, the memory 720 stores executable instructions, and the processor 710 can read the executable instructions from the memory 720 and execute the instructions to implement all or part of the steps of the software platform construction method described in any of the exemplary embodiments above.

[0123] Exemplary computer-readable storage media

[0124] In addition to the methods and apparatus described above, exemplary embodiments of this disclosure may also be a computer program product or a computer-readable storage medium storing the computer program product. The computer product includes computer program instructions that can be executed by a processor to perform all or part of the steps described in any of the methods in the exemplary embodiments described above.

[0125] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this disclosure. These programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages, and scripting languages ​​(e.g., Python). The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0126] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media include: static random access memory (SRAM) having one or more electrically connected wires; electrically erasable programmable read-only memory (EEPROM); erasable programmable read-only memory (EPROM); programmable read-only memory (PROM); read-only memory (ROM); magnetic storage; flash memory; magnetic disk or optical disk; or any suitable combination thereof.

[0127] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of this disclosure. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0128] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for building a software platform, characterized in that, The method comprises: displaying a first page on a local server, the first page comprising at least one element, the element being used to identify a software platform file; obtaining a target element selected on the first page, the target element being selected from the at least one element; in a case where a platform building instruction is received, obtaining a pulling instruction bound to all target elements, inputting the pulling instruction into a pre-set code generator, generating a customized platform building script, and performing the following operations based on the customized platform building script: obtaining a target container image from a mirror server; obtaining a first software module having a binding relationship with a target hardware module from a software server, and installing the first software module into the target container image; obtaining a target software module from the software server, and installing the target software module into the local server to build a software platform; wherein the first page comprises three levels, in order, a first level, a second level and a third level, each element in the first level identifies a type of container image, each element in the second level identifies a type of hardware module, and each element in the third level identifies a software module, the second level is a next level of the first level, the third level is a next level of the second level, the target container image is a container image corresponding to an element selected in the first level, the target hardware module is a hardware module under the target container image, and the target software module is a software module under the target hardware module.

2. The method of claim 1, wherein the software platform is built by, The obtaining of the target element selected on the first page comprises: in a case where a selection instruction for a first element is received, updating a display state of the first element from a standby state to a selected state, and determining the first element as the target element.

3. The method of claim 2, wherein the software platform is built by: The first page comprises at least two levels, each level of the at least two levels comprising at least one element, each element in the first level having an association relationship with at least one element in a next level of the first level, the first level being any level except the last level of the at least two levels, a second element being an element in the next level of the first level having an association relationship with the first element, and a third element being a target element in the second element. After the display state of the first element is updated from the standby state to the selected state, the method further comprises: in a case where the first element is in the first level, displaying a second element having an association relationship with the first element on the first page; in a case where a selection instruction for the third element is received, determining the third element as the target element.

4. The method of claim 1, wherein the software platform is built by: The obtaining of the target software module from the software server and the installation of the target software module into the local server to build a software platform comprises: installing the target software module into the target container image from the software server.

5. The method of claim 1, wherein the software platform is built on a platform of a mobile device. The target software module is obtained from the software server, and the target software module is installed into the local server to build the software platform, including: The target software module is installed from the software server into the local server, and the target software module in the local server is mapped into the target container image.

6. A software platform building apparatus, characterized by comprising: Including: The display module is configured to display a first page on the local server, the first page including at least one element, the element being used to identify a software platform file; The obtaining module is configured to obtain a target element selected on the first page, the target element being selected from the at least one element; The building module is configured to, in a case where a platform building instruction is received, obtain a pulling instruction bound with all target elements, input the pulling instruction into a pre-set code generator, generate a customized platform building script, and perform the following operations based on the customized platform building script: Obtain a target container image from an image server; Obtain a first software module having a binding relationship with a target hardware module from a software server, and install the first software module into the target container image; Obtain a target software module from the software server, and install the target software module into the local server to build the software platform; The first page includes three levels, in order, a first level, a second level, and a third level, each element in the first level identifies a type of container image, each element in the second level identifies a type of hardware module, and each element in the third level identifies a software module, the second level is a next level of the first level, the third level is a next level of the second level, the target container image is a container image identified by an element selected in the first level, the target hardware module is a hardware module under the target container image, and the target software module is a software module under the target hardware module.

7. The software platform building apparatus of claim 6, wherein, The obtaining module is further configured to, in a case where a selection instruction for a first element is received, update a display state of the first element from a to-be-selected state to a selected state, and determine the first element as the target element.

8. An electronic device, comprising: Including: A processor; A memory for storing executable instructions of the processor; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the building method of the software platform according to any one of claims 1-5.

9. A computer-readable storage medium having stored thereon computer program instructions, wherein, The program instructions are executed by the processor to implement the steps of the building method of the software platform according to any one of claims 1-5.

Images