Installation management method, device and system for mini-program applications

Abstract

This specification provides a method, device, and system for the installation and management of mini-program applications. This method can provide a mini-program application service with multiple mini-programs for a hardware device. The device management platform can uniformly manage the hardware devices on which the mini-program applications are installed, ensuring the legitimacy of the hardware devices running the mini-program applications. In addition, the hardware devices do not need to adapt to the environments of different applications, and the mini-program services within the mini-program application can be changed at any time without relying on device upgrades.

Description

[0001] This application is a divisional application of the invention patent application with application number 202010460387.4, application date May 27, 2020, and invention name “Installation management method, device, equipment and system for mini program application”. Technical Field

[0002] This specification belongs to the field of computer technology, and in particular relates to a method, device, and system for installing and managing mini-program applications. Background Art

[0003] With the advancement of computer technology, more and more apps (applications) with different functions have been developed and used. Many hardware terminals need to download apps with different functions. For example, a car terminal may download and install a map navigation app, a weather forecast app, a music app, a traffic violation query app, and so on. These apps need to be downloaded and installed one by one by the manufacturer or the user, which is cumbersome and requires the hardware devices to adapt to the installation environment of each app. In addition, there is no unified management of the hardware devices with installed apps. Summary of the Invention

[0004] The purpose of the embodiments of this specification is to provide a method, device, and system for mini-program application installation management, thereby improving the accuracy and efficiency of mini-program application installation management.

[0005] In a first aspect, embodiments of this specification provide a method for managing the installation of a mini-program application, the method comprising:

[0006] Receiving a calling application binding request sent by a user terminal, wherein the calling application binding request includes a calling application and a hardware device to be bound;

[0007] Binding the calling application to the hardware device according to the calling application binding request, and receiving product information and device information of the hardware device uploaded in batches by the user terminal through the calling application;

[0008] receiving a mini-program service binding request sent by the user terminal through the calling application, wherein the mini-program service binding request includes the hardware device and multiple mini-program services to be bound;

[0009] The corresponding plurality of mini-program services are returned according to the mini-program service binding request, so that the user terminal installs the plurality of mini-program applications including the mini-program services into the hardware device.

[0010] In a second aspect, this specification provides a method for installing and managing a mini-program application, the method comprising:

[0011] Sending a calling application binding request to a device management platform, wherein the calling application binding request includes a calling application and a hardware device to be bound, so that the device management platform binds the calling application to the hardware device according to the calling application binding request;

[0012] Uploading the product information and device information of the hardware devices in batches to the device management platform through the calling application;

[0013] Sending a mini-program service binding request to the device management platform, and receiving multiple mini-program services returned by the device management platform based on the mini-program service binding request;

[0014] The plurality of mini-program services are added to the mini-program application, and the mini-program application including the mini-program services is installed on the corresponding hardware device according to the product information and device information of the hardware device in the mini-program service binding request.

[0015] In a third aspect, an embodiment of this specification provides an installation and management device for mini-program applications, comprising at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, the installation and management method for mini-program applications described in the first aspect or the second method above is implemented.

[0016] In a fourth aspect, embodiments of this specification provide an installation management system for mini-program applications, comprising: a device management platform, a user terminal, and hardware devices; wherein the device management platform includes at least one processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the method described in the first aspect is implemented to provide a mobile application including multiple mini-programs;

[0017] The user terminal is used to include at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the method described in the second aspect to request to call a mobile application including multiple applets provided by the device management platform and install the mobile application into the hardware device.

[0018] The installation and management method, device, and system of mini-program applications provided in this specification can provide a mini-program application service with multiple mini-programs for hardware devices. The manufacturer of the hardware device can obtain multiple mini-programs returned by the device management platform by sending a binding mini-program service request to the device management platform, and install the mini-program application including multiple mini-programs in the hardware device. The device management platform can uniformly manage the hardware devices on which the mini-program applications are installed, ensure the legitimacy of the hardware devices running the mini-program applications, and ensure the security of the mini-program application services. In addition, the hardware device does not need to adapt to the environment of different applications, and the mini-program services within the mini-program application can be changed at any time without relying on device upgrades. The hardware device also does not need to install applications one by one, but directly integrates multiple mini-programs into one application and provides it to the manufacturer of the hardware device, so that the hardware device can have mini-programs with multiple services. The operation is simple, which reduces the application configuration time, manpower, and cost of the hardware device, and can also reduce the memory space occupied by the application in the hardware device. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0020] Figure 1 This is a flowchart of an embodiment of a method for installing and managing a mini-program application provided in an embodiment of this specification;

[0021] Figure 2 This is a flowchart of the installation and management of a mini-program application in another embodiment of this specification;

[0022] Figure 3 This is a schematic diagram of the manufacturer registration process in the embodiments of this specification;

[0023] Figure 4 is a schematic diagram of the device registration process in some embodiments of this specification;

[0024] Figure 5 This is a schematic diagram of the process of uploading a public key in some embodiments of this specification;

[0025] Figure 6 is a schematic diagram of the process of application binding in some embodiments of this specification;

[0026] Figure 7 This is a schematic diagram of the process of batch uploading of devices in some embodiments of this specification;

[0027] Figure 8 is a schematic diagram of the device authentication process in some embodiments of this specification;

[0028] Figure 9 This is a flowchart of a method for installing and managing mini-program applications on a user's terminal side in some embodiments of this specification;

[0029] Figure 10 This is a schematic diagram of the process for manufacturers to install mini-program applications in some embodiments of this specification;

[0030] Figure 11 This is a schematic diagram of the module structure of an embodiment of the installation and management device for mini-program applications provided in this specification;

[0031] Figure 12 This is a schematic diagram of the module structure of another embodiment of the installation and management device for mini-program applications provided in this specification;

[0032] Figure 13 This is a hardware structure block diagram of the installation management server of the mini-program application in one embodiment of this specification. DETAILED DESCRIPTION

[0033] To help those skilled in the art better understand the technical solutions in this specification, the following will provide a clear and complete description of the technical solutions in the embodiments of this specification, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. All other embodiments derived by those skilled in the art based on the embodiments in this specification without creative effort shall fall within the scope of protection of this specification.

[0034] With the development of computers, there are more and more types of mobile applications, that is, mobile applications. Different mobile applications can generally provide different services. If a user needs multiple services, he needs to download and install different mobile applications. In some embodiments of this specification, a method can be provided to provide a mobile application, that is, a mini-program application, for a hardware device, which includes multiple applets. Only one mobile application needs to be installed on the hardware device to use all the applets on the mobile application. A mini-program can be understood as an application that can be used without downloading and installing. It can be hosted in a mobile application and does not require independent development. Users can directly use the mini-programs in the mobile application. Different applets can provide different services, and each applet can meet relatively simple basic applications.

[0035] In some embodiments of this specification, a device management platform can be provided. The device management platform can be a network platform provided by some applications with multiple applets (such as some payment applications with more functions, social applications, etc.). The application can open up the ability to provide multiple applets to the outside world, that is, the device management platform can include multiple applets. The manufacturer or processing manufacturer of the hardware device can send a mobile application binding applet service request to the device management platform through its user terminal. The device management platform can return multiple applets to the manufacturer based on the received binding applet service request. The manufacturer can select the applets they need through the user terminal. The device management platform can add the applets selected by the manufacturer to the mobile application and return it to the manufacturer, and the manufacturer can install the mobile application into the hardware device. The hardware device can provide consumers with all the applet services in the mobile application. The hardware device can be a smart phone, tablet computer, computer, car-mounted device, smart wearable device, smart robot and other devices. The device management platform can also uniformly manage the hardware devices that apply to call the applets therein, which will lay an important foundation for subsequent risk control and punishment in the device dimension.

[0036] Figure 1 It is a flow chart of an embodiment of the installation management method of the mini-program application provided in the embodiment of this specification. Although this specification provides the method operation steps or device structure as shown in the following embodiments or drawings, more or fewer operation steps or module units may be included in the method or device based on routine or no creative labor. In the steps or structures where there is no necessary causal relationship logically, the execution order of these steps or the module structure of the device is not limited to the execution order or module structure shown in the embodiments or drawings of this specification. When the method or module structure is applied to an actual device, server or terminal product, it can be executed sequentially or in parallel according to the method or module structure shown in the embodiment or drawings (for example, a parallel processor or multi-threaded processing environment, or even an implementation environment of distributed processing and server clusters).

[0037] A specific implementation example Figure 1 As shown, in one embodiment of the mini-program application installation management method provided in this specification, the method can be applied on the device management platform side, which can be a terminal such as a computer, tablet computer, or server. The method can include the following steps:

[0038] Step 102: Review the registration information in the registration request uploaded by the user terminal. If the review is passed, return a registration success message.

[0039] In the specific implementation process, the user terminal may be the terminal corresponding to the manufacturer of the hardware device that produces, processes or sells the hardware device, which may be a smart phone, tablet computer, computer, etc. If the manufacturer wants to use the mini-program application service provided by the device management platform in the embodiment of this specification, it can first send a registration request to the device management platform through its corresponding user terminal. The registration request may include manufacturer information (such as name, address, website, business license, contact person, contact number, contact email, etc.). The device management platform can conduct a business access review on the registration information provided by the manufacturer and review the relevant qualification information of the manufacturer, such as whether the manufacturer is legal, whether the information filled in by the manufacturer is accurate, the production volume or ownership of the manufacturer's hardware equipment, whether the type of hardware equipment can use the mini-program application, and whether it meets the requirements for accessing the mini-program service. Other contents can also be reviewed, such as whether the CPU (central processing unit), memory, version, etc. of the hardware device meet the installation conditions of the mobile application and whether the registration information is accurate and reliable. Manufacturers that have the conditions for accessing the mini-program application service of the device management platform can be allowed to settle in, that is, the review is passed. After the review is passed, the device management platform will return a registration success message to the user terminal, that is, the manufacturer has successfully settled in the device management platform.

[0040] In some embodiments of this specification, after the manufacturer successfully settles in, it can upload product information, equipment information, etc. in the device management platform. Product information can include product types such as: cars, car-mounted, refrigerators, TVs, watches, etc. It can also upload the production capacity and shipment volume of different types of products. Different types of product information can correspond to a product identification. After the product information application is completed, the manufacturer can also create a model in the corresponding product type, that is, upload the device information of certain devices under the product type. The device information can represent the information of a specific device such as: a certain car from a car manufacturer. The device information can include the device identification and the device parameters of the device, etc. By building new data models and processes such as manufacturers, equipment, and models, the basic information of hardware equipment manufacturers, agent model information, and specific hardware equipment identification information are all collected and established in the device management platform, laying the foundation for subsequent management and punishment of the device dimension.

[0041] Step 104: Receive a mini-program service binding request sent by the user terminal after successful registration, and return a corresponding mini-program service according to the mini-program service binding request, so that the user terminal installs the mini-program application including the mini-program service into the corresponding hardware device.

[0042] In the specific implementation process, the device management platform can be a network platform provided by an application with multiple mini-programs (some payment applications, social applications, etc. with multiple service mini-programs), which can include multiple mini-programs in the application and can be managed directly by the application without the need for additional mini-program development and maintenance. After the manufacturer successfully settles in, it can send a binding mini-program service request to the device management platform, that is, request to call the mini-program service for the hardware device. The binding mini-program service request can include the bound mini-program service and the corresponding hardware device, such as: requesting to bind a map navigation mini-program, a music playback mini-program, a violation query mini-program, etc. for the on-board equipment of a certain car. After the device management platform receives the binding mini-program service request sent by the manufacturer, it can return the mini-program service requested to be bound by the manufacturer. The manufacturer can integrate the mini-program service returned by the device management platform into the mini-program application, and install the mini-program application to the corresponding hardware device. The mini-program service in the embodiments of this specification can be understood as a mini-program, and the mini-program application is an application that integrates multiple mini-program services. It can be understood as a mini-program engine, an application that can run in a hardware device, or an application package, such as: APK (Android application package), etc.

[0043] Step 106: Receive an application activation request for activating the mini-program application in the hardware device, where the application activation request includes signature information of the hardware device.

[0044] During the specific implementation process, after the mini-program application is installed in the hardware device, it needs to be activated before it can be used normally. The application activation request of the mini-program application can be triggered by clicking to log in to the mini-program application in the hardware device, or an application activation request for activating a mini-program application can be directly sent to the device management platform. The application activation request in the embodiment of this specification may include the signature information of the hardware device, and the signature information may be encrypted information for performing an encryption operation on the device information of the hardware device. The signature information can be used to perform security verification on the hardware device to prevent the leakage of the manufacturer's device information. Other devices can also use the same parameters to run the mini-program.

[0045] Step 108: Verify the hardware device according to the application activation request, and activate the mini-program application in the hardware device if the verification passes.

[0046] During the specific implementation process, after the device management platform receives the application activation request, it can verify the hardware device based on the application activation request. For example, by verifying the signature information in the application activation request, it can verify whether the request is sent by the manufacturer of the hardware device. It can also perform legal verification on the device information, manufacturer information, etc. in the application activation request. After the verification is passed, the mini program application in the hardware device can be activated.

[0047] In some embodiments of this specification, verifying the hardware device according to the application activation request may include:

[0048] When an application activation request is received, the product information and device information of the hardware device corresponding to the application activation request are obtained, and the obtained product information and device information are matched with the product information and device information uploaded by the user terminal. If the match is successful, the signature information is verified. If the verification passes, it is determined that the hardware device verification has passed.

[0049] In the specific implementation process, when an application activation request is received, the product information and device information of the hardware device corresponding to the application activation request can be obtained, and the obtained product information and device information can be matched with the product information and device information uploaded by the user terminal to determine whether the product information and device information of the hardware device corresponding to the application activation request are in the device management platform. If so, the match is successful, and the signature information is verified. If the signature verification passes, it is determined that the hardware device verification has passed, and the mini-program application in the hardware device is activated. Of course, other information of the hardware device can also be verified, and this specification does not specifically limit it. In the embodiment of this specification, by verifying the product information and device information of the hardware device, it can be verified that the hardware device is a legal device registered in the device management platform. Combined with the verification of the signature information, the legitimacy of the hardware device that activates the mini-program application can be determined more accurately, thereby improving the security of the installation device of the mini-program application.

[0050] The installation and management method of the mini-program application provided in the embodiments of this specification can provide a mini-program application service with multiple mini-programs for a hardware device. The manufacturer of the hardware device can obtain multiple mini-programs returned by the device management platform by sending a binding mini-program service request to the device management platform, and install the mini-program application including multiple mini-programs in the hardware device. The device management platform can uniformly manage the hardware device on which the mini-program application is installed, that is, the installation device of the mini-program application, to ensure the legitimacy of the hardware device running the mini-program application, and the hardware device does not need to adapt to the environment of different applications. The mini-program service within the mini-program application can be changed at any time without relying on device upgrades. The hardware device also does not need to install applications one by one, and directly integrates multiple mini-programs into one application and provides it to the manufacturer of the hardware device, so that the hardware device can have mini-programs with multiple services. The operation is simple, and the application configuration time, manpower and cost of the hardware device are reduced. It can also reduce the memory space occupied by the application in the hardware device.

[0051] Based on the above embodiments, in some embodiments of this specification, the method further includes:

[0052] After successful registration, receiving the public key of the hardware device uploaded by the user terminal;

[0053] The signature information of the hardware device is encrypted information obtained by encrypting the device information and product information of the hardware device using the private key corresponding to the public key;

[0054] The verifying the hardware device according to the application activation request includes:

[0055] The public key of the hardware device is used to decrypt and verify the signature information. If the decryption is successful, the signature verification is passed.

[0056] In specific implementations, the device management platform can provide manufacturers with a software development kit (SDK) with encryption algorithms. Manufacturers can use the SDK to generate a public and private key pair. The private key can be used to encrypt and sign the hardware device's device information, product information, and other information. For example, the private key can be used to encrypt the hardware device's product and device identification to obtain the hardware device's signature information. Each hardware device must be re-signed and cannot use the same call parameters. Device signatures can be signed using a generated RSA2 private key, with UTF-8 as the character set. After the manufacturer joins the device management platform, they can upload the product and device information of the hardware devices that will use the mini-program application services. They can also upload the hardware device's public key through the user terminal. When sending an application activation request to the device management platform, the hardware device's signature information, encrypted using the hardware device's private key, can be sent to the device management platform. When verifying the hardware device, the device management platform can decrypt and verify the signature information using the uploaded hardware device's public key. If decryption is successful, the signature verification passes, and the verification of other hardware device information continues.

[0057] It should be noted that the same manufacturer may have multiple products, and each product may have multiple series of hardware devices. In other words, the same manufacturer may have multiple hardware devices. The public and private keys used by different hardware devices can be the same, that is, a manufacturer has a pair of public and private keys to sign the device information of the hardware devices under its name. Different hardware devices can also have different public and private keys. For example, the manufacturer can use the information of different hardware devices to generate a pair of public and private keys for different hardware devices using an encryption algorithm, and transmit the public keys of different hardware devices to the device management platform. The manufacturer uses the corresponding private key to sign the device information and product information of the hardware device. The device management platform needs to use the public key corresponding to the hardware device to decrypt and verify the signature.

[0058] The embodiments of this specification utilize end-to-end (server to client) public and private key management. When the hardware manufacturer registers and uploads the device information of the hardware device, it uploads the public key corresponding to the hardware device. When the hardware device is dynamically running, in the pre-process of running the mini-program application, authentication is performed through the signature information of the device information, thereby ensuring the legitimacy of the device before running the mini-program application.

[0059] Based on the above embodiments, in some embodiments of this specification, the method may further include:

[0060] Generate a unique device identifier for the hardware device based on the device identifier in the device information of the hardware device uploaded by the user terminal and the startup information of the hardware device;

[0061] The unique device identifier is associated with the device identifier in the device information of the hardware device.

[0062] During the specific implementation process, when uploading device information, the manufacturer can upload the device identifier of the hardware device, such as the product serial number (such as SN, Serial Number) or the mobile device identification code (such as International Mobile Equipment Identity, IMEI). These device identifiers are defined or uploaded by the manufacturer. The device identifiers of different manufacturers may be the same. At the same time, the device identification has no direct relationship with the actual operating environment, and the device identifiers in the device management platform may be repeated. The device management platform can also generate a device unique identifier for the hardware device based on the device identifier in the device information of the hardware device uploaded by the manufacturer through the user terminal and the startup information when the hardware device is started, and associate the device unique identifier with the device identifier in the device information of the hardware device, establish the uniqueness of the device identifier in the global device manufacturer, ensure the uniqueness of the applet running by a single manufacturer and a single device, and different devices cannot simulate the same request parameters to run and open the applet, thereby ensuring the isolation and independence between hardware devices. Among them, the startup information may include environmental information when the hardware device is started, such as time, device startup parameters, geographic location, etc., which is not specifically limited in the embodiments of this specification.

[0063] Based on the above embodiment, in some embodiments of this specification, the startup information includes the startup time and startup random number of the hardware device;

[0064] Generating a unique device identifier for the hardware device based on the device identifier in the device information of the hardware device uploaded by the user terminal and the startup information of the hardware device includes:

[0065] Perform hash calculation on the device identifier, the startup time, and the startup random number to generate a unique identifier for the hardware device.

[0066] In the specific implementation process, in some embodiments of this specification, the operating environment of the hardware device can be used as a parameter for generating the device's unique identifier. That is, the startup information can include the hardware device's startup time and startup random number. The startup random number is a random number that serves as a parameter for the hardware device startup. After performing a hash calculation on the hardware device's device identifier, the hardware device's startup time, and the startup random number uploaded by the manufacturer, the hash calculation result can be used as the hardware device's unique identifier. The hash function used in the hash calculation can be selected according to actual needs and is not specifically limited in the embodiments of this specification.

[0067] In the embodiments of this specification, the operating environment and device identification of the hardware device are combined to generate a unique device identification for the hardware device, and the unique device identification is associated with the device identification in the device information of the hardware device, thereby establishing the uniqueness of the device identification in the global device manufacturer, ensuring the uniqueness of the mini program running on a single manufacturer and a single device, and different devices cannot simulate the same request parameters to run and open the mini program, thereby ensuring the isolation and independence between hardware devices.

[0068] Based on the above embodiments, in some embodiments of this specification, verifying the hardware device according to the application activation request further includes:

[0069] The unique device identifier of the hardware device is verified, and if the verification is successful, it is determined that the hardware device has passed the verification.

[0070] In a specific implementation, when verifying a hardware device, the unique device identifier of the hardware device may also be verified. For example, the device identifier in the application activation request may be verified to see if it has a corresponding unique device identifier in the device platform. If so, verification is successful. Alternatively, the device unique identifier in the application activation request may be verified to see if it exists in the device management platform. If so, verification is successful. Alternatively, verification may be performed in other ways, which are not specifically limited in this embodiment.

[0071] In the embodiment of this specification, during the pre-process of running the mini-program, authentication is performed through device information and the unique device identifier, thereby ensuring the legitimacy of the hardware device before running the mini-program application.

[0072] Based on the above embodiments, in some embodiments of this specification, the method further includes:

[0073] receiving a calling application binding request sent by the user terminal, wherein the calling application binding request includes a calling application to be bound;

[0074] Binding the calling application to the hardware device according to the calling application binding request;

[0075] Receive product information and device information uploaded in batches by the user terminal through the calling application.

[0076] During the specific implementation process, considering that hardware device manufacturers may mass-produce tens of thousands to hundreds of thousands of devices, the embodiments of this specification can provide a batch upload application capability interface, and the calling interface requires an open application identifier. In order to prevent others from making mistaken calls, in the embodiments of this specification, the manufacturer can send a calling application binding request to the device management platform, requesting that a calling application be bound to certain hardware devices. The calling application can upload and subsequently manage the device on behalf of the manufacturer. A calling application is a type of application, which can be a mini-program application, a web application, a mobile application, etc. After the device management platform receives the binding calling application request sent by the manufacturer through the user terminal, it can bind the calling application for the manufacturer. The manufacturer can connect to the interface of the device management platform through the calling application, access the device management platform, and further send a binding mini-program service request to the device management platform. For example: after accessing the device management platform through the bound calling application, the device information of the hardware device that needs to install the mini-program application can be registered in the device management platform. After successful registration, a call binding mini-program service request can be initiated for the hardware device. Each calling application can correspond to an application identifier, which can be connected to the device management platform. By calling the application, manufacturers can interact with the device management platform for data, realize the calling and installation of mini-program applications, and can also upload product information, device information, etc. of hardware devices in batches by calling the application. The uploaded hardware devices can also be edited and managed by calling the application.

[0077] In addition, the same hardware device can be bound to one or more calling applications, and each calling application can send a request to the hardware device to bind a different mini-program service.

[0078] The embodiments of this specification implement batch uploading of device information by binding and calling applications, thereby accelerating the data processing efficiency of mini-program applications.

[0079] Figure 2 This is a flowchart of the installation management of a mini-program application in another embodiment of this specification. Figure 2 The process of installing and managing the mini-program application in the embodiments of this specification is described in detail:

[0080] (1) Hardware equipment manufacturers enter the equipment management platform. Figure 3 This is a flowchart of the manufacturer registration process in the embodiment of this specification, such as Figure 3As shown, when registering on the device management platform, manufacturers need to provide complete manufacturer information (manufacturer registration account ID, manufacturer name, business address, company website, business license, main products, contact person, contact number, contact email address), etc. The device management platform will conduct a business access review of the information provided by the manufacturer, and the terminal platform will review the manufacturer's relevant qualification information to ensure that it meets the conditions for accessing the mini-program application. After the manufacturer's registration review is successful, the manufacturer's registration status can be updated on the device management platform. During the review period, the manufacturer can also query its review status on the device management platform.

[0081] (2) Figure 4 This is a flow chart of device registration in some embodiments of this specification. After the manufacturer completes the registration, it is necessary to apply for the type of device to be operated, such as car machine, car, refrigerator, TV, watch, etc., to determine the production capacity and shipment volume of the type. After the application is completed, the manufacturer can create a model in the corresponding device type and continue to upload the device identification. Figure 4 As shown, after the manufacturer uploads the device information, the device management platform needs to review the device information uploaded by the manufacturer, such as whether the device information is accurate and whether the hardware device meets the requirements for accessing the mini program application service.

[0082] (3) Upload the device public key. To prevent the leakage of the hardware manufacturer's hardware type identification and device identification, and to allow other devices to run the mini-program with the same parameters, the embodiments of this manual require the device to be signed. The hardware manufacturer uploads the public key to the terminal device platform and keeps the private key for the unique signature of each device. In the embodiments of this manual, the RSA2 public and private key verification method can be used. Figure 5 This is a flow chart of the public key upload process in some embodiments of this specification, such as Figure 5 As shown, after a manufacturer's application for a device type is approved, they can add a model under that device type. For example, for a certain brand of car, they can add the car model as a product identifier for a certain type of device. After the manufacturer uploads the hardware device's device information, the device management platform verifies the device's model name, number, and parameters. If verification is successful, the manufacturer's public key can be uploaded under the device information for signature verification of the hardware device.

[0083] (4) Upload device application binding. Considering that hardware device manufacturers may mass-produce tens to hundreds of thousands of devices, it is necessary to provide a batch upload application capability interface. The calling interface requires the open application identifier. In order to prevent others from calling it by mistake, it is necessary to add application binding for device identifier upload. The bound application can upload and subsequently manage the device on behalf of the manufacturer. Figure 6 is a flowchart of application binding in some embodiments of this specification, such as Figure 6As shown, when binding the calling application, the bound calling application can be verified. After the verification is successful, a binding relationship is established between the calling application and the product type of the hardware device, so that the manufacturer can interact with the device management platform through the calling application.

[0084] (5) Batch upload of device information. After completing the above steps, you can upload the device information to the specified manufacturer and product type through the open interface. Only the hardware devices uploaded through this step are legal devices and meet one of the conditions for running mini-programs. Figure 7 This is a flow chart of batch uploading of devices in some embodiments of this specification, such as Figure 7 As shown, after the application is successfully called and bound, the device information of multiple hardware devices can be uploaded in batches by calling the application. The device management platform will perform a legality check on the uploaded device information, such as: checking whether the binding relationship between the device model and the calling application is legal, whether the number of devices uploaded in batches meets the requirements, and whether the device identification of the hardware device is unique.

[0085] Since the entire hardware equipment is controlled by the hardware manufacturer, there is a great deal of uncertainty in the operating environment of the mini-program application, and the user's account security, data security, financial security, etc. all require a high level of security assurance. For this reason, the embodiment of this specification requires the hardware manufacturer to upload all the device information of all hardware devices to the device management platform as a unique identifier for subsequent security, risk control security scanning and penalties.

[0086] (6) Collection of device unique identification. The device identification is uploaded by the manufacturer itself, and is generally the SN or IMEI number of the hardware device, but it may be repeated between different manufacturers. At the same time, the device identification has no direct relationship with the actual operating environment. The embodiment of this specification combines the IMEI or SN of the actual operating hardware, combines the timestamp, random number and other information hash code to generate, generates it at the first startup, and persists it in the device as much as possible. The collection is automatically completed by the mobile application in the device management platform and uploaded to the server. The server automatically collects the device unique identification and establishes a unique mapping relationship with the device identification uploaded by the manufacturer. When the device is activated, the device operating environment information is collected to generate the global unique identification of the device, and the manufacturer's device identification is bound to the terminal device platform unique identification to facilitate the unified management of the hardware device.

[0087] (7) Device signature. To prevent manufacturers’ devices from using the same request parameters for business processing, which would result in the device not being included in the overall monitoring system, signature information needs to be generated for each device. The public key in step 3 is used to sign the private key. Each device needs to be signed again and the same call parameters cannot be used. The device signature method uses the generated RSA2 private key for signing, and the character set is UTF-8.

[0088] (8) After completing the above steps, ensure that the manufacturer is legal. At the same time, the devices that the manufacturer wants to run and install the mini-program application framework are already managed in the overall system. When the mini-program application is running and loaded, legality authentication is required to ensure that each device running the mini-program is within the scope of security control. Figure 8 This is a flow chart of device authentication in some embodiments of this specification, such as Figure 8 and Figure 2 As shown, the authentication process can be referred to as follows:

[0089] 1) Each device needs to generate a unique signature information, namely Signature (Product ID + Device ID + Private Key), based on the public key added during model registration. Each time the mini-program application in the hardware device is dynamically run, it needs to communicate with the mobile application in the device management platform through IPC (Inter-Process Communication) to activate the device.

[0090] 2) Before the device is activated, it is necessary to perform operation authentication control. According to the above steps (1) to (7), the running applet application passes in Hostappid (application identifier of the calling application), Productid (or productid, product identifier), Deviceid (or deviceid, device identifier), and Signature (or signature, signature information) for verification to determine the legitimacy of Productid and Device. If they are not in the device management platform, the activation will not pass. The legitimacy of the Signature is verified based on the public key uploaded by the Deviceid. If the signature verification fails, the activation will not pass. The device unique ID is verified. If the verification fails, the activation will not pass. Through the above steps, it is ensured that all hardware devices are within the control range of the device management platform system. At the same time, the information of each hardware device is collected, which can be used as an effective mechanism for risk control, punishment, and tracking in the future.

[0091] above Figure 3-Figure 8 The basic parameter check can be understood as checking whether the parameters of the manufacturer, hardware equipment, calling application, etc. are legal and non-empty. The specific inspection content is not specifically limited in the embodiments of this specification.

[0092] The embodiments of this specification, through the construction of new data models and processes such as manufacturers, equipment, and models, all the basic information of hardware equipment manufacturers, agent model information, and specific hardware equipment identification information are collected and established in the equipment management platform system, laying the foundation for the subsequent management and punishment of equipment dimensions. By utilizing end-to-end (server to client) public and private key management and a two-stage verification mechanism, when the hardware manufacturer registers and uploads the device, it uploads the public key corresponding to the hardware device. When the device is dynamically running, in the pre-process of running the mini-program, the device information and the unique signature of the device are used for authentication, which ensures the legitimacy of the device before running the mini-program. By constructing a unique mapping and binding between the device identifier and the automatically collected hardware information to generate the device unique identifier, the uniqueness of the device identifier in the global device manufacturer is established, which ensures the uniqueness of the mini-program run by a single manufacturer and a single device. Different devices cannot simulate the same request parameters to run and open the mini-program, which ensures the isolation and independence of devices.

[0093] Based on the above embodiments, some embodiments of this specification may also provide a method for installing and managing mini-program applications executed on the manufacturer's user terminal side. Figure 9 This is a flowchart of a method for installing and managing a mini-program application on a user's terminal side in some embodiments of this specification. Figure 9 As shown, the method may include:

[0094] Step 902: Send a registration request to the device management platform, and receive a registration success message returned by the device management platform after the registration review is passed.

[0095] During the specific implementation process, if the manufacturer wants to use the mini-program application service provided by the device management platform in the embodiment of this specification, it can first send a registration request to the device management platform through its corresponding user terminal. The registration request may include manufacturer information (such as: name, address, website, business license, contact person, contact number, contact email, etc.), and the device management platform can conduct a business access review of the registration information provided by the manufacturer and review the relevant qualification information of the manufacturer. For the specific review content, please refer to the records of the above embodiment and will not be repeated here. After the review is passed, the device management platform will return a successful registration message to the user terminal, that is, the manufacturer has successfully settled in the device management platform.

[0096] Step 904: Send a mini-program service binding request to the device management platform, and receive the mini-program service returned by the device management platform based on the mini-program service binding request.

[0097] During the specific implementation process, the device management platform can be a network platform provided by an application with multiple mini-program services (some payment applications, social applications, etc. with multiple service mini-programs), which can include multiple mini-programs in the application and can be managed directly by the application without the need for additional development and maintenance of mini-programs. Figure 10 This is a flowchart of the manufacturer installing the mini-program application in some embodiments of this specification, such as Figure 10 As shown, the device management platform will provide a mini-program pool, which includes multiple mini-program services. Manufacturers can select the mini-program services that need to be bound from the mini-program pool. After the device management platform receives the mini-program service binding request sent by the manufacturer, it can return multiple mini-program services to the manufacturer's user terminal based on the mini-program service binding request. For example: After the manufacturer successfully settles in and applies to bind the calling application, it accesses the device management platform through the calling application and can register the device information of the hardware device in the device management platform. After successful registration, the hardware device can integrate the mini-program engine framework and operating environment. After the device management platform receives the mini-program service binding request sent by the manufacturer, it can return multiple mini-programs to the user terminal where the manufacturer is located for the manufacturer to choose.

[0098] Step 906: Add the mini-program service to the mini-program application, and install the mini-program application including the mini-program service into the corresponding hardware device.

[0099] In the specific implementation process, the manufacturer can integrate the mini-program service returned by the device management platform into the mini-program application, and install the mini-program application into the corresponding hardware device. The mini-program application in the embodiments of this specification can be understood as an application that integrates multiple mini-program services, can be understood as a mini-program engine, can be understood as an application that can run in a hardware device, and can also be understood as an application package, such as: APK (Android application package, Android application package), etc. Figure 10 As shown, the bound mini-program services can be uploaded to different hardware devices, and different hardware devices can upload different mini-program services according to actual needs.

[0100] Step 908: Send an application activation request to the device management platform to activate the mini-program application in the hardware device, where the application activation request includes the signature information of the hardware device, so that the device management platform activates the mini-program application in the hardware device based on the application activation request.

[0101] During the specific implementation process, after the mini-program application is installed in the hardware device, it needs to be activated before it can be used normally. The application activation request of the mini-program application can be triggered by clicking to log in to the mini-program application in the hardware device, or the application activation request for activating a mini-program application can be directly sent to the device management platform. The application activation request in the embodiment of this specification may include the signature information of the hardware device. The signature information can be encrypted information of the device information of the hardware device. The signature information can be used to perform security verification on the hardware device to prevent the leakage of the manufacturer's device information. Other devices can also use the same parameters to run the mini-program. After receiving the application activation request, the device management platform can verify the hardware device based on the application activation request, such as: by verifying the signature information in the application activation request, verifying whether the request is sent by the manufacturer of the hardware device, and can also perform legal verification on the device information, manufacturer information, etc. in the application activation request. After the verification is passed, the mini-program application in the hardware device can be activated. The specific verification content can refer to the records of the above embodiment and will not be repeated here.

[0102] The installation and management method of the mini-program application provided in the embodiments of this specification can provide a mini-program application service with multiple mini-programs for hardware devices. The manufacturer of the hardware device can obtain multiple mini-programs returned by the device management platform by sending a binding mini-program service request to the device management platform, and select the mini-programs they need from them. The device management platform can uniformly manage the hardware devices on which the mini-program applications are installed, ensure the legitimacy of the hardware devices running the mini-program applications, and the hardware devices do not need to adapt to the environments of different applications. The mini-program services within the mini-program applications can be changed at any time without relying on device upgrades. The hardware devices also do not need to install applications one by one, but directly integrate multiple mini-programs into one application and provide it to the manufacturer of the hardware device, so that the hardware device can have mini-programs for multiple services. The operation is simple, which reduces the application configuration time, manpower and cost of the hardware device, and can also reduce the memory space occupied by the application in the hardware device.

[0103] Based on the above embodiments, in some embodiments of this specification, the method further includes:

[0104] After successful registration, upload the product information, device information and public key of the hardware device corresponding to the hardware device to the device management platform;

[0105] The signature information is obtained using the following method:

[0106] The product information and device information of the hardware device are encrypted using the private key corresponding to the public key of the hardware device to obtain the signature information.

[0107] During the specific implementation process, the device management platform can provide manufacturers with a software development kit for encryption algorithms, such as an SDK (Software Development Kit). Manufacturers can use the SDK to generate a pair of public and private keys. The private key can be used to encrypt and sign the device information, product information, etc. of the hardware device. For example, use the private key to encrypt the product identification and device identification of the hardware device to obtain the signature information of the hardware device. Each hardware device needs to be re-signed and the same call parameters cannot be used. The device signature method can use the generated RSA2 private key for signing, and the character set can be selected as UTF-8. Figure 10 As shown in the figure, after the manufacturer enters the device management platform, it can upload the product information and device information of the hardware devices that need to use the mini program application service in the device management platform. Figure 10 As shown, manufacturers can upload product information of different product types. Each product type can correspond to different series of hardware devices. For example, the car computer can include x1 series, x2 series, and x3 series. Figure 10 The Modelname in the code can be understood as the device name of different series of hardware devices. Figure 10 The productid in the product can represent the product identification of products of different product types, and the deviceid represents the device identification of different hardware devices, such as Figure 10 As shown, the device ID can use the sn provided by the manufacturer, that is, the serial number of the product. Figure 10 As shown, manufacturers can also upload the public key of the hardware device through the user terminal. When sending an application activation request to the device management platform, the signature information of the hardware device can be sent to the device management platform. The signature information can be an encrypted information of the device information of the hardware device. The signature information can be used to perform security verification on the hardware device to prevent the leakage of the manufacturer's device information. Other devices can also run the mini-program with the same parameters. When verifying the hardware device, the device management platform can use the public key of the hardware device uploaded by common sense to decrypt and verify the signature information. If the decryption is successful, the verification is passed and other information of the hardware device is verified.

[0108] Based on the above embodiments, in some embodiments of this specification, the method further includes:

[0109] Sending a calling application binding request to the device management platform, wherein the calling application binding request includes the calling application to be bound, so that the device management platform binds the calling application to the hardware device according to the calling application binding request;

[0110] The product information and device information are uploaded in batches through the calling application.

