Application installation methods, devices, computer equipment, media, and products

By unifying application configuration through a cloud platform and matching customized configuration files with the serial number of the target device, the problem of large workload and slow response speed in factory production testing in the artificial intelligence host installation method is solved, and efficient and secure application installation is achieved.

CN123114500APending Publication Date: 2026-11-17NEW H3C INTELLIGENCE TERMINAL CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611468766.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-20
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The current installation method of artificial intelligence hosts results in a large workload for factory production and testing, slow response speed, and inability to quickly adapt to changes in project requirements and software version updates.

Method used

By managing the application configurations of multiple target devices in a unified manner through a cloud platform, and matching customized application configuration files with the serial numbers of the target devices, differentiated application installation can be achieved, reducing the difficulty of deploying and maintaining large-scale terminal application clusters, and supporting both online and offline installation scenarios.

Benefits of technology

It improves application installation efficiency and response speed, reduces factory production testing workload, supports flexible business deployment needs, and ensures the security and accuracy of the installation process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114500A_ABST
    Figure CN123114500A_ABST
Patent Text Reader

Abstract

This invention relates to the field of artificial intelligence technology and discloses a method, apparatus, computer device, medium, and product for installing applications. The method for installing applications includes: obtaining an application configuration request from a target device; the target device being a device to which the application is to be installed; determining a target customized application configuration file from multiple preset customized application configuration files according to the application configuration request; the target customized application configuration file is used to instruct the target device to install the application. This invention pre-completes the unified storage and management of customized configuration files through a cloud platform, and determines the target customized application configuration file based on the application configuration request of the target device, so that the target device can install the application according to the target customized application configuration file, thereby improving the efficiency of application installation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of artificial intelligence technology, and more specifically to methods, apparatus, computer equipment, media, and products for installing applications. Background Technology

[0002] With the rapid application of artificial intelligence (AI) technology across various fields, an increasing number of projects require the deployment of AI hosts with local inference capabilities. AI hosts typically need to be pre-installed with different software environments, model files, inference engines, business applications, and auxiliary tools depending on the specific business scenario. Customers in different industries may have varying requirements for business applications, model versions, security policies, offline deployment requirements, installation paths, and service ports.

[0003] In related technologies, the installation method for artificial intelligence involves the project team providing the factory with a software list, model files, installation packages, and installation scripts before the AI ​​host leaves the factory. The factory then creates a dedicated system image based on the project requirements, or installs the required software on each device before it leaves the factory. However, this method requires the creation of a separate image or manual pre-installation for each project, resulting in a large workload for factory production and testing. When project requirements change or software versions are updated, the image needs to be recreated or the installation needs to be reworked, leading to a slow response time. Summary of the Invention

[0004] This invention provides an application installation method, apparatus, computer equipment, medium, and product to solve the problems of large workload and slow response speed in factory production and testing caused by artificial intelligence installation methods in related technologies.

[0005] In a first aspect, the present invention provides a method for installing an application, comprising: obtaining an application configuration request of a target device; the target device being a device for which an application is to be installed; determining a target customized application configuration file from a plurality of preset customized application configuration files according to the application configuration request; the target customized application configuration file being used to instruct the target device to install the application.

[0006] The application installation method of the present invention obtains the application configuration request of the target device on the cloud platform side, matches the target customized application configuration file as needed, realizes that the cloud platform acts as a centralized management and control node, uniformly distributes differentiated application configurations to multiple target devices, centrally manages the set of applications that can be installed on each target device, reduces the difficulty of deployment and maintenance of large-scale terminal application clusters, eliminates the need to create a dedicated system image for each project, and when the project software requirements change, only the application scenario strategy or software version needs to be adjusted on the cloud platform, and the device can pull the configuration again without returning to the factory for reinstallation, thus improving the installation efficiency of the application.

[0007] In one optional implementation, the application installation method further includes: sending a target customized application configuration file to a target device, so that the target device verifies the target customized application configuration file according to multiple application configuration parameters carried in the target customized application configuration file, and after the verification is passed, installing the application to be installed corresponding to the target customized application configuration file according to the software application list in the target customized application configuration file.

[0008] The application installation method of the present invention sends a target customized application configuration file to a target device, verifies the target customized application configuration file through the target device, and, after successful verification, installs the application to be installed corresponding to the target customized application configuration file according to the software application list in the target customized application configuration file. The verification process effectively avoids abnormal installation problems caused by configuration file tampering and transmission errors, and ensures the security and accuracy of the application installation process and the final installation result.

[0009] In one alternative implementation, the application installation method further includes: storing the target customized application configuration file on an offline storage device, so as to import the target customized application configuration file into the target device via the offline storage device.

[0010] The application installation method of the present invention stores the target customized application configuration file on an offline storage device, so as to import the target customized application configuration file into the target device through the offline storage device. This method is suitable for offline production installation scenarios with no network connection or limited network environment, avoiding the problem of configuration acquisition failure due to unstable network transmission or network permission restrictions. It can take into account the different needs of online batch deployment and offline customized installation.

[0011] In one optional implementation, selecting a target customized application configuration file from multiple preset customized application configuration files based on the application configuration request includes: parsing the serial number of the target device carried in the application configuration request; querying each preset customized application configuration file according to the serial number to obtain the target customized application configuration file corresponding to the serial number.

[0012] The application installation method of the present invention, by parsing the target device serial number carried in the application configuration request, and using the serial number as a search condition to query and match in multiple preset customized application configuration files, can accurately locate the customized application configuration file that matches the current target device, thus avoiding the problem of mismatch between configuration files of different devices.

[0013] In one optional implementation, the application installation method further includes: in response to an application scenario creation instruction triggered by a target object, obtaining multiple application scenarios and application installation resource packages associated with each application scenario; in response to a project creation instruction triggered by the target object, obtaining multiple preset customized application configuration files; associating each preset customized application configuration file with its corresponding serial number to obtain a first association relationship; and associating each preset customized application configuration file with its corresponding application scenario to obtain a second association relationship; and storing the associated preset customized application configuration files based on the first association relationship and the second association relationship.

[0014] The application installation method of this invention, by responding to application scenario creation instructions and project creation instructions, obtains the installation resource package corresponding to the application scenario and a preset customized application configuration file, and establishes a first association relationship between the configuration file and the serial number, and a second association relationship between the configuration file and the application scenario, so that each preset customized application configuration file is simultaneously bound to the serial number and application scenario information. At the same time, it can also support retrieving preset customized application configuration files by device serial number and by application scenario, reducing the query cost of preset customized application configuration files, facilitating batch application deployment across multiple devices and application scenarios, and improving the convenience and deployment efficiency of customized applications.

[0015] In one alternative implementation, the application installation method further includes: in response to a multi-scenario file generation instruction triggered by the target object, merging software application lists from multiple application scenarios to generate a preset customized application configuration file.

[0016] The application installation method of the present invention, in response to the multi-scenario file generation instruction triggered by the target object, can automatically merge the software application lists corresponding to multiple application scenarios and integrate them into a unified preset customized application configuration file, which meets the usage requirements of a single target device to support multiple application scenarios at the same time. It eliminates the need to generate configuration files multiple times for the same target device, further simplifying the installation process of multi-scenario applications and adapting to flexible and ever-changing business deployment requirements.

