Software license verification method and device, medium, equipment and program product

Abstract

The invention relates to a software license verification method and device, a medium, equipment and a program product, and relates to the technical field of computers.The method comprises the steps that an access request is received through a gateway, and whether a software license corresponding to a back-end software service stored in the gateway is within the validity period or not is verified through the gateway; in response to the fact that the software license is in the validity period, the access request is forwarded to the back-end software service through the gateway, the gateway can execute verification operation on the software license, offline verification on the software license is achieved under the condition of not depending on a server side, and the verification efficiency of the software license is improved. The back-end software service deployed in the private deployment environment can be effectively verified, so that the back-end software service is unavailable under the condition that the software license is expired. Moreover, the validity period of the software license is verified through the gateway, and the back-end software service is not invaded, so that the stability of the back-end software service is ensured.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a software license certificate verification method, apparatus, medium, equipment and program product. Background Art

[0002] In the related art, when verifying a software license, the client needs to interact with the server to verify the legitimacy of the software license. However, in the private deployment scenario of software services, access to the server used to verify the legitimacy of the license is not allowed. Therefore, a new method is urgently needed to verify the legitimacy of the license without using the server. Summary of the invention

[0003] This summary is provided to introduce concepts in a brief form that will be described in detail in the detailed description below. This summary is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0004] In a first aspect, the present disclosure provides a software license certificate verification method, comprising: Receive, through the gateway, an access request sent by a client, wherein the access request is used to request access to a backend software service; Verifying, through the gateway, whether the software license corresponding to the backend software service stored in the gateway is within the validity period; In response to the software license being within a validity period, the access request is forwarded to the backend software service through the gateway.

[0005] In a second aspect, the present disclosure provides a software license certificate verification device, comprising: A receiving module is configured to receive an access request sent by a client through a gateway, wherein the access request is used to request access to a backend software service; A verification module is configured to verify, through the gateway, whether the software license corresponding to the backend software service stored in the gateway is within the validity period; The forwarding module is configured to forward the access request to the backend software service through the gateway in response to the software license being within the validity period.

[0006] In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processing device, implements the steps of the method described in the first aspect.

[0007] In a fourth aspect, the present disclosure provides an electronic device, including: a storage device having a computer program stored thereon; A processing device is used to execute the computer program in the storage device to implement the steps of the method described in the first aspect.

[0008] In a fifth aspect, the present disclosure provides a computer program product, including a computer program, which implements the steps of the method described in the first aspect when executed by a processor.

[0009] Based on the above technical solution, the gateway receives the access request for requesting access to the backend software service, verifies whether the software license corresponding to the backend software service stored in the gateway is within the validity period, and forwards the access request to the backend software service through the gateway in response to the software license being within the validity period. By storing the software license corresponding to the backend software service in the gateway and performing the verification operation on the validity of the software license by the gateway, the software license can be verified offline without relying on the server, ensuring that the backend software service deployed in a private deployment environment can also be effectively verified, thereby making the backend software service unavailable when the software license expires. Moreover, the verification of the validity period of the software license through the gateway will not be intrusive to the backend software service, thus ensuring the stability of the backend software service.

[0010] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale. In the drawings: Figure 1 is a flow chart of a method for verifying a software license certificate according to some embodiments.

[0012] Figure 2 is a schematic diagram of a software license certificate verification method according to some embodiments.

[0013] Figure 3 is a logical diagram of a software license certificate verification method according to some embodiments.

[0014] Figure 4 The figure is a schematic diagram of the structure of a software license certificate verification device according to an exemplary embodiment.

[0015] Figure 5 It is a schematic structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0016] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0017] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0018] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0019] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0020] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0021] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0022] Figure 1 FIG. 1 is a flowchart of a method for verifying a software license certificate according to some embodiments. Figure 1 As shown, the embodiment of the present disclosure provides a software license certificate verification method, which can be executed by an electronic device, specifically by a software license certificate verification device, which can be implemented by software and / or hardware and configured in the electronic device. Figure 1 As shown, the method may include the following steps.

[0023] In step 110, an access request sent by a client is received through a gateway, where the access request is used to request access to a backend software service.

