CN111651734A

CN111651734A - Installation management method, device, equipment and system for applet

Info

Publication number: CN111651734A
Application number: CN202010460387.4A
Authority: CN
Inventors: 刘静; 王少龙; 边炀凯
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-05-27
Filing date: 2020-05-27
Publication date: 2020-09-11
Anticipated expiration: 2040-05-27
Also published as: WO2021238954A1; CN114896570A; CN111651734B

Abstract

The present specification provides an installation management method, an installation management device, an installation management apparatus, and an installation management system for an applet, where the method can provide an applet service having a plurality of applets for a hardware device, and a device management platform can perform unified management on the hardware device where the applet is installed, thereby ensuring the validity of the hardware device running the applet application, and the hardware device does not need to adapt to different application environments, and the applet service in the applet application can be changed at any time without depending on device upgrade.

Description

Installation management method, device, equipment and system for applet

Technical Field

The present specification belongs to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a system for installation management of an applet application.

Background

With the development of computer technology, more and more APPs (applications) with different functions are developed and used, and many hardware terminals need to download APPs with different functions, such as: the vehicle-mounted terminal may download an installation map navigation APP, a weather forecast APP, a song listening type APP, a violation query type APP and the like. These APPs need to be downloaded and installed by manufacturers or users one by one, are relatively cumbersome to operate, require hardware devices to adapt to the installation environments of various APPs, and do not have uniform management for the hardware devices in which the applications are installed.

Disclosure of Invention

An object of the embodiments of the present specification is to provide a method, an apparatus, a device, and a system for installation management of an applet, which improve accuracy and efficiency of installation management of the applet.

In a first aspect, an embodiment of the present specification provides an installation management method for an applet, where the method includes:

verifying the registration information in the registration request uploaded by the user terminal, and if the verification is passed, returning registration success information;

receiving a binding applet service request sent by the user terminal after the registration is successful, and returning corresponding applet service according to the binding applet service request so that the user terminal installs the applet application including the applet service into corresponding hardware equipment;

receiving an application activation request for activating an applet application in a hardware device, wherein the application activation request comprises signature information of the hardware device;

and verifying the hardware equipment according to the application activation request, and activating the applet application in the hardware equipment if the verification is passed.

In a second aspect, the present specification provides a method for installation management of an applet, the method comprising:

sending a registration request to an equipment management platform, and receiving registration success information returned by the equipment management platform after the registration audit is passed;

sending an applet binding service request to the equipment management platform, and receiving an applet service returned by the equipment management platform based on the applet binding service request;

adding the applet service to an applet application, and installing the applet application including the applet service into a corresponding hardware device;

sending an application activation request for activating an applet application in a hardware device to the device management platform, wherein the application activation request includes signature information of the hardware device, so that the device management platform activates the applet application in the hardware device based on the application activation request.

In a third aspect, the present specification provides an installation management apparatus for an applet, comprising:

the registration auditing module is used for auditing the registration information in the registration request uploaded by the user terminal, and if the audit is passed, the registration success information is returned;

the applet service binding module is used for receiving an applet binding service request sent by the user terminal after the registration is successful, and returning corresponding applet service according to the applet binding service request so that the user terminal can install the applet application including the applet service into corresponding hardware equipment;

an activation request receiving module, configured to receive an application activation request for activating an applet application in a hardware device, where the application activation request includes signature information of the hardware device;

and the application activation module is used for verifying the hardware equipment according to the application activation request, and activating the applet application in the hardware equipment if the verification is passed.

In a fourth aspect, the present specification provides an installation management apparatus for an applet, comprising:

the registration request module is used for sending a registration request to the equipment management platform and receiving registration success information returned by the equipment management platform after the registration audit is passed;

the applet service request module is used for sending an applet binding service request to the equipment management platform and receiving the applet service returned by the equipment management platform based on the applet binding service request;

the applet application installation module is used for adding the applet service into the applet application and installing the applet application comprising the applet service into the corresponding hardware equipment;

an activation request module, configured to send an application activation request for activating an applet application in a hardware device 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 applet application in the hardware device based on the application activation request.

In a fifth aspect, an embodiment of the present specification provides an installation management device for an applet, including at least one processor and a memory for storing processor-executable instructions, where the processor executes the instructions to implement the installation management method for an applet described in the first aspect or the second method.

In a sixth aspect, an embodiment of the present specification provides an installation management system for an applet, including: the system comprises an equipment management platform, a user terminal and hardware equipment; wherein the device management platform comprises at least one processor and a memory for storing processor-executable instructions, and the processor, when executing the instructions, implements the method of the first aspect for providing a mobile application comprising a plurality of applets;

the user terminal is configured to include at least one processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the method according to the second aspect is implemented to request to invoke a mobile application provided by the device management platform and including a plurality of applets, and install the mobile application into the hardware device.

The installation management method, apparatus, device and system for an applet provided in this specification can provide an applet service having a plurality of applets for a hardware device, and a manufacturer of the hardware device can obtain a plurality of applets returned by a device management platform by sending an applet binding service request to the device management platform, and install an applet application including the plurality of applets in the hardware device. The device management platform can uniformly manage the hardware device for installing the applet application, and ensure the legality of the hardware device for running the applet application so as to ensure the safety of the applet application service. And the hardware equipment does not need to adapt to the environments of different applications, and the applet service in the applet application can be changed at any time without depending on equipment upgrading. The hardware equipment also does not need to install the application programs one by one, and a plurality of small programs are directly integrated in one application program and provided for manufacturers of the hardware equipment, so that the hardware equipment can have the small programs with various services, the operation is simple, the application configuration time, the labor and the cost of the hardware equipment are reduced, and the memory space occupied by the application programs in the hardware equipment can be reduced.

Drawings

In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic flowchart of an embodiment of an installation management method for an applet provided in an embodiment of the present specification;

FIG. 2 is a flow diagram illustrating installation management of applet applications in yet another embodiment of the present description;

FIG. 3 is a flow chart of vendor registration in an embodiment of the present specification;

FIG. 4 is a flow diagram illustrating device registration in some embodiments of the present description;

FIG. 5 is a flow diagram illustrating public key upload in some embodiments of the present description;

FIG. 6 is a flow diagram illustrating application binding in some embodiments of the present description;

FIG. 7 is a schematic flow diagram of a batch upload of devices in some embodiments of the present description;

FIG. 8 is a schematic flow chart illustrating authentication of a device in some embodiments of the present description;

FIG. 9 is a flowchart of a method for managing installation of an applet at a terminal side among users in some embodiments of the present disclosure;

FIG. 10 is a flow diagram illustrating installation of an applet by a vendor in some embodiments of the present description;

