TW202409861A - Authorization system, method and computer readable medium for software component usage - Google Patents

Abstract

The invention discloses an authorization system, method and computer readable medium for software component usage. A user device unforgeable token through an electronic device is produced according to a software component usage period, a software component warranty period and agreed user device environment information, and a software component unforgeable token for a software component is produced, and then combines the software component with the user device unforgeable token and the software component unforgeable token to insert into the user device. Next, when the user device wants to start the execution of the software component, the software component shall use the software component usage period, the software component warranty period and the agreed user device environment information of the user device unforgeable token and the software component unforgeable token to automatically or actively perform authorization check of the software components for the user device.

Description

Authorization systems, methods and computer-readable media for use of software components

The present invention relates to a software component authorization technology, and in particular to an authorization system, method and computer-readable medium for the use of software components.

In today's information explosion society, the amount of information such as software, music, video, games, etc. that is disseminated through the Internet every day is extremely huge. However, for various software components (such as software/firmware/applications, etc.) on the software component distribution side, most users do not know how to check or verify the source or legitimacy of various software components through user devices, nor can they automatically or proactively perform verification and authorization or terminate authorization of software components in user devices.

In an existing technology, a method and system for software authentication using a software authentication chain are proposed. The software authentication chain issued by the management system located in the software management center is used to perform software authentication on the software that has been installed or will be installed on the software carrier. Certification.

In another prior art, a method of public authorization access control of open API (Application Programming Interface) based on application of digital signature authentication is proposed. A public authorization mechanism for open API is established in the form of an alliance or a third-party public service platform. Only Through the alliance or public service platform Only certified Web (network) applications or application software products can be authorized to use open APIs within the alliance or third-party public service platforms.

However, the above-mentioned existing technologies cannot generate (produce) user device non-counterfeiting symbols and software component non-counterfeiting symbols with reliability, legality and non-repudiation by the software component issuer, and cannot be used. The non-counterfeiting token of the user device and the non-counterfeiting token of the software component serve as the basis of trust for the authorization check of the software component. It is also impossible to combine the non-counterfeiting token of the user device with various time information and user device environment information to achieve the goal of software components. It is also impossible for the software component issuer to publish a public information to verify the authenticity of the software component's non-counterfeiting symbol, nor to include a software component explanation in the production (production) process of the software component's non-counterfeiting symbol. The user device environment information of the timeout or blacklist is used to restrict or terminate the use authorization of the software components when the user device defaults.

Therefore, how to provide an innovative software component licensing technology to solve any of the above problems or provide related functions/services has become a major research topic for technical personnel in this field.

The present invention provides an innovative authorization system, method and computer-readable medium for the use of software components, which can generate (produce) user devices with reliability, legality and non-repudiation by the software component issuing end and cannot be counterfeited. The token and the software component cannot be counterfeited, and the user device uncounterfeitable token and the software component uncounterfeitable token can be used as the basis of trust for the authorization check of the software component, or the user device uncounterfeitable token can be combined Various time information (such as software component usage period/software component warranty period) and user device environment information to achieve software component authorization Authorization inspection, or the software component issuer publishes a public information to verify the authenticity of the software component non-counterfeiting symbol, or adds software component release during the generation (production) process of the software component non-counterfeiting symbol Time or user device environment information in the blacklist to limit or terminate the use authorization of software components when the user device defaults.

The software component authorization system of the present invention includes: an electronic device, which generates a user device non-counterfeit token based on the software component usage period, the software component warranty period and the agreed user device environment information of the software component, and the electronic device generates the software component non-counterfeit token for the software component; and at least one user device is interconnected or communicated with the electronic device to combine the software component with the user device non-counterfeit token and the software component non-counterfeit token through the electronic device. token, and then place the combined user device unforgeable token, software component unforgeable token and software component into the user device, wherein when the user device wants to start and execute the software component, the software component uses the software component usage period, software component warranty period and agreed user device environment information of the user device unforgeable token in the user device and the software component unforgeable token to automatically or proactively perform an authorization check on the user device for the software component.

The software component use authorization method of the present invention includes: generating a user device non-counterfeit token through an electronic device according to the software component use period, the software component warranty period and the agreed user device environment information of the software component, and generating a software component non-counterfeit token for the software component through the electronic device; combining the software component with the user device non-counterfeit token and the software component non-counterfeit token through the electronic device to make the combined user device non-counterfeit token The user device cannot be forged token, the software component cannot be forged token, and the software component are placed in the user device; and when the user device wants to start and execute the software component, the software component uses the software component usage period of the user device cannot be forged token, the software component warranty period, the agreed user device environment information, and the software component cannot be forged token in the user device to automatically or proactively perform an authorization check on the user device for the software component.

The computer-readable medium of the present invention is applied to a computing device or a computer and stores instructions for executing the authorization method for using the above-mentioned software components.

In order to make the above features and advantages of the present invention more clearly understandable, the following examples are given and detailed descriptions are provided in conjunction with the attached drawings. The following description will partially explain the additional features and advantages of the present invention, and these features and advantages will be partially known from the description or can be learned through the practice of the present invention. It should be understood that both the general description above and the detailed description below are exemplary and explanatory, and are not intended to limit the scope of the present invention.

