CN113127809A - Product license management method and system - Google Patents
Product license management method and system Download PDFInfo
- Publication number
- CN113127809A CN113127809A CN201911399147.1A CN201911399147A CN113127809A CN 113127809 A CN113127809 A CN 113127809A CN 201911399147 A CN201911399147 A CN 201911399147A CN 113127809 A CN113127809 A CN 113127809A
- Authority
- CN
- China
- Prior art keywords
- product
- license
- interface
- user
- approval
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 96
- 238000000034 method Methods 0.000 claims abstract description 38
- 238000012795 verification Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 13
- 230000003993 interaction Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 15
- 230000006870 function Effects 0.000 description 13
- 238000013461 design Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000008520 organization Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000007474 system interaction Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Storage Device Security (AREA)
Abstract
The invention provides a product license management method and a system, wherein the method comprises the following steps: the product permission management system receives a user registration request, examines and approves the user registration request, and after the registration examination and approval is passed, role management authority and user management authority are distributed to the user; the product license management system receives a product access request of the user, examines and approves the product access request, and after the access request is approved, the product is accessed to the product license management system and is managed; and the product license management system receives a license application of the user for the product, approves the license application, and generates a license file of the product after the license approval is passed. In the invention, the product License is created and managed uniformly, and the expansibility and the compatibility are stronger, thereby realizing the uniform management and control of the product License.
Description
Technical Field
The invention relates to the field of License management and manufacturing, in particular to a product License management system method and system.
Background
The number and variety of current software products are very large, and the generation and management of License of the products generally have the following defects: 1) products have respective generation tools, so that strict management and control are difficult to achieve; 2) the products have respective generation rules, and the expandability is weak; 3) license examination and approval processes are different, and management is loose; 4) there are relatively few solutions that can both create and tightly manage License.
Disclosure of Invention
The embodiment of the invention provides a product license management method and system, which at least solve the problem that the product license generation and management in the related technology are not uniform, so that the compatibility and expandability are weak.
According to an embodiment of the present invention, there is provided a product license management method including: the product permission management system receives a user registration request, examines and approves the user registration request, and after the registration examination and approval is passed, role management authority and user management authority are distributed to the user; the product license management system receives a product access request of the user, examines and approves the product access request, and after the access request is approved, the product is accessed to the product license management system and is managed; and the product license management system receives a license application of the user for the product, approves the license application, and generates a license file of the product after the license approval is passed.
Optionally, the role management authority includes at least one of: a super administrator role, a product administrator role, a common user role.
Optionally, the product license management system includes: the system comprises an internal API interface and an external interface interacting with a third-party system, wherein the internal interface comprises a verification interface and a generation interface, and the external interface comprises a notification interface.
Optionally, after the product license management system receives the license application for the product from the user, the product license management system further includes: checking an interface type of a license application of the product; dynamically constructing license rule information of the product according to a template under the condition that the interface type is an internal API (application program interface) interface or the interface type is an external interface from a third-party system and the product access code is valid;
and calling a verification interface to verify the license application and informing an administrator with the approval authority to approve.
Optionally, if the product request is from a third-party system, an access code is set, the access code needs to be verified in interaction between the systems, and an access result of the product is notified to the third-party system through a notification interface, where the access result carries the access code.
Optionally, after generating the license file of the product, the method further includes: license information for the product is maintained and license inquiry and download of the product is provided.
Optionally, the method further comprises at least one of: and sending a reminding message to the user after the registration approval is passed, sending the reminding message to the requester after the access request approval is passed, and sending the reminding message to the requester after the permission approval is passed.
According to another embodiment of the present invention, there is provided a product license management system including: the user module is used for receiving a user registration request, examining and approving the user registration request, and after the registration examination and approval is passed, assigning role management authority and user management authority to the user; the product module is used for receiving a product access request of the user, examining and approving the product access request, and accessing the product to the product license management system and managing the product after the examination and approval is passed; and the license management module is used for receiving a license application of the user for the product, approving the license application, and generating a license file of the product after the approval is passed.
Optionally, the role management authority includes at least one of: a super administrator role, a product administrator role, a common user role.
Optionally, the system further comprises: the system comprises an internal API interface and an external interface interacting with a third-party system, wherein the internal interface comprises a verification interface and a generation interface, the external interface comprises a notification interface, if the product request comes from the third-party system, an access code is set, the access code needs to be verified in interaction among the systems, and the third-party system is notified of the access result of the product through the notification interface.
Optionally, the license management module is further configured to: checking an interface type of a license application of the product; dynamically constructing license rule information of the product according to a template under the condition that the interface type is the internal API interface or the interface type is an external interface from a third-party system and the product access code is valid; and calling a verification interface to verify the license application and informing an administrator with the approval authority to approve.
Optionally, the license management module is further configured to maintain license information of the product, and provide license inquiry and download of the product.
According to a further embodiment of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.
In the embodiment of the invention, the product License is created and managed uniformly, and the expansibility and the compatibility are stronger, so that the uniform management and control of the product License is realized.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow diagram of a product license management method according to an embodiment of the invention;
FIG. 2 is a schematic diagram of the overall application of the system according to an embodiment of the invention;
FIG. 3 is an overall block diagram of a system according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of user-role-product relationships according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating function menu permissions according to an embodiment of the present invention;
FIG. 6 is a block diagram of a user module according to an embodiment of the invention;
fig. 7 is a diagram of a License management module structure according to an embodiment of the present invention;
FIG. 8 is a block diagram of a product module according to an embodiment of the invention;
FIG. 9 is a schematic diagram of product organization relationships, according to an embodiment of the invention;
FIG. 10 is a schematic diagram of interface types according to an embodiment of the invention;
FIG. 11 is a schematic diagram of an overall business process according to an embodiment of the invention;
FIG. 12 is a schematic diagram illustrating a process of approval of a user application according to an embodiment of the present invention;
FIG. 13 is a schematic illustration of a product application approval process according to an embodiment of the present invention;
figure 14 is a schematic diagram of a License application approval process according to an embodiment of the present invention;
fig. 15 is a schematic view of an access code update flow according to an embodiment of the present invention;
FIG. 16 is a block diagram of a product license management according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
In the present embodiment, a product license management method is provided, and fig. 1 is a flowchart of a method according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
step S102, a product permission management system receives a user registration request, examines and approves the user registration request, and after the registration examination and approval is passed, role management authority and user management authority are distributed to the user;
step S104, the product license management system receives the product access request of the user, and examines and approves the product access request, and after the access request is examined and approved, the product is accessed to the product license management system and is managed;
and step S106, the product license management system receives the license application of the user for the product, approves the license application, and generates a license file of the product after the license approval is passed.
In step S102 of this embodiment, the role management authority includes at least one of the following: a super administrator role, a product administrator role, a common user role.
In this embodiment, the product license management system may include an internal API interface including a verification interface and a generation interface and an external interface including a notification interface that interacts with a third party system.
In step S106 of this embodiment, after the product license management system receives the license application for the product from the user, the method may further include: checking an interface type of a license application of the product; dynamically constructing license rule information of the product according to a template under the condition that the interface type is an internal API (application program interface) interface or the interface type is an external interface from a third-party system and the product access code is valid; and calling a verification interface to verify the license application and informing an administrator with the approval authority to approve.
In this embodiment, if the product request is from a third-party system, an access code is set, the systems interact with each other to verify the access code, and an access result of the product is notified to the third-party system through a notification interface, where the access result carries the access code.
In step S106 of this embodiment, after the generating the license file of the product, the method may further include: license information for the product is maintained and license inquiry and download of the product is provided.
In this embodiment, at least one of the following may be further included: and sending a reminding message to the user after the registration approval is passed, sending the reminding message to the requester after the access request approval is passed, and sending the reminding message to the requester after the permission approval is passed.
In order to facilitate understanding of the technical solutions provided by the present invention, the following detailed description will be given with reference to embodiments of specific scenarios.
Aiming at the defects of License management of products in the prior art, the embodiment aims to construct a set of management system with strong applicability, strong expansibility, strong compatibility, high safety and strict flow, and strengthen the management and control of the License of the products.
Fig. 2 is an overall application diagram of the License management system constructed in the embodiment. As shown in fig. 2, in the embodiment, the License management system constructed mainly includes 3 large core modules, i.e., a user, a License and a product, and the product is used as an operation unit to implement uniform manufacture and management of the licenses of all products accessing the system, thereby achieving the effects of universal applicability and strict management and control.
Fig. 3 is a block diagram of the overall structure of the License management system according to this embodiment. As shown in fig. 3, the user module is mainly responsible for user registration, user approval, role management, and user management. The user registration is mainly used for automatic login and registration of a new user, the login mode supports manual login and code scanning login, the login is successful, the registration information is submitted, and the successful registration mail informs an administrator to examine and approve. And the user approval is used for processing the user to be approved, and the approval result is notified to the registered user by an email. Role management is used to manage the roles of users, and the roles need to be classified. In this embodiment, the role is set to level 3, which is specifically divided into: a super manager role, a product manager role, and a common user role; the user management is used to maintain the user's regular information. As shown in fig. 4, in the present embodiment, the user mainly possesses the product and role 2 attributes.
The License management module mainly comprises License application, License examination and approval, License management and my License. As shown in fig. 7, the License application function uses a product as an operation unit, a product rule is provided by a template management function, a verification interface is applied for verification, the interface is implemented by the product itself, and an application result is notified to a manager in a mail manner. And the License examination and approval is used for examining and approving the License, the examination and approval generates a License file through a calling interface, and an examination and approval result mail is notified to the application user. License management is used to maintain License information. My License is primarily used to query and download licenses.
The product management module mainly comprises block product application, product approval, product management and template management. As shown in fig. 8, the product application is for applying product access from the system. Product approval is used to allow the product access to the system. Product management is responsible for maintaining product information. Template management is mainly used for maintaining License rule information of products.
In this embodiment, the system mainly includes 3 approval processes: a user application approval process, a product application approval process and a License application approval process. The user application approval process is shown in fig. 12, and the product application approval process is shown in fig. 13. If the product is docked with a third-party system, an access code is set for the product due to security design, the interaction between the systems needs to verify the access code, and the updating mechanism of the access code is shown in fig. 15. See figure 14 for License application approval flow.
In this embodiment, the overall architecture design of the system, including the technical framework and the module design, ensures that the system has strict authority, strict flow and higher security, introduces the concept of the product, does not concern the product type, has universal applicability to general products, introduces the product template to achieve the effect of dynamically constructing License information for the product, realizes unified creation and management of License, provides multiple types of interfaces for the outside, ensures that the system has stronger compatibility, and selects the design of the access code for the external system, thereby ensuring that the system interaction has relatively higher security.
In this embodiment, the overall system construction flow process is as follows:
s1, constructing the web application based on the springboot and the spring-security, and ensuring clear system authority and high safety. In this embodiment, a spring-security framework may be adopted to achieve the effect of strictly controlling each function right, and an overall service logic may be designed according to fig. 11.
And S2, constructing a function module which comprises a user module, a License management module, a product management module, a log management module and a system management module, wherein the log management and system management module belongs to an auxiliary module and has strong expansibility but does not necessarily consist of the auxiliary module.
And S3, controlling the function menu authority, wherein the user associates roles and products, the association relationship is shown in figure 4, and the roles control the function menu to achieve the effect shown in figure 5.
In this embodiment, as shown in fig. 6, the user module mainly includes the following functions:
user registration: the new user logs in and registers firstly, the login mode comprises code scanning and manual login, the login is successful, the registration information is perfected, the login is submitted, and the administrator is informed of approval through the mail.
User approval: and the administrator receives the new user registration mail, logs in the system, approves the user and notifies the user of a result mail.
Role management and user management: the system is used for system maintenance for an administrator, and has strong expansibility.
In this embodiment, as shown in fig. 7, the License management module mainly includes the following functions:
license application: the product is taken as an operation unit, the product must be uploaded with a template, the internal interaction of the system needs to realize verification and interface generation, the interaction between the systems needs to realize notification, verification and interface generation, the classification processing is carried out according to the interface type of the product, the REST and Webservice interfaces need to verify the validity of the product access code, the system dynamically constructs License rule information of the product according to the template, an application is submitted, the verification interface is called, and a mail is notified to an authorized administrator, and the service flow is shown in FIG. 14.
License approval: providing a License unified approval inlet, allowing an administrator to approve License application of a product managed by the administrator, allowing approval to pass, calling a generation interface, generating the License of the product, and notifying an approval result mail to an applicant, wherein a business process is shown in fig. 14.
License management: the License management system is provided for an administrator for use, and is used for maintaining License conventional information and managing product licenses in a unified mode.
My License: for querying and downloading License to the user.
In this embodiment, as shown in fig. 8, the product management module mainly includes the following functions:
product application: filling related product information and applying for accessing the management system.
Product approval: the product access system needs to go through the approval process, and can be accessed into the system formally after approval is passed by a super manager, and the service process is shown in fig. 11.
Product management: maintaining product information, wherein products have an organization relationship, the top organization of the products is a company, the bottom organization is a department, as shown in fig. 7, each product must implement a generation and verification interface of a system, if the product is a non-internal API interface, a notification interface needs to be implemented, the notification interface is used for notifying a third-party system of an access result of the product, the result carries an access code, the interface type is as shown in fig. 10, and the internal API interface is taken as an example, as follows:
1. verification interface
ResOut validateParamsByProd(Map<String,Object>paramMap,String jsonStr,int prodId)；
2. Generating an interface
ResOut execute(Map<String,Object>paramMap,String jsonStr,int prodId)；
Template management: the product application License must have a template, the system provides a standard template, and License rule information of the product is arranged in the template and uploaded to a management platform.
In this embodiment, a database may also be constructed, and all the relationship data is maintained in the database, and according to the above embodiment, the table may be designed according to the following scheme: 1. user table, 2 system function table, 3 role table, 4 product table, 5 product template table, 6 role function relation table, 7 user role relation table, 8 user product relation table, 9 system configuration table and 10 mail table.
In the embodiment of the invention, by constructing a set of unified management system, taking products as operation units, creating and managing License for various products of the system are realized, strict control on License is realized, the system faces to an interface, the realization of the algorithm of the License of the product is not considered, and the universal applicability to the product is realized.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
In this embodiment, a product license management system is further provided, and the system is used to implement the foregoing embodiments and preferred embodiments, and the description already made is omitted for brevity. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 16 is a block diagram of the structure of a product license management system according to an embodiment of the present invention, which includes a user module 10, a product module 20, and a license management module 30, as shown in fig. 16.
The user module 10 is configured to receive a user registration request, examine and approve the user registration request, and assign a role management authority and a user management authority to the user after the registration examination and approval is passed.
And the product module 20 is configured to receive a product access request of the user, approve the product access request, and access the product to the product license management system and manage the product after the approval is passed.
And the license management module 30 is configured to receive a license application for the product from the user, approve the license application, and generate a license file for the product after the approval is passed.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
Embodiments of the present invention also provide a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (13)
1. A product license management method, comprising:
the product permission management system receives a user registration request, examines and approves the user registration request, and after the registration examination and approval is passed, role management authority and user management authority are distributed to the user;
the product license management system receives a product access request of the user, examines and approves the product access request, and after the access request is approved, the product is accessed to the product license management system and is managed;
and the product license management system receives a license application of the user for the product, approves the license application, and generates a license file of the product after the license approval is passed.
2. The method of claim 1, wherein the role management rights comprise at least one of: a super administrator role, a product administrator role, a common user role.
3. The method of claim 1, wherein the product license management system includes an internal API interface and an external interface for interacting with third party systems, wherein the internal interface includes a verification interface and a generation interface, and wherein the external interface includes a notification interface.
4. The method of claim 3, wherein after the product license management system receives the license application for the product from the user, the method further comprises:
checking an interface type of a license application of the product;
dynamically constructing license rule information of the product according to a template under the condition that the interface type is an internal API (application program interface) interface or the interface type is an external interface from a third-party system and the product access code is valid;
and calling a verification interface to verify the license application and informing an administrator with the approval authority to approve.
5. The method of claim 1, wherein if the product request is from a third-party system, setting an access code, interacting between systems requiring verification of the access code, and notifying the third-party system of an access result of the product through a notification interface, wherein the access result carries the access code.
6. The method of claim 1, after generating the license file for the product, further comprising:
license information for the product is maintained and license inquiry and download of the product is provided.
7. The method of claim 1, further comprising at least one of:
sending a reminding message to the user after the registration approval is passed;
sending a reminding message to the requester after the access request examination and approval is passed;
and sending a reminding message to the requester after the approval is passed.
8. A product license management system, characterized by comprising:
the user module is used for receiving a user registration request, examining and approving the user registration request, and after the registration examination and approval is passed, assigning role management authority and user management authority to the user;
the product module is used for receiving a product access request of the user, examining and approving the product access request, and accessing the product to the product license management system and managing the product after the examination and approval is passed;
and the license management module is used for receiving a license application of the user for the product, approving the license application, and generating a license file of the product after the approval is passed.
9. The system of claim 8, further comprising: the system comprises an internal API interface and an external interface interacting with a third-party system, wherein the internal interface comprises a verification interface and a generation interface, the external interface comprises a notification interface, if the product request comes from the third-party system, an access code is set, the access code needs to be verified in interaction among the systems, and the third-party system is notified of the access result of the product through the notification interface.
10. The system of claim 8, wherein the license management module is further configured to:
checking an interface type of a license application of the product;
dynamically constructing license rule information of the product according to a template under the condition that the interface type is the internal API interface or the interface type is an external interface from a third-party system and the product access code is valid;
and calling a verification interface to verify the license application and informing an administrator with the approval authority to approve.
11. The system of claim 8, wherein the license management module is further configured to maintain license information for the product and provide license inquiry and download for the product.
12. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 7 when executed.
13. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911399147.1A CN113127809A (en) | 2019-12-30 | 2019-12-30 | Product license management method and system |
| PCT/CN2020/139157 WO2021136075A1 (en) | 2019-12-30 | 2020-12-24 | Product license management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911399147.1A CN113127809A (en) | 2019-12-30 | 2019-12-30 | Product license management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113127809A true CN113127809A (en) | 2021-07-16 |
Family
ID=76686472
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911399147.1A Pending CN113127809A (en) | 2019-12-30 | 2019-12-30 | Product license management method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113127809A (en) |
| WO (1) | WO2021136075A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114356374A (en) * | 2021-12-30 | 2022-04-15 | 中国第一汽车股份有限公司 | Vehicle data processing method and device and vehicle |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102509034B (en) * | 2011-09-30 | 2014-11-26 | 广东电子工业研究院有限公司 | Software license control method of software license control device |
| CN103838987A (en) * | 2013-06-24 | 2014-06-04 | 电子科技大学 | Software license dynamic authorization management method based on local area network |
| CN106534362B (en) * | 2016-12-14 | 2020-03-27 | 航天通信中心 | Software resource sharing method and device based on cloud platform |
| US11113366B2 (en) * | 2017-06-06 | 2021-09-07 | Infosys Limited | Cryptographic mechanisms for software setup using token-based two-factor authentication |
| CN109033758B (en) * | 2018-08-01 | 2020-04-21 | 北京景行锐创软件有限公司 | License resource access method and system |
-
2019
- 2019-12-30 CN CN201911399147.1A patent/CN113127809A/en active Pending
-
2020
- 2020-12-24 WO PCT/CN2020/139157 patent/WO2021136075A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021136075A1 (en) | 2021-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10348774B2 (en) | Method and system for managing security policies | |
| US10848520B2 (en) | Managing access to resources | |
| US10754932B2 (en) | Centralized consent management | |
| CN113239344B (en) | Access right control method and device | |
| CN113297550A (en) | Authority control method, device, equipment, storage medium and program product | |
| CN111181975B (en) | Account management method, device, equipment and storage medium | |
| CN111062028B (en) | Authority management method and device, storage medium and electronic equipment | |
| US11366912B2 (en) | Context-aware consent management | |
| JP2010503123A (en) | Security permission query | |
| US11580206B2 (en) | Project-based permission system | |
| US20210377272A1 (en) | Secure resource authorization for external identities using remote principal objects | |
| CN102571815B (en) | A kind of method of e-procurement privately owned cloud integrating ERP authenticating user identification | |
| CN112818328A (en) | Multi-system authority management method, device, equipment and storage medium | |
| CN111279317A (en) | Dynamic rule-based transformation of API calls | |
| US20080066169A1 (en) | Fact Qualifiers in Security Scenarios | |
| CN114666124B (en) | Business system login method, login device, electronic equipment and storage medium | |
| US20230222137A1 (en) | Data management platform | |
| CN113127809A (en) | Product license management method and system | |
| CN116305217A (en) | Multi-tenant management method, device, computer equipment and storage medium | |
| US20170300633A1 (en) | Online provisioning for electronic medical records | |
| CN111414591B (en) | Workflow management method and device | |
| Ruo-Fei et al. | A united access control model for systems in collaborative commerce | |
| WO2024120316A1 (en) | System operation permission method and apparatus, and computer device and storage medium | |
| US20220277266A1 (en) | System and method for real-time healthcare claim adjustment | |
| Perkins et al. | Consider identity and access management as a process, not a technology |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |