WO2015180272A1 - Software licensing method and system - Google Patents

Abstract

Disclosed are a software licensing method and system, the method comprising: receiving a software licensing request from a user terminal; acquiring a license agreement in response to the software licensing request, and transmitting to the user terminal; receiving a license agreement modification request from the user terminal; determining a modified agreement according to the modification request, and transmitting to the user terminal; receiving a modification agreement acceptance message from the user terminal, and utilizing the modified agreement as a final license agreement; and transmitting the license information to the user terminal. In response to the license agreement modification request from the user terminal, the implemented method and system determine a modified agreement according to the modification request, and after the user terminal accepts the modified agreement, use the modified agreement as the final license agreement for software licensing, allowing the same software to be licensed to different user terminals via different license agreements, thus improving the software licensing range, and reducing development and service costs of the software.

Description

 Software licensing method and system

 The present invention relates to the field of computer technologies, and in particular, to a software licensing method and system. Background technique

 With current software licensing technology, users typically install applications and then register over the network. When registering via the network, you must accept the license agreement before you can complete the registration.

 However, one of the above software licensing technologies corresponds to a license agreement and can only be licensed to the client that matches the license agreement, which will reduce the software license range and increase the software development cost. Summary of the invention

 Based on this, it is necessary to provide a software licensing method and system for the above software licensing technology, which will reduce the software license range and increase the software development cost.

 A software licensing method that includes the following steps:

 Receiving a software license request from the client;

 Retrieving a license agreement in response to the software license request, and transmitting to the client;

 Receiving a modification request of the user terminal to the license agreement;

 Determining a modification protocol according to the modification request, and sending the message to the client;

 Receiving an acceptance instruction of the modification protocol by the client, and using the modification protocol as a final license agreement;

 Sending license information to the client.

 A software licensing system, including:

 a first receiving module, configured to receive a software license request of the user end;

 a protocol sending module, configured to obtain a license agreement in response to the software license request, and send the license agreement to the user end;

a second receiving module, configured to determine a modification protocol according to the modification request, and send the modification protocol to the UE; a protocol modification module, configured to receive an acceptance instruction of the modification protocol by the client, and use the modification protocol as a final license agreement;

 The third receiving module is configured to send the license information to the client.

 The software license method and system, in response to a request for modification of a license agreement by a client, determine a modification protocol according to the modification request, and use the modified protocol as a final license agreement after receiving an acceptance instruction of the modification protocol by the user end. Software licenses allow the same software to be licensed to different clients under different license agreements, thereby increasing the software license and reducing software development and service costs.

 A software licensing method that includes the following steps:

 Send a software license request to the license side;

 Receiving a license agreement of the license end;

 If the license agreement does not satisfy the preset agreement acceptance condition, obtaining a modification request for the license agreement, and sending the request to the license end;

 Receiving a modification protocol of the license end;

 And if the modification protocol satisfies the preset protocol acceptance condition, sending an acceptance instruction to the modification protocol to the permission end;

 Receiving license information of the license side.

 A software licensing system, including:

 a first sending module, configured to send a software license request to the license end;

 a license agreement receiving module, configured to receive a license agreement of the license end;

 a second sending module, configured to acquire a modification request for the license agreement when the license agreement does not satisfy a preset protocol acceptance condition, and send the request to the permission end;

 Modifying a protocol receiving module, configured to receive a modification protocol of the permission end;

 a third sending module, configured to send an accepting instruction to the modifying protocol to the permission end when the modifying protocol satisfies the preset protocol accepting condition;

 The license information receiving module is configured to receive the license information of the license end.

The software license method and system, when the license agreement does not satisfy a preset protocol acceptance condition, send a modification request to the license agreement to the license end, and when the license modification protocol satisfies the preset protocol acceptance condition Send an accept command to the license side, receive the license information of the license side, and implement the license. The software license can be obtained, and the license-side software license can be obtained by a modification agreement different from the original license agreement, which can expand the software selection range and reduce the license cost. DRAWINGS

 1 is a schematic flowchart of a first embodiment of a software licensing method according to the present invention;

 2 is a schematic flowchart of a second embodiment of a software licensing method according to the present invention;

 3 is a schematic structural diagram of a first embodiment of a software licensing system according to the present invention;

 4 is a schematic structural diagram of a second embodiment of a software licensing system according to the present invention;

 FIG. 5 is a schematic flowchart diagram of a third embodiment of a software licensing method according to the present invention; FIG.

 6 is a schematic flowchart of a fourth embodiment of a software licensing method according to the present invention;

 7 is a schematic structural diagram of a third embodiment of a software licensing method according to the present invention;

 8 is a schematic structural diagram of a fourth embodiment of a software licensing method according to the present invention;

 FIG. 9 is a schematic structural diagram of a first implementation environment of a software license method according to an embodiment of the present invention; FIG. 10 is a schematic structural diagram of a second implementation environment of a software license method according to an embodiment of the present invention; A schematic diagram of the structure of a third implementation environment of the method; FIG. 12 is a block diagram of a computer system capable of implementing an embodiment of the present invention. detailed description

 The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

 The components and components of the present invention may be present in a single form or in multiple forms, and the invention is not limited thereto, unless the context clearly dictates otherwise. The steps in the present invention are arranged by reference numerals, but are not intended to limit the order of steps. The relative order of the steps may be adjusted unless the order of the steps is explicitly stated or the execution of a step requires other steps as a basis. It will be understood that the term "and/or" as used herein relates to and encompasses any and all possible combinations of one or more of the associated listed items.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart diagram of a first embodiment of a software licensing method according to the present invention. The software licensing method of this embodiment is preferably an operation flow on the license side, and includes the following steps:

 Step S101: Receive a software license request of the client.

 Step S102: Acquire a license agreement in response to the software license request, and send the license agreement to the client. Step S103: Receive a modification request of the user terminal for the license agreement.

 Step S104: Determine a modification protocol according to the modification request, and send the modification protocol to the UE.

 Step S105: Receive an acceptance instruction of the modification protocol by the client, and use the modification protocol as a final license agreement.

 Step S106: Send permission information to the client.

 The software license method according to the embodiment, in response to the modification request of the user terminal to the license agreement, determines the modification protocol according to the modification request, and after receiving the acceptance instruction of the modification protocol by the user end, the modification protocol is The final license agreement for software license allows the same software to be licensed to different clients under different license agreements, thereby increasing the software license range and reducing software development and service costs.

 The user terminal is preferably a running terminal of the software to be licensed, such as a desktop computer, a notebook, a personal digital assistant, a smart phone, a tablet computer, a portable media player, a large-sized wall-mounted display device, etc., for step S101. It can also be a server for deploying the operating environment of the software to be licensed.

 Preferably, the permission request may be an application for deploying an operating environment of the software to be licensed, may include a software identifier of the software to be licensed, and may further include an identifier (host name or network address) of the user end.

 Further, the user of the user terminal is preferably a main body, a government department, a school, an individual, and the like that can construct a cloud computing environment. The cloud computing environment includes a public cloud mode, a private cloud mode, a hybrid cloud mode, a community cloud mode, and the like.

 In one embodiment, before the step of receiving the software license request of the client, the method further includes the following steps:

 Push the service information of the software to be licensed to the target network.

 In this embodiment, the service information of the software to be licensed is pushed to the target network, so that the user can query the service information of each software and perform software selection.

Preferably, the service information may include function information of the software to be licensed or a service that can be provided. Place The license software may be software that can provide cloud services, and the service information may be cloud service information.

 Further, service information of the software to be licensed may also be displayed on the target network in the form of a service directory.

 In other embodiments, the service information of the software to be licensed may also be pushed to the cloud server of the client or the license end.

 For step S102, the pre-existing license agreement of the corresponding software may be invoked as a license agreement corresponding to the software license request according to the software identification or the correspondence between the license request and the software to be licensed in the software license request.

 For step S103, the modification request may include a modification proposal or a modified protocol content of the license agreement.

 For the step S104, the modification protocol may be generated in real time according to the modification request, and the pre-stored other software protocol different from the license agreement may be invoked as the modification protocol according to the modification request.

 Preferably, after receiving the modification request, determining whether the modification request satisfies a preset protocol modification condition, if yes, determining a modification protocol according to the modification request, and sending the modification protocol to the user end.

 Further, if the modification request does not satisfy the preset protocol modification condition, the user may send a prompt for changing the modification request.

 In one embodiment, the step of determining a modification protocol based on the modification request and transmitting to the client includes the following steps:

 Extracting, by the modification request, the modification data of the license agreement by the user end;

 Determining whether the requested data is within a preset protocol modification range;

 If yes, the modification protocol is determined according to the modification data, and is sent to the client; if not, the prompt for changing the modification request is sent to the client.

 In this embodiment, the modification request may be prompted by the user end when the modification request of the user end does not satisfy the preset protocol modification range.

Preferably, the corresponding protocol data of the license agreement may be directly replaced by the modified data, and a modification protocol may be generated, or the protocol data corresponding to the modified data may be retrieved from the pre-stored protocol database to replace the correspondence of the license agreement. Protocol data, generate modification protocol, and also retrieve from the modified protocol library The modification protocol corresponding to the modified data.

 For step S105, the accepting instruction is used to identify that the modified protocol meets the requirements of the client. Preferably, the modification protocol is used as a final license agreement, and the final license agreement is a license agreement of the software to be licensed corresponding to the client. The licensed software can store different final license agreements for different clients.

 In an embodiment, before receiving the step of the client accepting the modification protocol, the method further includes the following steps:

 Receiving a modification request of the modification protocol by the client.

 Determines whether the number of times the request for modification is received exceeds the requested threshold.

 If not, the modification protocol is determined according to the modification request, and is sent to the client.

 If yes, a license termination instruction is sent to the client.

 In this embodiment, after receiving the modification request of the modification protocol by the UE, the modification protocol may be modified again.

 For step S106, the license information is preferably a license credential for the licensed client to use the corresponding software.

 Further, if the license information is associated with the final license agreement, different license information may be generated in advance according to different modification protocols in the modified protocol library, or new license information may be generated in real time according to the final license agreement.

 In one embodiment, the step of transmitting the license information to the client may further comprise the step of: storing the modification protocol as a final license agreement to license the corresponding software to the client.

 And determining, according to the final protocol, usage information of the client by using the corresponding software, and generating the license information.

 The generated license information is transmitted to the client.

 Preferably, the corresponding software is software requested by the software license request. The usage information may include usage information such as charging criteria of the software at the user end, number of user registrations, number of online users, number of concurrent users, and the like. The license information may include the user information and credential information using the software.

Further, the corresponding information in the installation package of the corresponding software may be modified according to the final license agreement. In another embodiment, after the license information is sent to the client, the integrity of the final license agreement, the consistency with the final license agreement stored by the client, and the security and confidentiality of the final license agreement are ensured through a security management mechanism. Finally, the license agreement is filed. The security management mechanism can support third-party information security and confidentiality authentication services, such as CA authentication, and also supports private security protocols and keys established between the license and the client.

 Please refer to FIG. 2. FIG. 2 is a schematic flowchart diagram of a second embodiment of the software licensing method of the present invention. The software licensing method of the present embodiment differs from the first embodiment in that: after acquiring the license information in which the modification protocol is a license agreement and transmitting the information to the client, the following steps are further included:

 Step S201: Send a deployment instruction of the software running environment to the client, where the deployment instruction includes configuration information of an operating environment of the software.

 Step S202, receiving a deployment completion instruction of the client, and permitting the client to download and install the corresponding software.

 In this implementation manner, after the user end completes the deployment of the software permission environment, the user terminal is allowed to download and install the corresponding software, so that the user terminal can monitor and manage the software application.

 For the step S201, the operating environment of the software may include the software environment and the hardware environment. The software environment mainly includes an operating system, such as windows, Linux, etc., and may also include some other software, such as office, and may also include a third-party runtime library. , such as DotNet, DirectX, etc. The hardware environment mainly includes server configuration, such as CPU, memory, graphics card, hard disk, and so on.

 Preferably, the configuration information may include an instruction function write for implementing a software service, information for driving an application to run, address information of a client, and the like.

 Further, the configuration information may include configuration information of a virtual machine in a cloud computing environment. It is convenient for software to provide cloud services for users in a cloud computing environment.

 For step S202, the downloading program of the software may be started by the software download manager, and the user is permitted to download and install the corresponding software.

 In an embodiment, after the step of sending the deployment instruction of the software running environment to the client, the method further includes the following steps:

The software charging program for the client is started by using the final license agreement as a charging protocol. In this embodiment, the number of users of the software at the user end and the duration of use are recorded, and the user terminal is charged according to a modification protocol as a license agreement.

 Please refer to FIG. 3. FIG. 3 is a schematic structural diagram of a first embodiment of the software licensing system of the present invention. The software license system of the present embodiment is preferably an operating system on the license side, including a first receiving module 110, a protocol sending module 120, a second receiving module 130, a protocol modifying module 140, a third receiving module 150, and License module 160, wherein:

 The first receiving module 110 is configured to receive a software license request of the client.

 The protocol sending module 120 is configured to obtain a license agreement in response to the software license request, and send the license agreement to the user.

 The second receiving module 130 is configured to receive a modification request of the user terminal to the license agreement.

 The protocol modification module 140 is configured to determine a modification protocol according to the modification request, and send the protocol to the client.

 The third receiving module 150 is configured to receive an accepting instruction of the modification protocol by the user end, and use the modified protocol as a final license agreement.

 The license module 160 is configured to send the license information to the client.

 The software license system according to the embodiment, in response to the modification request of the user terminal to the license agreement, determines the modification protocol according to the modification request, and after receiving the acceptance instruction of the modification protocol by the user end, the modification protocol is The final license agreement for software license allows the same software to be licensed to different clients under different license agreements, thereby increasing the software license range and reducing software development and service costs.

 Wherein, for the first receiving module 110, the user terminal is preferably a running terminal of the software to be licensed, such as a desktop computer, a notebook, a personal digital assistant, a smart phone, a tablet computer, a portable media player, a large-sized wall display. A device, etc., may also be a server for deploying an operating environment of the software to be licensed.

 Preferably, the permission request may be an application for deploying an operating environment of the software to be licensed, may include a software identifier of the software to be licensed, and may further include an identifier (host name or network address) of the user end.

Further, the user of the user terminal is preferably a main body, a government department, a school, an individual, and the like that can construct a cloud computing environment. The cloud computing environment includes a public cloud mode, a private cloud mode, a hybrid cloud mode, a community cloud mode, and the like. In one embodiment, a push module is further included for pushing service information of the software to be licensed to the target network.

 In this embodiment, the service information of the software to be licensed is pushed to the target network, so that the user can query the service information of each software and perform software selection.

 Preferably, the service information may include function information of the software to be licensed or a service that can be provided. The software to be licensed may be software capable of providing a cloud service, and the service information may be cloud service information.

 Further, service information of the software to be licensed may also be displayed on the target network in the form of a service directory.

 In other embodiments, the service information of the software to be licensed may also be pushed to the cloud server of the client or the license end.

 For the protocol sending module 120, the pre-stored license agreement corresponding to the software may be invoked as a license agreement corresponding to the software license request according to the software identifier in the software license request or the correspondence between the license request and the license software.

 For the second receiving module 130, the modification request may include a modification suggestion or a modified protocol content of the license agreement.

 For the protocol modification module 140, the modification protocol may be generated in real time according to the modification request, and the pre-stored other software protocol different from the license agreement may be invoked as a modification protocol according to the modification request.

 Preferably, after receiving the modification request, determining whether the modification request satisfies a preset protocol modification condition, if yes, determining a modification protocol according to the modification request, and sending the modification protocol to the user end.

 Further, if the modification request does not satisfy the preset protocol modification condition, the user may send a prompt for changing the modification request.

 In one embodiment, the protocol modification module 140 can be used to:

 Extracting, by the modification request, the modification data of the license agreement by the user end;

 Determining whether the requested data is within a preset protocol modification range;

If yes, the modification protocol is determined according to the modification data, and is sent to the client; if not, the prompt for changing the modification request is sent to the client. In this embodiment, the modification request may be prompted by the user end when the modification request of the user end does not satisfy the preset protocol modification range.

 Preferably, the corresponding protocol data of the license agreement may be directly replaced by the modified data, and a modification protocol may be generated, or the protocol data corresponding to the modified data may be retrieved from the pre-stored protocol database to replace the correspondence of the license agreement. The protocol data, the modification protocol is generated, and the modification protocol corresponding to the modification data may also be retrieved from the modification protocol library.

 For the third receiving module 150, the accepting instruction is used to identify that the modified protocol meets the requirements of the client.

 Preferably, the modification protocol is used as a final license agreement, and the final license agreement is a license agreement of the software to be licensed corresponding to the client. The licensed software can store different final license agreements for different clients.

 In an embodiment, the method further includes a modification determining module, configured to:

 Receiving a modification request of the modification protocol by the client.

 Determines whether the number of times the request for modification is received exceeds the requested threshold.

 If not, the modification protocol is determined according to the modification request, and is sent to the client.

 If yes, a license termination instruction is sent to the client.

 In this embodiment, after receiving the modification request of the modification protocol by the UE, the modification protocol may be modified again.

 For the license module 160, the license information is preferably a license credential for the licensed client to use the corresponding software.

 Further, if the license information is associated with the final license agreement, different license information may be generated in advance according to different modification protocols in the modified protocol library, or new license information may be generated in real time according to the final license agreement.

 In one embodiment, the license module 160 can also be used to:

 The modification protocol is stored as a final license agreement to license the corresponding software to the client.

 And determining, according to the final protocol, usage information of the client by using the corresponding software, and generating the license information.

The generated license information is transmitted to the client. Preferably, the corresponding software is software requested by the software license request. The usage information may include usage information of software, such as charging criteria, number of user registrations, number of online users, number of concurrent users, and the like. The license information may include the user information and credential information using the software.

 Further, the corresponding information in the installation package of the corresponding software may be modified according to the final license agreement. In another embodiment, after the license information is sent to the client, the integrity of the final license agreement, the consistency with the final license agreement stored by the client, and the security and confidentiality of the final license agreement are ensured through a security management mechanism. Finally, the license agreement is filed. The security management mechanism supports third-party information security and confidentiality authentication services, such as CA authentication, and also supports private security protocols and keys established between the license and the client.

 Please refer to FIG. 4. FIG. 4 is a schematic structural diagram of a second embodiment of the software licensing system of the present invention. The software licensing system of the present embodiment differs from the first embodiment in that it may further include a software delivery module 170, which may be used to:

 And transmitting, to the client, a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software.

 Receiving a deployment completion instruction of the client, and permitting the client to download and install the corresponding software. In this implementation manner, after the user end completes the deployment of the software permission environment, the user terminal is allowed to download and install the corresponding software, so that the user terminal can monitor and manage the software application.

 For the software delivery module 170, the operating environment of the software may include both a software environment and a hardware environment. The software environment mainly includes an operating system, such as windows, Linux, etc., and may also include some other software, such as an office, and may also include a third party. Run the library, such as DotNet, DirectX, etc. The hardware environment mainly includes server configuration, such as CPU, memory, graphics card, hard disk, and so on.

 Preferably, the configuration information may include an instruction function write for implementing a software service, information for driving an application to run, address information of a client, and the like.

 Further, the configuration information may include configuration information of a virtual machine in a cloud computing environment. It is convenient for software to provide cloud services for users in a cloud computing environment.