FIG. 11 is a block diagram of an installation management apparatus for an applet, according to an embodiment of the present disclosure;

fig. 12 is a block diagram illustrating a module configuration of another embodiment of an installation management apparatus for an applet provided in the present specification;

fig. 13 is a block diagram of a hardware configuration of an installation management server of an applet in one embodiment of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.

With the development of computers, the variety of mobile application programs, i.e., mobile applications, is increasing, different mobile applications can generally provide different services, and if a user needs multiple services, different mobile applications need to be downloaded and installed. In some embodiments of the present description, a method may be provided for providing a hardware device with a mobile application including a plurality of applets, i.e., an applet, and all applets on the mobile application may be used only by installing one mobile application on the hardware device. The applet can be understood as an application which can be used without downloading and installation, can be hosted in the mobile application, does not need independent development, and can be directly used in the mobile application by a user, and different applets can provide different services, and each applet can meet a simpler basic application.

Some embodiments of the present disclosure may provide a device management platform, which may be a network platform provided by applications with multiple applets (e.g., payment applications with multiple functions, social applications, etc.), and the application may provide the capability of providing multiple applets to the outside, that is, multiple applets may be included in the device management platform. A manufacturer or a processing manufacturer of hardware equipment can send an applet binding service request of mobile application to an equipment management platform through a user terminal of the manufacturer or the processing manufacturer, the equipment management platform can return a plurality of applets for the manufacturer according to the received applet binding service request, and the manufacturer can select the needed applets through the user terminal. The device management platform can add the applet selected by the manufacturer to the mobile application and return the applet to the manufacturer, and the manufacturer can install the mobile application into the hardware device. The hardware device can provide all applet services in the mobile application for the consumer, and the hardware device can be a smart phone, a tablet computer, a vehicle-mounted device, an intelligent wearable device, an intelligent robot and the like. The device management platform can also uniformly manage the hardware devices applying for calling the applet applications, and can lay an important foundation for subsequent device dimension wind control, penalty and the like.

Fig. 1 is a flowchart illustrating an embodiment of an installation management method for an applet provided in an embodiment of this specification. Although the present specification provides the method steps or apparatus structures as shown in the following examples or figures, more or less steps or modules may be included in the method or apparatus structures based on conventional or non-inventive efforts. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution order of the steps or the block structure of the apparatus is not limited to the execution order or the block structure shown in the embodiments or the drawings of the present specification. When the described method or module structure is applied to a device, a server or an end product in practice, the method or module structure according to the embodiment or the figures may be executed sequentially or in parallel (for example, in a parallel processor or multi-thread processing environment, or even in an implementation environment including distributed processing and server clustering).

In a specific embodiment, as shown in fig. 1, in an embodiment of the installation management method for an applet provided in this specification, the method may be applied to a device management platform side, where the device management platform may be a terminal such as a computer, a tablet computer, and a server, and the method may include the following steps:

and 102, verifying the registration information in the registration request uploaded by the user terminal, and if the verification is passed, returning registration success information.

In a specific implementation process, the user terminal may be a terminal corresponding to a manufacturer that produces, processes, or sells the hardware device, and may be a smart phone, a tablet computer, a computer, or the like, and if the manufacturer wants to use the applet service provided by the device management platform in the embodiment of the present disclosure, the manufacturer may first send a registration request to the device management platform through the corresponding user terminal. The registration request may include manufacturer information (e.g., name, address, website, business license, contact person, contact phone, contact mailbox, etc.), and the device management platform may perform service admission audit on the registration information provided by the manufacturer, and audit related qualification information of the manufacturer, such as: whether the manufacturer is legal or not is audited, whether the information filled by the manufacturer is accurate or not, the production capacity or the holding capacity of hardware equipment of the manufacturer, whether the type of the hardware equipment can use the applet application or not and whether the requirements for accessing the applet service are met or not are checked. Other content such as: and checking whether a CPU (central processing unit), a memory, a version and the like of the hardware equipment conform to the installation condition of the mobile application and whether the registration information is accurate and reliable and the like. And after the verification is passed, the equipment management platform returns registration success information to the user terminal, namely the manufacturer successfully registers in the equipment management platform.

In some embodiments of this specification, after the manufacturer successfully resides in the device management platform, product information, device information, and the like may be uploaded in the device management platform, and the product information may include product types such as: the system comprises an automobile, a vehicle, a refrigerator, a television, a watch and the like, and can also upload the production capacity, the shipment volume and the like of different types of products, and the product information of different types can correspond to a product identification. After the product information application is completed, the manufacturer may also create a model in the corresponding product type, that is, upload the device information of some devices under the product type, and the device information may indicate information of a specific device, such as: the device information of a certain type of automobile in an automobile manufacturer may include a device identifier, device parameters of the device, and the like. Through new data models and flows of manufacturers, equipment, models and the like, basic information, agent model information and specific hardware equipment marking information of hardware equipment manufacturers are all collected and established in an equipment management platform, and a foundation is laid for the control and punishment of subsequent equipment dimensions.

And 104, receiving a binding applet service request sent by the user terminal after the registration is successful, and returning the corresponding applet service according to the binding applet service request, so that the user terminal installs the applet application including the applet service into the corresponding hardware equipment.

In a specific implementation process, the device management platform may be a network platform provided by an application with multiple applets (some payment applications, social applications, etc. with multiple servlets), may include multiple applets in the application, and may be directly managed by the application without additional development and maintenance of the applets. After the vendor successfully hosts, a binding applet service request may be sent to the device management platform, i.e., a request to invoke an applet service for the hardware device. The bound applet service request may include the bound applet service and corresponding hardware device, such as: a map navigation applet, a music play applet, a violation query applet, etc. may be requested for the onboard equipment of a particular car. The equipment management platform can return the applet service requested to be bound by the manufacturer after receiving the applet binding service request sent by the manufacturer, and the manufacturer can integrate the applet service returned by the equipment management platform into the applet application and install the applet application into the corresponding hardware equipment. The applet service in the embodiment of the present specification may be understood as an applet, the applet application is an application integrated with a plurality of applet services, may be understood as an applet engine, and may be an application running in a hardware device, and may also be understood as an application package, where: APK (Android application package), and the like.

Step 106, receiving an application activation request for activating an applet application in a hardware device, where the application activation request includes signature information of the hardware device.

In a specific implementation process, after an applet is installed in a hardware device, the applet needs to be activated to enable normal use. The application activation request of the applet can be triggered by clicking the applet application in the login hardware device, or the application activation request for activating a certain applet application can be directly sent to the device management platform. The application activation request in the embodiment of this specification may include signature information of the hardware device, where the signature information may be encryption information for performing encryption operation on device information of the hardware device, and the signature information may be used to perform security verification on the hardware device, so as to prevent device information of a manufacturer from being leaked, and other devices may also perform applet operation through the same parameter.

