Patent Description:
The invention relates to methods and systems involving a plurality of identifier transmitters. For example, the invention relates to a method and system for enabling a payment between a payor using a mobile device and one or more of a plurality of payees corresponding to respective ones of the identifier transmitters, and is of particular but by no means exclusive application in enabling a payment between a passenger using a smartphone in a taxi and one of a plurality of drivers of respective taxis. In another example, the invention relates to a method and system for identifying one of a plurality of service providers corresponding to respective ones of the identifier transmitters, and is of particular but by no means exclusive application in identifying one of a plurality of drivers of respective taxis.

In Australia and many parts of the world, taxi drivers (including drivers of limousines or other chauffeured vehicles) accept payment made in cash or using a charge or credit card via an electronic payment device. A receipt of payment must be provided by a driver of a taxi to a passenger of the taxi if payment for a trip is made by the passenger using a charge or credit card. The receipt must include details of the driver and details of the taxi. Payment for a trip usually takes place at the end of the trip, but it is not unusual for taxi drivers to request for payment (such as a partial upfront advance) at the beginning of the trip. It is also possible for a payment to be made during a trip.

<CIT> discloses a method where a central server tracks wireless identity transmitters and associates them with proximity broadcast receivers, such as smartphones. The server registers these associations and monitors the transmitters' proximity to the receivers, transmitting notifications when a transmitter moves out of range or is no longer detected.

<CIT> describes methods for secure data communication, where user inputs trigger the transmission of identifiers and information between devices and a central system. The focus is on ensuring secure exchanges of data, using encryption and verification during transmission and querying processes.

<CIT> discloses systems for transmitting location-based data between devices and a central server, ensuring that objects are within a predefined area. The system tracks objects using wireless transmitters and sends notifications when they move beyond the specified range.

There is a need for an alternative or improved method of enabling payments between passengers and drivers.

In order that the invention may be more clearly ascertained, embodiments will now be described, by way of example, with reference to the accompanying drawings, in which:.

Referring to <FIG> of the drawings, there is shown a system <NUM>, <NUM> comprising a plurality of identifier transmitters <NUM> and a mobile device <NUM>, <NUM>. As described in further detail below, the system <NUM>, <NUM> is arranged to associate an identifier corresponding to the mobile device <NUM>, <NUM>. For example, in an embodiment of the system <NUM> as illustrated in <FIG>, the system <NUM> is arranged to associate an identifier corresponding to one of a plurality of payee devices <NUM> in communication with respective ones of the identifier transmitters <NUM> with an identifier corresponding to the mobile device <NUM> in order to enable a payment between a payor using the mobile device and one or more of a plurality of payees corresponding to respective ones of the identifier transmitters <NUM>. In another example, an alternative embodiment of the system <NUM> as illustrated in <FIG> is arranged to associate an identifier corresponding to one of the identifier transmitters <NUM> with an identifier corresponding to the mobile device <NUM> in order to enable an identification of one of a plurality of service providers corresponding to respective ones of the identifier transmitters <NUM>. It is envisaged the features from an embodiment of the system <NUM>, <NUM> may be incorporated into another embodiment of the system <NUM>, <NUM>. For example, in the alternative embodiment of the system <NUM> illustrated in <FIG>, the system <NUM> may alternatively be arranged to associate an identifier corresponding to one of a plurality of intermediaries (such as the payee devices <NUM> of the embodiment of the system <NUM> illustrated in <FIG>) in communication with respective ones of the identifier transmitters <NUM> (rather than an identifier corresponding to one of the identifier transmitters <NUM>) with an identifier corresponding to the mobile device <NUM> in order to enable an identification of one of a plurality of service providers corresponding to respective ones of the identifier transmitters <NUM>.

Turning now to <FIG> of the drawings, there is shown an embodiment of a system <NUM> for enabling a payment between a payor (a passenger of a taxi) using a mobile device <NUM> (such as smartphone in the form of an iPhone (trademark) developed by Apple Inc. ) and one or more payees (in particular, taxi drivers) using respective payee devices <NUM>. The system <NUM> comprises a payment processor <NUM> in communication with the mobile device <NUM>. The payment processor <NUM> is configured to, upon receipt from the mobile device <NUM> of a first identifier (such as a driver identifier (ID)) corresponding to one of the payee devices <NUM> and a second identifier (such as a media access control (MAC) address or Device ID of an iPhone) corresponding to the mobile device <NUM>, associate the first identifier with the second identifier in a memory <NUM>. The payment processor <NUM> is also configured to, in response to receipt of a payment request transmitted from the mobile device <NUM>, generate a payment notification in respect of the payment request, and transmit the payment notification to the payee device <NUM> corresponding to the first identifier associated with the second identifier in the memory <NUM>. Advantageously, the system <NUM> facilitates an automatic payment from the payor using the mobile device <NUM> to one of the payees using any of the payee devices <NUM>, once the first identifier is associated with the second identifier. Another advantage is that payment may be made by the payor to a payee without requiring a direct connection between the mobile device <NUM> and the payee device <NUM> to be established. A further advantage is that the system <NUM> allows an offer, coupon or discount or some other benefit to be managed and applied to any payment by the payment processor <NUM> at a central location (rather than by payee devices <NUM> at distributed locations).

It is envisaged that the payment processor <NUM> is typically implemented by a computing device such as a computer server (which may be located remotely or via "cloud computing"), a desktop personal computer, a portable computer (such as a laptop computer, a notebook computer or a tablet computer), or a mobile computing device (such as a smartphone), a programmable circuit etc. Persons skilled in the art will appreciate that the payment processor <NUM> may be implemented by multiple computing devices such that each computing device implements only a part or parts of the payment processor <NUM>.

<FIG> is a schematic diagram of the physical architecture of an embodiment of the system <NUM>. The system <NUM> comprises a payment processor <NUM> connected to a payment processor memory <NUM> and a network <NUM> in the form of the Internet. The system <NUM> also comprises a plurality of payee devices <NUM> for use by respective payees, each of the payee devices <NUM> being in wireless communication with a respective one of a plurality of identifier transmitters <NUM>. In this embodiment, the system <NUM> takes advantage of the iBeacon (trademark) arrangement and the Passbook application developed by Apple Inc. Thus, each of the payee devices <NUM> is a smartphone in the form of an iPhone (trademark) located in a taxi, and each of the identifier transmitters <NUM> is an iBeacon that is adapted to broadcast notifications using a short range communication standard such as Bluetooth Low Energy (BLE) or Bluetooth Smart (trademark). The use of BLE or Bluetooth Smart is advantageous in that it has a range that is suitable for broadcasting signals within a taxi, a maximum data rate that is high enough for broadcasting iBeacon signals (about <NUM> megabits-per-second), and relatively low peak current consumption (about <NUM> milliamperes). The system <NUM> also comprises a mobile device <NUM> for use by the payor to receive the notifications broadcast from the identifier transmitters <NUM>. In this embodiment, the mobile device <NUM>-like each of the payee devices <NUM>-is a smartphone in the form of an iPhone. The mobile device <NUM> and each of the payee devices <NUM> can be in wireless communication with the network <NUM> via a mobile communication network such as a Long Term Evolution (LTE) network or alternatively a wireless local area network such as Wi-Fi.

In this embodiment of the system <NUM>, the payee devices <NUM>, the identifier transmitters <NUM> and the mobile device <NUM> are devices that are compatible with the Passbook (trademark) application by Apple Inc. However, it is envisaged that the system <NUM> may alternatively or additionally comprise devices that are not compatible with the Passbook (trademark) application by Apple Inc. but are compatible with equivalent products such as Google Wallet (trademark). For example, it is envisaged that an alternative embodiment of the system <NUM> may comprise payee devices <NUM> in the form of smartphones where each identifier transmitter <NUM> is integrated within a smartphone (rather than in a separate device such as an iBeacon), for example, by an application (in particular, a proprietary application supplied or provided by a service provider such as a Payment Service Provider (PSP) or a taxi company) installed on the smartphone.

It is envisaged that an alternative embodiment of the system <NUM> may comprise more than one mobile device <NUM>. Also, the system <NUM> may comprise one or more payee devices <NUM>. Also, it is envisaged that an alternative embodiment of the system <NUM> may take advantage of an arrangement other than the iBeacon arrangement, or an application (such as a proprietary application provided or supplied by a service provider such as a PSP or a taxi company) in addition to or other than the Passbook application. In this respect, the notifications from the identifier transmitters <NUM> may not be broadcast using BLE or Bluetooth Smart as specified by the iBeacon arrangement, but using other short range communication standards such as Near Field Communication (NFC) as specified by an alternative arrangement. In this respect, a person skilled in the art will appreciate that any alternative communication standard having a suitable range (for example, one having a range of at least <NUM> meter, or one having a maximum of about <NUM> meters) to broadcast the notifications within a taxi to a passenger of the taxi may be used. Examples of such alternative communication standards include wireless local area network (Wi-Fi) standards, and mobile or cellular communication standards such as LTE or UMTS. It is also envisaged that other communication methods such as barcodes, for example, Quick Response (QR) codes may be used in other embodiments.

Persons skilled in the art will appreciate that the payment processor memory <NUM> may be implemented in a single device (for example, as part of the payment processor <NUM>) or in separate devices.

The system <NUM> comprises a number of functional components for enabling a payment between a payor using the mobile device <NUM> and each of the payees using respective payee devices <NUM>. It is envisaged that the functional components are typically implemented by a processor of a device executing program code and data stored in a memory of the device. However, persons skilled in the art will appreciate that this need not be the case. For example, one or more of the components could be implemented in an alternative manner, for example, as a dedicated circuit. <FIG> is a schematic diagram showing the functional components of the system <NUM>. In <FIG>, only one of the identifier transmitters <NUM> and only one of the payee devices <NUM> are shown.

Beginning first with the payment processor <NUM> of the system <NUM>, the payment processor <NUM> comprises a processor <NUM> and a communication interface <NUM>. The processor <NUM> of the payment processor <NUM> is arranged to implement functional components in the form of an identifier associator <NUM>, a payment notification generator <NUM>, and a modified payment information generator <NUM> based on program code and data stored in the payment processor memory <NUM> connected to the payment processor <NUM>.

As indicated above, the identifier transmitter <NUM> is adapted to broadcast notifications using BLE or Bluetooth Smart as specified according to the iBeacon arrangement. In particular, the identifier transmitter <NUM> is arranged to broadcast an identifier (a payee device identifier) of the payee device <NUM> over a BLE or Bluetooth Smart communication channel. It is envisaged that the identifier transmitter <NUM> may alternatively broadcast an identifier of a payee, or any identifier corresponding to either a payee device <NUM> or a payee.

In use, the payee device identifier is provided to the identifier transmitter <NUM> before the payee device identifier is broadcast by the identifier transmitter <NUM>. It is envisaged that the payee device identifier may be provided to the identifier transmitter <NUM> in different ways. For example, the payee device identifier may be output by a communication interface <NUM> of the payee device <NUM> (or some other device such as another smartphone) to the identifier transmitter <NUM> using BLE or Bluetooth Smart. In another example, the payee device identifier may be provided to the identifier transmitter <NUM> by connecting the identifier transmitter <NUM> to a computer (for example, a desktop computer or a laptop computer) via a Universal Serial Bus (USB), and outputting the payee device identifier from the computer to the identifier transmitter <NUM> via the USB connection. More details will be provided below with reference to <FIG> (for example, with reference to item <NUM> of <FIG>).

The mobile device <NUM> is adapted to monitor the BLE or Bluetooth Smart communication channel for receipt of a broadcast of a payee device identifier. As indicated above, the mobile device <NUM> is an iPhone in this embodiment. An application in the form of the Passbook application by Apple Inc. is installed in the mobile device <NUM>. In use, the Passbook application monitors the BLE or Bluetooth Smart communication channel for receipt of a broadcast signal that includes a broadcast identifier in the form of a universally unique identifier (UUID), and a payee device identifier in the form of an identifier of a driver of a taxi (a driver ID), an identifier of the taxi (a vehicle ID), or both the driver ID and the vehicle ID.

For example, the broadcast signal may include:.

In the above example of the broadcast signal, the Major and Minor values represent settings of an iBeacon that are configurable by a service provider (such as the PSP) to differentiate iBeacons in different taxis.

Upon receipt by the mobile device <NUM> of the broadcast signal, the mobile device <NUM> determines whether the broadcast identifier (that is, the UUID) of the broadcast signal matches or corresponds to a designated broadcast identifier (that is, a designated UUID). In response to a determination that the UUID of the broadcast signal corresponds to a designated UUID, the mobile device <NUM> displays an identifier request in the form of a notification to display information relating to the driver of the taxi and/or the taxi (that is, the taxi driver and/or taxi corresponding to the payee device identifier of the broadcast signal transmitted by the identifier transmitter <NUM>). When the mobile device <NUM> receives from the payor (that is, the passenger) a payor input to display the information relating to the driver of the taxi and/or the taxi, the mobile device <NUM> generates an identifier notification comprising the payee device identifier and an identifier (a payor identifier) corresponding to either the mobile device <NUM> or the payor such as an identifier of the payor or an identifier of the mobile device <NUM> (such as a media access control (MAC) address or device ID of the mobile device <NUM>), and transmits the identifier notification over a communication channel through the LTE network and the Internet <NUM> to the payment processor <NUM>. Then, the mobile device <NUM> generates and displays to the payor the information relating to the driver of the taxi and/or the taxi via the Passbook app (or alternatively via an equivalent app such as Google Wallet, a proprietary application provided or supplied by a service provider such as a PSP or a taxi company, or a web browser app in alternative embodiments). It is envisaged that the information relating to the driver of the taxi and/or the taxi may be generated by the mobile device <NUM> in different ways. For example, the information may be generated by retrieving the information from the payment processor <NUM>. In another example, the information may be generated by retrieving the information from a memory of the mobile device <NUM>.

In this embodiment, the information relating to the driver of the taxi displayed via the Passbook app on the mobile device <NUM> includes information relating to making a payment via the payment processor <NUM>. The information relating to making a payment via the payment processor <NUM> includes an offer, coupon or discount for payments made via the payment processor <NUM>. However, it is envisaged that, in an alternative embodiment of the system <NUM>, the information relating to making a payment via the payment processor <NUM> may not include such an offer, coupon or discount. Depending on the embodiment, the information relating to making a payment may be in the form of a uniform resource locator (URL) displayed either via the Passbook app (or alternatively via an equivalent app such as Google Wallet, a proprietary application provided or supplied by a service provider such as a PSP or a taxi company, or a web browser application implemented by the mobile device <NUM>). When the mobile device <NUM> receives from the payor a payor input to display the information relating to making a payment, the mobile device <NUM> takes that payor input as an input to generate and transmit a payment request, and generates a payment request comprising the payor identifier. Then, the mobile device <NUM> transmits the payment request over a communication channel through the LTE network and the Internet <NUM> to the payment processor <NUM>. In this embodiment, the payment request includes information relating to the offer, coupon or discount for payments made via the payment processor <NUM>. Depending on the embodiment, the payment request and the identifier notification may be transmitted over the same communication channel through the LTE network and the Internet <NUM> connecting the mobile device <NUM> to the payment processor <NUM>, or over different communication channels, through different network or networks, or over different communication channels and through different network or networks. For example, either the payment request or the identifier notification may alternatively be transmitted through a wireless local area network (rather than the LTE network) and the Internet <NUM>.

The communication interface <NUM> of the payment processor <NUM> is adapted to receive the identifier notification transmitted from the mobile device <NUM>, and the payment request transmitted from the mobile device <NUM>. The identifier associator <NUM> is arranged to, in response to receipt by the communication interface <NUM> of the identifier notification transmitted from the mobile device <NUM>, associate the payee identifier of the identifier notification with the payor identifier of the identifier notification in the payment processor memory <NUM> connected to the payment processor <NUM>. The payment notification generator <NUM> is adapted to, in response to receipt by the communication interface <NUM> of the payment request transmitted from the mobile device <NUM>, generate a payment notification in respect of the payment request, and transmit the payment notification to the payee device <NUM> corresponding to the payee identifier associated with the payor identifier in the payment processor memory <NUM> connected to the payment processor <NUM>.

Turning now to the functional components of the payee device <NUM> of the system <NUM>, the payee device <NUM> comprises a processor <NUM>, a communication interface <NUM> and a memory <NUM>. The processor <NUM> of the payee device <NUM> is arranged to implement a functional component in the form of a payment information generator <NUM> based on program code and data stored in the memory <NUM> of the payee device <NUM>.

The communication interface <NUM> of the payee device <NUM> is adapted to receive the payment notification transmitted from the payment processor <NUM>. The payment information generator <NUM> is arranged to generate payment information in respect of the payment request, and transmit the payment information over a communication channel through the LTE network and the Internet <NUM> to the payment processor <NUM>.

In use, the payee device <NUM> displays to the payee (that is, the taxi driver) a request to make a payee input, in response to receipt by the communication interface <NUM> of the payee device <NUM> of the payment notification transmitted from the payment processor <NUM>. As indicated above, the payee device <NUM> is a smartphone in the form of an iPhone. In this embodiment, the request to make a payee input is a request to input the fare for a trip (that is, the charge or the cost of the trip) displayed by an application installed on the iPhone <NUM>. Upon receipt of the payee input, the payment information generator <NUM> of the payee device <NUM> generates payment information in respect of the payment request based on the payee input. Then, the payment information generator <NUM> transmits the generated payment information over a communication channel through the LTE network and the Internet <NUM> to the payment processor <NUM>.

The communication interface <NUM> of the payment processor <NUM> is adapted to receive the payment information transmitted from the payee device <NUM>. The modified payment information generator <NUM> of the payment processor <NUM> is adapted to, in response to receipt by the communication interface <NUM> of the payment processor <NUM> of the payment information transmitted from the payee device <NUM>, generate modified payment information based on the payment information, and transmit the modified payment information to the mobile device <NUM>. In this embodiment, the modified payment information is generated based on not only the payment information transmitted from the payee device <NUM>, but also the information relating to the offer, coupon or discount for payments made via the payment processor <NUM>. Thus, the modified payment information includes an offered, redeemable or discounted fare compared to the fare input by the payee (that is, the taxi driver). It is envisaged that the modified payment information is transmitted from the payment processor <NUM> over a communication channel through the Internet <NUM> and the LTE network connecting the payment processor <NUM> to the mobile device <NUM>, but a person skilled in the art will appreciate that the modified payment information may be transmitted via an alternative network or networks. Also, it is envisaged that, in an alternative embodiment, the fare input by the payee may be modified into an offered, redeemable or discounted fare by a proprietary application provided or supplied by a service provider such as a PSP or a taxi company.

When the mobile device <NUM> receives the modified payment information from the payment processor <NUM>, the mobile device <NUM> displays the modified payment information including the offered fare, redeemable fare or discounted fare. In this embodiment, the modified payment information is displayed on a webpage via a web browser application implemented by the mobile device <NUM>. However, it is envisaged that the modified payment information may be alternatively displayed, for example, by another application implemented by the mobile device <NUM>, for example, a proprietary application provided or supplied by a service provider such as a PSP or a taxi company, a payment application provided or supplied by a payment service provider (PSP), Google Wallet, a web browser app etc..

In this embodiment, modified payment information is generated by the payment processor <NUM> to apply any offer, coupon or discount, after payment information is received by the payment processor <NUM>. However, it is envisaged that, in an alternative embodiment, an offer, coupon or discount may be applied before the modified payment information is generated by the payment processor <NUM>. For example, in an alternative embodiment, the payment notification generated by the payment processor <NUM> may include information relating to an offer, coupon or discount such that the payee (that is, the taxi driver) may apply the offer, coupon or discount before payment information is generated and transmitted from the payee device <NUM> to the payment processor <NUM>.

It is envisaged that payment information may be generated and transmitted from a payee device <NUM> to the payment processor <NUM> before commencement of a trip, during a trip or after the completion of a trip.

It is envisaged that the broadcast signal by the identifier transmitter <NUM> may include information other than the broadcast identifier and the payee identifier. For example, the broadcast signal may include details about the driver of the taxi, the taxi itself, any affiliated organizations (such as the company providing or delivering the taxi or transportation service), related or unrelated advertisements, and an option to pay for a trip or the transportation service.

It is envisaged that an application or applications may be installed in the mobile device <NUM> used by the payor (that is, the passenger of the taxi) to provide the payor with an option or multiple options to make a payment in respect of a trip or transportation service. As indicated above, it is envisaged that the payee device <NUM> is notified if a payor takes up an option to make a payment in respect of a trip or transportation service using such an application or applications. In this respect, it is envisaged that such an option or options may include making a payment on a website via a web browser application, a proprietary application provided or supplied by a service provider such as a PSP or a taxi company, a payment application that may be previously installed on the mobile device. Also, it is envisaged that a payor may also decide to manually make a payment using cash or a point of sale payment device. It is also envisaged that a notification such as an email or short messaging service (SMS) message may be transmitted to the payor, the payee, or both the payor and the payee, upon approval or completion of a payment.

Also, it is envisaged that an application or applications may be installed in the payee device <NUM> used by the payee (that is, the driver of the taxi) to enable the payee to receive a payment in respect of a trip or transportation service. An example of such an application or applications is described below with reference to <FIG>.

Also, it is envisaged that the payment processor <NUM> may be additionally configured to complete any payment made by the payor using the mobile device <NUM>. For example, a payment made by the payor using the mobile device <NUM> may be first received by a PSP operating the payment processor <NUM> before being forwarded to the payee (for example, a payee-specified bank account). In this respect, the payment processor <NUM> may be additionally or alternatively configured to deduct any fees before forwarding payment to the payee.

<FIG> is a flow chart of an embodiment of the method of enabling a payment, carried out using the system of <FIG> and <FIG>. As indicated in the figure, additional steps may precede or follow the steps illustrated in the figure. These additional steps are described in more detail below with reference to <FIG>.

At step <NUM>, an application of the mobile device <NUM> (that is, the Passbook application installed in the iPhone of a passenger of a taxi, or alternatively a proprietary application provided or supplied by a service provider such as a PSP or a taxi company) monitors a communication channel in the form of a BLE or Bluetooth Smart communication channel for receipt of a broadcast signal from an identifier transmitter <NUM> (that is, an iBeacon), the broadcast signal comprising a broadcast identifier in the form of a UUID, and a payee device identifier in the form of a driver ID and a vehicle ID.