In one embodiment, the software delivery module 170 can initiate a download process of the software through the software download manager, permitting the client to download and install the corresponding software. In an embodiment, the charging module may be further configured to start a software charging procedure for the client by using the modification protocol as a charging protocol.

 In this embodiment, the number of users of the software at the user end and the duration of use are recorded, and the user terminal is charged according to a modification protocol as a license agreement.

 Please refer to FIG. 5. FIG. 5 is a schematic flowchart diagram of a third embodiment of the software licensing method of the present invention. The software licensing method of the present embodiment is preferably an operation flow on the user side, and may include the following steps:

 Step S501, sending a software license request to the license end.

 Step S502: Receive a license agreement of the license end.

 Step S503: If the license agreement does not satisfy the preset protocol acceptance condition, obtain a modification request for the license agreement, and send the request to the permission end.

 Step S504, receiving a modification protocol of the permission end.

 Step S505: If the modification protocol satisfies the preset protocol acceptance condition, send an acceptance instruction to the modification protocol to the permission end.

 Step S506, receiving license information of the license end.

 The software license method of the present embodiment sends a modification request for the license agreement to the license end when the license agreement does not satisfy the preset protocol acceptance condition, and the modification protocol of the license end satisfies the preset protocol acceptance condition. When the license is sent to the license, the license information is received, the license-side license is implemented, and the license is granted to the software by a modification protocol different from the initial license agreement, the software selection range can be extended, and the license cost can be reduced.

 Wherein, in step S501, the license end may be a management server that manages the software to be licensed or a providing server that generates the software to be licensed. Such as desktops, notebooks, personal digital assistants, tablets, and more.

 In one embodiment, prior to the step of transmitting a software license request to the license, the method further includes the steps of:

 The software for satisfying the preset requirement information is found by the target network, where the service information of each software is stored in the target network.

 If found, a software license request is sent to the license side of the found software.

In this embodiment, the software that satisfies the user's needs can be quickly found through the network, and the permission request is made. Preferably, the preset requirement information may include service information that can be provided by software required by the user. Further, the service catalog displayed by the target network may also be used to find software that meets the preset requirement information.

 In other embodiments, the software that meets the preset requirement information may be found by receiving the service information of the pushed software to be licensed or the cloud server of the license end.

 For step S503, the modification request may be generated in real time, and the pre-stored modification request may be directly retrieved. In an embodiment, if the license agreement does not satisfy the preset protocol acceptance condition, obtaining a modification request for the license agreement, and sending the request to the permission end includes the following steps:

 Get the trigger event for the protocol modification button.

 If the trigger event is obtained, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and the protocol modification box is displayed.

 Receiving the modification data input to the protocol modification box, and generating a modification request including the modification data. Sending the generated modification request to the permission side.

 In this embodiment, by receiving the input modification data and generating a modification request, the license agreement may be modified in real time to transmit the modification suggestion of the user end to the license end.

 The trigger event for the protocol modification button may preferably be a cursor or a touch point move-in event of the area where the protocol modification button is located.

 Preferably, after receiving the license agreement, the license agreement and the protocol accept button, the protocol reject button, and the protocol modification button corresponding to the license agreement may be displayed on the user end, and a trigger event for the protocol accept button is obtained. Then, an acceptance instruction for the license agreement is sent, and when a trigger event for the protocol rejection button is obtained, a rejection instruction for the license agreement is sent.

 Preferably, the modification data is triggered by a user input.

 In other embodiments, determining that the license agreement does not satisfy a preset protocol acceptance condition may display a protocol modification option, obtain a trigger event for the protocol modification option, and generate a tamper request including the protocol modification option.

In other implementations, the triggering event of the license agreement may also be obtained, and if the triggering event is obtained, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, the protocol modification option is displayed, and the protocol modification option is obtained. Trigger event, generating a modification request including the protocol modification option. The protocol modification option may be a modification proposal for the license agreement, or may be a data content after modifying the corresponding protocol content of the license agreement.

 In another embodiment, if the license agreement does not satisfy the preset protocol acceptance condition, obtaining a modification request for the license agreement, and sending the request to the permission end includes the following steps:

 Extracting protocol data in the license agreement, and comparing whether the extracted protocol data matches the preset protocol data.

 If there is no match, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and a modification request for the license agreement is generated according to the comparison result.

 Sending the generated modification request to the permission side. Quickly generate a modification request.

 For the step S504, before receiving the modification protocol of the permission end, receiving the prompt of the change modification request of the permission end, receiving the prompt, displaying the request modification box, receiving the modification data inputting the request modification frame, and generating the modification including the modification A request for modification of data is sent to the license side.

 Further, after receiving the prompt, the permission of the license agreement may be sent to the permission end.

 For step S505, an accepting instruction input by the user may be received, and an accepting instruction may also be generated by comparing the modified protocol and the preset protocol accepting condition.

 Preferably, after the accepting instruction is sent, the modified protocol is stored as a license agreement.

 In one embodiment, if the modification protocol satisfies the preset protocol acceptance condition, the step of transmitting an acceptance instruction to the modification protocol to the permission terminal includes the following steps:

 Extracting protocol data in the modification protocol, and comparing whether the extracted protocol data matches the preset protocol data.

 If they match, it is determined that the license agreement satisfies a preset agreement acceptance condition, and an accept instruction for the modification protocol is sent to the license end.

 If there is no match, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and a modification request for the modification protocol is generated according to the comparison result.

