CN113127846B - Software authorization method, device, equipment and storage medium - Google Patents
Software authorization method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113127846B CN113127846B CN202110535414.4A CN202110535414A CN113127846B CN 113127846 B CN113127846 B CN 113127846B CN 202110535414 A CN202110535414 A CN 202110535414A CN 113127846 B CN113127846 B CN 113127846B
- Authority
- CN
- China
- Prior art keywords
- authorization
- sub
- software
- account
- authorized
- 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
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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
-
- 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Human Resources & Organizations (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a software authorization method, a device, equipment and a storage medium, which are applied to a production side and comprise the following steps: acquiring a mother account number distributed to the producer by an authorizer according to the order information of the producer and the type and the authorized quantity of authorized software corresponding to the mother account number; and distributing a sub-account corresponding to the parent account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the parent account, so that the foundry can produce the terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account. According to the method and the system, software is authorized by setting the primary and secondary accounts, and the producer creates and manages the secondary accounts based on the primary accounts distributed by the authorizer, so that the difficulty in maintaining the authorized accounts is reduced, and the authorization efficiency is improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a software authorization method, apparatus, device, and storage medium.
Background
Along with the continuous development of internet technology, the product form is also greatly changed in the current society, and the selling software service is gradually becoming an important product form. The back of a product containing a plurality of professional technical achievements is often the result of the common efforts of a plurality of technical teams, so the software authorization process involves a plurality of roles, namely product development, authorization framework design, encryption scheme implementation, authorization information communication, production line production interaction and supply chain management, each link is systematic and complex work, and how to balance the safety and the production and marketing benefits is a difficult problem.
The current situation of software product production in a factory is very common, and one producer corresponds to one authorized account number, which is not beneficial to the safety of account number maintenance. If a plurality of accounts are provided at the same time, the maintenance cost is increased for an authorized party, the accounts are difficult to manage, and thus, substantial problems such as account authorization, encryption process and the like are brought to the authorization security.
Disclosure of Invention
In view of this, the present invention aims to provide a software authorization method, device, equipment and storage medium, where software is authorized by setting primary and secondary accounts, and a producer creates and manages a secondary account based on a primary account allocated by an authorizer, so as to reduce difficulty in maintaining an authorized account and improve authorization efficiency. The specific scheme is as follows:
a first aspect of the present application provides a software authorization method, applied to a producer, including:
acquiring a parent account number distributed for the producer by an authorizer according to the order information of the producer and the type and the authorization quantity of authorization software corresponding to the parent account number;
and distributing a sub-account corresponding to the parent account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the parent account, so that the foundry can produce the terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account.
Optionally, the allocating, based on the parent account, a child account corresponding to the parent account and the type and authorized number of the authorized software corresponding to the child account to each foundry according to a production plan includes:
and accessing an authorization main server by logging in the parent account, and distributing a child account corresponding to the parent account and the type and authorization quantity of the authorization software corresponding to the child account for each foundry according to a production plan by using the authorization main server.
Optionally, the manufacturing factory produces the terminal device including the authorized software according to the type and the authorized number of the authorized software of the assigned sub-account, including:
and the factory agent logs in the allocated sub account number to access the authorization main server so as to authorize the terminal equipment containing the authorization software through the authorization main server.
Optionally, the manufacturing factory produces the terminal device including the authorized software according to the type and the authorized number of the authorized software of the assigned sub-account, including:
the factory-substitute login assigned sub-account number accesses a factory sub-server so as to authorize the terminal equipment containing the authorization software through the factory sub-server; the factory sub-server is authorized by the authorization main server and used for issuing an authorization certificate corresponding to the terminal equipment containing authorization software based on the request of the factory agent.
Optionally, the logging in the allocated sub-account to access the factory sub-server on behalf of the factory to authorize the terminal device including the authorization software through the factory sub-server includes:
and the factory-representative accesses the factory sub-server by logging in the allocated sub-account through the production line client, so that the factory sub-server generates an authorization certificate corresponding to the terminal equipment by using the universal unique identification code of the terminal equipment containing authorization software based on the request of the production line client.
Optionally, after the foundry produces the terminal device including the authorized software according to the type and the authorized amount of the authorized software of the assigned sub-account, the foundry further includes:
and sending the authorization quantity corresponding to the sub-account number and the quantity of the actually issued authorization certificates on the factory sub-servers to the authorization main server so as to match the authorization main server with the flow data stored in the authorization main server.
Optionally, the sending the authorization quantity corresponding to the sub-account on the factory sub-server and the quantity of the actually issued authorization certificates to the authorization master server so that the authorization master server matches with the flow data stored in the authorization master server includes:
and uploading and storing the authorization number corresponding to the sub-account number and the number of the actually issued authorization certificates on the factory sub-server to a backup server so that the main authorization server can match the flow data on the backup server with the flow data stored by the main authorization server.
A second aspect of the present application provides a software authorization apparatus, applied to a production side, including:
the system comprises a primary account number acquisition module, a primary account number acquisition module and a primary account number acquisition module, wherein the primary account number acquisition module is used for acquiring a primary account number distributed by an authorizing party for the producing party according to the order information of the producing party and the type and the authorized quantity of authorized software corresponding to the primary account number;
and the sub-account generation module is used for allocating sub-accounts corresponding to the parent account and the types and the authorized quantities of the authorized software corresponding to the sub-accounts to each agent factory according to the production plan based on the parent account, so that the agent factory can produce the terminal equipment containing the authorized software according to the types and the authorized quantities of the authorized software of the allocated sub-accounts.
A third aspect of the application provides an electronic device comprising a processor and a memory; wherein the memory is used for storing a computer program which is loaded and executed by the processor to implement the aforementioned software authorization method.
A fourth aspect of the present application provides a computer-readable storage medium having stored therein computer-executable instructions that, when loaded and executed by a processor, implement the aforementioned software authorization method.
In the method, a producer firstly obtains a parent account number distributed by an authorizer for the producer according to order information of the producer and the type and authorized quantity of authorized software corresponding to the parent account number; and then distributing a sub-account corresponding to the mother account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the mother account, so that the foundry can produce terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account. According to the method and the system, the software is authorized by setting the primary and secondary accounts, and the producer creates and manages the secondary accounts on the basis of the primary account distributed by the authorizer, so that the difficulty in maintaining the authorized accounts is reduced, and the software authorization efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flow chart of a software authorization method provided by the present application;
FIG. 2 is a flowchart of a specific software authorization method provided in the present application;
FIG. 3 is a flow chart of another specific software authorization method provided by the present application;
FIG. 4 is a diagram of a software authorization system architecture provided by the present application;
FIG. 5 is a functional block diagram of an authorization master server provided in the present application;
FIG. 6 is a device model management interface provided herein;
FIG. 7 is an authorized recharge interface provided herein;
FIG. 8 is a pipelined query interface provided by the present application;
FIG. 9 is a local data statistics interface provided herein;
FIG. 10 is a factory management interface provided herein;
FIG. 11 is a schematic structural diagram of a software authorization apparatus provided in the present application;
fig. 12 is a block diagram of a software-authorized electronic device according to the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The current situation of software product production in a factory is very common, and one producer corresponds to one authorized account number, which is not beneficial to the safety of account number maintenance. If a plurality of accounts are provided at the same time, the difficulty in managing the accounts increases the maintenance cost of the authorized party, which brings a series of substantial problems to the authorization security. In order to solve the technical problems, the software authorization scheme is provided, software is authorized by setting primary and secondary accounts, and a producer creates and manages a secondary account based on a primary account distributed by an authorizer, so that the difficulty of maintaining an authorized account is reduced, and the software authorization efficiency is improved.
Fig. 1 is a flowchart of a software authorization method provided in an embodiment of the present application, and is applied to a producer. Referring to fig. 1, the software authorization method includes:
s11: and acquiring a parent account number distributed for the producer by an authorizer according to the order information of the producer and the type and the authorized quantity of the authorized software corresponding to the parent account number.
In this embodiment, the authorizer creates a parent account for different producers in advance, provides the created parent account for the producers, and adds the created parent account to the parent account according to the type and number of the software products ordered by the producers, where the parent account represents, for example, the type and number of the software products, that is, the producer obtains the parent account allocated by the authorizer to the producer according to the order information of the producer and the type and authorized number of the authorized software corresponding to the parent account. Wherein the authorized amount is the amount of authorized software purchased by the producer.
S12: and distributing a sub-account corresponding to the parent account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the parent account, so that the foundry can produce the terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account.
In this embodiment, after the production party obtains the primary account number allocated by the authorization party, a secondary account number corresponding to the primary account number, and the type and the authorization quantity of the authorization software corresponding to the secondary account number are allocated to each foundry according to a production plan based on the primary account number, so that the foundry can produce terminal equipment including the authorization software according to the type and the authorization quantity of the authorization software of the allocated secondary account number. Because a producer can correspond a plurality of factories, and a plurality of factories share an account and are difficult to ensure the safety of the account, the producer can set a plurality of sub-accounts based on the mother account, and a factory corresponds to a sub-account, and the accounts are independent from each other, thereby reducing the difficulty in account management. And the producer generates a plurality of sub-account numbers corresponding to the parent account number according to production requirements, distributes the authorization number to the corresponding sub-account numbers, and releases labor resources of the authorizer without participating in the distribution process of the sub-account numbers. It is understood that the authorization software is operated on the terminal equipment produced by the production line.
As can be seen, in the embodiment of the present application, a producer first obtains a parent account number allocated by an authorizer to the producer according to order information of the producer, and a type and an authorized number of authorized software corresponding to the parent account number; and then distributing a sub-account corresponding to the parent account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the parent account, so that the foundry can produce the terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account. According to the method and the system for authorizing the software, the software is authorized by setting the primary and secondary accounts, and the producer creates and manages the secondary accounts based on the primary accounts distributed by the authorizer, so that the difficulty in maintaining the authorized accounts is reduced, and the software authorization efficiency is improved.
Fig. 2 is a flowchart of a specific software authorization method according to an embodiment of the present application. Referring to fig. 2, the software authorization method includes:
s21: and acquiring a parent account number distributed for the producer by an authorizer according to the order information of the producer and the type and the authorized quantity of the authorized software corresponding to the parent account number.
In this embodiment, for the specific process of the step S21, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated herein.
S22: and accessing an authorization main server by logging in the allocated mother account, and allocating a sub-account corresponding to the mother account and the type and the authorization quantity of the authorization software corresponding to the sub-account for each foundry according to a production plan by using the authorization main server.
In this embodiment, the producer accesses the authorization master server by logging in the allocated parent account, and allocates a child account corresponding to the parent account and the type and authorization quantity of the authorization software corresponding to the child account to each foundry according to a production plan by using the authorization master server. After the authorized software is developed, the authorizing party stores the product number of the authorized software to the authorization main server, and when the producing party logs in the allocated mother account to access the authorization main server, the authorizing main server allocates the sub-account corresponding to the mother account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan.
S23: and the factory agent logs in the allocated sub account number to access the authorization main server so as to authorize the terminal equipment containing the authorization software through the authorization main server.
In this embodiment, during production line production, the foundry logs in the assigned sub-account to access the authorization main server, so as to authorize the terminal device including the authorization software through the authorization main server. There are many methods for authorizing the main authorization server to authorize the terminal device, such as a dongle, which is not limited in this embodiment.
Therefore, a producer accesses the total authorization server by logging in the primary account number allocated by the authorizer, and allocates the secondary account number corresponding to the primary account number, the type and the authorization quantity of the authorization software corresponding to the secondary account number to each foundry according to a production plan by using the total authorization server. On the basis, the foundry logs in the allocated sub-account to access the authorization main server, so as to authorize the terminal equipment containing the authorization software through the authorization main server. The method and the system realize the hierarchical management of the authorized account, reduce the difficulty of maintaining the authorized account and improve the software authorization efficiency.
Fig. 3 is a flowchart of another specific software authorization method provided in an embodiment of the present application. Referring to fig. 3, the software authorization method includes:
s31: and acquiring a parent account number distributed for the producer by an authorizer according to the order information of the producer and the type and the authorized quantity of the authorized software corresponding to the parent account number.
S32: and accessing an authorization main server by logging in the allocated mother account, and allocating a sub-account corresponding to the mother account and the type and the authorization quantity of the authorization software corresponding to the sub-account for each foundry according to a production plan by using the authorization main server.
In a conventional authorization system, an authorizing party adds a product code to an authorization server after completing product development, allocates an authorization account number to each producing party, and adds a corresponding product authorization number. The production side provides the authorized account number for a factory, the factory applies for authorization to the authorization server through the production line client during production, the production line client synchronizes the authorized consumption flow to the local server for summary, the local server does not participate in the authorization flow, and the method is mainly used for counting the authorized account flow of the production side so as to facilitate account checking, clearing and filing. On one hand, one producer corresponds to one authorized account, which is not beneficial to the safety of account maintenance, and on the other hand, the deployment of the authorization server is single, which is easy to cause all production line stops due to the instability of the system. Particularly, when the number and the production scale of the generation factory reach a certain magnitude, the stability of the authorization server and the system architecture can hardly meet the production requirement, and the expansion is inconvenient. In this embodiment, as to the specific processes of the step S31 and the step S32, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
S33: the factory-substitute login assigned sub-account number accesses a factory sub-server so as to authorize the terminal equipment containing the authorization software through the factory sub-server; and the factory sub-server is authorized by the authorization main server and is used for issuing an authorization certificate corresponding to the terminal equipment containing authorization software based on the request of the factory.
In this embodiment, after the product development is completed, the product number is added to the master server, and the authorization number is added to each parent account according to the order condition. And the authorizing party provides a mother account number to the producing party for accessing the total server, and the mother account number represents the authorization category and the number. And the production party is uniformly adapted to the production line client, the distribution of each sub-account number is determined according to the authorized number in the master account number and the production plan, and the sub-account numbers are provided for the factory. On the basis, the factory agent logs in the allocated sub account number to access a factory sub server, so that the terminal equipment containing the authorization software is authorized through the factory sub server. Further, the foundry logs in the allocated sub-account to access the foundry sub-server through the production line client, so that the foundry sub-server generates an authorization certificate corresponding to the terminal device by using the universal unique identification code of the terminal device containing the authorization software based on the request of the production line client.
It can be understood that the factory sub-servers must be authorized by the main server and can be used after registration, and are used for issuing an authorization certificate corresponding to the terminal device including authorization software based on the request of the factory, and have the function of an authorization license algorithm, and when the terminal device is produced, each factory sub-server does not need to transmit a license request to the authorization main server. Meanwhile, the factory sub-servers need to renew the lease available period to the authorization main server periodically, and the system can be automatically off-line and cannot be used after being off-line for one week, so that the safety and controllability of the factory sub-servers are ensured.
S34: and sending the authorization quantity corresponding to the sub-account number on the factory sub-server and the quantity of the actually issued authorization certificates to the authorization main server so that the authorization main server can be matched with the flow data stored in the authorization main server.
In this embodiment, the License recharging running water of the authorized amount and the License consuming running water of the authorized amount consumed during the production of the product in the foundry need to be collected to a parent account periodically, that is, to the authorization master server, the authorization master server checks the local License running water and the accounts of each foundry to ensure consistency, and the authorization master server checks the accounts one by one to ensure that the accounts are not tampered manually. In order to ensure the data storage security, a backup server may be introduced, and the authorization quantity corresponding to the sub-account number and the quantity of the actually issued authorization certificate on the factory sub-server are uploaded and stored in the backup server, so that the authorization main server matches the flow data on the backup server with the flow data stored by the authorization main server. That is, the producer archives the License recharging running water and the consumption running water to the backup server, and the authorized party can utilize the running water data to analyze the data.
Fig. 4 is an architecture diagram of a software authorization system provided in this embodiment, and the architecture diagram includes a main authorization server, a factory sub-server, and a production line client, where the factory sub-server has a control capability of an authorization class, the main authorization server is deployed in a public network by an authorizer, and the factory sub-server is deployed in a factory network environment. In this embodiment, the authorization master server deployed on the public network mainly includes an authorization (License) management module and a system management module, which is specifically shown in fig. 5. The License management module is mainly responsible for the functions of License authorization service such as distribution, recharging, inquiry, statistics and the like, and specifically comprises equipment model management, authorized recharging, running water inquiry, account book management and local data statistics. The License model management module can distribute License models and support adding and deleting software models, a user can achieve the purpose of adding License prototype machines by entering a section of encrypted authorization code, and can also maintain the state of the prototype machines to achieve the purpose of identifying production stopping equipment, as shown in fig. 6; under the condition that a primary account logs in, a user can add License number of a specific style to a specified factory sub-account to achieve the purpose of authorized production, and a correct recharging password is required to be input during recharging, wherein the password is not equal to a primary account login password, as shown in fig. 7; the streamline query module is mainly used for a user to know the authorized recharging condition through an streamline query interface, as shown in fig. 8; the account book management module is used for enabling a user to know account book reconciliation conditions of various factories through an account book management interface; the local data statistics module is used for enabling a user to query License consumption running data through the interface and outputting a statistics report according to each dimension, as shown in fig. 9. The system management module is mainly responsible for system configuration management, and specifically comprises account management, factory management and factory authorization. The account management module is used for configuring a system login account password and a background administrator account, and a user can modify the system login password and the consumption password through the interface; the factory management module is used by a user to query the real-time state of each factory server, and can also cancel or disable the corresponding factory sub-account, as shown in fig. 10; the factory authorization module is an authorization file which is required by a user to generate a factory sub-server to run, and the factory sub-server must be authorized by the main server and can be used after being registered.
Therefore, the embodiment of the application provides a hierarchical architecture software authorization method from two dimensions of software and hardware, and realizes hierarchical management of authorization accounts and authorization services. The hierarchical management of the authorized account avoids risks brought by account sharing, meanwhile, the account safety is effectively improved from the aspect of software, the problem of line stop caused by unstable service is solved through localized deployment, and the requirements of production efficiency and safety are met.
Referring to fig. 11, the embodiment of the present application further discloses a software authorization apparatus, which includes:
a parent account number obtaining module 11, configured to obtain a parent account number allocated by an authorizer to the producer according to the order information of the producer, and a type and an authorized number of authorized software corresponding to the parent account number;
and the sub-account generation module 12 is configured to allocate, to each foundry, a sub-account corresponding to the parent account and the type and the authorized number of the authorized software corresponding to the sub-account based on the parent account according to a production plan, so that the foundry produces the terminal device including the authorized software according to the type and the authorized number of the authorized software of the allocated sub-account.
As can be seen, in the embodiment of the present application, a producer first obtains a parent account number allocated by an authorizer to the producer according to order information of the producer, and a type and an authorized number of authorized software corresponding to the parent account number; and then distributing a sub-account corresponding to the mother account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the mother account, so that the foundry can produce terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account. According to the method and the device for authorizing the software, the software is authorized by setting the primary and secondary accounts, and the producer creates and manages the secondary accounts on the basis of the primary accounts distributed by the authorizer, so that the difficulty in maintaining the authorized accounts is reduced, and the software authorization efficiency is improved.
In some specific embodiments, the sub-account generation module 12 is specifically configured to access an authorization master server by logging in the allocated parent account, and allocate, by using the authorization master server, a sub-account corresponding to the parent account and a type and an authorization quantity of the authorization software corresponding to the sub-account for each foundry according to a production plan.
Correspondingly, the sub-account generation module 12 specifically includes:
the first access unit is used for logging in the assigned sub-account number to access the authorization main server by the agent factory so as to authorize the terminal equipment containing the authorization software through the authorization main server;
the second access unit is used for the factory sub-server to be accessed by the sub-account allocated by the factory login, so as to authorize the terminal equipment containing the authorization software through the factory sub-server; the factory sub-server is authorized by the authorization main server and used for issuing an authorization certificate corresponding to the terminal equipment containing authorization software based on the request of the factory agent.
In some specific embodiments, the software authorization apparatus further includes a matching module, configured to send the authorization quantity corresponding to the sub-account and the quantity of the authorization certificates actually issued on the factory sub-server to the total authorization server, so that the total authorization server is matched with the self-stored flow data.
Further, the embodiment of the application also provides electronic equipment. FIG. 12 is a block diagram illustrating an electronic device 20 according to an exemplary embodiment, and nothing in the figure should be taken as a limitation on the scope of use of the present application.
Fig. 12 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present disclosure. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. Wherein the memory 22 is used for storing a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the software authorization method disclosed in any of the foregoing embodiments.
In this embodiment, the power supply 23 is configured to provide a working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and a communication protocol followed by the communication interface is any communication protocol applicable to the technical solution of the present application, and is not specifically limited herein; the input/output interface 25 is configured to obtain external input data or output data to the outside, and a specific interface type thereof may be selected according to specific application requirements, which is not specifically limited herein.
In addition, the storage 22 is used as a carrier for resource storage, and may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the resources stored thereon may include an operating system 221, a computer program 222, data 223, etc., and the storage may be a transient storage or a permanent storage.
The operating system 221 is used for managing and controlling each hardware device and the computer program 222 on the electronic device 20, so as to realize the operation and processing of the mass data 223 in the memory 22 by the processor 21, and may be Windows Server, netware, unix, linux, and the like. The computer programs 222 may further include computer programs that can be used to perform other specific tasks in addition to the computer programs that can be used to perform the software authorization method performed by the electronic device 20 disclosed in any of the foregoing embodiments. Data 223 may include the type of authorization and the number of authorizations collected by electronic device 20.
Further, an embodiment of the present application further discloses a storage medium, in which a computer program is stored, and when the computer program is loaded and executed by a processor, the steps of the software authorization method disclosed in any of the foregoing embodiments are implemented.
In the present specification, the embodiments are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same or similar parts between the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Finally, it should also be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a" \8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The software authorization method, device, apparatus and storage medium provided by the present invention are described in detail above, and the principle and implementation of the present invention are explained herein by applying specific examples, and the description of the above embodiments is only used to help understanding the method and core ideas of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, the specific embodiments and the application range may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (8)
1. A software authorization method, applied to a producer, comprising:
acquiring a mother account number distributed to the producer by an authorizer according to the order information of the producer and the type and the authorized quantity of authorized software corresponding to the mother account number;
distributing a sub-account corresponding to the parent account and the type and the authorized quantity of the authorized software corresponding to the sub-account for each foundry according to a production plan based on the parent account, so that the foundry can produce terminal equipment containing the authorized software according to the type and the authorized quantity of the authorized software of the distributed sub-account;
the allocating, based on the parent account, a child account corresponding to the parent account and the type and the authorized amount of the authorized software corresponding to the child account for each production plant according to a production plan includes:
accessing an authorization main server by logging in the allocated parent account, and allocating a child account corresponding to the parent account and the type and authorization quantity of the authorization software corresponding to the child account for each foundry according to a production plan by using the authorization main server; the authorization master server is deployed in a public network by an authorization party;
the method for producing the terminal equipment containing the authorized software by the foundry according to the type and the authorized quantity of the authorized software of the assigned sub-account number comprises the following steps:
the factory-substitute login assigned sub-account number accesses a factory sub-server so as to authorize the terminal equipment containing the authorization software through the factory sub-server; the factory sub-server is authorized by the authorization main server and used for issuing an authorization certificate corresponding to the terminal equipment containing authorization software based on the request of the factory agent; the factory sub-servers are deployed in a factory network environment and are authorized and registered by the main server for use.
2. The software authorization method according to claim 1, characterized in that the factory as a substitute produces terminal devices containing authorized software according to the type and authorized amount of the authorized software of the sub-account number assigned thereto, and comprises:
and the factory agent logs in the allocated sub account number to access the authorization main server so as to authorize the terminal equipment containing the authorization software through the authorization main server.
3. The software authorization method according to claim 1, wherein the factory agent logging in the assigned sub-account to access a factory sub-server, so as to authorize the terminal device containing the authorized software through the factory sub-server, and the method comprises:
and the factory agent logs in the allocated sub-account number to access the factory sub-server through the production line client, so that the factory sub-server generates an authorization certificate corresponding to the terminal equipment by using the universal unique identification code of the terminal equipment containing the authorization software based on the request of the production line client.
4. The software authorization method according to claim 1 or 3, wherein after the foundry produces the terminal device including the authorized software according to the type and the authorized amount of the authorized software of the assigned sub-account, the method further comprises:
and sending the authorization quantity corresponding to the sub-account number on the factory sub-server and the quantity of the actually issued authorization certificates to the authorization main server so that the authorization main server can be matched with the flow data stored in the authorization main server.
5. The software authorization method according to claim 4, wherein the sending the authorization number corresponding to the sub-account number on the factory sub-server and the number of the actually issued authorization certificates to the authorization main server so that the authorization main server matches with the stored pipeline data thereof includes:
and uploading and storing the authorization number corresponding to the sub-account number and the number of the actually issued authorization certificates on the factory sub-server to a backup server so that the main authorization server can match the flow data on the backup server with the flow data stored by the main authorization server.
6. A software authorization apparatus, applied to a producer, comprising:
the system comprises a primary account number acquisition module, a primary account number acquisition module and a primary account number acquisition module, wherein the primary account number acquisition module is used for acquiring a primary account number distributed by an authorizing party for the producing party according to the order information of the producing party and the type and the authorized quantity of authorized software corresponding to the primary account number;
the sub-account generation module is used for distributing sub-accounts corresponding to the mother account and the types and the authorization quantities of the authorized software corresponding to the sub-accounts to each foundry according to a production plan based on the mother account, so that the foundry can produce terminal equipment containing the authorized software according to the types and the authorization quantities of the authorized software of the distributed sub-accounts;
the software authorization apparatus is further configured to:
accessing an authorization main server by logging in the allocated mother account, and allocating a sub-account corresponding to the mother account and the type and the authorization quantity of the authorization software corresponding to the sub-account for each foundry according to a production plan by using the authorization main server;
the factory-substitute login assigned sub-account number accesses a factory sub-server so as to authorize the terminal equipment containing the authorization software through the factory sub-server; the factory sub-server is authorized by the authorization main server and used for issuing an authorization certificate corresponding to the terminal equipment containing authorization software based on the request of the factory agent.
7. An electronic device, wherein the electronic device comprises a processor and a memory; wherein the memory is for storing a computer program that is loaded and executed by the processor to implement the software authorization method of any of claims 1 to 5.
8. A computer-readable storage medium storing computer-executable instructions which, when loaded and executed by a processor, carry out a software authorization method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110535414.4A CN113127846B (en) | 2021-05-17 | 2021-05-17 | Software authorization method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110535414.4A CN113127846B (en) | 2021-05-17 | 2021-05-17 | Software authorization method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113127846A CN113127846A (en) | 2021-07-16 |
| CN113127846B true CN113127846B (en) | 2022-12-09 |
Family
ID=76782180
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110535414.4A Active CN113127846B (en) | 2021-05-17 | 2021-05-17 | Software authorization method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113127846B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107111830A (en) * | 2014-01-13 | 2017-08-29 | 帕特丽夏·李 | The system and method for Financial Management |
| CN110224971B (en) * | 2018-03-02 | 2022-05-27 | 阿里巴巴集团控股有限公司 | Method, authorization server, system, device and storage medium for authorizing login |
| CN109936565A (en) * | 2019-01-28 | 2019-06-25 | 平安科技（深圳）有限公司 | Log in the method, apparatus, computer equipment and storage medium of multiple service clusters |
| CN111352653B (en) * | 2020-03-06 | 2023-07-14 | 中国工商银行股份有限公司 | System development method based on PaaS cloud platform server and server |
| CN111859359A (en) * | 2020-06-04 | 2020-10-30 | 青岛海信智慧家居系统股份有限公司 | Intelligent equipment authorization system, method, device, equipment and medium |
-
2021
- 2021-05-17 CN CN202110535414.4A patent/CN113127846B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN113127846A (en) | 2021-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110490305B (en) | Machine learning model processing method based on block chain network and node | |
| US7610286B1 (en) | System and method for access control and for supply chain management via a shared bill of material | |
| CN1939036B (en) | Optimized concurrent data download within a grid computing environment | |
| US20120310860A1 (en) | Cloud-Based Demand Response | |
| CN108959621A (en) | A kind of implementation method, device, equipment and the storage medium of block chain network | |
| CA2264819A1 (en) | Trusted infrastructure support systems, methods and techniques for secure electronic commerce, electronic transactions, commerce process control and automation, distributed computing, and rights management | |
| CN109683936A (en) | Gray scale dissemination method and device, storage medium and electronic equipment | |
| CN102821160B (en) | Towards the system of loose cloud node multi-levels data protection and method under a kind of system for cloud computing environment | |
| CN110717832A (en) | Clean energy trading method, system, device and storage medium based on block chain | |
| CN102821162A (en) | System for novel service platform of loose cloud nodes under cloud computing network environment | |
| CN103440150A (en) | Method capable of assembling software being downloaded from remote component warehouse as required in field | |
| CN102801812A (en) | Novel cloud service component management system and method in loose network environment | |
| WO2013130222A2 (en) | Identity data management system for high volume production of product-specific identity data | |
| CN109885424A (en) | A kind of data back up method, device and computer equipment | |
| CN113706312A (en) | Photovoltaic electricity transaction method and device based on block chain | |
| CN103440166A (en) | System capable of assembling software being downloaded from remote component warehouse as required in field | |
| CN113127846B (en) | Software authorization method, device, equipment and storage medium | |
| Cameron et al. | Advances in ATLAS@ Home towards a major ATLAS computing resource | |
| CN111861117A (en) | Musical instrument evaluation data sharing method and system based on alliance chain | |
| CN110110510A (en) | A kind of engineering calculation model management method based on cloud computing | |
| CN105636031A (en) | Packet communication management method, apparatus and system | |
| CN111526180B (en) | Data sharing method and device | |
| KR20080083723A (en) | System and method for on-line production cooperation | |
| Burruss et al. | Remote computing using the national fusion grid | |
| CN114282210A (en) | Sandbox automatic construction method and system, computer equipment and readable storage medium |
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 |