At step <NUM>, the Passbook application (or alternatively the proprietary application mentioned at step <NUM>) installed in the mobile device <NUM> determines whether or not the UUID of the broadcast signal matches or corresponds to a designated UUID. If the mobile device <NUM> determines that the UUID of the broadcast signal does not match or correspond to the designated UUID, the mobile device <NUM> monitors the communication channel for receipt of another broadcast signal. Otherwise, if the mobile device <NUM> determines that the UUID of the broadcast signal matches or corresponds to the designated UUID, the mobile device <NUM> displays an identifier request in the form of a notification (such as a pop-up window if the mobile device <NUM> is being used by the payee, or a notice on a lock screen displayed by the mobile device <NUM> if the mobile device <NUM> is not being used by the payee) to display information relating to a payee, for example, a notification to display via the Passbook application a pass comprising information relating to the driver of the taxi, or alternatively a notification to display the information relating to the driver of the taxi via the proprietary application mentioned at step <NUM>. As indicated above, it is envisaged that the information relating to a payee may include other information including information relating to the taxi, an affiliated transportation company or PSP, an option to pay and/or redeem an offer and/or discount by making a payment via the payment processor <NUM> etc..

If the mobile device <NUM> does not receive an input to display the pass, the mobile device <NUM> continues to display the notification to display information relating to a payee, until the mobile device <NUM> no longer receives the broadcast signal from the identifier transmitter <NUM>.

At step <NUM>, the mobile device <NUM> receives an input from the payor (that is, the passenger in the taxi) using the mobile device <NUM> to display via the Passbook application (or alternatively, via the proprietary application mentioned at step <NUM>) the pass comprising information relating to the driver of the taxi (that is, to display the identifier request).

At step <NUM>, the mobile device <NUM> displays the identifier request, that is, displays via the Passbook application (or alternatively, via the proprietary application mentioned at step <NUM>) the pass comprising information relating to the driver of the taxi including information relating to any discount for making a payment via the payment processor <NUM>. In this embodiment, the information relating to a discount for making a payment via the payment processor <NUM> includes a proprietary app download or URL for initiating a payment via the payment processor <NUM>. The mobile device <NUM> also generates an identifier notification comprising the payee device identifier (that is, the driver ID and the vehicle ID of the broadcast signal from the iBeacon <NUM>) and a MAC address or device ID (a payor identifier) of the mobile device <NUM>, and transmits the identifier notification over a communication channel through the LTE network and the Internet <NUM> to the payment processor <NUM>.

At step <NUM>, the payment processor <NUM> associates the MAC address or device ID (the payor identifier) of the identifier notification with the driver ID and the vehicle ID (that payee identifier) of the identifier notification in the payment processor memory <NUM> connected to the payment processor <NUM>.

As indicated above, the identifier request displayed by the mobile device <NUM> via the Passbook application installed on the mobile device <NUM> includes a URL for initiating a payment which can be made, for example, via the payment processor <NUM> or some other payment processor. At step <NUM>, the payor accesses the URL to initiate a payment, for example, by clicking the URL. As indicated above, it is envisaged that, in an alternative embodiment, the identifier request (that is, the information relating to the driver of the taxi) could alternatively be displayed via the proprietary application mentioned at step <NUM>. In such an alternative embodiment, the proprietary application may be used by the payor to initiate the payment at step <NUM>.

At step <NUM>, a payment request comprising the payor identifier (that is, the MAC address or device ID of the mobile device or iPhone <NUM>) is generated and transmitted from the mobile device <NUM> to the payment processor <NUM>. In this embodiment, the payment request may include information relating to the discount for payments made via the payment processor <NUM>.

At step <NUM>, the payment processor <NUM> receives the payment request from the mobile device <NUM>, and retrieves from the payment processor memory <NUM> the payee identifier associated with the received payor identifier (that is, the MAC address or device ID of the payment request received from the mobile device <NUM>). Then, the payment processor <NUM> generates a payment notification in respect of the payment request, and transmits the payment notification to the payee device <NUM> corresponding to the associated payee identifier.

At step <NUM>, in response to receipt by the communication interface <NUM> of the payee device <NUM> of the payment notification transmitted from the payment processor <NUM>, the payee device <NUM> displays to the payee (that is, the taxi driver) a request to make a payee input, and an input to generate and transmit payment information is received by the payee device <NUM> when the payee inputs the fare for a trip. As indicated above, depending on the embodiment, the fare input by the payee may or may not take into account any offer, coupon or discount.

At step <NUM>, the payee device <NUM> generates the payment information based on the fare input by the payee, and transmits the generated payment information to the payment processor <NUM>.

At step <NUM>, the payment processor <NUM> receives the payment information from the payee device <NUM>, and generates modified payment information based on the received payment information and the information relating to any offer or discount for payments made via the payment processor <NUM> included in the payment request previously transmitted at step <NUM>. Then, the payment processor <NUM> transmits the modified payment information to the mobile device <NUM>.

As indicated in the <FIG>, additional steps may optionally precede the steps illustrated in the <FIG>. These optional preceding steps are described in more detail below with reference to <FIG>.

At step <NUM>, a designated UUID is defined for enabling a payment from a payor to a payee. At step <NUM>, the payee device <NUM> used by the payee (that is, the driver of the taxi using the payee device <NUM>) is provided or supplied with the designated UUID. In this embodiment, the designated UUID is provided to a payee device <NUM> when the taxi driver using the payee device <NUM> downloads a payment application provided by a PSP from an application store in the form of the iTunes (trademark), installs the payment application on the payee device, and creates an account with the PSP and provides bank account details to receive payments from the PSP. Persons skilled in the art will appreciate that creating and installing the payment application may involve steps such as entering and authenticating payee details such as the bank details of the payee.

At step <NUM>, the mobile device <NUM> used by the payor is provided or supplied with a pass compatible with the Passbook application implemented on the mobile device <NUM>. As indicated above, the pass corresponds to an offer or coupon that may be from an affiliated transportation company, a PSP etc. It is envisaged that the pass may be provided to the mobile device <NUM> via different ways including email, social media, SMS, Bluetooth, Ethernet, Wi-Fi, QR codes etc. As indicated above, the pass remains dormant (but active) in the mobile device <NUM> until the mobile device <NUM> receives a broadcast signal corresponding to a designated broadcast identifier such as a designated UUID. As indicated above, the mobile device <NUM> may, in an alternative embodiment, receive an equivalent of the pass that is compatible with an alternative to the Passbook application supplied by an affiliated transportation company, a payment service provided (PSP) etc..

At step <NUM>, the designated UUID is provided to identifier transmitter <NUM> in communication with the payee device <NUM>. The identifier transmitter <NUM> is a standalone device (specifically, an iBeacon) in this embodiment. However, as indicated above, it is envisaged that the identifier transmitter <NUM> may not be a standalone device. In particular, the identifier transmitter <NUM> may be the payee device <NUM> (or a part of the payee device <NUM>) as indicated above.

At step <NUM>, a broadcast signal comprising a broadcast identifier in the form of a UUID and a payee identifier (such as a Driver ID or a vehicle ID) is broadcast by the identifier transmitter <NUM>. As indicated above, the identifier transmitter is an iBeacon, and the broadcast signal is broadcast using a BLE or Bluetooth Smart communication channel. Below is an example of details included in the broadcast signal:.

As indicated above, it is envisaged that the identifier transmitter may not be an iBeacon, and the broadcast signal may alternatively or additionally be broadcast using other communication channels such as a Wi-Fi communication channel. Also, depending on the embodiment, the payee identifier and the broadcast identifier may be broadcast separately from different devices. For example, the broadcast identifier (that is, the UUID) may be broadcast by the identifier transmitter <NUM> and the payee identifier (that is, the Driver ID and/or the vehicle ID) may be broadcast by the payee device <NUM>.

As indicated in the <FIG>, additional steps may optionally follow the steps illustrated in the <FIG>. These optional following steps are described in more detail below with reference to <FIG>.

At step <NUM>, the mobile device <NUM> displays a discounted fare based on the modified payment information transmitted from the payment processor <NUM> to the mobile device <NUM> at step <NUM> of <FIG>. In this embodiment, the payor can accept the discounted fare (that is, accept to pay the discounted fare for the trip), for example, by pressing an on screen button, a swiping action etc. As indicated above, it is envisaged that, in an alternative embodiment, modification of payment information may be performed by a proprietary application provided or supplied by a service provider such as a PSP or a taxi company. That is, the fare input by the payee may be modified into an offered, redeemable or discounted fare by a proprietary application in an alternative embodiment. In such an alternative embodiment, at step <NUM>, the mobile device <NUM> may alternatively display a discounted fare (or offered fare, redeemed fare etc.) based on payment information that is modified by the proprietary application (rather than payment information that is modified by and transmitted from the payment processor <NUM>). For example, a proprietary application installed on the mobile device <NUM> may apply a discount voucher from a pass in the Passbook application, before displaying a discounted fare at step <NUM>.

At step <NUM>, upon acceptance of the discounted fare, the mobile device <NUM> detects whether or not there is an application (a pre-installed application) installed on the mobile device <NUM> for making a payment of the discounted fare. In this embodiment, the pre-installed application is provided by the bank of the payor. However, it is envisaged that the pre-installed application may alternatively be provided by another entity including a service provider (such as a taxi company), a credit or charge card issuer, a PSP such as PayPal, a mobile device hardware provider, a mobile device operating system provider etc..

At step <NUM>, upon detection by the mobile device <NUM> that there is a pre-installed application for making a payment of the discounted fare, the mobile device <NUM> provides information including payor details to the pre-installed application. In this respect, it is envisaged that other information such as payee details (such as specific merchant details for making a payment to the relevant payee) or the preferred payment method of the payor (for example, via a preferred credit card) may be additionally or alternatively provided to the pre-installed application.

At step <NUM>, upon detection by the mobile device <NUM> that there is no pre-installed application for making a payment of the discounted fare, the mobile device <NUM> automatically downloads a new application provided by a PSP, installs the new application on the mobile device <NUM>, and provides information such as payor and payee details to the new application for paying the discounted fare. A person skilled in the art will appreciate that it may be necessary to create an account and/or specify a preferred payment method or methods before making the payment.

At step <NUM>, upon payment of the discounted fare, a receipt or acknowledgement of payment is transmitted (for example, via email or SMS) to the mobile device <NUM> and/or the payee device <NUM>. It is envisaged that the receipt or acknowledge may also be displayed by the mobile device <NUM>, the payee device <NUM>, or both the mobile device <NUM> and the payee device <NUM>, upon receipt of the receipt or acknowledgement.

Turning now to <FIG> of the drawings, there is shown an embodiment of a system <NUM> for identifying one of a plurality of service providers (such as taxi drivers). The system <NUM> comprises a plurality of identifier transmitters <NUM> (such as a plurality of iBeacons) located at different locations for respective use by the service providers (in particular, in a plurality of taxis respectively associated with the taxi drivers), and a transmitter identifying device <NUM> in communication with a mobile device <NUM> (such as smartphone in the form of an iPhone) and a querying device (which is the mobile device <NUM> in this embodiment, but may be another device in an alternative embodiment). The transmitter identifying device <NUM> is configured to, upon receipt from the mobile device <NUM> of a first identifier (such as a taxi driver identifier) corresponding to one of the identifier transmitters <NUM> and a second identifier (such as a MAC address or device ID of an iPhone) corresponding to the mobile device <NUM>, associate the first identifier with the second identifier in a memory <NUM>. The transmitter identifying device <NUM> is also configured to, in response to receipt of an identifier request transmitted from the querying device, generates a transmitter notification based on the first identifier associated with the second identifier in the memory, and transmit the transmitter notification to the querying device <NUM>. Advantageously, the system <NUM> enables an identification of an identifier transmitter <NUM> (and hence, the service provider using the identifier transmitter <NUM>) of which the mobile device <NUM> is within range, after the first identifier corresponding to the identifier transmitter <NUM> is associated with the second identifier corresponding to the mobile device <NUM> in the memory <NUM>.

It is envisaged that the transmitter identifying device <NUM> is typically implemented by a computing device such as a computer server (which may be located remotely or via "cloud computing"), a desktop personal computer, a portable computer (such as a laptop computer, a notebook computer or a tablet computer), or a mobile computing device (such as a smartphone), a programmable circuit etc. Persons skilled in the art will appreciate that the transmitter identifying device <NUM> may be implemented by multiple computing devices such that each computing device implements only a part or parts of the transmitter identifying device <NUM>.

<FIG> is a schematic diagram of the physical architecture of an embodiment of the system <NUM>. The system <NUM> comprises a transmitter identifying device <NUM> connected to a transmitter identifying device memory <NUM> and a network <NUM> in the form of the Internet. The system <NUM> also comprises a plurality of identifier transmitters <NUM> for use by respective service providers in the form of respective taxi drivers. In this embodiment, the system <NUM> takes advantage of the iBeacon arrangement, the Passbook application (which in an alternative embodiment may be a proprietary application provided or supplied by a service provider such as a taxi company or a PSP), and each of the identifier transmitters <NUM> is an iBeacon that is adapted to broadcast notifications within a taxi using a short range communication standard in the form of either BLE or Bluetooth Smart. As indicated above in respect of the method and system for enabling a payment, the use of BLE or Bluetooth Smart by an identifier transmitter <NUM> is advantageous in that it enables the transmitter identifier <NUM> to have a range (as illustrated by the dotted lines surrounding the identifier transmitter <NUM> in <FIG>) that is suitable for broadcasting signals within a taxi, a maximum data rate that is high enough for broadcasting iBeacon signals (about <NUM> megabits-per-second), and relatively low peak current consumption (about <NUM> milliamperes). It is envisaged that the identifier transmitter <NUM> and the mobile device <NUM> may not be compatible with the Passbook application in an alternative embodiment, and may alternatively or additionally be compatible with an equivalent application such as Google Wallet in an alternative embodiment.

In this embodiment, the system <NUM> also comprises a mobile device <NUM> in the form of an iPhone for use by a user in the form of a passenger in the taxi, and the mobile device <NUM> and the transmitter identifying device <NUM> are in wireless communication with the network <NUM> via a cellular data communication network in the form of a LTE network. It is envisaged that the mobile device <NUM> and the transmitter identifying device <NUM> may alternatively be connected by a wireless local area network such as Wi-Fi in an alternative embodiment.

The system <NUM> also comprises a querying device that is arranged to send an identifier request requesting the transmitter identifying device <NUM> for an identification of one of the plurality of identifier transmitters <NUM> used by the respective service providers. In this embodiment, the mobile device <NUM> is also the querying device. However, it is envisaged that the querying device may be another device such as another mobile device.

It is envisaged that an alternative embodiment of the system <NUM> may comprise more than one mobile device <NUM>, just one identifier transmitter <NUM>, and/or more than one transmitter identifying device <NUM>. Also, it is envisaged that an alternative embodiment of the system <NUM> may take advantage of an arrangement other than the iBeacon arrangement such that notifications from one or more of the identifier transmitters <NUM> may not be broadcast using BLE or Bluetooth Smart as specified by the iBeacon arrangement, but using other short range communication standards as specified by an alternative arrangement. In this respect, a person skilled in the art will appreciate that any alternative communication standard having a suitable range (for example, one having a range of at least <NUM> meter, or one having a maximum of about <NUM> meters) to broadcast the notifications within a taxi to a passenger of the taxi may be used. Examples of such alternative communication standards include other mobile or cellular data communication standards such as UMTS. It is also envisaged that other communication methods such as barcodes or QR codes may be used in alternative embodiments. Also, persons skilled in the art will appreciate that the transmitter identifying device memory <NUM> may be implemented by a single device (for example, as part of the transmitter identifying device <NUM>) or by separate devices.

