AU2017210602A1 - Transport transaction method and system - Google Patents

Abstract

TRANSPORT TRANSACTION METHOD AND SYSTEM Abstract Disclosed herein are a transport transaction method and system. The method comprises: registering a set of scheduled services, each scheduled service having an associated passenger manifest containing passenger details of users registered with that service; registering a user with a username; receiving a booking from the registered user in relation to a selected one of the scheduled services, the booking including payment; receiving authentication information from an authentication device associated with the selected scheduled service, the authentication information provided by the user; comparing the authentication information with passenger details contained in the passenger manifest associated with the selected scheduled service in order to authenticate the user as a valid passenger; and on authenticating the user as a valid passenger, issuing a positive notification. - 3/12 cyo 00c coc cvo a)a a) (n coo m CDo 0 rl0 o N zo

Description

TRANSPORT TRANSACTI ON METHOD AND SYSTEM Related Application [0001] The present application is related to Australian Provisional Patent Application No. 2016903104 titled “Transport Transaction Method And System” and filed 8 August 2016 in the name of Niftie IP Services Pty Ltd, the entire content of which is incorporated by reference as if fully set forth herein.

Technical Field [0002] The present disclosure relates to a transport transaction method and system and, in particular, to a transaction system that is cashless and card-less.

Background [0003] Public transport is a broad descriptor for various modes of transport that enable people to travel from a starting point to a destination. As such, public transport may be provided by government or private entities. Such modes of transport include buses, taxis, trains, ferries, trams, and light rail.

[0004] While some public transport services are ostensibly free to users, such as free bus or tram services within a central business district, those services are typically paid for by a local government. More commonly, a user of a public transport service pays to use the service. In the most common arrangement, a user pays per trip by purchasing a ticket in advance or at the beginning of the trip, such as occurs for train and bus travel, or at the end of the trip, such as for metered taxi rides.

[0005] In recent times, cashless payment systems have been introduced, such as the Oyster, Opal, and Myki systems that require users to purchase pre-paid tickets in order to access public transport services. A user of such a cashless payment system swipes or taps a pre-paid ticket at a predefined access point in order to gain access to a station or on boarding a bus or tram. The user then swipes or taps the pre-paid ticket at a corresponding pre-paid access point at a destination station or on disembarking the bus or tram. The access points are coupled to a central server that determines the appropriate charge for the trip, whereupon the appropriate charge is deducted from the pre-paid ticket or a corresponding account.

[0006] The above-noted systems require a user to either carry cash to pay the requisite fare or a pre-paid approved card for the relevant transport system. People often lose their wallets or purses, including cash and pre-paid transport cards, and are then presented with difficulties to travel to their destinations.

[0007] Thus, a need exists for an improved transport transaction method and system. Summary [0008] The present disclosure relates to a transport transaction method and system in which a user makes an advance payment in relation to a transport service and the transport service authenticates the user as a valid traveller on boarding the service.

[0009] A first aspect of the present disclosure provides a transport transaction method comprising: registering a set of scheduled services, each scheduled service having an associated passenger manifest containing passenger details of users registered with that service; registering a user with a username; receiving a booking from the registered user in relation to a selected one of the scheduled services, the booking including payment; receiving authentication information from an authentication device associated with the selected scheduled service, the authentication information provided by the user; comparing the authentication information with passenger details contained in the passenger manifest associated with the selected scheduled service in order to authenticate the user as a valid passenger; and on authenticating the user as a valid passenger, issuing a positive notification.

[0010] A second aspect of the present disclosure provides a transport transaction system comprising: a server coupled to a communications network, the server including: a processor; a memory for storing: personal details associated with a set of registered users, the personal details including at least a name and login identifier; a set of scheduled services, each scheduled service having an associated timetable and route; and a passenger manifest associated with each scheduled service; and computer program code relating to a transport transaction application, the application including instructions that, when executed on the processor, perform the steps of: receiving passenger details from a registered user in relation to a selected one of the scheduled services, the passenger details including at least the name and login identifier for the user; adding the received passenger details to the passenger manifest associated with the selected service; matching authentication information against the passenger manifest to authenticate the user; transmitting a positive notification, when the authentication information matches the passenger manifest; and transmitting a negative notification, when the authentication information does not match the passenger manifest.

[0011] According to another aspect, the present disclosure provides an apparatus for implementing any one of the aforementioned methods.

[0012] According to another aspect, the present disclosure provides a computer program product including a computer readable medium having recorded thereon a computer program for implementing any one of the methods described above.

[0013] Other aspects of the present disclosure are also provided.

Brief Description of the Drawings [0014] One or more embodiments of the present disclosure will now be described by way of specific example(s) with reference to the accompanying drawings, in which: [0015] Fig. 1 is a schematic representation of a tablet computing device adapted to implement an authentication device in relation to a transport system; [0016] Fig. 2 is a flow diagram illustrating a method for authenticating a user of a transport system in accordance with the present disclosure; [0017] Fig. 3 is a schematic representation of a system on which one or more embodiments of the present disclosure may be practised; [0018] Fig. 4 is a schematic block diagram representation of a system that includes a general purpose computer on which one or more embodiments of the present disclosure may be practised; [0019] Fig. 5 is a schematic block diagram representation of a system that includes a general smartphone on which one or more embodiments of the present disclosure may be practised; [0020] Fig. 6 is a flow diagram illustrating a transport payment method in accordance with the present disclosure; [0021] Fig. 7 is a screenshot of a sample welcome screen presented on a display of the authentication device; [0022] Fig. 8 is a screenshot of a passenger manifest display screen presented on a display of the authentication device; [0023] Fig. 8 is a screenshot of a PIN entry screen; [0024] Fig. 10 is an example of an approval screen; [0025] Fig. 11 is an example of a rejection screen; and [0026] Fig. 12 is an illustration of relationships among a set of tables that may be used to implement the management system.

Detailed Description [0027] Method steps or features in the accompanying drawings that have the same reference numerals are to be considered to have the same function(s) or operation(s), unless the contrary intention is expressed or implied.

[0028] The present disclosure provides a transport transaction method and system. In particular, the method and system of the present disclosure enable a user to pre-register for a scheduled service. Such a service may be a one-off service relating to a particular event or may be a regular commuter service. On accessing the scheduled service, the system authenticates the user against a list of pre-registered passengers, using an appropriate authentication device.

[0029] Authentication may be based on, for example, a personal identification number (PIN), a password, biometric identification, or a combination thereof. Suitable biometric identification may include, for example, voice recognition, facial recognition, fingerprint scanning, retina scanning, or any combination thereof. The authentication device may be implemented using a computing device, such as a smartphone, computing tablet, phablet, or the like, or a dedicated input terminal. Thus, the system authenticates a user as a valid passenger without requiring payment or use of a card at the point of embarkation or on the transport means itself.

[0030] Fig. 3 is a schematic representation of a system 300 on which embodiments of the present disclosure may be practised. The system 300 includes a centralised management system 301 that includes a server 330 coupled to a storage medium 370. The storage medium 370 optionally stores data relating to past transport services and bookings managed by the management system 301.

[0031] The server 330 includes a services database 332, which stores information about one or more transport services for which the management system 301 will authenticate passengers. The server 330 also includes a customer database 334, which stores a customer profile for each customer registered with the management system 330. Each customer profile may include, for example, name and contact details and identifying information for that customer. The customer profile optionally includes further details, such as loyalty points, seating preferences, service preferences and the like. Service preferences may include, for example, times and stops for regular commuter services managed by the management system 301.

[0032] The server 330 further includes an accounts module 336, which manages transfers of payments to and from the management system 301. Each of the services database 332, customer database 334, and accounts module 336 is coupled to a bus 338, which enables information to be exchanged among those modules.

[0033] The server 330 is coupled to a communications network 305. The communications network 305 may be implemented using one or more wired or wireless transmission links and may include, for example, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof.

[0034] In the example of Fig. 3, the management system 301 manages bookings for services relating to a commuter train service 380 and an event specific bus shuttle 390. The services database 332 stores timetable and/or route information for the train service 380 and the bus shuttle 390.

[0035] I n one example, the bus shuttle 390 relates to a Saturday night shuttle associated with a music concert to be held at Sydney Olympic Park on 3 September 2016. The shuttle is scheduled to operate between the Sydney CBD and Sydney Olympic Park. A user 310 has purchased a ticket to the music concert and now needs transport to and from the Sydney Olympic Park venue. The user 310 accesses a computing device 320, such as a smartphone, to communicate via the communications network 305 with the management system 301. In one arrangement, the user 310 downloads a software application (“app”) associated with the management system 301, whereby the downloaded software application executes on a processor of the smartphone 320. In another arrangement, the user utilises a web browser to access content from a website hosted by or in association with the management system 301.

[0036] The app or browser provides a user interface to the display of the smartphone 320, such that the user 310 navigates the user interface to identify transport services associated with the required music event.

[0037] The user 310 then purchases a return ticket on the bus shuttle 390. The ticket may relate to a nominated time or time range or may simply relate to the event, depending on how many services are scheduled to run. The user 310 arranges payment of the ticket, such as via a payment gateway using a credit card, direct funds transfer, PayPal, or other electronic payment means. In one implementation, the user 310 also provides an identifying input to be used in validating the user when the user boards the bus shuttle 390. Such identifying input may be, for example, a PIN, password, or biometric information, such as a captured facial image, fingerprint, voice sample, retina scan, or the like. In another implementation, the transaction management system uses identifying details provided by the user when registering with the system. Details provided by the user are stored in the customer database 334 and the services database 332.

[0038] In one implementation, the services database 332 stores a passenger manifest for each scheduled service managed by the management system 301. In this example, the services database 332 stores a passenger manifest listing all customers that have registered for the bus shuttle 390 in relation to Saturday night’s music concert.

[0039] Table 1 is an example of a passenger manifest for Coach 1 in relation to the scheduled service for Saturday night on 3 September 2016. In this example, the user 310 corresponds to the passenger named Kerry Auld, who is to board the bus, Coach 1, at

Stop 4 along the route. Details of the passenger manifest may be derived from one or more records stored in the services database 332 or the external storage medium 370. Fig. 12 is an illustration of relationships among a set of tables that may be used to implement the management system 301. The set of tables may include, for example, tables for users, purchased tickets, excluded dates, events, buses, buses events, locations, tickets, and pricing.

Table 1 [0040] On the night of Saturday, 3 September 2016, the user 310 attends a nominated bus stop in the Sydney CBD, in this case Stop 4, to catch the scheduled shuttle bus 390 to the music concert. Rather than having to pay on boarding the bus or presenting a prepurchased ticket or other card, the user 310 boards the bus and accesses an authentication device located on the bus.

[0041] The authentication device includes a display for presenting a user interface to capture authentication information from the user 310. Fig. 7 is a screenshot of a sample welcome screen 700 presented on a display of the authentication device. In the example of Fig. 7, the welcome screen includes a dropdown box 710 that enables a user to select a scheduled service. Fig. 8 is a screenshot of a passenger manifest display screen 800 presented on a display of the authentication device to the user 310 on boarding the scheduled bus service. The passenger manifest display screen 800 includes an array of avatars corresponding to the passengers registered for that bus service, wherein the registered passengers correspond to those in the manifest of Table 1. As can be readily seen, where the passenger manifest records that a passenger has an associated image, that image is displayed on the screen 800.

[0042] The user 310 boards the bus, selects the avatar 810 corresponding to Kerry A, being the alias for the nominated user and provides the authentication information. In this case, passenger Kerry provides a PIN as authentication information, such as via the keypad shown in the PIN entry screen 900 of Fig. 9. In one implementation, the authentication device sends the authentication information via a wireless communication link to the server 330 to be compared against stored identifying information for the nominated user. In another implementation, the authentication device uses identifying information stored in a passenger manifest pushed from the server 330 to the authentication device.

[0043] The server 330 or authentication device compares the received authentication information against the initial identifying information provided by the user when booking the shuttle service. If the authentication information and identifying information match, the authentication device issues a notification, such as a written message and/or positive audible alert, to indicate that the user 310 has been authenticated and the user is then able to board the bus. Fig. 10 is an example of an approval screen 1000, in which the user receives a notification 1010 in the form of a message with a tick. If the user enters an incorrect PIN, the authentication device issues a notification, such as a written message and/or negative audible alert. Fig. 11 is an example of a rejection screen 1100, in which the user receives a notification 1110 in the form of a message with a cross with instructions to try again. In one embodiment, a passenger manifest relating to the scheduled bus service 390 is transmitted from the services database 332 to the authentication device on the bus shuttle 390.

[0044] Fig. 6 is a flow diagram illustrating a transport transaction method 600 in accordance with the present disclosure. The method 600 begins at a Start step 605 and proceeds to step 610, which registers a set of scheduled transport services with a transport management system 301. As described above in relation to Fig. 3, the scheduled transport services may be regularly scheduled commuter transport services or one-off, event specific services. For each registered transport service, the transport management system 301 generates a schedule of services and each scheduled service is associated with a passenger manifest stores in the services database 332. The passenger manifest for a scheduled service provides details of each passenger registered with that scheduled service.

[0045] Control passes from step 610 to 615, which publishes all available transport services registered with the transport management system 301. In one arrangement, publishing the services makes the services available on a website associated with the transport management system 301. In another arrangement, the server 330 pushes the transport services information to software applications installed on user computing devices, such as the smartphone 320 of the user 310. Published transport services may be published with associated route and timetable information.

[0046] I n step 620, a user, such as the user 310, registers with the transport management system 301. Such registration may be performed by the user 310 accessing the smartphone 320 to browse a website associated with the server 330 or by using a software application associated with the transport management system 301. The transport management system 301 receives personal information from the user 310 and stores the information in the customer database 334 as a user profile associated with that particular user. The personal information includes one or more identifying features, such as PIN, Password, voice sample, facial recognition image, retina scan, fingerprint, or any combination thereof.

[0047] In a following step 625, the transport management system 301 receives user input from the smartphone 320 in relation to a scheduled service, selected from the set of services provided in step 610, for which the user 310 wants to purchase a ticket. The transport management system 301 records relevant details from the user, including details of the selected service and relevant payment details. Step 630 stores the user as a passenger on the passenger manifest associated with the selected transport service.

The passenger manifest is pushed to/pulied from the server 301 using a store/retrieve Application Programming Interface (API) method to a software application executing on the authentication device, located on board the vehicle. The manifest displays within the application the current service and route information, as well as passengers’ aliases and profile images.

[0048] At a later time corresponding to the departure time of the selected scheduled service, the user 310 boards the transport vehicle, such as the bus 390 and provides authentication information to an authentication device located on the transport vehicle. The authentication information includes a user name or alias associated with the user 310 and at least one other identification detail.

[0049] Fig. 1 is a schematic representation of a computing device 1 adapted to function as an authentication device on a vehicle. In the example of Fig. 1, the computing device is implemented using a tablet computing device adapted to be mounted on a transport vehicle, such as a bus, train, ferry, coach, tram, light rail carriage, and the like. In one implementation, the tablet computing device 1 includes a power supply in the form of a battery (not shown), such as a rechargeable lithium-ion, lithium-polymer, or nickel cadmium battery. Alternatively, the tablet computing device 1 is coupled to an external power supply from the transport vehicle.

[0050] Mounting of the tablet computing device 1 may be implemented in any number of arrangements, such as through the use of one or more brackets, clamps, clips, cases, or other suitable mounting devices.

[0051] The tablet computing device 1 optionally includes a microphone 4 adapted to receive an audio input, when the tablet computing device 1 functions to perform voice recognition. The tablet computing device 1 optionally includes a biometric scanning device 5, adapted to scan one or more biometric features of a user, when the tablet computing device 1 is adapted to perform biometric scanning. For example, the biometric scanning device 4 may be implemented to scan one or more of fingerprints, retinas, or facial features. Alternatively, a camera 3 is used to capture an image of a face of a user for user. Image recognition software is then applied to the captured image to compare features of the captured image against a stored image of the user.

[0052] The tablet computing device 1 includes a processor (not shown), on which executes a software application (“app”). The app includes computer program code to perform the instructions of authenticating a user, through receiving an authentication input and then comparing the received authentication input against identification information associated with a pre-registered passenger manifest for a nominated service. In one implementation, the tablet computing device 1 includes a wireless transceiver, such as a 3G or 4G transceiver to communicate wirelessly with a remote server on which is stored the passenger manifest. In another implementation, a remote server pushes a passenger manifest to the tablet computing device 1. The app then issues an indication as to whether or not the user is authenticated as a valid passenger.

[0053] Returning to Fig. 6, control passes from step 635 to decision step 640, which determines whether the authentication information presented by the user matches the corresponding identifying information stored in relation to the passenger manifest associated with the selected scheduled service. If the authentication information does not match, No, then control returns to step 635 for the user to re-enter the identifying information. However, if at step 640 the authentication information does match, Yes, control passes from step 640 to step 645, which issues a positive notification message, such as a beep or green tick on a display of the authentication device. Control passes from step 645 to an End step 650 and the method 600 terminates.

[0054] Fig. 2 is a flow diagram illustrating a method 200 of authenticating a user for a particular service. The method 200 begins at a Start step 6 and proceeds to step 7, in which the user provides a user input to an authentication device, such as the tablet computing device 1 of Fig. 1. Control passes to decision step 8, which determines whether or not the user is an authorised user of the particular service. As described above, authentication of a user may be performed by comparing the user authentication input, such as a PIN, password, or biometric parameter, against registered identifying information on a passenger manifest.

[0055] If step 8 determines that the user is not authorised for the particular service, No, control passes to step 9, which issues a negative notification alert. The negative notification alert may be, for example, an audible alert, a visual alert, or a combination thereof. An audible alert may be a buzzer, beep, or siren. A visual alert may be a red cross or red background displayed on a display of the tablet computing device 1. Control returns from step 9 to step 7 to receive further user input.

[0056] Returning to step 8, if the user is authorised, Yes, control passes to step 10, which issues a positive notification alert. The positive notification alert may be, for example, an audible alert, a visual alert, or a combination thereof. An audible alert may be a buzzer, beep, or siren. A visual alert may be a green tick or green background displayed on a display of the tablet computing device 1. Control passes from step 10 to step 11, which allows entry of the user to the vehicle.

[0057] The transport payment system of the present disclosure may be practised using a computing device, such as a general purpose computer or computer server. Fig. 4 is a schematic block diagram of a system 400 that includes a general purpose computer 410. The general purpose computer 410 includes a plurality of components, including: a processor 412, a memory 414, a storage medium 416, input/output (I/O) interfaces 420, and input/output (I/O) ports 422. Components of the general purpose computer 410 generally communicate using one or more buses 448.

[0058] The memory 414 may be implemented using Random Access Memory (RAM), Read Only Memory (ROM), or a combination thereof. The storage medium 416 may be implemented as one or more of a hard disk drive, a solid state “flash” drive, an optical disk drive, or other storage means. The storage medium 416 may be utilised to store one or more computer programs, including an operating system, software applications, and data. In one mode of operation, instructions from one or more computer programs stored in the storage medium 416 are loaded into the memory 414 via the bus 448. Instructions loaded into the memory 414 are then made available via the bus 448 or other means for execution by the processor 412 to implement a mode of operation in accordance with the executed instructions.

[0059] One or more peripheral devices may be coupled to the general purpose computer 410 via the I/O ports 422. In the example of Fig. 4, the general purpose computer 410 is coupled to each of a speaker 424, a camera 426, a display device 430, an input device 432, a printer 434, and an external storage medium 436. The speaker 424 may be implemented using one or more speakers, such as in a stereo or surround sound system. In the example in which the general purpose computer 410 is utilised to implement the authentication device 1 of Fig. 1, one or more peripheral devices may relate to biometric scanners connected to the I/O ports 422.

[0060] The camera 426 may be a webcam, or other still or video digital camera, and may download and upload information to and from the general purpose computer 410 via the I/O ports 422, dependent upon the particular implementation. For example, images recorded by the camera 426 may be uploaded to the storage medium 416 of the general purpose computer 410. Similarly, images stored on the storage medium 416 may be downloaded to a memory or storage medium of the camera 426. The camera 426 may include a lens system, a sensor unit, and a recording medium.

[0061] The display device 430 may be a computer monitor, such as a cathode ray tube screen, plasma screen, or liquid crystal display (LCD) screen. The display 430 may receive information from the computer 410 in a conventional manner, wherein the information is presented on the display device 430 for viewing by a user. The display device 430 may optionally be implemented using a touch screen to enable a user to provide input to the general purpose computer 410. The touch screen may be, for example, a capacitive touch screen, a resistive touchscreen, a surface acoustic wave touchscreen, or the like.

[0062] The input device 432 may be a keyboard, a mouse, a stylus, drawing tablet, or any combination thereof, for receiving input from a user. The external storage medium 436 may include an external hard disk drive (HDD), an optical drive, a floppy disk drive, a flash drive, or any combination thereof and may be implemented as a single instance or multiple instances of any one or more of those devices. For example, the external storage medium 436 may be implemented as an array of hard disk drives.

[0063] The I/O interfaces 420 facilitate the exchange of information between the general purpose computing device 410 and other computing devices. The I/O interfaces may be implemented using an internal or external modem, an Ethernet connection, or the like, to enable coupling to a transmission medium. In the example of Fig. 4, the I/O interfaces 422 are coupled to a communications network 438 and directly to a computing device 442. The computing device 442 is shown as a personal computer, but may be equally be practised using a smartphone, laptop, or a tablet device. Direct communication between the general purpose computer 410 and the computing device 442 may be implemented using a wireless or wired transmission link.

[0064] The communications network 438 may be implemented using one or more wired or wireless transmission links and may include, for example, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, such as a Public Switch Telephony Network (PSTN), a mobile telephone cellular network, a short message service (SMS) network, or any combination thereof. The general purpose computer 410 is able to communicate via the communications network 438 to other computing devices connected to the communications network 438, such as the mobile telephone handset 444, the touchscreen smartphone 446, the personal computer 440, and the computing device 442.

[0065] One or more instances of the general purpose computer 410 may be utilised to implement a server acting as the server 301 to implement a transport payment system in accordance with the present disclosure. In such an embodiment, the memory 414 and storage 416 are utilised to store data relating to scheduled transport services, fares, registered users, and passenger manifests for the various transport services. Software for implementing the transport payment system is stored in one or both of the memory 414 and storage 416 for execution on the processor 412. The software includes computer program code for implementing method steps in accordance with the method of registering users, receiving bookings, and authenticating users described herein.

[0066] Fig. 5 is a schematic block diagram of a system 500 on which one or more aspects of a transport payment method and system of the present disclosure may be practised. The system 500 includes a portable computing device in the form of a smartphone 510, which may be used by the registered user 310 of the transport payment system 300 in Fig. 3. The smartphone 510 includes a plurality of components, including: a processor 512, a memory 514, a storage medium 516, a battery 518, an antenna 520, a radio frequency (RF) transmitter and receiver 522, a subscriber identity module (SIM) card 524, a speaker 526, an input device 528, a camera 530, a display 532, and a wireless transmitter and receiver 534. Components of the smartphone 510 generally communicate using one or more bus connections 548 or other connections therebetween. The smartphone 510 also includes a wired connection 545 for coupling to a power outlet to recharge the battery 518 or for connection to a computing device, such as the general purpose computer 410 of Fig. 4. The wired connection 545 may include one or more connectors and may be adapted to enable uploading and downloading of content from and to the memory 514 and SIM card 524.

[0067] The smartphone 510 may include many other functional components, such as an audio digital-to-analogue and analogue-to-digital converter and an amplifier, but those components are omitted for the purpose of clarity. However, such components would be readily known and understood by a person skilled in the relevant art.

[0068] The memory 514 may include Random Access Memory (RAM), Read Only Memory (ROM), or a combination thereof. The storage medium 516 may be implemented as one or more of a solid state “flash” drive, a removable storage medium, such as a Secure Digital (SD) or microSD card, or other storage means. The storage medium 516 may be utilised to store one or more computer programs, including an operating system, software applications, and data. In one mode of operation, instructions from one or more computer programs stored in the storage medium 516 are loaded into the memory 514 via the bus 548. Instructions loaded into the memory 514 are then made available via the bus 548 or other means for execution by the processor 512 to implement a mode of operation in accordance with the executed instructions.

[0069] The smartphone 510 also includes an application programming interface (API) module 536, which enables programmers to write software applications to execute on the processor 512. Such applications include a plurality of instructions that may be pre-installed in the memory 514 or downloaded to the memory 514 from an external source, via the RF transmitter and receiver 522 operating in association with the antenna 520 or via the wired connection 545.

[0070] The smartphone 510 further includes a Global Positioning System (GPS) location module 538. The GPS location module 538 is used to determine a geographical position of the smartphone 510, based on GPS satellites, cellular telephone tower triangulation, or a combination thereof. The determined geographical position may then be made available to one or more programs or applications running on the processor 512.

[0071] The wireless transmitter and receiver 534 may be utilised to communicate wirelessly with external peripheral devices via Bluetooth, infrared, or other wireless protocol. In the example of Fig. 5, the smartphone 510 is coupled to each of a printer 540, an external storage medium 544, and a computing device 542. The computing device 542 may be implemented, for example, using the general purpose computer 410 of Fig. 4.

[0072] The camera 526 may include one or more still or video digital cameras adapted to capture and record to the memory 514 or the SIM card 524 still images or video images, or a combination thereof. The camera 526 may include a lens system, a sensor unit, and a recording medium. A user of the smartphone 510 may upload the recorded images to another computer device or peripheral device using the wireless transmitter and receiver 534, the RF transmitter and receiver 522, or the wired connection 545.

[0073] In one example, the display device 532 is implemented using a liquid crystal display (LCD) screen. The display 532 is used to display content to a user of the smartphone 510. The display 532 may optionally be implemented using a touch screen, such as a capacitive touch screen or resistive touchscreen, to enable a user to provide input to the smartphone 510.

[0074] The input device 528 may be a keyboard, a stylus, or microphone, for example, for receiving input from a user. In the case in which the input device 528 is a keyboard, the keyboard may be implemented as an arrangement of physical keys located on the smartphone 510. Alternatively, the keyboard may be a virtual keyboard displayed on the display device 532.

[0075] The SIM card 524 is utilised to store an International Mobile Subscriber Identity (IMSI) and a related key used to identify and authenticate the user on a cellular network to which the user has subscribed. The SIM card 524 is generally a removable card that can be used interchangeably on different smartphone or cellular telephone devices. The SIM card 524 can be used to store contacts associated with the user, including names and telephone numbers. The SIM card 524 can also provide storage for pictures and videos. Alternatively, contacts can be stored on the memory 514.

[0076] The RF transmitter and receiver 522, in association with the antenna 520, enable the exchange of information between the smartphone 510 and other computing devices via a communications network 590. In the example of Fig. 5, RF transmitter and receiver 522 enable the smartphone 510 to communicate via the communications network 590 with a cellular telephone handset 550, a smartphone or tablet device 552, a computing device 554 and the computing device 542. The computing devices 554 and 542 are shown as personal computers, but each may be equally be practised using a smartphone, laptop, or a tablet device.

[0077] The communications network 590 may be implemented using one or more wired or wireless transmission links and may include, for example, a cellular telephony network, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, such as a Public Switch Telephony Network (PSTN), a cellular (mobile) telephone cellular network, a short message service (SMS) network, or any combination thereof. I ndustrial Applicability [0078] The arrangements described are applicable to the transport industry.

[0079] The foregoing describes only some embodiments of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.

[0080] In the context of this specification, the word “comprising” and its associated grammatical constructions mean “including principally but not necessarily solely” or “having” or “including”, and not “consisting only of”. Variations of the word "comprising", such as “comprise” and “comprises” have correspondingly varied meanings.

[0081] As used throughout this specification, unless otherwise specified, the use of ordinal adjectives "first", "second", "third", “fourth”, etc., to describe common or related objects, indicates that reference is being made to different instances of those common or related objects, and is not intended to imply that the objects so described must be provided or positioned in a given order or sequence, either temporally, spatially, in ranking, or in any other manner.

[0082] Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms.

Claims (10)

1. The claims defining the invention are as follows:

   1. A transport transaction method comprising: registering a set of scheduled services, each scheduled service having an associated passenger manifest containing passenger details of users registered with that service; registering a user with a username; receiving a booking from said registered user in relation to a selected one of said scheduled services, said booking including payment; receiving authentication information from an authentication device associated with said selected scheduled service, said authentication information provided by said user; comparing said authentication information with passenger details contained in the passenger manifest associated with the selected scheduled service in order to authenticate said user as a valid passenger; and on authenticating said user as a valid passenger, issuing a positive notification.
2. 2. The method according to claim 1, wherein said authentication device is a computing device with a wireless transceiver adapted to communicate with a remote server via a communications network, said remote server storing service details of said set of scheduled services, including said associated passenger manifests, and personal details of said registered users.
3. 3. The method according to claim 2, wherein said authentication device is one of a tablet computing device, a phablet computing device, and a dedicated hardware terminal.
4. 4. The method according to either one of claims 2 and 3, wherein said wireless transceiver utilises one of 3G or 4G telecommunication protocols.
5. 5. The method according to any one of claims 1 to 4, wherein said authentication information includes a username and at least one of a personal identification number (PIN), a password, biometric identification, or a combination thereof.
6. 6. The method according to claim 4, wherein said authentication information includes biometric information selected from the group consisting of a voice sample, facial recognition image, fingerprint scan, retina scan, or any combination thereof
7. 7. The method according to any one of claims 1 to 6, wherein said passenger details include at least one of a passenger name, alias, image, boarding point, customer identifier, and biometric information.
8. 8. A transport transaction system comprising: a server coupled to a communications network, said server including: a processor; a memory for storing: personal details associated with a set of registered users, said personal details including at least a name and login identifier; a set of scheduled services, each scheduled service having an associated timetable and route; and a passenger manifest associated with each scheduled service; and computer program code relating to a transport transaction application, said application including instructions that, when executed on the processor, perform the steps of: receiving passenger details from a registered user in relation to a selected one of said scheduled services, said passenger details including at least said name and login identifier for said user; adding said received passenger details to the passenger manifest associated with said selected service; matching authentication information against said passenger manifest to authenticate said user; transmitting a positive notification, when said authentication information matches said passenger manifest; and transmitting a negative notification, when said authentication information does not match said passenger manifest.
9. 9. The system according to claim 8, wherein said login identifier is at least one of a personal identification number (PIN), a password, biometric identification, or a combination thereof.
10. 10. The system according to either one of claims 8 and 9, further comprising: an authentication device positioned on said selected scheduled service, wherein said authentication device is adapted to receive said authentication information provided by said user on boarding said selected service, and further wherein said authentication device includes a display for displaying a message based on said positive notification or said negative notification.