[0017] In a second aspect, the present invention provides an application installation apparatus, comprising: a request acquisition unit, configured to acquire an application configuration request from a target device; the target device being a device for which an application is to be installed; and a file determination unit, configured to determine a target customized application configuration file from a plurality of preset customized application configuration files according to the application configuration request; the target customized application configuration file being used to instruct the target device to install the application.

[0018] Thirdly, the present invention provides an electronic device, comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the application installation method of the first aspect or any corresponding embodiment thereof, or the application installation method of the second aspect or any corresponding embodiment thereof.

[0019] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the installation method of the application program described in the first aspect or any of the corresponding embodiments thereof, or the installation method of the application program described in the second aspect or any of the corresponding embodiments thereof.

[0020] Fifthly, the present invention provides a computer program product, including computer instructions for causing a computer to execute the installation method of the application program described in the first aspect or any of the corresponding embodiments thereof, or the installation method of the application program described in the second aspect or any of the corresponding embodiments thereof. Attached Figure Description

[0021] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0022] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of the present invention; Figure 2 This is a schematic diagram of a first method for installing an application according to an embodiment of the present invention; Figure 3 This is a schematic diagram of a second process for installing an application according to an embodiment of the present invention; Figure 4 This is a schematic diagram of a third process for installing an application according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the fourth process of an application installation method according to an embodiment of the present invention; Figure 6 This is a schematic diagram of the structure of an application installation system according to an embodiment of the present invention; Figure 7 This is a schematic diagram of the fifth process of an application installation method according to an embodiment of the present invention; Figure 8 This is a structural block diagram of an application installation device according to an embodiment of the present invention; Figure 9 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] It is understood that before using the technical solutions disclosed in the various embodiments of the present invention, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in the present invention and their authorization should be obtained in accordance with relevant laws and regulations through appropriate means.

[0025] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, "a plurality of" means two or more, unless otherwise explicitly specified.

[0026] As an optional application scenario of this invention, such as Figure 1 As shown, the application's installation system may include at least one electronic device and at least one server. Figure 1 The system is illustrated in the example, which includes a computer 101, a mobile terminal 102, and a server 103, and the terminal devices such as the computer 101 and the mobile terminal 102 are connected to the server 103 through a network 110.

[0027] Specifically, electronic devices can be smartphones, tablets, laptops, PDAs, desktop computers, game consoles, smart TVs, smart wearable devices, in-vehicle terminals, VR (Virtual Reality) devices, AR (Augmented Reality) devices, AI hosts, etc. Server 103 can be a standalone physical server, a server cluster, a distributed system, or a cloud server providing cloud services. Network 110 can be a wired or wireless network, examples of which include, but are not limited to, the Internet, corporate intranets, local area networks, wide area networks, mobile communication networks, and combinations thereof.

[0028] In actual project delivery, the customization requirements for AI mainframes change frequently, and the software combinations required for different customers, projects, and batches of equipment often differ. Even for the same type of software, different versions may need to be installed due to factors such as project version, model version, hardware resources, and customer security requirements.

[0029] In related technologies, AI-based installation typically occurs during the factory production phase, where a software list is manually compiled based on project requirements, and the necessary software is pre-installed into the device system image. This method involves a large workload for factory pre-installation, frequent software version changes, and the inability to uniformly pre-install software for different scenarios. Device local storage, video memory, RAM, and computing power resources are limited. Project-device binding and management are difficult. If the installation package or script is copied, unauthorized devices may also install the corresponding software. Different projects, different customers, and different versions generate a large number of system images, making version maintenance complex and prone to confusion. Once pre-installation is complete, the software is usually already locally present, making it difficult to restrict its installation or operation on devices with specific serial numbers.

[0030] In related technologies, AI installation methods also include pre-installing a software download center or application market on the AI ​​host. Users can see all installable software on their devices and click to install as needed. This method generally includes the following steps: the software download center is pre-installed on the device; the software center connects to the server to obtain a complete list of software; the user selects the required software; the device downloads the software package and executes the installation. However, this method cannot precisely control the software scope for a project. Customers may mistakenly install software that is not suitable for the current project, leading to dependency conflicts, port conflicts, or insufficient resources; software licensing control is insufficient, and installation packages and scripts may be copied to other devices for use; and customized projects cannot be managed and maintained through a cloud platform.

[0031] This invention provides a method for installing applications, which completes the installation through a pre-customized adaptation configuration file on a cloud platform, thereby improving the installation efficiency of artificial intelligence applications.

[0032] According to an embodiment of the present invention, an embodiment of an application installation method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0033] This embodiment provides a method for installing an application, which can be used on a cloud platform. Figure 2 This is a first flowchart of an application installation method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps: Step S201: Obtain the application configuration request of the target device; the target device is the device where the application is to be installed.

[0034] The target device refers to the hardware entity that will be responsible for installing the application, such as an AI host. In other words, it is a device pre-installed with an AI-related operating environment, inference engine, model, or business application, which can be used for applications such as local inference, intelligent operation and maintenance, AI bidding, knowledge base question answering, and visual recognition.

[0035] The target device is used to generate an application configuration request for the application to be installed based on device attribute information, and then send the application configuration request to the cloud platform. During the target device determination process, by receiving an application installation request initiated on the current device, the machine initiating the installation request is identified as the target device for the application to be installed. Then, the machine's device information is read to obtain device attribute information such as the device's unique identifier, system version, and hardware model. Alternatively, it can receive remote installation commands issued by the cloud platform, parse the device location information carried in the commands, locate the corresponding controlled terminal device within the network, and identify that controlled terminal as the target device. It can also display a list of accessible devices, and, in response to the user's selection, identify the device selected by the user as the target device for the application to be installed.

[0036] The application configuration request is a configuration request sent by the target device to obtain the target customized application configuration file. Specifically, it obtains the target device's serial number (SN) and device asset information; device attribute information includes the serial number and device asset information; and the application configuration request is obtained by encapsulating the message based on the serial number and device asset information.

[0037] Specifically, device asset information refers to all attribute data used to identify and describe a hardware device. This information includes the device model, system version, local customized management platform version, currently installed application list, optional hardware resource information such as CPU, memory, video memory, and disk space, as well as optional device authentication information. When the target device leaves the factory, its serial number and device asset information are programmed into a one-time programmable area of ​​the chip or a hardware storage chip. The serial number and device asset information of the target device are obtained by reading this one-time programmable area or hardware storage chip.

[0038] In one specific example, the target device sends an application configuration request to the cloud platform interface through a communication channel, and the cloud platform receives the application configuration request according to the interface.

[0039] Step S202: Based on the application configuration request, determine the target customized application configuration file from multiple preset customized application configuration files; the target customized application configuration file is used to instruct the target device to install the application.

[0040] The cloud platform pre-stores multiple preset customized application configuration files, each bound to a matching serial number. The cloud platform receives application configuration requests uploaded by the target device, parses the request content, and filters out a unique target customized application configuration file through the target device's serial number. The multiple preset customized application configuration files are multiple sets of application configuration files pre-stored by the cloud platform, and each set of application configuration files includes a list of AI software applications that are allowed to be installed on its corresponding target device.

[0041] In one specific example, the cloud platform can also pre-group multiple target devices. Each preset customized application configuration file is bound to a device group tag. Based on the device SN in the application configuration request, the cloud platform ledger is queried to obtain the device group to which the target device belongs. The device group tag is used as a matching condition to match the group tag bound to the preset customized application configuration file. If the group matching is successful, the target customized application configuration file is obtained.

[0042] The application installation method of this invention involves the cloud platform obtaining the application configuration request of the target device, matching the target customized application configuration file as needed, and enabling the cloud platform to act as a centralized management node to uniformly distribute differentiated application configurations to multiple target devices. This centralized management of the set of applications that can be installed on each target device reduces the difficulty of deploying and maintaining large-scale terminal application clusters. It eliminates the need to create a dedicated system image for each project. When project software requirements change, only the application scenario strategy or software version needs to be adjusted on the cloud platform, and the device can then re-pull the configuration without having to return to the factory for reinstallation, thus improving the efficiency of application installation.

[0043] This embodiment provides a method for installing an application, which can be used on a cloud platform. Figure 3 This is a second flowchart of an application installation method according to an embodiment of the present invention, such as... Figure 3 As shown, the process includes the following steps: Step S301: Obtain the application configuration request of the target device; the target device is the device where the application is to be installed.

[0044] Step S302: Based on the application configuration request, determine the target customized application configuration file from multiple preset customized application configuration files; the target customized application configuration file is used to instruct the target device to install the application.

[0045] Specifically, step S302 includes: Step S3021: Parse the serial number of the target device carried in the application configuration request.

[0046] The cloud platform receives the original message of the application configuration request uploaded by the target device, parses the original message into a structured object in the cloud platform's memory, locates the child node corresponding to the device asset information from the structured object, reads the value of the serial number field, and obtains the serial number of the target device.

[0047] Step S3022: Query each preset customized application configuration file according to the serial number to obtain the target customized application configuration file corresponding to the serial number.

[0048] In one specific example, the serial number is used as an index to search through multiple preset customized application configuration files to obtain the target customized application configuration file corresponding to the serial number.

[0049] In another specific example, all preset custom application configuration files can be traversed based on the serial number to determine whether the current SN exists in the SN whitelist of the preset custom application configuration file; if the SN matches the whitelist of a preset custom application configuration file, then the configuration file is selected as a candidate; if multiple configuration file whitelists contain the SN, then the highest priority configuration file is selected as the target custom application configuration file according to the configuration priority.

[0050] In another specific example, the cloud platform can also maintain an independent mapping data table, with the device serial number as the primary key and the target customized application configuration file identifier stored in the field. Using the serial number as the index key, the mapping table can be queried directly to obtain the target customized application configuration file identifier; the corresponding preset customized application configuration file can be read based on the target customized application configuration file identifier and used as the target customized application configuration file.

[0051] The application installation method of the present invention, by parsing the target device serial number carried in the application configuration request, and using the serial number as a search condition to query and match in multiple preset customized application configuration files, can accurately locate the customized application configuration file that matches the current target device, thus avoiding the problem of mismatch between configuration files of different devices.

[0052] In some optional implementations, when a target device requests configuration, the cloud platform queries its target customized application configuration file and application scenario based on the target device's SN, and obtains the corresponding software application list, version information, icon, installation script, and download address based on the application scenario. For example, when generating the target customized application configuration file, the cloud platform writes the device's preset SN into the configuration file, sets a version number and validity period for the configuration file, generates an authorization token bound to the SN for each software application, generates hash verification values ​​for the installation script and software packages, and digitally signs the entire target customized application configuration file. Optionally, the configuration file or its sensitive fields are encrypted based on the device SN. Optionally, a time-limited download address is generated to prevent download links from remaining valid for an extended period.

[0053] In some optional implementations, an authorization token bound to the serial number (SN) is generated for each software application. This includes: the cloud platform maintaining a platform key (platformSecret, a high-strength random string of at least 256 bits); the local customized management platform pre-setting this key at the factory; and when generating the token, concatenating the computer device SN, application identifier (appId), software version (softwareVersion), and expiration time (expireTime) using a fixed separator to form the token payload (tokenPayload). Then, a device serial number bound token (snBindToken) is generated using one of the following two methods: First, using the platformSecret as the key to calculate the symmetric message authentication code on the tokenPayload, and the result is Base64 encoded as the snBindToken. The computer device recalculates the hash message authentication code using the same key and the same concatenation method and compares it with the token in the configuration file; if they match, it is valid. The second method uses the platformSecret as the key to encrypt the tokenPayload using AES-256-GCM (a block cipher algorithm with a 256-bit key) (including a random one-time number to prevent replay). The ciphertext is then Base64 encoded as the snBindToken. The computer device decrypts the token and compares it against the SN, appId, version, and expiration date. Because the token is bound to a specific SN, even if the configuration file is copied to another device, the token verification will inevitably fail due to the different SN.

[0054] In some optional implementations, hash checksums are generated for the installation script and software packages. This includes: the cloud platform synchronously calculates hash values ​​when uploading the installation script and software packages, using the SHA-256 algorithm to obtain the installation script hash (scriptHash) and the software package hash (packageHash). The scriptHash is used to verify the integrity of the installation script, and the packageHash is used to verify the integrity of the software packages (including dependency packages, model packages, etc.). For large files, incremental hash calculation can be performed by reading in chunks. After downloading, the device recalculates the hash and compares it with the value in the configuration file to ensure that the file has not been tampered with during transmission.

