Method for Verifying the Validity of a Ticket; Mobile Device

Abstract

A method for checking the validity of a ticket involves transferring information from a control entity to a mobile device. A code is computed on the basis of this information, of a derived key and of a property individual for the mobile device, the code being subsequently checked by the control entity.

Claims

1-16. (canceled)

17. A method for checking the validity of a ticket, having the following steps of: transferring an information item, in particular a ticket-checking-process initiation information item from a control entity to a mobile device; computing a code individual for the mobile device in the mobile device, employing the information, wherein in the mobile device a key is stored which is incorporated in the computation of the individual code, wherein the key is formed from a key stored on a server and of a property individual for the mobile device; representing the code on the mobile device and/or transmitting the code from the mobile device to the control entity over an air interface; checking the code by the control entity.

18. The method according to claim 17, wherein the transfer of the information is effected by reading and/or by photographing the information from a display device of the control entity.

19. The method according to claim 17, wherein the transfer of the information is effected via a contactless information exchange, in particular over an air interface.

20. The method according to claim 17, wherein the information and/or the code is a machine-readable information item, and/or a manually transferable information item and/or code.

21. The method according to claim 17, wherein the mobile device is a mobile phone, a tablet PC and/or a smart phone.

22. The method according to claim 17, wherein the computation of the individual code is effected without requiring a mobile data connection.

23. The method according to claim 17, wherein the computation of the individual code is effected exclusively employing the data already present on the mobile device at the time of the transfer of the information from the control entity to the mobile device.

24. The method according to claim 17, wherein the control entity is a ticket checking device.

25. The method according to claim 17, wherein before the transfer of the information a ticket purchase from a ticket server is effected, wherein, after completion of the purchase, wherein a ticket information item in the form of a machine-readable code is transferred to the mobile device.

26. The method according to claim 17, wherein the ticket information is incorporated additionally in the computation of the control code.

27. The method according to claim 17, wherein the representation of the code on the mobile device comprises the representation of the ticket information.

28. The method according to claim 17, wherein the property individual for the mobile device is an information item from at least one of an IMEI, a processor serial number and/or the MAC address of the mobile device.

29. The method according to claim 17, wherein the property individual for the mobile device is data which are protected in the mobile device against copying and/or unauthorized use.

30. A mobile device which is adapted to receive an information item from a control entity, wherein the mobile device is configured to compute, by means of a computing unit, a code that is individual for the mobile device, while employing the information, wherein the mobile device has a memory in which a key can be stored which is incorporated in the computation of the individual code, wherein the key is executed such that it is formed from a key stored on a server and a property individual for the mobile device, and wherein the mobile device is configured to represent the code on a display device of the mobile device.

31. Use of a mobile device in a method according to claim 17.

32. Use of a control entity in a method according to claim 17.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG. 1 shows a schematic representation of components that can be used in a method according to the invention; and

[0027] FIG. 2 shows the sequence of a method according to the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION

[0028] In the following the invention will be described with reference to the FIGS. 1 and 2 by means of merely exemplary embodiments.

[0029] FIG. 1 shows a mobile device 10. The mobile device can be a mobile communication device, a tablet PC and/or a smart phone, for example. The mobile device 10 is supplied with a display device 18, which can serve as input means simultaneously. The display device 18 can be configured as a touch-sensitive or capacitive display, for example. Further, the mobile device can be supplied with a multiplicity of tactile operation elements 19, as well as a camera device on the back side (not shown), wherein in FIG. 1 one operation element 19 is represented exemplarily.

[0030] Applications can be loaded on the mobile device. With the aid of applications, it is possible for a user of a mobile device to execute services on the mobile device. Applications can be employed to display, for example, news and/or the weather, applications can be employed for example to purchase tickets or tickets for transport means or access cards. These tickets can be employed to prove an access authorization in public transport means. So far, in public transport means tickets have been used that were printed on paper or the like, in order to prove that the passenger/user has paid for a ticket before boarding the transport means. However, lately electronic payment methods have increasingly become accepted, wherein the user buys the ticket electronically before boarding the transport means and shows said ticket in electronic form upon an inspection. In order avoid multiple copying of the ticket 11, the tickets are tied to a further authentication factor, such as for example a credit card, an identity card and/or a discount card of the user (two-factor authentication). If the user copied the ticket 11, he would also have to copy the discount card, the credit card and/or the identity card, which is not possible or is possible only with considerable effort.

[0031] However, this type of two-factor authentication has the disadvantage that a check of the ticket 11 by means of a control device 16 takes considerable time, since not only the ticket 11 has to be read, but also the credit card or discount card. Consequently, depending on the time available, inspectors/conductors are not able to inspect all electronic tickets “properly”, limiting themselves to a quick glance at the QR code.

[0032] This is where the invention comes to bear. According to the invention, the user first buys a ticket 11 by means of his mobile device 10. To simplify the buying process, he can download a suitable application from an app store 20 for this purpose. Alternatively, the user can also buy the ticket via a browser interface of the provider or he can buy the ticket at home and subsequently send it to his mobile device 10, for example by email or MMS, or download the ticket with his mobile device 10.