1: Authorization system for the use of software components

10: Electronic devices

11: User devices cannot forge tokens

111: Software component usage period

112: Software component warranty period

113: Agreed user device environment information

12: Software components cannot forge tokens

121:Software component release time

122: Blacklist user device environment information

13: Software components

20: User device

21: User device environment information

A: Software component distributor

B:User

S01 to 510: Steps

Figure 1 is a schematic diagram of the architecture of the authorization system used by the software components of the present invention.

FIG. 2 is a schematic flowchart of the authorization check of the software component in the user device in the authorization method for the use of the software component of the present invention.

The following describes the embodiments of the present invention through specific specific embodiments. Those skilled in the art can understand other advantages and effects of the present invention from the content disclosed in this specification, and can also implement it through other different specific equivalent embodiments or Use.

Figure 1 is a schematic structural diagram of an authorization system 1 used by software components of the present invention. As shown in the figure, the authorization system 1 for the use of software components may include at least one (such as plural) electronic device 10 of the software component issuer A and at least one (such as plural) user device 20 of user B that are connected or communicated with each other. . The software component issuer A can generate (produce) a software component through the electronic device 10 The user device non-counterfeiting sign 11 and the software component non-counterfeiting sign 12 of reliability, legality and non-repudiation are used by the software component issuer A to combine (match) the software component 13 with the user through the electronic device 10 The device non-counterfeiting token 11 and the software component non-counterfeiting token 12 are then installed into the user device 20 . The user device non-counterfeiting sign 11 may at least include the software component usage period 111, the software component warranty period 112, the agreed user device environment information 113, etc., and the software component non-counterfeiting sign 12 may at least include the software component release The time 121 and the user device environment information 122 of the blacklist (such as the user device environment information list/list of the blacklist), etc.

In one embodiment, the software component 13 can be various software (software), firmware (firmware), application software, application program (APP), software development kit (Software Development Kit; SDK), packaged software, Computer program products, etc., and firmware can be software embedded or stored in hardware. The software component issuer A can be an individual, group, company, unit, organization, institution, etc. that issues the software component 13. The user B can be an individual, group, company, unit, etc. that is authorized by the software component issuer A to use the software component 13. Organizations, institutions, etc. The electronic device 10 or the user device 20 may be a computer, a server, a smartphone, a smart watch, a smart TV, augmented reality (AR) glasses, virtual reality (VR) glasses, an IoT embedded sensing electronic device, etc. , the computer can be a tablet computer, desktop computer, notebook computer, etc., and the server can be a central server, cloud server, network server, remote server, etc.

In one embodiment, the uncounterfeitable token 11 of the user device may be an uncounterfeitable token (such as an electronic certificate, a natural person certificate, etc.) that represents, certifies or is unique to the user B or the user device 20, and the software component cannot The counterfeit token 12 may be an uncounterfeitable token that represents, certifies or is unique to the software component 13, and the user device device has the uncounterfeitable token 11 or the "token" in the software component's uncounterfeitable token 12 "It can also be called token, token, beacon, pass, scepter, etc."

The software component usage period 111, the software component warranty period 112, the software component release time 121 and the software component identification information may respectively represent the usage period, the warranty period, the release time and the identification information of the software component 13. The agreed user device environment information 113 may be at least one of the agreed hardware identifier, application identifier, operating system identifier, and software development kit identifier. The user device environment information 21 may be at least one of the hardware identifier, application identifier, operating system identifier, and software development kit identifier of the user device 20. The "contract or agreement" may represent the contract or agreement between the software component publisher A and the real owner of the user device 20 (such as the real owner).

In one embodiment, the "connection or communication" mentioned in the present invention can represent mutual connection or communication through wired means (such as a wired network) or wireless means (such as a wireless network), and "at least one" means more than one (such as one, Two or more), "plural" means more than two (such as two, three, four, five or more than ten). However, the present invention is not limited to the above.

In the software component use authorization system 1 and its method of the present invention, at least one software component issuer A first uses the electronic device 10 according to the software component usage period 111, software component warranty period 112 and the agreed user device of the software component 13. The environment information 113 generates (produces) the user device non-counterfeiting token 11, and the software component issuer A generates (produces) the software component non-counterfeiting token 12 for the software component 13 through the electronic device 10. Subsequently, the software component issuer A combines the software component 13 with the user device non-counterfeiting symbol 11 and the software component non-counterfeiting symbol 12 through the electronic device 10, so that the combined user device non-counterfeiting symbol 12 11. The software components cannot be counterfeited to insert the token 12 and the software component 13 into the user device 20 . When the user device 20 wants to start executing the software component 13, the software component 13 first uses the software component service life 111 and software component warranty of the user device non-counterfeiting sign 11 in the user device 20. The deadline 112 and the agreed user device environment information 113 and the software component non-forgery token 12 are used to automatically or proactively perform authorization checks on the software component 13 on the user device 20 .

In other words, after the software component distributor A signs a contract or makes an agreement with the real owner of the user device 20 in the business model through the electronic device 10, it can distribute the software component 13 according to various time information (such as the software component usage period 111 and the software component warranty period 112) and the agreed user device environment information 113 (such as the agreed hardware identification code/application identification code/operating system At least one of the unified identification code/software development kit identification code) generates/produces a user device non-counterfeiting token 11 with reliability, legality and non-repudiation, and the software component distributor A can also generate (produce) a software component non-counterfeiting token 12 with reliability, legality and non-repudiation for various different versions or updated versions of software components 13 through the electronic device 10. Then, the software component distributor A can combine (match) the software component 13 with the user device unforgeable token 11 and the software component unforgeable token 12 through the electronic device 10, and deliver the combined (matched) software component 13, the user device unforgeable token 11 and the software component unforgeable token 12 to the real owner of the user device 20, so as to place the user device unforgeable token 11, the software component unforgeable token 12 and the software component 13 into (such as directly into) the user device 20.

When the user device 20 wants to start executing the software component 13, the software component 13 can use the information of the user device non-counterfeiting token 11 in the user device 20 (such as the software component usage period 111, software component warranty period 112, agreement The user device environment information 113) and the software component non-forgery token 12 are used to automatically or proactively perform authorization checks on the software components 13 (such as use authorization or warranty authorization checks) on the user device 20. If necessary, the software component 13 can also obtain the user device environment information 21 from the user device 20 to facilitate processing based on the user device environment information 21 in the user device 20 (such as the hardware identification code of the user device 20 / Application identification At least one of the code/operating system identification code/software development kit identification code) and the user device environment information 113 agreed in the user device non-counterfeiting mark 11 (such as the agreed hardware identification code/application identification code/ At least one of the operating system identification code/software development kit identification code) performs authorization check of the software component (such as use authorization or warranty authorization check).

The software component issuer A can generate (produce) a user device unforgeable token 11 and a software component unforgeable token 12 that are reliable, legal, and irrefutable, so as to use the user device unforgeable token 11 and the software component unforgeable token 12 to ensure the user device 20's trust in the software component 13. The user device unforgeable token 11 is generated (produced) for the real owner of the user device 20, and the software component unforgeable token 12 is generated (produced) for various versions or updated versions of the software component 13. During the generation (production) process of the software component unforgeable token 12, the software component distributor A can add the software component release time 121 of the software component 13 to the software component unforgeable token 12 through the electronic device 10, and can also add the blacklisted user device environment information 122 (such as at least one of the blacklisted hardware identifier/application identifier/operating system identifier/software development kit identifier) to the blacklisted user device environment information 122 if necessary. (i) is added to the software component non-forgery token 12, so that when the user device 20 violates the contract or agreement (breach of contract), the user device 20 is restricted or terminated from using the software component 13 (such as a different version or updated version of the software component 13) according to the software component release time 121 in the software component non-forgery token 12 and the user device environment information 122 in the blacklist.

Therefore, the software component use authorization system 1 and method of the present invention can use the user device unforgeable token 11 (such as an electronic certificate/personal certificate) and the software component unforgeable token 12 as the trust basis for the authorization check of the software component 13 (such as the use authorization or warranty authorization check), and combine the user device unforgeable token 11 with various time information (such as the software component The software component usage period 111 and the software component warranty period 112, etc.) and the agreed user device environment information 113 (such as at least one of the agreed hardware identifier/application identifier/operating system identifier/software development kit identifier) are used to achieve the authorization check of the software component 13 (such as the use authorization or warranty authorization check), and can also be applied to multiple or different business model scenarios.

In one embodiment, the authorization system 1 and method for using software components of the present invention may include the following: [1] Issuance method of user device non-counterfeiting token 11 and software component non-counterfeiting token 12, [2] ] Authorization check method for software component 13.

[1] The method for issuing the user device unforgeable token 11 and the software component unforgeable token 12 may include the following steps P11 to P13.

Procedure P11: The software component issuer A owns and publishes through the electronic device 10 the user device non-counterfeiting token 11 and the software component non-counterfeiting token 12 that can be used to verify that the software component issuer A generated (produced) Public information (such as public verification information). That is to say, the software component issuer A can publish a public information (such as public verification information) through the electronic device 10, so that the software component 13 can use the public information (such as public verification information) to automatically or actively verify the software component issuer A in the future. The generated user device cannot counterfeit the token 11 and the software component cannot counterfeit the authenticity of the token 12 .

Procedure P12: The software component issuer A generates (produces) and delivers the corresponding (different) user device non-counterfeit token 11 to the user device 20 of user B under different contracts through the electronic device 10, and the user device The non-counterfeiting mark 11 may include various information such as software component information of the software component 13, software component usage period 111, software component warranty period 112, software component release time 121 and agreed user device environment information 113, and the software component The information includes relevant information that can identify the software component 13 authorized for use by the software component issuer A. as well as That is, the software component issuer A can record various information that can be verified for authorized use through the user device non-counterfeiting token 11 issued by the electronic device 10 according to the content of the contract or agreement.