[0111] In the specific implementation process, considering that hardware device manufacturers may mass-produce tens of thousands to hundreds of thousands of devices, the embodiments of this manual can provide a batch upload application capability interface, and the calling interface requires an open application identifier. In order to prevent others from making accidental calls, in the embodiments of this manual, the manufacturer can send a calling application binding request to the device management platform to request the binding of a calling application. The calling application can upload and subsequently manage the device on behalf of the manufacturer. The calling application is a type of application, which can be a mini-program application, a web application, a mobile application, etc. Figure 10 The mobile application in the description can be understood as the calling application in the embodiment of this specification. After the device management platform receives the binding calling application request sent by the manufacturer through the user terminal, it can bind the calling application for the manufacturer. The manufacturer can connect to the interface of the device management platform through the calling application, access the device management platform, and further send a binding mini-program service request to the device management platform. For example: after accessing the device management platform through the bound calling application, the device information of the hardware device that needs to install the mini-program application can be registered in the device management platform. After the registration is successful, a call binding mini-program service request can be initiated for the hardware device. Each manufacturer's calling application can correspond to an application identifier, and the application identifier can be connected to the device management platform. By calling the application, the manufacturer can interact with the device management platform for data, realize the calling and installation of the mini-program application, and can also upload the product information, device information, etc. of the hardware device in batches by calling the application. The uploaded hardware devices can also be edited and managed by calling the application. For example Figure 10 As shown, Hostappid can be understood as the application identifier of the calling application. A hardware device can be bound to different calling applications, and different calling applications can bind different mini-program services to the hardware device. Different calling applications can be in different clients of the hardware device and can simultaneously exchange data with the device management platform. The device management platform provides the hardware device with a login state and the mini-program application runtime environment.

[0112] In this specification, the various embodiments of the above method are described in a progressive manner. The same or similar parts between the various embodiments can be referenced to each other. Each embodiment focuses on the differences from other embodiments. For related parts, refer to the partial description of the method embodiment.

[0113] Based on the installation management method of the mini-program application described above, one or more embodiments of this specification also provide a system for the installation management of the mini-program application. The system may include a system (including a distributed system), software (application), modules, components, servers, clients, etc. that use the method described in the embodiments of this specification and a device combined with necessary implementation hardware. Based on the same innovative concept, the devices in one or more embodiments provided in the embodiments of this specification are as described in the following embodiments. Since the implementation scheme and method for solving the problem of the device are similar, the implementation of the specific device in the embodiments of this specification can refer to the implementation of the aforementioned method, and the repetitions will not be repeated. As used below, the term "unit" or "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0114] Specifically, Figure 11 This is a schematic diagram of the module structure of an embodiment of the installation management device for the mini-program application provided in this specification. The device can immediately become the device management platform in the above embodiments, such as Figure 11 As shown, the mini-program application installation management device provided in this specification may include: a registration review module 111, a mini-program service binding module 112, an activation request receiving module 113, and an application activation module 114, wherein:

[0115] The registration review module 111 is used to review the registration information in the registration request uploaded by the user terminal, and return a registration success message if the review passes;

[0116] The mini-program service binding module 112 is configured to receive a mini-program service binding request sent by the user terminal after successful registration, and return a corresponding mini-program service according to the mini-program service binding request, so that the user terminal installs the mini-program application including the mini-program service into the corresponding hardware device;

[0117] An activation request receiving module 113 is configured to receive an application activation request for activating a mini-program application in a hardware device, wherein the application activation request includes signature information of the hardware device;

[0118] The application activation module 114 is configured to verify the hardware device according to the application activation request, and activate the mini-program application in the hardware device if the verification passes.

[0119] The installation and management device for mini-program applications provided in the embodiments of this specification can provide a mini-program application service with multiple mini-programs for hardware devices. The manufacturer of the hardware device can obtain multiple mini-programs returned by the device management platform by sending a binding mini-program service request to the device management platform, and select the mini-programs they need from them. The device management platform can uniformly manage the hardware devices on which the mini-program applications are installed, ensure the legitimacy of the hardware devices running the mini-program applications, and the hardware devices do not need to adapt to the environments of different applications. The mini-program services within the mini-program applications can be changed at any time without relying on device upgrades. The hardware devices also do not need to install applications one by one, but directly integrate multiple mini-programs into one application and provide it to the manufacturer of the hardware device, so that the hardware device can have mini-programs for multiple services. The operation is simple, which reduces the application configuration time, manpower and cost of the hardware device, and can also reduce the memory space occupied by the application in the hardware device.

[0120] In some embodiments of this specification, the device further includes an information receiving module for

[0121] After successful registration, receive product information and device information uploaded by the user terminal;

[0122] The application activation module is specifically used to:

[0123] When an application activation request is received, the product information and device information of the hardware device corresponding to the application activation request are obtained, and the obtained product information and device information are matched with the product information and device information uploaded by the user terminal. If the match is successful, the signature information is verified. If the verification passes, it is determined that the hardware device verification has passed.

[0124] In the embodiments of this specification, by verifying the product information and device information of the hardware device, it can be verified that the hardware device is a legitimate device registered in the device management platform. Combined with the verification of the signature information, the legitimacy of the hardware device that activates the mini-program application can be more accurately determined, thereby improving the security of the installation device of the mini-program application.

[0125] Based on the above embodiment, the device further includes a public key receiving module, which is used to:

[0126] After successful registration, receiving the public key of the hardware device uploaded by the user terminal;

[0127] The signature information of the hardware device is encrypted information obtained by encrypting the device information and product information of the hardware device using the private key corresponding to the public key;

[0128] The application activation module is specifically used to:

[0129] The public key of the hardware device is used to decrypt and verify the signature information. If the decryption is successful, the signature verification is passed.

[0130] The embodiments of this specification utilize end-to-end (server to client) public and private key management. When the hardware manufacturer registers and uploads the device information of the hardware device, it uploads the public key corresponding to the hardware device. When the hardware device is dynamically running, in the pre-process of running the mini-program application, authentication is performed through the signature information of the device information, thereby ensuring the legitimacy of the device before running the mini-program application.

[0131] Based on the above embodiment, the device further includes a unique identifier generation module configured to:

[0132] Generate a unique device identifier for the hardware device based on the device identifier in the device information of the hardware device uploaded by the user terminal and the startup information of the hardware device;

[0133] The unique device identifier is associated with the device identifier in the device information of the hardware device.

[0134] In the embodiments of this specification, a unique device identifier is generated for the hardware device based on the device identifier in the device information of the hardware device uploaded by the manufacturer through the user terminal and the startup information when the hardware device is started, and the unique device identifier is associated with the device identifier in the device information of the hardware device, thereby establishing the uniqueness of the device identifier in the global device manufacturer, ensuring the uniqueness of the mini-program run by a single manufacturer and a single device, and preventing different devices from simulating the same request parameters to run and open the mini-program, thereby ensuring the isolation and independence between hardware devices.

[0135] Based on the above embodiment, the startup information includes the startup time and the startup random number of the hardware device;

[0136] The unique identifier generation module is specifically used to:

[0137] Perform hash calculation on the device identifier, the startup time, and the startup random number to generate a unique identifier for the hardware device.

[0138] The embodiments of this specification combine the operating environment and device identification of the hardware device to generate a unique device identification for the hardware device, and associate the unique device identification with the device identification in the device information of the hardware device, thereby establishing the uniqueness of the device identification in the global device manufacturer, ensuring the uniqueness of the mini-program running on a single manufacturer and a single device, and preventing different devices from simulating the same request parameters to run and open the mini-program, thereby ensuring the isolation and independence between hardware devices.

[0139] Figure 12This is a schematic diagram of the module structure of another embodiment of the installation management device for mini-program applications provided in this specification. The device can immediately be the user terminal corresponding to the manufacturer in the above embodiment, such as Figure 12 As shown, the mini-program application installation management device provided in this specification may include: a registration request module 121, a mini-program service request module 122, a mini-program application installation module 123, and an activation request module 124, wherein:

[0140] The registration request module 121 is used to send a registration request to the device management platform and receive a registration success message returned by the device management platform after the registration review is passed;

[0141] The mini-program service request module 122 is configured to send a mini-program service request to the device management platform and receive a mini-program service returned by the device management platform based on the mini-program service request;