The system <NUM> comprises a number of functional components for identifying one of the identifier transmitters <NUM>. It is envisaged that the functional components are typically implemented by a processor of a device executing program code and data stored in a memory of the device. However, persons skilled in the art will appreciate that this need not be the case. For example, one or more of the components could be implemented in an alternative manner, for example, as a dedicated circuit. <FIG> is a schematic diagram showing the functional components of the system <NUM>. In <FIG>, only one of the identifier transmitters <NUM> is shown.

Beginning first with the functional components of the mobile device <NUM> of the system <NUM>, the mobile device <NUM> comprises a processor <NUM> and a communication interface <NUM>. The processor <NUM> of the mobile device <NUM> is arranged to implement functional components in the form of a broadcast identifier matcher <NUM>, an information request generator <NUM>, an identifier notification generator <NUM>, and an identifier request generator <NUM> based on program code and data stored in a memory (not shown in <FIG>) of the mobile device <NUM>. In this embodiment, the functional components implemented by the processor <NUM> are provided by a combination of a proprietary application provided by a service provider and the Passbook application. That is, each one of the functional components is provided by the Passbook application, the proprietary application, or a combination of the Passbook application and the proprietary application. It is envisaged that the components may be provided in some other way in an alternative embodiment. For example, in an alternative embodiment, the functional components may all be provided by a proprietary application.

As indicated above, the identifier transmitter <NUM> is adapted to broadcast notifications using BLE or Bluetooth Smart as specified according to the iBeacon arrangement. In particular, the identifier transmitter <NUM> is arranged to broadcast a first identifier in the form of an identifier (a transmitter identifier) of the identifier transmitter <NUM> over a BLE or Bluetooth Smart communication channel. In this embodiment, the transmitter identifier is a taxi driver ID. However, it is envisaged that the identifier transmitter <NUM> may alternatively be an identifier of the taxi, or any identifier corresponding to either an identifier transmitter <NUM> or a user of an identifier transmitter <NUM> in an alternative embodiment.

In use, the transmitter identifier is associated with the identifier transmitter <NUM> before the transmitter identifier is broadcast by the identifier transmitter <NUM>. In this embodiment, the transmitter identifier is an identifier stored in association with information relating to the identifier transmitter <NUM> in the transmitter identifying device memory <NUM>. In this embodiment, the information relating to the identifier transmitter <NUM> is information relating to a taxi driver. However, it is envisaged that the information relating to the identifier transmitter <NUM> may alternatively be information relating to a taxi or some other information in an alternative embodiment.

In this embodiment, the transmitter identifier is provided to the identifier transmitter <NUM> by connecting the identifier transmitter <NUM> to the transmitter identifying device <NUM>, and outputting the transmitter identifier together with the information relating to the identifier transmitter <NUM> from the transmitter identifying device <NUM> to the identifier transmitter <NUM>. It is envisaged that the transmitter identifier may be associated with the identifier transmitter <NUM> in other ways. For example, the transmitter identifier may be an identifier that is predetermined (that is, previously assigned to the identifier transmitter <NUM> without any setup by the manufacturer of the identifier transmitter <NUM>) in an alternative embodiment. In such an alternative embodiment, the transmitter identifier may be outputted from the identifier transmitter <NUM> to the transmitter identifying device <NUM>, and the predetermined transmitter identifier may be associated with information relating to the identifier transmitter <NUM> stored in the transmitter identifying device memory <NUM> after connecting the identifier transmitter <NUM> to the transmitter identifying device <NUM>.

The mobile device <NUM> is adapted to monitor the BLE or Bluetooth Smart communication channel for receipt of a broadcast of a transmitter identifier. As indicated above, the mobile device <NUM> is an iPhone with the Passbook application (or proprietary application in an alternative embodiment) installed in the mobile device <NUM>. In this embodiment, the Passbook application (or proprietary application in an alternative embodiment) monitors the BLE or Bluetooth Smart communication channel for receipt of a broadcast signal that includes a broadcast identifier in the form of a UUID and the transmitter identifier. It is envisaged that, in an alternative embodiment, the broadcast signal may include other identifiers such as a taxi driver ID, a taxi ID, or both a taxi driver ID and a taxi ID.

The communication interface <NUM> of the mobile device <NUM> is adapted to receive the broadcast signal broadcast from the identifier transmitter <NUM>. The broadcast identifier matcher <NUM> of the mobile device <NUM> is adapted to, upon receipt by the communication interface <NUM> of the mobile device <NUM> of the broadcast signal, determine whether the broadcast identifier (that is, the UUID) of the broadcast signal matches or corresponds to a designated broadcast identifier (that is, a designated UUID). The broadcast identifier matcher <NUM> is also arranged to, in response to a determination by the broadcast identifier matcher <NUM> that the UUID of the broadcast signal corresponds to a designated UUID, display an identifier request in the form of a notification to display the information relating to the identifier transmitter <NUM> corresponding to the transmitter identifier of the broadcast signal transmitted by the identifier transmitter <NUM>. As indicated above, the broadcast matcher <NUM> may be implemented by a proprietary application or the Passbook application depending on the embodiment.

The information request generator <NUM> of the mobile device <NUM> is arranged to, upon receipt by the mobile device <NUM> of a user input from the user of the mobile device (that is, the passenger of the taxi) to display the information relating to the identifier transmitter <NUM>, generate an information request comprising the transmitter identifier of the broadcast signal received from the identifier transmitter <NUM>, and control the communication interface <NUM> to transmit over a communication channel through the LTE network and the Internet <NUM> to the transmitter identifying device <NUM> the information request to request for the information relating to the identifier transmitter <NUM>. As indicated in greater detail below, the transmitter identifying device <NUM> is arranged to respond to the information request with the information relating to the identifier transmitter <NUM>.

The identifier notification generator <NUM> of the mobile device <NUM> is arranged to, upon receipt of the information relating to the identifier transmitter <NUM> by the communication interface <NUM> of the mobile device <NUM>, generate an identifier notification comprising the transmitter identifier of the broadcast signal received from the identifier transmitter <NUM> and the mobile device identifier, and to control the communication interface <NUM> of the mobile device <NUM> to transmit the identifier notification over the communication channel through the LTE network and the Internet <NUM> to the transmitter identifying device <NUM>. The identifier notification generator <NUM> is also arranged to control the mobile device <NUM> to display to the user of the mobile device <NUM> the information relating to the identifier transmitter <NUM> via the Passbook app (or alternatively via a proprietary application provided or supplied by a service provider such as a taxi company or a PSP, an equivalent app such as Google Wallet or a web browser app in an alternative embodiment).

As indicated above, in this embodiment, the mobile device <NUM> is also a querying device that requests the transmitter identifying device <NUM> for an identification of one of the plurality of identifier transmitters <NUM>. In use, it is envisaged that such a request or query would typically be made sometime after association of the transmitter identifier and the mobile device identifier has been made. That is, it is envisaged that there will normally be a time delay between the time when a transmitter identifier has been associated with a mobile device identifier and when an identification of the identifier transmitter <NUM> corresponding to the associated transmitter identifier is requested. The identifier request generator <NUM> of the mobile device <NUM> is arranged to generate an identifier request comprising the mobile device identifier, and to control the communication interface <NUM> to transmit the identifier request to the transmitter identifying device <NUM>. In this embodiment, the identifier request is transmitted by the querying device (that is, the mobile device <NUM>) over a communication channel through the LTE network and the Internet <NUM> to the transmitter identifying device <NUM>.