Sending the generated modification request to the permission side. For step S506, the license information of the license end is preferably the license information of the final license agreement with the accepted modification protocol, and upon receiving the license information, it may further verify whether the license information is the license agreement with the accepted modification protocol. If not, an alert reminder is sent to the license end to obtain license information with the modified protocol as a license agreement.

 In one embodiment, after receiving the license information of the license side, the integrity of the accepted modification protocol, the consistency with the final license agreement stored by the license side, and the security and confidentiality of the accepted modification protocol may be ensured through the security management mechanism. Sex, finally archive the license agreement. The security management mechanism can support third-party information security and confidentiality authentication services, such as CA authentication, and also supports private security protocols and keys established between the license and the client.

 Please refer to FIG. 6. FIG. 6 is a schematic flowchart diagram of a fourth embodiment of the software licensing method of the present invention. The software license method of this embodiment differs from the third embodiment in that: after receiving the license information of the license side, the method further includes the following steps:

 Step S601: Receive a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software.

 Step S602: Perform deployment of a software running environment on the user end according to the configuration information. Step S603: If the deployment of the software running environment is completed, send a deployment completion instruction to the permission end, and download and install the corresponding software.

 In this embodiment, after the user side deploys the software permission environment, the deployment completion instruction is sent to the permission end, and the corresponding software is downloaded and installed, so that the user terminal can monitor and manage the software application.

 The operating environment of the software may include the software environment and the hardware environment in step S601. The software environment mainly includes an operating system, such as windows, Linux, etc., and may also include some other software, such as office, and may also include a third-party runtime library. , such as DotNet, DirectX, etc. The hardware environment mainly includes server configuration, such as CPU, memory, graphics card, hard disk, and so on.

 Preferably, the configuration information may include an instruction function write for implementing a software service, information for driving an application to run, address information of a client, and the like.

 Further, the configuration information may include configuration information of a virtual machine in a cloud computing environment. It is convenient for software to provide cloud services for users in a cloud computing environment.

For step S602, the software environment and the hardware environment may be deployed on the user end according to the configuration information. In an embodiment, when the configuration information includes the configuration information of the virtual machine in the cloud computing environment, the step of deploying the software running environment on the user end according to the configuration information includes the following steps:

 According to the configuration information, virtual machine deployment in a cloud computing environment is performed on the user end.

 In this embodiment, the virtual machine deployment can be performed according to the standardized configuration technology of the virtual machine in the cloud computing environment. In another embodiment, after the deployment completion instruction is sent to the permission end, and the step of installing the corresponding software is downloaded, the following steps are further included:

 Obtaining running status information of the software on the user end.

 If the running status information satisfies the preset normal operating condition, the accepted modification protocol is a charging protocol, and the software charging program for the user end is started at the user end.

 If the running status information does not satisfy the preset normal operating condition, an abnormal alarm is sent.

 In this embodiment, the software can be monitored and managed on the user end.

 Preferably, when the license agreement is terminated, the license side may also be notified to terminate the license to the software and uninstall the virtual machine at the user end.

 Further, the modification protocol may be a charging protocol, and the software charging program is started at the user end.

 Please refer to FIG. 7. FIG. 7 is a schematic structural diagram of a third embodiment of the software licensing system of the present invention. The software license system of the present embodiment is preferably an operating system on the user side, and may include a first sending module 210, a license agreement receiving module 220, a second sending module 230, a modifying protocol receiving module 240, and a third sending. Module 250 and license information receiving module 260, wherein:

 The first sending module 210 is configured to send a software license request to the license end.

 The license agreement receiving module 220 is configured to receive the license agreement of the license end.

 The second sending module 230 is configured to obtain a modification request for the license agreement when the license agreement does not satisfy the preset protocol acceptance condition, and send the request to the license end.

 The modification protocol receiving module 240 is configured to receive the modification protocol of the permission end.

 The third sending module 250 is configured to send an accepting instruction to the modifying protocol to the permission end when the modifying protocol satisfies the preset protocol accepting condition.

The license information receiving module 260 is configured to receive the license information of the license end. The software license system of the present embodiment sends a modification request for the license agreement to the license end when the license agreement does not satisfy the preset protocol acceptance condition, and the modification protocol of the license end satisfies the preset agreement acceptance condition. When the license is sent to the license, the license information is received, the license-side license is implemented, and the license is granted to the software by a modification protocol different from the initial license agreement, the software selection range can be extended, and the license cost can be reduced.

 For the first sending module 210, the permission end may be a management server that manages software to be licensed or a providing server that generates software to be licensed. Such as desktops, notebooks, personal digital assistants, tablets, and more.

 In an embodiment, a query module is further included for:

 The software for satisfying the preset requirement information is found by the target network, where the service information of each software is stored in the target network.

 If found, a software license request is sent to the license side of the found software.

 In this embodiment, the software that satisfies the user's needs can be quickly found through the network, and the permission request is made. Preferably, the preset requirement information may include service information that can be provided by software required by the user. Further, the service catalog displayed by the target network may also be used to find software that meets the preset demand information.

 In other embodiments, the software that meets the preset requirement information may be found by receiving the service information of the pushed software to be licensed or the cloud server of the license end.

 For the license agreement receiving module 220, the license is preferably a license agreement for software that is licensed with the license request.

 For the second sending module 230, the modification request may be generated in real time, and the pre-stored modification request may also be directly retrieved.

 In one embodiment, the second sending module 230 can be used to:

 Get the trigger event for the protocol modification button.

 If the trigger event is obtained, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and the protocol modification box is displayed.

Receiving the modification data input to the protocol modification box, and generating a modification request including the modification data. Sending the generated modification request to the permission side. In this embodiment, by receiving the input modification data and generating a modification request, the license agreement may be modified in real time to transmit the modification suggestion of the user end to the license end.

 The trigger event for the protocol modification button may preferably be a cursor or a touch point move-in event of the area where the protocol modification button is located.

 Preferably, after receiving the license agreement, the license agreement and the protocol accept button, the protocol reject button, and the protocol modification button corresponding to the license agreement may be displayed on the user end, and a trigger event for the protocol accept button is obtained. Then, an acceptance instruction for the license agreement is sent, and when a trigger event for the protocol rejection button is obtained, a rejection instruction for the license agreement is sent.

 Preferably, the modification data is triggered by a user input.

 In other embodiments, determining that the license agreement does not satisfy a preset protocol acceptance condition may display a protocol modification option, obtain a trigger event for the protocol modification option, and generate a tamper request including the protocol modification option.

 In other implementations, the triggering event of the license agreement may also be obtained, and if the triggering event is obtained, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, the protocol modification option is displayed, and the protocol modification option is obtained. Trigger event, generating a modification request including the protocol modification option.

 The protocol modification option may be a modification proposal for the license agreement, or may be a data content after modifying the content of the corresponding protocol of the license agreement.

 In another embodiment, the second sending module 230 can be used to:

 Extracting protocol data in the license agreement, and comparing whether the extracted protocol data matches the preset protocol data.

 If there is no match, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and a modification request for the license agreement is generated according to the comparison result.

 Sending the generated modification request to the permission side. Quickly generate a modification request.

