WO2009109119A1 - Procédé de commande de licence et dispositif de gestion - Google Patents

Procédé de commande de licence et dispositif de gestion Download PDF

Info

Publication number
WO2009109119A1
WO2009109119A1 PCT/CN2009/070470 CN2009070470W WO2009109119A1 WO 2009109119 A1 WO2009109119 A1 WO 2009109119A1 CN 2009070470 W CN2009070470 W CN 2009070470W WO 2009109119 A1 WO2009109119 A1 WO 2009109119A1
Authority
WO
WIPO (PCT)
Prior art keywords
license
client
authorization
unit
server
Prior art date
Application number
PCT/CN2009/070470
Other languages
English (en)
Chinese (zh)
Inventor
贺建斌
谢永政
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2009109119A1 publication Critical patent/WO2009109119A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
    • H04L2463/101—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measures for digital rights management

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a license control method and a license management apparatus.
  • the network that implements the license control includes a license server and several clients, as shown in Figure 1.
  • the license control is that the license server on the network loads the license file and communicates with the client to manage the authorization of the client, thereby implementing centralized control of the license server for all client licenses.
  • Step 101 The license server loads and enables the license file, and establishes an authorization database.
  • Step 102 The client requests a resource authorization or a function license from the license server.
  • Step 103 The license server determines whether the loaded license authorization period expires. The period returns to failure, otherwise proceeds to step 104;
  • Step 104 If the client sends a resource authorization request, the license server calculates whether the sum of the resource used by the client and the resource requested by the client is greater than the value of the licensable resource in the license file, if the value is less than or equal to the license file. If the resource value can be authorized, the license server returns the resource authorization of the specified size to the client; otherwise, the return of the client authorization fails;
  • An embodiment of the present invention provides a license control method and a license management apparatus to implement authorization according to different time periods or different service requirements.
  • an embodiment of the present invention provides a license control method and a license management apparatus that are implemented as follows:
  • a method of license control including:
  • a license management device includes:
  • a parsing unit configured to force the first license and the second license
  • a management unit configured to enable the first license and enable the second license when the second license trigger condition is met
  • the authorization unit authorizes the first license and the second license to the client.
  • the technical solution provided by the embodiment of the present invention can be used to detect the usage condition of the second license in the process of using the first license.
  • the license management device enables the second license and authorizes the second license to the client.
  • the use condition of the second license includes: enabling the second license when the initial use time of the second license is reached, or enabling the second license when the first license cannot provide the resource requested by the client and/or the requested function.
  • the client can be licensed differently under different business conditions.
  • FIG. 2 is a flow chart of an embodiment of a license control method of the present invention
  • FIG. 3 is a flow chart of another embodiment of a license control method according to the present invention.
  • FIG. 4 is a flow chart of another embodiment of a license control method according to the present invention.
  • FIG. 5 is a flowchart of another embodiment of a license control method according to the present invention.
  • FIG. 7 is a flow chart of another embodiment of a license control method according to the present invention.
  • Figure 8 is a block diagram of an embodiment of a server of the present invention.
  • FIG. 9 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 10 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 11 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 12 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 13 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 14 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 15 is a block diagram of another embodiment of the server of the present invention.
  • FIG. 16 is a block diagram of another embodiment of the server of the present invention.
  • Figure 17 is a block diagram of another embodiment of a server of the present invention.
  • the embodiment of the invention provides a license control method and a license management device.
  • the added customized interface may be in the form of a configuration file, a script command, a graphical interface, or the like.
  • the information of these configurations can be directly saved in the corresponding license file, or saved in the license file.
  • the second license is enabled to provide the service.
  • the trigger condition may be: detecting that the initial use time of the second license is set, or using the first license. Resources and/or features requested by the client cannot be provided.
  • FIG. 2 shows a flow of an embodiment of the license control method of the present invention. As shown in FIG. 2, the method includes: Step 201: The monthly license is loaded with the Normal License and the Promotion License.
  • the server can also establish an authorization database based on the loaded Normal License and Promotion License.
  • the server can load at least two levels of licenses.
  • Here is a description of loading the Normal License and the Promotion License.
  • Step 202 The server sets a usage period of the Promotion License through a customized interface.
  • the Normal License can be similar to the prior art, and is a licensee used by the server in daily situations.
  • Step 203 During the process of using the Normal License by the server, the custom use period of the Promotion License is detected, and the Promotion Licsnss is used when the start time of the time period arrives.
  • Step 204 The server sends an authorization notification to the client.
  • the server Since the server used the new license in the previous step, in this step, the server notifies the client to obtain authorization on the server, so that the client can obtain a new license on the server.
  • step 205 is not required, and the following step 205 may be directly performed.
  • Step 205 The client requests authorization from the server.
  • the client sends an authorization request to the server, requesting the server to authorize the resource or function.
  • the client may request authorization directly from the server if authorization is required, without having to wait for the notification from the server before requesting authorization from the server.
  • step 206 may be directly performed without performing steps 204 and 205.
  • the server can directly license the Promotion License to the client.
  • Step 206 may further include:
  • step 209 is not necessary, and the following step 209 can be directly performed.
  • Step 209 The client requests the return of the authorization to the server.
  • the client requests the return of the resource or function to the server.
  • the client may directly request the return authorization from the server if the aforementioned Promotion License is used, without waiting for the notification from the server to request the return authorization from the server.
  • the client may actively send a return authorization request to the server, so that in the case of a limited number of authorizations, the client-returned authorization may continue to be authorized to other clients. Improve license utilization and reduce the burden on the server.
  • Step 210 The server reclaims the authorization for the client Promotion License.
  • step 210 may be directly performed without performing steps 208 and 209. In this way, after the use of the Promotion License, the server can directly reclaim the authorization of the client.
  • Figure 3 shows the flow of another embodiment of the method, as shown in Figure 3, including:
  • Step 301 The monthly license is loaded with the Normal License and the Promotion License.
  • the server can also establish an authorization database based on the loaded Normal License and Promotion License.
  • the server can load at least two levels of licenses.
  • Here is a description of loading the Normal License and the Promotion License.
  • Step 302 The server sets the start time and duration of the Promotion License through a customized interface.
  • the Normal License can be similar to the prior art, and is a license used by the server in a daily situation.
  • the Promotion License is a license that is used from a specific point in time. It can be used for a specific length of time. Therefore, it is necessary to set the start time and duration of the Promotion License through the customized interface of the server.
  • Step 303 During the process of using the Normal License, the server detects the Promotion License. The initial usage time, and use the Promotion License when the initial usage time arrives.
  • Step 304 The server notifies the client to obtain the authorization.
  • the server Since the server used the new license in the previous step, in this step, the server notifies the client to obtain authorization on the server, so that the client can obtain a new license on the server.
  • this step is not required, and the following step 305 can be directly performed.
  • Step 306 The server authorizes the client and records the client authorization data.
  • the method may further include:
  • Step 307 The server detects the usage duration of the set Promotion License, and stops the Promotion License when the usage duration is exhausted.
  • Step 308 The server notifies the client to return the authorization.
  • step 309 is not necessary, and the following step 309 can be directly performed.
  • Step 309 The client requests the return of the authorization to the server.
  • the client requests the return of the resource or function to the server.
  • the client may directly request the return authorization from the server if the aforementioned Promotion License is used, without waiting for the notification from the server to request the return authorization from the server.
  • the client may actively send a return authorization request to the server, so that in the case where the number of authorizations is limited, the client-returned authorization may continue to be authorized to other clients, thereby Improve license utilization and reduce the burden on the server.
  • Step 310 The server reclaims the authorization for the client promotion license.
  • step 310 may be performed without performing steps 308 and 309. In this way, after the use of the Promotion License, the server can directly reclaim the authorization of the client.
  • Figure 4 shows the flow of another embodiment of the method, as shown in Figure 4, including:
  • the server can load at least two levels of licenses.
  • Here is a description of loading the Normal License and the Promotion License.
  • Step 402 The server sets the start time and the number of uses of the Promotion License through a customized interface.
  • the Normal License can be similar to the prior art, and is a licensee used by the server in daily situations.
  • Step 403 During the process of using the Normal License, the server detects the start time of the Promotion License and uses the Promotion License when the initial usage time arrives.
  • Step 404 The server notifies the client to obtain the authorization.
  • the server Since the server used the new license in the previous step, in this step, the server notifies the client to obtain authorization on the server, so that the client can obtain a new license on the server.
  • step 405 is not required, and the following step 405 may be directly performed.
  • Step 405 The client requests authorization from the server.
  • the client sends an authorization request to the server, requesting the server to authorize the resource or function.
  • the client may request authorization directly from the server if authorization is required, without having to wait for the notification from the server before requesting authorization from the server.
  • Step 406 The server authorizes the client and records the client authorization data.
  • step 406 may be directly performed without performing steps 404 and 405.
  • the monthly server can directly use the Promotion License. Authorized to the client.
  • Step 406 may further include:
  • Step 407 The server detects the number of times the resources and/or functions in the set Promotion License are used, and stops the Promotion License when the number of uses is exhausted.
  • Step 408 The server notifies the client to return the authorization.
  • step 409 is not necessary, and the following step 409 can be directly performed.
  • Step 409 The client requests the return of the authorization to the server.
  • the client may directly request the return authorization from the server if the aforementioned Promotion License is used, without waiting for the notification from the server to request the return authorization from the server.
  • the client may actively send a return authorization request to the server, so that in the case where the number of authorizations is limited, the client-backed authorization may continue to be authorized to other clients. Improve license utilization and reduce the burden on the server.
  • Step 410 The server reclaims the authorization for the client promotion license.
  • step 410 may be directly performed without performing steps 408 and 409. In this way, after the use of the Promotion License, the server can directly reclaim the authorization of the client.
  • the difference includes that the server sets the usage conditions of the Promotion License through the customized interface, which are the usage time period, the initial usage time, the usage duration, the start time, and the resources in the Promotion License and/or Or the number of uses of the feature. That is to say, the use of the Promotion License is determined by the time period, or by the time and duration of use, or by the start time and the number of times the resources and/or functions in the Promotion License are used.
  • the usage conditions include the initial usage time, so the server can start using the Promotion License when it detects the arrival of the initial usage time.
  • the above three embodiments are merely illustrative, and other usage conditions may be used according to actual needs.
  • the license server can automatically enable the previous license in the usual time, enable the latter license in a certain period of time, and resume the previous license after a certain period of time. In this way, the actual needs of the business can be met, the benefits of the user's investment can be maximized, and the cost of the customer can be reduced in the purchase.
  • FIG. 5 shows a flow of an embodiment of the method. As shown in FIG. 5, the method includes:
  • Step 501 The monthly license is loaded with the Normal License and the Promotion License.
  • the server can also establish an authorization database based on the loaded Normal License and Promotion License.
  • the server can load at least two levels of licenses.
  • the Normal License can be similar to the prior art, and is a license used by the server in daily situations.
  • a Promotion License is a license that is used in a specific business situation.
  • the Promotion License includes a specific feature license (such as a function that the Normail License does not have), and/or includes more traffic than the Normal License. Resource authorization.
  • Step 502 The client initiates an authorization request to the server, and reports the resource and/or function request.
  • the client sends an authorization request to the server, where the authorization request includes resource request information and/or function request information for requesting corresponding resources and/or functions.
  • Step 503 When the normal license cannot provide the resources and/or functions requested by the client, the Promotion License is enabled and authorized to the client;
  • the server detects that the total number of resources requested by the client exceeds the number of authorized resources in the Normal License file and/or the requested function is not enabled in the Normal License file, the server enables resources and/or functions in the Promotion License file, and The Promotion License is licensed to the client.
  • Step 503 may further include:
  • Step 504 The client periodically reports the currently required resources and/or functions to the server.
  • Step 505 Stop the Promotion License when using the Normal License to provide the resources requested by the client and/or the requested function;
  • the server detects that the total number of resources requested by the client is within the number of authorized resources in the Normal License file and/or the requested function is enabled in the Normal License file, the server disables the resources and/or functions in the Promotion License file. And reclaim the Promotion License authorization for the client.
  • Step 601 The monthly service is loaded with the Normal License and the Promotion License.
  • the server can also establish an authorization database based on the loaded Normal License and Promotion License.
  • the server can load at least two levels of licenses.
  • the Normal License can be similar to the prior art, and is a license used by the server in daily situations.
  • a Promotion License is a license that is used in a specific business situation.
  • the Promotion License includes a specific feature license (such as a function that the Normail License does not have), and/or includes more traffic than the Normal License. Resource authorization.
  • Step 603 The client initiates an authorization request to the server, and reports the resource and/or function request.
  • the client sends an authorization request to the server, where the authorization request includes resource request information and/or function request information for requesting corresponding resources and/or functions.
  • Step 604 Enable the Promotion License and authorize the client when the normal license cannot provide the resources and/or functions requested by the client;
  • the server detects that the total number of resources requested by the client exceeds the number of authorized resources in the Normal License file and/or the requested function is not enabled in the Normal License file, the server enables resources and/or functions in the Promotion License file, and The Promotion License is licensed to the client.
  • Step 604 can also include:
  • FIG. 7 shows a flow of another embodiment of the method. As shown in FIG. 7, the method includes:
  • Step 701 The monthly service is loaded with the Normal License and the Promotion License.
  • the server can also establish an authorization database based on the loaded Normal License and Promotion License.
  • Step 702 The server sets the number of times the Promotion License is used through the customized interface.
  • Step 703 The client initiates an authorization request to the server, and reports the resource and/or function request.
  • the client sends an authorization request to the server, where the authorization request includes resource request information and/or function request information for requesting corresponding resources and/or functions.
  • Step 704 When the normal license cannot provide the resources and/or functions requested by the client, the Promotion License is enabled and authorized to the client;
  • the server detects that the total number of resources requested by the client exceeds the number of authorized resources in the Normal License file and/or the requested function is not enabled in the Normal License file, the server enables resources and/or functions in the Promotion License file, and The Promotion License is licensed to the client.
  • the method may further include:
  • Step 705 The server detects the number of times the set client uses the resources and/or functions in the Promotion License, and disables the resources and/or functions in the Promotion License file when the set number of uses is reached, that is, when the number of uses is exhausted. Reclaim the Promotion License authorization for the client.
  • the server disables the Promotion License, which is the current resource and/or function usage reported by the client, and the duration of use.
  • the number of times a resource and/or feature has been used in the Promotion License may be used according to actual needs.
  • the server may also set a usage period of the Promotion License through a customized interface, where the usage period is defined by a start usage time and an usage end time, and during the usage period, the client request cannot be provided by using the Normal License.
  • the Promotion License is enabled and authorized to the client, and then the set end time is detected.
  • the Promotion License file is stopped and the Promotion License authorization for the client is further withdrawn.
  • the server receives the authorization request and the resource and/or function request sent by the client, and when the normal license cannot provide the resource and/or function requested by the client, for example, the server If the total number of resources requested by the client exceeds the number of authorized resources in the first license file and/or the function of the request is not enabled in the first license file, the resources and/or functions in the second license file are enabled, and the first The second license is granted to the client, so that the server can perform different licenses for the client under different business conditions.
  • the license server can automatically enable the former license under the condition of general traffic demand or general function requirements, and is enabled under specific traffic demand conditions or specific function requirements.
  • the latter license is restored to the previous license after a specific traffic demand situation or a specific function requirement. In this way, the actual needs of the business can be met, the benefits of the user's investment can be maximized, and the cost of the customer can be reduced in the purchase.
  • FIG. 8 shows a block diagram of an embodiment of the license management apparatus, as shown in the following figure:
  • a license management apparatus includes a parsing unit 801, a management unit 802, and an authorization unit 803, where
  • the parsing unit 801 is configured to load the first license and the second license
  • the management unit 802 is configured to enable the first license and enable the second license when the second license trigger condition is met;
  • Authorization unit 803 authorizes the first license and the second license to the client.
  • the license management device may be specifically a server.
  • FIG. 9 is a block diagram of another embodiment of the license management apparatus.
  • the license management apparatus may further include a customized interface 901 and a detecting unit 902, where The customized interface 901 is configured to set an initial usage time of the second license.
  • the detecting unit 902 is configured to detect a start time of the set second license, and notify the management unit 802 that the second license trigger condition is satisfied when the initial use time arrives.
  • the customized interface 901 is further configured to set a usage end time of the second license.
  • the detecting unit 902 is further configured to detect a usage end time of the set second license, when the use end time arrives, The management unit 802 is notified to stop the second license.
  • the custom interface 901 is further configured to set a usage duration of the second license
  • the license management device further includes a timing unit 903, configured to detect a usage duration of the set second license, and notify the management unit 802 to stop the second license when the usage duration is exhausted.
  • the timing unit 903 may be a single module or may be combined with the detecting unit 902.
  • an embodiment may be further included, where the customized interface 901 is further configured to set the number of times of using the second license;
  • the license management device further includes a counting unit 904, configured to detect the used number of times of the set second license, and notify the management unit to stop the second license when the number of uses is exhausted.
  • the counting unit 904 may be a single module or may be combined with the detecting unit 902.
  • the license management apparatus may further include: a receiving unit, configured to receive a return authorization request sent by the client, and notify the authorization unit to reclaim the first Second license authorization;
  • the authorization unit is further configured to reclaim the second license authorization for the client according to the return authorization request sent by the client received by the receiving unit.
  • FIG. 13 is a block diagram of another embodiment of the license management apparatus.
  • the license management apparatus may further include a receiving unit 1301 and a determining unit 1302, where The receiving unit 1301 is configured to receive an authorization request sent by the client, where the authorization request includes a resource request and/or a function request;
  • the determining unit 1302 is configured to determine, according to the authorization request received by the receiving unit 1301, that the management unit 802 is notified to satisfy the second license triggering condition when the first license cannot provide the resource and/or function requested by the client.
  • the determining unit 1302 is further configured to send a stop to the management unit 802 when the first license can provide resources and/or functions requested by the client.
  • the management unit 802 may be further configured to stop the second license according to the stopping the second license notification sent by the determining.
  • the customized interface 1401 is configured to set a usage end time of the second license.
  • the detecting unit 1402 is configured to detect a usage end time of the set second license, and notify the management unit 802 to stop the second license when the usage end time arrives.
  • FIG. 15 shows a block diagram of another embodiment of the license management apparatus.
  • the license management apparatus may further include a customized interface 1501 and a timing unit 1502, where
  • the customized interface 1501 is configured to set a usage duration of the second license.
  • the timing unit 1502 is configured to detect a usage duration of the set second license, and notify the management unit 802 to stop the second license when the usage duration is exhausted.
  • the customized interface 1601 is further configured to set the number of times the second license is used
  • the counting unit 1602 is configured to detect a used number of times of the second license, where the When the number of uses is exhausted, the management unit 802 is notified to stop the second license.
  • the receiving unit 1301 is further configured to receive a return authorization request sent by the client, and notify the authorization unit 803 to reclaim the second license authorization for the client.
  • the authorization unit 803 is further configured to reclaim the second license authorization for the client according to the return authorization request sent by the client received by the receiving unit 1301.
  • the promotion license is enabled when the start time of the Promotion License arrives, and the Promotion License is authorized to the client; or the server uses the Normal License. If the total number of resources requested by the client exceeds the number of authorized resources in the Normal License file and/or the requested function is not enabled in the Normal License file, the resources and/or functions in the Promotion License file are enabled, and the Promotion License is authorized. Client. In this way, the server can be differently licensed to the client in different time periods or different business situations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention porte sur un procédé de commande de licence qui comprend la fourniture d'un service à un terminal client par l'utilisation de la première licence ; le démarrage de la seconde licence conformément à la condition de déclenchement de seconde licence ; l'autorisation de la seconde licence au terminal client. L'invention porte également sur un dispositif de gestion de licence. Le procédé et le dispositif sont capables d'effectuer différentes autorisations de licences au terminal client dans différents segments temporels, ou d'effectuer différentes autorisations de licences au terminal client dans différentes circonstances commerciales.