The communication interface <NUM> of the mobile device <NUM> is also arranged to receive from the transmitter identifying device <NUM> a transmitter notification including the information relating to the identifier transmitter <NUM>. As discussed in greater detail below, the transmitter notification is generated based on a transmitter identifier associated with the mobile device identifier in the transmitter identifying device memory <NUM>. It is envisaged that the transmitter notification may include other information. For example, in an embodiment where the information relating to the identifier transmitter <NUM> is information relating to a taxi driver, the transmitter notification may additionally include information relating to a taxi corresponding to the taxi driver. The mobile device <NUM> is also arranged to, upon receipt of the transmitter notification, display information derivable from the transmitter notification on a webpage via a web browser application implemented by the mobile device <NUM>. It is envisaged that the information may be alternatively displayed, for example, by another application implemented on the mobile device <NUM>, for example, the proprietary application provided or supplied by the transmitter identifying device <NUM>, the Passbook application, Google Wallet etc..

Depending on the embodiment, the identifier request, the information request and the identifier notification may be transmitted over the same communication channel through the LTE network and the Internet <NUM> connecting the mobile device <NUM> to the transmitter identifying device <NUM>, or over different communication channels, through different network or networks, or over different communication channels and through different network or networks. For example, any one or more of the identifier request, the information request and the identifier notification may alternatively be transmitted through a wireless local area network (rather than the LTE network) and the Internet <NUM>.

Turning now to the functional components of the transmitter identifying device <NUM> of the system <NUM>, the transmitter identifying device <NUM> comprises a processor <NUM> and a communication interface <NUM>. The processor <NUM> of the transmitter identifying device <NUM> is arranged to implement functional components in the form of an identifier associator <NUM>, a transmitter notification generator <NUM>, and a transmitter information generator <NUM> based on program code and data stored in the transmitter identifying device memory <NUM> connected to the transmitter identifying device <NUM>.

The communication interface <NUM> of the transmitter identifying device <NUM> is adapted to receive the information request transmitted from the mobile device <NUM>, the identifier notification transmitted from the mobile device <NUM>, and the identifier request transmitted from the querying device (which is the mobile device <NUM> in this embodiment). The transmitter information generator <NUM> is arranged to, in response to receipt by the communication interface <NUM> of the information request transmitted from the mobile device <NUM>, generate information relating to the identifier transmitter <NUM> (that is, information relating to the driver of the taxi) by locating and retrieving the information relating to the identifier transmitter <NUM> from the transmitter identifying device memory <NUM> based on the transmitter identifier of the information request received from the mobile device <NUM>, and control the communication interface <NUM> to transmit the information relating to the identifier transmitter <NUM> to the mobile device <NUM>. The identifier associator <NUM> is arranged to, in response to receipt by the communication interface <NUM> of the identifier notification transmitted from the mobile device <NUM>, associate the transmitter identifier of the identifier notification with the mobile device identifier of the identifier notification in the transmitter identifying device memory <NUM> connected to the transmitter identifying device <NUM> (for example, by storing the mobile device identifier against a data record corresponding to the transmitter identifier in the transmitter identifying device memory <NUM>). The transmitter notification generator <NUM> is adapted to, in response to receipt by the communication interface <NUM> of the identifier request transmitted from the querying device (which is the mobile device <NUM> in this embodiment), generate a transmitter notification based on the transmitter identifier associated with the mobile device identifier of the identifier request (for example, by locating and retrieving from the transmitter identifying device memory <NUM> the transmitter identifier associated with the mobile device identifier of the identifier request, and generating a transmitter notification comprising the retrieved transmitter identifier), and control the communication interface <NUM> to transmit the transmitter notification to the querying device.

<FIG> is a flow chart of an embodiment of the method of identifying one of a plurality of identifier transmitters, carried out using the system of <FIG> and <FIG>. At step <NUM>, a designated UUID is defined for enabling an identification of any one of the plurality of identifier transmitters <NUM> of the system <NUM>. At step <NUM>, each identifier transmitter <NUM> is provided or supplied with the designated UUID. In this embodiment, the designated UUID is provided to each identifier transmitter <NUM> by connecting the identifier transmitter <NUM> to the transmitter identifying device <NUM> and outputting the designated UUID from the transmitter identifying device <NUM> to each identifier transmitter <NUM>. Each identifier transmitter <NUM> is a standalone device (specifically, an iBeacon) located in a taxi in this embodiment. However, as indicated above, it is envisaged that each identifier transmitter <NUM> may not be a standalone device. For example, as indicated above in respect of <FIG>, each identifier transmitter <NUM> may be connected to a device of a service provider in the form of an iPhone. In this respect, it is also envisaged that, each identifier transmitter <NUM> may not be an iBeacon, but an iPhone with a proprietary application installed in the phone in an alternative embodiment.

At step <NUM>, a broadcast signal comprising a broadcast identifier in the form of a UUID and an identifier of the identifier transmitter <NUM> (that is, the transmitter identifier) is broadcast by the identifier transmitter <NUM>. As indicated above, the identifier transmitter is an iBeacon, and the broadcast signal is broadcast using a BLE or Bluetooth Smart communication channel. As indicated above, it is envisaged that the identifier transmitter may not be an iBeacon, and the broadcast signal may alternatively or additionally be broadcast using other communication channels such as a Wi-Fi communication channel or NFC.

As indicated above, a proprietary application and the Passbook application are installed on the mobile device <NUM> in this embodiment. At step <NUM>, the Passbook application installed on the mobile phone <NUM> monitors a communication channel in the form of a BLE or Bluetooth Smart communication channel for receipt of a broadcast signal from an identifier transmitter <NUM> (that is, an iBeacon), the broadcast signal comprising a broadcast identifier in the form of a UUID, and a transmitter identifier.

At step <NUM>, the broadcast identifier matcher <NUM> implemented by the processor <NUM> of the mobile device <NUM> (which depending on the embodiment could be part of the Passbook application or the proprietary application installed in the mobile device <NUM>) determines whether or not the UUID of the broadcast signal matches or corresponds to the designated UUID provided or supplied to each of the identifier transmitters <NUM> at step <NUM>. If the mobile device <NUM> determines that the UUID of the broadcast signal does not match or correspond to the designated UUID, the mobile device <NUM> monitors the communication channel for receipt of another broadcast signal. Otherwise, if the mobile device <NUM> determines that the UUID of the broadcast signal matches or corresponds to the designated UUID, the broadcast identifier matcher <NUM> controls the mobile device <NUM> to display an identifier request in the form of a notification (such as a pop-up window if the mobile device <NUM> is being currently in use, or a notice on a lock screen displayed by the mobile device <NUM> if the mobile device <NUM> is not currently in use) to display information relating to the identifier transmitter <NUM> (for example, a notification to display via the Passbook application a pass comprising information relating to the driver of the taxi). As indicated above, it is envisaged that the information relating to the identifier transmitter <NUM> may include other information including information relating to the taxi, an affiliated transportation company, PSP etc. As indicated above, it is envisaged that, in an alternative embodiment, the information relating to the identifier transmitter <NUM> may be displayed by a proprietary application that is provided or supplied by a service provider and is installed on the mobile device <NUM>. In this respect, it is envisaged that the information relating to the identifier transmitter <NUM> may not only include information relating to the driver of the taxi, but also other information such as information relating to a service provider such as a taxi company.

