(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2011/0153495 A1
`(43) Pub. Date:
`Jun. 23, 2011
`Dixon et al.
`
`US 2011 O153495A1
`
`(54)
`(75)
`
`(73)
`
`(21)
`(22)
`
`(60)
`
`MOBILE WIRELESS PAYMENT AND ACCESS
`Philip B. Dixon, San Diego, CA
`(US); Walter C. Bonneau, JR.,
`Escondido, CA (US); Kay
`Paetzold, Hamburg (DE);
`Raymond L. DeKozan, La Mesa,
`CA (US); Ann C. DeKozan, legal
`representative, (US); Timothy
`Cook, Carlsbad, CA (US); Pradip
`Mistry, San Diego, CA (US)
`Cubic Corporation, San Diego,
`CA (US)
`12/952,706
`Nov. 23, 2010
`Related U.S. Application Data
`Provisional application No. 61/354,148, filed on Jun.
`11, 2010, provisional application No. 61/264,618,
`filed on Nov. 25, 2009.
`
`Assignee:
`
`Appl. No.:
`Filed:
`
`Inventors:
`
`Publication Classification
`
`(51) Int. Cl.
`G06O 20/00
`G07B 5/02
`
`(2006.01)
`(2011.01)
`
`(52) U.S. Cl. ........................................... 705/39; 235/384
`
`ABSTRACT
`(57)
`Embodiments of systems, methods, and devices are disclosed
`for enabling wireless mobile devices to be automatically
`detected and used as fare media on vehicles in a transit and/or
`transportation system. Embodiments include detecting a
`wireless mobile device and utilizing a unique identifier of the
`wireless mobile device to track a transit user's entry to and
`exit from a transit vehicle. Embodiments further include
`causing the wireless mobile device to display a fare payment
`indicator, allowing the transit user to use the wireless mobile
`device to show proof of payment if so solicited by a fare
`inspector. A corresponding fare can be calculated and paid for
`in a variety of ways.
`
`Financial
`institution
`
`Funding
`Source
`
`160
`
`165
`
`
`
`250
`
`
`
`20
`
`Transit
`Application
`Source
`
`Financial Network
`
`170
`
`
`
`
`
`
`
`Mobile Carrier
`Network
`
`
`
`
`
`Central
`Ticketing
`System
`
`130-1
`
`Station
`System
`
`140
`
`130-2
`
`Station
`System
`
`Station
`System
`
`130-n
`
`190
`
`Customer
`service Center
`
`Petitioner Kiosoft Exhibit 1008
`1
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 1 of 17
`
`US 2011/O153495 A1
`
`
`
`Financial
`institution
`
`160
`
`Funding
`Source
`
`165
`
`250
`
`120
`
`Transit
`Application
`Source
`
`
`
`150
`
`170
`
`Financial Network
`
`
`
`
`
`Mobile Carrier
`NetWork
`
`- - - - - - - -
`
`|- - - - - -110
`112
`?
`
`140
`
`Central
`Ticketing
`System
`
`114
`
`
`
`Central Control
`System
`
`190
`
`Customer
`Service Center
`
`F.G. 1
`
`1OO
`
`System
`
`Station
`System
`
`i.
`
`130-2
`
`O
`O
`O
`
`130-n
`
`Station
`System
`
`-
`
`Petitioner Kiosoft Exhibit 1008
`2
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 2 of 17
`
`US 2011/O153495 A1
`
`A
`
`208
`
`
`
`Fare
`Collection
`Points
`
`212
`
`Ticket
`Vending
`Machines
`
`140
`
`
`
`a
`
`224
`
`240
`
`220
`
`Ticket Booth
`Computer
`
`FIG. 2
`
`Petitioner Kiosoft Exhibit 1008
`3
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 3 of 17
`
`sIIQoN
`
`solAaq
`
`Z[IQo|
`
`S0lAaq
`
`SIQOoW|
`
`sdlAeq
`
`sIqoW|
`
`s[aTySAMSUBL],
`
`SSOOIEAA
`
`SjeoRpiaiuy
`
`
`
`BIUSAWSUCLL
`
`Jainduog
`
`algo
`
`adlAaq
`
`sd1Aaq
`
`aed
`
`Jopedsu
`
`ao1Aeq
`
`US 2011/0153495 Al
`
`Petitioner Kiosoft Exhibit 1008
`4
`
`Petitioner Kiosoft Exhibit 1008
`4
`
`
`

`

`Patent Application Publication
`
`
`
`089089
`
`
`
`
`
`Petitioner Kiosoft Exhibit 1008
`5
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 5 of 17
`
`US 2011/O153495 A1
`
`
`
`Petitioner Kiosoft Exhibit 1008
`6
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 6 of 17
`
`US 2011/O153495 A1
`
`
`
`
`
`
`
`
`
`
`
`Petitioner Kiosoft Exhibit 1008
`7
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 7 of 17
`
`US 2011/O153495 A1
`
`420
`
`APC
`
`y"
`
`470
`
`Proximity
`Sensor(s)
`
`41 O
`
`
`
`325
`
`Processor
`
`Act
`
`LOCation
`Module
`
`CMemory
`
`430
`
`450
`
`
`
`453
`
`455
`
`Identifier/
`Validation
`Information
`Security/
`Encryption
`457-1NSAA e
`
`Motion
`Sensor(s)
`
`460
`
`440
`
`WAN Interface
`
`FIG. 4
`
`Petitioner Kiosoft Exhibit 1008
`8
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 8 of 17
`
`US 2011/O153495 A1
`
`J. 51O
`
`information Sources For
`Determining Location
`?. 511
`
`
`
`Mobile Device :
`: GPSData
`-. 512
`... . . . . . . . -- . . . . . . .
`: Mobile Device:
`: ACCelerometer: - .
`Data
`a
`a
`?. 513
`
`
`
`:Transit Vehicle:
`Route
`Information :
`?. 514
`
`sea e o see e s a es e s a
`
`Transit Vehicle:
`GPS Data
`
`J. 515
`Distance? ":
`:
`: Triangulation :
`k
`Data
`i
`
`r.
`: Other Data : :
`Sources
`...
`
`1. 530
`: Local/Remote
`
`: Verification
`
`. ..............."
`
`Transit Vehicle
`Computer
`O
`
`
`
`
`
`330
`
`Fare Inspector
`Device
`
`250
`
`540
`
`Mobile Device
`
`e s s a se e s is a s a 1.
`
`:Transit Service:
`: Provider Data :
`
`FIG. 5
`
`Petitioner Kiosoft Exhibit 1008
`9
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 9 of 17
`
`US 2011/O153495 A1
`
`FG. 6A
`
`
`
`250
`
`630
`
`330
`
`ID: 1289A}640
`
`4567B
`8485C
`4939D
`958SG
`
`650
`
`Late Arriving
`1.
`289A
`
`660
`
`F.G. 6B
`
`Petitioner Kiosoft Exhibit 1008
`10
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 10 of 17
`
`US 2011/O153495 A1
`
`705
`
`Detect New
`Mobile
`Device
`
`725
`
`720
`
`710
`
`
`
`Ignore
`
`N (> Y
`
`N
`
`715
`
`Collect
`Additional
`Location
`Information
`
`745
`
`Y
`
`750
`
`Y
`
`730
`
`
`
`N
`
`lag f
`OSSOe
`Fraud
`
`785................. ria
`Send
`: Information :
`: To Inspector
`
`e 8 e i se e s - e. e. e s see e
`
`Log Entry
`Evcnt
`
`Collect
`Additional
`Location
`Information
`
`Vehicle?
`
`N
`
`760
`
`765
`
`770
`
`775
`
`Calculate
`Fare
`
`Send Fare Charge
`To Mobile Carrier
`Network
`
`Send User/Fare
`Information To
`Central Control
`SVStem
`
`
`
`
`
`
`
`FIG 7A
`
`Petitioner Kiosoft Exhibit 1008
`11
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 11 of 17
`
`US 2011/0153495 A1
`
`
`
`705
`
`Detect New
`Mobile
`Device
`
`Mobile
`Device
`Registered
`
`707
`
`710
`
`Ignore
`
`725
`
`720
`
`Y
`
`710
`
`
`
`715
`
`Ignore
`
`N
`
`Y
`
`N
`
`Collect
`Additional
`Location
`Information
`
`
`
`
`
`Notify
`4.
`Transit User
`Of Entry
`-
`
`Collect
`
`750
`
`Additional
`y r,
`Location
`Information
`
`Flag For
`Possible
`Fraud
`
`Send
`:
`: Information :
`: To Fare
`:
`Inspector :
`
`
`
`760
`
`763
`
`767
`
`Send USer/Fare
`Information To
`Central Control
`Svstem
`
`Notify
`Transit User
`Of Charge
`
`FIG. 7B
`
`Petitioner Kiosoft Exhibit 1008
`12
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 12 of 17
`
`US 2011/O153495 A1
`
`Instantiate Rider List
`
`Detect Riders
`
`Add Riders To Rider List
`
`Retrieve Head Count Data
`
`Compare Rider List To Head
`Count Data
`
`Report And/Or Log Findings
`
`
`
`Flag Data And/Or Notify Fare
`Inspector If Over A Certain
`Threshold
`
`810
`
`820
`
`830
`
`840
`
`850
`
`860
`
`870
`
`FIG. 8
`
`Petitioner Kiosoft Exhibit 1008
`13
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 13 of 17
`
`US 2011/0153495 A1
`
`Mobile Device
`
`Transit Vehicle
`Computer
`
`Central Control
`System
`
`910
`
`915
`
`Transmit Unique
`Identifier
`
`925
`Establish Connection
`With Transit Vehicle
`Computer
`
`Detect Entry Of
`Mobile Device
`
`920
`Establish Connection
`With Mobile Device
`
`930
`Verify Unique
`Identifier
`
`940
`
`935
`
`Display Fare Payment
`Indicator
`
`Send Fare Payment
`Indicator Information
`
`950
`
`Detect Exit Of Mobile
`Device
`
`955
`
`Calculate Fare
`
`960
`
`965
`
`Send Fare Charge
`Information
`
`PrOccSS Farc Data
`
`975
`Display Fare Charge
`Information
`
`970
`SESe
`Mobile Device
`
`FIG 9A
`
`Petitioner Kiosoft Exhibit 1008
`14
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 14 of 17
`
`US 2011/0153495 A1
`
`Mobile Device
`
`Transit Vehicle
`Computer
`
`Central Control
`System
`
`910
`
`915
`
`Transmit Unique
`identifier
`
`925
`Ethy
`
`Computer
`
`940
`
`Detect Entry Of
`Mobile Device
`920
`Establish Connection
`
`With Mobile Device
`
`Send Unique
`Identifier For
`X
`Verification
`
`933
`
`935
`
`931
`Access Account
`
`Information
`
`932
`
`Display Fare Payment
`Indicator
`
`Send Fare Payment
`Indicator Information
`
`Return Verification
`Information
`
`950
`
`Detect Exit Of Mobile
`Device
`
`961
`
`963
`
`Send USer/Fare Data
`
`Calculate Fare
`
`
`
`965
`
`Process Fare Data
`
`
`
`
`
`973
`Send Fare Charge
`Information To
`Transit User
`
`FIG. 9B
`
`Petitioner Kiosoft Exhibit 1008
`15
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 15 of 17
`
`US 2011/O153495 A1
`
`Mobile Device
`
`Transit Vehicle
`Computer
`
`Central Control
`System
`
`910
`
`917
`
`Transmit Unique
`Identifier
`
`Detect Possible Entry
`Of Mobile Device
`
`923
`
`920
`
`Prompt Transit User
`Confirmation of Entry
`
`Establish Connection
`With Mobile Device
`
`927
`
`Receive Transit User
`Confirmation
`
`940
`Display Fare Payment
`Indicator
`
`952
`
`Prompt Transit User
`Confirmation of Exit
`
`930
`Verify Unique
`Identifier
`
`935
`
`Send Fare Payment
`Indicator Information
`
`950
`
`Detect Exit Of Mobile
`Device
`
`95 1
`
`
`Send Information
`Regarding Detected
`Exit
`
`953
`
`955
`
`Receive Transit User
`Confirmation
`
`Calculate Fare
`
`964
`Send Fare Charge To
`Mobile Carrier
`Network
`
`975
`Display Fare Charge
`Information
`
`974.
`
`965
`
`Send Fare Charge
`Information
`
`FIG. 9C
`
`Process Fare Data
`
`Petitioner Kiosoft Exhibit 1008
`16
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 16 of 17
`
`US 2011/0153495 A1
`
`
`
`Receive Indication That Mobile
`Device May Be On Transit
`Vehicle
`
`Receive Update Transit
`Information
`
`Display Updated Transit
`Information And Fare Payment
`Indicator
`
`Receive Indication That Mobile
`Device May Have Exited Transit
`Vehicle
`
`Receive Fare Charge Information
`
`Display Fare Charge Information
`
`1010
`
`1020
`
`1030
`
`1040
`
`1050
`
`1060
`
`FIG 10A
`
`Petitioner Kiosoft Exhibit 1008
`17
`
`

`

`Patent Application Publication
`
`Jun. 23, 2011 Sheet 17 of 17
`
`US 2011/0153495 A1
`
`Request User Confirmation
`- - - - T - - -
`-- r
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`1045
`
`Send User Confirmation
`- - - - - - -
`
`Receive Fare Charge Information
`
`1043
`
`105O
`
`1060
`
`1070
`
`1075
`
`Detect Proximity Of Transit
`Vehicle
`
`Open User Interface
`
`Receive Indication That Mobile
`Device May Be On Transit
`
`1005
`
`1 OO7
`
`
`
`1010
`
`
`
`
`
`
`
`1013
`
`Display Fare Charge Information
`
`1 O15
`L?
`o
`Send User Confirmation
`- - - - - - -
`
`Detect Transit Vehicle Is No
`Longer Proximate
`
`Close User Interface
`
`Receive Updated Transit
`Information
`
`Display Updated Transit
`Information And Fare Payment
`Indicator
`
`Receive Indication That Mobile
`Device May Have Exited Transit
`Vehicle
`
`FIG. 1 OB
`
`Petitioner Kiosoft Exhibit 1008
`18
`
`

`

`US 2011/O153495 A1
`
`Jun. 23, 2011
`
`MOBILE WIRELESS PAYMENT AND ACCESS
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`0001. This application is related to and claims the benefit
`of U.S. Provisional Patent Application No. 61/264,618 filed
`Nov. 25, 2009 by deKozan et al. and entitled “Mobile Wire
`less Payment and Access' and U.S. Provisional Patent Appli
`cation No. 61/354,148 filed Jun. 11, 2010 by Dixon et al. and
`entitled "Be-InBe-Out' all of which the entire disclosures of
`each are incorporated herein by reference for all purposes.
`
`BACKGROUND OF THE INVENTION
`0002 This invention relates to automatic payment using
`wireless mobile devices and, in particular, to said automatic
`payments in transit and/or transportation systems.
`0003 Transit systems typically limit access to transit
`vehicles based on two methods: barrier and proof of payment.
`The barrier method usually requires transit users to Swipe,
`tap, or otherwise present fare media at an access control point,
`Such as a turnstile, of the transit system to gain entry to and/or
`exit from an area or vehicle of the transit system. On the other
`hand, the proof of payment method generally permits transit
`users to gain entry to and/or exit from an area or vehicle of the
`transit System, but requires transit users to provide proof of
`payment if solicited to do so by a fare inspector.
`0004 Both barrier and proof of payment methods typi
`cally use impersonalized fare media issued by the transit
`service provider. Fare media often includes, for example,
`tickets (which may need to be validated), stored value smart
`cards, magnetic stripe cards, etc. Because this fare media is
`typically issued by the transit service provider, it requires
`transit users to purchase new fare media or reload used fare
`media from the transit service provider to access the transit
`system. Moreover, the tickets and/or cards typically used as
`fare media are often lost or stolen, leading to loss of value to
`the transit user, the transit service provider, or both.
`
`BRIEF SUMMARY OF THE INVENTION
`0005 Embodiments of systems, methods, and devices are
`disclosed for enabling wireless mobile devices to be auto
`matically detected and used as fare media on vehicles in a
`transit and/or transportation system. Embodiments include
`detecting a wireless mobile device and utilizing a unique
`identifier of the wireless mobile device to trackatransit user's
`entry to and exit from a transit vehicle. Embodiments further
`include causing the wireless mobile device to display a fare
`payment indicator, allowing the transit user to use the wire
`less mobile device to show proof of payment if so solicited by
`a fare inspector. A corresponding fare can be calculated and
`paid for in a variety of ways.
`0006. According to one embodiment, a method is pro
`vided for enabling automatic fare paymentina transit System.
`The method comprises providing a transit vehicle computer
`on a transit vehicle, where the transit vehicle computer has a
`wireless interface. The method further includes using the
`wireless interface to receive a unique identifier associated
`with a mobile device and determine that the mobile device has
`entered the transit vehicle. The wireless interface further can
`be used to send information regarding a fare payment indica
`tor to the mobile device. This information can cause the
`mobile device to show the fare payment indicator on the
`mobile device's display it is determined the mobile device has
`
`exited the transit vehicle. The method can further comprise
`using the wireless interface to determine the mobile device
`has exited the transit vehicle and calculating a fare associated
`with the unique identifier.
`0007 Numerous variations of this embodiment are con
`templated. For example, determining that the mobile device
`has entered and/or exited the vehicle can include receiving a
`first communication from the mobile device when the transit
`vehicle is at a first location, and receiving a second commu
`nication from the mobile device when the transit vehicle is at
`a second location. Additionally or alternatively, the method
`can include sending information associated with the fare to a
`mobile device, a wireless carrier network, a central server of
`the transit system, or any combination thereof. Moreover,
`where the fare payment indicator is a first fare payment indi
`cator, the wireless interface can be used to send additional
`information to the mobile device that causes the mobile
`device to show a second fare payment indicator on the
`device's display.
`0008. This embodiment may also provide interaction with
`a fare inspector device. For instance, the method can include
`using the wireless interface to send inspection information to
`a fare inspector device. This inspection information can cause
`the fare inspector device the fare payment indicator on the
`fare inspector device's display. Additionally or alternatively,
`the method can include determining that a second mobile
`device is already in the transit vehicle and sending informa
`tion to a fare inspector device to indicate possible fraud asso
`ciated with the second mobile device. Moreover, the infor
`mation sent to the fare inspector device can include a unique
`identifier associated with the second mobile device.
`0009. Yet other variations of this embodiment are contem
`plated. For instance the method can include accessing iden
`tifier information from a database and determining whether
`the unique identifier is included in the identifier information.
`Additionally or alternatively information associated with the
`unique identifier can be accessed from a database. This can
`further include determining whether to send the fare payment
`indicator information to the mobile device, based, at least in
`part, on the information associated with the unique identifier.
`The method can also include using the information associated
`with the unique identifier to determine that an account asso
`ciated with the unique identifier has inadequate funds to pay
`for the fare and sending information to the mobile device
`causing the mobile device to display an indication that the
`account has inadequate funds to pay for the fare. Additionally
`or alternatively, payment information can be received from
`the mobile device.
`0010 Yet other variations are contemplated. For example,
`determining that the mobile device has entered and/or exited
`the vehicle can include using location information associated
`with the mobile device, transit vehicle, or both; movement
`information associated with the mobile device, transit
`vehicle, or both; information regarding the route of the transit
`vehicle; information received from one or more additional
`wireless devices in the transit vehicle; and/or input received
`by the mobile device from a transit user. Furthermore, the
`wireless interface can be used to send information associated
`with a current location of the transit vehicle. Finally, the fare
`calculation can be based, at least in part, on the determination
`(s) that the mobile device has entered and/or exited the transit
`vehicle, an associated location, and/or a time of day.
`0011. According to an alternate embodiment, a system is
`provided for enabling automatic fare payment in transit. The
`
`Petitioner Kiosoft Exhibit 1008
`19
`
`

`

`US 2011/O153495 A1
`
`Jun. 23, 2011
`
`system can comprise a wireless interface configured to com
`municate with a mobile device on a transit vehicle, a proces
`sor communicatively coupled with the wireless interface and
`a memory, and the memory. The memory can have instruc
`tions embodied therein which, when executed by the proces
`Sor, cause the system to use the wireless interface to receive a
`unique identifier associated with the mobile device and deter
`mine that the mobile device has entered the transit vehicle.
`The wireless interface can be further used to send fare pay
`ment indicator information to the mobile device, which
`causes the mobile device to show a fare payment indicator on
`the mobile device's display. The fare payment indicator can
`be displayed by the mobile device before the processor deter
`mines the mobile device has exited the transit vehicle. The
`instructions can further cause the system to determine that the
`mobile device has exited the transit vehicle and calculate a
`fare associated with the unique identifier.
`0012. As described herein, numerous variations to this
`embodiment are contemplated. For example, determining
`that the mobile device has entered and/or exited can include
`receiving a first communication from the mobile device when
`the transit vehicle is at a first location and receiving a second
`communication from the mobile device when the transit
`vehicle is at a second location. Moreover, the system further
`can comprise a location module communicatively coupled
`with the processor that provides location information of the
`transit vehicle. In fact, the instructions, when executed by the
`processor, further can cause the system to send information
`associated with a current location of the transit vehicle. Addi
`tionally or alternatively, at least one motion sensor can be
`communicatively coupled with the processor provide to
`motion information of the transit vehicle.
`0013 Yet other alterations to the system are contemplated.
`One Such alteration includes having instructions, when
`executed by the processor, further causing the system use the
`wireless interface to send additional information to the
`mobile device. This additional information can cause the
`mobile device to show a second fare payment indicator on the
`mobile device's display. Additionally or alternatively, the
`wireless interface may be used to send information to a fare
`inspector device. This information can cause the fare inspec
`tor device to show the fare payment indicator on its display. In
`fact, the information sent to the fare inspector device can also
`cause the fare inspector device to show the unique identifier of
`the mobile device on the fare inspector device's display.
`Moreover, the instructions, when executed by the processor,
`can further cause the system to access identifier information
`from a database and determine whether the unique identifier
`is included in the identifier information. The memory can also
`information regarding fare rates, and calculating the fare can
`include retrieving the information regarding fare rates from
`the memory.
`0014. The system also can include a wide area network
`(WAN). The instructions, for instance, further can cause the
`system to use the WAN interface to send information associ
`ated with the fare to a wireless carrier networkassociated with
`the mobile device. Additionally or alternatively, calculating
`the fare can comprise using the WAN interface to retrieve
`information from a database not located in the transit vehicle.
`This can include information associated with the unique iden
`tifier. Moreover, the system can use the information associ
`ated with the unique identifier to determine that an account
`associated with the unique identifier has inadequate funds to
`pay for the fare, sending information to the mobile device to
`
`cause the mobile device to display and indication that the
`account has inadequate funds to pay for the fare. With this in
`mind, the system can also receive payment information from
`the mobile device.
`0015 The system can include yet more features. Deter
`mining that the mobile device has entered and/or exited the
`vehicle can include, for example, using location information
`associated with the mobile device, transit vehicle, or both;
`movement information associated with the mobile device,
`transit vehicle, or both; information regarding the route of the
`transit vehicle; information received from one or more addi
`tional wireless devices in the transit vehicle; and/or input
`received by the mobile device from a transit user. Addition
`ally or alternatively, the fare can be based on the determina
`tion that the mobile device has entered the transit vehicle, the
`determination that the mobile device has exited the transit
`vehicle, a location associated with the determining that the
`mobile device has entered the transit vehicle, a location asso
`ciated with the determining that the mobile device has entered
`the transit vehicle, and/or a time of day.
`0016. An additional embodiment includes a mobile device
`for enabling automatic fare payment in transit. This mobile
`device can comprise a wireless interface allowing communi
`cation with a system on a transit vehicle, a display, a processor
`communicatively coupled with the wireless interface, the dis
`play, and a memory. The memory can have instructions
`embodied therein which, when executed by the processor,
`cause the mobile device to use the wireless interface to send
`a unique identifier associated with the mobile device. It can
`also use the wireless interface to receive an indication that the
`mobile device is on the transit vehicle and receive fare pay
`ment indicator information. The mobile device further can
`show a fare payment indicator on the display, where the fare
`payment indicator is based, at least in part, on the fare pay
`ment indicator information. The fare payment indicator can
`be shown on the display before the mobile device receives an
`indication that the mobile device has exited the transit
`vehicle. The mobile device can further receive, using the
`wireless interface, an indication that the mobile device has
`exited the transit vehicle.
`0017. As with the other embodiments described herein,
`various alterations and/or additions are contemplated. If, for
`example, where the fare payment indicator information com
`prise a first set of fare payment indicator information and the
`fare payment indicator comprises a first fare payment indica
`tor, the mobile can use the wireless interface to receive a
`second set of fare payment indicator information and show a
`second fare payment indicator on the display. The second fare
`payment indicator can be based, at least in part, on the second
`set of fare payment indicator information, and shown on the
`display before the mobile device receives the indication that
`the mobile device has exited the transit vehicle.
`0018. The mobile device can include other features in
`addition, or as an alternative, to those discussed above. For
`instance, the mobile device can include a location module
`communicatively coupled with the processor that provides
`location information associated with the mobile device. The
`mobile device can therefore send the location information
`associated with the mobile device. Additionally or alterna
`tively, the instructions, when executed by the processor, fur
`ther can cause the mobile device to use the wireless interface
`to receive information associated with a current location of
`the transit vehicle and show information on the display based,
`at least in part, on the information associated with the current
`
`Petitioner Kiosoft Exhibit 1008
`20
`
`

`

`US 2011/O153495 A1
`
`Jun. 23, 2011
`
`location of the transit vehicle. Moreover, the mobile device
`can include at least one motion sensor, communicatively
`coupled with the processor, that provides motion information
`associated with the mobile device. The mobile device can
`therefore send the motion information associated with the
`mobile device. Finally, the mobile device can include a user
`input interface, allowing the instructions, when executed by
`the processor, to further cause the mobile device to use the
`wireless interface to receive an indication that an account
`associated with the unique identifier has inadequate funds,
`receive payment information, and send the payment informa
`tion.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0019 FIG. 1 is a block diagram of an embodiment of a
`transit system providing transit user accounts for manage
`ment of transactions of a transit user.
`0020 FIG. 2 is a block diagram of an embodiment of a
`transit station system.
`0021
`FIG. 3A is a simplified block illustration of a transit
`vehicle with a wireless detection Zone, according to certain
`embodiments.
`0022 FIG. 3B is a simplified block illustration of a gated
`access area with a wireless detection Zone, according to cer
`tain embodiments.
`0023 FIG. 3C is a simplified block illustration of a non
`gated access area with a wireless detection Zone, according to
`certain embodiments.
`0024 FIG. 3D is a simplified block illustration of a toll
`area with a wireless detection Zone, according to certain
`embodiments.
`0025 FIG. 4 is a block diagram of an embodiment of a
`transit vehicle computer that can be used to establish a wire
`less detection Zone and/or otherwise facilitate wireless fare
`collection.
`0026 FIG. 5 is a block diagram illustrating information
`sources which can be utilized by a transit vehicle computer,
`according to some embodiments.
`0027 FIG. 6A is a simplified illustration of how a mobile
`device can display different fare payment indicators at differ
`ent times, according to some embodiments.
`0028 FIG. 6B is a simplified illustration of how, according
`to some embodiments, a fare inspector device can display the
`fare payment indicator, list unique identifiers associated with
`mobile devices, and indicate possible fraud of certain mobile
`devices.
`0029 FIG. 7A is flow chart of a method for determining a
`mobile device is on a transit vehicle and calculating a corre
`sponding fare, according to Some embodiments.
`0030 FIG. 7B is flow chart of an alternative method for
`determining a mobile device is on a transit vehicle and cal
`culating a corresponding fare, according to some embodi
`mentS.
`FIG. 8 is a simplified diagram for inventorying pas
`0031
`sengers on a transit vehicle and detecting possible fraud,
`according to some embodiments.
`0032 FIG. 9A is swim-lane diagram illustrating an
`embodiment of how a mobile device, transit vehicle com
`puter, and central control system can interact to provide wire
`less fare payment.
`0033 FIG.9B is swim-lane diagram illustrating an alter
`native embodiment of how a mobile device, transit vehicle
`computer, and central control system can interact to provide
`wireless fare payment.
`
`0034 FIG. 9C is swim-lane diagram illustrating yet
`another embodiment how a mobile device, transit vehicle
`computer, and central control system can interact to provide
`wireless fare payment.
`0035 FIG. 10A is diagram illustrating the functionality of
`a transit application executed by a mobile device, according
`to one embodiment.
`0036 FIG. 10B is diagram illustrating the functionality of
`a transit application executed by a mobile device, according
`to an alternative embodiment.
`
`DETAILED DESCRIPTION OF THE INVENTION
`0037. In the following description, for the purposes of
`explanation, numerous specific details are set forth in order to
`provide a thorough understanding of various embodiments. It
`will be apparent, however, to one skilled in the art that various
`embodiments may be practiced without Some of these spe
`cific details. In other instances, well-known structures and
`devices are shown in block diagram form.
`0038 Specific details are given in the following descrip
`tion to provide a thorough understanding of the embodiments.
`However, it will be understood by one of ordinary skill in the
`art that the embodiments may be practiced without these
`specific details. For example, circuits, systems, networks,
`processes, and other components may be shown as compo
`nents in block diagram form in order not to obscure the
`embodiments in unnecessary detail. In other instances,
`known circuits, processes, algorithms, structures, and tech
`niques may be shown without unnecessary detail in order to
`avoid obscuring the embodiments.
`0039. Also, it is noted that individual embodiments may
`be described as a process which is depicted as a flowchart, a
`flow diagram, a data flow diagram, a structure diagram, or a
`block diagram. Although a flowchart may describe the opera
`tions as a sequential process, many of the operations can be
`performed in parallel or concurrently. In addition, the order of
`the operations may be re-arranged. A process is terminated
`when its operations are completed, but could have additional
`steps not included in a figure. A process may correspond to a
`method, a function, a procedure, a Subroutine, a Subprogram,
`etc. When a process corresponds to a function, its termination
`can correspond to a return of the function to the calling
`function or the main function.
`0040. Furthermore, embodiments may be implemented by
`hardware, Software, firmware, middleware, microcode, hard
`ware description languages, or any combination thereof.
`When implemented in software, firmware, middleware or
`microcode, the program code or code segments to perform the
`necessary tasks may be stored in a machine readable medium.
`A processor(s) may perform the necessary tasks.
`0041
`Embodiments of the invention described herein are
`directed to enabling a transit and/or transportation vehicle
`(such as a bus, light rail, commuter rail, trolley, etc.) to detect
`mobile devices configured for wireless communication and
`determine if, when, and where such mobile devices enter and
`exit the transit vehicle. With this information, an associated
`fare may be calculated and charged in any of a variety of
`ways. Moreover, information may be sent to the mobile
`device to provide proof of fare payment. This ultimately
`allows transit users having mobile devices to use the mobile
`devices instead of traditional fare media (e.g., fare cards,
`tickets, etc.). In fact, little or no action and/or input may be
`required by the transit user—other than entering and exiting
`the transit vehicle.
`
`Petitioner Kiosoft Exhibit 1008
`21
`
`

`

`US 2011/O153495 A1
`
`Jun. 23, 2011
`
`0042. The term “fare used herein can be interpreted
`broadly to mean any type of value or other indicator associ
`ated with a transaction, Such as a ride, in a transit System. Fare
`payment therefore can mean any form of fare settlement, Such
`as a monetary payment, debit and/or credit to an account,
`and/or any other type of conveyance of value. It should be
`known that a fare can be based on any of a variety of factors,
`Such as distance, time (e.g., time of day, length of time, et