Procedure P13: The software component distributor A generates a corresponding software component unforgeable token 12 for a different version or updated version of the software component 13 through the electronic device 10, and releases the software component unforgeable token 12 and the software component 13 to the user device 20 of the user B. The software component unforgeable token 12 may include the software component 13. Information, software component identification information, software component release time 121, blacklisted user device environment information 122 (such as at least one of the blacklisted hardware identification code/application identification code/operating system identification code/software development kit identification code), and the software component identification information may include relevant information that can identify the integrity and difference of the software component 13. That is, the software component distributor A can record various information that can be used for authorized use verification in the software component non-forgery token 12 generated (produced) by the electronic device 10 for the released software component 13.

[2] Authorization checking method for software component 13: may include the following procedures P21 to P28.

Procedure P21: User B integrates the public information (such as public verification information) of the software component issuer A, the user device non-counterfeiting token 11, the software component non-counterfeiting token 12 and the software component 13 through the user device 20 to the user device 20 for use. That is, user B can use the user device 20 to combine the public information (such as public verification information) provided by the software component issuer A, the user device non-counterfeiting symbol 11, the software component non-counterfeiting symbol 12 with the software. The component 13 is integrated into the user device 20 for use, so that the authorization check mechanism of the software component 13 can be activated before the function of the software component 13 is operated.

Procedure P22: The user device 20 verifies the origin of the software component 13, and then The origin may be the source reliability, source legality or source non-repudiation of the software component 13 . That is, the user device 20 can use the public information (such as public verification information) published by the software component issuer A to automatically or actively verify the source of the software component 13, so as to determine the user based on the verification result of the source of the software component 13. Whether the device 20 can use this software component 13. For example, when the verification result of the source of the software component 13 is verification passed (verification successful), it can be preliminarily determined that the user device 20 is expected or able to use this software component 13, or the verification results in procedures P22 to P28 can all be verification. Only through (successful verification) can it be finally determined that the user device 20 can use the software component 13 (but is not limited to this). On the contrary, when the verification result of the source of the software component 13 is unverified (verification failed), it is directly determined that the user device 20 cannot use the software component 13 .

Procedure P23: The software component 13 verifies the source and correctness of the uncounterfeitable symbol 11 of the user device, and the source can be the source reliability, source legality or source non-repudiation of the user device's uncounterfeitable symbol 11 . That is to say, the software component 13 can automatically or proactively verify the source and correctness of the user device's non-counterfeit mark 11 by using the public information (such as public verification information) published by the software component issuer A to ensure that the user device cannot be counterfeited according to the user's device. The verification results of the origin and correctness of the counterfeit token 11 determine whether the user device 20 can use the software component 13 . For example, when the verification result of the source and correctness of the uncounterfeitable token 11 of the user device is verification passed (verification successful), it can be preliminarily determined that the user device 20 is expected or able to use the software component 13, and it can also be determined in the program The verification results from P22 to P28 are all verification passed (verification successful) before it is finally determined that the user device 20 can use the software component 13 (but is not limited to this). On the contrary, when the verification result of the source and correctness of the user device's unforgeable token 11 is unverified (verification failed), it is directly determined that the user device 20 cannot use the software component 13 .

Procedure P24: Software component 13 verifies that the software component cannot be counterfeited and comes from the symbol 12 Source and correctness, and the source may be the reliability of the source, legality of the source or non-repudiation of the source of the software component's non-counterfeiting symbol 12. That is to say, the software component 13 can use the public information (such as public verification information) published by the software component issuer A to automatically or actively verify the source and correctness of the software component non-counterfeiting mark 12, so as to ensure that the software component cannot be counterfeited. The verification result of the origin and correctness of the token 12 determines whether the user device 20 can use the software component 13 . For example, when the verification result of the source and correctness of the software component non-counterfeiting symbol 12 is verification passed (verification successful), it can be preliminarily determined that the user device 20 is expected or able to use the software component 13, or in the process P22 The verification results up to P28 are all verification passed (verification successful) before it is finally determined that the user device 20 can use the software component 13 (but is not limited to this). On the contrary, when the verification result of the source and correctness of the software component unforgery mark 12 is unverified (verification failed), it is directly determined that the user device 20 cannot use the software component 13 .

Procedure P25: The software component 13 verifies the agreed user device environment information 113. That is, the software component 13 can verify whether the user device environment information 21 in the user device 20 conforms to the agreed user device environment information 113 in the user device unforgeable token 11, and determine whether the user device 20 can use the software component 13 based on the verification result of the user device environment information 21 and the agreed user device environment information 113. For example, when the user device environment information 21 meets the agreed user device environment information 113, so that the verification result of the agreed user device environment information 113 is verification passed (verification success), it can be preliminarily determined that the user device 20 is expected to or can use this software component 13, and it can also be finally determined that the user device 20 can use this software component 13 only when the verification results of procedures P22 to P28 are all verification passed (verification success) (but not limited to this). On the contrary, when the user device environment information 21 does not meet the agreed user device environment information 113, so that the verification result of the agreed user device environment information 113 is not verification passed (verification failure), it is directly determined that the user device 20 cannot use this software component 13.