[0024] Here, the client may be a client corresponding to a software user using the backend software service. The backend software service may be a software service deployed in a private deployment environment. Private deployment refers to deploying software or services in a server or private cloud environment within an enterprise. For example, the backend software service may be a cloud computing service deployed in a private deployment environment. Of course, the backend software service may not be a software service deployed in a private deployment environment.

[0025] The gateway is used to receive and process access requests. For example, in a private deployment environment, the gateway receives and processes access requests from the internal network. The access request is used to request access to the backend software service.

[0026] It is worth noting that when the client needs to access the backend software service, the client sends an access request to the gateway in the electronic device, and the gateway receives the access request and determines whether to forward the access request to the backend software service.

[0027] In step 120, the gateway verifies whether the software license corresponding to the backend software service stored in the gateway is within the validity period.

[0028] Here, the software license is a license file included in the software service, which is used to specify the conditions under which the software service can be used, copied, modified and distributed. The software license corresponding to the backend software service is stored in the gateway. When the gateway receives an access request sent by the client to request access to the backend software service, the gateway determines the software license of the backend software service corresponding to the access request and verifies whether the software license is within the validity period.

[0029] It should be understood that the software license certificate can be generated by the software provider based on the relevant information provided by the client when the software user purchases the software service. When the backend software service is deployed, the generated software license certificate can be stored in the gateway corresponding to the backend software service.

[0030] In some embodiments, the validity period of the software license certificate may be queried from the software license certificate, and in response to the current time not exceeding the validity period, it is determined that the software license certificate is within the validity period.

[0031] The software license may record a corresponding validity period. If the current time does not exceed the validity period, the software license is determined to be within the validity period. If the current time exceeds the validity period, the software license is determined to be out of the validity period. For example, if the validity period in the software license is September 1, 2054, if the current time is June 1, 2054, the software license is within the validity period. If the current time is September 2, 2054, the software license is out of the validity period.

[0032] It is worth noting that the current time refers to the real time of the system. The length of the effective time depends on the length of time the user purchases the backend software service.

[0033] In step 130, in response to the software license being within the validity period, the access request is forwarded to the backend software service through the gateway.

[0034] Here, the software license is within the validity period, which means that the backend software service purchased by the user is still within the validity period, and the gateway forwards the access request to the backend software service so that the client can access the corresponding backend software service.

[0035] It is worth noting that, if the software license is not within the validity period, the gateway will not forward the access request to the backend software service, and the gateway can return a prompt message to the client that the software license has expired.

[0036] Thus, the gateway receives an access request for requesting access to the backend software service, verifies through the gateway whether the software license corresponding to the backend software service stored in the gateway is within the validity period, and forwards the access request to the backend software service through the gateway in response to the software license being within the validity period. By storing the software license corresponding to the backend software service in the gateway and performing the verification operation on the validity of the software license by the gateway, the software license can be verified offline without relying on the server, ensuring that the backend software service deployed in a private deployment environment can also be effectively verified, thereby making the backend software service unavailable when the software license expires. Moreover, by verifying the validity period of the software license through the gateway, it will not be intrusive to the backend software service, thus ensuring the stability of the backend software service.

[0037] In some feasible implementations, in step 120, the digital signature in the software license can be decrypted according to the public key stored in the gateway to obtain the decrypted digital signature, and the legality of the software license can be verified according to the decrypted digital signature. Then, in response to the legality of the software license, it is verified whether the software license corresponding to the back-end software service stored in the gateway is within the validity period.

[0038] Here, the software license carries a digital signature, which is generated by the private key corresponding to the public key. When the gateway receives an access request, the gateway reads the corresponding digital signature from the software license stored in the gateway, and decrypts the digital signature using the public key stored in the gateway to obtain the decrypted digital signature.

[0039] The hash value can be calculated for the content of the software license, and the calculated hash value can be encrypted with a private key to generate a corresponding digital signature, and the generated digital signature can be written into the software license. When the gateway receives an access request, it decrypts the digital signature in the software license using the public key stored in the gateway, and compares the decrypted digital signature with the hash value corresponding to the content of the software license (except the digital signature). If they are consistent, it means that the software license is legal. If they are inconsistent, it means that the software license has been tampered with and the software license is illegal.

[0040] It should be understood that the public key and the private key serve as a key pair, the digital signature is generated by the private key, and during the legitimacy verification, the digital signature is decrypted by the public key to ensure that the software license certificate is not tampered with.

[0041] If the software license is legal, the gateway will perform the operation of determining whether the software license is valid. If the software license is illegal, it means that the software license has been tampered with, and the gateway will not perform the operation of determining whether the software license is valid, and the gateway startup fails.

[0042] Therefore, through the public key stored in the gateway, the legitimacy of the software license can be verified in the gateway, and the validity period of the software license can be verified in the gateway, thereby realizing the verification of the legitimacy and validity of the software license in an offline environment without relying on the server.

[0043] In some practicable implementations, before step 110, a software license corresponding to the backend software service and a public key corresponding to the software license may be received and stored in the gateway.

[0044] Here, the software license is obtained according to the certificate generation template, the relevant information used to generate the software license and the digital signature generated by the private key, wherein the relevant information at least includes the validity period of the software license.

[0045] The software user may provide the software provider with relevant information required to generate a software license. Exemplarily, the relevant information may include, but is not limited to, the validity period, the first number of clients allowed to simultaneously access the backend software service, and / or a media access control (MAC) address used to describe the deployment environment of the backend software service.

[0046] After obtaining the relevant information required to generate a software license, the software provider can generate a key pair including a public key and a private key, and then issue a software license based on the relevant information and key pair in combination with a certificate generation template.

[0047] When deploying the backend software service, the software license and the public key are sent to the gateway of the backend software service to store the software license and the public key in the gateway of the backend software service.

[0048] Exemplarily, the certificate generation template may be as follows: type License struct { Company string `json:"company,omitempty"` (used to configure customer name) ProductName string `json:"product_name,omitempty"` (used to configure the software name) Version string `json:"version"` (used to configure the software version information) LicenseType string `json:"license_type"` (used to configure the type of software license certificate) IssuedDate string `json:"issued_date,omitempty"` (used to configure the issuance time of the software authorization certificate) ExpiryDate string `json:"expiry_date"` (used to configure the validity period of the software authorization certificate) Extra string `json:"extra,omitempty"` (used to configure other extended information) Signature []byte `json:"signature,omitempty"` (used to configure digital signature) } The certificate generation template may include the software name of the software service, the version information of the software service, and the expiration time of the software service. Of course, the Extra field may also be used in the certificate generation template to expand the first quantity information and / or MAC address information on the software authorization certificate.

[0049] It is worth noting that the software license generated based on the certificate generation template is actually a license.json file. For example, the software license can be expressed as: { "company":"ABC", "product_name":"test" "version":"v1.0" "license_type":"poc" "issued_date":"2024-01-15" "expiry_date":"2024-12-31" "signature":"" "extra":"{\"userlimit\":20000}" } In some embodiments, a corresponding software license may be generated by combining a certificate generation template and related information through a license generation tool, and then the generated digital signature is written into the signature field of the software license through the license generation tool.

[0050] Figure 2 FIG. 1 is a schematic diagram of a software license verification method according to some embodiments. Figure 2 As shown, the software user provides the software provider with relevant information for generating a software license. The software provider generates a key pair including a public key and a private key. The software provider generates a software license through the private key and related information. The software provider provides the software license and public key to the software user offline. The software user deploys the back-end software service and imports the software license and public key to the gateway of the back-end software service. When the software user needs to access the back-end software service, the software user sends an access request to the gateway, and the gateway verifies the legitimacy of the software license. If the software license is legal, the gateway further verifies the validity of the software license. If the software license is valid, the gateway forwards the access request to the back-end software service.

[0051] Figure 3 FIG. 1 is a logic diagram of a software license certificate verification method according to some embodiments. Figure 3As shown, the software provider side includes a license library and a license generation tool written in GO language. The license library includes a first function for generating a digital signature, a second function for verifying the legitimacy of the software license, and a third function for verifying the validity of the software license. Among them, the first function can generate a digital signature using an asymmetric algorithm. The license generation tool and the gateway rely on the license library.

[0052] The license generation tool generates an initial software license through the certificate generation template and related information, and then the license generation tool calls the first function in the license library to add the corresponding digital signature in the Signature field of the initial software license. The software license and public key generated by the license generation tool are stored in the gateway. When the gateway receives an access request sent by the client, the gateway calls the second function of the license library to verify the legality of the corresponding software license. If the software license is legal, the gateway references the third function of the license library to verify the validity of the corresponding software license. If the software license is within the validity period, the gateway forwards the access request to the backend software service.