For modifying the protocol receiving module 240, before receiving the modification protocol of the permission end, receiving the prompt of the change modification request of the permission end, receiving the prompt, displaying the request modification box, receiving the modification data inputting the request modification frame, and generating The modification request of the modification data is sent to the permission end. Further, after receiving the prompt, the license may be sent an instruction to reject the license agreement.

 For the third sending module 250, the accepting instruction input by the user may be received, and the accepting instruction may also be generated by comparing the modification protocol and the preset protocol accepting condition.

 Preferably, after the accepting instruction is sent, the modified protocol is stored as a license agreement.

 In one embodiment, the third transmitting module 250 can be used to:

 Extracting protocol data in the modification protocol, and comparing whether the extracted protocol data matches the preset protocol data.

 If they match, it is determined that the license agreement satisfies a preset agreement acceptance condition, and an accept instruction for the modification protocol is sent to the license end.

 If there is no match, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and a modification request for the modification protocol is generated according to the comparison result.

 Sending the generated modification request to the permission side.

 For the license information receiving module 260, the license information of the license end is preferably the license information of the final license agreement with the accepted modification protocol, and upon receiving the license information, it may be further verified whether the license information is permitted by the accepted modification protocol. protocol. If not, an alert reminder is sent to the license end to obtain license information with the modified protocol as a license agreement.

 In one embodiment, after receiving the license information of the license side, the integrity of the accepted modification protocol, the consistency with the final license agreement stored by the license side, and the security and confidentiality of the accepted modification protocol may be ensured through the security management mechanism. Sex, finally archive the license agreement. The security management mechanism can support third-party information security and confidentiality authentication services, such as CA authentication, and also supports private security protocols and keys established between the license and the client.

 Please refer to FIG. 8. FIG. 8 is a schematic structural diagram of a fourth embodiment of the software licensing system of the present invention. The software licensing system of this embodiment differs from the third embodiment in that: a deployment module 270 is further included for:

 Receiving a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software.

According to the configuration information, deployment of a software running environment is performed at the user end. If the deployment of the software running environment is completed, sending a deployment completion instruction to the permission end, and downloading and installing the corresponding software.

 In this embodiment, after the user side deploys the software permission environment, the deployment completion instruction is sent to the permission end, and the corresponding software is downloaded and installed, so that the user terminal can monitor and manage the software application.

 For the deployment module 270, the operating environment of the software may include both a software environment and a hardware environment. The software environment mainly includes an operating system, such as windows, Linux, etc., and may also include some other software, such as office, and may also include a third-party operation. Libraries, such as DotNet, DirectX, etc. The hardware environment mainly includes server configuration, such as CPU, memory, graphics card, hard disk, and so on.

 Preferably, the configuration information may include an instruction function write for implementing a software service, information for driving an application to run, address information of a client, and the like.

 Further, the configuration information may include configuration information of a virtual machine in a cloud computing environment. It is convenient for software to provide cloud services for users in a cloud computing environment.

 The deployment module 270 can also deploy the software environment and the hardware environment on the user side according to the configuration information. In one embodiment, the deployment module 270 is further configured to perform virtual machine deployment in a cloud computing environment at the user end according to the configuration information.

 In this embodiment, the virtual machine deployment can be performed according to the standardized configuration technology of the virtual machine in the cloud computing environment. In another embodiment, a management module may also be included for:

 Obtaining running status information of the software on the user end.

 If the running status information satisfies the preset normal operating condition, the accepted modification protocol is a charging protocol, and the software charging program for the user end is started at the user end.

 If the running status information does not satisfy the preset normal operating condition, an abnormal alarm is sent.

 In this embodiment, the software can be monitored and managed on the user end.

 Preferably, when the license agreement is terminated, the license side may also be notified to terminate the license to the software and uninstall the virtual machine at the user end.

 Further, the modification protocol may be a charging protocol, and the software charging program is started at the user end.

Referring to FIG. 9, FIG. 9 is a first structural diagram of an implementation environment of a software licensing method according to an embodiment of the present invention. The implementation environment shown in FIG. 9 is used to implement the software licensing method according to any embodiment or embodiment of the present invention, including a terminal, a client 2020, and a license terminal 2060. The terminal and the license terminal 2060 are connected through a wireless network or a limited network.

 The terminal includes at least one of a terminal device such as a desktop computer, a notebook, a personal digital assistant, a smart phone, a tablet computer, a portable media player, a large-sized wall-mounted display device, and the license terminal 2060. A terminal device for implementing the software licensing method of the present invention, including a desktop, a notebook, a personal digital assistant, a tablet, and the like.

 Further, the number of the client 2020 and the license terminal 2060 may be two or more.

 Preferably, the operating procedure of the software license may include:

 Step S901: The client 2020 sends a download and deployment request (software permission request) to the license end 2060 of the found software through an environment such as the Internet or cloud computing (when the software that satisfies the preset demand information is found).

 Step S902: After receiving the download and deployment request, the license terminal 2060 sends a license agreement to the client 2020.

 Step S903: After receiving the license agreement, the client 2020 starts the protocol review process, and if there is a suggestion for modification to the license agreement, sends a modification proposal to the license end 2060 to modify the license agreement.

 Step S904: After receiving the modification proposal, the permission end 2060 generates a modification protocol according to the proposal, and sends the modification protocol to the client 2020.

 Step S905: After receiving the modification protocol, the client 2020 starts the protocol review process. If there is a modification suggestion to the modification protocol, the proposal for modifying the modification protocol is sent to the permission end 2060, and if there is no modification suggestion, the user is accepted. The modification protocol sends an accept command to the license terminal 2060.

 Step S906: After receiving the accepting instruction, the license terminal 2060 sends the license information with the modified protocol as the license agreement to the client 2020. If a modification suggestion for the modification protocol is received, step S904 to step S906 are repeatedly executed until the acceptance instruction is received.

 Step S907: After transmitting the license information to the client 2020, the deployment instruction of the software running environment is sent to the client 2020. And start the software download program after receiving the deployment completion command.

Step S908: After receiving the deployment instruction, the client 2020 is configured according to the configuration information in the deployment instruction. The client deploys the software running environment. After the deployment is completed, the deployment completion instruction is sent to the license terminal 2060, and the software is downloaded from the license terminal 2060, and the software is installed at the client terminal 2020. After the software is customized and initialized, it enters the usable state.

 Step S909: After the license of the software is completed, the license mechanism is established and activated on the license end 2060 and the client 2020 by using the accepted modification protocol as the final license agreement.

 The above software licensing method can be used on PaaS, SaaS, cloud security, and cloud support platforms to support end-to-end management in a variety of endpoints and heterogeneous virtual environments. The invention can solve the license management mechanism and protocol of various types of software and application services in the cloud computing environment in a unified mode, and will make the automatic deployment of software and application services and user self-service become feasible. Schematic diagram.