Procedure P26: Software component 13 verifies the usage period 111 (validity period) of the software component authorized for use. That is to say, the software component 13 can use the system time of the user device 20 and the software component usage period 111 in the user device non-forgery token 11 to verify the validity period based on the system time of the user device 20 and the software component. The verification result of the usage period 111 determines whether the user device 20 can use the software component 13 . For example, when the system time of the user device 20 is within the range of the software component usage period 111, so that the verification result of the software component usage period 111 is verification passed (verification successful), it can be preliminarily determined that the user device 20 is expected or able to use this The software component 13 can also be finally determined that the user device 20 can use the software component 13 (but is not limited to this) when the verification results of procedures P22 to P28 are all passed (verification successful). On the contrary, when the system time of the user device 20 is not within the range of the software component usage period 111 and the verification result of the software component usage period 111 is unverified (verification failed), it is directly determined that the user device 20 cannot use the software. Component 13.

Procedure P27: Software component 13 verifies the authorized software component warranty period 112. That is, the software component 13 can use the software component release time 121 in the software component non-counterfeiting symbol 12 and the software component warranty period 112 in the user device non-counterfeiting symbol 11 to verify the warranty period. The verification results of the component release time 121 and the software component warranty period 112 determine whether the user device 20 can use the software component 13 . For example, when the software component release time 121 is within the range of the software component warranty period 112, so that the verification result of the software component warranty period 112 is verification passed (verification successful), it can be preliminarily determined that the user device 20 is expected or able to use the software. The component 13 can also be finally determined that the user device 20 can use the software component 13 (but is not limited to this) when the verification results of procedures P22 to P28 are all passed (verification successful). opposite In other words, when the software component release time 121 is not within the scope of the software component warranty period 112 and the verification result of the software component warranty period 112 is unverified (verification failed), it is directly determined that the user device 20 cannot use the software component 13 .

Procedure P28: Software component 13 verifies that the software component cannot counterfeit the user device environment information 122 in the blacklist in token 12, such as the blacklist's hardware identification code/application identification code/operating system identification code/software development kit identification code At least one of them. That is to say, the software component 13 can use the user device environment information 113 agreed in the user device non-counterfeiting token 11 and the user device environment information 122 of the blacklist in the software component non-counterfeiting token 12 to perform blacklist retrieval. Or verification, to determine whether the user device 20 can use the software component 13 based on the retrieval or verification results of the agreed user device environment information 113 and the blacklisted user device environment information 122 . For example, when the agreed user device environment information 113 is not retrieved from the user device environment information 122 of the blacklist, so that the verification result of the user device environment information 122 of the blacklist is verification passed (verification successful), it may be initially It is determined that the user device 20 is expected or able to use the software component 13. It can also be determined that the user device 20 can use the software component 13 after the verification results of procedures P22 to P28 are all verified (verification successful) (but not in this way). limited). On the contrary, when the agreed user device environment information 113 has been retrieved from the blacklisted user device environment information 122, so that the verification result of the blacklisted user device environment information 122 is not verified (verification failed), directly It is determined that the user device 20 cannot use the software component 13 .

In one embodiment, the authorization system 1 and method for using the software component of the present invention may also include the following: [1] Generation (production) of the user device non-counterfeitable mark 11, [2] Software component non-counterfeitable The production (production system) of Maofuji 12.

[1] The user device cannot forge the generation (production) of the token 11: The true owner of the user device 20 and the software component publisher A agree to complete the use authorization and warranty authorization of the software component 13, and the true owner of the user device 20 and the software component publisher A agree to complete the software component usage period 111, software component warranty period 112 and agreed user device environment information 113 (such as at least one of the agreed hardware identifier/application identifier/operating system identifier/software development kit identifier) of the software component 13. Next, the software component issuer A can generate (produce) a user device non-forgeable token 11 with reliability, legitimacy and non-repudiation through the electronic device 10 according to various information such as the software component usage period 111, the software component warranty period 112 and the agreed user device environment information 113.

[2] Generation (production) of the software component non-counterfeit sign 12: The software component issuer A can use the electronic device 10 to release the software component 121 of different versions or updated versions of the software component 13 and use the blacklist The device environment information 122 (such as at least one of the blacklisted hardware identification code/application identification code/operating system identification code/software development kit identification code) is added to generate (produce) products that are reliable and legal. Software components with non-repudiation cannot be counterfeited12.

Furthermore, the software component distributor A can deliver the user device non-forgeable token 11, the software component non-forgeable token 12 and the software component 13 to the real owner of the user device 20 through the electronic device 10 in accordance with the contract or agreement, so as to directly place the user device non-forgeable token 11, the software component non-forgeable token 12 and the software component 13 into the user device 20. Whenever the software component 13 is activated in the user device 20, the software component 13 can perform a series of authorization checks (such as usage authorization or warranty authorization checks) as shown in the following FIG. 2 to determine whether the user device 20 can execute the software component 13.

Figure 2 is a schematic flowchart of the authorization check (such as use authorization or warranty authorization check) of the software component 13 in the user device 20 in the authorization method for the use of software components of the present invention. Figure, and refer to Figure 1 for explanation. At the same time, the authorization check of the software component 13 in the user device 20 may include steps S01 to S10 as shown in FIG. 2 , but this embodiment is only used as an example, and the order of steps S02 to S09 can be adjusted or the steps S02 to S09 can be reduced. At least one of them (depending on actual needs).

