GB2475837A

GB2475837A - Electronic ticketing using mobile devices

Info

Publication number: GB2475837A
Application number: GB0920888A
Authority: GB
Inventors: Michael Kowalzik; Thorsten Trapp; Carsten Pohl
Original assignee: Tyntec Ltd
Current assignee: Tyntec Ltd
Priority date: 2009-11-30
Filing date: 2009-11-30
Publication date: 2011-06-08
Also published as: GB0920888D0

Abstract

A system and method for electronic ticketing of goods or services offered by a service provider. The method comprises: storing ticket data associated to a ticket representative of the goods or service and sending, to a mobile device, a message indicative that the ticket is available. The message includes a link to a web server which generates graphics data comprising a graphics vector associated to the ticket and sends the graphics data to the mobile device. The message sent to the mobile device is preferably one of an SMS, email or instant message. The exchange of data between the web server and the mobile device is similar to WAP push. The method may include gathering information about the mobile device, such as the display capability and generating the graphics data based on the gathered information. When the message is received at the mobile device a browser may be opened with a connection to the web server. The present invention does not require that image or graphics data is stored at the web server and ensures that the graphics data is compatible with the mobile device.

Description

Title: A method and system for ticketing of goods and services

Cross-Reference to Related Applications

[0001] None

Field of the Invention

[0002] The field of the invention relates to a method and system for ticketing. In particular, the invention relates to a method and apparatus for mobile ticketing of goods or services offered by a service provider as well as the delivery of coupons associated to goods or services.

Background of the Tnvention

[0003] With the development of electronic communications, electronic services have been widely developed. Electronic commerce is one example of these electronic services. Mobile ticketing or electronic ticket services allows a customer to purchase goods or services using a mobile device and receive a ticket or a proof of purchase on the mobile device. The goods or services may be a railway ticket, an airline ticket or a concert ticket, etc.. The mobile ticketing offers cost reductions as the need for printing a paper ticket disappears, whilst providing the customer with a convenient way to purchase the ticket. The customer usually always carries his or her mobile device, thereby reducing the risks of loss of the ticket. The mobile ticketing further helps providing ubiquitous services, as the customer can be reached everywhere as long as mobile data communications are supported on a mobile communications network. The term "ticketing" as used herein refers to the generation and delivery of the generated ticket or coupons associated with the purchased goods or services.

[0004] Patent application GB236 1570 teaches a method of operating a ticketing system. A reservation centre generates data representing a ticket which is broadcast via a mobile communications network to a mobile station. The data from the mobile station can then be used to verify the transaction e.g. via a reader linked to a reservations computer. The ticket data can be sent in the form of a text e.g. SMS message or in browser readable format and is preferably in machine readable code. Preferably, the reader is an optical bar or pin code reader.

[0005] Different methods are used for the display of the tickets or coupons on the mobile phone. One method is the delivery of a barcode, in which data representative of the transaction are generated upon the purchase of the ticket and sent as a barcode to the mobile device of the user. The barcode is later used as the ticket and for authentication purposes.

[0006] The variety of mobile devices available on the market implies a variety of functions, display capabilities and communication protocols. For example, some mobile devices are capable of handling multimedia messages whilst other mobile devices may handle text only. This can be problematic for ticketing. In particular, ticket delivery, including the delivery of the barcode, may fail should the mobile device not be able to handle the required delivery format of the generated ticket.

[0007] The International Patent Publication WO 2004/027662 discloses a system and method for sending optimised messages containing barcode information to mobile devices. A message processor means generates message data comprising a coupon. A message optimiser means generates an optimised message responsive to the message data and the capabilities of the mobile device. The capabilities of the mobile device comprise device attribute associated with a mobile device type, and are stored in a database means. The optimised message is transmitted to the mobile device. For basic mobile devices, simple text message including barcode number and associated text will be delivered. Otherwise, subject to the mobile device supporting the required display dimensions and colour depth, a barcode image, picture, and/or multimedia content will be delivered. This system requires the generation of the barcode upon the transaction and the storage of the barcode in a database for later sending.

[0008] There therefore remains a need for a system which allows for greater flexibility for the sending of ticket or coupon.

[0009] There is further a need for a system and method capable of handling different mobile device capabilities and frmnctionalities.

Summary of the Tnvention

[0010] A method for mobile ticketing of goods or services offered by a service provider is disclosed. The method comprises storing ticket data associated with a ticket representative of the goods or services. The method further comprises sending, to a mobile device, a message indicative that the ticket is available. The message comprises a link to a web server.

Thereafter the method comprises generating graphics data associated to the ticket and comprising a graphics vector and sending the graphics data to the mobile device.

[0011] The term "ticket data" in this disclosure is intended to encompass tickets, coupons or vouchers sent from the service provider to the customer on purchase.

[0012] The step of sending a message comprises sending of a SMS message, an email or an instant message in one aspect of the invention [0013] A html page which references downloadable graphics data may be sent to a customer purchasing the goods or services.

[0014] In an aspect of the invention, the method further comprises gathering information about the mobile device and generating the graphics data using the information about the mobile device. The information about the mobile device includes, but is not limited to, one or more of an identity of the mobile device, a display capability of the mobile device, an operating system and a type of browser running on the mobile device. The browser may be for example a web browser, a WAP browser, or using Flash technology.

[0015] The method comprises further opening the browser on the mobile device upon reception of the message, and opening a connection to the web server. The browser is adapted to fetch the graphics data and to display the graphics data on a mobile device display.

[0016] The disclosure also teaches a system for mobile ticketing of goods or services offered by a service provider which comprises a database adapted to store ticket data associated to the goods or services offered by the service provider, a sending device adapted to send, to a customer mobile device, a message indicative that the ticket is available, the message comprising a link to a web server. The web server is adapted to generate graphics data associated to the ticket and to send, to the mobile device, the graphics data to be displayed on the mobile device.

[0017] The sending means are adapted to send a SMS message, an email or an instant message.

[0018] The web server is adapted to provide a html code which references the graphics data. The web server is adapted to gather information about the mobile device and to generate the graphics data based on said information. The information about the mobile device may include, but is not limited to, one or more of an identity of client device, display capability of the client device, an operating system and a type of browser running on the client device.

[0019] A communications provider may manage a system for mobile ticketing. The service providers offering the goods and the services may subscribe to the ticketing system.

The service provider generates the ticket data when the customer purchases the goods or services or when the service provider wishes to send data associated to the goods or services.

The ticket data are sent to the communications provider which manages the database in which the ticket data are stored. The ticketing process is handled by the communications provider which runs the web server that generates the graphics data. The customer needs a mobile device having a display for the display of the graphics data, and a browser. The browser is adapted to open a connection to the web server upon reception of the message. The browser is adapted to fetch the graphics data and to display the graphics data on a client device display.

Description of the Figures

Fig. 1 shows a system for ticketing according to the invention.

Fig. 2 shows a workflow for the receipt of ticket including a barcode according to the invention.

Detailed Description of the Invention

[0020] For a complete understanding of what is taught and the advantages thereof, reference is now made to the following detailed description taken in conjunction with the Figures.

[0021] It should be appreciated that the various aspects of the disclosed method and system for the ticketing of goods and services discussed herein are merely illustrative of the specific ways to make and use of the method and system for the ticketing of the goods and services and do not therefore limit the scope of what is disclosed when taken into consideration with the claims and the following detailed description. It will also be appreciated that features from one embodiment of the disclosed system and method may be combined with features from another embodiment of the disclosed method and system.

[0022] Figure 1 shows a system for ticketing according to one aspect of the disclosure.