The implementation environment shown in FIG. 10 is used to implement the software licensing method according to any embodiment or embodiment of the present invention. The difference from the first structure of the implementation environment of the software licensing method of the embodiment of the present invention is: the license terminal P includes software delivery. The server and the license management server, the client U _r U _M may include a software deployment server and a software management server, respectively.

 The license management server of the license terminal P performs the operation flow in the above steps 902, 904, 906, and 909 instead of the license terminal 2060.

The software delivery server of the license terminal P performs the operation flow of the above step 907 instead of the license terminal 2060. The software management server of the client U _r U _M can perform the operation flow in step 901, step 903, step 905, and step 909 described above.

 The client-side UrUM software delivery server replaces the client 2020 to perform the operation of step 908 above.

Further, the software delivery server and the license management server of the license terminal P respectively interact with the software deployment and license management server of any one of the user terminals UU _M to implement the software license. Implement licenses for multiple software or multiple application services.

 Referring to FIG. 11, FIG. 11 is a third structural diagram of an implementation environment of a software licensing method according to an embodiment of the present invention.

The implementation environment shown in FIG. 11 is used to implement the software license described in any embodiment or embodiment of the present invention. The method is different from the first structure of the implementation environment of the software licensing method of the embodiment of the present invention in that: the license terminals P _R P _M respectively include a software delivery server and a license management server, and the client LL may include a software deployment server and a software management server. .

The license management server of the license terminal P _R P _M performs the operation flow in the above steps 902, 904, 906, and 909 instead of the license terminal 2060.

The software delivery server of the license terminal P _R P _M performs the above-described operation flow of step 907 instead of the license terminal 2060.

 The software management server of the client U can proxy the client 2020 to perform the operation flow in the above steps 901, 903, 905, and 909.

 The software delivery server of the client U performs the operation flow of the above step 908 instead of the client 2020. Further, the software delivery server and the license management server of the client U interact with the software deployment and license management server of any one of the license terminals P-PM to implement the software license. Autonomous deployment and autonomous management of multiple software or application services of the client U are implemented.

 Figure 12 is a block diagram of a computer system 1000 in which embodiments of the present invention can be implemented. The computer system 1000 is merely an example of a computer environment suitable for use with the present invention and is not to be considered as limiting the scope of use of the present invention. Computer system 1000 is also not to be construed as requiring a combination of one or more components in an exemplary computer system 1000 that is dependent on or illustrated.

 The computer system 1000 shown in Figure 12 is an example of a computer system suitable for use with the present invention. Other architectures with different subsystem configurations can also be used. For example, desktops, notebooks, personal digital assistants, smart phones, tablets, and the like, which are well known to the public, may be suitable for some embodiments of the present invention. However, it is not limited to the devices listed above.

As shown in FIG. 12, computer system 1000 includes a processor 1010, a memory 1020, and a system bus 1022. Various system components, including memory 1020 and processor 1010, are coupled to system bus 1022. Processor 1010 is a hardware for executing computer program instructions through basic arithmetic and logic operations in a computer system. Memory 1020 is a physical device for temporarily or permanently storing computing programs or data (e.g., program state information). System bus 1020 can be any of the following types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus. The processor 1010 and the memory 1020 can communicate via the system bus 1022. Memory 1020 includes read only memory (ROM) or flash memory (not shown), and random access memory (RAM), which generally refers to main memory loaded with an operating system and applications.

 Computer system 1000 also includes a display interface 1030 (e.g., a graphics processing unit), a display device 1040 (e.g., a liquid crystal display), an audio interface 1050 (e.g., a sound card), and an audio device 1060 (e.g., a speaker). Display device 1040 and audio device 1060 are media devices for experiencing multimedia content.

 Computer system 1000 generally includes a storage device 1070. Storage device 1070 can be selected from a variety of computer readable media, which are any available media that can be accessed by computer system 1000, including both mobile and fixed media. For example, a computer readable medium includes, but is not limited to, a flash memory (micro SD card), a CD-ROM, a digital versatile disc (DVD) or other optical disc storage, a magnetic tape cartridge, a magnetic tape, a magnetic disk storage, or other magnetic storage device, or Any other medium that stores the required information and is accessible by computer system 1000.

 Computer system 1000 also includes an input device 1080 and an input interface 1090 (e.g., a 10 controller). The user can enter commands and information into the computer system 1000 via an input device 1080, such as a keyboard, mouse, or touch panel device on the display device 1040. Input device 1080 is typically coupled to system bus 1022 via input interface 1090, but may be coupled via other interfaces or bus structures, such as a universal serial bus (USB).

 Computer system 1000 can be logically coupled to one or more network devices in a network environment. The network device can be a personal computer, server, router, smart phone, tablet or other public network node. The computer system 1000 is connected to the network device via a local area network (LAN) interface 1100 or a mobile communication unit 1110. A local area network (LAN) is a network of computers that are interconnected in a limited area, such as a home, a school, a computer lab, or an office building that uses network media. WiFi and twisted pair cabling Ethernet are the two most common technologies for building LANs. WiFi is a technology that enables computer system 1000 to exchange data or connect to a wireless network via radio waves. The mobile communication unit 1110 can answer and make calls over a radio communication line while moving within a wide geographical area. In addition to the call, the mobile communication unit 1110 also supports Internet access in a 2G, 3G or 4G cellular communication system providing mobile data services.

It should be noted that other computers including more or fewer subsystems than computer system 1000 The system can also be applied to inventions. For example, computer system 1000 can include a Bluetooth unit that can exchange data over short distances, an image sensor for photography, and an accelerometer for measuring acceleration.

 As described in detail above, computer system 1000 suitable for use with the present invention is capable of performing the specified operations of the software licensing method. Computer system 1000 performs these operations in the form of software instructions that processor 1010 runs on a computer readable medium. These software instructions can be read into memory 1020 from storage device 1070 or through local area network interface 1100 from another device. The software instructions stored in the memory 1020 cause the processor 1010 to execute the software licensing method described above. Furthermore, the present invention can also be implemented by a hardware circuit or a hardware circuit in combination with software instructions. Thus, the invention is not limited to any specific combination of hardware circuitry and software.

 A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

However, it is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the scope of the invention should be determined by the appended claims.

Claims