PCT/CN2009/070470 2008-03-03 2009-02-19 Procédé de commande de licence et dispositif de gestion WO2009109119A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810083101.4 2008-03-03
CN2008100831014A CN101247400B (zh) 2008-03-03 2008-03-03 许可证控制方法及管理装置

Publications (1)

Publication Number Publication Date
WO2009109119A1 true WO2009109119A1 (fr) 2009-09-11

Family

ID=39947598

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070470 WO2009109119A1 (fr) 2008-03-03 2009-02-19 Procédé de commande de licence et dispositif de gestion

Country Status (2)

Country Link
CN (1) CN101247400B (fr)
WO (1) WO2009109119A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11987831B2 (en) 2012-03-30 2024-05-21 Novozymes A/S Processes for producing a fermentation product

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247400B (zh) * 2008-03-03 2011-02-02 华为技术有限公司 许可证控制方法及管理装置
CN101945394A (zh) * 2009-07-10 2011-01-12 华为技术有限公司 许可证管理方法、装置与系统
CN104751025B (zh) * 2013-12-30 2018-08-24 新华三技术有限公司 一种授权许可License的控制方法和装置
CN104504308B (zh) * 2014-12-11 2017-09-01 国云科技股份有限公司 一种禁止虚拟机使用软件的许可证验证方法
CN104468825B (zh) * 2014-12-26 2018-06-26 湖南华凯文化创意股份有限公司 远程授权方法及系统
CN108241681A (zh) * 2016-12-26 2018-07-03 大唐移动通信设备有限公司 一种许可文件批量生成方法和系统
CN110781459A (zh) * 2019-09-04 2020-02-11 西安交大捷普网络科技有限公司 一种授权许可的管控方法、系统及电子设备
CN112100641A (zh) * 2020-11-09 2020-12-18 成都掌控者网络科技有限公司 一种多维授权方法、系统、设备及存储介质
CN115391068B (zh) * 2022-10-26 2023-01-17 南方电网数字电网研究院有限公司 基于it资源管控体系的框架构建方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004046756A (ja) * 2002-05-20 2004-02-12 Fujitsu Fip Corp ライセンス管理方法、ライセンス管理システム、ライセンス管理プログラム
CN1645797A (zh) * 2005-01-28 2005-07-27 南望信息产业集团有限公司 在数字版权管理系统中使用的优化安全数据传输的方法
CN1874218A (zh) * 2006-01-05 2006-12-06 华为技术有限公司 一种许可证管理方法、系统及装置
CN1946033A (zh) * 2006-10-24 2007-04-11 华为技术有限公司 一种实现电信设备端口license管理的方法及其系统
CN101247400A (zh) * 2008-03-03 2008-08-20 华为技术有限公司 许可证控制方法及管理装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4767689B2 (ja) * 2003-12-05 2011-09-07 ソニー株式会社 コンテンツ配信システム、コンテンツ配信方法、コンテンツ処理装置、コンテンツ処理方法、記録媒体、及び、プログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004046756A (ja) * 2002-05-20 2004-02-12 Fujitsu Fip Corp ライセンス管理方法、ライセンス管理システム、ライセンス管理プログラム
CN1645797A (zh) * 2005-01-28 2005-07-27 南望信息产业集团有限公司 在数字版权管理系统中使用的优化安全数据传输的方法
CN1874218A (zh) * 2006-01-05 2006-12-06 华为技术有限公司 一种许可证管理方法、系统及装置
CN1946033A (zh) * 2006-10-24 2007-04-11 华为技术有限公司 一种实现电信设备端口license管理的方法及其系统
CN101247400A (zh) * 2008-03-03 2008-08-20 华为技术有限公司 许可证控制方法及管理装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11987831B2 (en) 2012-03-30 2024-05-21 Novozymes A/S Processes for producing a fermentation product

