Unified licensing methods and devices for device modules, electronic devices and storage media
By receiving, verifying, and merging authorization files from module manufacturers through a dedicated unified authorization management system, and generating and integrating unified authorization files, the system solves the problem of complex authorization and activation processes for trusted terminal device modules, and achieves secure and reliable unified authorization.
Patent Information
- Application Number
- CN202311608247.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-28
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-11-28
AI Technical Summary
The module authorization and activation process for trusted terminal devices in existing technologies is complex and lacks unified management, resulting in insufficient security and trustworthiness.
The dedicated equipment unified authorization management system receives authorization files and verification packages from various module manufacturers, verifies and merges them to generate a unified authorization file, and integrates it into the target directory address to achieve unified authorization for various device modules.
The authorization and activation process for trusted terminal devices has been simplified, ensuring the security and trustworthiness of uniformly generated authorization files.
Smart Images

Figure CN117708772B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer information security, and more specifically, to a unified authorization method and apparatus for device modules, electronic devices, and storage media. Background Technology
[0002] Currently, there are various methods for authorizing and activating modules on trusted terminal devices (e.g., servers, desktops, workstations, etc.). Each module has its own independent activation method; for example, module A is activated via an authorization code, module B via digital certificate authentication, and module C via remote authorization. Some modules even lack authorization management altogether. Therefore, the lack of a unified authorization method for all modules on a trusted terminal device leads to a complex authorization and activation process, and makes it impossible to guarantee the security and reliability of independent authorization and activation for each module.
[0003] There is currently no effective solution to the above problems. Summary of the Invention
[0004] This invention provides a unified authorization method and apparatus for device modules, an electronic device and a storage medium, to at least solve the technical problem of the relatively complex process of authorizing and activating trusted terminal devices in related technologies.
[0005] According to one aspect of the present invention, a method for unified authorization of device modules is provided, comprising: determining a set of device modules for a target device, wherein the set of device modules includes: a plurality of device modules, each device module corresponding to a module manufacturer; receiving an authorization file uploaded by each module manufacturer and an authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file; for each authorization file, verifying the authorization file using the authorization file verification package, and merging all the authorization files if all the authorization files pass verification to obtain a target authorization file, wherein the target authorization file is used to authorize each of the device modules; integrating the target authorization file into a target directory address to complete the unified authorization of each of the device modules, wherein the target directory address is used to store the target authorization file.
[0006] Furthermore, before receiving the authorization file uploaded by each of the module manufacturers and the authorization file verification package associated with the authorization file, the method further includes: obtaining the device production strategy of the device manufacturer of the target device; generating a parameter file for the target device based on the device production strategy, wherein the parameter file includes: a preset parameter type set, and a preset parameter range of a preset parameter indicated by each preset parameter type in the preset parameter type set; distributing the parameter file to each of the module manufacturers, wherein the module manufacturers generate the authorization file based on the parameter file and construct the authorization file verification package for the authorization file.
[0007] Furthermore, before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, the method further includes: the module manufacturer verifying the parameters in the authorization file based on the parameter file to obtain a verification result; if the verification result indicates that the parameter types of all the parameters in the authorization file belong to the preset parameter type set and the parameter values of all the parameters belong to the target parameter range, the module manufacturer determines that the parameter verification in the authorization file is passed, wherein the target parameter range is the preset parameter range indicated by the preset parameter that is consistent with the parameter type of the parameter; the module manufacturer uploads the authorization file and the authorization file verification package associated with the authorization file to the preset unified authorization system.
[0008] Furthermore, before verifying the authorization file using the authorization file verification package, the method further includes: checking whether all module manufacturers have uploaded the authorization file and the authorization file verification package associated with the authorization file; if all module manufacturers have uploaded the authorization file and the authorization file verification package associated with the authorization file, determining the merging status and information content of all authorization files; if the merging status of all authorization files is unmerged and the information content of all authorization files is less than a preset information threshold, determining that all authorization files have passed the check.
[0009] Furthermore, after determining that all the licensed documents have passed the check, the method further includes: for each licensed document, verifying the licensed document's authorization logic using the licensed document verification package; if the authorization logic is normal, determining that the licensed document has passed the verification.
[0010] Further, the step of merging all the authorized files to obtain a target authorized file includes: generating an authorization identifier for each authorized file, wherein each authorized identifier is associated with the device module; merging all the authorized files based on a preset file template to obtain a target authorized file, wherein the target authorized file includes at least: a device type identifier, a device manufacturer identifier, and authorization information associated with the authorized identifier.
[0011] Furthermore, after integrating the target license file into the target directory address, the method further includes: the module manufacturer obtaining the target license file from the target directory address; the module manufacturer using the target license information indicated by the target license identifier in the target license file to authorize the device module, wherein the target license identifier is the license identifier associated with the device module of the module manufacturer.
[0012] According to another aspect of the present invention, a unified authorization apparatus for device modules is also provided, comprising: a determining unit, configured to determine a set of device modules for a target device, wherein the set of device modules includes: a plurality of device modules, each device module corresponding to a module manufacturer; a receiving unit, configured to receive an authorization file uploaded by each module manufacturer and an authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file; a merging unit, configured to verify the authorization file for each authorization file using the authorization file verification package, and merge all the authorization files to obtain a target authorization file if all the authorization files pass the verification, wherein the target authorization file is used to authorize each of the device modules; and an integrating unit, configured to integrate the target authorization file into a target directory address to complete the unified authorization of each of the device modules, wherein the target directory address is used to store the target authorization file.
[0013] Furthermore, the unified authorization device further includes: a first acquisition module, configured to acquire the device production strategy of the device manufacturer of the target device before receiving the authorization file uploaded by each of the module manufacturers and the authorization file verification package associated with the authorization file; a first generation module, configured to generate a parameter file of the target device based on the device production strategy, wherein the parameter file includes: a preset parameter type set and a preset parameter range of a preset parameter indicated by each preset parameter type in the preset parameter type set; and a first distribution module, configured to distribute the parameter file to each of the module manufacturers, wherein the module manufacturers generate the authorization file based on the parameter file and construct the authorization file verification package for the authorization file.
[0014] Furthermore, the unified authorization device further includes: a first verification module, used to, before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, verify the parameters in the authorization file based on the parameter file to obtain a verification result; a first determination module, used to, when the verification result indicates that the parameter in the authorization file has passed verification, and all parameter values in the authorization file belong to the preset parameter type set and all parameter values belong to the target parameter range, wherein the target parameter range is the preset parameter range indicated by the preset parameter that is consistent with the parameter type of the parameter; and a first upload module, used to, when the module manufacturer uploads the authorization file and the authorization file verification package associated with the authorization file to the preset unified authorization system.
[0015] Furthermore, the unified authorization device further includes: a first checking module, used to check whether all module manufacturers have uploaded the authorization file and the authorization file verification package associated with the authorization file before verifying the authorization file using the authorization file verification package; a second determining module, used to determine the merging status and information content of all authorization files when all module manufacturers have uploaded the authorization file and the authorization file verification package associated with the authorization file; and a third determining module, used to determine that the inspection of all authorization files has passed when the merging status of all authorization files is unmerged and the information content of all authorization files is less than a preset information threshold.
[0016] Furthermore, the unified authorization device further includes: a second verification module, used to verify the authorization logic of each authorization file using the authorization file verification package after determining that all the authorization files have passed the check; and a fourth determination module, used to determine that the authorization file has passed the verification if the authorization logic is normal.
[0017] Further, the merging unit includes: a second generation module, used to generate an authorization identifier for each of the authorization files, wherein each authorization identifier is associated with the device module; and a first merging module, used to merge all the authorization files based on a preset file template to obtain a target authorization file, wherein the target authorization file includes at least: a device type identifier, a device manufacturer identifier, and authorization information associated with the authorization identifier.
[0018] Furthermore, the unified authorization device further includes: a second acquisition module, used to obtain the target authorization file from the target directory address after the target authorization file is integrated into the target directory address; and a first authorization module, used to authorize the device module by the module manufacturer using the target authorization information indicated by the target authorization identifier in the target authorization file, wherein the target authorization identifier is the authorization identifier associated with the device module of the module manufacturer.
[0019] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to execute any of the above-described unified authorization methods for device modules.
[0020] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement any of the above-described unified authorization methods for device modules.
[0021] In this invention, a set of device modules for the target device is determined. Authorization files and associated verification packages are received from each module manufacturer. For each authorization file, the verification package is used to verify it. If all authorization files pass verification, they are merged to obtain a target authorization file. This target authorization file is then integrated into a target directory address, completing the unified authorization for each device module. This invention first receives authorization files and associated verification packages from the module manufacturers corresponding to each device module on the target device. Then, the verification packages are used to verify the authorization files. If all authorization files pass verification, they are merged to generate a target authorization file. This target authorization file is then integrated into a target directory address, allowing each module manufacturer to obtain the target authorization file from the target directory address and complete the unified authorization for their respective device modules. This not only simplifies the authorization and activation process for trusted terminal devices but also ensures the security and reliability of the uniformly generated target authorization file, thus solving the technical problem of the complex authorization and activation process for trusted terminal devices in related technologies. Attached Figure Description
[0022] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings:
[0023] Figure 1 This is a flowchart of an optional unified authorization method for device modules according to an embodiment of the present invention;
[0024] Figure 2 This is a schematic diagram of an optional unified authorization management system based on dedicated equipment according to an embodiment of the present invention;
[0025] Figure 3 This is a schematic diagram of an optional process for generating a unified license file according to an embodiment of the present invention;
[0026] Figure 4 This is a schematic diagram of an optional unified license file generation process according to an embodiment of the present invention;
[0027] Figure 5 This is a schematic diagram of an optional unified authorization management system central structure according to an embodiment of the present invention;
[0028] Figure 6 This is a schematic diagram of another optional unified license file generation process according to an embodiment of the present invention;
[0029] Figure 7 This is a schematic diagram of an optional unified licensing device for device modules according to an embodiment of the present invention;
[0030] Figure 8 This is a hardware structure block diagram of an electronic device (or mobile device) according to an embodiment of the present invention for a unified licensing method for device modules. Detailed Implementation
[0031] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0032] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0033] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this invention are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0034] This invention proposes a method for unified planning, generation, and activation of authorization functions for various modules of a trusted terminal device. A dedicated unified authorization management system generates a unified authorization file for the trusted terminal device, containing the encrypted authorization content of each security module. Each security module integrated into the trusted terminal device can read this unified authorization file, parse and decrypt its required data, and then activate the authorization. The dedicated unified authorization management system enables unified authorization for each independent module on the trusted terminal device, providing a foundation and support for the construction of a trusted network platform.
[0035] The present invention will now be described in detail with reference to various embodiments.
[0036] Example 1
[0037] According to an embodiment of the present invention, an embodiment of a unified authorization method for device modules is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0038] Figure 1 This is a flowchart of an optional unified authorization method for device modules according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:
[0039] Step S101: Determine the set of device modules for the target device, wherein the set of device modules includes: multiple device modules, each device module corresponding to a module manufacturer.
[0040] Step S102: Receive the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file.
[0041] Step S103: For each authorization file, the authorization file verification package is used to verify the authorization file. If all authorization files pass the verification, all authorization files are merged to obtain the target authorization file, which is used to authorize each device module.
[0042] Step S104: Integrate the target authorization file into the target directory address to complete the unified authorization of each device module. The target directory address is used to store the target authorization file.
[0043] Through the above steps, the set of device modules of the target device can be determined. The system receives the authorization files uploaded by each module manufacturer, along with the authorization file verification package associated with each file. For each authorization file, the authorization file verification package is used to verify it. If all authorization files pass verification, they are merged to obtain the target authorization file. This target authorization file is then integrated into the target directory address, completing the unified authorization for each device module. In this embodiment of the invention, the system first receives the authorization files uploaded by the module manufacturers corresponding to each device module on the target device, along with the authorization file verification package associated with each file. Then, the authorization file verification package is used to verify the authorization files. If all authorization files pass verification, they are merged to generate the target authorization file. The target authorization file is then integrated into the target directory address, allowing each module manufacturer to obtain the target authorization file from the target directory address and complete the unified authorization for their respective device modules. This not only simplifies the authorization and activation process for trusted terminal devices but also ensures the security and reliability of the uniformly generated target authorization file, thereby solving the technical problem of the complex authorization and activation process for trusted terminal devices in related technologies.
[0044] The embodiments of the present invention will now be described in detail with reference to the steps described above.
[0045] In this embodiment of the invention, a unified authorization management system for dedicated devices is proposed. Figure 2 This is a schematic diagram illustrating an optional unified authorization management system based on dedicated equipment according to an embodiment of the present invention, such as... Figure 2As shown, the system includes: initialization for each module vendor, a unified authorization management system for dedicated equipment (including authorization file verification module management, a unified authorization file library, authorization file management, and authorization file merging and export functions), and trusted terminal devices (e.g., desktop computers, workstations, servers, etc.). Each module vendor needs to initialize first, meaning they need to generate their own authorization files based on the device data files and provide independent authorization file verification modules. These authorization files and authorization file verification modules are then uploaded to the unified authorization management system for dedicated equipment. The authorization file verification modules are managed through the authorization file verification module, and these authorization files are managed through the authorization file management system, forming a unified authorization file library for easy future retrieval. The authorization files use a preset format (e.g., JSON format, a lightweight data exchange format) that defines standards and specifications. When an authorization file is uploaded, the unified authorization management system for dedicated equipment parses and verifies it. After successful verification, basic information such as the file name and parameter number of the authorization file is entered into the library, and the authorization file itself is stored permanently. Afterwards, the dedicated equipment unified authorization management system merges the authorization files of each module manufacturer that have been uploaded, generates a unified authorization file, and then exports the unified authorization file to the equipment manufacturer for integration, so that the module manufacturers of each module on the trusted terminal device can perform unified authorization and activation.
[0046] Step S101: Determine the set of device modules for the target device, wherein the set of device modules includes: multiple device modules, each device module corresponding to a module manufacturer.
[0047] In this embodiment of the invention, the set of device modules involved in the target device (i.e., trusted terminal device) can be determined first. The set of device modules includes: multiple device modules, each device module corresponding to a module manufacturer (i.e., the manufacturer that produces the device module).
[0048] Optionally, before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, the method further includes: obtaining the device production strategy of the device manufacturer of the target device; generating a parameter file for the target device based on the device production strategy, wherein the parameter file includes: a set of preset parameter types, and a preset parameter range of preset parameters indicated by each preset parameter type in the set of preset parameter types; distributing the parameter file to each module manufacturer, wherein the module manufacturer generates an authorization file based on the parameter file and constructs an authorization file verification package for the authorization file.
[0049] In this embodiment of the invention, module manufacturers need to generate their own authorization files based on the device data file (i.e., the parameter file of the target device) and provide an independent authorization file verification module (i.e., authorization file verification package). Specifically, the module manufacturers first obtain the device production plan (i.e., the device production strategy) planned by the device manufacturer to generate the parameter file of the target device (i.e., obtain the device production strategy of the device manufacturer of the target device, and generate the parameter file of the target device based on the device production strategy (the parameter file includes: a set of preset parameter types (i.e., the required parameter types, such as device number, etc.), and the preset parameter range of the preset parameter indicated by each preset parameter type in the set of preset parameter types)). This allows them to determine the data specifications of the authorization file based on the parameter file. Then, the parameter file is distributed to each module manufacturer (i.e., the parameter file is distributed to each module manufacturer). After receiving the parameter file, each module manufacturer uses the parameter file as the parameter specification to generate its own authorization file and develops an independent authorization file verification module to verify the authorization file (i.e., the module manufacturer generates the authorization file based on the parameter file and builds an authorization file verification package for the authorization file).
[0050] Optionally, before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, the method further includes: the module manufacturer verifying the parameters in the authorization file based on the parameter file and obtaining the verification result; if the verification result indicates that the parameter types of all parameters in the authorization file belong to the preset parameter type set and the parameter values of all parameters belong to the target parameter range, the module manufacturer determines that the parameter verification in the authorization file is passed, wherein the target parameter range is the preset parameter range indicated by the preset parameters that are consistent with the parameter types of the parameters; the module manufacturer uploading the authorization file and the authorization file verification package associated with the authorization file to the preset unified authorization system.
[0051] In this embodiment of the invention, before the module manufacturer uploads the authorization file and the authorization file verification module to the dedicated device unified authorization management system (i.e., the preset unified authorization system), it is also necessary to verify the authorization file. Specifically, the module manufacturer needs to verify the standardization of the parameters in the authorization file according to the parameter file to obtain the verification result. If the verification result indicates that the parameter types of all parameters in the authorization file belong to the preset parameter type set and the parameter values of all parameters belong to the target parameter range (i.e., the preset parameter range indicated by the preset parameters that are consistent with the parameter types of the parameters), then it is determined that all parameters in the authorization file conform to the data specifications, and the parameter verification in the authorization file is determined to be passed. After that, the authorization file and the authorization file verification package associated with the authorization file are uploaded to the preset unified authorization system.
[0052] Step S102: Receive the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file.
[0053] In this embodiment of the invention, the pre-defined unified authorization system can receive the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file (the authorization file verification package is used to verify the authorization file).
[0054] Optionally, before verifying the license file using the license file verification package, the method further includes: checking whether all module vendors have uploaded the license file and the license file verification package associated with the license file; if all module vendors have uploaded the license file and the license file verification package associated with the license file, determining the merging status and information content of all license files; and if the merging status of all license files is unmerged and the information content of all license files is less than a preset information threshold, determining that all license files have passed the check.
[0055] In this embodiment of the invention, before merging all authorized files, the pre-defined unified authorization system needs to check whether each authorized file meets the specifications, whether it has been stored, whether it has been merged, and whether the size of the file's authorization information items meets the requirements. Specifically, it can first check whether all module vendors have uploaded authorized files and authorization file verification packages associated with the authorized files. If all module vendors have uploaded authorized files and authorization file verification packages associated with the authorized files, it is also necessary to determine the merging status and information content of all authorized files. If the merging status of all authorized files is unmerged and the information content of all authorized files is less than the preset information threshold (which can be set according to the actual situation), then it can be determined that the check of all authorized files has passed.
[0056] Optionally, after determining that all license files have passed the check, the method further includes: for each license file, verifying the license file's authorization logic using an authorization file verification package; if the authorization logic is normal, determining that the license file verification has passed.
[0057] In this embodiment of the invention, on a trusted terminal device, all its software or modules form a community, and this community is only considered complete when all of them are fully authorized. Therefore, before merging the authorization files of various module vendors to form a unified authorization file, it is necessary to verify whether the authorization logic of these communities is normal and whether it can be called to generate authorization files. That is, it is necessary to use each authorization file verification package to verify the authorization logic of the corresponding authorization file. Only if the authorization logic is normal can the authorization file be determined to have passed verification.
[0058] Step S103: For each authorization file, the authorization file verification package is used to verify the authorization file. If all authorization files pass the verification, all authorization files are merged to obtain the target authorization file, which is used to authorize each device module.
[0059] Optionally, the step of merging all license files to obtain a target license file includes: generating an authorization identifier for each license file, wherein each authorization identifier is associated with a device module; merging all license files based on a preset file template to obtain a target license file, wherein the target license file includes at least: a device type identifier, a device manufacturer identifier, and authorization information associated with the authorization identifier.
[0060] In this embodiment of the invention, after all the authorized files have been verified, all the authorized files are merged to obtain a unified authorized file (i.e., a target authorized file, which is used to authorize each device module). Specifically, an authorization identifier (associated with a device module) can be generated for each authorized file first. Then, all the authorized files are merged according to a preset file template to obtain a target authorized file. The target authorized file includes: device type identifier, device manufacturer identifier, and authorization information associated with the authorization identifier.
[0061] In this embodiment of the invention, the preset file template (i.e., the merged unified authorization file format) is as follows:
[0062]
[0063] The descriptions of each field in the preset file template are shown in Table 1:
[0064] Table 1
[0065]
[0066] Step S104: Integrate the target authorization file into the target directory address to complete the unified authorization of each device module. The target directory address is used to store the target authorization file.
[0067] In this embodiment of the invention, the unified authorization file is exported and downloaded from the dedicated equipment unified authorization management system and handed over to the equipment manufacturer for integration, so that the target authorization file is integrated into the target directory address (the target directory address is used to store the target authorization file and can be set according to the actual situation), thereby completing the unified authorization of each equipment module.
[0068] Optionally, after integrating the target license file into the target directory address, the method further includes: the module manufacturer obtaining the target license file from the target directory address; the module manufacturer using the target license information indicated by the target license identifier in the target license file to license the device module, wherein the target license identifier is the license identifier associated with the device module of the module manufacturer.
[0069] In this embodiment of the invention, each module manufacturer on the trusted terminal device can authorize and activate its own module according to the unified authorization file integrated by the device manufacturer (i.e., the module manufacturer obtains the target authorization file from the target directory address, and then uses the target authorization information indicated by the target authorization identifier (i.e. the authorization identifier associated with the device module of the module manufacturer) in the target authorization file to authorize the device module).
[0070] Figure 3 This is a schematic diagram of an optional process for generating a unified license file according to an embodiment of the present invention, such as... Figure 3 As shown, after each module vendor uploads its license file, the license management system manages the files. Then, it checks whether all license files are complete. If not, it continues to wait for each module vendor to upload its license file. If all license files are complete, it merges all license files to generate a unified license file and saves it to the disk. Finally, it exports the unified license file for unified licensing.
[0071] Figure 4 This is a schematic diagram of an optional unified license file generation process according to an embodiment of the present invention, such as... Figure 4 As shown, the process includes the following:
[0072] (1) The equipment manufacturer releases the production plan, generates equipment parameter files, and distributes the parameter files;
[0073] (2) Each module manufacturer (e.g., module manufacturer 1, module manufacturer 2, etc.) receives the parameter file, then generates the authorization file based on the parameter file, and prepares the authorization verification module at the same time;
[0074] (3) Each module manufacturer uploads the authorization verification module and the authorization file to the unified authorization management system for dedicated equipment;
[0075] (4) The unified authorization management system for special equipment needs to merge the authorization files and then export the merged authorization files. After that, the equipment manufacturers integrate the authorization files to generate a unified authorization file.
[0076] The following describes in detail another optional implementation method.
[0077] In this embodiment of the invention, a unified authorization management system for dedicated devices is proposed. This system is a web (website) system with a B / S architecture (i.e., browser / server architecture).
[0078] Figure 5 This is a schematic diagram of an optional unified authorization management system central structure according to an embodiment of the present invention, such as... Figure 5 As shown, it includes: authorization verification module management, unified authorization file management, device request parameter file management, and device manufacturer management.
[0079] The authorization verification module management includes the following functions:
[0080] (1) Upload the authorization document verification package of each module manufacturer.
[0081] (2) Manage the uploaded authorization file verification package.
[0082] (3) Call the authorization verification module to verify the validity of the authorization documents of each module vendor.
[0083] For device request parameter file management, the following functions are included:
[0084] (1) Upload and manage request parameter files.
[0085] (2) Equipment manufacturers provide equipment parameter files to each module manufacturer. These files serve as input parameters for each module manufacturer's authorized modules. When these parameter files are uploaded to the unified authorization management system, the system generates a software-independent authorization file for that module manufacturer based on its authorized modules.
[0086] (3) Manage and download the independent license files generated by each module manufacturer.
[0087] The unified license file management includes the following functions:
[0088] (1) Upload and manage the authorization files of each module vendor.
[0089] (2) Call the authorization verification module to verify the authorization file of the module manufacturer.
[0090] (3) Based on the uploaded authorization files of each module manufacturer, merge them to generate a unified authorization file.
[0091] (4) Download and export the unified license file.
[0092] For equipment manufacturer management, the following functions are included:
[0093] (1) Maintain the equipment manufacturer.
[0094] (2) Upload the corresponding equipment parameter request file according to the equipment manufacturer.
[0095] (3) Unify and merge authorizations based on equipment manufacturers.
[0096] Figure 6 This is a schematic diagram of another optional unified license file generation process according to an embodiment of the present invention, such as... Figure 6 As shown, you can first enter the authorization module management system, then upload the authorization module for whole-machine management, then upload the authorization files of each manufacturer, and then verify the authorization files. If the verification module fails, re-upload the authorization module. If the authorization file fails, re-upload the authorization files of each manufacturer. After the verification is successful, merge them to generate a unified authorization file and export it.
[0097] In this embodiment of the invention, in order to achieve unified authorization and activation management for modules that originally required independent authorization, a unified authorization management system using dedicated equipment is used. This ensures that authorization request data is generated uniformly, that independent authorization files are generated based on the request data, and that the individual authorization files are then merged to generate a unified authorization file. This simplifies the authorization and activation process for trusted terminal devices and effectively guarantees the security and reliability of the uniformly generated authorization file.
[0098] The following is a detailed description with reference to another embodiment.
[0099] Example 2
[0100] The unified authorization device for device modules provided in this embodiment includes multiple implementation units, each of which corresponds to a specific implementation step in Embodiment 1 above.
[0101] Figure 7 This is a schematic diagram of an optional unified licensing device for device modules according to an embodiment of the present invention, such as... Figure 7 As shown, the unified authorization device may include: a determining unit 70, a receiving unit 71, a merging unit 72, and an integrating unit 73, wherein...
[0102] The determining unit 70 is used to determine the set of equipment modules of the target device, wherein the set of equipment modules includes: multiple equipment modules, each equipment module corresponding to a module manufacturer;
[0103] The receiving unit 71 is used to receive the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file;
[0104] The merging unit 72 is used to verify the authorization file using the authorization file verification package for each authorization file, and merge all authorization files to obtain the target authorization file if all authorization files pass the verification. The target authorization file is used to authorize each device module.
[0105] Integration unit 73 is used to integrate the target authorization file into the target directory address to complete the unified authorization of each device module. The target directory address is used to store the target authorization file.
[0106] The aforementioned unified authorization device can determine the set of device modules of the target device through the determining unit 70, receive the authorization files uploaded by each module manufacturer and the authorization file verification package associated with the authorization files through the receiving unit 71, verify the authorization files of each authorization file using the authorization file verification package through the merging unit 72, and merge all authorization files to obtain the target authorization file if all authorization files pass the verification. The target authorization file is then integrated into the target directory address through the integration unit 73, thus completing the unified authorization of each device module. In this embodiment of the invention, the device can first receive the authorization files uploaded by the module manufacturers corresponding to each device module on the target device and the authorization file verification package associated with the authorization files, then verify the authorization files using the authorization file verification package. If all authorization files pass the verification, they can be merged to generate the target authorization file. The target authorization file is then integrated into the target directory address, so that each module manufacturer can obtain the target authorization file from the target directory address to complete the unified authorization of their respective device modules. This not only simplifies the authorization and activation process of trusted terminal devices, but also ensures the security and reliability of the uniformly generated target authorization file, thereby solving the technical problem of the relatively complex authorization and activation process for trusted terminal devices in related technologies.
[0107] Optionally, the unified authorization device further includes: a first acquisition module, configured to acquire the device production strategy of the device manufacturer of the target device before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file; a first generation module, configured to generate a parameter file for the target device based on the device production strategy, wherein the parameter file includes: a preset parameter type set and a preset parameter range of a preset parameter indicated by each preset parameter type in the preset parameter type set; and a first distribution module, configured to distribute the parameter file to each module manufacturer, wherein the module manufacturer generates an authorization file based on the parameter file and constructs an authorization file verification package for the authorization file.
[0108] Optionally, the unified authorization device further includes: a first verification module, used to verify the parameters in the authorization file based on the parameter file before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, and obtain the verification result; a first determination module, used to determine that the parameter verification in the authorization file is passed when the verification result indicates that the parameter types of all parameters in the authorization file belong to a preset parameter type set and the parameter values of all parameters belong to a target parameter range, wherein the target parameter range is a preset parameter range indicated by preset parameters that are consistent with the parameter types of the parameters; and a first upload module, used to upload the authorization file and the authorization file verification package associated with the authorization file to the preset unified authorization system.
[0109] Optionally, the unified authorization device further includes: a first checking module, used to check whether all module manufacturers have uploaded authorization files and authorization file verification packages associated with the authorization files before verifying the authorization files using the authorization file verification package; a second determining module, used to determine the merging status and information content of all authorization files when all module manufacturers have uploaded authorization files and authorization file verification packages associated with the authorization files; and a third determining module, used to determine that the inspection of all authorization files has passed when the merging status of all authorization files is unmerged and the information content of all authorization files is less than a preset information threshold.
[0110] Optionally, the unified authorization device further includes: a second verification module, used to verify the authorization logic of each authorization file using an authorization file verification package after determining that all authorization files have passed the check; and a fourth determination module, used to determine that the authorization file verification has passed if the authorization logic is normal.
[0111] Optionally, the merging unit includes: a second generation module for generating an authorization identifier for each authorization file, wherein each authorization identifier is associated with a device module; and a first merging module for merging all authorization files based on a preset file template to obtain a target authorization file, wherein the target authorization file includes at least: a device type identifier, a device manufacturer identifier, and authorization information associated with the authorization identifier.
[0112] Optionally, the unified authorization device further includes: a second acquisition module, used to obtain the target authorization file from the target directory address after the target authorization file is integrated into the target directory address; and a first authorization module, used to authorize the device module by the module manufacturer using the target authorization information indicated by the target authorization identifier in the target authorization file, wherein the target authorization identifier is the authorization identifier associated with the device module of the module manufacturer.
[0113] The aforementioned unified authorization device may also include a processor and a memory. The aforementioned determining unit 70, receiving unit 71, merging unit 72, and integrating unit 73 are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.
[0114] The aforementioned processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured; by adjusting kernel parameters, the target license file can be integrated into the target directory address, thus achieving unified licensing for various device modules.
[0115] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.
[0116] The present invention also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: determining a set of device modules for a target device, receiving an authorization file uploaded by each module manufacturer and an authorization file verification package associated with the authorization file, verifying the authorization file using the authorization file verification package for each authorization file, and merging all authorization files to obtain a target authorization file when all authorization files have been verified, integrating the target authorization file into a target directory address, and completing the unified authorization of each device module.
[0117] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to execute the above-described unified authorization method for device modules.
[0118] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the above-described unified authorization method for device modules.
[0119] Figure 8 This is a hardware structure block diagram of an electronic device (or mobile device) according to an embodiment of the present invention for a unified licensing method for device modules. Figure 8 As shown, an electronic device may include one or more ( Figure 8The processor 802 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 804 for storing data may also be included. In addition, it may include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 8 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device may also include components that are more... Figure 8 The more or fewer components shown, or having the same Figure 8 The different configurations shown.
[0120] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0121] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0122] In the several embodiments provided by this invention, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection can be through some interfaces; the indirect coupling or communication connection of units or modules can be electrical or other forms.
[0123] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0124] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0125] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0126] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.
Claims
1. A unified authorization method for device modules, characterized in that, include: Determine the set of device modules for the target device, wherein the set of device modules includes: multiple device modules, each device module corresponding to a module manufacturer; The system receives an authorization file uploaded by each module manufacturer and an authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file. For each of the authorized files, the authorized file verification package is used to verify the authorized file. If all the authorized files pass the verification, all the authorized files are merged to obtain a target authorized file, wherein the target authorized file is used to authorize each of the device modules. The target authorization file is integrated into the target directory address to complete the unified authorization of each device module, wherein the target directory address is used to store the target authorization file; The process includes, before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file, the following: Obtain the equipment manufacturing strategy of the equipment manufacturer of the target equipment; Based on the equipment production strategy, a parameter file for the target equipment is generated, wherein the parameter file includes: a set of preset parameter types, and a preset parameter range for each preset parameter type in the set of preset parameter types; The parameter file is distributed to each of the module manufacturers, wherein the module manufacturers generate the authorization file based on the parameter file and construct the authorization file verification package for the authorization file; The process includes, before verifying the authorization file using the authorization file verification package, the following: Check whether all the module manufacturers have uploaded the license file and the license file verification package associated with the license file; If all the module manufacturers have uploaded the license files and the license file verification packages associated with the license files, determine the merged status and information content of all the license files; If all the authorized files are in an unmerged state and the amount of information in all the authorized files is less than a preset information threshold, then the check on all the authorized files is deemed to have passed.
2. The unified authorization method according to claim 1, characterized in that, Before receiving the authorization file uploaded by each of the module manufacturers and the authorization file verification package associated with the authorization file, the process also includes: The module manufacturer verifies the parameters in the authorization file based on the parameter file and obtains the verification result; When the verification result indicates that the parameter types of all the parameters in the authorization file belong to the preset parameter type set and the parameter values of all the parameters belong to the target parameter range, the module manufacturer determines that the parameter verification in the authorization file is passed, wherein the target parameter range is the preset parameter range indicated by the preset parameter that is consistent with the parameter type of the parameter; The module manufacturer uploads the authorization file and the authorization file verification package associated with the authorization file to the preset unified authorization system.
3. The unified authorization method according to claim 1, characterized in that, After confirming that all the aforementioned license files have passed the checks, the following is also included: For each of the authorized files, the authorization logic of the authorized file is verified using the authorization file verification package; If the authorization logic is normal, the authorization file is confirmed to have passed verification.
4. The unified authorization method according to claim 1, characterized in that, The steps of merging all the aforementioned license files to obtain the target license file include: An authorization identifier is generated for each of the authorization files, wherein each authorization identifier is associated with the device module; All the authorized files are merged based on a preset file template to obtain a target authorized file, wherein the target authorized file includes at least: a device type identifier, a device manufacturer identifier, and authorized information associated with the authorized identifier.
5. The unified authorization method according to claim 4, characterized in that, After integrating the target license file into the target directory address, the following is also included: The module manufacturer obtains the target license file from the target directory address; The module manufacturer authorizes the device module using the target authorization information indicated by the target authorization identifier in the target authorization file, wherein the target authorization identifier is the authorization identifier associated with the device module of the module manufacturer.
6. A unified authorization device for device modules, characterized in that, include: A determining unit is used to determine a set of device modules for a target device, wherein the set of device modules includes: multiple device modules, each device module corresponding to a module manufacturer; The receiving unit is configured to receive the authorization file uploaded by each of the module manufacturers and the authorization file verification package associated with the authorization file, wherein the authorization file verification package is used to verify the authorization file; The merging unit is configured to verify each of the authorized files using the authorized file verification package, and merge all the authorized files to obtain a target authorized file if all the authorized files pass the verification, wherein the target authorized file is used to authorize each of the device modules; An integration unit is used to integrate the target authorization file into a target directory address to complete the unified authorization of each device module, wherein the target directory address is used to store the target authorization file; The unified authorization device further includes: The first acquisition module is used to acquire the equipment production strategy of the equipment manufacturer of the target device before receiving the authorization file uploaded by each module manufacturer and the authorization file verification package associated with the authorization file; The first generation module is used to generate a parameter file for the target device based on the device production strategy, wherein the parameter file includes: a set of preset parameter types and a preset parameter range for each preset parameter type in the set of preset parameter types; The first distribution module is used to distribute the parameter file to each of the module manufacturers, wherein the module manufacturers generate the authorization file based on the parameter file and construct the authorization file verification package for the authorization file; The unified authorization device further includes: The first inspection module is used to check whether all the module manufacturers have uploaded the authorization file and the authorization file verification package associated with the authorization file before verifying the authorization file using the authorization file verification package; The second determining module is used to determine the merging status and information content of all the authorized files when all the module manufacturers have uploaded the authorized files and the authorized file verification package associated with the authorized files; The third determining module is used to determine that all the authorized files have passed the check when the merged state of all the authorized files is unmerged and the information content of all the authorized files is less than a preset information threshold.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the unified licensing method for device modules as described in any one of claims 1 to 5.
8. An electronic device, characterized in that, It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the uniform licensing method for device modules as described in any one of claims 1 to 5.
Citation Information
Patent Citations
Managing Heterogeneous Product Features Using a Unified License Manager
US20140090051A1