[0055] In some optional implementations, the entire target customized application configuration file is digitally signed, including: the cloud platform holding a pair of asymmetric keys: cloudPrivateKey (private key, stored only in the cloud platform's secure environment) and cloudPublicKey (public key, pre-installed in the local customized management platform of the computer device). The signature algorithm can be RSA-SHA256, ECDSA, or the Chinese national cryptographic standard SM2. The signing process is as follows: generate a complete target customized application configuration file JSON, with the signature field temporarily empty; remove the signature field, serialize the remaining JSON into standardized configuration data according to the standard format, calculate the SHA-256 digest, sign the SHA-256 digest using the cloud platform's private key; and write the Base64 encoded digest signature into the signature field. The signed target customized application configuration file has the authenticity of its source and the integrity of its content; any modification to any field will result in signature verification failure.

[0056] In some alternative implementations, the configuration file or its sensitive fields are encrypted based on the device SN, including encrypting sensitive parts of a software package, model package, or installation script using a key associated with the device SN.

[0057] Step S303: Send the target customized application configuration file to the target device so that the target device can verify the target customized application configuration file according to the multiple application configuration parameters carried in the target customized application configuration file. After the verification is successful, install the application to be installed corresponding to the target customized application configuration file according to the software application list in the target customized application configuration file.

[0058] The cloud platform sends the target customized application configuration file to the target device via a communication channel. The target device then receives the configuration file, verifies it, and, upon successful verification, installs the corresponding application based on the software application list within the configuration file.

[0059] A communication channel is configured between the cloud platform and the target device. Based on the communication channel, the application configuration request is sent to the cloud platform interface. The communication channel can be built using common IoT protocols such as HTTP (Hypertext Transfer Protocol) and MQTT (Message Queuing Telemetry Transport).

[0060] In some optional implementations, after the cloud platform matches the target customized application configuration file among multiple preset customized application configuration files, it sends the target customized application configuration file as a response payload to the target device that initiated the application configuration request through the established communication channel.

[0061] In some alternative implementations, the application installation method further includes storing the target customized application configuration file on an offline storage device to import the target customized application configuration file into the target device via the offline storage device.

[0062] Offline storage devices include USB flash drives, local area network file servers, or offline media. The target device verifies the device serial number (SN), configuration signature, and package hash. Devices without the specified SN cannot import or install the offline target-customized application configuration file.

[0063] The application installation method of this invention stores the target customized application configuration file on an offline storage device, so as to import the target customized application configuration file into the target device through the offline storage device. This method is suitable for offline production installation scenarios with no network connection or limited network environment, and avoids the problem of configuration acquisition failure due to unstable network transmission or network permission restrictions. It can take into account the different needs of online batch deployment and offline customized installation.

[0064] In some optional implementations, the application installation method further includes: in response to an application scenario creation instruction triggered by a target object, obtaining multiple application scenarios and application installation resource packages associated with each application scenario; in response to a project creation instruction triggered by the target object, obtaining multiple preset customized application configuration files; associating each preset customized application configuration file with its corresponding serial number to obtain a first association relationship; and associating each preset customized application configuration file with its corresponding application scenario to obtain a second association relationship; and storing the associated preset customized application configuration files based on the first association relationship and the second association relationship.

[0065] The target entity creates multiple application scenarios on the cloud platform and configures a corresponding AI application installation resource package for each scenario. The AI ​​application installation resource package includes the software application, application icon, software version, and installation script. For example, a "default scenario" is created, associated with basic utility software; a "customized operation and maintenance scenario" is created, associated with an AI operation and maintenance platform, log model, monitoring and data collection components, etc.; and a "customized bidding and tendering scenario" is created, associated with an AI bidding and tendering assistant, bid document knowledge base service, document parsing model, etc. The cloud platform stores the mapping relationship between application scenarios, software application names, application icons, software versions, and installation scripts. For example, the mapping relationship between application scenarios and software applications is shown in Table 1.

[0066] Table 1: A schematic diagram of the mapping relationship between application scenarios and software applications.

[0067]

[0068] The default scenario can include basic tools and optional software common to all devices; the operation and maintenance customized scenario only includes operation and maintenance related software and installation scripts; and the bidding and tendering customized scenario only includes bidding and tendering related software and installation scripts.

[0069] In some optional implementations, the target object creates multiple preset customized application configuration files in the cloud platform and enters the SN of the target device corresponding to each preset customized application configuration file to obtain a first association relationship. In response to a project creation command triggered by the target object, multiple preset customized application configuration files are created. For example, the mapping relationship of the preset customized application configuration files is as follows: Preset customized application configuration file A → SN-A001, SN-A002 → Operation and maintenance customized scenario; Preset customized application configuration file B → SN-B001, SN-B002 → Bidding and tendering customized scenario. The cloud platform stores the first and second association relationships of the preset customized application configuration files, device preset SNs, and application scenarios. When different devices under the same project require different software sets, different application scenarios or combinations of multiple application scenarios can also be configured for different SNs. For example, the second association relationship between the preset customized application configuration files and device preset SNs is shown in Table 2.

[0070] Table 2: Schematic diagram of the second association between preset custom application configuration files and device preset SN.

[0071]

[0072] In some optional implementations, the cloud platform can generate independent authorization information for each target device's SN, such as: SN binding token, configuration decryption key derived from SN, configuration file signature, installation script signature, time-limited download address, package hash check value, and combined authorization code of device SN and application identifier. This authorization information is used to ensure that the specified software can only be obtained, decrypted, verified, or installed by the target device with the specified SN.

[0073] In some optional implementations, based on the first association relationship and the second association relationship, the preset customized application configuration files that have been associated are stored. When an application configuration request is received, the target customized application configuration file is determined from the stored multiple preset customized application configuration files according to the application configuration request.

[0074] The application installation method of this invention, in response to application scenario creation instructions and project creation instructions, obtains the installation resource package corresponding to the application scenario and a preset customized application configuration file. It then establishes a first association between the configuration file and the serial number, and a second association between the configuration file and the application scenario, ensuring that each preset customized application configuration file is simultaneously bound to both the serial number and application scenario information. Furthermore, it supports retrieving preset customized application configuration files using either the device's serial number or the application scenario, reducing the query cost of preset customized application configuration files and facilitating batch application deployment across multiple devices and application scenarios, thereby improving the convenience and deployment efficiency of customized applications.

[0075] In some alternative implementations, the application installation method further includes: merging software application lists from multiple application scenarios in response to a multi-scenario file generation instruction triggered by the target object, and generating a preset customized application configuration file.

[0076] The rules for merging software application lists from multiple application scenarios are as follows: for the same application, the highest version is taken; for the same application, the version specified by the project takes priority; if there is a port conflict, the administrator is prompted to adjust; if the resource requirements exceed the device capacity, distribution is prohibited or a risk warning is issued.

[0077] The application installation method of this invention, in response to the multi-scenario file generation instruction triggered by the target object, can automatically merge the software application lists corresponding to multiple application scenarios and integrate them into a unified preset customized application configuration file. This meets the usage requirements of a single target device to simultaneously support multiple application scenarios, eliminating the need to generate configuration files multiple times for the same target device. This further simplifies the installation process of multi-scenario applications and adapts to flexible and ever-changing business deployment needs.

[0078] The application installation method provided in this embodiment only requires the target device to be pre-installed with a unified local customized management platform at the factory. The software applications, versions, and installation scripts required for specific projects are dynamically distributed by the cloud platform based on the device's serial number (SN), and installation permissions are controlled through SN binding authorization and encryption verification mechanisms. This eliminates the need to create separate system images for each project at the factory, and enables subsequent on-demand installation through the unified pre-installed local customized management platform. A mapping relationship of "application scenario - software application - application icon - software version - installation script" is established in the cloud platform, allowing different application scenarios to correspond to different software installation sets. A binding relationship of "customized project - device SN - application scenario" is established in the cloud platform, ensuring that each device can only obtain application configurations corresponding to its own SN. After the target device is powered on, it automatically pulls the customized application configuration file from the cloud platform based on its own SN and dynamically renders the list of installable applications locally. Through SN binding, encryption, signing, or verification mechanisms, devices with non-specified SNs cannot install the corresponding software applications. This reduces the workload of factory pre-installation, improves project delivery efficiency, and supports rapid software version iteration and flexible adjustment of project strategies.

[0079] This embodiment provides a method for installing an application, which can be used on a target device. Figure 4 This is a third flowchart of an application installation method according to an embodiment of the present invention, such as... Figure 4 As shown, the process includes the following steps: Step S401: Obtain the target customized application configuration file that matches the application configuration request sent by the cloud platform.

[0080] The target customized application configuration file is a customized configuration file that is sent to the target device after the cloud platform is successfully matched.

[0081] In one specific example, the cloud platform sends the target customized application configuration file to the target device through a communication channel, and the target device obtains the target customized application configuration file.

[0082] In another specific example, the cloud platform can also put the target customized application configuration file into the HTTP response body and return it to the target device. The target device reads and parses the HTTP response body to obtain the target customized application configuration file.

[0083] In another specific example, the cloud platform can also encapsulate the target customized application configuration file into an MQTT message payload, and the target device listens for and captures the MQTT message payload to extract the target customized application configuration file.

[0084] In some optional implementations, after the target device is powered on, the local custom management platform automatically starts, reads the target device's serial number (SN), and sends an application configuration request to the cloud platform.

[0085] In some optional implementations, the local customized management platform serves as a unified foundational component for all AI hosts. The local customized management platform can be configured to: automatically start upon the first power-on of the target device; automatically pop up after the user logs into the system; provide an entry point on the desktop, start menu, or system tray; support manual refreshing of cloud platform configuration; and support displaying the current device serial number and the project scene it belongs to.

[0086] Step S402: Verify the target customized application configuration file. If the target customized application configuration file passes the verification, install the application to be installed corresponding to the target customized application configuration file on the target device according to the software application list in the target customized application configuration file.

[0087] The software application list is a list of artificial intelligence software applications stored in the target customized application configuration file, representing the artificial intelligence applications that the target device is allowed to deploy.

[0088] The verification of the target customized application configuration file includes two verification results: one is that the target customized application configuration file passes the verification, and the other is that the target customized application configuration file fails the verification.

[0089] Verification is a security verification operation that includes signature verification, hash verification, and certificate verification to confirm that the file has not been tampered with and that its source is trustworthy.

[0090] If the target customized application configuration file passes the verification, the target customized application configuration file is parsed, the software application list is extracted, the software application list is traversed, the installation packages of the applications to be installed are obtained in order, and the application installation is executed according to the installation packages of the applications to be installed.

[0091] In one specific example, the software application list can be parsed, the dependencies of each application can be extracted, multiple independent applications to be installed can be downloaded concurrently, and the installation service can be called in parallel to perform the installation.

[0092] In another specific example, the software application list can be parsed to obtain the target version of the target application, query the application versions currently installed on the target device, determine whether the local version matches the target version specified in the list, if the old version is already installed, obtain the differential incremental package, and perform an incremental upgrade without downloading the full installation package; if the old version is not installed, perform a full package installation.

[0093] In another specific example, the software application list can be parsed to obtain multiple applications to be installed, and the installation packages of each application can be obtained one by one. The applications can then be installed sequentially according to their installation packages.

[0094] In some optional implementations, the above method further includes: generating an installation status log file based on the installation information of the application to be installed, and sending the installation status log file to a cloud platform.

[0095] The installation status log file includes: device SN, target customized application configuration file number, application ID (Identifier), software version, installation result, installation time, error code, installation log summary, current service running status, etc.

[0096] The device serial number (SN) can be derived from the BIOS (Basic Input / Output System), motherboard serial number, TPM (Trusted Platform Module), security chip, system configuration file, device management interface, or production-written information.

[0097] Based on the installation information of the application to be installed, an installation status log file is generated and sent to the cloud platform. This allows the cloud platform to maintain the device software installation ledger based on the installation status log file, facilitating subsequent operation, maintenance, upgrades, and troubleshooting.

[0098] The application installation method provided in this embodiment obtains the target device of the application to be installed, generates an application configuration request corresponding to the application to be installed based on the device attribute information of the target device, and binds the application configuration request to the identity of the target device. This ensures that the cloud platform accurately matches the target customized application configuration file adapted to the target device, and sends the application configuration request to the cloud platform. The cloud platform is used to select the target customized application configuration file from multiple preset customized application configuration files according to the application configuration request, and can manage application combination schemes corresponding to different target devices and different application scenarios in batches. This embodiment of the invention obtains the target customized application configuration file sent by the cloud platform that matches the application configuration request, and verifies the target customized application configuration file. It can identify invalid target customized application configuration files in advance, prevent untrusted configuration files from initiating the installation process, and avoid security risks in application deployment. If the target customized application configuration file passes verification, the application to be installed corresponding to the target customized application configuration file is installed on the target device according to the software application list in the target customized application configuration file. Only after the target customized application configuration file is verified to be trustworthy and legal will the application installation proceed according to the software application list in the target customized application configuration file, thereby realizing automated application installation. Compared with related technologies, this embodiment of the invention only needs to obtain the target customized application configuration file according to the application configuration request of the target device, and then install the application to be installed corresponding to the target customized application configuration file. There is no need to create a dedicated system image for each project. When the software requirements of the project change, only the application scenario strategy or software version needs to be adjusted on the cloud platform, and the target device can re-pull the configuration without returning to the factory for reinstallation. This embodiment of the invention improves the installation efficiency and response speed of applications.

[0099] This embodiment provides a method for installing an application, which can be used on a target device configured with a local customized management platform. The target device can be the aforementioned electronic device. Figure 5 This is a fourth flowchart of an application installation method according to an embodiment of the present invention, such as... Figure 5 As shown, the process includes the following steps: Step S501: Obtain the target customized application configuration file that matches the application configuration request sent by the cloud platform. For details, please refer to [link to relevant documentation]. Figure 4 Step S401 of the illustrated embodiment will not be described again here.

[0100] Step S502: Verify the target customized application configuration file. If the target customized application configuration file passes the verification, install the application to be installed corresponding to the target customized application configuration file on the target device according to the software application list in the target customized application configuration file.

[0101] Specifically, step S502 above includes: Step S5021: Parse and obtain multiple application configuration parameters in the target customized application configuration file.

[0102] The application configuration parameters are various control parameters stored inside the target customized application configuration file, which are read by the application to be installed at runtime. These application configuration parameters include the device's preset serial number, validity period, cloud platform signature, and configuration version.

[0103] Read the original content of the target customized application configuration file from local storage, call the corresponding format parser to parse the text file into a structured data object in memory, locate the configuration node corresponding to the application configuration parameters from the parsed structured object, traverse and read all key-value pairs to obtain multiple application configuration parameters.

[0104] In one specific example, the target customized application configuration file can be parsed to generate a structured object, a set of predefined configuration path expressions can be defined to point to the various parameters that need to be obtained, and a path query engine can be used to directly query according to the path expressions to extract the corresponding multiple application configuration parameters in batches.

[0105] Step S5022: Verify each application configuration parameter separately to obtain the parameter verification results corresponding to each application configuration parameter.

[0106] Specifically, step S5022 includes: Step a1: Verify the integrity of the data structure of the target customized application configuration file and obtain the integrity verification result.

[0107] In some optional implementations, the integrity of the JSON structure of the target customized application configuration file is checked to confirm that all required fields are complete and of the correct type. If all required fields are complete and of the correct type, the integrity check result is "validation passed". If the required fields are incomplete or of the wrong type, the integrity check result is "validation failed".

[0108] Step a2: Based on the comparison result between the serial number of the target device and the preset serial number of the device, obtain the serial number verification result.

[0109] The serial number of the target device is compared with the preset serial number of the device. If the serial number of the target device matches the preset serial number of the device, the serial number verification result is "verification passed". If the serial number of the target device does not match the preset serial number of the device, the serial number verification result is "verification failed".

[0110] Step a3: Based on the comparison between the current time and the validity period, obtain the validity period verification result.

[0111] Obtain the expiration date from the target customized application configuration file, compare the current time with the expiration date, and if the current time is within the expiration date, the expiration date verification result is "verification passed"; if the current time is outside the expiration date, the expiration date verification result is "verification failed".

[0112] In some optional implementations, the target customized application configuration file can also be checked for tampering through a three-level verification process. The first level of verification confirms that the configuration file as a whole has not been tampered with through the aforementioned signature verification, and any addition, deletion, or modification of any field will result in a change in the hash digest. The second level of verification compares the device's preset serial number with the current device's serial number, the version number in the version field to ensure it is not lower than the local cached version (to prevent rollback attacks), whether the current time is within the effective start time and expiration deadline interval (to prevent expired replay), and whether the format of each field is valid. The third level of verification verifies the integrity of the data structure of the target customized application configuration file. When all three levels of verification pass, the verification result is considered passed; when any level of verification fails, the verification result is considered failed.

[0113] Step a4: Obtain the local verification fingerprint and original content digest corresponding to the cloud platform signature, and obtain the signature verification result based on the comparison result between the original content digest and the local verification fingerprint.

[0114] The signature field in the cloud platform signature is decoded to obtain the signature byte stream; the signature byte stream is decrypted according to the preset public key to obtain the original content digest; the cloud platform signature is hashed to obtain the local verification fingerprint.

[0115] Specifically, the signature field is extracted from the target customized application configuration file, and the signature field in the cloud platform signature is decoded to obtain the signature byte stream; the signature field is removed from the target customized application configuration file, and the remaining JSON is serialized according to the standard format and a local verification fingerprint is calculated; the signature byte stream is decrypted using a preset public key to obtain the original content digest, and the original content digest is compared with the local verification fingerprint. If the original content digest and the local verification fingerprint are consistent, the signature verification result is that the verification is successful; if the original content digest and the local verification fingerprint are inconsistent, the signature verification result is that the verification is unsuccessful.

[0116] In a specific example, the corresponding signature verification function can also be called, and the cloud platform signature, original digest, and preset public key can be input into the signature verification function to obtain the signature verification result.

[0117] If the signature verification result is successful, it means that the target customized application configuration file was issued by a legitimate cloud platform and has not been tampered with. If the signature verification result is unsuccessful, the configuration will not be loaded.

[0118] By obtaining the original content digest and the local verification fingerprint respectively, signature verification can be carried out from two different dimensions: signature decryption and restoration, and signature hash itself. This facilitates subsequent verification of the legality of the signature source and the integrity of the signature, and identifies abnormal situations such as signature tampering and signature forgery, thereby improving the comprehensiveness and accuracy of signature verification on the cloud platform.

[0119] Step a5: Obtain the hash message authentication code corresponding to the serial number of the target device, and obtain the authentication verification result based on the comparison result between the hash message authentication code and the cloud platform signature of each application.

[0120] For each application's cloud platform signature, the target device's serial number, application identifier, and software version number are read. When using a message authentication code based on SHA256 hash, the computer device's serial number, application identifier, and software version number are concatenated in the same format, the hash message authentication code is recalculated, and the hash message authentication code is compared with each application's cloud platform signature.

[0121] If the hash message authentication code matches the cloud platform signature, the authentication verification result is successful; if the hash message authentication code does not match the cloud platform signature, the authentication verification result is unsuccessful. When using a block encryption algorithm, the cloud platform signature of each application is decrypted to obtain the token payload. The device's preset serial number, preset application identifier, preset version identifier, and preset expiration timestamp are parsed out. The target device's serial number is compared with the device's preset serial number, the application identifier is compared with the preset application identifier, and the software version number is compared with the preset version identifier. It is determined whether the current time is before the preset expiration timestamp. If all verifications pass, the authentication verification result is successful. If any verification fails, the authentication verification result is unsuccessful, the application is marked as "unauthorized," and installation is prohibited.

[0122] Step a6: Based on the comparison between the local cache version and the configured version of the target device, obtain the version verification result.

[0123] If the local cache version of the target device is consistent with the configured version, the version verification result is "verification passed"; if the local cache version of the target device is inconsistent with the configured version, the version verification result is "verification failed".

[0124] The application installation method of this invention comprehensively determines the legality of the configuration through multi-dimensional verification results, constructing a multi-dimensional, three-dimensional security verification system. This significantly increases the difficulty for illegal configurations to bypass verification, thereby improving the security of application installation. Specifically, based on the comparison result between the serial number of the target device and the device's preset serial number, a serial number verification result is obtained, realizing the binding verification between the target device and the device's preset serial number of the target customized application configuration file, preventing the legitimate configuration file from being copied or migrated to other unauthorized devices. Based on the comparison result between the current time and the validity period, a validity period verification result is obtained, adding time-limited control capabilities to the target customized application configuration file. Through validity period verification, expired authorized configurations can be automatically intercepted, realizing time-dimensional control of application deployment permissions. By obtaining the local verification fingerprint corresponding to the cloud platform signature and the original content digest, and based on the comparison result between the original content digest and the local verification fingerprint... As a result, a signature verification result is obtained, ensuring that the target customized application configuration file is issued by a trusted cloud platform and has not been tampered with during transmission. By obtaining the hash message authentication code corresponding to the serial number of the target device, and comparing the hash message authentication code with the cloud platform signature of each application, an authentication verification result is obtained, realizing authorization verification at the application level, and accurately controlling the installation permissions of each application in the target customized application configuration file. Based on the comparison result between the local cache version and the configuration version of the target device, the version verification result is obtained, which can identify duplicate old version configurations, skip redundant installation processes, and accurately identify version upgrade requirements.

[0125] Step S5023: If all parameter verification results indicate that the verification has passed, then the target customized application configuration file is determined to have passed the verification.

[0126] The target customized application configuration file is deemed to have passed verification when all of the following verification results are passed: integrity verification, serial number verification, validity period verification, signature verification, authentication verification, and version verification.

[0127] When the target customized application configuration file passes the verification, the customized applications that the target device can install are dynamically rendered based on the list of software applications in the target customized application configuration file.

[0128] The software application list includes: application name, application icon, software version, application description, resource requirements, current installation status, install button, upgrade button, uninstall button, and installation log entry.

[0129] Because the software application list is dynamically generated based on the device serial number and application scenario, different computer devices will display different sets of installable applications even if they use the same system image.

[0130] By parsing the target customized application configuration file, multiple application configuration parameters are extracted and verified one by one. Based on the verification results of all parameters, the verification status of the configuration file is determined. This allows for the identification of specific abnormal configuration parameter items, and the recognition of abnormal configuration files with packet loss, file corruption, or incorrect formatting. This effectively intercepts customized application configuration files with parameter defects, avoiding application deployment failures and operational anomalies caused by abnormal configuration parameters, and improving the completeness and reliability of customized application configuration file verification.

[0131] Step S5024: In response to the application installation command triggered by the target object on the target device, perform authorization token verification on the application to be installed.

[0132] The target user selects the application to be installed in the local customized management platform and clicks install. In response to the application installation command triggered by the target user on the target device, the authorization token verification is performed again.

[0133] In some optional implementations, the authorization token verification of the application to be installed includes: obtaining the serial number of the target device, reading the SN binding token corresponding to the application to be installed, verifying the SN binding token using a local verification algorithm, a cloud platform public key, or a device private key, and determining whether the SN binding token is valid only for the current target device's SN, the current application to be installed, and the current version. If the SN binding token is valid only for the current target device's SN, the current application to be installed, and the current version, the authorization token verification result is that the verification passed; otherwise, the authorization token verification result is that the verification failed.

[0134] If the authorization token verification result is successful, the download and installation scripts and software resources are allowed; if the authorization token verification result is unsuccessful, the installation of the application to be installed is refused.

[0135] In this way, even if the configuration file or installation script is copied to other devices, those other devices will not be able to pass the SN authorization verification.

[0136] Step S5025: If the verification result of the authorization token is successful, download the program resource package of the application to be installed.

[0137] When the authorization token verification result is successful, the program resource package of the application to be installed is downloaded. The program resource package includes download address, installation script, software package, model package or dependency package, etc.

[0138] Step S5026: Perform hash verification and authorization token verification on the program resource package. If both verification results are successful, install the application to be installed according to the program resource package.

[0139] The system checks whether the hash value of the installation script matches the hash value of the configuration script in the target customized application's configuration file, and whether the hash value of the software package matches the overall hash of the software installation package in the target customized application's configuration file. If both match, the hash value verification result is considered successful; otherwise, the hash value verification result is considered unsuccessful.

[0140] At the same time, it verifies whether the authorization token in the download address is still valid. If it is valid, the authorization token verification result is "verification passed"; if it is invalid, the authorization token verification result is "verification failed".

[0141] The verification result is "verification passed" if both the hash value verification result and the authorization token verification result are passed; otherwise, the verification result is "verification failed".

[0142] In some alternative implementations, verification may also include: verifying the SN license file in the installation package and performing SN-based decryption of the encrypted software package.

[0143] If the verification result is successful, the application to be installed will be installed according to the program resource package. If the verification result is unsuccessful, the installation will be stopped, invalid files will be deleted, and the reason for the failure will be reported to the cloud platform.

[0144] In some optional implementations, the installation of the application to be installed is performed according to the program resource package, including: checking the system environment; checking hardware resources; checking dependent software; creating an installation directory; unzipping the software package and model package; writing configuration files; configuring environment variables; registering system services; starting the inference engine or business services; performing a post-installation health check; and returning installation results and error codes.

[0145] In some alternative implementations, during the installation of the program resource package, the local customization management platform can display the installation progress in real time and record the installation log.

[0146] In some optional implementations, after the program resource package is successfully installed, the target device's serial number can be verified when the target artificial intelligence application is launched to prevent users from bypassing the installation process and copying the software directory to other devices for operation.

[0147] The application installation method of this invention downloads the application resource package only when the authorization token verification result is successful. This improves the security of application resource package downloads by initiating the download only when the application authorization is legitimate. By performing hash verification and authorization token verification on the application resource package, the application to be installed is installed according to the application resource package when the verification result is successful. After the resource package download is complete, hash integrity verification and authorization token review are performed again to identify resource packages that have been tampered with, lost, or damaged during transmission. The second authorization token verification verifies the validity of the application authorization, forming a dual verification of the integrity of the resource package itself and the legitimacy of the application authorization. This ensures that the final deployed and running application is intact, unaltered, and its authorization remains valid, guaranteeing the secure and controllable installation and delivery of the application.

[0148] This embodiment provides an application installation system. Figure 6 This is a flowchart of the application installation system according to an embodiment of the present invention, such as... Figure 6 As shown, the process includes the following steps: The application installation system includes a cloud platform 601 and an AI host 602. The cloud platform 601 includes a device management module 6011, a customized project management module 6012, an application scenario management module 6013, a software application management module 6014, a scenario policy configuration module 6015, an SN binding authorization module 6016, a customized application configuration generation module 6017, a configuration distribution interface module 6018, and an installation status receiving module 6019. The AI ​​host 602 configures a local customized management platform, including a device SN acquisition module 6021, a configuration request module 6022, a configuration verification module 6023, an application list rendering module 6024, an installation script download module 6025, a software resource download module 6026, an installation execution module 6027, an SN authorization verification module 6028, an installation status feedback module 6029, and a local cache module 60210.

[0149] In some optional implementations, the device management module 6011 is used to input, import, query, and maintain AI host device SNs; the customized project management module 6012 is used to create customized projects and bind one or more device SNs to the customized project; the application scenario management module 6013 is used to create and maintain different application scenarios, such as default scenarios, operation and maintenance customized scenarios, bidding customized scenarios, etc.; the software application management module 6014 is used to maintain software application names, application icons, software versions, installation package addresses, model package addresses, installation scripts, dependency information, resource requirements, and description information; the scenario policy configuration module 6015 is used to establish a mapping relationship of "application scenario - software application - application icon - software version - installation script"; and the SN binding authorization module 6016... The module is used to generate authorization tokens, encryption keys, signature data, or verification fields based on the device SN, so that configuration files, installation scripts, or download links are bound to the specified SN; the customized application configuration generation module 6017 is used to generate customized application configuration files that can be obtained by the specified device according to the relationship of "customized project - device, SN - application scenario"; the configuration distribution interface module 6018 is used to respond to the configuration pull request of the AI ​​host and return the corresponding customized application configuration file to the legitimate device; the installation status receiving module 6019 is used to receive information such as software installation status, installation logs, error codes, and current version uploaded by the AI ​​host.

[0150] In some optional implementations, the device SN acquisition module 6021 is used to read the device SN of the AI ​​host; the configuration request module 6022 is used to send the device SN, device model, system version, hardware resource information, etc. to the cloud platform to request a customized application configuration file; the configuration verification module 6023 is used to verify the signature, validity period, SN, binding information and integrity of the configuration file returned by the cloud platform; the application list rendering module 6024 is used to display installable software applications on the local interface according to the configuration file, including application name, icon, version, description, installation status, resource requirements, etc.; and the installation script download module 6025 is used to download the corresponding installation script according to the installation script address or script identifier in the configuration file. The software resource download module 6026 is used to download resources such as software installation packages, model packages, dependency packages, or container images; the installation execution module 6027 is used to execute the installation script and complete software deployment, environment configuration, service startup, and post-installation verification; the SN authorization verification module 6028 is used to re-verify whether the current device SN is consistent with the authorized SN in the configuration file before installation, download, or script execution; the installation status feedback module 6029 is used to upload installation progress, installation results, failure reasons, and installed versions to the cloud platform; and the local caching module 60210 is used to cache the most recent valid configuration file, software installation status, and necessary installation logs to support status display or interrupted installation in case of network anomalies.

[0151] The application installation system of this invention reduces factory pre-installation workload: AI hosts only need to be pre-installed with a unified local customized management platform when shipped, eliminating the need to create dedicated system images for each project. It improves project delivery efficiency: when project software requirements change, only the application scenario strategy or software version needs to be adjusted on the cloud platform, and the device can then re-fetch the configuration without needing to return to the factory for reinstallation. It supports flexible customization across multiple scenarios: through the mapping relationship of "application scenario—software application—version—installation script," different software combinations can be configured for different business scenarios. It achieves precise distribution based on device SN: the cloud platform generates configuration files based on the relationship of "customized project—device SN—application scenario," ensuring that each device can only obtain its own authorized software list. It enhances software authorization security: through SN-bound tokens, configuration signatures, time-limited downloads, hash verification, SN-based encryption, and secondary verification of the installation script, devices with non-specified SNs cannot install the corresponding software. It adapts to rapid iteration of AI applications: software versions, model versions, and installation scripts can all be updated on the cloud platform, and the device can fetch the latest configuration on demand. Facilitates centralized operation and maintenance management: The cloud platform can record the software installation status, version information, and installation logs of each device, facilitating subsequent upgrades, troubleshooting, and asset management. Enhances project isolation capabilities: Software policies, installation licenses, and application lists for different projects are isolated from each other, reducing the risk of cross-project software misuse.

[0152] This embodiment provides a method for installing an application, which can be used on a computer device. Figure 7 This is a fifth flowchart of an application installation method according to an embodiment of the present invention, such as... Figure 7 As shown, the process includes the following steps: Device power on; Start local platform; Read SN; Request cloud configuration; Verify configuration; Render application list; User initiates installation; SN authorization verification; Download installation package; Hash verification; Execute installation; Upload installation status.

[0153] In some optional implementations, for projects without internet access, an offline configuration package bound to the device's serial number (SN) can be pre-generated by the cloud platform. This offline configuration package includes: a customized application configuration file; an installation script; a software package or model package; a SN authorization file; and signature and hash verification files. The device imports the configuration package via USB flash drive, a local area network file server, or offline media. The local customization management platform still verifies the device SN, configuration signature, and software package hash. Devices without the specified SN cannot import or install this offline configuration package.

[0154] In some alternative implementations, for customers with internal networks, the cloud platform can be deployed within the customer's local area network. The AI ​​host does not access the public network but instead accesses the internal cloud platform to obtain configuration files and install resources. This solution is suitable for customers with high security requirements.

[0155] In some alternative implementations, a single device can be bound to multiple application scenarios simultaneously. For example, a device may require both default scenario software and operation and maintenance customized scenario software. The cloud platform can merge the software application lists of multiple scenarios to generate a configuration file. The merging process can follow these rules: the highest version for the same application; priority for the version specified by the project for the same application; prompting the administrator to adjust if there are port conflicts; prohibiting distribution or issuing risk warnings when resource requirements exceed the device's capacity. This multi-factor binding enhances authorization security.

[0156] This invention addresses several issues in customized AI host delivery, including complex factory pre-installation, rapid version iteration, resource shortages, difficulties in project isolation, and insufficient software installation authorization control. It pre-installs a local customized management platform on the AI ​​host and maintains a mapping relationship of "customized project—device SN—application scenario—software application—software version—installation script" on the cloud platform. This allows the device to dynamically retrieve customized application configuration files based on the SN upon startup and display and install the corresponding software locally. Furthermore, this invention employs techniques such as SN-bound authorization, configuration signing, time-limited downloads, package hash verification, SN-based encryption, and secondary verification of the installation script to prevent devices with non-designated SNs from installing the corresponding software.

[0157] This embodiment also provides an application installation device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0158] This embodiment provides an application installation device, such as... Figure 8 As shown, it includes: The request acquisition unit 801 is used to acquire the application configuration request of the target device; the target device is the device where the application is to be installed. The file determination unit 802 is used to determine the target customized application configuration file from multiple preset customized application configuration files according to the application configuration request; the target customized application configuration file is used to instruct the target device to install the application.