In step S01 , the software component 13 starts checking, that is, the software component 13 automatically or actively performs authorization checking (such as usage authorization or warranty authorization checking) in the user device 20 .

In step S02, does the software component 13 automatically or actively check whether there is a user device non-forgeable token 11 in the user device 20? If yes (the user device non-forgeable token 11 exists in the user device 20), the software component 13 proceeds to the following step S03. On the contrary, if no (the user device non-forgeable token 11 does not exist in the user device 20), the software component 13 automatically or actively determines that the user device non-forgeable token 11 has not passed the authorization check (authorization check failed), so that the user device 20 cannot execute the software component 13.

In step S03, the software component 13 automatically or actively checks whether the user device non-forgery mark 11 in the user device 20 is generated/produced by the software component issuer A? If so (the user device non-forgery token 11 is generated/produced by the software component issuer A), then the software component 13 proceeds to the following step S04. On the contrary, if not (the non-counterfeitable symbol 11 of the user device is not generated/produced by the software component issuer A), then the software component 13 automatically or actively determines the generation/production of the non-counterfeitable symbol 11 of the user device. The authorization check fails (authorization check fails), so that the user device 20 cannot execute the software component 13 .

In step S04 , the software component 13 automatically or actively obtains the system time of the user device 20 from the user device 20 to check whether the system time of the user device 20 is within the software component in the user device non-forgery mark 11 Within the period of use 111? If so (make The system time of the user device 20 is within the range of the software component usage period 111), then the software component 13 continues to the following step S05. On the contrary, if not (the system time of the user device 20 is not within the range of the software component usage period 111), the software component 13 automatically or actively determines that the system time of the user device 20 has failed the authorization check (authorization check failed), so that the use The device 20 cannot execute the software component 13.

In step S05 , the software component 13 automatically or actively obtains the user device environment information 21 (such as at least one of a hardware identification code/application identification code/operating system identification code/software development kit identification code) from the user device 20 ), to check whether the user device environment information 21 complies with the user device environment information 113 agreed in the user device non-counterfeit mark 11 (such as the agreed hardware identification code/application identification code/operating system identification code/software At least one of the development kit identification codes)? If so (the user device environment information 21 complies with the agreed user device environment information 113), the software component 13 proceeds to the following step S06. On the contrary, if not (the user device environment information 21 does not comply with the agreed user device environment information 113), the software component 13 automatically or actively determines that the user device environment information 21 fails the authorization check (authorization check fails), causing the user to Device 20 cannot execute software component 13.

In step S06 , the software component 13 automatically or actively checks whether there is a software component unforgery mark 12 in the user device 20 . If so (the software component non-forgery token 12 exists in the user device 20), the software component 13 continues to the following step S07. On the contrary, if not (there is no software component non-counterfeiting symbol 12 in the user device 20), the software component 13 automatically or actively determines that the software component non-counterfeiting symbol 12 has failed the authorization check (authorization check failed), so that the user The device 20 cannot execute the software component 13.

In step S07, the software component 13 automatically or actively checks that the software component cannot Is the counterfeit symbol 12 generated/manufactured by software component publisher A? If so (the software component non-counterfeiting sign 12 is generated/produced by the software component issuer A), then the software component 13 continues to the following step S08. On the contrary, if not (the software component non-counterfeiting symbol 12 is not generated/produced by the software component issuer A), then the software component 13 automatically or actively determines that the generation/production of the software component non-counterfeiting symbol 12 has failed. Authorization check (authorization check failed) makes the user device 20 unable to execute the software component 13 .

In step S08, the software component 13 automatically or proactively obtains the software component warranty period 112 from the user device non-forgeable token 11 of the user device 20 to check whether the software component release time 121 in the software component non-forgeable token 12 is within the range of the software component warranty period 112 in the user device non-forgeable token 11. If yes (the software component release time 121 is within the range of the software component warranty period 112), the software component 13 proceeds to the following step S09. On the contrary, if not (the software component release time 121 is not within the scope of the software component warranty period 112), it means that this version of the software component 13 cannot be executed in the user device 20 according to the contract or agreement between the software component publisher A and the user B. Then the software component 13 automatically or proactively determines that the software component release time 121 has not passed the authorization check (authorization check failure), so that the user device 20 cannot execute the software component 13.

In step S09 , the software component 13 automatically or actively obtains the agreed user device environment information 113 (such as the agreed hardware identification code/application identification code/operating system identification code/ At least one of the software development kit identification codes) to check whether the agreed user device environment information 113 is not listed in the user device environment information 122 of the blacklist in the software component non-counterfeiting token 12 (such as the blacklisted hardware At least one of the identification code/application identification code/operating system identification code/software development kit identification code)? If it is (agreed user equipment If the environment information 113 is not listed in the blacklist of the user device environment information 122), the software component 13 continues to step S10, so that the user device 20 can execute the software component 13. On the contrary, if not (the agreed user device environment information 113 has been listed in the blacklisted user device environment information 122), it means that this version of the software component 13 cannot be released in accordance with the contract or agreement between the software component issuer A and user B. When executed in the user device 20 , the software component 13 automatically or actively determines that the agreed user device environment information 113 fails the authorization check (authorization check fails), so that the user device 20 cannot execute the software component 13 .