And 108, verifying the hardware equipment according to the application activation request, and activating the applet application in the hardware equipment if the verification is passed.

In a specific implementation process, after receiving the application activation request, the device management platform may verify the hardware device based on the application activation request, for example: the signature verification method comprises the steps of verifying whether a request sent by a manufacturer of hardware equipment is verified in a manner of verifying signature information in an application activation request, carrying out legal verification on equipment information, manufacturer information and the like in the application activation request, and activating the applet application in the hardware equipment after the verification is passed.

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

when an application activation request is received, acquiring product information and equipment information of hardware equipment corresponding to the application activation request, matching the acquired product information and equipment information with the product information and equipment information uploaded by the user terminal, if the matching is successful, checking the signature information, and if the signature passes, determining that the hardware equipment passes the verification.

In a specific implementation process, when an application activation request is received, product information and device information of hardware equipment corresponding to the application activation request can be acquired, the acquired product information and device information are matched with the product information and device information uploaded by the user terminal, whether the product information and device information of the hardware equipment corresponding to the application activation request are in the equipment management platform or not is judged, if yes, matching is successful, signature verification is carried out on signature information, if the signature verification is passed, the hardware equipment is determined to be verified, and the applet application in the hardware equipment is activated. Of course, other information of the hardware device may also be checked, and the embodiments of the present specification are not particularly limited. In the embodiment of the specification, the hardware device can be verified to be a legal device registered in the device management platform through verification of the product information and the device information of the hardware device, and the validity of the hardware device for activating the applet application can be more accurately determined by combining verification of the signature information, so that the safety of the installation device of the applet application is improved.

The installation management method for an applet provided in this specification may provide an applet service having multiple applets for a hardware device, and a manufacturer of the hardware device may obtain multiple applets returned by a device management platform by sending an applet binding service request to the device management platform, and install an applet including the multiple applets in the hardware device. The device management platform can uniformly manage hardware devices for installing the applet application, namely installation devices for the applet application, the legality of the hardware devices for running the applet application is guaranteed, the hardware devices do not need to adapt to environments of different applications, and the applet service in the applet application can be changed at any time without depending on device upgrading. The hardware equipment also does not need to install the application programs one by one, and a plurality of small programs are directly integrated in one application program and provided for manufacturers of the hardware equipment, so that the hardware equipment can have the small programs with various services, the operation is simple, the application configuration time, the labor and the cost of the hardware equipment are reduced, and the memory space occupied by the application programs in the hardware equipment can be reduced.

On the basis of the above embodiments, in some embodiments of the present specification, the method further includes:

after the registration is successful, receiving a public key of the hardware equipment uploaded by the user terminal;

the signature information of the hardware equipment is encrypted information obtained by encrypting the equipment information and the product information of the hardware equipment by using a private key corresponding to the public key;

the verifying the hardware device according to the application activation request comprises:

and decrypting and checking the signature information by adopting the public key of the hardware equipment, and if the decryption is successful, checking the signature to pass.

In particular implementations, the device management platform may provide a software Development kit such as an SDK (software Development kit) for the vendor to use to generate a pair of public and private keys. The private key may be used to perform encryption signature on device information, product information, and the like of the hardware device, such as: and encrypting the product identification and the equipment identification of the hardware equipment by using a private key to obtain the signature information of the hardware equipment. Each hardware device needs to be re-signed, the same calling parameters cannot be used, the device signature mode can be used for signature adding through the generated RSA2 private key, and the character set can be selected to be UTF-8. After the manufacturer resides in the device management platform, product information, device information and the like of the hardware device needing to use the applet application service can be uploaded in the device management platform, and a public key of the hardware device can be uploaded through the user terminal. When an application activation request is sent to the equipment management platform, signature information encrypted by a private key of the hardware equipment to the hardware equipment can be sent to the equipment management platform together, when the hardware equipment is verified by the equipment management platform, the public key of the hardware equipment uploaded by common knowledge can be used for decrypting and verifying the signature information, if the decryption is successful, the signature verification is passed, and other information of the hardware equipment is continuously verified.

It should be noted that the same manufacturer may have multiple products, and each product may have multiple series of hardware devices, that is, the same manufacturer may have multiple hardware devices, and the public key and the private key used by different hardware devices may be the same, that is, one manufacturer has a pair of public key and private key for signing device information of its named hardware device. Different hardware devices can also have different public keys and private keys, such as: the manufacturer can use the information of different hardware devices to generate a pair of public key and private key for different hardware devices by using an encryption algorithm, and conduct 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 the product information of the hardware device, and the device management platform needs to use the public key corresponding to the hardware device to decrypt and check the signature.

In the embodiment of the specification, the end-to-end (from the server side to the client side) public and private key management and control is utilized, when the hardware manufacturer registers and uploads the device information of the hardware device, the public key corresponding to the hardware device is uploaded, and when the hardware device runs dynamically, the signature information of the device information is used for authentication in the pre-process of running the applet application, so that the legality of the device before the applet application is run is guaranteed.

On the basis of the foregoing embodiments, in some embodiments of the present specification, the method may further include:

generating a unique device identifier for the hardware device based on a device identifier in the device information of the hardware device uploaded by the user terminal and the start information of the hardware device;

and associating the unique equipment identifier with the equipment identifier in the equipment information of the hardware equipment.

In a specific implementation process, when uploading the device information, the manufacturer may upload the device identifier of the hardware device, such as: a product Serial Number (e.g., SN, Serial Number) or a mobile equipment Identity (e.g., IMEI), where the equipment identities are defined or uploaded by vendors, the equipment identities of different vendors may be the same, and the equipment Identity has no direct relationship with an actual operating environment, and the equipment identities in the equipment management platform may be duplicated. The equipment management platform can also generate an equipment unique identifier for the hardware equipment according to the equipment identifier in the equipment information of the hardware equipment uploaded by a manufacturer through the user terminal and the starting information when the hardware equipment is started, and associates the equipment unique identifier with the equipment identifier in the equipment information of the hardware equipment, so that the uniqueness of the equipment identifier in the global equipment manufacturer is established, the uniqueness of running the small programs by a single manufacturer and a single equipment is ensured, the small programs cannot be run and opened by different equipment through the simulation of the same request parameters, and the isolation and independence between the hardware equipment are ensured. The start information may include environment information when the hardware device is started, such as: time, device start parameters, geographic location, etc., and the embodiments of the present specification are not particularly limited.