[0159] In some optional implementations, the document determination unit 802 includes: The serial number parsing subunit is used to parse the serial number of the target device carried in the application configuration request.

[0160] The target file determination subunit is used to query each preset customized application configuration file according to the serial number to obtain the target customized application configuration file corresponding to the serial number.

[0161] In some alternative implementations, the application installation device further includes: The online installation unit is used to send the target customized application configuration file to the target device, so that the target device can verify the target customized application configuration file according to the multiple application configuration parameters carried in the target customized application configuration file, and after the verification is successful, install the application to be installed corresponding to the target customized application configuration file according to the software application list in the target customized application configuration file.

[0162] In some alternative implementations, the application installation device further includes: The offline installation unit is used to store the target customized application configuration file on an offline storage device, so as to import the target customized application configuration file into the target device through the offline storage device.

[0163] In some alternative implementations, the application installation device further includes: The information acquisition unit is used to acquire multiple application scenarios and the application installation resource package associated with each application scenario in response to the application scenario creation instruction triggered by the target object.

[0164] The file acquisition unit is used to acquire multiple preset custom application configuration files in response to the project creation command triggered by the target object.

[0165] The association unit is used to associate each preset customized application configuration file with its corresponding serial number to obtain a first association relationship; and to associate each preset customized application configuration file with its corresponding application scenario to obtain a second association relationship.