Claim A software licensing method, comprising the steps of:  Receiving a software license request from the client;  Retrieving a license agreement in response to the software license request, and transmitting to the client;  Receiving a modification request of the user terminal to the license agreement;  Determining a modification protocol according to the modification request, and sending the message to the client;  Receiving an acceptance instruction of the modification protocol by the client, and using the modification protocol as a final license agreement;  Sending license information to the client.  2. The software licensing method according to claim 1, wherein before the step of receiving the software permission request of the client, the method further comprises the steps of:  Push the service information of the software to be licensed to the target network.  3. The software licensing method according to claim 1, wherein the determining the modification protocol according to the modification request and transmitting to the client comprises the following steps:  Extracting, by the modification request, the modification data of the license agreement by the user end;  Determining whether the requested data is within a preset protocol modification range;  If yes, the modification protocol is determined according to the modification data, and is sent to the client; if not, the prompt for changing the modification request is sent to the client.  The software licensing method according to any one of claims 1 to 3, further comprising the following steps after the step of transmitting the license information to the user terminal:  Sending, to the client, a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software;  Receiving a deployment completion instruction of the client, and permitting the client to download and install the corresponding software. The software license method according to claim 4, wherein the configuration information comprises configuration information of a virtual machine in a cloud computing environment.  The software licensing method according to claim 4, further comprising the following steps after the step of transmitting the deployment instruction of the software running environment to the client: The software charging program for the client is started by using the final license agreement as a charging protocol. 7. A software licensing system, comprising:  a first receiving module, configured to receive a software license request of the user end;  a protocol sending module, configured to obtain a license agreement in response to the software license request, and send the license agreement to the user end;  a second receiving module, configured to determine a modification protocol according to the modification request, and send the modification protocol to the user end;  a protocol modification module, configured to receive an acceptance instruction of the modification protocol by the client, and use the modification protocol as a final license agreement;  The third receiving module is configured to send the license information to the client.  8. The software licensing system of claim 7, wherein the protocol modification module is further configured to:  Extracting, by the modification request, the modification data of the license agreement by the user end;  Determining whether the requested data is within a preset protocol modification range;  If yes, the modification protocol is determined according to the modification data, and is sent to the client; if not, the prompt for changing the modification request is sent to the client.  The software licensing system according to claim 7 or 8, further comprising a software delivery module, configured to:  Sending, to the client, a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software;  Receiving a deployment completion instruction of the client, and permitting the client to download and install the corresponding software. 10. The software licensing system of claim 9, wherein the configuration information comprises configuration information of a virtual machine in a cloud computing environment.  11. A software licensing method, comprising the steps of:  Send a software license request to the license side;  Receiving a license agreement of the license end;  If the license agreement does not satisfy the preset agreement acceptance condition, obtaining a modification request for the license agreement, and sending the request to the license end; Receiving a modification protocol of the license end; And if the modification protocol satisfies the preset protocol acceptance condition, sending an acceptance instruction to the modification protocol to the permission end;  Receiving license information of the license side.  12. The software licensing method according to claim 11, wherein before the step of transmitting the software license request to the license side, the method further comprises the steps of:  And the software for satisfying the preset requirement information by using the target network, where the service information of each software is stored in the target network;  If found, a software license request is sent to the license side of the found software.  The software license method according to claim 11, wherein if the license agreement does not satisfy a preset protocol acceptance condition, obtaining a modification request for the license agreement, and transmitting the request to the license end The steps include the following steps:  Get a trigger event for the protocol modification button;  If the trigger event is obtained, determining that the license agreement does not satisfy a preset protocol acceptance condition, and displaying a protocol modification box;  Receiving the modification data input to the protocol modification box, generating a modification request including the modification data; and transmitting the generated modification request to the permission terminal.  The software license method according to claim 11, wherein if the license agreement does not satisfy a preset protocol acceptance condition, obtaining a modification request for the license agreement, and transmitting the request to the license end The steps include the following steps:  Extracting protocol data in the license agreement, and comparing whether the extracted protocol data matches the preset protocol data;  If there is no match, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and a modification request for the license agreement is generated according to the comparison result;  Sending the generated modification request to the permission side.  The software licensing method according to claim 11, wherein if the modification protocol satisfies the preset protocol acceptance condition, the step of transmitting an acceptance instruction to the modification protocol to the permission terminal comprises: The following steps: Extracting protocol data in the modification protocol, comparing the extracted protocol data with preset protocol data Whether it matches;  If yes, determining that the license agreement satisfies a preset protocol acceptance condition, and sending an acceptance instruction to the modification protocol to the permission end;  If there is no match, it is determined that the license agreement does not satisfy the preset protocol acceptance condition, and a modification request for the modification protocol is generated according to the comparison result;  Sending the generated modification request to the permission side.  The software licensing method according to any one of claims 11 to 15, characterized in that, after the step of receiving the license information of the license side, the method further comprises the steps of:  Receiving a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software;  Performing, in the user end, deployment of a software running environment according to the configuration information;  If the deployment of the software running environment is completed, the deployment completion instruction is sent to the permission end, and the corresponding software is downloaded and installed.  The software license system according to claim 16, wherein, when the configuration information includes configuration information of a virtual machine in a cloud computing environment, deploying a software running environment on the user end according to the configuration information The steps include the following steps:  According to the configuration information, virtual machine deployment in a cloud computing environment is performed on the user end.  The software license system according to claim 16, wherein after the step of transmitting the deployment completion instruction to the license terminal and downloading and installing the corresponding software, the method further comprises the following steps:  Obtaining running status information of the software on the user end;  If the running status information meets the preset normal operating condition, the accepted modification protocol is a charging protocol, and the software charging program for the user end is started at the user end;  If the running status information does not satisfy the preset normal operating condition, an abnormal alarm is sent.  19. A software licensing system, comprising:  a first sending module, configured to send a software license request to the license end;  a license agreement receiving module, configured to receive a license agreement of the license end; a second sending module, configured to: when the license agreement does not meet a preset protocol acceptance condition, obtain a modification request for the license agreement, and send the request to the permission end; Modifying a protocol receiving module, configured to receive a modification protocol of the permission end;  a third sending module, configured to send an accepting instruction to the modifying protocol to the permission end when the modifying protocol satisfies the preset protocol accepting condition;  The license information receiving module is configured to receive the license information of the license end.  20. The software licensing system of claim 19, further comprising a deployment module for:  Receiving a deployment instruction of a software running environment, where the deployment instruction includes configuration information of an operating environment of the software;  Performing, in the user end, deployment of a software running environment according to the configuration information;  If the deployment of the software running environment is completed, the deployment completion instruction is sent to the permission end, and the corresponding software is downloaded and installed.