Electronic ticket, system for issuing electronic tickets, and devices for using and performing operations on electronic tickets

• US 20040030658A1
• Filed: 05/28/2003
• Published: 02/12/2004
• Est. Priority Date: 05/28/2002
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Cruz, Carmen Santa
• Application Number:
  US10/446,515
• Publication Number:
  US 20040030658A1
• Time in Patent Office: Days
• US Class Current: 705/65
• CPC Class Codes: G06Q 20/045 using payment protocols involving tickets
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G07B 15/00 Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points handling coins or valuable papers, e.g. banknotes, G07D; apparatus for vending or hiring articles or services activated by coins, credit cards, paper currency or the like G07F7/00, G07F17/00
• CPC Class Codes: G07F 17/42 for ticket printing or like apparatus , e.g. apparatus for dispensing of printed paper tickets or payment cards

Abstract

An electronic ticket includes user information, ticket application information, and a ticket object further including a ticket data object. A modular electronic ticket includes an XLM document divided into several XML parts, the parts further including user information, and individual tickets, the individual tickets further including user information, and ticket application information including a part for a ticket object with a link specified by a keyword to a ticket data object, the ticket data object being presented by a device when the ticket is to be used.

Claims

1. A device (102) for presenting an electronic ticket (300),

characterised in that

the device (102) includes

receiving means (263) for receiving an electronic ticket (300) from a ticket issuing system (101), the electronic ticket (300) including user information (301), ticket application information (302), and ticket object (303),

a ticket storage (230) for storing at least one electronic ticket (300),

parsing means (202) for detecting a predefined keyword (402) in the ticket object (303) thus generating a parsing result,

generation means (206) responsive to the parsing means (202) for generating a presentation command for presenting means (260B) adapted to present a ticket data object (403) defined by a link including the keyword (402), if the parsing result is that the predefined keyword (402) is detected.

2. A device according to claim 1,

wherein the presenting means (260) include a display (261) for displaying the object (403).

3. A device according to claim 1,

wherein the presenting means (260) include a radio frequency tag (265) for beaconing the object (403).

4. A device according to claim 1,

wherein the presenting means (260) include a loudspeaker (264) for presenting the object (403) aurally.

5. A device according to claim 1,

wherein the presenting means (260) include a sending means (262) for sending the object (403) to a predefined address (ADDR) via a communications channel, such as over the air interface.

6. A device according to claim 1,

characterized in that

the device further includes security means (250) for encrypting and/or decrypting, authenticate and/or sign (PKI means) the ticket data.

7. A device according to claim 1 or 6,

characterised in that

the ticket storage (230) is adapted to store a receipt relating the ticket (300).

8. A device according to claim 1, 6, or 7,

characterised in that

it has means for using or storing a modular ticket (350) containing a plurality of tickets (300A, 300B, 300C).

9. A device according to claim 8,

characterised in that

the modular ticket (350) further includes a plurality of ticket application identifiers (302A, 302B, 302C) each relating to specific ticket object (303A, 303B, 303C) or to one ticket application (200).

10. A device according to claim 5,

wherein the predefined address (ADDR) is included in the ticket application information (302) or ticket object (303).

11. A device according to any one of the preceding claims,

wherein the parsing means (202) are responsive to a request (REQ) received from an inspection system (106).

12. A device according to claim 5 or 10,

wherein the predefined address (ADDR) is obtained from a ticket inspection system (105, 106).

13. A device according to any one of the preceding claims,

wherein the electronic ticket is an XML document.

14. A device according to any one of the preceding claims,

wherein said device (102) is a mobile terminal.

15. A system (101) for issuing electronic tickets (300),

characterised in that the system includes

generating means (501) for generating an electronic ticket (300) including user information (301), ticket application information (302), and ticket object (303), wherein the generating means (501) generate a link including a predefined keyword (402) into the ticket object (303), the link defining a ticket data object (403),

sending means (502) adapted to send the electronic ticket (300) and the ticket data object (403) to a device (102, 103, 104, 105), especially to a device (102) according to any one of the claims 1 to 14.

16. A system according to claim 15,