[0053] It is worth noting that the license generation tool can have 4 parameters, including: isPreGenerateKeys, licenseFile, privateKeyFilePath, and publicKeyFilePath. Among them, isPreGenerateKeys is used to configure whether to generate public and private keys, licenseFile is used to indicate the file path of the software license, privateKeyFilePath is used to indicate the file path of the private key, and publicKeyFilePath is used to indicate the file path of the public key. The software provider can provide private.key and public.key according to the actual situation, and the license generation tool will automatically generate private.key and public.key.

[0054] Therefore, through the above implementation, the software license corresponding to the backend software service and the public key corresponding to the software license can be stored in the gateway, so as to perform the verification operation on the legality and validity of the software license in the gateway.

[0055] In some practicable implementations, the relevant information further includes information indicating a first number of clients allowed to simultaneously access the backend software service and / or a media access control address for describing a deployment environment of the backend software service.

[0056] The first quantity information is used to describe the number of users supported by the backend software service. The media access control address is used to describe the MAC restriction of the deployment environment of the backend software service.

[0057] Accordingly, the certificate generation template includes a preset field, and the preset field is used to write the first quantity information and / or the media access control address into the software license certificate.

[0058] Here, a preset field of Extra may be included in the certificate generation template, which is used to define the first quantity information and / or the media access control address in the software license certificate, so as to be able to extend other information in the software license certificate.

[0059] Therefore, by presetting the fields, other information can be expanded and filled in on the software license certificate to expand the resource type of the software license certificate and improve the flexibility of the software license certificate.

[0060] In some feasible implementations, in step 130, in response to the software license being within its validity period, the gateway can determine second quantity information of clients currently accessing the backend software service, and when the second quantity information is less than the first quantity information, the gateway can forward the access request to the backend software service.

[0061] Here, the second quantity information of the clients currently accessing the backend software service may refer to the number of clients currently using the backend software service. If the software license is within the validity period, the gateway further determines the second quantity information of the clients currently accessing the backend software service, and queries the first quantity information recorded in the software license through the software license. When the second quantity information is less than the first quantity information, it means that the backend software service can still receive access requests from other clients, and the gateway forwards the access request to the backend software service.

[0062] When the second quantity information is greater than or equal to the first quantity information, it indicates that the backend software service cannot receive too many concurrent access requests. In order to avoid overloading the backend software service, the gateway may not forward the access request to the backend software service. Accordingly, the gateway may return a prompt message to the client indicating that the backend software service is overloaded, so as to instruct the client to re-access the backend software service after a certain period of time.

[0063] Thus, by carrying the first quantity information in the software license, and forwarding the access request to the backend software service when the second quantity information is less than the first quantity information, the backend software service can be prevented from being overloaded due to too many access requests. Moreover, the access request can also be concurrently controlled through the software license and the gateway.

[0064] Figure 4FIG. 1 is a schematic diagram of a software license verification device according to an exemplary embodiment. Figure 4 As shown, the embodiment of the present disclosure provides a software license certificate verification device 400, and the software license certificate verification device 400 includes: The receiving module 401 is configured to receive an access request sent by a client through a gateway, wherein the access request is used to request access to a backend software service; A verification module 402 is configured to verify, through the gateway, whether the software license corresponding to the backend software service stored in the gateway is within the validity period; The forwarding module 403 is configured to forward the access request to the backend software service through the gateway in response to the software license being within the validity period.

[0065] Optionally, the verification module 402 is configured to: Decrypting the digital signature in the software license certificate according to the public key stored in the gateway to obtain the decrypted digital signature; Verify whether the software license is legal based on the decrypted digital signature; In response to the software license being legal, verify whether the software license corresponding to the backend software service stored in the gateway is within the validity period.

[0066] Optionally, the software license certificate verification device 400 further includes: A storage module is configured to receive and store in the gateway a software license corresponding to the back-end software service and a public key corresponding to the software license, wherein the software license is obtained according to a certificate generation template, relevant information for generating the software license and a digital signature generated by a private key, and the relevant information includes at least the validity period of the software license.

[0067] Optionally, the relevant information further includes first quantity information indicating clients allowed to simultaneously access the backend software service and / or a media access control address for describing a deployment environment of the backend software service; The certificate generation template includes a preset field, and the preset field is used to write the first quantity information and / or the media access control address into the software license certificate.