At step <NUM>, the mobile device <NUM> receives an input from the user (that is, a passenger in the taxi) using the mobile device <NUM> to display via either the Passbook application or the proprietary application information relating to the identifier transmitter <NUM> that is broadcasting the broadcast signal at step <NUM>. If the mobile device <NUM> does not receive an input to display the information relating to the identifier transmitter <NUM>, the mobile device <NUM> continues to display the notification to display information relating to the identifier transmitter <NUM> that is broadcasting the broadcast signal at step <NUM>, until the mobile device <NUM> no longer receives the broadcast signal from the identifier transmitter <NUM>.

Otherwise , upon receipt by the mobile device <NUM> of the input from the user of the mobile device <NUM> to display the information relating to the identifier transmitter <NUM> at step <NUM>, the information request generator <NUM> of the processor <NUM> of the mobile device <NUM> generates an information request comprising the transmitter identifier of the broadcast signal received from the identifier transmitter <NUM> that is broadcasting the broadcast signal at step <NUM> and controls the communication interface <NUM> to transmit the information request to the transmitter identifying device <NUM> to request the transmitter identifying device <NUM> for the information relating to the identifier transmitter <NUM> at step <NUM>. The information request is then received by the communication interface <NUM> of the transmitter identifying device <NUM>. Upon receipt of the information request by the transmitter identifying device <NUM>, the transmitter information generator <NUM> implemented by the processor <NUM> of the transmitter identifying device <NUM> then generates the information relating to the identifier transmitter <NUM> corresponding to the transmitter identifier of the information request received from the mobile device <NUM>, and controls the communication interface <NUM> of the transmitter identifying device <NUM> to transmit the generated information to the mobile device <NUM>.

At step <NUM>, the information relating to the identifier transmitter <NUM> is received by the communication interface <NUM> of the mobile device <NUM>.

At step <NUM>, upon receipt of the information relating to the identifier transmitter <NUM> by the communication interface <NUM> of the mobile device <NUM>, the identifier notification generator <NUM> of the mobile device <NUM> controls the mobile device <NUM> to generate a identifier notification comprising the transmitter identifier of the broadcast signal received from the identifier transmitter <NUM> and an identifier (a mobile device identifier) corresponding to either the mobile device <NUM> or the user of the mobile device <NUM>. The identifier notification generator <NUM> then controls the communication interface <NUM> to transmit the identifier notification over a communication channel through the LTE network and the Internet <NUM> to the transmitter identifying device <NUM>.

At step <NUM>, the identifier notification transmitted by the mobile device <NUM> is received by the communication interface <NUM> of the transmitter identifying device <NUM>. The identifier associator <NUM> of the transmitter identifying device <NUM>, upon receipt of the identifier notification transmitted by the mobile device <NUM>, associates the transmitter identifier of the identifier notification with the mobile device identifier of the identifier notification by storing the transmitter identifier of the identifier notification in association with the mobile device identifier of the identifier notification in the transmitter identifying device memory <NUM> connected to the transmitter identifying device <NUM>. At or around the same time, the identifier notification generator <NUM> of the mobile device <NUM> controls the mobile device <NUM> to display the information relating to the identifier transmitter <NUM> that was received at step <NUM>.

At step <NUM>, the mobile device <NUM> receives an input from a user of a querying device (which in this embodiment is the user using the mobile device <NUM>) to request the transmitter identifying device <NUM> for an identification of one of the plurality of identifier transmitters <NUM> used by the respective service providers. Upon receipt of the input by the mobile device <NUM> for the identification of one of the plurality of identifier transmitters <NUM>, the identifier request generator <NUM> of the mobile device <NUM> generates an identifier request comprising the mobile device identifier at step <NUM>. Then, the identifier request generator <NUM> controls the communication interface <NUM> to transmit the generated identifier request from the mobile device <NUM> to the transmitter identifying device <NUM>. As indicated above, it is envisaged that the identifier request may include other information, for example, information about why identification of one of the identifier transmitters <NUM> is requested. As indicated by the dotted lines in <FIG>, the input from the user is subsequently received by the mobile device <NUM> sometime after association of the transmitter identifier and the mobile device identifier has been made at step <NUM>. Thus, there is a time delay between the time when a transmitter identifier has been associated with a mobile device identifier and when an identification of the identifier transmitter <NUM> corresponding to the associated transmitter identifier is requested.

At step <NUM>, the communication interface <NUM> of the transmitter identifying device <NUM> receives the identifier request from the mobile device <NUM>, and the transmitter notification generator <NUM> of the transmitter identifying device <NUM> retrieves from the transmitter identifying device memory <NUM> the transmitter identifier associated with the mobile device identifier of the identifier request received from the mobile device <NUM>. Then, the transmitter notification generator <NUM> generates transmitter notification based on the transmitter identifier associated with the mobile device identifier, and controls the communication interface <NUM> of the transmitter identifying device <NUM> to transmit the transmitter notification to the querying device which in this embodiment is also the mobile device1300, in order to thereby enable the querying device (that is, the mobile device <NUM> in this embodiment) to identify the identifier transmitter <NUM> (and hence the service provider using the identifier transmitter <NUM>) of which the mobile device <NUM> is within range.

Further aspects of the method of <FIG> and/or the method of <FIG> will be apparent from the above description of the system. Persons skilled in the art will also appreciate that either one or both of the methods could be embodied in program code. The program code could be supplied in a number of ways, for example on a tangible computer readable medium, such as a disc or a memory (for example, that could replace part of memory) or as a data signal (for example, by transmitting it from a server).

Similarly, it will be appreciated that data in memory (such as the data in the payment processor memory and/or the transmitter identifying device memory) can be supplied on any appropriate tangible data carrier, such as by writing them to a portable device (such as a USB drive), storing them in a memory (including transmitting identifiers to a device having a memory) etc..

Modifications within the scope of the invention may be readily effected by those skilled in the art. It is to be understood, therefore, that this invention is not limited to the particular embodiments described by way of example hereinabove.

It is to be understood that, if any prior art is referred to herein, such reference does not constitute an admission that the prior art forms a part of the common general knowledge in the art in any country.

Claim 1:
A method of identifying one of a plurality of payees using respective payee devices, each payee device being in communication with a respective one of a plurality of identifier transmitters, said method comprising:
transmitting (<NUM>), from one of the plurality of payee devices to the identifier transmitter in communication with the payee device, a broadcast identifier provided by a payment processor;
transmitting (<NUM>), by the identifier transmitter, a broadcast over a first communication channel, the broadcast comprising the broadcast identifier and a first identifier corresponding to the payee device;
monitoring (<NUM>), by a mobile device used by a payor, a first communication channel for receipt from the identifier transmitter of the broadcast comprising the broadcast identifier and the first identifier corresponding to the payee device;
upon receipt of the broadcast by the mobile device, determining (<NUM>) that the broadcast identifier corresponds to a designated broadcast identifier, and in response to receipt by the mobile device of a first user input, generating (<NUM>) an identifier notification comprising the first identifier and a second identifier corresponding to the mobile device, and transmitting the identifier notification over a second communication channel to the payment processor;
in response to receipt of the identifier notification at the payment processor, associating (<NUM>) the second identifier of the identifier notification with the first identifier of the identifier notification in a memory of the payment processor;
upon receipt (<NUM>) by a querying device of a second user input to transmit an identifier request comprising the second identifier, the payment processor receiving (<NUM>) from the querying device the identifier request comprising the second identifier; and
in response to receipt of the identifier request, retrieving the first identifier associated with the second identifier in the memory of the payment processor based on the second identifier of the identifier request, generating a transmitter notification in respect of the identifier request, and transmitting (<NUM>) the transmitter notification to the querying device,
wherein the querying device is not the mobile device.