[0033] According to the invention it is provided that a key is stored in the mobile device 10, preferably in a secure memory area (secure element) or a secure software container of the mobile device. This key is transmitted from a server 12 to the mobile device 10, wherein the key transmitted to the mobile device 10 is a derived key. The derived key is derived from the key stored on the server 12 in a secure environment (master key), wherein a property individual for the mobile device 10 is incorporated in the key. The derived key stored in the mobile device 10 is updated at regular intervals, for example hourly, daily, weekly and/or monthly.

[0034] During an inspection of the ticket 11, a (ticket) inspector transfers an information item to the mobile device by means of a control entity 16, in particular with his ticket checking device. The information can be transferred manually, for example. Therein, the inspector shows the user a multi-digit number that is represented on the control entity 16 and the user of the mobile device 10 inputs this information on the display device 18 of the mobile device. Alternatively, the user can read and process a QR code represented on the display device of the control entity 16 by means of a camera device of the mobile device 10. Alternatively, the information can be transmitted over the air interface, in particular via WLAN, Bluetooth and/or NFC, from the control entity 16 to the mobile device 10. In case of a transmission via NFC (according to ISO 14443) it is required to establish a relatively short distance (<10 cm) between the mobile device 10 and the control entity 16 for a short period of time.

[0035] As soon as the mobile device 10 has received the information from the control entity 16, the mobile device 10 computes an individual code 13 in the mobile device. The transferred information, the derived key stored in the mobile device and an individual property of the mobile device are incorporated in the computation of the individual code 13. The individual property of the mobile device 10 can already be present in the derived key and be introduced by the server 12. In other words, the IMEI is regarded as an individual property of the mobile device, for example. The IMEI (international mobile station equipment identity) is a number which is unique for each mobile device 10. Consequently, it can be ensured that the code 13 is tailored individually to the mobile device 10, the derived key and the information transferred by the control entity 16. Since both the derived key and the information transferred by the control entity 16 change at regular intervals, it can be ensured that counterfeiting of the ticket is rendered nearly impossible.

[0036] The computation of the individual code 13 is effected by means of a computing device (CPU) of the mobile device 10. The computed code 13 can be stored subsequently in a memory, in particular in a secure storage area (secure element), of the mobile device 10. For the computation of the code 13 it is not required that the mobile device 10 is connected to the server 12 via an online data connection. This is advantageous when the inspection takes place in locations with insufficient data connection.

[0037] After the computation of the code 13, said code is represented on the display device 18 of the mobile device 10. In the embodiment example shown in FIG. 1, the ticket 11 bought from the ticket server 22 and the code 13 are represented in an arrangement of one above the other. Alternatively, the code 13 could also comprise the ticket information 11, so that merely the representation of a QR code 13 is effected on the display device 18. Further, it would also be possible to represent the ticket information 11 and the 13 code offset in time on the display device 18, wherein it is possible in addition that the representation of the ticket information 11 of the code 13 is effected alternately at intervals of time.

[0038] As soon as the code 13 is represented on the display device 18, the control entity 16 can read out the code 13 (and possibly also the ticket information 11) by means of a camera device or a scanner device (for example a laser scanner). The control entity 16 checks whether the code 13 was formed employing the information ascertained by the control entity 16, the current, derived key, and the property individual for the mobile device 10. If this is true, it can be safely determined that a valid ticket information item 11 for this mobile device 10 is given.

[0039] The process just described can be carried out in a very short time (less than 10 seconds) and does not require presentation of a second object (for example the credit card). Thereby, the method can be carried out very quickly.

[0040] Alternatively or additionally, it is possible, as already stated above, that the representation of the code 13 is effected on a wireless transmission device of the mobile device 10. The wireless transmission device can be a Bluetooth module, an NFC module and/or a WLAN module. With this wireless transmission device it is possible to transmit the code to the control entity 16 over an air interface in wireless manner. In the control entity it can be checked whether the ticket and the computed code 13 are valid, i.e. whether the computation has been carried out correctly. This procedure has the advantage that it takes place completely in the background and the user does not need to present the mobile device 10 to the inspector for reading an optical code 13 by means of the control entity 16.

[0041] FIG. 2 shows again by means of a diagram how the derived key is transmitted from the server 12 to the mobile device 10. The derived key can be transmitted from the control entity 16 to the mobile device 10 before and/or after transferring the information. It is merely required that the current, derived key is present in the mobile device 10 at the time of computation of the code. However, it is preferred to transmit the derived key in advance, so that the complete check of the validity of the ticket 11 can be carried out “off line”, i.e. without an existing or active data connection.

[0042] The method according to the invention further has the advantage that in a transition phase, the control device 16 can be configured so that it can check tickets both according to the hitherto procedure (two-factor authentication) and to the method according to the invention. Further, it is not required to convert the hardware of the control entity 16. Merely the software of the control entity 16 would have to be adjusted.

[0043] In FIG. 1, the ticket server, from which the ticket information or the ticket 11 is purchased, and the server 12, on which the key is stored, are represented as two separate units. It need not be mentioned that the server 12 and the ticket server 22 could also be represented as one unit. In the derivation of the key by means of the server 12 known PKI methods can be used. The control entity 16 must have a public key for checking or verifying the code.