WO2001055820A2

WO2001055820A2 - Data processing system

Info

Publication number: WO2001055820A2
Application number: PCT/DE2001/000017
Authority: WO
Inventors: Bernd Hochdorfer
Original assignee: Infineon Technologies Ag
Priority date: 2000-01-25
Filing date: 2001-01-05
Publication date: 2001-08-02
Also published as: DE10003086A1; WO2001055820A3

Abstract

The invention concerns a data processing system, comprising a first data processing device (1) having at least one program object; an interface device (2) connected to the first data processing device (1) and a second data processing device (7) that can be connected to the interface device (2) and that contains a read-only storage having at least a second program object, whereby the first and the second program objects have program interfaces for communicating with one another and the first program object is completely functional only when communication of the program object is enabled by the connection of the second data processing device (7) to the interface device (2). The second data processing device is preferably a portable device, for example a chip card, while the first data processing device is an ordinary computer.

Description

description

Data processing system

The invention relates to a data processing system, in particular a data processing system with two communicating data processing devices.

The unauthorized, i.e. license-free use of software such as application programs, databases or

Data collections (pictures, texts) is in the state of the art u. a. prevented with so-called dongles. A dongle that is connected, for example, to the parallel interface of a data processing system or more recently to the Universal Serial Bus (USB) is a component that uses suitable hardware to carry out logical tasks such as encrypting and counting system starts, for example, and a program, which controls this hardware, confirms the licensing of a program. The program to be executed on the computer sends a request to the dongle and sends an answer back to the program. If this answer is the expected one, the program can carry out its tasks in the computer so that it can be used by the user. A dongle is therefore limited to sending a type of "OK" signal without otherwise interfering with the functionality of the program. The program on the computer is working or is not working entirely.

However, there are disadvantages to using dongles. The program to be performed contains places in which the query of the dongle is programmed. By tracking this down Query points in the program can be removed from the program using suitable programming tools. A program modified in this way can therefore be reproduced without having to use the software protection (dongle) provided.

A further disadvantage is that it is possible to use replicas of the dongle used for a program in order to deceive the querying program about the true license status.

Another frequently occurring phenomenon in the prior art is the existence of various different variants of a program which differ in the configuration of their program code and which therefore have different performance features. So there is

Differences in performance that result from the program composition. Depending on the scope of the various program variants, the program provider may charge a different price.

However, this procedure has the disadvantage that different program versions have to be maintained at the same time and that new program variants may have to be imported if the performance requirements change. This requires a lot of time for both the manufacturer and possibly the user.

In the course of developing an increasingly complex software market, differentiated

Licensing models developed. So there are so-called demo versions that can be used free of charge for a certain time or only a certain predetermined number of Allow program starts. Also commercially licensed

Programs sometimes have expiry times at which the

License becomes invalid. Common full versions, however, cost a fixed amount regardless of their useful life. Only in the case of complex large-scale computing systems are there billing systems for software in which, for example, the used one

Computing time or the processor type used (depending on

Performance) lead to different license amounts. Small computer systems such as desktop computers, personal computers or workstations do not have such billing forms. So it makes no difference whether one

Word processing software is used only once a month or permanently.

The present invention is therefore based on the object of avoiding the disadvantages outlined in the prior art, outlined above, by providing a new type of flexible software management.

The object is achieved by the provision of a data processing system according to independent claim 1. Further advantageous configurations, aspects and details of the invention result from the dependent patent claims, the description and the attached drawing.

In one aspect, the invention relates to a system in which parts of the software are outsourced to an external system which is inaccessible to the user.

In a further aspect, the invention relates to at least two data processing devices, on each of which Program projects run that can only achieve the functionality of an application program in connection with each other.

In another aspect, the invention relates to a billing system which is located in an external data processing device shielded by the user.

The invention is therefore directed to a data processing system having a first data processing device with at least a first program object, an interface device connected to the first data processing device and a second data processing device connectable to the interface device, which contains a read-only memory with at least one second program object located therein, the first and the second program object has program interfaces for communication with one another and the first program object is only fully functional if the communication of the program objects by

Connection of the second data processing device to the interface device is made possible.

A data processing device in the sense of the present invention is to be understood as a unit which is suitable for independent data processing. This must therefore consist of a computing unit which is able to process program codes, a memory in which such a program code is located and in which, if applicable. Data are stored, as well as input and

Output interfaces for communication of the data processing device with its environment, such as for example input / output channels for controlling

Screens, keyboards etc.

A program object in the sense of the present invention is to be understood as a program code (sequence of commands to the computing unit), which forms a self-contained functional unit and is capable of processing the program code on request from outside, for example by other program objects Calculate results on the computing unit and pass them on to other program objects, or display them on output media. A program object is decoded step by step from a memory in the computing unit and executed there. The delimitation of a program object is not always easy, since a program object can have several functions, which in turn can be carried out by partial program objects of a program object. However, the term program object and its use are sufficiently familiar to the person skilled in the art.

An interface device in the sense of the present invention is to be understood as a physical unit which is able to connect at least two but also more data processing devices to one another in such a way that data between these data processing devices is transported in at least one direction, but preferably in both directions can be.

A program interface in the sense of the present invention includes defined data structures or

Understand program codes that are used to exchange information between different program objects. These program objects communicate with each other via program interfaces.

The invention is therefore based on the idea of using at least one second data processing device in which part of the functionality of the program is stored in a read-only memory and can be processed there independently. A read-only memory in the sense of the present invention is any memory which is capable of receiving program code or data, which can not be changed by the user of a program and a first data processing device without undue effort. In the simplest case, a read-only memory can be a ROM which does not permit changes to the data stored therein. These are therefore not accessible to a user. To improve flexibility, however, it is preferred that the read-only memory be programmable one or more times. However, this is done by special programming devices that are not accessible to the user or by

Encryption methods that hide the stored information.

By using a specialized second data processing device with a read-only memory, the functionalities implemented therein or the program objects executable there can be effectively protected against access by users.

So neither is manipulation of the second

Program objects stored in the data processing device can also analyze the functionality on which they are based. The sequence of the interaction of the first data processing device and the second data processing device follows the following general flow diagram.

- Program object n

Calls up a program object x (program part) which has been outsourced to a second data processing device; Transfer of parameters via the interface;

-Check the parameters in the second

Data processing system;

Processing of the outsourced program object x;

Transfer of results via the interface; -Continue with program object n or n + 1.

The parameters and the results can also be transferred in encrypted form in order to reliably prevent manipulation of the mechanism by unauthorized persons.

The first data processing device preferably has an application program with a plurality of first program objects. An application program typically consists of a large number of functional units, which can be referred to here as program objects and which can interact with one another and with program objects which are stored on the second data processing device.

By providing a second

Data processing device, the functionality of the first, actual data processing device is completed. The phrase "only makes it full The desired overall functionality of the program is available to the user of the first data processing device only when the two data processing devices are connected both to Hardware1eve1, that is to say via the interface device and to software level, that is to say via the defined program interfaces.

The term “full functionality” in the sense of the present invention can be understood to mean various things.

Firstly, the at least second program object can have functions which can be called up by at least one first program object via the interface and which are necessary for the full functionality of the first program object. In such a case, the program that is to run on the first data processing device, for example, cannot be started at all, if not the second

Data processing device via the interface device with the first

Data processing device is connected. In this respect, the second data processing device according to the invention fulfills a function similar to the dongle, albeit a more complex one.

The difference to the dongle can be seen in the fact that no program functionality is outsourced to the dongle, but the entire program functionality remains on the computer and only a query with a defined answer to the

Dongle is put. Furthermore, the "full functionality" can consist in that the second data processing device has at least one

Contains program object that supplements the functionality of at least a first program object. In this case, the program is basically also without the connection to the second

Data processing device has limited executability. The additional program objects in the second

However, data processing devices can be used to allow different program versions to be created through specifically outsourced functionality components, although only a single program has to be distributed and installed on the computer (first data processing device). The performance features can thus be generated in the desired composition.

Furthermore, the "full functionality" of the first program object can relate to the fact that the second data processing device contains at least one program object which replaces the functionality of at least one corresponding first program object. Through this

Software developers are given the opportunity to correct the errors in their delivered software without the first

Data processing device manipulations, such as the import of patches or the like, must be carried out. Instead of a patch, which requires laborious installation, the user is simply sent a new, second data processing device which, after replacing the old second data processing device, takes over its function and contains program objects which now take the place of program objects which were originally executable in the first data processing device. The original program objects must be dated Application program can be identified and deactivated. For this, too, it makes sense to provide appropriate mechanisms that interact in an

Program objects of the first data processing device and program objects of the second data processing device can take place.

The division of the data processing system according to the invention into a first data processing device and a second

Data processing device opens up completely new possibilities in the service design of a software provider. It is thus possible to design the program on the first data processing device in such a way that the first data processing device has a program object which can store error messages from the first data processing device and / or further program objects located on the first data processing device in a memory of the second data processing device. For this purpose, for example, a corresponding program object can be provided on the second data processing device, which accepts the data from the first program object on the first data processing device and stores it in a memory (which of course cannot then be a read-only memory). In this way it is possible to generate an error history that can be read out by suitable readers from technicians of the respective software provider on site or after the second data processing device has been sent to the manufacturer and can then be evaluated in order to detect errors in the program or