[0068] Optionally, the verification module 402 is specifically configured to: Query the validity period of the software license from the software license; In response to the current time not exceeding the valid time, it is determined that the software license certificate is within the valid period.

[0069] Optionally, the software license certificate includes first quantity information for indicating clients that are allowed to simultaneously access the backend software service; The forwarding module 403 is specifically configured as follows: In response to the software license being within the validity period, determining, through the gateway, second quantity information of clients currently accessing the backend software service; When the second quantity information is less than the first quantity information, the access request is forwarded to the backend software service.

[0070] The logic of the method executed by each functional module in the software license certificate verification device 400 can refer to the part of the method related to the above embodiment, and will not be repeated here.

[0071] Reference below Figure 5 , which shows a structural schematic diagram of an electronic device (eg, a server) 500 suitable for implementing an embodiment of the present disclosure. Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0072] like Figure 5 As shown, the electronic device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 to a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0073] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0074] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0075] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0076] In some embodiments, the client, gateway, and backend software services may communicate using any currently known or future developed network protocol, such as HTTP (HyperTextTransfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0077] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0078] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: receives an access request sent by a client through a gateway, wherein the access request is used to request access to a back-end software service; verifies through the gateway whether a software license corresponding to the back-end software service stored in the gateway is within the validity period; and in response to the software license being within the validity period, forwards the access request to the back-end software service through the gateway.

[0079] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0080] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0081] The modules involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a module does not, in some cases, limit the module itself.

[0082] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0083] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0084] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0085] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0086] Although the subject matter has been described in language specific to structural features and / or method logic actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims. Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Claims

1. A software license verification method, characterized in that: include: Receive, through the gateway, an access request sent by a client, wherein the access request is used to request access to a backend software service; Verifying, through the gateway, whether the software license corresponding to the backend software service stored in the gateway is within the validity period; In response to the software license being within a validity period, the access request is forwarded to the backend software service through the gateway.

2. The method according to claim 1, characterized in that The verifying whether the software license corresponding to the backend software service stored in the gateway is within the validity period includes: Decrypting the digital signature in the software license certificate according to the public key stored in the gateway to obtain the decrypted digital signature; Verify whether the software license is legal based on the decrypted digital signature; In response to the software license being legal, verify whether the software license corresponding to the backend software service stored in the gateway is within the validity period.

3. The method according to claim 2, characterized in that Before receiving the access request sent by the client through the gateway, the method further includes: Receive and store in the gateway a software license corresponding to the back-end software service and a public key corresponding to the software license, wherein the software license is obtained according to a certificate generation template, relevant information for generating the software license, and a digital signature generated by a private key, and the relevant information includes at least the validity period of the software license.

4. The method according to claim 3, characterized in that The relevant information also includes first quantity information indicating clients allowed to simultaneously access the backend software service and / or a media access control address for describing a deployment environment of the backend software service; The certificate generation template includes a preset field, and the preset field is used to write the first quantity information and / or the media access control address into the software license certificate.

5. The method according to claim 1, characterized in that The verifying whether the software license corresponding to the backend software service stored in the gateway is within the validity period includes: Query the validity period of the software license from the software license; In response to the current time not exceeding the valid time, it is determined that the software license certificate is within the valid period.

6. The method according to claim 1, characterized in that The software license certificate includes first quantity information for indicating the clients allowed to simultaneously access the backend software service; In response to the software license being within the validity period, forwarding the access request to the backend software service through the gateway includes: In response to the software license being within the validity period, determining, through the gateway, second quantity information of clients currently accessing the backend software service; When the second quantity information is less than the first quantity information, the access request is forwarded to the backend software service.

7. A software license verification device, characterized in that: include: A receiving module is configured to receive an access request sent by a client through a gateway, wherein the access request is used to request access to a backend software service; A verification module is configured to verify, through the gateway, whether the software license corresponding to the backend software service stored in the gateway is within the validity period; The forwarding module is configured to forward the access request to the backend software service through the gateway in response to the software license being within the validity period.

8. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processing device, the steps of the method according to any one of claims 1 to 6 are implemented.

9. An electronic device, characterized in that: include: a storage device having a computer program stored thereon; A processing device, configured to execute the computer program in the storage device to implement the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images