On the basis of the foregoing embodiments, in some embodiments of the present specification, the start information includes start time and a start random number of the hardware device;

generating a device unique 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 start information of the hardware device, including:

and performing hash calculation on the equipment identifier, the starting time and the starting random number to generate the unique identifier of the hardware equipment generating equipment.

In a specific implementation process, in some embodiments of the present specification, an operating environment of a hardware device may be used as a parameter generated by a unique device identifier, that is, the start information may include start time and a start random number of the hardware device, where the start random number is a random number and is used as a parameter for starting the hardware device. After the hash calculation is performed on the device identifier of the hardware device uploaded by the manufacturer, the start time of the hardware device, and the start random number, the hash calculation result can be used as the unique device identifier of the hardware device. The hash function used for hash calculation may be selected according to actual needs, and embodiments of the present specification are not specifically limited.

In the embodiment of the description, the unique device identifier of the hardware device is generated by combining the operating environment of the hardware device and the device identifier, and is associated with the device identifier in the device information of the hardware device, so that the uniqueness of the device identifier in a global device manufacturer is established, the uniqueness of running applets by a single manufacturer and a single device is ensured, the applets cannot be run and opened by simulation of the same request parameter between different devices, and the isolation and independence between the hardware devices are ensured.

On the basis of the foregoing embodiments, in some embodiments of the present specification, the verifying the hardware device according to the application activation request further includes:

and verifying the unique equipment identifier of the hardware equipment, and if the verification is successful, determining that the hardware equipment passes the verification.

In a specific implementation process, when the hardware device is verified, the device unique identifier of the hardware device may also be verified, such as: whether the device identifier in the application activation request has the associated device unique identifier in the device platform can be verified, and if yes, the verification is successful. The device unique identifier in the application activation request may also be checked to determine whether the device unique identifier is in the device management platform, and if the device unique identifier exists in the application activation request, the checking is successful, or other ways are used for checking, and the embodiment of the present specification is not particularly limited.

In the embodiment of the specification, in the pre-process of running the applet, the authentication is carried out through the equipment information and the equipment unique identifier, so that the legality of the hardware equipment before the applet is run is guaranteed.

receiving a calling application binding request sent by the user terminal, wherein the calling application binding request comprises a calling application to be bound;

binding the calling application for the hardware equipment according to the calling application binding request;

and receiving product information and equipment information uploaded by the user terminal in batch through the calling application.

In a specific implementation process, considering that a hardware device manufacturer may produce tens of thousands to hundreds of thousands of devices in batch, in this specification embodiment, a batch upload application capability interface may be provided, and an application identifier needs to be opened for a call interface. The calling application is an application type, which may be an applet, a web application, a mobile application, etc. The method comprises the steps that after receiving a binding calling application request sent by a manufacturer through a user terminal, the equipment management platform can bind calling application for the manufacturer, the manufacturer can be connected to an interface of the equipment management platform through the calling application, the interface is accessed into the equipment management platform, and the binding applet service request is further sent to the equipment management platform. Such as: after the bound calling application is accessed to the device management platform, the device information of the hardware device needing to install the applet application can be registered in the device management platform, and after the registration is successful, a calling binding applet service request can be initiated for the hardware device. Each calling application can correspond to an application identifier, the application identifier can be accessed into the equipment management platform, a manufacturer can perform data interaction with the equipment management platform through the calling application, calling and installation of the applet application are achieved, product information, equipment information and the like of the hardware equipment can be uploaded in batch through the calling application, and the uploaded hardware equipment can be edited and managed through the calling application.

In addition, the same hardware device may bind one or more calling applications, each of which may send a request to bind a different applet service for the hardware device.

In the embodiment of the specification, the batch uploading of the device information is realized by binding and calling the application, and the data processing efficiency of the applet application is accelerated.

Fig. 2 is a schematic flow chart of installation management of an applet in another embodiment of this specification, and a process of installation management of an applet in this embodiment of this specification is specifically described below with reference to fig. 2:

(1) and the hardware equipment manufacturer resides in the equipment management platform. Fig. 3 is a schematic diagram of a process of vendor registration in an embodiment of this specification, and as shown in fig. 3, when a vendor registers in a device management platform, the vendor needs to provide complete vendor information (vendor registration account ID, vendor name, management address, enterprise official network, enterprise business license, main business product, contact person, contact phone, contact mailbox) and other information, the device management platform performs business admission audit on the information provided by the vendor, and the terminal platform audits the relevant qualification information of the vendor, and has a condition for accessing an applet application. After the manufacturer enrollment audit is successful, the manufacturer enrollment state can be updated in the device management platform, and during the audit period, the manufacturer can also inquire the audit state in the device management platform.

(2) Fig. 4 is a schematic flow diagram of device registration in some embodiments of the present description, where after registration is completed by a manufacturer, the manufacturer may apply for a device type to be operated, such as a car machine, a car, a refrigerator, a television, a watch, and the like, to determine a production capacity, a shipment volume, and the like of the type, and after the application is completed, the manufacturer may create a machine type in the corresponding device type, and then may continue to upload a device identifier. As shown in fig. 4, after the manufacturer uploads the device information, the device management platform needs to check the device information uploaded by the manufacturer, for example: and checking whether the equipment information is accurate, whether the hardware equipment meets the requirements of accessing the applet application service and the like.

(3) And uploading the public key of the equipment. In order to prevent the hardware type identifier and the device identifier of the hardware manufacturer from being leaked, other devices can run the applet through the same parameter, in the embodiment of the description, the device needs to be signed, the hardware manufacturer uploads the public key to the terminal device platform, and the private key is stored by itself and used for unique signature of each device, and in the embodiment of the description, a public and private key signature adding and verifying mode of RSA2 can be adopted. Fig. 5 is a schematic flowchart of uploading a public key in some embodiments of this specification, and as shown in fig. 5, after a manufacturer applies for passing a device type, a model of the device, such as a certain brand of automobile, may be added to the device type to serve as a product identifier of a class of devices. After the manufacturer uploads the device information of the hardware device, the device management platform can verify the model name, the serial number, the parameters and the like of the device, and after the verification is successful, the public key of the manufacturer can be uploaded under the device information to be used for signing, checking and signing the hardware device.

(4) The method comprises the steps of uploading equipment application binding, considering that a hardware equipment manufacturer can produce tens of thousands to hundreds of thousands of levels of equipment in batch, an application capacity interface for batch uploading needs to be provided, an application identifier needs to be opened for calling the interface, and the bound application can be used for uploading and subsequent management of the equipment on behalf of the manufacturer in order to prevent other people from calling the equipment by mistake and increase the application binding uploaded by the equipment identifier. Fig. 6 is a schematic flowchart of application binding in some embodiments of the present specification, and as shown in fig. 6, when an application is bound and called, the bound and called application may be verified, and after the verification is successful, a binding relationship between the calling application and a product type of a hardware device is established, so that a manufacturer can perform data interaction with a device management platform through the calling application.