To be able to recognize data processing device. This results in the preferred embodiment that the second data processing device at least one

Contains data object, which contains information about errors that have occurred in the first data processing device and / or the first program object.

Furthermore, it is possible to additionally implement the functionality of a classic dongle by the first

Data processing device has a program object which can read and identify at least one license key stored in a memory of the second data processing device. Since the second data processing device is an independent data processing device with a computing unit and suitable program objects, it is possible to use a dongle functionality of the second, if desired

Extend data processing device far beyond what is possible with conventional dongles. Such a licensing system can include different modes of billing the use of the software license. For example, the number of operations called, the number of system initializations, system starts, date limits, for example an expiry date of the license, the duration of the programs or the computing power consumed when deciding whether the license is still valid or has already expired can be taken into account. The license key is then currently calculated in the second data processing device based on such criteria and output to a first program object on the first data processing device. It is therefore no longer a classic in the classic sense

License key, but more about information as to whether the program object may start correctly depending on various evaluation parameters. In a simple case, the second

Data processing device simply have a program object which, on request of a program object of the first data processing device, can transmit a license key or a consent signal to the first data processing device.

In addition, the data processing system can be characterized in that the second

Data processing device has at least one second program object which is able to determine how long and / or how often first program objects of the first data processing device are used and which can store the corresponding information.

If different configurations of a program or different time-limited versions of a program are to be operated simultaneously and by means of a single second data processing device, it makes sense to provide the first data processing device with a program object which read at least one version key stored in a memory of the second data processing device and can identify. A version key must also be included in the second data processing device, which version key has been individually tailored to the respective user, for example. It is therefore possible to provide a second data processing device in which all the necessary externalized program objects are present at the same time, for example in a read-only memory, and when the program is delivered, information is provided in a memory provided for this purpose, here as a version key designated to file which configuration respectively

Versions of the respective user legally allowed to run on his first data processing device.

Accordingly, the invention is preferably limited to one

Data processing system aimed at the second

Data processing device has a program object, which on request of a program object of the first

Data processing device can transmit a version key to the first data processing device.

As already indicated variously above, it will often be preferred for reasons of flexibility that the second data processing device is a transportable unit. A transportable unit is to be understood as one which can be carried out without great effort

Interface device can be removed and can be sent back and forth between users and software manufacturers via usual transport routes, for example by post. However, it is also conceivable not to make the second data processing device transportable, for example by connecting it firmly to the first data processing device. In such a case, it may make sense to equip the second data processing device with a modem and a telephone connection, so that remote maintenance or key release etc. is possible via a telephone line.

In particular, it is preferred that the second data processing device is a chip card. A

Chip card is usually a flat card, for example in the format of a check card, on which an integrated circuit as a computer unit and a memory, etc. which is located at the top of the

Contacts with contacts, for example one

Interface device within the scope of the invention

Data processing system can be contacted. The computing unit on the chip card makes it possible to

Provide functionality in the form of program objects on the chip card. It is desirable that

Complexity of those on the chip card

Adapt program objects to the computing power and the memory requirement and capacity of the chip card.

To design the second data processing device and the interface between the first data processing device and the interface device, which is the second

Data processing device houses, numerous possibilities are available.

In the case of a fixed installation, the second data processing device is permanently installed in the computer or so with the computer (first

Data processing device) connected that a solution is only possible with disproportionate effort. For example, it is possible to provide a plug-in board that implements the second data processing device or that embodies the second data processing device in the form of an installation housing for a hard disk insert. When using a permanently installed card, the card to be installed must be adapted to the bus system used in the computer, for example PCI, Future Bus or Nubus.

A second data processing device installed in the first data processing device in the form of a standalone built-in housing can be used via conventional internal

Channel systems are connected to the first data processing device, for example via SCSI connections or

SCA connections or IEEE 1394 (Firewire) connections. These bus systems are also available when the second data processing device is implemented as an external unit in the form of an independent housing. In addition, it is also possible to establish a connection between the second data processing device and the first via further, simpler external bus systems

To carry out data processing device, for example through the Universal Serial Bus (USB), via serial or parallel interfaces or even via conventional network connections such as the Internet or token ring.

The alternative to a fixed installation in the computer or directly on the computer is to install the second data processing device in a mobile manner. Here, the connection between the first and second data processing device is designed such that it can be easily canceled, preferably even during operation, as is possible with modern bus systems such as Firewire or USB. It is also possible to design the interface device as an external unit, for example in the form of a chip card reader or a PCMCIA connection or via a connection to another interface. Accordingly, chip cards or PCMCIA or other logic cards must be used.

The data processing system according to the invention with a connectable second data processing device has numerous advantages and gives software developers a completely new flexibility in distribution, maintenance and Licensing your software. Will be the second

