CN116010905B - Software management method, system and management device - Google Patents
Software management method, system and management device Download PDFInfo
- Publication number
- CN116010905B CN116010905B CN202211703164.1A CN202211703164A CN116010905B CN 116010905 B CN116010905 B CN 116010905B CN 202211703164 A CN202211703164 A CN 202211703164A CN 116010905 B CN116010905 B CN 116010905B
- Authority
- CN
- China
- Prior art keywords
- software
- license
- information
- user terminal
- identifier
- 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.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 111
- 238000000034 method Methods 0.000 claims abstract description 32
- 238000004891 communication Methods 0.000 claims description 18
- 238000012545 processing Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 13
- 238000012544 monitoring process Methods 0.000 claims description 10
- 230000004927 fusion Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 10
- 239000002699 waste material Substances 0.000 description 5
- 230000005856 abnormality Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a software management method, a system and a management device, wherein the method comprises the following steps: the store server receives a software license request sent by the user terminal, generates a credit request according to the usable software module identifier, the user identity information and the user terminal identifier when the user identity information exists in the identity database and the idle license module exists in the order database, enables the license management server to generate a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sends the white list writing request to the license server, and enables the license server to write the usable software module identifier and the user terminal identifier into a credit white list. After the order request of the user is acquired, the identity information of the user is determined, and then the license management server and the license server are introduced, so that the automatic license management of various software resources is realized.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a software management method, system, and management device.
Background
The oil exploration and development is a comprehensive, complex and technically intensive work, and the long working chain is adopted, so that the production of a large number of specialized software is promoted by the characteristics.
In the current mode, the server performs one-to-one correspondence between the software types and the user demands on the software resource management.
However, in the prior art, because of the diversified demands of different stages and different users on the types and the quantity of the software, one-to-one software resource management modes cause the shortage or the waste of the software resources, and the user experience is poor.
Disclosure of Invention
The application provides a software management method, a system and a management device, which are used for solving the technical problems of insufficient or waste of software resources and poor user experience caused by one-to-one software resource management mode due to diversified requirements of different stages and different users on software types and quantity in the prior art.
In a first aspect, the present application provides a software management method applied to a store server, the method comprising:
receiving a software license request sent by a user terminal, wherein the software license request comprises a software identifier to be used, user identity information and a user terminal identifier;
when the user identity information exists in the identity database and the idle permission module exists in the order database, a credit request is generated according to the usable software module identification, the user identity information and the user terminal identification, so that the permission management server generates a white list writing request according to the usable software module identification, the user identity information and the user terminal identification, and the white list writing request is sent to the permission server, so that the permission server writes the usable software module identification and the user terminal identification into the credit white list.
Further, the method further comprises:
receiving software use information sent by the license management server; the software use information comprises a user terminal identifier, a software module identifier, login time and logout time;
the local statistical order information and the software use information are used for fusion, so that the software use information of each order is obtained; the order information includes: order identification, software module identification, purchased license number, occupied license number, and free license number;
and uploading the software use information of each order to a certificate.
In a second aspect, the present application provides a software management method, the method being applied to a rights management server, the method comprising:
receiving a credit request sent by a store server, wherein the credit request is generated according to a usable software module identifier, user identity information and a user terminal identifier when the store server receives a software license request sent by a user terminal and determines that user identity information exists in an identity database and determines that an idle license module exists in a store server order database; the trust request comprises a usable software module identifier, user identity information and a user terminal identifier;
and generating a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sending the white list writing request to a license server, so that the license server writes the usable software module identifier, the user identity information and the user terminal identifier into a credit-giving white list.
Further, the method further comprises:
monitoring and collecting license information between the license server and the user terminal, wherein the license information comprises a user terminal identifier, a software module identifier and a license occupation time period;
counting the license information to obtain the software use information, and sending the software use information to a store server; fusing the order information of the store server using the local statistics and the software use information to obtain the software use information of each order; the order information includes: order identification, software module identification, purchased license number, occupied license number, and free license number; and the software usage information of each order is uploaded and verified.
In a third aspect, the present application provides a store server comprising a memory, a processor, the memory storing a computer program executable on the processor, the processor implementing the method of the first aspect when executing the computer program.
In a fourth aspect, the present application provides a license management server, comprising a memory, a processor, the memory storing a computer program executable on the processor, the processor implementing the method of the second aspect when executing the computer program.
In a fifth aspect, the present application provides a blockchain-based software management system, including a software operating system, a blockchain system, a supervisory system, and a partner management system, the software operating system including a store server according to the third aspect, a license management server according to the fourth aspect;
the block chain system is used for receiving processing information and software use information of each order sent by the software operation system; the monitoring system is also used for receiving the monitoring information sent by the monitoring system; the system is also used for receiving reconciliation information sent by the partner management system;
the software operation system and the blockchain system are communicated through a blockchain communication module; the supervision system and the blockchain system are communicated through a blockchain communication module; the partner management system and the blockchain system are communicated through a blockchain communication module.
Further, the blockchain system specifically includes:
an operator blockchain node, a supervisory blockchain node, and a partner blockchain node;
the operation block link point is used for receiving processing information and software use information of each order sent by the software operation system;
the supervision block link point is used for receiving supervision information sent by the supervision system;
the partner blockchain node is used for receiving reconciliation information sent by the partner management system;
the operation block chain node and the supervision block chain node are communicated through software; the partner blockchain node and the supervision blockchain node are communicated through software; the partner blockchain node and the operating blockchain node are in communication through software.
In a sixth aspect, the present application provides a management apparatus, the apparatus being applied to a store server, the apparatus comprising:
the system comprises an acquisition module, a user terminal and a control module, wherein the acquisition module is used for receiving a software license request sent by the user terminal, and the software license request comprises a software identifier to be used, user identity information and a user terminal identifier;
and the processing module is used for generating a credit request according to the usable software module identifier, the user identity information and the user terminal identifier when the user identity information exists in the identity database and the idle permission module exists in the order database, so that the permission management server generates a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sends the white list writing request to the permission server, so that the permission server writes the usable software module identifier and the user terminal identifier into a credit white list.
In a seventh aspect, the present application provides a management apparatus, the apparatus being applied to a license management server, the apparatus comprising:
the acquisition module is used for receiving a credit request sent by the store server, wherein the credit request is generated according to a usable software module identifier, user identity information and a user terminal identifier when the store server receives a software license request sent by the user terminal and determines that user identity information exists in the identity database and determines that an idle license module exists in the store server order database; the trust request comprises a usable software module identifier, user identity information and a user terminal identifier;
and the processing module is used for generating a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sending the white list writing request to the license server so that the license server writes the usable software module identifier, the user identity information and the user terminal identifier into the credit giving white list.
In an eighth aspect, the present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the methods of the first and second aspects.
In a ninth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the methods of the first and second aspects.
According to the software management method, system and management device provided by the application, after the software license request of the user is acquired, the identity information of the user is further determined, and then the license management server and the license server are introduced to generate the credit white list, so that the automatic license management of multiple users and multiple types of software resources is realized, and the problems of poor user experience caused by one-to-one software resource management mode due to the diversified requirements of different stages and different users on the types and quantity of software in the prior art are solved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic flow chart of a software management method according to an embodiment of the present application;
FIG. 2 is a flow chart of a method for uploading software usage information for each order to a blockchain system according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a software management system according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a management device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another management apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a store server according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a license management server according to an embodiment of the present application.
Specific embodiments of the present disclosure have been shown by way of the above drawings and will be described in more detail below. These drawings and the written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
The oil exploration and development is a comprehensive, complex and technically intensive work, and the long working chain is adopted, so that the production of a large number of specialized software is promoted by the characteristics.
In the current mode, the server performs one-to-one correspondence between the software types and the user demands on the software resource management.
However, in the prior art, because of the diversified demands of different stages and different users on the types and the quantity of the software, one-to-one software resource management modes cause the shortage or the waste of the software resources, and the user experience is poor.
Aiming at the problems, the embodiment of the application provides a software management method, a system and a management device, which aim to solve the technical problems of poor user experience caused by insufficient or waste of software resources in a one-to-one software resource management mode due to diversified requirements of different stages and different users on software types and quantity in the prior art. The technical conception of the application is as follows: after the store server acquires the user software license request of the user terminal, the identity information of the user is further determined, the store server sends a credit request to the license management server, the license management server generates a white list writing request, the white list writing request is sent to the license server, and the license server generates a trusted white list.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 is a flow chart of a software management method according to an embodiment of the present application, as shown in fig. 1, where the method includes:
101. the user terminal sends a software license request to the store server.
The execution subject of the present embodiment may be, for example, an electronic device, or a terminal device, or a license management server, or a license server, or a software management apparatus or device, or a store server, or other apparatus or device that may execute the present embodiment, which is not limited thereto.
The method comprises the steps that a user selects professional software to be used on an application store of a user terminal, wherein the user terminal can be a computer terminal and a server terminal; and transmitting a software license request of the professional software of the right to be purchased to a store server through the application store, wherein the software license request comprises a used software identifier, user identity information and a user terminal identifier.
102. And when the store server determines that the identity database has user identity information and the order database has an idle permission module, a credit request is generated according to the usable software module identification, the user identity information and the user terminal identification.
The store server comprises an identity management module, and the store server matches user identity information sent by a user terminal in an identity database through the identity management module and screens related orders through the user identity information; the store server comprises an order management module, a license management module and a metering module, and judges whether the store server has an idle license module in the user related order specification through the order management module, the license management module and the metering module; after the store server determines the user identity information in the identity database and determines that there is an empty license module in the order database user-related order specification, the store server generates a credit request according to the available software module identification, the user identity information and the user terminal identification.
103. The store server sends a credit request to the license management server.
Illustratively, the license request is for the store server to acquire rights to use the specialized software, such as license, after acquiring the specialized software, so that the store server sends a credit request to the license management server via bus communication.
104. The license management server generates a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier.
Illustratively, the license management server includes a license granting module by which the license management server generates the whitelist write request from the software module identification, the user identity information, and the user terminal identification that are available.
105. The license management server sends a white list write request to the license server.
Illustratively, in order to efficiently manage license information of a user using software, the license management server generates a white list write request, and after the license management server generates the white list write request, the license management server transmits the white list write request to the license server through bus communication.
106. The license server writes the usable software module identification and the user terminal identification into a credit whitelist.
Illustratively, the license server, after receiving the white list writing request, writes the usable software identifier and the user terminal identifier into a trusted white list, implements automatic license management of the software resource of the user according to the trusted white list,
in the embodiment of the application, after the store server acquires the software license request sent by the user terminal, the identity information of the user is further determined, license request information is generated, and then the license management server and the license server are introduced to generate the credit whitelist, so that the automatic license management of different users and different types of software resources is realized, and the problem that in the prior art, one-to-one software resource management mode causes insufficient or waste of software resources and poor user experience is solved because the requirements of different stages and different users on the types and the quantity of software are diversified.
FIG. 2 is a flowchart of a method for uploading software usage information for each order to a blockchain system according to an embodiment of the present application, as shown in FIG. 2, the method includes:
201. the license management server monitors license information between the license server and the user terminal.
Illustratively, the license management server monitors that the user terminal sends a request license to the license server, which sends the license to the user terminal by reading the local credit whitelist. And when the user finishes using the professional software and logs out the professional software, the license server also recovers the professional software license. The license management server gathers license information about the license occupied by the user stored by the license server.
202. And acquiring and sorting the license information by the license management server to obtain software use information.
Illustratively, the license management server counts the user terminal identifier, the software identifier and the license time period in the license information to obtain all the software usage information, wherein the software usage information includes: user terminal identification, software module identification, and license entry time and exit time.
203. The license management server transmits the software usage information to the store server.
Illustratively, the license management server transmits the software usage information and the user identification information to the store server through data communication.
204. The store server uses the locally counted order information and the software use information to fuse and obtain the software use information of each order.
Illustratively, the store server stores order information locally, wherein the order information includes: order identification, software module identification, purchased license number, occupied license number, and free license number; the store server sorts the locally counted user related order information, and judges whether the order has idle permission or not by combining the software use information, so that the software use information of each order is finally obtained.
205. The store server links the software usage information for each order to a certificate.
Illustratively, the store server uploads the software usage information for each order to the blockchain system via software communications. An automatic, accurate, transparent license management and data metering mode is provided for users.
In the embodiment of the application, a license management server monitors license information between the license server and a user terminal, and acquires and sorts the license information to obtain software use information, wherein a user terminal identifier and a software identifier are matched with user identity information; the license management server sends software use information to the store server, and the store server fuses the locally counted order information and the software use information to obtain the software use information of each order; the store server uploads the software usage information for each order to the blockchain system. The system and the method support various license management types and metering capabilities, flexibly issue licenses to users, and the users can flexibly experience the service of the professional software system according to various metering modes such as time, quantity, resource quantity and the like according to requirements. An automatic, accurate, transparent license management and data metering mode is provided for users.
Fig. 3 is a schematic structural diagram of a software management system according to an embodiment of the present application, and as shown in fig. 3, a software management system 300 includes: a software operations system 301, a blockchain system 304, a supervisory system 302, and a partner management system 303;
illustratively, the software operating system 301 is configured to generate software usage information for each order and upload the software usage information for each order to the blockchain system; wherein the software operating system 301 includes a store server, a license management server, and a license server;
the store server comprises an identity management module, a commodity information management module, a transaction management module and a blockchain communication module. The identity management module is responsible for managing and verifying identity information of users and partners, asset attribution information and other related information. The commodity information management module is responsible for managing commodity information of professional software, including commodity specification, pricing, service and other information. The transaction management module is responsible for managing transaction related information such as transactions among users, user payments, transaction bills and the like, and sending user order information to the license management server.
The license server is responsible for storing a license white list and issuing software licenses according to the white list.
The license management server comprises a software monitoring module, a license granting module and a metering module. The software monitoring module is responsible for monitoring the real-time online user condition of the software license server. The license granting module is responsible for receiving the grant information sent by the store server and managing the white list stored in the license server. The metering module is responsible for reading a professional software running log according to an API (application program interface) opened by the professional software and collecting metering information such as the use time length, the use flow and the like of the professional software of a user; for professional software without running logs, the metering module can sort statistical metering information according to the user permission occupation information acquired by the software monitoring module.
The blockchain system 304 includes: an operator block chain node 3041, a supervision block link point 3043, and a partner block link point 3042; the operation blockchain node 3041 is configured to receive software usage information of each order sent by the software operation system 301; the supervision block chain node 3043 is configured to receive supervision information sent by the supervision server system 303; the partner block link point 3042 is configured to receive accounting information sent by the partner management system 303; the operation block chain node 3041 and the supervision block chain link point 3043 are in communication through software; the partner blockchain node 3042 communicates with the superblockchain link point 3043 through software; the partner block link point 3042 and the operator block link point 3041 communicate with each other through software. The blockchain system 304 is developed based on HyperledgerFabric, and the communication functions with the various servers and systems are implemented through the Fabric software development kit SDK. The operations blockchain node 3041, the supervision blockchain node 3043, and the partner blockchain node 3042 synchronize the information of the respective systems and server uplinks at regular time to form a common ledger. The public ledger stores three types of credential data: data logging, transaction credentials, use credentials. The data storage certificate mainly comprises user information, asset information, professional software price, attribution and other information. The transaction vouchers mainly comprise transaction information such as professional software transactions, service transactions, changes, order bills, payment situations and the like. The use certificate mainly comprises use records of the shared authorization software, such as use metering information of user use duration, use flow and the like.
The supervision system 302 is composed of an identity management module, a query module, a supervision module, and a blockchain communication module. The identity management module is responsible for managing and verifying identity information of users and partners, asset attribution information and other related information. The query module is responsible for sending a request to the blockchain system to query corresponding order information. The supervision module can supervise orders responsible by supervision staff, the supervision staff checks the order information inquired by the inquiry module, and when abnormality exists, the supervision module feeds back the abnormality information. The blockchain communication module is responsible for timing the uploading of query records, exception feedback information, etc. to the blockchain system 304.
Partner management system 303 includes an identity management module, a query module, a reconciliation module, and a blockchain communication module. The identity management module is responsible for managing and verifying identity information of users and partners, asset attribution information and other related information. The query module is responsible for sending a request to the blockchain system 304, querying corresponding order information, and the partner can query orders belonging to all professional software of the user through the query module, and confirm the orders and query reconciliation through the reconciliation module. The blockchain communication module is responsible for timing the uploading of query records, reconciliation records, feedback information, etc. to the blockchain system 304.
In the embodiment of the application, the user orders after the application store selects professional software, and the professional software is uploaded to the blockchain system by the store server at regular time. When the user starts professional software, the software license request is sent to the application store through the user terminal, and the credit request is sent to the license management server in real time through the store server. The license management server sends a white list writing request to the license server, and the license server issues a license according to the white list information. And the license management server returns metering information collected and managed in real time according to the use condition of the user to the application store server, and the metering information is uploaded to the blockchain system at regular time by the application store. And the supervisory personnel inquires the transaction and metering information on the blockchain through the supervisory system and feeds back the supervisory information to the chain at regular time. The partner inquires the transaction and metering information through the partner management system and feeds back the accounting information to be linked in a timing mode. The information such as transaction information, permission and metering information, supervision information, account checking information, inquiry records and the like are uplink to form a public account book, and are stored on each node in a decentralization mode. The information on each block chain node is synchronized at fixed time to ensure the consistency of the public account book; the security of the software management system transaction is ensured, and a mutually trusted software management system for professional software service transaction is created. Meanwhile, the user can flexibly meet the self requirements according to the provided license management mode and metering function.
Fig. 4 is a schematic structural diagram of a management apparatus according to an embodiment of the present application, as shown in fig. 4, an apparatus 400 is applied to a store server, and the apparatus 400 includes:
an obtaining module 401, configured to receive a software license request sent by a user terminal, where the software license request includes a software identifier to be used, user identity information, and a user terminal identifier;
and the processing module 402 is configured to generate a trust request according to the usable software module identifier, the user identity information and the user terminal identifier when it is determined that the user identity information exists in the identity database and it is determined that the order database has an idle license module, enable the license management server to generate a white list write request according to the usable software module identifier, the user identity information and the user terminal identifier, and send the white list write request to the license server, so that the license server writes the usable software module identifier and the user terminal identifier into the trust white list.
In an embodiment, the apparatus 400 further comprises:
the obtaining module 401 is further configured to receive software usage information sent by the license management server; the software use information comprises a user terminal identifier, a software module identifier, login time and logout time;
the processing module 402 is further configured to fuse the order information and the software usage information that are locally counted, so as to obtain software usage information of each order; the order information includes: order identification, software module identification, purchased license number, occupied license number, and free license number;
the processing module 402 is further configured to upload the software usage information of each order.
The device of the embodiment may execute the technical scheme in the above method, and the specific implementation process and the technical principle are the same and are not described herein again.
Fig. 5 is a schematic structural diagram of another management apparatus according to an embodiment of the present application, as shown in fig. 5, an apparatus 500 is applied to a license management server, and the apparatus 500 includes:
the acquiring module 501 is configured to receive a credit request sent by a store server, where the credit request is generated according to a usable software module identifier, user identity information and a user terminal identifier when the store server receives a software license request sent by a user terminal and determines that user identity information exists in an identity database and determines that an idle license module exists in an order database of the store server; the trust request comprises a usable software module identifier, user identity information and a user terminal identifier;
the processing module 502 is configured to generate a whitelist writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and send the whitelist writing request to the license server, so that the license server writes the usable software module identifier, the user identity information and the user terminal identifier into the trusted whitelist.
In an embodiment, the apparatus 500 further comprises:
the processing module 502 is further configured to monitor and collect license information between the license server and the user terminal, where the license information includes a user terminal identifier, a software module identifier, and a license occupation period.
Fig. 6 is a schematic structural diagram of a store server according to an embodiment of the present application, and as shown in fig. 6, a store server 600 includes: a memory 601 and a processor 602;
wherein the memory 601 is for storing computer instructions executable by the processor;
the processor 602, when executing computer instructions, implements the steps of the methods of the embodiments described above. Reference may be made in particular to the relevant description of the embodiments of the method described above.
Alternatively, the memory 601 may be separate or integrated with the processor 602. When the memory 601 is provided separately, the detection device further comprises a bus for connecting the memory 601 and the processor 602.
Fig. 7 is a schematic structural diagram of a license management server according to an embodiment of the present application, and as shown in fig. 7, a license management server 700 includes: a memory 701 and a processor 702;
wherein the memory 701 is used for storing computer instructions executable by the processor;
the processor 702, when executing the computer instructions, implements the steps of the method in the above embodiments. Reference may be made in particular to the relevant description of the embodiments of the method described above.
Alternatively, the memory 701 may be separate or integrated with the processor 702. When the memory 701 is provided separately, the detection device further comprises a bus for connecting the memory 701 and the processor 702.
Embodiments of the present application also provide a non-transitory computer-readable storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the method provided by the above embodiments.
The embodiment of the application also provides a computer program product, which comprises: a computer program stored in a readable storage medium, from which at least one processor of an electronic device can read, the at least one processor executing the computer program causing the electronic device to perform the solution provided by any one of the embodiments described above.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (8)
1. A method of software management, the method being applied to a store server, the method comprising:
receiving a software license request sent by a user terminal, wherein the software license request comprises a software identifier to be used, user identity information and a user terminal identifier;
when the user identity information exists in the identity database and the idle permission module exists in the order database, generating a credit request according to the usable software module identifier, the user identity information and the user terminal identifier, enabling a permission management server to generate a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sending the white list writing request to the permission server, so that the permission server writes the usable software module identifier and the user terminal identifier into a credit white list;
receiving software use information sent by the license management server; the software use information comprises a user terminal identifier, a software module identifier, login time and logout time;
the local statistical order information and the software use information are used for fusion, so that the software use information of each order is obtained; the order information includes: order identification, software module identification, purchased license number, occupied license number, and free license number;
and uploading the software use information of each order to a certificate.
2. A software management method, wherein the method is applied to a license management server, the method comprising:
receiving a credit request sent by a store server, wherein the credit request is generated according to a usable software module identifier, user identity information and a user terminal identifier when the store server receives a software license request sent by a user terminal and determines that user identity information exists in an identity database and determines that an idle license module exists in a store server order database; the trust request comprises a usable software module identifier, user identity information and a user terminal identifier;
generating a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sending the white list writing request to a license server, so that the license server writes the usable software module identifier, the user identity information and the user terminal identifier into a credit-giving white list;
monitoring and collecting license information between the license server and the user terminal, wherein the license information comprises a user terminal identifier, a software module identifier and a license occupation time period;
sorting the license information to obtain software use information; the software use information comprises a user terminal identifier, a software module identifier, login time and logout time; the software use information is sent to the store server, so that the store server uses the locally counted order information and the software use information to be fused, and the software use information of each order is obtained; the order information includes: order identification, software module identification, purchased license number, occupied license number and idle license number, and the software use information of each order is stored in a chain.
3. A management device for application to a store server, the device comprising:
the system comprises an acquisition module, a user terminal and a control module, wherein the acquisition module is used for receiving a software license request sent by the user terminal, and the software license request comprises a software identifier to be used, user identity information and a user terminal identifier;
the processing module is used for generating a credit request according to the usable software module identifier, the user identity information and the user terminal identifier when the user identity information exists in the identity database and the idle permission module exists in the order database, so that the permission management server generates a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sends the white list writing request to the permission server, and the permission server writes the usable software module identifier and the user terminal identifier into a credit white list;
the acquisition module is further used for receiving the software use information sent by the license management server; the software use information comprises a user terminal identifier, a software module identifier, login time and logout time;
the processing module is further used for fusing the order information counted locally with the software use information to obtain the software use information of each order; the order information includes: order identification, software module identification, purchased license number, occupied license number, and free license number;
and the processing module is also used for uploading the software use information of each order to a certificate.
4. A management apparatus, the apparatus being applied to a license management server, the apparatus comprising:
the acquisition module is used for receiving a credit request sent by the store server, wherein the credit request is generated according to a usable software module identifier, user identity information and a user terminal identifier when the store server receives a software license request sent by the user terminal and determines that user identity information exists in the identity database and determines that an idle license module exists in the store server order database; the trust request comprises a usable software module identifier, user identity information and a user terminal identifier;
the processing module is used for generating a white list writing request according to the usable software module identifier, the user identity information and the user terminal identifier, and sending the white list writing request to the license server so that the license server writes the usable software module identifier, the user identity information and the user terminal identifier into a credit white list;
the processing module is further used for monitoring and collecting license information between the license server and the user terminal, wherein the license information comprises a user terminal identifier, a software module identifier and a license occupation time period; sorting the license information to obtain software use information; the software use information comprises a user terminal identifier, a software module identifier, login time and logout time; the software use information is sent to the store server, so that the store server uses the locally counted order information and the software use information to be fused, and the software use information of each order is obtained; the order information includes: order identification, software module identification, purchased license number, occupied license number and idle license number, and the software use information of each order is stored in a chain.
5. A store server comprising a memory, a processor, said memory having stored thereon a computer program executable on said processor, said processor implementing the method of claim 1 when said computer program is executed.
6. A license management server comprising a memory, a processor, the memory storing a computer program executable on the processor, the processor implementing the method of claim 2 when executing the computer program.
7. A blockchain-based software management system comprising a software operating system, a blockchain system, a supervisory system and a partner management system, the software operating system comprising the store server of claim 5, the license management server of claim 6;
the block chain system is used for receiving processing information and software use information of each order sent by the software operation system; the monitoring system is also used for receiving the monitoring information sent by the monitoring system; the system is also used for receiving reconciliation information sent by the partner management system;
the software operation system and the blockchain system are communicated through a blockchain communication module; the supervision system and the blockchain system are communicated through a blockchain communication module; the partner management system and the blockchain system are communicated through a blockchain communication module.
8. The system of claim 7, wherein the blockchain system specifically comprises:
an operator blockchain node, a supervisory blockchain node, and a partner blockchain node;
the operation block link point is used for receiving the software use information of each order sent by the software operation system;
the supervision block link point is used for receiving supervision information sent by the supervision system;
the partner blockchain node is used for receiving reconciliation information sent by the partner management system;
the operation block chain node and the supervision block chain node are communicated through software; the partner blockchain node and the supervision blockchain node are communicated through software; the partner blockchain node and the operating blockchain node are in communication through software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211703164.1A CN116010905B (en) | 2022-12-29 | 2022-12-29 | Software management method, system and management device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211703164.1A CN116010905B (en) | 2022-12-29 | 2022-12-29 | Software management method, system and management device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116010905A CN116010905A (en) | 2023-04-25 |
| CN116010905B true CN116010905B (en) | 2023-11-03 |
Family
ID=86031250
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211703164.1A Active CN116010905B (en) | 2022-12-29 | 2022-12-29 | Software management method, system and management device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116010905B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119691705A (en) * | 2023-09-22 | 2025-03-25 | 华为云计算技术有限公司 | A software authorization method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546294A (en) * | 2013-10-10 | 2014-01-29 | 小米科技有限责任公司 | Entrance guard authorization method, entrance guard authorization device and entrance guard authorization equipment |
| CN104134122A (en) * | 2014-07-30 | 2014-11-05 | 华为技术有限公司 | Method and device for applying for license |
| KR20150056244A (en) * | 2013-11-15 | 2015-05-26 | (주)닥터소프트 | Terminal device and software managing method thereof |
| CN111355726A (en) * | 2020-02-26 | 2020-06-30 | 广东工业大学 | Identity authorization login method and device, electronic equipment and storage medium |
| CN113553588A (en) * | 2021-07-28 | 2021-10-26 | 中国南方电网有限责任公司 | Terminal software management method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006101549A2 (en) * | 2004-12-03 | 2006-09-28 | Whitecell Software, Inc. | Secure system for allowing the execution of authorized computer program code |
| KR101985179B1 (en) * | 2017-12-26 | 2019-09-03 | 상명대학교 천안산학협력단 | Blockchain based id as a service |
-
2022
- 2022-12-29 CN CN202211703164.1A patent/CN116010905B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546294A (en) * | 2013-10-10 | 2014-01-29 | 小米科技有限责任公司 | Entrance guard authorization method, entrance guard authorization device and entrance guard authorization equipment |
| KR20150056244A (en) * | 2013-11-15 | 2015-05-26 | (주)닥터소프트 | Terminal device and software managing method thereof |
| CN104134122A (en) * | 2014-07-30 | 2014-11-05 | 华为技术有限公司 | Method and device for applying for license |
| CN111355726A (en) * | 2020-02-26 | 2020-06-30 | 广东工业大学 | Identity authorization login method and device, electronic equipment and storage medium |
| CN113553588A (en) * | 2021-07-28 | 2021-10-26 | 中国南方电网有限责任公司 | Terminal software management method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116010905A (en) | 2023-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113222752B (en) | Block chain based data processing system, method, computing device and storage medium | |
| CN110599276B (en) | Bill reimbursement method, device and equipment and computer storage medium | |
| CN104240342A (en) | Access control method and device | |
| CN113535774A (en) | A business data processing method and device | |
| CN110084698A (en) | Interactive system, exchange method and device based on block chain | |
| CN110602215B (en) | Resource processing method based on alliance block chain and alliance block chain system | |
| CN107689009A (en) | Annuity data processing method, device, server and storage medium | |
| CN116010905B (en) | Software management method, system and management device | |
| CN104240014A (en) | Door access control method and door access control platform | |
| CN114201166A (en) | Message information generation method and device, electronic equipment and storage medium | |
| CN114140223B (en) | Financial product issuing auditing method, system and device based on alliance chain | |
| CN115600167A (en) | Login-free access and embedded configuration method and equipment | |
| CN114297841A (en) | Simulation model resource system construction system and construction method | |
| KR20210003396A (en) | Method for providing online exchange service | |
| CN106487799A (en) | Facility information storage system based on cloud platform | |
| CN101841800A (en) | Prepayment service charging method and system | |
| CN110336872B (en) | Method, device and system for acquiring third-party data | |
| KR20220015062A (en) | Syatem for collecting electronic tax invoice and making a erp connection and method thereo | |
| CN105787791B (en) | Service request processing method and device | |
| CN111401873A (en) | Task creation method and device, storage medium and electronic equipment | |
| WO2024078109A1 (en) | Multi-blockchain data processing method and apparatus, and device, system and medium | |
| KR102107454B1 (en) | System for multiplication of financial payment networks, method for financial services using the same and computer program for the same | |
| KR100777670B1 (en) | Financial Transaction History Provision System and Method | |
| KR102214229B1 (en) | Method for providing online exchange service | |
| CN112967058A (en) | Block chain based electronic account book management method |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |