WO2021218621A1 - 应用功能配置方法、终端设备、服务器及存储介质 - Google Patents

应用功能配置方法、终端设备、服务器及存储介质 Download PDF

Info

Publication number
WO2021218621A1
WO2021218621A1 PCT/CN2021/086729 CN2021086729W WO2021218621A1 WO 2021218621 A1 WO2021218621 A1 WO 2021218621A1 CN 2021086729 W CN2021086729 W CN 2021086729W WO 2021218621 A1 WO2021218621 A1 WO 2021218621A1
Authority
WO
WIPO (PCT)
Prior art keywords
plug
terminal device
algorithm plug
target
algorithm
Prior art date
Application number
PCT/CN2021/086729
Other languages
English (en)
French (fr)
Inventor
康家梁
吴文川
沈玺
傅宜生
Original Assignee
中国银联股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国银联股份有限公司 filed Critical 中国银联股份有限公司
Publication of WO2021218621A1 publication Critical patent/WO2021218621A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons

Definitions

  • This application belongs to the field of data processing, and in particular relates to an application function configuration method, terminal device, server, and storage medium.
  • the terminal device can realize various functions by running the application program.
  • terminal devices can only run applications that they support. Different terminal devices can use different hardware, so that applications that implement the same function are exclusive to different terminal devices.
  • the application C1 configured on the terminal device B1 that adopts the living body detection algorithm A1 cannot run on the terminal device B2 that adopts the living body detection algorithm A2.
  • the exclusivity of applications that realize the same function to different terminal devices reduces the versatility of application functions in terminal devices.
  • the embodiments of the present application provide an application function configuration method, terminal device, server, and storage medium, which can improve the versatility of application function implementation in the terminal device.
  • an embodiment of the present application provides an application function configuration method applied to a terminal device.
  • the method includes: sending a query request message to a management server.
  • the query request message includes the hardware identification of the terminal device.
  • the management server stores the hardware identification and Correspondence of algorithm plug-ins;
  • the plug-in management server obtains the target algorithm plug-in, where the plug-in management server includes a management server or a cloud server, and the plug-in management server stores at least one algorithm plug-in.
  • the algorithm plug-in is used to implement the function of the application, and the target algorithm plug-in is Query the algorithm plug-in corresponding to the hardware identifier in the request message; load the target algorithm plug-in.
  • the embodiment of the present application provides an application function configuration method, which is applied to a server, and the server stores a correspondence between a hardware identifier and an algorithm plug-in; the method includes: receiving a query request message sent by a terminal device, and the query request message includes the terminal The hardware identification of the device; according to the corresponding relationship between the stored hardware identification and the algorithm plug-in, the target algorithm plug-in or the query response message used to indicate the target algorithm plug-in is sent to the terminal device.
  • the target algorithm plug-in is the algorithm corresponding to the hardware identification in the query request message Plug-in.
  • an embodiment of the present application provides a terminal device, including: a sending module, configured to send a query request message to a management server, the query request message includes the hardware identification of the terminal device, and the management server stores the correspondence between the hardware identification and the algorithm plug-in Relationship; receiving module, used to obtain the target algorithm plug-in from the plug-in management server, where the plug-in management server includes a management server or a cloud server, the plug-in management server stores at least one algorithm plug-in, the algorithm plug-in is used to implement the function of the application, the target algorithm plug-in It is the algorithm plug-in corresponding to the hardware identifier in the query request message; the loading module is used to load the target algorithm plug-in.
  • an embodiment of the present application provides a server, which includes: a storage module for storing the correspondence between a hardware identifier and an algorithm plug-in; a receiving module for receiving a query request message sent by a terminal device, the query request message including the terminal device
  • the sending module is used to send the target algorithm plug-in or the query response message used to indicate the target algorithm plug-in to the terminal device according to the corresponding relationship between the stored hardware identification and the algorithm plug-in.
  • the target algorithm plug-in is the hardware in the query request message Identify the corresponding algorithm plug-in.
  • an embodiment of the present application provides a terminal device, including a processor, a memory, and a computer program stored in the memory and running on the processor.
  • the computer program is executed by the processor to implement the technical solution of the first aspect
  • the application function configuration method is described in detail below.
  • an embodiment of the present application provides a server, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor.
  • the computer program is executed by the processor to implement the technical solutions in the second aspect Application function configuration method.
  • embodiments of the present application provide a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, the application function configuration method in the technical solution of the first aspect or the second The application function configuration method in the technical solution of the aspect.
  • the embodiment of the application provides an application function configuration method, a terminal device, a server, and a storage medium.
  • the terminal device can send a query request message including the hardware identification of the terminal device to the management server, so that the corresponding relationship between the hardware identification and the algorithm plug-in is.
  • the terminal device can obtain the algorithm plug-in corresponding to the hardware identifier in the query request message, that is, the target algorithm plug-in, from the management server or the cloud server, and load the target algorithm plug-in to realize the function of the target application. Run the same application on different mobile terminals.
  • the mobile terminal itself can be configured with appropriate algorithm plug-ins, so that applications that implement the same function are not It is also exclusive, which improves the versatility of application functions in terminal devices.
  • FIG. 1 is a schematic diagram of an example of an application scenario of an application function configuration method provided by an embodiment of the application;
  • FIG. 2 is a schematic diagram of another example of an application scenario of the application function configuration method provided by an embodiment of the application;
  • FIG. 3 is a flowchart of an embodiment of an application function configuration method applied to a terminal device provided by this application;
  • FIG. 4 is a flowchart of another embodiment of an application function configuration method applied to a terminal device provided by this application;
  • FIG. 5 is a flowchart of another embodiment of the application function configuration method applied to terminal equipment provided by this application.
  • FIG. 6 is a flowchart of an embodiment of an application function configuration method applied to a server provided by this application;
  • FIG. 7 is a flowchart of another embodiment of an application function configuration method applied to a server provided by this application.
  • FIG. 8 is a schematic structural diagram of an embodiment of a terminal device provided by this application.
  • FIG. 9 is a schematic structural diagram of another embodiment of a terminal device provided by this application.
  • FIG. 10 is a schematic structural diagram of an embodiment of a server provided by this application.
  • FIG. 11 is a schematic structural diagram of another embodiment of a server provided by this application.
  • FIG. 12 is a schematic diagram of the hardware structure of an embodiment of a terminal device provided by this application.
  • This application provides an application function configuration method, terminal device, server, and storage medium, which can be applied to a scenario where application function configuration is performed for a terminal device.
  • the application function is the function of the application installed in the terminal device, and the category of the application function is not limited here.
  • the application function may include a biometric recognition application function, a face payment application function, a biometric check-in application function, a map positioning application function, a file editing application function, and the like.
  • FIG. 1 is a schematic diagram of an example of an application scenario of an application function configuration method provided by an embodiment of the application.
  • the application function configuration system may include a terminal device 100 and a management server 200.
  • the terminal device 100 may include a mobile phone, a computer, a tablet computer, a gate, and other terminal devices, which are not limited herein.
  • An application is installed in the terminal device 100, and when the application runs, the function corresponding to the application can be realized.
  • the management server 200 stores the corresponding relationship between the hardware identifier and the algorithm plug-in.
  • the correspondence between the hardware identification and the algorithm plug-in can be realized as a correspondence between the hardware identification and the download address of the algorithm plug-in, or as the correspondence between the hardware identification and the plug-in identification of the algorithm plug-in, which is not limited here.
  • the management server 200 may also store algorithm plug-ins.
  • the terminal device 100 can interact with the management server 200.
  • FIG. 2 is a schematic diagram of another example of an application scenario of the application function configuration method provided by an embodiment of the application.
  • the application function configuration system may include a terminal device 100, a management server 200 and a cloud server 300.
  • the management server 200 stores the corresponding relationship between the hardware identifier and the algorithm plug-in.
  • the correspondence between the hardware identification and the algorithm plug-in may be implemented as a correspondence between the hardware identification and the download address of the algorithm plug-in, or as a correspondence between the hardware identification and the plug-in identification of the algorithm plug-in, which is not limited herein.
  • the cloud server 300 may be set in the cloud and store algorithm plug-ins.
  • the terminal device 100, the management server 200, and the cloud server 300 can interact with each other.
  • FIG. 3 is a flowchart of an embodiment of an application function configuration method applied to a terminal device provided by this application. As shown in FIG. 3, the application function configuration method may include step S401 to step S403.
  • step S401 a query request message is sent to the management server.
  • the query request message can be sent to the management server when the target application in the terminal device is started for the first time after installation; it can also be sent to the management server every time the target application in the terminal device is started. ; It can also send a query request message to the management server when the target application in the terminal device is customized for a certain time or several times, which is not limited here.
  • the target application is an application installed on the terminal device. When the terminal device starts the target application, it can send a query request message to the management server.
  • the query request message includes the hardware identification of the terminal device.
  • the hardware identification of the terminal device can identify the terminal device, and can also identify the relevant components of the terminal device configuration.
  • the hardware identification of the terminal device may include the model of the terminal device and/or the model of related components of the terminal device configuration.
  • the hardware identification of the terminal device may also include the fingerprint information of the terminal device.
  • the hardware identification can be specifically set according to the terminal device, which is not limited here. For example, if the terminal device is a biometric identification terminal, the hardware identification may include the model of the biometric identification terminal and the model of the camera component configured on the biometric identification terminal.
  • the management server stores the corresponding relationship between the hardware identifier and the algorithm plug-in.
  • the algorithm plug-in can run in the terminal device identified by the hardware identification. That is to say, if the terminal device identified by a certain hardware identification supports the operation of an algorithm plug-in, the hardware identification has a corresponding relationship with the algorithm plug-in.
  • step S402 the target algorithm plug-in is obtained from the plug-in management server.
  • the plug-in management server includes a management server or a cloud server.
  • the plug-in management server stores at least one algorithm plug-in. Algorithm plug-ins are used to implement application functions.
  • the target algorithm plug-in is an algorithm plug-in corresponding to the hardware identifier in the query request message.
  • the target algorithm plug-in is an algorithm plug-in corresponding to the hardware identification in the query request message in the correspondence between the hardware identification and the algorithm plug-in stored in the management server.
  • the plug-in management server includes a management server.
  • the management server receives the query request message, and can push the target algorithm plug-in to the terminal device according to the corresponding relationship between the hardware identifier stored in itself and the algorithm plug-in, and the hardware identifier in the query request message.
  • the terminal device obtains the target algorithm plug-in from the management server.
  • the management server receives the query request message, and sends a message indicating the target algorithm plugin to the cloud server storing the algorithm plugin, so that the cloud server sends the target algorithm plugin to the management server.
  • the management server may push the received target algorithm plug-in to the terminal device.
  • the terminal device obtains the target algorithm plug-in from the management server.
  • the plug-in management server includes a cloud server. After receiving the query request message, the management server may send a message that can be used to indicate the target algorithm plug-in to the terminal device. The terminal device can obtain the target algorithm plug-in from the cloud server. Alternatively, after receiving the query request message, the management server sends a message indicating the target algorithm plug-in and the terminal device to the cloud server, so that the cloud server can push the target algorithm plug-in to the terminal device. The terminal device can obtain the target algorithm plug-in from the cloud server.
  • Algorithm plug-ins are used to implement application functions.
  • the algorithm plug-in may be specifically implemented as an Android application package (APK), jar file, rar file, or binary file (ie, bin file), etc., which is not limited here.
  • API Android application package
  • the different algorithm plug-ins stored in the plug-in management server can be plug-ins that implement the same function but different algorithms, or plug-ins that implement the same algorithm but different versions, or plug-ins that implement the same function but adapt to different terminal manufacturers. Plug-ins that have the same function but are adapted to different terminal hardware can also be plug-ins that implement different functions, which is not limited here.
  • the target algorithm plug-in obtained by the terminal device from the plug-in management server may be an algorithm plug-in that implements the function of the target application for the first time, or it may be an updated algorithm plug-in of the function of the target application.
  • the terminal device obtains the target algorithm plug-in from the plug-in management server, and can use differential download technology, resumable transmission technology, etc., which are not limited here. Using differential download technology, resumable download technology, etc. to obtain the target algorithm plug-in can improve the download efficiency, save the bandwidth occupied by the download, and reduce the amount of data that needs to be downloaded.
  • the target algorithm plug-in is obtained using differential download technology, resumable transmission technology, etc.
  • the downloaded data needs to be combined into a complete algorithm plug-in, so that the terminal device can run the algorithm plug-in normally and realize the function of the target application.
  • the differential download technology is often used in the scenario of updating algorithm plug-ins, that is, if you want to replace the current version of the algorithm plug-in in the terminal device with another version of the algorithm plug-in, you only need to download the other version of the algorithm plug-in and the current algorithm plug-in from the plug-in management server.
  • the different parts of the version of the algorithm plug-in can be used.
  • step S403 the target algorithm plug-in is loaded.
  • dynamic loading technology can be used to load the target algorithm plug-in. After loading the target algorithm plug-in, the function of the target application can be realized.
  • the specific implementation of loading can be determined according to the type of the terminal device or the type of the operating system in the terminal device, which is not limited here. For example, if the terminal device is an Android terminal device, the Android native loader or other technologies based on similar principles can be used to load the target algorithm plug-in.
  • the terminal device may also obtain a summary of the target algorithm plug-in from the plug-in management server.
  • the terminal device may perform security verification on the obtained target algorithm plug-in based on the target algorithm plug-in and the obtained summary of the target algorithm plug-in. If the security check succeeds, the terminal device allows the target algorithm plug-in to be loaded. If the security check fails, the terminal device is not allowed to load the target algorithm plug-in. Through security verification, it can be ensured that the terminal device loads the target algorithm plug-in safely and legally, and the security of the terminal device running application is improved.
  • the terminal device may send a query request message including the hardware identification of the terminal device to the management server, so that according to the correspondence between the hardware identification and the algorithm plug-in, the terminal device can obtain the information from the management server or the cloud server.
  • the algorithm plug-in corresponding to the hardware identifier in the query request message is the target algorithm plug-in, and the target algorithm plug-in is loaded to realize the function of the target application. Run the same application on different mobile terminals.
  • the mobile terminal Through the interaction between the terminal device and the management server, or through the interaction of the terminal device, the management server, and the cloud server, the mobile terminal itself can be configured with appropriate algorithm plug-ins, so that applications that implement the same function are not It is also exclusive, which improves the versatility of application functions in terminal devices.
  • the terminal device can implement a variety of different algorithms, and the hardware of the terminal device itself can also be freely combined according to requirements, so that the implementation of application functions can be docked with different types of algorithms and hardware, which improves the terminal Equipment function realization and flexibility of terminal equipment production.
  • the application function configuration method may be applied in a biometric recognition scenario, and the target application may include a face recognition application.
  • the hardware identification of the aforementioned terminal device may include the terminal identification and/or the identification of the biometric collection component.
  • the terminal identifier may include an identifier for identifying the entire terminal device, such as the model of the terminal device or the device code of the terminal device, etc., which is not limited herein.
  • the biometric collection component identifier is used to identify the biometric collection component configured by the terminal device, and the biometric collection component identifier can be obtained according to the standard interface of the biometric collection component.
  • the in vivo detection technology may include structured light in vivo detection technology, Time of Flight (TOF) in vivo detection technology, infrared binocular in vivo detection technology, etc., which are not limited here.
  • the biological feature collection component may include one or more of a structured light-based biological feature collection component, a TOF-based biological feature collection component, and an infrared binocular biological feature collection component.
  • the structured light-based biological feature collection component can be specifically implemented as a camera module based on the structured light live detection algorithm.
  • the TOF-based biometric collection component can be specifically implemented as a camera module based on the TOF live detection algorithm.
  • the infrared binocular biological feature acquisition component can be specifically realized as a camera module based on the infrared binocular live detection algorithm.
  • the target algorithm plug-in acquired by the terminal device is an algorithm plug-in that can be supported by the terminal device for implementing the structured light living body detection algorithm.
  • the target algorithm plug-in acquired by the terminal device is an algorithm plug-in that can be supported by the terminal device and used to implement the TOF live detection algorithm.
  • the target algorithm plug-in acquired by the terminal device is an algorithm plug-in that can be supported by the terminal device for implementing the infrared binocular living detection algorithm.
  • Fig. 4 is a flowchart of another embodiment of an application function configuration method applied to a terminal device provided by this application.
  • the plug-in management server includes a cloud server.
  • the difference between FIG. 4 and FIG. 3 is that the application function configuration method shown in FIG. 4 may further include step S404, and step S402 in FIG. 3 may be refined into step S4021 in FIG.
  • step S404 a query response message sent by the management server is received.
  • the query response message is generated by the management server based on the query request message.
  • the query response message is used to indicate the target algorithm plug-in.
  • step S4021 the target algorithm plug-in is obtained from the cloud server.
  • the cloud server stores at least one algorithm plug-in.
  • the query response message may specifically include the download address of the target algorithm plug-in in the cloud server.
  • the terminal device can download the target algorithm plug-in from the cloud server according to the download address of the target algorithm plug-in in the response message.
  • the query response message may also include a summary of the target algorithm plug-in, or the terminal device may also obtain a summary of the target algorithm plug-in from the cloud server.
  • the terminal device may perform security verification on the downloaded target algorithm plug-in based on the target algorithm plug-in and the obtained summary of the target algorithm plug-in. If the security check succeeds, the terminal device allows the target algorithm plug-in to be loaded. If the security check fails, the terminal device is not allowed to load the target algorithm plug-in. Through security verification, it can be ensured that the terminal device loads the target algorithm plug-in safely and legally, and the security of the terminal device running application is improved.
  • the query response message received by the terminal device indicates the use that the terminal device can support.
  • Algorithm plug-in for realizing structured light live detection algorithm In the case that the biometrics collection component includes a TOF-based biometrics collection component, the query response message received by the terminal device indicates the algorithm plug-in used to implement the TOF live detection algorithm that the terminal device can support. In the case that the biometrics collection component includes an infrared binocular biometrics collection component, the query response message received by the terminal device indicates the algorithm plug-in used to implement the infrared binocular live detection algorithm that the terminal device can support.
  • the management server stores the correspondence between the version of the algorithm plug-in and the algorithm plug-in.
  • the management server can store the hardware identification, the version of the algorithm plug-in, and the corresponding relationship of the algorithm plug-in.
  • the management server can also store the corresponding relationship between more information, which is not limited here.
  • the terminal device can determine the version of the algorithm plug-in required by the target application according to its own operating conditions or user input operations.
  • the query request message may also include version request information used to characterize the version of the algorithm plug-in requested by the terminal device.
  • the version request information may be a version number, etc., which is not limited here.
  • the target algorithm plug-in obtained from the plug-in management server is the target algorithm plug-in corresponding to the version request information.
  • the query response message can also be used to indicate the target algorithm plug-in corresponding to the version request information, that is, the query response message can be used to indicate what the terminal device requests The target algorithm plugin for the algorithm plugin version.
  • FIG. 5 is a flowchart of another embodiment of the application function configuration method applied to terminal equipment provided by this application.
  • the difference between FIG. 5 and FIG. 3 is that the application function configuration method shown in FIG. 5 may further include step S405 and step S406, and step S403 in FIG. 3 may be specifically refined into step S4031 in FIG. 5.
  • step S405 when the target application is started in the terminal device, it is detected whether the terminal device stores an algorithm plug-in for realizing the function of the target application.
  • the target algorithm plug-in obtained when the target application is started before can be stored in the terminal device, and the target algorithm plug-in can realize the function of the target application.
  • step S406 when the terminal device stores the algorithm plug-in for realizing the function of the target application, load the algorithm plug-in for realizing the function of the target application stored in the terminal device.
  • the terminal device stores an algorithm plug-in used to implement the function of the target application
  • the stored algorithm plug-in used to implement the function of the target application can be directly loaded.
  • the algorithm plug-in stored in the terminal device for realizing the function of the target application can also be checked for security. If the security check succeeds, the terminal device loads the algorithm plug-in again.
  • step S401 to step S403 in the above-mentioned embodiment can be executed, which will not be repeated here.
  • step S4031 when the target application in the terminal device is started next time, the latest version of the target algorithm plug-in is loaded.
  • the terminal device stores an algorithm plug-in for realizing the function of the target application, but the algorithm plug-in is not the latest version of the algorithm plug-in, you can use the query request message, or through the query request message and query response message, Request the latest version of the target algorithm plugin.
  • the latest version of the target algorithm plugin may be obtained from the plugin management server, or the query response message may be used to indicate the latest version of the target algorithm plugin.
  • the terminal device may first load the algorithm plug-in stored in the terminal device for realizing the function of the target application, and run the target application.
  • the query request message also includes gray-scale release reference information.
  • the gray-scale release reference information is used for the gray-scale release of algorithm plug-ins by the management server.
  • the gray-scale release reference information may include one or more of terminal device hardware information, terminal device geographic location information, terminal device user information, and target application usage frequency information in the terminal device, which is not limited herein.
  • the management server can determine the gray-scale release of the algorithm plug-in corresponding to the target application of the terminal device according to the gray-scale release reference information, set the correspondence between the hardware identification and the algorithm plug-in, and the correspondence between the version of the algorithm plug-in and the algorithm plug-in.
  • Fig. 6 is a flowchart of an embodiment of a method for configuring application functions applied to a server provided by this application. As shown in FIG. 6, the application function configuration method may include step S501 to step S502.
  • step S501 a query request message sent by a terminal device is received.
  • the query request message includes the hardware identification of the terminal device.
  • the query request message includes the hardware identification of the terminal device.
  • step S502 according to the stored corresponding relationship between the hardware identifier and the algorithm plug-in, the target algorithm plug-in or a query response message for indicating the target algorithm plug-in is sent to the terminal device.
  • the terminal device identifiable by the hardware identifier supports the loading and running of the algorithm plug-in corresponding to the hardware identifier.
  • the server may determine the algorithm plug-in corresponding to the hardware identifier in the query request message according to the stored hardware identifier and the corresponding relationship between the algorithm plug-in, and use the algorithm plug-in as the target algorithm plug-in.
  • the query response message is used to indicate the target algorithm plug-in.
  • the server may generate a query response message according to the stored hardware identifier and the query response message of the algorithm plug-in, and the hardware identifier in the query request message.
  • the server stores the corresponding relationship between the hardware identifier and the algorithm plug-in.
  • the hardware identification in the query request message sent by the terminal device can be used to determine the algorithm plug-in that the terminal device is adapted to, that is, the target algorithm plug-in, and the target algorithm plug-in can be sent to the terminal device, or it will be able to
  • the query response message indicating the target algorithm plug-in is sent to the terminal device, so that the terminal device can obtain the algorithm plug-in adapted to itself, that is, the target algorithm plug-in. Run the same application on different mobile terminals.
  • the server and the terminal device it is possible to configure the applicable algorithm plug-in for the mobile terminal itself, so that the application that realizes the same function is no longer exclusive, which improves the realization of the application function on the terminal device. Versatility.
  • the hardware identification of the terminal device includes a terminal identification and/or a biometrics collection component identification.
  • the biometric collection component identifier is used to identify the biometric collection component configured by the terminal device.
  • the identification of the biometrics collection component, and the identification of the biometrics collection component please refer to the relevant description in the above-mentioned embodiment, which will not be repeated here.
  • the server also stores one or more of the correspondence between the version of the algorithm plug-in and the algorithm plug-in, the summary of the algorithm plug-in, the download address of the algorithm plug-in, and the update type of the algorithm plug-in.
  • the server can store the correspondence between the hardware identification, the algorithm plug-in, and the version of the algorithm plug-in, so as to store the correspondence between the hardware identification and the algorithm plug-in, and store the correspondence between the version of the algorithm plug-in and the algorithm plug-in.
  • the summary of the algorithm plug-in can be used by the terminal device to perform security verification on the downloaded algorithm plug-in.
  • the update type of the algorithm plug-in may include forced update, non-sense update, etc., which is not limited here.
  • the server stores the correspondence between the version of the algorithm plug-in and the algorithm plug-in.
  • the query request message also includes version request information used to characterize the version of the algorithm plug-in requested by the terminal device.
  • the target algorithm plug-in that the server can send to the terminal device is the target algorithm plug-in corresponding to the version request information.
  • the query response message can be used to indicate the target algorithm plug-in corresponding to the requested information.
  • the target algorithm plug-in sent to the terminal device is the latest version of the target algorithm plug-in.
  • the query response message is used to indicate the latest version of the target algorithm plug-in.
  • FIG. 7 is a flowchart of another embodiment of the application function configuration method applied to the server provided by this application. The difference between FIG. 7 and FIG. 6 is that the application function configuration method shown in FIG. 7 further includes step S503.
  • step S503 according to the gray-level publishing reference information, perform gray-level publishing of the algorithm plug-in to the terminal device.
  • the query request message in the foregoing embodiment may include gray-scale release reference information.
  • gray-scale release reference information please refer to the relevant description part in the above-mentioned embodiment, which will not be repeated here.
  • the server can determine the gray publishing strategy based on the gray publishing reference information. For example, determine the version of the algorithm plug-in adapted for each terminal device.
  • the server can publish reference information according to the gray level, and allocate different versions of algorithm plug-ins to users in different ranges to meet the business needs of different users.
  • FIG. 8 is a schematic structural diagram of an embodiment of a terminal device provided by this application.
  • the terminal device 100 may include a sending module 101, a receiving module 102, and a loading module 103.
  • the sending module 101 is used to send a query request message to the management server.
  • the query request message includes the hardware identification of the terminal device.
  • the management server stores the corresponding relationship between the hardware identification and the algorithm plug-in;
  • the receiving module 102 is used to obtain the target algorithm plug-in from the plug-in management server.
  • the plug-in management server includes a management server or a cloud server.
  • the plug-in management server stores at least one algorithm plug-in. Algorithm plug-ins are used to implement application functions.
  • the target algorithm plug-in is an algorithm plug-in corresponding to the hardware identifier in the query request message.
  • the loading module 103 is used to load the target algorithm plug-in.
  • the terminal device may send a query request message including the hardware identification of the terminal device to the management server, so that according to the correspondence between the hardware identification and the algorithm plug-in, the terminal device can obtain the information from the management server or the cloud server.
  • the algorithm plug-in corresponding to the hardware identifier in the query request message is the target algorithm plug-in, and the target algorithm plug-in is loaded to realize the function of the target application. Run the same application on different mobile terminals.
  • the mobile terminal Through the interaction between the terminal device and the management server, or through the interaction of the terminal device, the management server, and the cloud server, the mobile terminal itself can be configured with appropriate algorithm plug-ins, so that applications that implement the same function are not It is also exclusive, which improves the versatility of application functions in terminal devices.
  • the hardware identification of the terminal device includes a terminal identification and/or a biometrics collection component identification.
  • the biometric collection component identifier is used to identify the biometric collection component configured by the terminal device.
  • the plug-in management server includes a cloud server.
  • the above-mentioned receiving module 102 may also be used to receive a query response message sent by the management server.
  • the query response message is used to indicate the target algorithm plug-in.
  • the query request message also includes version request information used to characterize the version of the algorithm plug-in requested by the terminal device.
  • the management server stores the correspondence between the version of the algorithm plug-in and the algorithm plug-in.
  • the target algorithm plug-in obtained from the plug-in management server is a target algorithm plug-in corresponding to the version request information.
  • the query response message may be used to indicate the target algorithm plug-in corresponding to the version request information.
  • FIG. 9 is a schematic structural diagram of another embodiment of a terminal device provided by this application. The difference between FIG. 9 and FIG. 8 is that the terminal device 100 shown in FIG. 9 may further include a detection module 104.
  • the detection module 104 is configured to detect whether the terminal device stores an algorithm plug-in for realizing the function of the target application when the target application is started in the terminal device.
  • the loading module 103 in the foregoing embodiment may also be used to load the algorithm plug-in used to implement the function of the target application stored in the terminal device when the terminal device stores the algorithm plug-in used to implement the function of the target application.
  • the target algorithm plugin obtained from the plugin management server is the latest version of the target algorithm plugin.
  • the receiving module 102 is also used to receive the query response message sent by the management server, the query response message may be used to indicate the latest version of the target algorithm plug-in.
  • the loading module 103 can be used to load the latest version of the target algorithm plug-in when the target application is started next time in the terminal device.
  • the query request message also includes gray-scale release reference information.
  • the gray-scale release reference information is used for the gray-scale release of algorithm plug-ins by the management server.
  • FIG. 10 is a schematic structural diagram of an embodiment of a server provided by this application.
  • the server 200 may include a storage module 201, a receiving module 202, and a sending module 203.
  • the storage module 201 can be used to store the corresponding relationship between the hardware identifier and the algorithm plug-in.
  • the receiving module 202 can be used to receive a query request message sent by a terminal device.
  • the query request message includes the hardware identification of the terminal device.
  • the sending module 203 may be configured to send the target algorithm plugin or a query response message for indicating the target algorithm plugin to the terminal device according to the stored corresponding relationship between the hardware identifier and the algorithm plugin.
  • the target algorithm plug-in is an algorithm plug-in corresponding to the hardware identifier in the query request message.
  • the query response message can be generated by the generation module (not shown in the figure) in the server 200 according to the stored hardware identifier and the query response message of the algorithm plug-in, and the hardware identifier in the query request message.
  • the server stores the corresponding relationship between the hardware identifier and the algorithm plug-in.
  • the hardware identification in the query request message sent by the terminal device can be used to determine the algorithm plug-in that the terminal device is adapted to, that is, the target algorithm plug-in, and the target algorithm plug-in can be sent to the terminal device, or it will be able to
  • the query response message indicating the target algorithm plug-in is sent to the terminal device, so that the terminal device can obtain the algorithm plug-in adapted to itself, that is, the target algorithm plug-in. Run the same application on different mobile terminals.
  • the server and the terminal device it is possible to configure the applicable algorithm plug-in for the mobile terminal itself, so that the application that realizes the same function is no longer exclusive, which improves the realization of the application function on the terminal device. Versatility.
  • the hardware identification of the terminal device includes a terminal identification and/or a biometrics collection component identification.
  • the biometric collection component identifier is used to identify the biometric collection component configured by the terminal device.
  • the storage module 201 may also be used to store one or more of the correspondence between the version of the algorithm plug-in and the algorithm plug-in, the summary of the algorithm plug-in, the download address of the algorithm plug-in, and the update type of the algorithm plug-in.
  • the storage module 201 also stores the correspondence between the version of the algorithm plug-in and the algorithm plug-in.
  • the query request message also includes version request information used to characterize the version of the algorithm plug-in requested by the terminal device.
  • the target algorithm plug-in sent to the terminal device is the target algorithm plug-in corresponding to the version request information.
  • the query response message is used to indicate the target algorithm plug-in corresponding to the version request information.
  • the target algorithm plug-in sent to the terminal device is the latest version of the target algorithm plug-in.
  • the query response message is used to indicate the latest version of the target algorithm plug-in.
  • FIG. 11 is a schematic structural diagram of another embodiment of a server provided by this application. The difference between FIG. 11 and FIG. 10 is that the server shown in FIG. 11 may further include a gray-scale publishing module 203.
  • the query request message may also include gray-scale release reference information.
  • the gray-scale publishing module 203 can be used to publish the reference information according to the gray-scale and perform the gray-scale publishing of the algorithm plug-in to the terminal device.
  • FIG. 12 is a schematic diagram of the hardware structure of an embodiment of a terminal device provided by this application.
  • the terminal device 600 includes a memory 601, a processor 602, and a computer program stored on the memory 601 and running on the processor 602.
  • the aforementioned processor 602 may include a central processing unit (CPU) or a specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
  • CPU central processing unit
  • ASIC specific integrated circuit
  • the memory 601 may include a large-capacity memory for data or instructions.
  • the memory 601 may include an HDD, a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these.
  • the storage 601 may include removable or non-removable (or fixed) media.
  • the memory 601 can be opened inside or outside the terminal device 600 in the terminal hotspot.
  • the memory 601 is a non-volatile solid-state memory.
  • the memory 601 includes read-only memory (ROM).
  • the ROM can be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically rewritable ROM (EAROM) or flash memory or A combination of two or more of these.
  • the processor 602 runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory 601, so as to implement the application function configuration method applied to the terminal device in the foregoing embodiment.
  • the terminal device 600 may further include a communication interface 603 and a bus 604. Wherein, as shown in FIG. 12, the memory 601, the processor 602, and the communication interface 603 are connected through the bus 604 and complete the communication with each other.
  • the communication interface 603 is mainly used to implement communication between various modules, devices, units, and/or devices in the embodiments of the present application.
  • the input device and/or output device can also be accessed through the communication interface 603.
  • the bus 604 includes hardware, software, or both, and couples the components of the terminal device 600 to each other.
  • the bus 604 may include an accelerated graphics port (AGP) or other graphics bus, an enhanced industry standard architecture (EISA) bus, a front side bus (FSB), a hypertransport (HT) interconnect, an industry standard architecture (ISA) ) Bus, unlimited bandwidth interconnect, low pin count (LPC) bus, memory bus, microchannel architecture (MCA) bus, peripheral component interconnect (PCI) bus, PCI-Express (PCI-X) bus, serial advanced Technical Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus or other suitable bus or a combination of two or more of these.
  • the bus 604 may include one or more buses.
  • the present application also provides a server.
  • the hardware structure of the server is similar to the terminal device 600 in the above-mentioned embodiment. It may include a memory, a processor, and a computer program stored on the memory and running on the processor. Refer to the description of the hardware structure of the terminal device in the foregoing embodiment, which will not be repeated here.
  • the processor runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the application function configuration method applied to the server in the foregoing embodiment.
  • the server may also include a communication interface and a bus.
  • the memory, the processor, and the communication interface are connected through the bus and complete the communication between each other.
  • the present application also provides a computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, it can implement the application function configuration method or application applied to the terminal device in the above-mentioned embodiment The method of configuring the application function of the server.
  • Such a processor can be, but is not limited to, a general-purpose processor, a dedicated processor, a special application processor, or a field programmable logic circuit. It can also be understood that each block in the block diagram and/or flowchart and the combination of the blocks in the block diagram and/or flowchart can also be implemented by dedicated hardware that performs specified functions or actions, or can be implemented by dedicated hardware and A combination of computer instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

本申请提供了一种应用功能配置方法、终端设备、服务器及存储介质, 涉及数据处理领域。该方法包括: 向管理服务器发送查询请求消息, 查询请求消息包括终端设备的硬件标识, 管理服务器存储有硬件标识与算法插件的对应关系; 从插件管理服务器下载目标算法插件, 插件管理服务器包括管理服务器或云端服务器, 插件管理服务器存储有至少一个算法插件, 算法插件用于实现应用的功能, 目标算法插件为与查询请求消息中硬件标识对应的算法插件; 加载目标算法插件。利用本申请的技术方案能够提高应用功能在终端设备实现的通用性。

Description

应用功能配置方法、终端设备、服务器及存储介质
相关申请的交叉引用
本申请要求享有于2020年04月27日提交的名称为“应用功能配置方法、终端设备、服务器及存储介质”的中国专利申请202010344072.3的优先权，该申请的全部内容通过引用并入本文中。
技术领域
本申请属于数据处理领域，尤其涉及一种应用功能配置方法、终端设备、服务器及存储介质。
背景技术
随着电子信息技术的逐渐发展，电子信息技术应用的领域也越来越广泛。终端设备可通过运行应用程序来实现各种功能。但由于终端设备的多样化，终端设备只能运行自身支持的应用程序。不同的终端设备可采用不同的硬件，使得实现同一功能的应用程序对不同终端设备具有排他性。
例如，实现人脸支付功能对于采用活体检测算法A1的终端设备B1配置的应用程序C1，并不能在采用活体检测算法A2的终端设备B2上运行。实现同一功能的应用程序对不同终端设备的排他性，降低了应用功能在终端设备实现的通用性。
发明内容
本申请实施例提供了一种应用功能配置方法、终端设备、服务器及存储介质，能够提高应用功能在终端设备实现的通用性。
第一方面，本申请实施例提供一种应用功能配置方法，应用于终端设备，该方法包括：向管理服务器发送查询请求消息，查询请求消息包括终端设备的硬件标识，管理服务器存储有硬件标识与算法插件的对应关系； 插件管理服务器获取目标算法插件，其中，插件管理服务器包括管理服务器或云端服务器，插件管理服务器存储有至少一个算法插件，算法插件用于实现应用的功能，目标算法插件为与查询请求消息中硬件标识对应的算法插件；加载目标算法插件。
第二方面，本申请实施例提供一种应用功能配置方法，应用于服务器，服务器存储有硬件标识与算法插件的对应关系；该方法包括：接收终端设备发送的查询请求消息，查询请求消息包括终端设备的硬件标识；根据存储的硬件标识与算法插件的对应关系，向终端设备发送目标算法插件或用于指示目标算法插件的查询应答消息，目标算法插件为与查询请求消息中硬件标识对应的算法插件。
第三方面，本申请实施例提供一种终端设备，包括：发送模块，用于向管理服务器发送查询请求消息，查询请求消息包括终端设备的硬件标识，管理服务器存储有硬件标识与算法插件的对应关系；接收模块，用于从插件管理服务器获取目标算法插件，其中，插件管理服务器包括管理服务器或云端服务器，插件管理服务器存储有至少一个算法插件，算法插件用于实现应用的功能，目标算法插件为与查询请求消息中硬件标识对应的算法插件；加载模块，用于加载目标算法插件。
第四方面，本申请实施例提供一种服务器，包括：存储模块，用于存储硬件标识与算法插件的对应关系；接收模块，用于接收终端设备发送的查询请求消息，查询请求消息包括终端设备的硬件标识；发送模块，用于根据存储的硬件标识与算法插件的对应关系，向终端设备发送目标算法插件或用于指示目标算法插件的查询应答消息，目标算法插件为与查询请求消息中硬件标识对应的算法插件。
第五方面，本申请实施例提供一种终端设备，包括处理器、存储器及存储在存储器上并可在处理器上运行的计算机程序，计算机程序被处理器执行时实现第一方面的技术方案中的应用功能配置方法。
第六方面，本申请实施例提供一种服务器，包括处理器、存储器及存储在存储器上并可在处理器上运行的计算机程序，计算机程序被处理器执行时实现第二方面的技术方案中的应用功能配置方法。
第七方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质上存储计算机程序，计算机程序被处理器执行时实现第一方面的技术方案中的应用功能配置方法或第二方面的技术方案中的应用功能配置方法。
本申请实施例提供一种应用功能配置方法、终端设备、服务器及存储介质，终端设备可向管理服务器发送包括该终端设备的硬件标识的查询请求消息，以使得根据硬件标识与算法插件的对应关系，终端设备能够从管理服务器或云端服务器获取到与查询请求消息中硬件标识对应的算法插件即目标算法插件，加载该目标算法插件，以实现目标应用的功能。在不同的移动终端上运行同一款应用，通过终端设备与管理服务器，或者，通过终端设备、管理服务器和云端服务器的交互，能够为移动终端自身配置适用的算法插件，使得实现同一功能的应用不再具有排他性，提高了应用功能在终端设备实现的通用性。
附图说明
从下面结合附图对本申请的具体实施方式的描述中可以更好地理解本申请。其中，相同或相似的附图标记表示相同或相似的特征。
图1为本申请实施例提供的应用功能配置方法的应用场景的一示例的示意图；
图2为本申请实施例提供的应用功能配置方法的应用场景的另一示例的示意图；
图3为本申请提供的应用于终端设备的应用功能配置方法的一实施例的流程图；
图4为本申请提供的应用于终端设备的应用功能配置方法的另一实施例的流程图；
图5为本申请提供的应用于终端设备的应用功能配置方法的又一实施例的流程图；
图6为本申请提供的应用于服务器的应用功能配置方法的一实施例的流程图；
图7为本申请提供的应用于服务器的应用功能配置方法的另一实施例的流程图；
图8为本申请提供的终端设备的一实施例的结构示意图；
图9为本申请提供的终端设备的另一实施例的结构示意图；
图10为本申请提供的服务器的一实施例的结构示意图；
图11为本申请提供的服务器的另一实施例的结构示意图；
图12为本申请提供的终端设备的一实施例的硬件结构示意图。
具体实施方式
下面将详细描述本申请的各个方面的特征和示例性实施例。在下面的详细描述中，提出了许多具体细节，以便提供对本申请的全面理解。但是，对于本领域技术人员来说很明显的是，本申请可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本申请的示例来提供对本申请的更好的理解。本申请决不限于下面所提出的任何具体配置和算法，而是在不脱离本申请的精神的前提下覆盖了元素、部件和算法的任何修改、替换和改进。在附图和下面的描述中，没有示出公知的结构和技术，以便避免对本申请造成不必要的模糊。
本申请提供一种应用功能配置方法、终端设备、服务器及存储介质，可应用于为终端设备进行应用功能配置的场景中。应用功能为终端设备中安装的应用的功能，应用功能的类别在此并不限定。例如，应用功能可包括生物识别应用功能、人脸支付应用功能、生物识别打卡应用功能、地图定位应用功能、文件编辑应用功能等。
图1为本申请实施例提供的应用功能配置方法的应用场景的一示例的示意图。如图1所示，应用功能配置系统可包括终端设备100和管理服务器200。其中，终端设备100可包括手机、电脑、平板电脑、闸机以及其他终端设备，在此并不限定。终端设备100中安装有应用，该应用运行，则可实现该应用对应的功能。管理服务器200存储有硬件标识与算法插件的对应关系。具体地，硬件标识与算法插件的对应关系可实现为硬件标识与算法插件的下载地址的对应关系，或者，实现为硬件标识与算法插件的 插件标识的对应关系，在此并不限定。管理服务器200还可存储有算法插件。终端设备100可与管理服务器200进行交互。
图2为本申请实施例提供的应用功能配置方法的应用场景的另一示例的示意图。如图2所示，应用功能配置系统可包括终端设备100、管理服务器200和云端服务器300。其中，终端设备100的说明可参见图1所示的终端设备的相关说明，在此不再赘述。管理服务器200存储有硬件标识与算法插件的对应关系。具体地，硬件标识与算法插件的对应关系可实现为硬件标识与算法插件的下载地址的对应关系，或者，实现为硬件标识与算法插件的插件标识的对应关系，在此并不限定。云端服务器300可设置在云端，存储有算法插件。终端设备100、管理服务器200、云端服务器300三者之间可进行交互。
本申请提供一种应用功能配置方法，可应用于终端设备。图3为本申请提供的应用于终端设备的应用功能配置方法的一实施例的流程图。如图3所示，该应用功能配置方法可包括步骤S401至步骤S403。
在步骤S401中，向管理服务器发送查询请求消息。
其中，可以在终端设备中的目标应用安装后的首次启动的情况下，向管理服务器发送查询请求消息；也可在终端设备中的目标应用每次启动的情况下，向管理服务器发送查询请求消息；还可在终端设备中的目标应用自定义的某一次或某几次启动的情况下，向管理服务器发送查询请求消息，在此并不限定。目标应用为终端设备安装的应用。在终端设备启动该目标应用时，可向管理服务器发送查询请求消息。查询请求消息包括终端设备的硬件标识。终端设备的硬件标识可标识终端设备，也可标识终端设备配置的相关部件。在一些示例中，终端设备的硬件标识可包括终端设备的型号和/或终端设备配置的相关部件的型号。终端设备的硬件标识也可包括该终端设备的指纹信息。硬件标识具体可根据终端设备设定，在此并不限定。例如，终端设备为生物识别终端，则硬件标识可包括该生物识别终端的型号和生物识别终端配置的摄像组件的型号。
管理服务器存储有硬件标识与算法插件的对应关系。对于具有对应关系的硬件标识和算法插件，算法插件在该硬件标识标识的终端设备中可以 运行。也就是说，若某硬件标识标识的终端设备支持某算法插件的运行，则该硬件标识与该算法插件具有对应关系。
在步骤S402中，从插件管理服务器获取目标算法插件。
其中，插件管理服务器包括管理服务器或云端服务器。插件管理服务器存储有至少一个算法插件。算法插件用于实现应用的功能。目标算法插件为与查询请求消息中硬件标识对应的算法插件。具体地，目标算法插件为在管理服务器存储的硬件标识与算法插件的对应关系中，与查询请求消息中硬件标识对应的算法插件。
在一些示例中，插件管理服务器包括管理服务器。管理服务器接收查询请求消息，可根据自身存储的硬件标识与算法插件的对应关系，以及查询请求消息中的硬件标识，向终端设备推送目标算法插件。终端设备从管理服务器获取到目标算法插件。或者，管理服务器接收查询请求消息，向存储有算法插件的云端服务器发送用于指示目标算法插件的消息，以使云端服务器向管理服务器发送目标算法插件。管理服务器可将接收到的目标算法插件向终端设备推送。终端设备从管理服务器获取到目标算法插件。
在另一些示例中，插件管理服务器包括云端服务器。管理服务器在接收查询请求消息后，可向终端设备发送可用于指示目标算法插件的消息。终端设备可从云端服务器获取目标算法插件。或者，管理服务器在接收查询请求消息后，向云端服务器发送用于指示目标算法插件和终端设备的消息，以使云端服务器可向终端设备推送目标算法插件。终端设备可从云端服务器获取目标算法插件。
算法插件用于实现应用的功能。具体地，算法插件可具体实现为安卓应用程序包(Android application package，APK)、jar文件、rar文件或二进制文件(即bin文件)等，在此并不限定。插件管理服务器存储的不同算法插件可以为实现相同功能但算法不同的插件，也可为实现相同算法但版本不同的插件，也可为实现相同功能但适配终端厂商不同的插件，也可为实现相同功能但适配终端硬件不同的插件，还可为实现不同功能的插件，在此并不限定。
终端设备从插件管理服务器获取的目标算法插件可以是首次对实现目 标应用的功能的算法插件，也可以是目标应用的功能的更新的算法插件。终端设备从插件管理服务器获取目标算法插件，可采用差分下载技术、断点续传技术等，在此并不限定。采用差分下载技术、断点续传技术等获取目标算法插件，可提高下载效率，节省下载占用的带宽，减小需要下载的数据量。若采用差分下载技术、断点续传技术等获取目标算法插件，需要将下载的数据组合成完整的算法插件，以使终端设备能够正常运行该算法插件，实现目标应用的功能。其中，差分下载技术常用于更新算法插件的场景中，即若要将终端设备中的当前版本的算法插件更替为其他版本的算法插件，只需从插件管理服务器中下载其他版本的算法插件与当前版本的算法插件的不同的部分即可。
在步骤S403中，加载目标算法插件。
具体地，可采用动态加载技术，加载目标算法插件。加载目标算法插件完成后，可实现目标应用的功能。加载的具体实现可根据终端设备的类型或终端设备中操作系统的类型确定，在此并不限定。例如，终端设备为安卓终端设备，则可利用安卓原生加载器或其他同类原理的技术实现目标算法插件的加载。
在一些示例中，终端设备还可从插件管理服务器获取目标算法插件的摘要。终端设备可基于目标算法插件和获取的目标算法插件的摘要，对获取的目标算法插件进行安全性校验。若安全性校验成功，则终端设备允许加载该目标算法插件。若安全性校验失败，则终端设备不允许加载该目标算法插件。通过安全性校验，可保证终端设备加载目标算法插件安全合法，提高终端设备运行应用的安全性。
在本申请实施例中，终端设备可向管理服务器发送包括该终端设备的硬件标识的查询请求消息，以使得根据硬件标识与算法插件的对应关系，终端设备能够从管理服务器或云端服务器获取到与查询请求消息中硬件标识对应的算法插件即目标算法插件，加载该目标算法插件，以实现目标应用的功能。在不同的移动终端上运行同一款应用，通过终端设备与管理服务器，或者，通过终端设备、管理服务器和云端服务器的交互，能够为移动终端自身配置适用的算法插件，使得实现同一功能的应用不再具有排他 性，提高了应用功能在终端设备实现的通用性。
采用本申请提供的应用功能配置方法，终端设备可实现各种不同的算法，终端设备自身的硬件也可根据需求自由组合，使得应用功能的实现可与不同类型的算法和硬件对接，提高了终端设备功能实现以及终端设备生产的灵活性。
在一些示例中，应用功能配置方法可应用于生物识别的场景中，目标应用可包括人脸识别应用。上述终端设备的硬件标识可包括终端标识和/或生物特征采集部件标识。终端标识可包括用于标识终端设备整体的标识，如终端设备的型号或终端设备的设备编码等，在此并不限定。生物特征采集部件标识用于标识终端设备配置的生物特征采集部件，可根据生物特征采集部件的标准接口获取生物特征采集部件标识。例如，在生物识别的人脸识别场景中，为了避免用户利用照片、硅胶模型或塑料模型等非生物物质对人脸识别造成干扰，可在人脸识别中增添活体检测流程。活体检测技术可包括结构光活体检测技术、飞行时间(Time of flight，TOF)活体检测技术、红外双目活体检测技术等，在此并不限定。对应地，生物特征采集部件可包括基于结构光的生物特征采集部件、基于TOF的生物特征采集部件、基于红外双目的生物特征采集部件中的一项或多项。基于结构光的生物特征采集部件具体可实现为基于结构光活体检测算法的摄像模组。基于TOF的生物特征采集部件具体可实现为基于TOF活体检测算法的摄像模组。基于红外双目的生物特征采集部件具体可实现为基于红外双目活体检测算法的摄像模组。对应地，在生物特征采集部件包括基于结构光的生物特征采集部件的情况下，终端设备获取的目标算法插件为该终端设备能够支持的用于实现结构光活体检测算法的算法插件。在生物特征采集部件包括基于TOF的生物特征采集部件的情况下，终端设备获取的目标算法插件为该终端设备能够支持的用于实现TOF活体检测算法的算法插件。在生物特征采集部件包括基于红外双目的生物特征采集部件的情况下，终端设备获取的目标算法插件为该终端设备能够支持的用于实现红外双目活体检测算法的算法插件。
图4为本申请提供的应用于终端设备的应用功能配置方法的另一实施 例的流程图。其中，插件管理服务器包括云端服务器。图4与图3的不同之处在于，图4所示的应用功能配置方法还可包括步骤S404，图3中的步骤S402可细化为图4中的步骤S4021。
在步骤S404中，接收管理服务器发送的查询应答消息。
查询应答消息是管理服务器基于查询请求消息生成的。查询应答消息用于指示目标算法插件。
在步骤S4021中，从云端服务器获取目标算法插件。
云端服务器存储有至少一个算法插件。
在一些示例中，查询应答消息具体可包括云端服务器中目标算法插件的下载地址。终端设备可根据应答消息中目标算法插件的下载地址，从云端服务器下载目标算法插件。
在一些示例中，查询应答消息还可包括目标算法插件的摘要，或者，终端设备从云端服务器还可获取目标算法插件的摘要。终端设备可基于目标算法插件和获取的目标算法插件的摘要，对下载的目标算法插件进行安全性校验。若安全性校验成功，则终端设备允许加载该目标算法插件。若安全性校验失败，则终端设备不允许加载该目标算法插件。通过安全性校验，可保证终端设备加载目标算法插件安全合法，提高终端设备运行应用的安全性。
在应用功能配置方法可应用于生物识别的场景中，对应地，在生物特征采集部件包括基于结构光的生物特征采集部件的情况下，终端设备接收的查询应答消息指示该终端设备能够支持的用于实现结构光活体检测算法的算法插件。在生物特征采集部件包括基于TOF的生物特征采集部件的情况下，终端设备接收的查询应答消息指示该终端设备能够支持的用于实现TOF活体检测算法的算法插件。在生物特征采集部件包括基于红外双目的生物特征采集部件的情况下，终端设备接收的查询应答消息指示该终端设备能够支持的用于实现红外双目活体检测算法的算法插件。
在一些示例中，管理服务器存储有算法插件的版本与算法插件的对应关系。管理服务器中可存储有硬件标识、算法插件的版本、算法插件的对应关系，管理服务器中还可存储更多信息之间的对应关系，在此并不限 定。
终端设备可根据自身运行情况或用户的输入操作，确定目标应用所需的算法插件的版本。查询请求消息还可包括用于表征终端设备请求的算法插件版本的版本请求信息。具体地，版本请求信息可为版本号等，在此并不限定。从插件管理服务器获取的所述目标算法插件为与版本请求信息对应的目标算法插件。
在插件管理服务器包括云端服务器，终端设备接收管理服务器发送的查询应答消息的情况下，查询应答消息还可用于指示与版本请求信息对应的目标算法插件，即查询应答消息可用于指示终端设备请求的算法插件版本的目标算法插件。
图5为本申请提供的应用于终端设备的应用功能配置方法的又一实施例的流程图。图5与图3的不同之处在于，图5所示的应用功能配置方法还可包括步骤S405和步骤S406，图3中的步骤S403可具体细化为图5中的步骤S4031。
在步骤S405中，在终端设备中目标应用启动的情况下，检测终端设备是否存储有用于实现目标应用的功能的算法插件。
若目标应用在终端设备中不是初次启动，在之前目标应用启动的情况下获取的目标算法插件可存储在终端设备中，该目标算法插件可实现目标应用的功能。
在步骤S406中，在终端设备存储有用于实现目标应用的功能的算法插件的情况下，加载终端设备存储的用于实现目标应用的功能的算法插件。
若检测到终端设备存储有用于实现目标应用的功能的算法插件，为了减少应用运行前的等待时间，可直接加载存储的用于实现目标应用的功能的算法插件。为了保证目标应用运行的安全性，还可先对终端设备中存储的用于实现目标应用的功能的算法插件进行安全性校验，若安全性校验成功，终端设备再加载该算法插件。
若目标应用在终端设备中是初次启动，则可执行上述实施例中的步骤S401至步骤S403，在此不再赘述。
在步骤S4031中，在终端设备中目标应用下一次启动的情况下，加载最新版本的目标算法插件。
在一些示例下，终端设备中存储有用于实现目标应用的功能的算法插件，但该算法插件并不是最新版本的算法插件，则可通过查询请求消息，或者，通过查询请求消息和查询应答消息，请求最新版本的目标算法插件。具体地，可从插件管理服务器获取最新版本的目标算法插件，或者，利用查询应答消息指示最新版本的目标算法插件。为了不影响目标应用当前的运行，减小下载等待时间，终端设备可先加载终端设备中存储的用于实现目标应用的功能的算法插件，运行目标应用。在运行目标应用的过程中，通过查询请求消息，或者，通过查询请求消息和查询应答消息，请求最新版本的目标算法插件，从插件管理服务器获取最新版本的目标算法插件，在目标应用下一次启动时，加载最新版本的目标算法插件。
在一些示例中，查询请求消息还包括灰度发布参考信息。灰度发布参考信息用于管理服务器进行算法插件的灰度发布。具体地，灰度发布参考信息可包括终端设备硬件信息、终端设备地理位置信息、终端设备用户信息、终端设备中目标应用使用频率信息等信息中的一项或多项，在此并不限定。管理服务器可根据灰度发布参考信息，确定对终端设备的目标应用所对应的算法插件的灰度发布，设定硬件标识与算法插件的对应关系、算法插件的版本与算法插件的对应关系等。
本申请还提供了一种应用功能配置方法，可应用于服务器，这里的服务器具体可指上述实施例中的管理服务器，该服务器存储有硬件标识与算法插件的对应关系。图6为本申请提供的应用于服务器的应用功能配置方法的一实施例的流程图。如图6所示，该应用功能配置方法可包括步骤S501至步骤S502。
在步骤S501中，接收终端设备发送的查询请求消息。
其中，查询请求消息包括终端设备的硬件标识。查询请求消息的具体内容可参见上述实施例中的相关说明部分，在此不再赘述。
在步骤S502中，根据存储的硬件标识与算法插件的对应关系，向终端设备发送目标算法插件或用于指示目标算法插件的查询应答消息。
其中，硬件标识可标识的终端设备支持与该硬件标识具有对应关系的算法插件的加载和运行。具体地，服务器可根据存储的硬件标识与算法插件的对应关系，确定与查询请求消息中硬件标识具有对应关系的算法插件，将该算法插件作为目标算法插件，即目标算法插件为与查询请求消息中硬件标识对应的算法插件。查询应答消息用于指示目标算法插件。
服务器可根据存储的硬件标识与算法插件的查询应答消息，以及查询请求消息中的硬件标识，生成查询应答消息。
在本申请实施例中，服务器存储有硬件标识与算法插件的对应关系。对于不同的终端设备，均可通过终端设备发送的查询请求消息中的硬件标识，确定该终端设备适配的算法插件即目标算法插件，并能够将目标算法插件向终端设备发送，或者，将能够指示目标算法插件的查询应答消息向终端设备发送，以使终端设备可获取得到与自身适配的算法插件即目标算法插件。在不同的移动终端上运行同一款应用，通过服务器与终端设备的交互，能够为移动终端自身配置适用的算法插件，使得实现同一功能的应用不再具有排他性，提高了应用功能在终端设备实现的通用性。
在一些示例中，终端设备的硬件标识包括终端标识和/或生物特征采集部件标识。生物特征采集部件标识用于标识终端设备配置的生物特征采集部件。其中，关于终端标识、生物特征采集部件标识、生物特征采集部件的具体内容可参见上述实施例中的相关说明部分，在此不再赘述。
在一些示例中，服务器还存储有算法插件的版本与算法插件的对应关系、算法插件的摘要、算法插件的下载地址、算法插件的更新类型中的一项或多项。
具体地，服务器可通过存储硬件标识、算法插件、算法插件的版本的对应关系，实现硬件标识与算法插件的对应关系的存储和算法插件的版本与算法插件的对应关系的存储。
算法插件的摘要可用于终端设备对下载的算法插件进行安全性校验。算法插件的更新类型可包括强制更新、无感更新等，在此并不限定。
在一些示例中，服务器存储有算法插件的版本与算法插件的对应关系。查询请求消息还包括用于表征终端设备请求的算法插件版本的版本请 求信息。对应地，服务器可向终端设备发送的目标算法插件为与版本请求信息对应的目标算法插件。或者，查询应答消息可用于指示与该本请求信息对应的目标算法插件。
在一些示例中，向终端设备发送的目标算法插件为最新版本的目标算法插件。或者，查询应答消息用于指示最新版本的目标算法插件。通过向终端设备发送用于指示最新版本的目标算法插件，以实现终端设备的目标应用的更新。
图7为本申请提供的应用于服务器的应用功能配置方法的另一实施例的流程图。图7与图6的不同之处在于，图7所示的应用功能配置方法还包括步骤S503。
在步骤S503中，根据灰度发布参考信息，对终端设备进行算法插件的灰度发布。
上述实施例中的查询请求消息中可包括灰度发布参考信息。灰度发布参考信息的具体内容可参见上述实施例中的相关说明部分，在此不再赘述。
服务器可根据灰度发布参考信息，确定灰度发布策略。例如，确定为各个终端设备适配的算法插件的版本。服务器可根据灰度发布参考信息，为划分的不同范围的用户分配不同版本的算法插件，以满足不同用户的业务需求。
本申请还提供一种终端设备。图8为本申请提供的终端设备的一实施例的结构示意图。如图8所示，该终端设备100可包括发送模块101、接收模块102和加载模块103。
发送模块101用于向管理服务器发送查询请求消息。
查询请求消息包括终端设备的硬件标识。管理服务器存储有硬件标识与算法插件的对应关系；
接收模块102用于从插件管理服务器获取目标算法插件。
插件管理服务器包括管理服务器或云端服务器。插件管理服务器存储有至少一个算法插件。算法插件用于实现应用的功能。目标算法插件为与查询请求消息中硬件标识对应的算法插件。
加载模块103用于加载目标算法插件。
在本申请实施例中，终端设备可向管理服务器发送包括该终端设备的硬件标识的查询请求消息，以使得根据硬件标识与算法插件的对应关系，终端设备能够从管理服务器或云端服务器获取到与查询请求消息中硬件标识对应的算法插件即目标算法插件，加载该目标算法插件，以实现目标应用的功能。在不同的移动终端上运行同一款应用，通过终端设备与管理服务器，或者，通过终端设备、管理服务器和云端服务器的交互，能够为移动终端自身配置适用的算法插件，使得实现同一功能的应用不再具有排他性，提高了应用功能在终端设备实现的通用性。
在一些示例中，终端设备的硬件标识包括终端标识和/或生物特征采集部件标识。生物特征采集部件标识用于标识终端设备配置的生物特征采集部件。
在一些示例中，插件管理服务器包括云端服务器。上述接收模块102还可用于接收管理服务器发送的查询应答消息。
其中，查询应答消息用于指示目标算法插件。
在一些示例中，查询请求消息还包括用于表征终端设备请求的算法插件版本的版本请求信息。管理服务器存储有算法插件的版本与算法插件的对应关系。其中，从所述插件管理服务器获取的所述目标算法插件为与版本请求信息对应的目标算法插件。
在接收模块102还用于接收管理服务器发送的查询应答消息的情况下，查询应答消息可用于指示与版本请求信息对应的目标算法插件。
图9为本申请提供的终端设备的另一实施例的结构示意图。图9与图8的不同之处在于，图9所示的终端设备100还可包括检测模块104。
检测模块104用于在终端设备中目标应用启动的情况下，检测终端设备是否存储有用于实现目标应用的功能的算法插件。
上述实施例中的加载模块103还可用于在终端设备存储有用于实现目标应用的功能的算法插件的情况下，加载终端设备存储的用于实现目标应用的功能的算法插件。
在一些示例中，从插件管理服务器获取的目标算法插件为最新版本的 目标算法插件。或者，在接收模块102还用于接收管理服务器发送的查询应答消息的情况下，查询应答消息可用于指示最新版本的目标算法插件。
加载模块103可用于在终端设备中目标应用下一次启动的情况下，加载最新版本的目标算法插件。
在一些示例中，查询请求消息还包括灰度发布参考信息。灰度发布参考信息用于管理服务器进行算法插件的灰度发布。
本申请还提供一种服务器。图10为本申请提供的服务器的一实施例的结构示意图。如图10所示，该服务器200可包括存储模块201、接收模块202和发送模块203。
存储模块201可用于存储硬件标识与算法插件的对应关系。
接收模块202可用于接收终端设备发送的查询请求消息。
查询请求消息包括终端设备的硬件标识。
发送模块203可用于根据存储的硬件标识与算法插件的对应关系，向终端设备发送目标算法插件或用于指示目标算法插件的查询应答消息。
目标算法插件为与查询请求消息中硬件标识对应的算法插件。
查询应答消息可由服务器200中的生成模块(图中未标示出)根据存储的硬件标识与算法插件的查询应答消息，以及查询请求消息中的硬件标识生成。
在本申请实施例中，服务器存储有硬件标识与算法插件的对应关系。对于不同的终端设备，均可通过终端设备发送的查询请求消息中的硬件标识，确定该终端设备适配的算法插件即目标算法插件，并能够将目标算法插件向终端设备发送，或者，将能够指示目标算法插件的查询应答消息向终端设备发送，以使终端设备可获取得到与自身适配的算法插件即目标算法插件。在不同的移动终端上运行同一款应用，通过服务器与终端设备的交互，能够为移动终端自身配置适用的算法插件，使得实现同一功能的应用不再具有排他性，提高了应用功能在终端设备实现的通用性。
在一些示例中，终端设备的硬件标识包括终端标识和/或生物特征采集部件标识。生物特征采集部件标识用于标识终端设备配置的生物特征采集部件。
在一些示例中，存储模块201还可用于存储算法插件的版本与算法插件的对应关系、算法插件的摘要、算法插件的下载地址、算法插件的更新类型中的一项或多项。
在一些示例中，存储模块201还存储有算法插件的版本与算法插件的对应关系。查询请求消息还包括用于表征终端设备请求的算法插件版本的版本请求信息。其中，向终端设备发送的目标算法插件为与版本请求信息对应的目标算法插件。或者，查询应答消息用于指示与版本请求信息对应的目标算法插件。
在一些示例中，向终端设备发送的目标算法插件为最新版本的目标算法插件。或者，查询应答消息用于指示最新版本的目标算法插件。
图11为本申请提供的服务器的另一实施例的结构示意图。图11与图10的不同之处在于，图11所示的服务器还可包括灰度发布模块203。
查询请求消息还可包括灰度发布参考信息。灰度发布模块203可用于根据灰度发布参考信息，对终端设备进行算法插件的灰度发布。
图12为本申请提供的终端设备的一实施例的硬件结构示意图。如图12所示，终端设备600包括存储器601、处理器602及存储在存储器601上并可在处理器602上运行的计算机程序。
在一个示例中，上述处理器602可以包括中央处理器(CPU)，或者特定集成电路(ASIC)，或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器601可以包括用于数据或指令的大容量存储器。举例来说而非限制，存储器601可包括HDD、软盘驱动器、闪存、光盘、磁光盘、磁带或通用串行总线(USB)驱动器或者两个或更多个以上这些的组合。在合适的情况下，存储器601可包括可移除或不可移除(或固定)的介质。在合适的情况下，存储器601可在终端热点开启终端设备600的内部或外部。在特定实施例中，存储器601是非易失性固态存储器。在特定实施例中，存储器601包括只读存储器(ROM)。在合适的情况下，该ROM可以是掩模编程的ROM、可编程ROM(PROM)、可擦除PROM(EPROM)、电可擦除 PROM(EEPROM)、电可改写ROM(EAROM)或闪存或者两个或更多个以上这些的组合。
处理器602通过读取存储器601中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序，以用于实现上述实施例中应用于终端设备的应用功能配置方法。
在一个示例中，终端设备600还可包括通信接口603和总线604。其中，如图12所示，存储器601、处理器602、通信接口603通过总线604连接并完成相互间的通信。
通信接口603，主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。也可通过通信接口603接入输入设备和/或输出设备。
总线604包括硬件、软件或两者，将终端设备600的部件彼此耦接在一起。举例来说而非限制，总线604可包括加速图形端口(AGP)或其他图形总线、增强工业标准架构(EISA)总线、前端总线(FSB)、超传输(HT)互连、工业标准架构(ISA)总线、无限带宽互连、低引脚数(LPC)总线、存储器总线、微信道架构(MCA)总线、外围组件互连(PCI)总线、PCI-Express(PCI-X)总线、串行高级技术附件(SATA)总线、视频电子标准协会局部(VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下，总线604可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线，但本申请考虑任何合适的总线或互连。
本申请还提供了一种服务器，该服务器的硬件结构与上述实施例中的终端设备600类似，可包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，具体内容可参见上述实施例中终端设备的硬件结构说明，在此不再赘述。处理器通过读取存储器中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序，以用于实现上述实施例中应用于服务器的应用功能配置方法。
服务器还可包括通信接口和总线。存储器、处理器、通信接口通过总线连接并完成相互间的通信，具体内容可参见上述实施例中终端设备的硬件结构说明，在此不再赘述。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时可实现上述实施例中的应用于终端设备的应用功能配置方法或应用于服务器的应用功能配置方法。
需要明确的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同或相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。对于终端设备实施例、服务器实施例和计算机可读存储介质实施例而言，相关之处可以参见方法实施例的说明部分。本申请并不局限于上文所描述并在图中示出的特定步骤和结构。本领域的技术人员可以在领会本申请的精神之后，作出各种改变、修改和添加，或者改变步骤之间的顺序。并且，为了简明起见，这里省略对已知方法技术的详细描述。
上面参考根据本申请的实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本申请的各方面。应当理解，流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其它可编程数据处理装置的处理器，以产生一种机器，使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑电路。还可理解，框图和/或流程图中的每个方框以及框图和/或流程图中的方框的组合，也可以由执行指定的功能或动作的专用硬件来实现，或可由专用硬件和计算机指令的组合来实现。
本领域技术人员应能理解，上述实施例均是示例性而非限制性的。在不同实施例中出现的不同技术特征可以进行组合，以取得有益效果。本领域技术人员在研究附图、说明书及权利要求书的基础上，应能理解并实现所揭示的实施例的其他变化的实施例。在权利要求书中，术语“包括”并不排除其他装置或步骤；不定冠词“一个”不排除多个；术语“第一”、“第二”用于标示名称而非用于表示任何特定的顺序。权利要求中的任何附图标记均不应被理解为对保护范围的限制。权利要求中出现的多个部分 的功能可以由一个单独的硬件或软件模块来实现。某些技术特征出现在不同的从属权利要求中并不意味着不能将这些技术特征进行组合以取得有益效果。

Claims (18)

  1. 一种应用功能配置方法，应用于终端设备，所述方法包括：
    向管理服务器发送查询请求消息，所述查询请求消息包括所述终端设备的硬件标识，所述管理服务器存储有硬件标识与算法插件的对应关系；
    从插件管理服务器获取目标算法插件，其中，所述插件管理服务器包括所述管理服务器或云端服务器，所述插件管理服务器存储有至少一个算法插件，所述算法插件用于实现应用的功能，所述目标算法插件为与所述查询请求消息中硬件标识对应的所述算法插件；
    加载所述目标算法插件。
  2. 根据权利要求1所述的方法，其中，所述终端设备的硬件标识包括终端标识和/或生物特征采集部件标识；
    所述生物特征采集部件标识用于标识所述终端设备配置的生物特征采集部件。
  3. 根据权利要求1所述的方法，其中，所述插件管理服务器包括所述云端服务器；
    在所述从插件管理服务器获取目标算法插件之前，还包括：
    接收所述管理服务器发送的查询应答消息，所述查询应答消息用于指示所述目标算法插件。
  4. 根据权利要求1所述的方法，其中，所述查询请求消息还包括用于表征所述终端设备请求的算法插件版本的版本请求信息，所述管理服务器存储有算法插件的版本与所述算法插件的对应关系；
    从所述插件管理服务器获取的所述目标算法插件为与所述版本请求信息对应的所述目标算法插件。
  5. 根据权利要求1所述的方法，还包括：
    在所述终端设备中目标应用启动的情况下，检测所述终端设备是否存储有用于实现所述目标应用的功能的算法插件；
    在所述终端设备存储有用于实现所述目标应用的功能的算法插件的情况下，加载所述终端设备存储的用于实现所述目标应用的功能的算法插 件。
  6. 根据权利要求5所述的方法，其中，从所述插件管理服务器获取的所述目标算法插件为最新版本的所述目标算法插件；
    所述加载所述目标算法插件，包括
    在所述终端设备中目标应用下一次启动的情况下，加载最新版本的所述目标算法插件。
  7. 根据权利要求1所述的方法，其中，所述查询请求消息还包括灰度发布参考信息，所述灰度发布参考信息用于所述管理服务器进行算法插件的灰度发布。
  8. 一种应用功能配置方法，应用于服务器，所述服务器存储有硬件标识与算法插件的对应关系；所述方法包括：
    接收终端设备发送的查询请求消息，所述查询请求消息包括所述终端设备的硬件标识；
    根据存储的硬件标识与算法插件的对应关系，向所述终端设备发送目标算法插件或用于指示所述目标算法插件的查询应答消息，所述目标算法插件为与所述查询请求消息中硬件标识对应的算法插件。
  9. 根据权利要求8所述的方法，其中，所述终端设备的硬件标识包括终端标识和/或生物特征采集部件标识；
    所述生物特征采集部件标识用于标识所述终端设备配置的生物特征采集部件。
  10. 根据权利要求8所述的方法，其中，所述服务器还存储有算法插件的版本与所述算法插件的对应关系、所述算法插件的摘要、所述算法插件的下载地址、所述算法插件的更新类型中的一项或多项。
  11. 根据权利要求8所述的方法，其中，所述服务器还存储有算法插件的版本与所述算法插件的对应关系；所述查询请求消息还包括用于表征所述终端设备请求的算法插件版本的版本请求信息；
    其中，向所述终端设备发送的所述目标算法插件为与所述版本请求信息对应的所述目标算法插件；
    或者，
    所述查询应答消息用于指示与所述版本请求信息对应的所述目标算法插件。
  12. 根据权利要求8所述的方法，其中，
    向所述终端设备发送的所述目标算法插件为最新版本的所述目标算法插件；
    或者，
    所述查询应答消息用于指示最新版本的所述目标算法插件。
  13. 根据权利要求8所述的方法，其中，所述查询请求消息还包括灰度发布参考信息；所述方法还包括：
    根据所述灰度发布参考信息，对所述终端设备进行所述算法插件的灰度发布。
  14. 一种终端设备，包括：
    发送模块，用于向管理服务器发送查询请求消息，所述查询请求消息包括所述终端设备的硬件标识，所述管理服务器存储有硬件标识与算法插件的对应关系；
    接收模块，用于从插件管理服务器获取目标算法插件，其中，所述插件管理服务器包括所述管理服务器或云端服务器，所述插件管理服务器存储有至少一个算法插件，所述算法插件用于实现应用的功能，所述目标算法插件为与所述查询请求消息中硬件标识对应的所述算法插件；
    加载模块，用于加载所述目标算法插件。
  15. 一种服务器，包括：
    存储模块，用于存储硬件标识与算法插件的对应关系；
    接收模块，用于接收终端设备发送的查询请求消息，所述查询请求消息包括所述终端设备的硬件标识；
    发送模块，用于根据存储的硬件标识与算法插件的对应关系，向所述终端设备发送目标算法插件或用于指示所述目标算法插件的查询应答消息，所述目标算法插件为与所述查询请求消息中硬件标识对应的算法插件。
  16. 一种终端设备，包括处理器、存储器及存储在所述存储器上并可 在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至7中任意一项所述的应用功能配置方法。
  17. 一种服务器，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求8至13中任意一项所述的应用功能配置方法。
  18. 一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至7中任意一项所述的应用功能配置方法或如权利要求8至13中任意一项所述的应用功能配置方法。
PCT/CN2021/086729 2020-04-27 2021-04-12 应用功能配置方法、终端设备、服务器及存储介质 WO2021218621A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010344072.3 2020-04-27
CN202010344072.3A CN111596967A (zh) 2020-04-27 2020-04-27 应用功能配置方法、终端设备、服务器及存储介质

Publications (1)

Publication Number Publication Date
WO2021218621A1 true WO2021218621A1 (zh) 2021-11-04

Family

ID=72181269

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/086729 WO2021218621A1 (zh) 2020-04-27 2021-04-12 应用功能配置方法、终端设备、服务器及存储介质

Country Status (3)

Country Link
CN (1) CN111596967A (zh)
TW (1) TWI765575B (zh)
WO (1) WO2021218621A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114756271A (zh) * 2022-04-29 2022-07-15 深圳市欧瑞博科技股份有限公司 界面更新方法、装置及电子设备

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110764836B (zh) 2019-09-18 2024-02-09 华为技术有限公司 插件实现的方法和插件实现的系统
CN111596967A (zh) * 2020-04-27 2020-08-28 中国银联股份有限公司 应用功能配置方法、终端设备、服务器及存储介质
CN114553855B (zh) * 2020-11-25 2024-04-05 北京奇艺世纪科技有限公司 插件灰度发布方法、装置、电子设备及存储介质
CN112764995B (zh) * 2021-01-26 2023-04-07 山东云海国创云计算装备产业创新中心有限公司 一种服务器硬件资源监控方法、装置和介质
CN113656093A (zh) * 2021-08-02 2021-11-16 珠海格力电器股份有限公司 插件配置方法、装置、设备及存储介质
CN114090113B (zh) * 2021-10-27 2023-11-10 北京百度网讯科技有限公司 数据源处理插件动态加载的方法、装置、设备及存储介质
CN114816571B (zh) * 2022-04-15 2023-06-16 西安广和通无线通信有限公司 外挂闪存的方法、装置、设备及存储介质
CN115474000A (zh) * 2022-08-16 2022-12-13 支付宝(杭州)信息技术有限公司 数据处理方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120054841A1 (en) * 2010-08-24 2012-03-01 Verizon Patent And Licensing Inc. Application registration, authorization, and verification
CN104125206A (zh) * 2013-04-27 2014-10-29 腾讯科技（深圳）有限公司 一种客户端的硬件环境适配方法、装置、服务器及系统
CN104702982A (zh) * 2013-12-20 2015-06-10 杭州海康威视数字技术股份有限公司 一种视频分析设备的算法配置方法和系统
CN109729116A (zh) * 2017-10-30 2019-05-07 腾讯科技（深圳）有限公司 插件信息的传输方法、装置、存储介质及电子装置
CN110688270A (zh) * 2019-09-27 2020-01-14 北京百度网讯科技有限公司 视频元素资源处理方法、装置、设备及存储介质
CN111596967A (zh) * 2020-04-27 2020-08-28 中国银联股份有限公司 应用功能配置方法、终端设备、服务器及存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20160016555A (ko) * 2014-07-31 2016-02-15 삼성전자주식회사 단말기를 제어하는 방법 및 그 단말기
WO2018078495A1 (en) * 2016-10-26 2018-05-03 Simpleway Technologies Ltd. System and method for device interoperability and synchronization
CN108984224A (zh) * 2018-06-13 2018-12-11 中国平安人寿保险股份有限公司 一种插件管理方法、计算机可读存储介质及终端设备
TWM574283U (zh) * 2018-11-19 2019-02-11 玉山商業銀行股份有限公司 利用活體及人臉辨識進行無卡交易開通的交易系統及自動櫃員機
TWM589850U (zh) * 2018-12-14 2020-01-21 兆豐國際商業銀行股份有限公司 網路銀行登入系統
US11216404B2 (en) * 2019-08-05 2022-01-04 Intel Corporation Mechanism for device interoperability of switches in computer buses

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120054841A1 (en) * 2010-08-24 2012-03-01 Verizon Patent And Licensing Inc. Application registration, authorization, and verification
CN104125206A (zh) * 2013-04-27 2014-10-29 腾讯科技（深圳）有限公司 一种客户端的硬件环境适配方法、装置、服务器及系统
CN104702982A (zh) * 2013-12-20 2015-06-10 杭州海康威视数字技术股份有限公司 一种视频分析设备的算法配置方法和系统
CN109729116A (zh) * 2017-10-30 2019-05-07 腾讯科技（深圳）有限公司 插件信息的传输方法、装置、存储介质及电子装置
CN110688270A (zh) * 2019-09-27 2020-01-14 北京百度网讯科技有限公司 视频元素资源处理方法、装置、设备及存储介质
CN111596967A (zh) * 2020-04-27 2020-08-28 中国银联股份有限公司 应用功能配置方法、终端设备、服务器及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114756271A (zh) * 2022-04-29 2022-07-15 深圳市欧瑞博科技股份有限公司 界面更新方法、装置及电子设备
CN114756271B (zh) * 2022-04-29 2023-07-28 深圳市欧瑞博科技股份有限公司 界面更新方法、装置及电子设备

Also Published As

Publication number Publication date
TWI765575B (zh) 2022-05-21
TW202141474A (zh) 2021-11-01
CN111596967A (zh) 2020-08-28

Similar Documents

Publication Publication Date Title
WO2021218621A1 (zh) 应用功能配置方法、终端设备、服务器及存储介质
US10452376B2 (en) Method for identifying file and mobile terminal
US11228901B2 (en) Method for installing subscriber profile and electronic device therefor
CN105357204B (zh) 生成终端识别信息的方法及装置
CN109634628B (zh) 在可信存储装置上生成校验和以加速认证
CN111343267B (zh) 一种配置的管理方法及系统
CN111259364B (zh) 一种使用国密加密卡的方法、装置、设备及存储介质
CN111338716A (zh) 基于规则引擎的数据处理方法、装置及终端设备
CN111722857A (zh) 软件开发工具包的更新方法、装置、电子设备及存储介质
CN117097682A (zh) 设备接入方法、装置、设备及存储介质
CN114637969A (zh) 目标对象的鉴权方法及装置
CN111339107B (zh) 比对源数据同步方法、装置、电子设备及存储介质
US11934853B2 (en) Electronic device and operating method thereof
CN114090127A (zh) 电子设备及其配置文件的加载方法和介质
CN110531991B (zh) 一种通用性烧录平台的实现方法和系统
CN109788054B (zh) 一种分布式应用协调服务节点的配置方法、服务器及介质
KR102540932B1 (ko) 차량의 업데이트 제공 장치 및 컴퓨터 기록 매체
US9189633B2 (en) Download management method and device based on android browser
US20150309788A1 (en) Function module modularizing method in data distribution service and modularizing apparatus thereof
CN114595106B (zh) 一种业务控制设备调测方法及装置
CN116828588B (zh) 通信方法、可读介质和电子设备
WO2023082032A1 (zh) 一种云平台参数适配方法、装置、终端设备及储存介质
CN113110890A (zh) 动态链接库调用方法、装置、计算机设备和存储介质
CN114567507A (zh) 限流方法、系统、设备及存储介质
CN112988691A (zh) 一种基于嵌入式系统的文件更新方法、装置及终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21795532

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21795532

Country of ref document: EP

Kind code of ref document: A1