26AMENDED CLAIMS[received by the International Bureau on 03 April 2003 (03.04.03) ]Claims
1. A method for licensing digital resources and services, characterized in that the method comprises the steps of:
- as a response to a licensing request, transforming a license template into a license request by changing and/or adding (411) attribute values in a license request unit
(103) handling license templates containing attributes, and transmitting (414) the formed license request to a license creation unit (102) processing license requests,
- in the license creation unit (102) transforming the license request into an execution license by changing and/or adding attribute values of the license request (506) and transmitting (512) the execution license to a license control unit (104) controlling the use of resources and/or services.
2. A method according to claim 1, characterized in that it comprises steps of:
- activating a certain license control unit (104) as a response to receiving an activating service request directed to a resource or a service (205),
- interpreting execution licenses of multiple services and/or resources in the certain license control unit (104), and
- controlling in the certain license control unit (104) on the basis of the attribute values of the execution licenses the operation of licensed services and/or resources and activating service requests (206) directed to them.
3. A method according to claim 1, characterized in that concurrent execution licenses controlled by a certain license control unit (104) directed to a certain service and/or resource contain different number of attributes and/or different attribute values and/or multiple values for certain attributes.
4. A method according to claim 1, characterized in that it comprises a step of defining by the attribute values of an execution license at least a version number of a license schema (311), a target environment of the execution license (321), an identifier of the licensed resource or service, and constraints of the execution license
(322).
5. A method according to claim 1, characterized in that it comprises steps of recognizing a set of pre-defined exceptional situations in the license control unit (104) and activating the instructions for exception handling (211) defined by the attribute values of the execution license in each of the exceptional situations.
6. A method as according to claim 5, characterized in that it comprises steps of observing, based on the version number of a license schema of a license template, in the license request unit (103), situations, where there is no capability in the license control unit (104) to interpret attributes of an execution license, and as a response to the observation, in the license request unit (103), executing a pre-defined instruction for exception handling.
7. A method according to claim 1, characterized in that it comprises a step of defining in addition integrity constraints limiting interrelationships between attributes for attribute values of an execution license or a check-sum (330) describing the integrity of attributes and/or a step of encrypting (312) part of a content of an execution license.
8. A method according to claim 1, characterized in that it comprises a step of combining, in the license request unit (103),
- data of a license template containing attribute values defining the product and being interpretable by an license control unit (104), and
- certain values built-up from the target environment
into a license request (411), which is transmitted to the license creation unit (414).
9. A method according to claim 1, characterized in that it comprises steps of transforming, in the license creation unit (102), a state-attribute from a license request state to an execution license state by changing attribute values (506), attaching (509) to the defined execution license certain license templates and product descriptions, which are usable by the license request unit (103), and transmitting the execu- tion license with the attachments to the license control unit (104) of the target environment.
10. A method according to claim 1, characterized in that with the attributes of the execution licenses there is defined constraints for limiting the use of a resource or a service.
11. A method according to claim 1, characterized in that it comprises steps of transmitting the license request through a data communication link to the license creation unit (102), which is integrated to a certain electronic trading center, and 28
transmitting the execution license created in the license creation unit (102) through an electronic trading center to a customer.
12. A method according to claim 1, characterized in that it comprises a step of transmitting customer-specific execution licenses (612, 613) as a response to a transmitted license request and customer data.
13. A method according to claim 12, characterized in that the licensed services and/or resources, and their customer-specific execution licenses (612, 613) are controlled by two or more manufacturers and/or distributors.
14. A method according to claim 1, characterized in that the steps as a response to a presented licensing request are executed automatically, mechanically and the handled attributes and attribute values of each of the steps are at a range interpret- able by a license control unit (104).
15. A system for licensing digital resources and services, characterized in that the system comprises
- a license request unit (103) for transforming license templates into license requests by changing and/or adding attribute values contained in those,
- a license creation unit (102) for transforming license requests into execution licenses by changing and/or adding attribute values contained in those, and
- a license control unit (104) for controlling the use of resources and/or services by the execution licenses based on attribute values contained in those.
16. A system according to claim 15, characterized in that an execution license is a full license for making use of the whole resource or service; a limited license, a trial license, an evaluation license, or a temporal license for limiting the usage; a transfer license for transferring an execution license to another execution environ- ment; a continuation license or an add-on product license for extending the functionality.
17. A system according to claim 15, characterized in that the system comprises in addition, a license template unit (101) for creating license templates based on a license schema defining an attribute.
18. A system according to claim 15, characterized in that the execution license comprises a version number (311) of a license schema and data about a product or a 29
service to be licensed, a license type, a target environment (321), constraints of the execution license (322), and instructions for exception handling (323).
19. A system according to claim 15, characterized in that the license request unit
(103) comprises means for establishing a data communication connection to the li- cense creation unit (102) for transmitting license requests.
20. A system according to claim 15, characterized in that the license creation unit (102) comprises means for recording a produced execution license into a data structure and/or for storing it in a mass memory.
21. A system according to claim 15, characterized in that the license creation unit (102) comprises means for establishing a data communication connection for transmitting an execution license to the license control unit (104).
22. A system according to claim 15, characterized in that the license creation unit (102) comprises means for establishing a data communication connection to a payment system for paying the license fees.
23. A system according to claim 15 or 22, characterized in that the license request unit (103), the license creation unit (102) and the license control unit (104) are located in the same equipment.
24. A system according to claim 15, characterized in that the license creation unit (102) is integrated to a payment system for paying the license fees.
25. A system according to claim 23 or 24, known from that the used payment system is a chargeable service number.
26. A system according to claim 15, characterized in that the license control unit
(104) and the unit using the execution license (105) are integrated into a uniform, single unit.
27. A system according to claim 15, characterized in that the license creation unit (102) is located in equipment of the party granting and managing the licenses.
28. A system according to claim 15, characterized in that a using unit (105) is a base product and used resources (106) are add-on products utilized by a base product.