[0142] The mini-program application installation module 123 is used to add the mini-program service to the mini-program application and install the mini-program application including the mini-program service to the corresponding hardware device;

[0143] The activation request module 124 is used to send an application activation request to the device management platform to activate the mini-program application in the hardware device. The application activation request includes the signature information of the hardware device, so that the device management platform activates the mini-program application in the hardware device based on the application activation request.

[0144] The installation and management device for mini-program applications provided in the embodiments of this specification can provide a mini-program application service with multiple mini-programs for hardware devices. The manufacturer of the hardware device can obtain multiple mini-programs returned by the device management platform by sending a binding mini-program service request to the device management platform, and select the mini-programs they need from them. The device management platform can uniformly manage the hardware devices on which the mini-program applications are installed, ensure the legitimacy of the hardware devices running the mini-program applications, and the hardware devices do not need to adapt to the environments of different applications. The mini-program services within the mini-program applications can be changed at any time without relying on device upgrades. The hardware devices also do not need to install applications one by one, but directly integrate multiple mini-programs into one application and provide it to the manufacturer of the hardware device, so that the hardware device can have mini-programs for multiple services. The operation is simple, which reduces the application configuration time, manpower and cost of the hardware device, and can also reduce the memory space occupied by the application in the hardware device.

[0145] Based on the above embodiments, in some embodiments of this specification, the device further includes a signature module, which is used to:

[0146] After successful registration, upload the product information, device information and public key of the hardware device corresponding to the hardware device to the device management platform;

[0147] The signature information is obtained using the following method:

[0148] The product information and device information of the hardware device are encrypted using the private key corresponding to the public key of the hardware device to obtain the signature information.

[0149] The embodiments of this specification utilize end-to-end (server to client) public and private key management. When the hardware manufacturer registers and uploads the device information of the hardware device, it uploads the public key corresponding to the hardware device. When the hardware device is dynamically running, the signature information of the device information is used for authentication in the pre-process of running the mini-program application, thereby ensuring the legitimacy of the device before running the mini-program application.

[0150] Based on the above embodiments, in some embodiments of this specification, the apparatus further includes calling an application binding module, which is configured to:

[0151] Sending a calling application binding request to the device management platform, wherein the calling application binding request includes the calling application to be bound, so that the device management platform binds the calling application to the hardware device according to the calling application binding request;

[0152] The product information and device information are uploaded in batches through the calling application.

[0153] It should be noted that the above-mentioned device may also include other implementations according to the description of the corresponding method embodiment. Specific implementations can refer to the description of the corresponding method embodiment above, and will not be described in detail here.

[0154] The embodiments of this specification also provide an installation management device for a mini-program application, including: at least one processor and a memory for storing processor-executable instructions, wherein when the processor executes the instructions, the information recommendation data processing method of the above embodiment is implemented, such as:

[0155] Review the registration information in the registration request uploaded by the user terminal, and return a registration success message if the review passes;

[0156] Receiving a mini-program service binding request sent by the user terminal after successful registration, and returning a corresponding mini-program service according to the mini-program service binding request, so that the user terminal installs the mini-program application including the mini-program service into the corresponding hardware device;

[0157] Receive an application activation request for activating a mini-program application in a hardware device, wherein the application activation request includes signature information of the hardware device;

[0158] The hardware device is verified according to the application activation request, and if the verification passes, the mini-program application in the hardware device is activated.

[0159] Or, send a registration request to the device management platform and receive a registration success message returned by the device management platform after the registration review is passed;

[0160] Sending a mini-program service binding request to the device management platform, and receiving a mini-program service returned by the device management platform based on the mini-program service binding request;

[0161] Adding the mini-program service to a mini-program application, and installing the mini-program application including the mini-program service to a corresponding hardware device;

[0162] An application activation request for activating the mini-program application in the hardware device is sent to the device management platform, where the application activation request includes signature information of the hardware device, so that the device management platform activates the mini-program application in the hardware device based on the application activation request.

[0163] The embodiments of this specification also provide an installation management system for mini-program applications, comprising: a device management platform, a user terminal, and hardware devices; wherein the device management platform includes at least one processor and a memory for storing processor-executable instructions, and the processor executes the method executed by the device management platform to provide a mobile application including multiple mini-programs;

[0164] The user terminal is used to include at least one processor and a memory for storing processor executable instructions. When the processor executes the instructions, it implements the method executed by the user terminal corresponding to the manufacturer to request to call the mobile application including multiple small programs provided by the device management platform, and install the mobile application into the hardware device.

[0165] It should be noted that the above-mentioned device and system may also include other implementations according to the description of the method embodiment. Specific implementations can refer to the description of the relevant method embodiment and will not be described in detail here.

[0166] The installation and management device for the mini-program application provided in this specification can also be used in a variety of data analysis and processing systems. The system or server or terminal or device can be a separate server, or it can include a server cluster, system (including distributed system), software (application), actual operation device, logic gate circuit device, quantum computer, etc. that uses one or more of the methods or one or more embodiments of the system or server or terminal or device of this specification and is combined with a terminal device of necessary implementation hardware. The detection system for checking the difference data may include at least one processor and a memory that stores computer-executable instructions, and the processor implements the steps of the method described in any one or more of the above embodiments when executing the instructions.

[0167] The method embodiments provided in the embodiments of this specification can be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Taking running on a server as an example, Figure 13 This is a hardware structure block diagram of the installation management server of the mini-program application in one embodiment of this specification. The computer terminal can be the installation management server of the mini-program application or the installation management device of the mini-program application in the above embodiment. Figure 13 The server 10 shown may include one or more (only one is shown in the figure) processors 100 (the processor 100 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a non-volatile memory 200 for storing data, and a transmission module 300 for communication functions. It will be understood by those skilled in the art that Figure 13 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 13 More or fewer components shown in the figure may also include other processing hardware, such as a database or multi-level cache, GPU, or other hardware with Figure 13 Different configurations shown.

[0168] The non-volatile memory 200 can be used to store software programs and modules of application software, such as the program instructions / modules corresponding to the installation management method of the mini-program application in the embodiment of this specification. The processor 100 executes various functional applications and resource data updates by running the software programs and modules stored in the non-volatile memory 200. The non-volatile memory 200 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the non-volatile memory 200 may further include a memory remotely located relative to the processor 100, and these remote memories can be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a network, a mobile communication network, and combinations thereof.

[0169] The transmission module 300 is used to receive or send data via a network. Specific examples of the aforementioned network may include a wireless network provided by a communications provider of a computer terminal. In one embodiment, the transmission module 300 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission module 300 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0170] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0171] The methods or devices described in the above embodiments of this specification can implement business logic through computer programs and record them on storage media. The storage media can be read and executed by a computer to achieve the effects of the solutions described in the embodiments of this specification, such as:

[0172] Review the registration information in the registration request uploaded by the user terminal, and return a registration success message if the review passes;

[0173] Receiving a mini-program service binding request sent by the user terminal after successful registration, and returning a corresponding mini-program service according to the mini-program service binding request, so that the user terminal installs the mini-program application including the mini-program service into the corresponding hardware device;

[0174] Receive an application activation request for activating a mini-program application in a hardware device, wherein the application activation request includes signature information of the hardware device;

[0175] The hardware device is verified according to the application activation request, and if the verification passes, the mini-program application in the hardware device is activated.

[0176] Or, send a registration request to the device management platform and receive a registration success message returned by the device management platform after the registration review is passed;

[0177] Sending a mini-program service binding request to the device management platform, and receiving a mini-program service returned by the device management platform based on the mini-program service binding request;

[0178] Adding the mini-program service to a mini-program application, and installing the mini-program application including the mini-program service to a corresponding hardware device;