wherein the ticket data object (403) is embedded to the electronic ticket (300) or into the ticket object (303).

17. A system according to claim 15 or 16,

characterised in that

the generating means (501) further store a predefined address (ADDR) to the ticket application information (302) or to ticket object (303) of the electronic ticket (300).

18. A system according to claim 15, 16, or 17,

characterised in that

the generating means (501) are further adapted to store a predefined address (ADDR) to the ticket application information (302) or to ticket object (303).

19. A system according to claim 15, 16, 17, or 18,

characterised in that

the generating means (501) further store a plurality of ticket object (303A, 303B, 303C) for one user information (301) and/or some ticket application information (302, 302A, 302B, 302C), thus forming a modular electronic ticket (350).

20. A system according to claim 15, 16, 17, 18 or 19,

wherein the ticket object (303) includes an XML frame (401).

21. A system according to claim 15, 16, 17, 18 or 19,

wherein the object (403) is embedded into the XML frame 401.

22. A system including

a system (101) for issuing electronic tickets, adapted to send electronic tickets (300) to a device (102), an electronic ticket (300) including user information (301), ticket application information (302), and ticket object (303), the system (101) particularly according to any one of the claims 15-21,

a device (102) for presenting an electronic ticket comprising i) a ticket storage (230) for storing at least one electronic ticket (300), ii) parsing means (202) for detecting a predefined keyword (402) in the ticket object (303), and iii) generation means (206) responsive to the parsing means (202) for generating a presentation command for presenting means (260B) if the parsing result is that the predefined keyword (402) is detected, the device (102) particularly according to any one of the claims 1-14, and

a device (105, 106) for inspecting electronic tickets (300), the device (105, 106) having predefined address (ADDR) and including i) receiving means (601) for receiving a ticket data object (403) from a device (102), the ticket data object (403) being defined in the device (102) by a link including a keyword (402), ii) checking means (603) for checking the contents of the object (403) received, the means producing a checking result, and iii) entry means (605) responsive to the checking means, adapted to allow entry, if the checking result shows that the ticket data object (403) corresponds to a valid ticket (300), and/or forbid entry in the opposite case.

23. A system according to claim 22,

characterised in that

the ticket (300) includes an XML frame (401) and a ticket data object (403).

24. An electronic ticket (300),

characterised in that

the ticket includes

user information (301),

ticket application information (302), and

a ticket object (303) further including a ticket data object (403), the electronic ticket (300) particularly for use in a device and/or system according to any one of the claims 1 to 23.

25. An electronic ticket (300) according to claim 24,

wherein the ticket object (303) further includes a keyword linking the ticket data object (403) to the electronic ticket (300).

26. An electronic ticket (300) according to claim 24 or 25,

wherein the ticket data object (403) is embedded into a frame (401).

27. An electronic ticket (300) according to claim 26,

wherein said frame (401) is an XML frame.

28. An electronic ticket (300) according to any one of claims 24-27,

characterised in that

the ticket (300) further includes a promotional object or an external reference thereto.

29. A ticket according to claim 28,

characterised in that

said promotional object is a ringing tone or an icon.

30. A modular electronic ticket (350)

characterised in that

the modular electronic ticket (350) includes an XLM document divided into several XML parts, the parts further including

user information (301), and

individual tickets (300A, 300B, 300C) according to any one of the claims 24-29, the individual tickets (300A, 300B, 300C) including

user information (301A, 301B, 301C), and

ticket application information (302A, 302B, 302C), the ticket application information (302A, 302B, 302C) including a part for a ticket object (303A, 303B, 303C) with a link (404A, 404B, 404C) including a keyword (402A, 402B, 402C) to a ticket data object (403A, 403B, 403C), the ticket data object (403A, 403B, 403C) being presented by a device (102) when the ticket (300A, 300B, 300C) is to be used.

31. Means for performing an operation on an electronic ticket (300A, 300B, 300C) according to any one of the claims 24-30, the electronic ticket including at least one XML based documents whose model includes user information that derives through XLM schemas from a basic user information (301) type, several of these tickets (300A, 300B, 300C) being delivered together using the stucture provided by the modular ticket (350).