In addition, the present invention also provides a computer-readable medium for an authorization method for the use of software components, which is applied to a computing device or computer with a processor and/or memory, and the computer-readable medium stores instructions and can be used The computing device or computer executes the computer-readable medium through the processor and/or memory to execute the above content when the computer-readable medium is executed. For example, the processor can be a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), etc., and the memory can be a random access memory (RAM), a memory card, a hard disk (such as a cloud/network hard drive), etc. discs), databases, etc., but are not limited to this.

In summary, the authorization system, method and computer-readable medium used by the software component of the present invention have at least the following features, advantages or technical effects.

1. The present invention can generate (produce) a user device unforgeable token and a software component unforgeable token with reliability, legitimacy and non-repudiation by the software component issuer, so as to ensure the user device's trust in the software component by using the user device unforgeable token and the software component unforgeable token.

2. The present invention can combine various time information (such as software component usage period/software component warranty period) with agreed user device environment information (such as agreed hardware identification code/application program). Identification code/operating system identification code/software development kit identification code) is added to the unforgeable mark of the user device to facilitate automatic or proactive execution of various authorization checks such as usage authorization and warranty authorization of software components.

3. The present invention can use the non-counterfeiting symbol of the user device and the non-counterfeiting symbol of the software component as the basis of trust for the authorization check of the software component (such as use authorization or warranty authorization check), and make the user device non-counterfeitable. The token combines (matches) various time information (such as software component usage period/software component warranty period) and agreed user device environment information (such as agreed hardware identification code/application identification code/operating system identification code/software development Package identification code) to facilitate the authorization check of software components (such as use authorization or warranty authorization check), and can also be applied to multiple or different business model scenarios.

4. The software component distributor of the present invention can publish public information (such as public verification information) through an electronic device, so that the software component can use the public information (such as public verification information) to automatically or actively verify the authenticity of the software component unforgeable token generated (produced) by the software component distributor.

5. The present invention can add the software component release time during the generation (production) process of the software component non-counterfeiting mark, and can further add the user device environment information of the blacklist (such as the hardware identification code of the blacklist/ Application Identification Code/Operating System Identification Code/Software Development Kit Identification Code) to facilitate the restriction or termination of the use authorization of different or updated versions of software components when the user's device violates the contract or agreement (breach of contract).

6. The present invention can provide the user device with various source checks such as source reliability, source legality or source non-repudiation of software components, so as to improve the reliability, legality or non-repudiation of the source of software components.

7. The present invention can provide user devices with authorization checks for software components of different versions or updated versions (such as use authorization or warranty authorization checks), and can also perform authorization checks on user devices. Restriction or termination of licenses for different versions or later versions of software components.

8. The user device of the present invention does not need to be connected to an external verification server or authorization server through a network (such as a wired network/wireless network/Internet), and can automatically or proactively execute verification and authorization or terminate authorization of software components in the user device.

The above embodiments are only illustrative of the principles, characteristics and effects of the present invention, and are not intended to limit the scope of the present invention. Anyone skilled in the art can make the above-mentioned modifications without violating the spirit and scope of the present invention. Modify and change the implementation form. Any equivalent changes and modifications made using the contents disclosed in the present invention shall still be covered by the patent application. Therefore, the protection scope of the present invention should be as listed in the patent application scope.

1: Authorization system for the use of software components

10: Electronic devices

11: User devices cannot forge tokens

111: Software component usage period

112: Software component warranty period

113: Agreed user device environment information

12: Software components cannot be counterfeited.

121:Software component release time

122: Blacklist user device environment information

13:Software components

20: User device

21: User device environment information

A:Software component publisher

B: User

Claims (17)