Carried out data processing device portable, for example, a program can be installed on several computers, after connecting the second data processing device to the respective computer

License is activated.

If an error history is saved on a portable system, maintenance of the entire system can be simplified if necessary, since this error memory can be read and interpreted by customer service. A costly journey by a service technician is therefore no longer necessary. Rather, only the transportable second data processing device has to be sent.

It is also possible to accommodate license and other maintenance systems for several programs simultaneously in a second data processing device according to the invention.

Parts of a program being tested do not need to be installed with the installation of the main program on the first data processing device, but can be stored in the second data processing device, so that after the completion of a corresponding program part, the second part can be replaced

Data processing device is sufficient to provide error-free functionality to the user. A partial reinstallation of the program on the first data processing device is therefore not necessary.

Figure 1 shows a highly schematic embodiment of the present invention. This becomes a mobile one System shown in which a computer 1 is the first

Represents data processing device and from a common computer hardware, program objects one

Application program and a suitable interface exists.

The interface device 2 has a contact strip with contacts 3 and screws 4, which can be screwed into corresponding screw holes at the interface of the first data processing device 1 by means of their end pieces 5. The interface device 2 also has a receptacle 6 into which a second data processing device, here a chip card 7, can be inserted. The interface device 2 can also be equipped with a plurality of receptacles 6.

In the present example, the second data processing device 7 is a so-called smart lock card and has an interface with which a coupling to the interface device is possible, a logic unit, a program memory and a memory for data. In the present case, the power supply also takes place via the interface device 2.

Claims

Patent Claims Patent claims

1. Data processing system with

a first data processing device (1) with at least one first program object;

an interface device (2) connected to the first data processing device (1); and

a second data processing device (7) which can be connected to the interface device (2) and which has a

Contains read-only memory with at least one second program object located therein;

wherein the first and second program objects have program interfaces for communication with one another and the first program object is only fully functional if the communication of the program objects is made possible by the connection of the second data processing device (7) to the interface device (2).

2. Data processing system according to claim 1, characterized in that the first data processing device

(1) has an application program with a plurality of first program objects.

3. Data processing system according to claim 1 or 2, characterized in that the at least one second program object has functions which of the at least a first Programmo ject can be called via the interface and which for the full functionality of the first

Program object are necessary.

4. Data processing system according to one of claims 1 to 3, characterized in that the second data processing device (7) contains at least one program object which is necessary for the functionality of at least a first program object.

5. Data processing system according to one of claims 1 to 4, characterized in that the second data processing device (7) contains at least one program object that complements the functionality of at least a first program object.

6. Data processing system according to one of claims 1 to 5, characterized in that the second data processing device (7) contains at least one program object which replaces the functionality of at least one corresponding first program object.

7. Data processing system according to one of claims 1 to 6, characterized in that the first data processing device (1) has a program object which error messages of the first data processing device (1) and / or further program objects can be stored in a memory of the second data processing device (7).

8. Data processing system according to one of claims 1 to 7, characterized in that the second data processing device (7) at least one data object contains information about errors occurring in the first data processing device (1) and / or the first

Program object occurred.

9. Data processing system according to one of claims 1 to 8, characterized in that the first data processing device (1) has a program object which can read and identify at least one license key stored in a memory of the second data processing device (7).

10. Data processing system according to one of claims 1 to

9, characterized in that the second data processing device (7) has a program object which, on request of a program object of the first data processing device (1), can transmit a license key to the first data processing device (1).

11. Data processing system according to one of claims 1 to

10, characterized in that the first data processing device (1) has a program object which can read and identify at least one version key stored in a memory of the second data processing device (7).

12. Data processing system according to one of claims 1 to

11, characterized in that the second data processing device (7) has a program object which, on request of a program object of the first data processing device (1), can transmit a version key to the first data processing device (1).

13. Data processing system according to one of claims 1 to

12, characterized in that the second data processing device (7) has at least one second program object which is able to determine how long and / or how often first program objects of the first data processing device (1) are used; and that can store the corresponding information.

14. Data processing system according to one of claims 1 to

13, characterized in that the second

Data processing device (7) is a portable unit.

15. Data processing system according to claim 14, characterized in that the second data processing device (7) is a chip card.

16. Data processing system according to claim 14 or 15, characterized in that the second

Data processing device is a chip card which has a computing unit, an interface for connection to the first data processing device (1) and a memory for storing program objects and data objects.

17. Data processing system according to one of claims 1 to 16, characterized in that the connection between the first data processing device (1) and interface device (2) has a serial interface.

18. Data processing system according to one of claims 1 to

16, characterized in that the connection between the first data processing device (1) and the interface device (2) has a parallel interface.