[0023] A service provider 5 offers electronic goods or services 7. The electronic goods or services 7 may be railway ticketing, museum tickets, or any kind of mobile and electronic ticket, coupon or voucher services. Whenever a customer 20 buys one of the electronics goods or services 7, the customer may receive a ticket 15 corresponding to a transaction on his or her mobile device 200. The ticket 15 may be not just a conventional ticket but also a coupon, a voucher or any kind of graphics data. The graphics data may comprise a barcode. The ticket is the proof of the transaction and may be used for later authentication, for example.

[0024] The mobile device 200 may be any kind of mobile telephone, computer, netbook, PDA, etc and has a variety of capabilities and communication protocols. The mobile device has a browser 230. The browser 230 could be any browser 230 available, such as iPhone, Safari Opera, etc. The browser may be a web browser or a WAP browser, or use flash technology.

[0025] The service provider 5 subscribes to a ticketing system or platform 100 maintained by a ticketing provider 10 for the delivery of the ticket 15.

[0026] The ticketing system 100 comprises a database 110 in which ticket data 50 corresponding to the electronics goods or services 7 purchased by the customer 20 are stored.

The ticket data 50 is preferably generated by the service provider 5 when the customer 20 purchases or subscribes to one of the electronics goods or services 7. The ticket data 50 may comprise information about the customer 20, as well as information about the transaction and the electronic goods or services 7 to which the customer 20 has subscribed.

[0027] The ticketing system 100 also comprises a web server 130 maintained by the ticketing provider 10. The web server 130 is adapted to generate graphics data to be sent to the customer 20. The web server 130 comprises text and graphics files 140, in graphical format such as, but not limited to, the JPEG or PNG format. The web server 130 is adapted to retrieve device information 210 from the mobile device 200. As an example, the browser 230 of the mobile device 200 may transmit a user agent comprising the identity of the mobile device 200. An example of a user agent is: "User-Agent: NokiaN73-1/2.0626.0.0.2 S60/3.0 Profile/MIDP-2.0 ConfigurationlCLDC-1.1 UP.Linki'6.3.0.0.0 X-Wap-Profile: "httpJ/ids.nokia.cçn/uaprof7NiN73 [0028] Information about the mobile device 200 may be looked-up in a profile database 220 which stores properties of known mobile devices 200, using the user agent of the mobile device 200. The profile database 220 may contain information in XML format about capabilities and features of mobile devices, such as the resolution, capacity and colour depth of the screen of the mobile device. The profile database 220 is freely available on the Internet or can be purchased from a special provider.

[0029] A workflow for the receipt of a ticket comprising a barcode according to the invention is described with reference to figure 2.

[0030] The service provider 5, such as but not limited to, a railway company, airline or ticket agency subscribes to the mobile ticketing service provided by the ticketing provider 10.

It should be understood that the ticketing provider 10 manages the ticketing process in this

aspect of the disclosure.

[0031] At step 1000 the customer 20 purchases the electronics goods or services 7 from the service provider 5. Different methods can be contemplated for the transaction (purchase) of the ticket including but not limited to placing an order online via a registered internet or web page, via text messaging, a phone call, a mobile application page using different communications protocols. Alternately, the service provider S may also wish to send a coupon, voucher or any other graphics data to the customer 20.

[0032] When the customer purchases the electronics goods and/or services 7, the ticket data is generated at step 1010. The ticket data is preferably generated by the service provider 5. The ticket data 15 may comprise, but is not limited to, a name of the customer, a type of the ticket and a date of purchase. Other information may be included in the ticket data 15.

[0033] The ticket data 15 is generated in one aspect in the form of a text file using a descriptive language such as the XML language. It should be understood that other data formats could be contemplated. The generated ticket data 15 is sent to the ticketing provider for storage into the database 110 at step 1020.