A licensing system for use of software components, including: The electronic device generates a user device non-counterfeit token based on the software component usage period, the software component warranty period and the agreed user device environment information of the software component, and the electronic device generates a software component non-counterfeit token for the software component; and At least one user device is interconnected or communicated with the electronic device, so as to combine the software component with the user device unforgeable token and the software component unforgeable token through the electronic device, and then place the combined user device unforgeable token, the software component unforgeable token and the software component into the user device, Among them, when the user device wants to start executing the software component, the software component uses the user device non-forgery mark in the user device to indicate the software component usage period, the software component warranty period and the agreement. The user device environment information and the software component cannot forge tokens to automatically or proactively perform authorization checks on the user device for the software component. The authorization system for the use of software components as described in claim 1, wherein, after the completion of the agreed usage period of the software component, the warranty period of the software component and the agreed user device environment information, through the electronic device Based on the usage period of the software component, the warranty period of the software component and the agreed user device environment information, a user device non-counterfeiting token with reliability, legality and non-repudiation is generated, and the software based on the software component The component release time and the user device environment information of the blacklist generate an uncounterfeitable sign of the software component with reliability, legality and non-repudiation. An authorization system for use of a software component as described in claim 1, wherein the software component further obtains user device environment information from the user device to perform an authorization check of the software component based on the user device environment information in the user device and the agreed user device environment information in the unforgeable token of the user device. The software component use authorization system as described in claim 1, wherein, in the process of generating the software component unforgeable token, the software component release time and the user device environment information of the blacklist are added to the software component unforgeable token through the electronic device, so that when the user device violates the contract or agreement, the use authorization of the software component is restricted or terminated for the user device according to the software component release time and the user device environment information of the blacklist in the software component unforgeable token. The authorization system for the use of software components as described in claim 1, wherein the electronic device further generates corresponding non-counterfeiting marks of the software components for different versions or updated versions of the software components, so as to make the software components non-counterfeitable. The counterfeit sign is released to the user device together with the software component, and the software component non-counterfeit sign includes the software component information, software component identification information, software component release time and blacklist of the software component. User device environment information. The authorization system for the use of software components as described in claim 1, wherein the software component further uses public information to verify both the non-counterfeiting symbol of the user device and the non-counterfeiting symbol of the software component, so as to verify the user's The verification results of both the non-counterfeiting symbol of the device and the non-counterfeiting symbol of the software component determine whether the user device can use the software component. The authorization system for the use of software components as described in claim 1, wherein the software component further uses the system time of the user device and the usage period of the software component in the non-forgery mark of the user device to verify the validity period. , and use the software component release time in the non-counterfeiting symbol of the software component and the warranty period of the software component in the user device non-counterfeiting symbol to verify the warranty period based on the system time of the user device The verification results of both the service life of the software component and the verification results of the release time of the software component and the warranty period of the software component determine whether the user device can use the software component. The authorization system for the use of software components as described in claim 1, wherein the software component further utilizes the agreed user device environment information in the user device non-counterfeiting symbol and the black code in the software component non-counterfeiting symbol. Perform blacklist retrieval or verification on the user device environment information of the list to determine whether the user device can use the software based on the retrieval or verification results of the agreed user device environment information and the user device environment information of the blacklist. components. An authorization method for the use of software components, including: The user device non-counterfeiting symbol is generated through the electronic device based on the software component usage period, the software component warranty period and the agreed user device environment information, and the software component non-counterfeiting symbol is generated through the electronic device for the software component. remember; Combining the software component with the user device unforgeable token and the software component unforgeable token through the electronic device, so as to place the combined user device unforgeable token, the software component unforgeable token and the software component into the user device; and When the user device wants to start executing the software component, the software component uses the user device non-forgery mark in the user device to indicate the usage period of the software component, the warranty period of the software component and the agreed use The user's device environment information and the software component may not forge tokens to automatically or proactively conduct authorization checks of the software component on the user's device. The method for authorizing the use of software components as described in claim 9 further includes generating a user device non-counterfeit token with reliability, legitimacy and irrefutability through the electronic device based on the software component usage period, the software component warranty period and the agreed user device environment information after the software component usage period, the software component warranty period and the agreed user device environment information are agreed upon, and generating a software component non-counterfeit token with reliability, legitimacy and irrefutability based on the software component release time and the blacklist user device environment information of the software component. The authorization method for using a software component as described in claim 9 further includes the software component obtaining user device environment information from the user device, so as to match the user device environment information in the user device with the use The user device may not forge the agreed user device environment information in the token to perform authorization check of the software component. The method for authorizing the use of a software component as described in claim 9 further includes adding the software component release time and the user device environment information of the blacklist to the software component unforgeable token through the electronic device during the generation process of the software component unforgeable token, so that when the user device violates the contract or agreement, the use authorization of the software component is restricted or terminated for the user device according to the software component release time and the user device environment information of the blacklist in the software component unforgeable token. The method for authorizing the use of a software component as described in claim 9 further includes generating a corresponding software component unforgeable token for different versions or updated versions of the software component through the electronic device, so as to release the software component unforgeable token together with the software component to the user device, wherein the software component unforgeable token includes software component information, software component identification information, software component release time, and user device environment information of the blacklist of the software component. The authorization method for use of a software component as described in claim 9 further includes the software component using public information to verify both the non-counterfeiting signature of the user device and the non-counterfeiting signature of the software component, so as to verify the user's The verification results of both the non-counterfeiting symbol of the device and the non-counterfeiting symbol of the software component determine whether the user device can use the software component. The method for authorizing the use of a software component as described in claim 9 further includes the software component using the system time of the user device and the use period of the software component in the unforgeable token of the user device to verify the validity period, and using the software component release time in the unforgeable token of the software component and the warranty period of the software component in the unforgeable token of the user device to verify the warranty period, so as to determine whether the user device can use the software component based on the verification results of the system time of the user device and the use period of the software component and the verification results of the software component release time and the warranty period of the software component. The method for authorizing the use of a software component as described in claim 9 further includes the software component using the agreed user device environment information in the user device unforgeable token and the user device environment information in the blacklist in the software component unforgeable token to search or verify the blacklist, so as to determine whether the user device can use the software component based on the search or verification results of the agreed user device environment information and the user device environment information in the blacklist. A computer-readable medium, used in a computing device or computer, stores instructions to execute the authorization method for the use of software components as described in any one of claims 9 to 16.

Images