(5) And after the steps are completed, equipment information can be uploaded to a specified manufacturer and a specified product type through an open interface, and only the hardware equipment uploaded in the step is legal equipment, which is one of conditions with running small programs. Fig. 7 is a schematic flowchart of a process of batch uploading of devices in some embodiments of the present description, and as shown in fig. 7, after the application binding is successfully invoked, the device information of a plurality of hardware devices may be uploaded in batch by invoking the application, and the device management platform may perform validity check on the uploaded device information, such as: and checking whether the binding relationship between the equipment type and the calling application is legal, whether the quantity of the equipment uploaded in batches meets the requirement, whether the equipment identification of the hardware equipment is unique, and the like.

Because the whole hardware equipment is controlled by a hardware manufacturer, the operating environment of the applet application has large uncertainty, and the account security, the data security, the fund security and the like of the user all need high security guarantee.

(6) And collecting the unique identifier of the equipment. The equipment identifier is uploaded by manufacturers, generally is the SN or IMEI number of a hardware device, but may be repeated among different manufacturers, and the equipment identifier has no direct relation with the actual operating environment. The embodiment of the description combines the IMEI or SN of the actual running hardware, combines the hash codes of the timestamp, the random number and other information, generates the hash codes when the hardware is started for the first time, and persists the hash codes to the equipment as far as possible. The collection is automatically collected by a mobile application in the equipment management platform and is uploaded to the server side, and the server side establishes a unique mapping relation with the equipment identification uploaded by a manufacturer through the unique identification of the automatic collection equipment. When the equipment is activated, the equipment operation environment information is collected, the global unique identifier of the equipment is generated, the binding of the manufacturer equipment identifier and the terminal equipment platform unique identifier is established, and the unified management of hardware equipment is facilitated.

(7) And equipment signature, wherein signature information needs to be generated for each equipment in order to prevent the equipment of a manufacturer from using the same request parameters for service processing, so that the equipment is not in an integral monitoring system. And (4) signing by the private key corresponding to the public key in the third step, wherein each device needs to re-sign and cannot use the same calling parameter, signing by the device signature mode by using the generated RSA2 private key, and selecting UTF-8 as the character set.

(8) After the steps are carried out, the manufacturer is guaranteed to be legal, meanwhile, the equipment, which is required to operate and install the applet application framework, of the manufacturer is controlled in the whole system, when the applet application is loaded in operation, legal authentication is required, and it is guaranteed that each equipment operating the applet is in a safety control range. Fig. 8 is a schematic flow chart of device authentication in some embodiments of the present disclosure, and as shown in fig. 8 and fig. 2, the following may be referred to for the authentication process:

1) each device needs to generate unique Signature information, namely Signature (product identifier) + device identifier) + private key, based on a public key added during machine type registration, and when an applet in a hardware device dynamically runs each time, IPC (Inter-Process Communication) Communication needs to be performed through a mobile application in an equipment management platform, so that the device is activated.

2) Before the Device is activated, operation authentication management and control are required, according to the steps (1) to (7), the running applet application transmits Hostappid (application identification for calling application), produced (or product identification), Deviceid (or Deviceid, Device identification) and Signature (or Signature information) to verify, the validity of the produced and the Device is judged, and if the running applet application is not in the Device management and control platform, the activation is not passed; carrying out validity check of Signature according to the public key uploaded by the DeviceID, and if the Signature check fails, activating the Signature to fail; and verifying the unique ID of the equipment, wherein the verification fails and the activation fails. Through the steps, the hardware equipment is ensured to be in the management and control range of the equipment management platform system, and the information of each hardware equipment is collected at the same time, so that the hardware equipment can be used as an effective mechanism for wind control, punishment and tracking in the future.

The basic parameter verification in fig. 3 to fig. 8 may be understood as verifying whether parameters of a manufacturer, a hardware device, a calling application, and the like are legal and non-null, and the specific verification content is not specifically limited in this embodiment of the present specification.

In the embodiment of the specification, by constructing new data models and processes of manufacturers, equipment, models and the like, all basic information, agent model information and specific hardware equipment marking information of hardware equipment manufacturers are collected and established in an equipment management platform system, and a foundation is laid for the control and penalty of subsequent equipment dimensions. By utilizing an end-to-end (from a server to a client) public and private key control and two-stage verification mechanism, when a hardware manufacturer registers and uploads equipment, a public key corresponding to the hardware equipment is uploaded, and authentication is performed through equipment information and an equipment unique signature in a small program running preposition process during dynamic running of the equipment, so that the legality of the equipment before the small program running is guaranteed. The unique mapping and binding of the equipment identification and the automatically acquired hardware information generation equipment unique identification are established, the uniqueness of the equipment identification in a global equipment manufacturer is established, the uniqueness of the small programs operated by a single manufacturer and a single equipment is guaranteed, the small programs cannot be operated and opened among different equipment through the simulation of the same request parameters, and the isolation and independence among the equipment are guaranteed.

On the basis of the foregoing embodiments, in some embodiments of the present specification, there may also be provided an installation management method for an applet executed on a user terminal side of a manufacturer, where fig. 9 is a flowchart illustrating an installation management method for an applet executed on a terminal side in a user in some embodiments of the present specification, and as shown in fig. 9, the method may include:

step 902, sending a registration request to the device management platform, and receiving registration success information returned by the device management platform after the registration audit is passed.

In a specific implementation process, if a manufacturer wants to use an applet service provided by the device management platform in an embodiment of this specification, the manufacturer may first send a registration request to the device management platform through a corresponding user terminal. The registration request may include manufacturer information (such as name, address, website, business license, contact person, contact phone, contact mailbox, etc.), and the device management platform may perform service admission audit on the registration information provided by the manufacturer, and audit the relevant qualification information of the manufacturer. For the detailed examination, reference is made to the above description of the embodiments, and details are not repeated here. After the verification is passed, the equipment management platform returns registration success information to the user terminal, namely, the manufacturer successfully registers in the equipment management platform.

Step 904, sending a binding applet service request to the device management platform, and receiving an applet service returned by the device management platform based on the binding applet service request.