[0179] An application activation request for activating the mini-program application in the hardware device is sent to the device management platform, where the application activation request includes signature information of the hardware device, so that the device management platform activates the mini-program application in the hardware device based on the application activation request.

[0180] The storage medium may include a physical device for storing information, typically digitizing the information and then storing it in a medium utilizing electrical, magnetic, or optical means. Examples of such storage media include: devices that use electrical energy to store information, such as various types of memory, such as RAM and ROM; devices that use magnetic energy to store information, such as hard disks, floppy disks, magnetic tapes, magnetic core memories, bubble memories, and USB flash drives; and devices that use optical means to store information, such as CDs or DVDs. Of course, there are also other types of readable storage media, such as quantum memories and graphene memories.

[0181] The installation and management method or device for the above-mentioned mini-program application provided in the embodiments of this specification can be implemented by a processor in a computer executing corresponding program instructions, such as using the C++ language of the Windows operating system on a PC, a Linux system, or other systems such as Android and iOS system programming languages on a smart terminal, as well as processing logic based on a quantum computer.

[0182] It should be noted that the device, computer storage medium, and system described above in the specification may also include other implementation methods according to the description of the relevant method embodiments. The specific implementation methods can refer to the description of the corresponding method embodiments and will not be described one by one here.

[0183] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences between the other embodiments. In particular, the hardware + program embodiments are generally similar to the method embodiments, so their description is relatively simple. For relevant portions, reference can be made to the description of the method embodiments.

[0184] The embodiments of this specification are not limited to those that must comply with industry communication standards, standard computer resource data update and data storage rules, or the situations described in one or more embodiments of this specification. Certain industry standards or slightly modified implementation plans based on the implementation described in the embodiments using custom methods or embodiments can also achieve the same, equivalent, or similar implementation effects as the above embodiments, or the expected implementation effects after deformation. The embodiments obtained by applying these modified or deformed data acquisition, storage, judgment, processing methods, etc. can still fall within the scope of the optional implementation plans of the embodiments of this specification.

[0185] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD through their own programming, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0186] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules that implement the method and structures within the hardware component.

[0187] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, an in-vehicle human-computer interaction device, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0188] Although one or more embodiments of this specification provide method operation steps as described in the embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the device or terminal product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed resource data update environment). The term "comprise", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or equipment including a series of elements includes not only those elements, but also includes other elements that are not clearly listed, or also includes elements inherent to such process, method, product or equipment. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or equipment including the elements. Words such as first and second are used to represent names and do not represent any particular order.

[0189] For the convenience of description, the above devices are described in terms of functions divided into various modules. Of course, when implementing one or more of the present specifications, the functions of each module can be implemented in the same or multiple software and / or hardware, or the module that implements the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0190] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable resource data update device to produce a machine, so that the instructions executed by the processor of the computer or other programmable resource data update device generate instructions for implementing the process in the flowchart. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0191] These computer program instructions can also be stored in a computer readable memory that can guide a computer or other programmable resource data update device to work in a specific manner, so that the instructions stored in the computer readable memory produce a product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0192] These computer program instructions can also be loaded onto a computer or other programmable resource data updating device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0193] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0194] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0195] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, graphene storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0196] Those skilled in the art will appreciate that one or more embodiments of this specification may be provided as a method, system, or computer program product. Thus, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0197] One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote devices connected via a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0198] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, since the system embodiments are generally similar to the method embodiments, their description is relatively simple, and relevant parts can be referenced to the partial description of the method embodiments. Throughout this specification, reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with that embodiment or example are included in at least one embodiment or example of this specification. In this specification, the schematic representations of these terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and integrate the different embodiments or examples, and features of different embodiments or examples, described in this specification, without conflict.

[0199] The foregoing description is merely an example of one or more embodiments of this specification and is not intended to limit the one or more embodiments of this specification. Those skilled in the art will appreciate that various modifications and variations of one or more embodiments of this specification are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of this specification are intended to be included within the scope of the claims.

Claims

1. A method for managing the installation of a mini-program application, the method comprising: Receiving a calling application binding request sent by a user terminal, wherein the calling application binding request includes a calling application and a hardware device to be bound; Binding the calling application to the hardware device according to the calling application binding request, and receiving product information and device information of the hardware device uploaded in batches by the user terminal through the calling application; receiving a mini-program service binding request sent by the user terminal through the calling application, wherein the mini-program service binding request includes the hardware device and multiple mini-program services to be bound; The corresponding plurality of mini-program services are returned according to the mini-program service binding request, so that the user terminal installs the mini-program application including the plurality of mini-program services into the hardware device.

2. The method according to claim 1, before receiving the application binding request sent by the user terminal, the method further comprises: Review the registration information in the registration request uploaded by the user terminal, and return a registration success message if the review is passed; After successful registration, the product information and device information of the hardware devices uploaded in batches by the user end are reviewed.

3. The method according to claim 1, after returning the corresponding mini-program service according to the bound mini-program service request, the method further comprises: Receive an application activation request for activating a mini-program application in a hardware device, wherein the application activation request includes signature information of the hardware device; Obtain the product information and device information of the hardware device corresponding to the application activation request, match the obtained product information and device information with the product information and device information uploaded by the user terminal, and if the match is successful, verify the signature information. If the verification passes, it is determined that the hardware device has passed the verification and activate the mini program application in the hardware device.

4. The method of claim 3, before receiving an application activation request for activating the mini-program application in the hardware device, the method further comprises: Receive the public key of the hardware device uploaded by the user terminal; wherein the signature information of the hardware device is encrypted information obtained by encrypting the device information and product information of the hardware device using the private key corresponding to the public key; The verifying the signature information includes: The public key of the hardware device is used to decrypt and verify the signature information. If the decryption is successful, the signature verification is passed.

5. The method of claim 1, further comprising: Generate a unique device identifier for the hardware device based on the device identifier in the device information of the hardware device uploaded by the user terminal and the startup information of the hardware device; The unique device identifier is associated with the device identifier in the device information of the hardware device.

6. A method for managing the installation of a mini-program application, comprising: Sending a calling application binding request to a device management platform, wherein the calling application binding request includes a calling application and a hardware device to be bound, so that the device management platform binds the calling application to the hardware device according to the calling application binding request; Uploading the product information and device information of the hardware devices in batches to the device management platform through the calling application; Sending a mini-program service binding request to the device management platform, and receiving multiple mini-program services returned by the device management platform based on the mini-program service binding request; The plurality of mini-program services are added to the mini-program application, and the mini-program application including the mini-program services is installed on the corresponding hardware device according to the product information and device information of the hardware device in the mini-program service binding request.

7. The method of claim 6, further comprising, after installing the mini-program application including the mini-program service into the corresponding hardware device: An application activation request for activating the mini-program application in the hardware device is sent to the device management platform, where the application activation request includes signature information of the hardware device, so that the device management platform activates the mini-program application in the hardware device based on the application activation request.

8. The method of claim 6, further comprising: Access the device management platform through the calling application to edit and manage the uploaded product information and equipment.

9. The method according to claim 6, before sending the application binding request to the device management platform, the method further comprises: Send a registration request to the device management platform, and receive a registration success message returned by the device management platform after the registration review is passed.

10. A device for managing the installation of a mini-program application, comprising: At least one processor and a memory for storing processor-executable instructions, wherein when the processor executes the instructions, the method according to any one of claims 1 to 5 or 6 to 9 is implemented.

11. An installation management system for mini-program applications, comprising: A device management platform, a user terminal, and a hardware device; wherein the device management platform includes at least one processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, it implements the method according to any one of claims 1 to 5, for providing a mini-program application including multiple mini-programs and managing the hardware devices that call the mini-program application; The user terminal includes at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the method described in any one of claims 6 to 9 to request to call a mini-program application including multiple mini-programs provided by the device management platform, and install the mini-program application into the hardware device.

Images