Also Published As

Publication number Publication date
CN101247400B (zh) 2011-02-02
CN101247400A (zh) 2008-08-20

Similar Documents

Publication Publication Date Title
WO2009109119A1 (fr) Procédé de commande de licence et dispositif de gestion
US9009079B2 (en) Planning assignment of software licenses
JP2004086392A (ja) 計算機構成変更方法およびシステム
US10909220B2 (en) Method and apparatus for facilitating the transfer of a software license between computer systems
JP5863128B2 (ja) ソフトウェアライセンスコントロール
EP2248060B1 (fr) Système de gestion de licences de logiciel qui fonctionne en mode déconnecté ou en mode connecté par intermittence
EP2248058B1 (fr) Système de gestion de licence de logiciel de poste-à-poste en vue de la réinstallation temporaire de licences de logiciel disponibles
CN108574593B (zh) 一种nfv网络中许可证的管理系统和管理方法
US20090119218A1 (en) License management apparatus, license management method, and license authentication program
MX2014008562A (es) Expedicion de licencias de aplicacion utilizando proveedores de sincronizacion.
CN111079091A (zh) 一种软件的安全管理方法、装置、终端及服务器
CN111526111B (zh) 登录轻应用的控制方法、装置和设备及计算机存储介质
US20130262265A1 (en) System and Method for Managing Software Licenses
EP2637120B1 (fr) Point d'ancrage de registraire de licence d'entreprise
WO2008080319A1 (fr) Procédé de gestion de licence web et système associé, terminal client et serveur de licence
US20060064387A1 (en) Systems and methods for software licensing
US20030061136A1 (en) Software license management system
CN109992298B (zh) 审批平台扩充方法、装置、审批平台及可读存储介质
US20080147850A1 (en) Method for Operating a Data Communications Network Using License Data and Associated Device Network
US8032928B2 (en) Methods, devices, and computer program products for controlling wireless connection access
CN106131187B (zh) 一种授权的控制方法及装置
WO2010130230A1 (fr) Procédé et appareil permettant d'offrir un service à un utilisateur
WO2008125042A1 (fr) Système de communication, dispositif de communication et procédé de contrôle de capacité
JP2003186559A (ja) ライセンス管理システム、ライセンス管理装置及び方法並びにプログラム
JP2010003215A (ja) 画像処理システム、画像処理装置及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09717573

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09717573

Country of ref document: EP

Kind code of ref document: A1