In a specific implementation process, the device management platform may be a network platform provided by an application (some payment applications, social applications, etc. having multiple servlets) with multiple servlets, may include multiple servlets in the application, and may be directly managed by the application without additional development and maintenance of the servlets. Fig. 10 is a flowchart illustrating an installation process of an applet performed by a vendor in some embodiments of the present disclosure, where, as shown in fig. 10, a device management platform provides an applet pool, where the applet pool includes a plurality of applet services, and the vendor can select an applet service that needs to be bound from the applet pool. After receiving the binding applet service request sent by the manufacturer, the device management platform can return a plurality of applet services to the user terminal of the manufacturer according to the binding applet service request. Such as: after the manufacturer successfully resides and applies for binding the calling application, the calling application is accessed to the equipment management platform, so that the equipment information of the hardware equipment can be registered in the equipment management platform, and after the registration is successful, the hardware equipment can integrate the small program engine framework and the running environment. After receiving the applet binding service request sent by the manufacturer, the equipment management platform can return a plurality of applets to be selected by the manufacturer at the user terminal where the manufacturer is located.

Step 906, adding the applet service to the applet application, and installing the applet application including the applet service into the corresponding hardware device.

In a specific implementation process, a vendor may integrate an applet service returned by a device management platform into an applet application and install the applet application into a corresponding hardware device. The applet in the embodiment of the present specification may be understood as an application integrated with a plurality of applet services, may be understood as an applet engine, may be an application running in a hardware device, and may also be understood as an application package, such as: APK (Android application package), and the like. As shown in fig. 10, the bound applet service can be uploaded to different hardware devices, and different hardware devices can upload different applet services according to actual needs.

Step 908, sending an application activation request for activating an applet application in a hardware device 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 applet application in the hardware device based on the application activation request.

In a specific implementation process, after an applet is installed in a hardware device, the applet needs to be activated to enable normal use. The application activation request of the applet can be triggered by clicking the applet application in the login hardware device, or the application activation request for activating a certain applet application can be directly sent to the device management platform. The application activation request in the embodiment of this specification may include signature information of the hardware device, where the signature information may be encrypted information performed on device information of the hardware device, and the signature information may be used to perform security verification on the hardware device, so as to prevent device information of a manufacturer from being leaked, and other devices may also perform applet running through the same parameter. After receiving the application activation request, the device management platform may verify the hardware device based on the application activation request, for example: the signature verification method comprises the steps of verifying whether a request sent by a manufacturer of hardware equipment is verified in a manner of verifying signature information in an application activation request, carrying out legal verification on equipment information, manufacturer information and the like in the application activation request, and activating the applet application in the hardware equipment after the verification is passed. For the specific verification, reference may be made to the descriptions of the above embodiments, and details are not described herein again.

The installation management method for an applet provided in this specification may provide an applet service having multiple applets for a hardware device, and a manufacturer of the hardware device may obtain multiple applets returned by a device management platform by sending an applet binding service request to the device management platform, and select an applet required by the manufacturer. The device management platform can uniformly manage the hardware device for installing the applet application, so that the legality of the hardware device for running the applet application is ensured, the hardware device does not need to adapt to different application environments, the applet service in the applet application can be changed at any time, and the upgrading of the device is not depended on. The hardware equipment also does not need to install the application programs one by one, and a plurality of small programs are directly integrated in one application program and provided for manufacturers of the hardware equipment, so that the hardware equipment can have the small programs with various services, the operation is simple, the application configuration time, the labor and the cost of the hardware equipment are reduced, and the memory space occupied by the application programs in the hardware equipment can be reduced.

after the registration is successful, product information and equipment information corresponding to the hardware equipment and a public key of the hardware equipment are uploaded to the equipment management platform;

obtaining the signature information by adopting the following method:

and encrypting the product information and the equipment information of the hardware equipment by using a private key corresponding to the public key of the hardware equipment to obtain the signature information.

In particular implementations, the device management platform may provide a software Development kit such as an SDK (software Development kit) for the vendor to use to generate a pair of public and private keys. The private key may be used to perform encryption signature on device information, product information, and the like of the hardware device, such as: and encrypting the product identification and the equipment identification of the hardware equipment by using a private key to obtain the signature information of the hardware equipment. Each hardware device needs to be re-signed, the same calling parameters cannot be used, the device signature mode can be used for signature adding through the generated RSA2 private key, and the character set can be selected to be UTF-8. As shown in fig. 10, after the vendor is resident in the device management platform, product information, device information, etc. of the hardware device that needs to use the applet service may be uploaded in the device management platform. As shown in fig. 10, a manufacturer may upload product information of different product types, and each product type may correspond to different series of hardware devices, for example, the car machine may include x1 series, x2 series, and x3 series. The model name in fig. 10 can be understood as the device name of different series of hardware devices, the produced in fig. 10 can represent the product identifiers of products of different product types, and the deviceids each represent the device identifier of different hardware devices, as shown in fig. 10, the device identifier Deviceid can use the sn, i.e., Serial Number product Serial Number provided by the manufacturer. As shown in fig. 10, a manufacturer may also upload a public key of a hardware device through a user terminal, and when sending an application activation request to the device management platform, may send signature information of the hardware device to the device management platform together, where the signature information may be encrypted information performed on device information of the hardware device, and the signature information may be used to perform security verification on the hardware device, so as to prevent device information of the manufacturer from being leaked, and other devices may also perform applet running through the same parameter. When the hardware equipment is verified by the equipment management platform, the public key of the hardware equipment uploaded by common knowledge can be used for decrypting and verifying the signature on the signature information, if the decryption is successful, the signature passes through verification, and other information of the hardware equipment is continuously verified.

sending a calling application binding request to the equipment management platform, wherein the calling application binding request comprises calling applications to be bound, so that the equipment management platform binds the calling applications for the hardware equipment according to the calling application binding request;

and product information and equipment information uploaded in batch by the calling application.

In a specific implementation process, considering that a hardware device manufacturer may produce tens of thousands to hundreds of thousands of devices in batch, in this specification embodiment, a batch upload application capability interface may be provided, and a call interface needs to open an application identifier. The calling application is an application type, and may be an applet, a web application, a mobile application, etc., and the mobile application in fig. 10 may be understood as the calling application in the embodiment of the present specification. The method comprises the steps that after receiving a binding calling application request sent by a manufacturer through a user terminal, the equipment management platform can bind calling application for the manufacturer, the manufacturer can be connected to an interface of the equipment management platform through the calling application, the interface is accessed into the equipment management platform, and the binding applet service request is further sent to the equipment management platform. Such as: after the bound calling application is accessed to the device management platform, the device information of the hardware device needing to install the applet application can be registered in the device management platform, and after the registration is successful, a calling binding applet service request can be initiated for the hardware device. The calling application of each manufacturer can correspond to an application identifier, the application identifier can be accessed into the equipment management platform, the manufacturer can perform data interaction with the equipment management platform through the calling application, calling and installing of the applet application can be achieved, product information, equipment information and the like of the hardware equipment can be uploaded in batches through the calling application, and the uploaded hardware equipment can be edited and managed through the calling application. As shown in fig. 10, Hostappid may be understood as an application identifier of a calling application, different calling applications may be bound in one hardware device, and different calling applications may bind different applet services for the hardware device. Different calling applications can be in different clients of the hardware equipment, the different calling applications can simultaneously perform data interaction with the equipment management platform, and the equipment management platform provides a login state and an operating environment of the applet application for the hardware equipment.

In the present specification, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. The relevant points can be obtained by referring to the partial description of the method embodiment.

Based on the installation management method of the applet, one or more embodiments of the present specification further provide a system for installation management of the applet. The system may include systems (including distributed systems), software (applications), modules, components, servers, clients, etc. that use the methods described in embodiments of the present specification in conjunction with any necessary hardware-implemented devices. Based on the same innovative conception, embodiments of the present specification provide an apparatus as described in the following embodiments. Since the implementation scheme of the apparatus for solving the problem is similar to that of the method, the specific apparatus implementation in the embodiment of the present specification may refer to the implementation of the foregoing method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Specifically, fig. 11 is a schematic block diagram of an embodiment of an installation management apparatus for an applet provided in this specification, which may be immediately used as a device management platform in the foregoing embodiment, and as shown in fig. 11, the installation management apparatus for an applet provided in this specification may include: a registration auditing module 111, an applet service binding module 112, an activation request receiving module 113, and an application activation module 114, wherein:

the registration auditing module 111 is used for auditing the registration information in the registration request uploaded by the user terminal, and if the audit is passed, the registration success information is returned;

an applet service binding module 112, configured to receive an applet binding service request sent by the user terminal after successful registration, and return a corresponding applet service according to the applet binding service request, so that the user terminal installs an applet application including the applet service in a corresponding hardware device;

an activation request receiving module 113, configured to receive an application activation request for activating an applet application in a hardware device, where the application activation request includes signature information of the hardware device;

and the application activation module 114 is configured to verify the hardware device according to the application activation request, and activate an applet application in the hardware device if the verification passes.

The installation management apparatus for an applet provided in this specification may provide an applet service having multiple applets for a hardware device, and a manufacturer of the hardware device may obtain multiple applets returned by a device management platform by sending an applet binding service request to the device management platform, and select an applet required by the manufacturer. The device management platform can uniformly manage the hardware device for installing the applet application, so that the legality of the hardware device for running the applet application is ensured, the hardware device does not need to adapt to different application environments, the applet service in the applet application can be changed at any time, and the upgrading of the device is not depended on. The hardware equipment also does not need to install the application programs one by one, and a plurality of small programs are directly integrated in one application program and provided for manufacturers of the hardware equipment, so that the hardware equipment can have the small programs with various services, the operation is simple, the application configuration time, the labor and the cost of the hardware equipment are reduced, and the memory space occupied by the application programs in the hardware equipment can be reduced.

In some embodiments of the present description, the apparatus further comprises an information receiving module for receiving information

After the registration is successful, product information and equipment information uploaded by the user terminal are received;

the application activation module is specifically configured to:

In the embodiment of the specification, the hardware device can be verified to be a legal device registered in the device management platform through verification of the product information and the device information of the hardware device, and the validity of the hardware device for activating the applet application can be more accurately determined by combining verification of the signature information, so that the safety of the installation device of the applet application is improved.

On the basis of the above embodiment, the apparatus further includes a public key receiving module, configured to:

the application activation module is specifically configured to:

On the basis of the above embodiment, the apparatus further includes a unique identifier generating module configured to:

According to the embodiment of the specification, an equipment unique identifier is generated for the hardware equipment according to the equipment identifier in the equipment information of the hardware equipment uploaded by a manufacturer through a user terminal and the starting information when the hardware equipment is started, the equipment unique identifier is associated with the equipment identifier in the equipment information of the hardware equipment, the uniqueness of the equipment identifier in a global equipment manufacturer is established, the uniqueness of running small programs by a single manufacturer and a single equipment is guaranteed, the small programs cannot be run and opened by different equipment through the simulation of the same request parameters, and the isolation and the independence between the hardware equipment are guaranteed.

On the basis of the above embodiment, the start information includes start time and a start random number of the hardware device;

the unique identifier generation module is specifically configured to:

In the embodiment of the description, the unique device identifier of the hardware device is generated by combining the operating environment of the hardware device and the device identifier, and the unique device identifier is associated with the device identifier in the device information of the hardware device, so that the uniqueness of the device identifier in a global device manufacturer is established, the uniqueness of the small programs operated by a single manufacturer and a single device is ensured, the small programs cannot be operated and opened by simulating the same request parameters among different devices, and the isolation and independence among the hardware devices are ensured.

Fig. 12 is a schematic structural diagram of a module of another embodiment of an installation management apparatus for an applet, which is a user terminal corresponding to a manufacturer in the foregoing embodiment, and as shown in fig. 12, the installation management apparatus for an applet provided in this specification may include: a registration request module 121, an applet service request module 122, an applet installation module 123, an activation request module 124, wherein:

the registration request module 121 is configured to send a registration request to the device management platform, and receive registration success information returned by the device management platform after the registration audit is passed;

an applet service request module 122, configured to send a binding applet service request to the device management platform, and receive an applet service returned by the device management platform based on the binding applet service request;

an applet installing module 123, configured to add the applet service to an applet application, and install the applet application including the applet service into a corresponding hardware device;

an activation request module 124, configured to send an application activation request for activating an applet in a hardware device 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 applet in the hardware device based on the application activation request.

On the basis of the foregoing embodiments, in some embodiments of the present specification, the apparatus further includes a signature module, configured to:

obtaining the signature information by adopting the following method:

In the embodiment of the description, the end-to-end (from the server to the client) public and private key management and control are utilized, when the hardware manufacturer registers and uploads the device information of the hardware device, the public key corresponding to the hardware device is uploaded, and when the hardware device runs dynamically, the signature information of the device information is used for authentication in the pre-process of running the applet application, so that the legality of the device before the applet application is run is guaranteed.

On the basis of the foregoing embodiments, in some embodiments of the present specification, the apparatus further includes a calling application binding module, configured to:

It should be noted that the above-mentioned apparatus may also include other embodiments according to the description of the corresponding method embodiment. The specific implementation manner may refer to the description of the above corresponding method embodiment, and is not described in detail herein.

An embodiment of the present specification further provides an installation management device for an applet, including: at least one processor and a memory for storing processor-executable instructions, the processor implementing the information recommendation data processing method of the above embodiment when executing the instructions, such as:

Or, sending a registration request to the equipment management platform, and receiving registration success information returned by the equipment management platform after the registration audit is passed;

An embodiment of the present specification further provides an installation management system of an applet, including: the system comprises an equipment management platform, a user terminal and hardware equipment; the device management platform comprises at least one processor and a memory for storing executable instructions of the processor, and the processor executes the method executed by the device management platform and is used for providing mobile application comprising a plurality of small programs;

the user terminal is used for comprising at least one processor and a memory for storing processor executable instructions, and when the processor executes the instructions, a method executed by the user terminal corresponding to a manufacturer is realized so as to request to call a mobile application comprising a plurality of applets provided by the equipment management platform and install the mobile application into the hardware equipment.

It should be noted that the above description of the apparatus and system according to the method embodiments may also include other embodiments. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.

The installation management device for applet provided in this specification can be applied to various data analysis processing systems. The system or server or terminal or device may be a single server, or may include a server cluster, a system (including a distributed system), software (applications), actual operating devices, logical gate devices, quantum computers, etc. using one or more of the methods described herein or one or more embodiments of the system or server or terminal or device, in combination with necessary end devices implementing hardware. The system for checking for discrepancies may comprise at least one processor and a memory storing computer-executable instructions that, when executed by the processor, implement the steps of the method of any one or more of the embodiments described above.

The method embodiments provided by the embodiments of the present specification can be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Taking an example of the application running on a server, fig. 13 is a hardware configuration block diagram of an installation management server of an applet in one embodiment of the present specification, and the computer terminal may be the installation management server of the applet or an installation management device of the applet in the above embodiment. As shown in fig. 13, the server 10 may include one or more (only one shown) processors 100 (the processors 100 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), 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 the structure shown in fig. 13 is only an illustration and is not intended to limit the structure of the electronic device. For example, the server 10 may also include more or fewer components than shown in FIG. 13, and may also include other processing hardware, such as a database or multi-level cache, a GPU, or have a different configuration than shown in FIG. 13, for example.

The non-volatile memory 200 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the installation management method of the applet in the embodiment of the present specification, and the processor 100 executes various functional applications and resource data updates by executing the software programs and modules stored in the non-volatile memory 200. Non-volatile memory 200 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the non-volatile memory 200 may further include memory located remotely from the processor 100, which may be connected to a computer terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, office-to-network, mobile communication networks, and combinations thereof.

The transmission module 300 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal. In one example, the transmission module 300 includes a Network adapter (NIC) that can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission module 300 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The method or apparatus provided in this specification and described in the foregoing embodiments may implement service logic through a computer program and record the service logic on a storage medium, where the storage medium may be read and executed by a computer, and implement the effects of the solutions described in the embodiments of this specification, such as:

The storage medium may include a physical device for storing information, and typically, the information is digitized and then stored using an electrical, magnetic, or optical media. The storage medium may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy, such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth.

The installation management method or apparatus for the applet provided in the embodiments of this specification may be implemented in a computer by a processor executing corresponding program instructions, for example, implemented in a PC end using a c + + language of a windows operating system, implemented in a linux system, or implemented in an intelligent terminal using android and iOS system programming languages, implemented in processing logic based on a quantum computer, and the like.

It should be noted that descriptions of the apparatus, the computer storage medium, and the system described above according to the related method embodiments may also include other embodiments, and specific implementations may refer to descriptions of corresponding method embodiments, which are not described in detail herein.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to only the partial description of the method embodiment.

The embodiments of the present description are not limited to what must be consistent with industry communications standards, standard computer resource data updating and data storage rules, or what is described in one or more embodiments of the present description. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments using the modified or transformed data acquisition, storage, judgment, processing and the like can still fall within the scope of the alternative embodiments of the embodiments in this specification.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, 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, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, 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.

Although one or more embodiments of the present description provide method operational steps as described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive approaches. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When the device or the end product in practice executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures (for example, in the environment of parallel processors or multi-thread processing, even in the environment of distributed resource data update). The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded. The terms first, second, etc. are used to denote names, but not any particular order.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, etc. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable resource data updating apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable resource data updating apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable resource data update apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable resource data update apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

As will be appreciated by one skilled in the art, one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, and the relevant points can be referred to only part of the description of the method embodiments. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

The above description is merely exemplary of one or more embodiments of the present disclosure and is not intended to limit the scope of one or more embodiments of the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present specification should be included in the scope of the claims.

Claims

1. A method of installation management of an applet, the method comprising:

2. The method of claim 1, further comprising:

the verifying the hardware device according to the application activation request includes:

3. The method of claim 1, further comprising:

4. The method of claim 1, further comprising:

5. The method of claim 4, the boot information comprising a boot time, a boot nonce, of the hardware device;

6. The method of claim 4, the verifying the hardware device according to the application activation request, further comprising:

7. The method of claim 1, further comprising:

8. An installation management method of an applet, comprising:

9. The method of claim 8, further comprising:

obtaining the signature information by adopting the following method:

10. The method of claim 8, further comprising:

11. The method of claim 10, further comprising:

and accessing the equipment management platform through the calling application to edit and manage the uploaded product information and equipment.

12. An installation management apparatus of an applet, comprising:

13. The apparatus of claim 12, further comprising an information receiving module for

the application activation module is specifically configured to:

14. The apparatus of claim 12, the apparatus further comprising a public key receiving module to:

the application activation module is specifically configured to:

15. The apparatus of claim 13, the apparatus further comprising a unique identification generation module to:

16. The apparatus of claim 15, the boot information comprising a boot time, a boot nonce, of the hardware device;

the unique identifier generation module is specifically configured to:

17. An installation management apparatus of an applet, comprising:

18. The apparatus of claim 17, the apparatus further comprising a signature module to:

obtaining the signature information by adopting the following method:

19. The apparatus of claim 17, the apparatus further comprising a call application binding module to:

20. An installation management apparatus of an applet, comprising: at least one processor and a memory for storing processor-executable instructions, the processor implementing the method of any of claims 1-7 or 8-11 when executing the instructions.

21. An installation management system of an applet, comprising: the system comprises an equipment management platform, a user terminal and hardware equipment; wherein the device management platform comprises at least one processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the method of any one of claims 1 to 7 is implemented for providing an applet comprising a plurality of applets and managing a hardware device calling the applet;

the user terminal comprises at least one processor and a memory for storing processor-executable instructions, which when executed by the processor implement the method of any of claims 8-11, to request invocation of an applet comprising a plurality of applets provided by the device management platform and installation of the applet into the hardware device.