[0166] The file storage unit is used to store the pre-defined customized application configuration files that have been associated based on the first association relationship and the second association relationship.

[0167] In some alternative implementations, the application installation device further includes: The list merging unit is used to merge software application lists from multiple application scenarios in response to multi-scenario file generation instructions triggered by the target object, and generate a preset customized application configuration file.

[0168] The application installation apparatus provided in this embodiment of the invention can execute the application installation method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method. Further functional descriptions of the various modules and units described above are the same as in the corresponding embodiments described above, and will not be repeated here.

[0169] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0170] The following is a detailed reference. Figure 9 This diagram illustrates a structural schematic suitable for implementing an electronic device according to embodiments of the present invention. The electronic device may include a processor (e.g., a central processing unit, graphics processor, etc.) 901, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 902 or a program loaded from memory 908 into random access memory (RAM) 903. The RAM 903 also stores various programs and data required for the operation of the electronic device. The processor 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0171] Typically, the following devices can be connected to I / O interface 905: input devices 906 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 907 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; memory devices 908 including, for example, magnetic tapes, hard disks, etc.; and communication devices 909. Communication device 909 allows electronic devices to exchange data via wireless or wired communication with other devices. Although Figure 9 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown, and more or fewer devices may be implemented or have instead.

[0172] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 909, or installed from a memory 908, or installed from a ROM 902. When the computer program is executed by the processor 901, it performs the functions defined in the application installation method of the embodiments of the present invention.