[0034] At step 1030 the customer 20 is informed that the ticket is available for ticket delivery by the ticketing provider 10. The ticketing provider 10 can send a message 310 to the customer mobile device 200 with a link to the web-server 130 maintained by the ticketing provider 10. The message 310 is sent in the form of a SMS message via an SMS platform 300. The SMS platform 300 may be provided by the ticketing provider 10 or by any other communications provider. Any other form of formats for the message 310 may be contemplated. Any other form of transport for the message 310 may be contemplated, such as instant messaging or email messaging.

[0035] It is noted that the customer 20 does not need to be informed immediately of the storage of the ticket data 15 in the database 110. This could happen at a later stage. It is possible, for example, that the customer 20 is only notified of part of the ticket data 15 initially (i.e. that the ticket has been purchased or that the voucher or coupon is ready for delivery) and further parts of the ticket data 15 (e.g. seat number of an airline) are notified at a later date.

[0036] The customer 20 clicks on the link on the display of the mobile device 200. The browser 230 opens (if the browser 230 is not already open). The browser 230 could be any browser 230 available, such as iPhone, Opera, etc. The browser may be a web browser or a WAP browser. The browser opens an HTTP connection 320 or a HTTPS connection to the web server 130 at step 1040. The HTTP/HTTPS connection 320 can be opened via WLAN, 3G, EDGE, or any other suitable communication protocol.

[0037] The browser 230 transmits the user agent of the mobile device 200 comprising the identity of the mobile device 200. Other information such as the operating system and type of browser 230 could be provided as well. The user agent is transmitted by the browser 230 when opening the HTTP/HTTPS connection to the web server 130.

[0038] The device information 210 about the mobile device capabilities can be retrieved by the web server 130 once the identity of the mobile device 200 is known (step 1050). The capabilities may include the functionality of the mobile device 200, the communication protocols, the type and capabilities of a display 240. Among other, the display resolution, picture messaging protocols. It is known that different mobile devices 200 have varying capabilities, from text only to multimedia capabilities.

[0039] The device information 210 about the mobile device capabilities can be retrieved from the Internet, for example using a freely available database 220 or purchased from a special database.

[0040] The web server 130 generates graphics data 330 corresponding to the ticket based on the ticket data 15 and based on the information about the mobile device 200 gathered at step 1060. In particular, the graphics data 330 for the ticket may be generated on the fly as a graphics data using the device information 210 about the mobile device. The graphics data may comprise text and graphics files, in graphical format such as the JPEG or PNG format.

The graphics data 330 is sent to the mobile device 200. Preferably the graphics data comprises a graphics vector, a barcode, a coupon. Preferably a HTML code is sent to the browser l30including a reference to the graphics data, at step 1060.

[0041] Next, the browser 230 of the mobile device 200 fetches the received graphics data and displays the graphics data 330 on the display 240 of the mobile device 200 at step 1070.

[0042] Additional information or data may be added to the graphics data 330 or ticket for delivery to the customer.

[0043] The ticketing process is transparent to the user.

[0044] This ticketing process allows the generation of the graphics data 330 including the barcode at a point in time at which the capabilities of the mobile device 200 are known. There is no need to generate an image upon the transaction with the ticketing provider 10. This allows for greater flexibility and less cost as no image is generated beforehand. The systems and method of the prior art required a generation of a high resolution image which needed to be downgraded if the mobile device 200 could not handle graphics format.

[0045] It will be clear from the description that the graphics data 330 is generated by the ticketing provider 10. Any communication protocol, graphics format and display standard can be used, depending on the service provider requirements and on the capabilities of the mobile device 200.

[0046] The above description of the illustrated embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Whilst specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention as those skilled in the relevant art will recognise. Accordingly it is not intended that the scope of the invention in any way be limited by the above description, but instead be determined entirely by reference to the claims.

[0047] List of reference numbers: Goods/Services Provider 7 Electronics goods or services Ticketing provider Customer Ticket data Ticketing system 110 Database Web server Text and graphics files Mobile device 210 Device information 220 Device database 230 Browser 240 Display 300 SMS Platform 310 SMS message 320 HTTP connection 330 Bar Code