[0173] Figure 9 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present invention.

[0174] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium after being downloaded via a network. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the application installation method shown in the above embodiments is implemented.

[0175] A portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0176] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for installing an application, characterized in that, The method includes: Obtain the application configuration request of the target device; the target device is the device on which the application is to be installed. Based on the application configuration request, a target customized application configuration file is determined from multiple preset customized application configuration files; the target customized application configuration file is used to instruct the target device to install the application.

2. The method according to claim 1, characterized in that, The method further includes: The target customized application configuration file is sent to the target device, so that the target device verifies the target customized application configuration file according to multiple application configuration parameters carried in the target customized application configuration file, and after the verification is passed, installs the application to be installed corresponding to the target customized application configuration file according to the software application list in the target customized application configuration file.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The target customized application configuration file is stored on an offline storage device, so that the target customized application configuration file can be imported into the target device through the offline storage device.

4. The method according to claim 1 or 2, characterized in that, The step of determining the target customized application configuration file from multiple preset customized application configuration files according to the application configuration request includes: Parse the serial number of the target device carried in the application configuration request; Based on the serial number, each preset customized application configuration file is queried to obtain the target customized application configuration file corresponding to the serial number.

5. The method according to claim 1 or 2, characterized in that, The method further includes: In response to an application scenario creation command triggered by a target object, multiple application scenarios and application installation resource packages associated with each application scenario are obtained; In response to a project creation command triggered by a target object, retrieve multiple preset custom application configuration files; Each preset customized application configuration file is associated with its corresponding serial number to obtain a first association relationship; and each preset customized application configuration file is associated with its corresponding application scenario to obtain a second association relationship. Based on the first association relationship and the second association relationship, the preset customized application configuration file that has been associated is stored.

6. The method according to claim 1 or 2, characterized in that, The method further includes: In response to the multi-scenario file generation instruction triggered by the target object, the software application lists of multiple application scenarios are merged to generate the preset customized application configuration file.

7. An application installation device, characterized in that, The device includes: A request acquisition unit is used to acquire an application configuration request from a target device; the target device is a device where an application is to be installed. The file determination unit is used to determine a target customized application configuration file from multiple preset customized application configuration files according to the application configuration request; the target customized application configuration file is used to instruct the target device to install the application.

8. An electronic device, characterized in that, include: A memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, the processor executing the computer instructions to perform the installation method of the application according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the installation method of the application program as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes computer instructions for causing a computer to execute the installation method of the application described in any one of claims 1 to 6.