US9441981B2

US9441981B2 - Variable bus stops across a bus route in a regional transportation network

Info

Publication number: US9441981B2
Application number: US14/309,912
Authority: US
Inventors: Raj Abhyanker
Original assignee: Fatdoor Inc
Current assignee: Individual
Priority date: 2014-06-20
Filing date: 2014-06-20
Publication date: 2016-09-13
Also published as: US20150369621A1

Abstract

Disclosed are a method and a system of variable bus stops across a bus route in a regional transportation network, according to one embodiment. A method of a bus server includes analyzing a current geospatial location of a mobile device responsive to a pick up request of a prospective bus passenger, associating a closest street intersection with the current geospatial location of the mobile device, and determining if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. A message may be communicated to the mobile device based on the determination of whether the bus route traverses the closest street intersection. A bus associated with the bus route may be instructed to pick up the prospective bus passenger when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device.

Description

FIELD OF TECHNOLOGY

This disclosure relates generally to the technical fields of communications and, in one example embodiment, to a method, apparatus, and system of variable bus stops across a bus route in a regional transportation network.

BACKGROUND

Individuals may rely on buses in order to accomplish daily tasks (e.g., to get to and/or from work and/or to run errands). Bus stops may not be properly located in order to address changing demands of bus passengers and/or may make it difficult for individuals to effectively use the bus. It may be inefficient for buses and/or bus passengers to use set bus stops along a route as effective pick up locations and/or drop off locations may vary drastically on an hourly, daily, and/or yearly basis.

SUMMARY

A method, device and system of variable bus stops across a bus route in a regional transportation network. In one aspect, a method of a bus server includes analyzing a current geospatial location of a mobile device responsive to a pick up request of a prospective bus passenger, associating a closest street intersection with the current geospatial location of the mobile device, and determining if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. A message may be communicated to the mobile device based on the determination of whether the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device.

A bus associated with the bus route may be instructed to pick up the prospective bus passenger at the closest street intersection on the bus route when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. An estimated time of arrival of the bus may be communicated to the prospective bus passenger through the message. The bus may only traverse the bus route in a unidirectional looping fashion (such that a particular bus on the bus route for which the closest street intersection is in a forward path of the particular bus is closest is preferred, as compared to other buses on the bus route that have already departed from the closest street intersection in forward journey on the bus route). The particular bus may be an autonomously navigating vehicle and/or a semiautonomously navigating vehicle.

Walking directions may be provided to the prospective bus passenger to the closest street intersection on the bus route. The mobile device may be periodically pinged to provide pickup updates to the prospective bus passenger based on a request of the prospective bus passenger. Multiple ones of the prospective bus passengers in a neighborhood of a current geospatial vicinity of the prospective bus passenger may be routed to a common intersection point that is within a threshold distance from each of the prospective bus passengers of the neighborhood to minimize delays of the particular bus on the bus route. The closest street intersection may be associated with an address that provides for safe navigation of the particular bus on the bus route, such that the particular bus is able to make a pit stop at a safe stopping location when picking up the prospective bus passenger.

A bus fare associated with a route of the bus may be settled directly on the mobile device of the prospective bus passenger prior to the prospective bus passenger boarding the bus. The bus fare may be dependent upon a distance desired to be travelled by the prospective bus passenger. The prospective bus passenger may select a drop off location using the mobile device. The drop off location may be a scheduled bus stop, a custom bus stop, and/or a shared ad-hoc bus stop with other current and prospective bus passengers on the bus route. The prospective bus passenger may pay a premium when the prospective bus passenger selects the custom bus stop on the bus route. The particular bus may be routed to the closest street intersection only when the bus fare is paid on the mobile device. The particular bus may open a door of the bus when the prospective bus passenger swipes the mobile device on a reader of the particular bus when the bus fare has been paid with the mobile device by the prospective bus passenger.

In another aspect, a method of a bus sever includes analyzing a current geospatial location of a mobile device responsive to a pick up request of a prospective bus passenger, associating a closest street intersection with the current geospatial location of the mobile device, and determining if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. The method also includes instructing a bus associated with the bus route to pick up the prospective bus passenger at the closest street intersection on the bus route when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. A message may be communicated to the mobile device based on the determination of whether the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device.

In yet another aspect, a system includes a mobile device having a current geospatial location, a network, and a bus server. The bus server is configured to analyze the current geospatial location of the mobile device responsive to a pick up request of a prospective bus passenger, associate a closest street intersection with the current geospatial location of the mobile device, determine if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device, and communicate, through the network, a message to the mobile device based on the determination of whether the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device.

A pick-up algorithm may instruct a bus associated with the bus route to pick up the prospective bus passenger at the closest street intersection on the bus route when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device. A time-of-arrival algorithm may communicate an estimated time of arrival of the bus to the prospective bus passenger through the message. The bus may only traverse the bus route in a unidirectional looping fashion (such that a particular bus on the bus route for which the closest street intersection is in a forward path of the particular bus is closest is preferred, as compared to other buses on the bus route that have already departed from the closest street intersection in forward journey on the bus route). The particular bus may be an autonomously navigating vehicle, and/or a semiautonomously navigating vehicle.

A direction algorithm may provide walking directions to the prospective bus passenger to the closest street intersection on the bus route. An update algorithm may periodically ping the mobile device to provide pickup updates to the prospective bus passenger based on a request of the prospective bus passenger. A rally algorithm may route multiple ones of the prospective bus passengers in a neighborhood of a current geospatial vicinity of the prospective bus passenger to a common intersection point that is within a threshold distance from each of the prospective bus passengers of the neighborhood to minimize delays of the particular bus on the bus route.

The closest street intersection may be associated with an address that provides for safe navigation of the particular bus on the bus route (such that the particular bus is able to make a pit stop at a safe stopping location when picking up the prospective bus passenger). A payment algorithm may directly settle a bus fare associated with a route of the bus on the mobile device of the prospective bus passenger prior to the prospective bus passenger boarding the bus. The bus fare may be dependent upon a distance desired to be travelled by the prospective bus passenger.

The prospective bus passenger may select a drop off location using the mobile device. The drop off location may be a scheduled bus stop, a custom bus stop, and/or a shared ad-hoc bus stop with other current and prospective bus passengers on the bus route. The prospective bus passenger may pay a premium when the prospective bus passenger selects the custom bus stop on the bus route. The particular bus may be routed to the closest street intersection only when the bus fare is paid on the mobile device. The particular bus may open a door of the bus when the prospective bus passenger swipes the mobile device on a reader of the particular bus when the bus fare has been paid with the mobile device by the prospective bus passenger.

The methods, systems, and apparatuses disclosed herein may be implemented in any means for achieving various aspects, and may be executed in a form of a machine-readable medium embodying a set of instructions that, when executed by a machine, cause the machine to perform any of the operations disclosed herein. Other features will be apparent from the accompanying drawings and from the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a regional transportation network view of a bus server receiving a pick-up request sent by a mobile device of a prospective bus passenger and communicating a message based on the pick-up request to the mobile device of the prospective bus passenger, according to one embodiment.

FIG. 2 is an exploded view of the bus server of FIG. 1, according to one embodiment.

FIG. 3 is a table view illustrating data relationships between the prospective bus passenger, the pick-up request, and the message of FIG. 1, according to one embodiment.

FIG. 4 is a critical path view illustrating a flow based on time where the prospective bus passenger with the mobile device sends pick-up request to the bus server of FIG. 1 and a message is communicated to the mobile device, according to one embodiment.

FIG. 5 is a schematic view of a unidirectional looping fashion of a bus route illustrating a forward path of a particular bus, according to one embodiment.

FIG. 6A is a user interface view displaying the pick-up request sent by the mobile device associated with the prospective bus passenger to the bus server of FIG. 1, according to one embodiment.

FIG. 6B is a user interface view displaying a message sent by the bus server to the mobile device associated with the prospective bus passenger of FIG. 1, according to one embodiment.

FIG. 7 is a graphical process flow of variable bus stops across the bus route in a regional transportation network, according to one embodiment.

FIG. 8 is a process flow detailing the operations involving variable bus stops across the bus route in a regional transportation network of FIG. 1, according to one embodiment.

Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.

DETAILED DESCRIPTION

Disclosed are a method and system of variable bus stops across the bus route in a regional transportation network. FIG. 1 is a regional transportation network view 150 of a bus server receiving a pick-up request sent by a mobile device of a prospective bus passenger and communicating a message based on the pick-up request to the mobile device of the prospective bus passenger, according t6 one embodiment. In particular, FIG. 1 shows a bus server 100, a network 101, a memory 102, a processor 104, a database 106, a prospective bus passenger 108, a mobile device 110, a closest street intersection 112, a pick-up request 114, a current geo-spatial location 116, a message 118, a bus 120, a bus route 122, a geo-spatial vicinity 124, and a threshold distance 126.

FIG. 1 illustrates a number of operations between the bus server 100, the prospective bus passenger 108, and the bus 120. Particularly, circle ‘1’ of FIG. 1 illustrates the pick-up request 114 being communicated from the mobile device 110 associated with the prospective bus passenger 108 to the bus server 100 through the network 101 (e.g., an Internet protocol network and/or a wide area network). The pick-up request 114 may include the current geo-spatial location 116 of the mobile device 110, a desired pick up time, a distance 308 desired to be traveled, a drop off location 306, and/or a desired bus fare 310. The mobile device 110 (e.g., a smartphone, a tablet, a laptop, a location service enabled portable device, and/or a personal planner) may communicate the pick-up request 114 through a network (e.g., the network 101 and/or a cellular network) using a browser application of the mobile device 110 (e.g., Google®, Chrome) and/or through a client-side application downloaded to the mobile device 110 (e.g., a Nextdoor.com mobile application, a Fatdoor.com mobile application). The prospective bus passenger 108 may be able to communicate the pick-up request 114 from any location (e.g., by indicating a future desired pick up location 302).

Circle ‘2’ shows the message 118 being communicated by the bus server 100 to the mobile device 110 associated with the prospective bus passenger 108. The message 118 may be generated, using the processor 104 and the memory 102, based on the pick-up request 114 communicated by the prospective bus passenger 108. The bus server 100 may analyze the current location of the mobile device 110, associate the current geo-spatial location 116 of the mobile device 110 with the closest street intersection 112, determine if a bus route 122 traverses the closest street intersection 112, and/or instruct a bus 120 that traverses the bus route 122 to pick up the prospective passenger at the closest street intersection 112.

The message 118 may be communicated to the mobile device 110 through the network 101. In one embodiment, the message 118 may include the closest street intersection 112 (e.g., an address associated with the closest street intersection 112), the bus fare 310, the estimated time of arrival 304, walking direction from the current geo-spatial location 116 to the closest street intersection 112, and/or a unique identifier of the bus 120 that will pick up the prospective bus passenger 108 (e.g., a bus number). The bus server 100 may simultaneously communicate a set of instructions through the network 101 to the bus 120 (e.g., the bus associated with the bus route 122 that traverses the closest street intersection 112). The set of instructions may route the bus 120 to a safe stopping location 706 to make a pit stop 704 to pick up the prospective bus passenger 108. The bus 120 may be an autonomous vehicle and/or a semiautonomous vehicle.

In one embodiment, the bus server 100 may create shared ad-hoc bus stops by routing multiple prospective bus passengers 108 in the geo-spatial vicinity 124 (e.g., a current geo-spatial vicinity 124) of the prospective bus passenger 108 to a common intersection point (e.g., the closest street intersection 112) that is in the threshold distance 126 from each of the prospective bus passengers 108. The bus server 100 may determine if a threshold number of prospective bus passengers 108 are and/or will be at the shared ad-hoc bus stop before creating the shared ad-hoc bus stop and/or instructing the bus 120 to pick up passengers at the shared ad-hoc bus stop. Prospective bus passengers 108 may be able to request, through the pick-up request 114, a custom bus stop (e.g., the bus 120 will pick them up and/or drop them off at a requested location (e.g., the current geo-spatial location 116). In one embodiment, the prospective bus passenger 108 may be required to pay a premium 602 for a custom bus stop (e.g., a fee in addition to a bus fare 310 and/or a higher bus fare 310).

FIG. 2 is an exploded view 250 of the bus server of FIG. 1, according to one embodiment. FIG. 2 shows a pick-up algorithm 202, a time-of-arrival algorithm 204, a direction algorithm 206, an update algorithm 208, a rally algorithm 210, and a payment algorithm 212.

The pick-up algorithm 202 may generate the set of instructions to route the bus 120 to the closest street intersection 112 and/or may instruct the bus 120 associated with the bus route 122 that traverses the closest street intersection 112 to pick up the prospective bus passenger(s) 108. In one embodiment, the pick-up algorithm 202 may instruct the bus 120 to only pick up (e.g., the doors only open for) certain prospective bus passengers 108 (e.g., prospective bus passengers 108 for whom the shared ad-hoc bus stop was created and/or prospective bus passengers 108 that sent the pick-up request 114 from which the set of instructions was generated).

The time-of-arrival algorithm 204 may communicate an estimated time of arrival 304 of the bus 120 to the mobile device 110 of the perspective bus 120 passenger through the message 118. In one embodiment, the time-of-arrival algorithm 204 may communicate a time until arrival to the prospective bus passenger 108 instead of or in addition to the time of arrival of the bus 120. The direction algorithm 206 may provide walking directions 604 to the prospective bus passenger 108. The walking directions 604 may be communicated as part of the message 118 and/or may direct the prospective bus passenger 108 from the current location of the mobile device 110 to the closest street intersection 112.

The update algorithm 208 may periodically ping the mobile device 110, providing updates to the prospective bus passenger 108 based on a request of the bus 120 passenger. The pickup updates may include progress of the bus 120 (e.g., a map through which the bus 120′ progress may be viewed) and/or time remaining until the bus 120 arrives. In one embodiment, the pickup updates may be sent as text messages 118 and/or push notifications and/or may be communicated at predetermined intervals (e.g., intervals specified by the bus server 100 and/or the prospective passenger). The intervals may include time intervals, progress points of the bus 120 (e.g., when the bus 120 is a specified distance 308 and/or time away), and/or when the prospective bus passenger 108 requests the pickup update.

The rally algorithm 210 may route multiple prospective bus passengers 108 to a common intersection point (e.g., the shared ad-hoc bus stop and/or the closest street intersection 112). The common intersection point may be required to be in the threshold distance 126 from each of the multiple prospective bus passengers 108. The rally algorithm 210 may determine the common intersection point based on a threshold number of prospective bus passengers 108 that may be routed to the common intersection point, a most efficient location of the common intersection point, and/or a most efficient manner of establishing common intersection points (e.g., the manner that minimizes delays of a particular bus route 122).

The payment algorithm 212 may enable a payment (e.g., payment of the bus fare 310 and/or the premium 702) of the prospective bus passenger 108 to be processed. The prospective bus passenger 108 may make payment using the mobile device 110. The payment may be made in the pick-up request 114, in response to the message 118, and/or before the bus 120 is routed to pick up the prospective bus passenger 108. The bus fare 310 and/or premium 602 may be dependent upon the distance 308 desired to be traveled by the prospective bus passenger 108, the number of prospective bus passengers 108 to be picked up and/or dropped off at the pick-up location and/or drop-off location of the prospective bus passenger 108, and/or a size of the current and/or predicted demand placed on the bus server 100.

FIG. 3 is a table view 350 illustrating data relationships between the prospective bus passenger, the pick-up request, and the message of FIG. 1, according to one embodiment. FIG. 3 shows a pick up location 302, an estimated time of arrival 304, a drop off location 306, a distance 308, and a bus fare 310. In one embodiment, the pick-up request 114 may include the current geo-spatial location 116 (e.g., a set of geo-spatial coordinates). The pick-up request 114 may be associated with the mobile device 110 and/or the prospective bus passenger 108 associated with the mobile device 110 (e.g., the name of the prospective bus passenger 108, a profile of the prospective bus passenger 108, and/or the payment information of the prospective bus passenger 108).

The pick up location 302 may be an address (e.g., an address of a building located at the closest street intersection 112), a location name (e.g., the name of a building and/or a landmark at the closest street intersection 112 and/or a name of the closest street intersection 112 (e.g., 1^stand Main street)), and/or a set of geo-spatial coordinates. The estimated time of arrival 304 may be an estimated time of arrival 304. The estimated time of arrival 304 may be the time at which the bus 120 will arrive at the pick up location 302 provided the bus route 122 remains the same (e.g., no pit stops 704 are added) and/or the bus 120 continues at its current, scheduled, and/or predicted pace.

The estimated time of arrival 304 may be updated based on the addition of other pick up locations 302 and/or other pick-up requests 114 between the current location of the bus 120 and the pick up location 302. The updated estimated time of arrival 304 may be communicated to the prospective bus passenger 108 through pickup updates. In one embodiment, the bus server 100 may prioritize fidelity to estimated times of arrival 304 and/or pick up locations 302 that have already been communicated to prospective bus passengers 108. Additional pick-up requests 114 and/or additional pit stops 704 may not be accommodated if the bus server 100 determines that accommodation of the additional pick-up requests 114 and/or additional pit stops 704 would alter a threshold number of estimated times of arrival 304 and/or create a delay over a threshold amount. The prospective bus passenger 108 may be able to “prioritize” their pick up and/or estimated time of arrival 304, paying a premium 602 to have the bus 120 go directly to their pick up location 302 and/or to prevent the bus server 100 from delaying the estimated time of arrival 304 (e.g., preventing the bus server 100 from accommodating additional pick-up requests 114 between the current location of the bus 120 and the pick up location 302 of the prospective bus passenger 108 paying the premium 602).

The drop off location 306 may be a set of geo-spatial coordinates, a location name, and/or an address to which the prospective bus passenger 108 has requested to be taken. The distance 308 may be the distance 308 between the pick up location 302 and the drop off location 306 and/or the distance 308 the bus 120 will travel between the pick up location 302 and the drop off location 306. The bas fare may depend upon the distance 308, the nature of the pick up and/or drop off (e.g., whether the pick up location 302 and/or the drop off location 306 are custom bus stops, shared ad-hoc bus stops and/or scheduled bus stops), whether the pick up and/or drop off has been prioritized (e.g., by the prospective bus passenger 108 that requested the pick up and/or drop off), and/or a demand placed on the bus server 100 (e.g., whether the pick up and/or drop off associated with the bus fare 310 occurs at peak business hours).

FIG. 4 is a critical path view 450 illustrating a flow based on time where the prospective bus passenger with the mobile device sends pick-up request to the bus server of FIG. 1 and a message is communicated to the mobile device, according to one embodiment.

In step 402, a prospective bus passenger 108 may send a pick-up request 114 through a network 101 to a bus server 100 using the mobile device 110. The bus server 100 may then analyze a current geo-spatial location 116 of the mobile device 110 (e.g., the current geo-spatial location 116 communicated in the pick-up request 114) in step 404. The bus server 100 may associate the current geo-spatial location 116 of the mobile device 110 with a closest street intersection 112 in step 406.

In step 408, the bus server 100 may determine whether a bus route 122 traverses the closest street intersection 112. In step 410, the bus server 100 may instruct a bus 120 (e.g., by communicating a set of instructions through the network 101) to pick up the prospective bus passenger 108 at the closest street intersection 112 when the bus route 122 associated with the bus 120 is determined to traverse the closest street intersection 112. The bus server 100 may only instruct the bus 120 to pick up the prospective bus passenger 108 when the prospective bus passenger 108 has made payment of the bus fare 310 and/or premium 602 associated with the pick-up request 114. In step 412, the bus 120 may pick up the prospective bus passenger 108 at the closest street intersection 112.

FIG. 5 is a schematic view 550 of a unidirectional looping fashion of a bus route illustrating a forward path of a particular bus, according to one embodiment. FIG. 5 shows a particular bus 502, a forward path 504, and unidirectional looping fashion 506ing fashion 506. In one embodiment, buses 120 may only travel in the unidirectional looping fashion 506 such that buses 120 may only make pickups and/or drop offs at locations (e.g., pit stops 704, safe parking locations, and/or closest street intersections 112) that are in the forward path 504.

In one embodiment, the bus server 100 may prefer the nearest bus 120 to which the closest street intersection 112 is in the forward path 504 as compared to other buses 120 that have departed from the closest street intersection 112. In the example embodiment of FIG. 5, the particular bus 502 may be preferred to pick up the prospective bus passenger 108 from the closest street intersection 112 over the bus 120. While the bus 120 may be physically closer to the closest street intersection 112, the bus 120 is shown to have departed from the closest street intersection 112 such that the closest street intersection 112 is no longer in the forward path 504 of the bus 120 (or such that the closest street intersection 112 is further away from the closest street intersection 112 along the forward path 504 than is the particular bus 502).

FIG. 6A is a user interface view 650 displaying the pick-up request 114 sent by the mobile device 110 associated with the prospective bus passenger 108 to the bus server 100 of FIG. 1, according to one embodiment. In user interface A, the prospective bus passenger 108 may be able to set their pick up location 302 (e.g., a custom bus stop and/or the current geo-spatial location 116 of the mobile device 110). The user may be able to enter an intersection, an address, and/or place a pin on a map view to indicate the requested pick up location 302. The prospective bus passenger 108 may be able to select the desired drop off location 306 through similar means.

The bus server 100 may automatically determine whether a bus 120 traverses the closes street intersection and/or requested pick up location 302 and/or the prospective bus passenger 108 may query the server after inputting information on the mobile device 110. The pick-up request 114 may include a desired bus fare 310 range, a desired bus fare 310, a desired time of pick up, a desired time of drop off, and/or a desired ride duration time. In one embodiment, the prospective bus passenger 108 may be required to sign onto their profile (e.g., on Fatdoor.com) in order to submit the pick-up request 114.

FIG. 6B is a user interface view 651 displaying a message sent by the bus server to the mobile device associated with the prospective bus passenger of FIG. 1, according to one embodiment. In user interface B, the prospective bus passenger 108 may be able to view whether a bus 120 traverses the closes street intersection and/or requested pick up location 302. The mobile device 110 may display the unique identifier of the bus 120 (e.g., the bus number), the associated closest street intersection 112, the estimated time of arrival 304, the bus fare 310, the premium 602 (if applicable), and/or the walking directions 604. The prospective bus passenger 108 may be able to pay the bus fare 310 and/or premium 602 and/or contact an operator through the user interface B.

User interface C may enable the prospective user to select a payment method and/or complete the payment using the mobile device 110. The prospective user may be able to select and/or enter a credit card (e.g., a credit card for which the user has previously provided information (e.g., card number, expiration date, and/or security code), a debit card, and/or an e-banking method (e.g., account transfer, PayPal®, and/or Venmo®). User interface D may enable the prospective user to view and/or use walking directions 604 from the current geo-spatial location 116 of the mobile device 110 to the requested pick up location 302 (e.g., the closest street intersection 112). The bus 120 may be instructed to pick the prospective bus passenger 108 up at the pick up location 302 once payment has been made and/or the prospective bus passenger 108 has confirmed the ride.

FIG. 7 is a graphical process flow 750 of variable bus stops across the bus route in a regional transportation network, according to one embodiment. Particularly, FIG. 7 shows a reader 702, a pit stop 704, and a safe stopping location 706. In circle ‘1,’ the prospective bus passenger 108 may communicate the pick-up request 114 to the bus server 100. In one embodiment, the pick-up request 114 may include a comment from the prospective bus passenger 108 (e.g., that the prospective bus passenger 108 has a bicycle with them and/or requires a seat due to age and/or disability).

The bus server 100 may generate the message 118 based on the pick-up request 114 and/or communicate the message 118 to the mobile device 110 in circle ‘2.’ The prospective bus passenger 108 may indicate the desired drop off location 306 using the mobile device 110 in circle ‘3.’ In one embodiment, the prospective bus passenger 108 may indicate the desired drop off location 306 in the pick-up request 114.

In circle ‘4,’ the prospective bus passenger 108 may pay the bus fare 310 and/or premium 702 using the mobile device 110. The bus 120 may be routed to the closest street intersection 112 and/or the pick up location 302 to pick up the prospective bus passenger 108 in circle ‘5.’ In circle ‘6,’ the bus 120 may continue along the forward path 504 on the unidirectional looping fashion 506 to the closest street intersection 112.

The bus 120 may make a pit stop 704 at the safe stopping location 706 to pick up the prospective bus passenger 108. The prospective bus passenger 108 may swipe the mobile device 110 on the reader 702 of the bus 120 (e.g., the particular bus 502) in circle ‘7.’ In circle ‘8,’ the doors of the bus 120 may open in response to the mobile device 110 being swiped on the reader 702. In one embodiment, the reader 702 may sense a signal sent from the mobile device 110 and/or a code (e.g., a QR code and/or a bar code) sent to the mobile device 110 from the bus server 100. The bus 120 door may only open for prospective bus passengers 108 whom have paid the bus fare 310 and/or premium 702. The safe stopping location 706 may be a designated area (e.g., a bus stop) and/or may be a sensed location that the bus 120 has determined to be a safe stopping location 706 (e.g., using an optical sensor, a laser sensor, a radar sensor, and/or an ultrasound sensor).

FIG. 8 is a process flow 850 detailing the operations involving variable bus stops across the bus route in a regional transportation network of FIG. 1, according to one embodiment. Operation 802 may analyze a current geo-spatial location 116 of a mobile device 110 responsive to a pick-up request 114 of a prospective bus passenger 108. Operation 804 may associate a closest street intersection 112 with the current geo-spatial location 116 of the mobile device 110. Operation 806 may determine if a bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110. Operation 808 may communicate a message 118 to the mobile device 110 based on the determination of whether the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110.

Disclosed are a method and system of variable bus stops across a bus route in a regional transportation network, according to one embodiment. In one embodiment, a method of a bus server 100 includes analyzing a current geo-spatial location 116 of a mobile device 110 responsive to a pick-up request 114 of a prospective bus passenger 108, associating a closest street intersection 112 with the current geo-spatial location 116 of the mobile device 110, and determining if a bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110. A message 118 may be communicated to the mobile device 110 based on the determination of whether the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110.

A bus 120 associated with the bus route 122 may be instructed to pick up the prospective bus passenger 108 at the closest street intersection 112 on the bus route 122 when the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110. An estimated time of arrival 304 of the bus 120 may be communicated to the prospective bus passenger 108 through the message 118. The bus 120 may only traverse the bus route 122 in a unidirectional looping fashion 506ing fashion 506 (such that a particular bus 502 on the bus route 122 for which the closest street intersection 112 is in a forward path 504 of the particular bus 502 is closest is preferred, as compared to other buses 120 on the bus route 122 that have already departed from the closest street intersection 112 in forward journey on the bus route 122). The particular bus 502 may be an autonomously navigating vehicle and/or a semiautonomously navigating vehicle.

Walking directions 604 may be provided to the prospective bus passenger 108 to the closest street intersection 112 on the bus route 122. The mobile device 110 may be periodically pinged to provide pickup updates to the prospective bus passenger 108 based on a request of the prospective bus passenger 108. Multiple ones of the prospective bus passengers 108 in a neighborhood of a current geo-spatial vicinity 124 of the prospective bus passenger 108 may be routed to a common intersection point that is within a threshold distance 126 from each of the prospective bus passengers 108 of the neighborhood to minimize delays of the particular bus 502 on the bus route 122. The closest street intersection 112 may be associated with an address that provides for safe navigation of the particular bus 502 on the bus route 122, such that the particular bus 502 is able to make a pit stop 704 at a safe stopping location 706 when picking up the prospective bus passenger 108.

A bus fare 310 associated with a route of the bus 120 may be settled directly on the mobile device 110 of the prospective bus passenger 108 prior to the prospective bus passenger 108 boarding the bus 120. The bus fare 310 may be dependent upon a distance 308 desired to be travelled by the prospective bus passenger 108. The prospective bus passenger 108 may select a drop off location 306 using the mobile device 110. The drop off location 306 may be a scheduled bus stop, a custom bus stop, and/or a shared ad-hoc bus stop with other current and prospective bus passengers 108 on the bus route 122. The prospective bus passenger 108 may pay a premium 702 when the prospective bus passenger 108 selects the custom bus stop on the bus route 122. The particular bus 502 may be routed to the closest street intersection 112 only when the bus fare 310 is paid on the mobile device 110. The particular bus 502 may open a door of the bus 120 when the prospective bus passenger 108 swipes the mobile device 110 on a reader 702 of the particular bus 502 when the bus fare 310 has been paid with the mobile device 110 by the prospective bus passenger 108.

In another embodiment, a method of a bus 120 sever includes analyzing a current geo-spatial location 116 of a mobile device 110 responsive to a pick-up request 114 of a prospective bus passenger 108, associating a closest street intersection 112 with the current geo-spatial location 116 of the mobile device 110, and determining if a bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110. The method also includes instructing a bus 120 associated with the bus route 122 to pick up the prospective bus passenger 108 at the closest street intersection 112 on the bus route 122 when the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110. A message 118 may be communicated to the mobile device 110 based on the determination of whether the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110.

In yet another embodiment, a system includes a mobile device 110 having a current geo-spatial location 116, a network 101, and a bus server 100. The bus server 100 is configured to analyze the current geo-spatial location 116 of the mobile device 110 responsive to a pick-up request 114 of a prospective bus passenger 108, associate a closest street intersection 112 with the current geo-spatial location 116 of the mobile device 110, determine if a bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110, and communicate, through the network 101, a message 118 to the mobile device 110 based on the determination of whether the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110.

A pick-up algorithm 202 may instruct a bus 120 associated with the bus route 122 to pick up the prospective bus passenger 108 at the closest street intersection 112 on the bus route 122 when the bus route 122 traverses the closest street intersection 112 associated with the current geo-spatial location 116 of the mobile device 110. A time-of-arrival algorithm 204 may communicate an estimated time of arrival 304 of the bus 120 to the prospective bus passenger 108 through the message 118. The bus 120 may only traverse the bus route 122 in a unidirectional looping fashion 506ing fashion 506 (such that a particular bus 502 on the bus route 122 for which the closest street intersection 112 is in a forward path 504 of the particular bus 502 is closest is preferred, as compared to other buses 120 on the bus route 122 that have already departed from the closest street intersection 112 in forward journey on the bus route 122). The particular bus 502 may be an autonomously navigating vehicle, and/or a semiautonomously navigating vehicle.

A direction algorithm 206 may provide walking directions 604 to the prospective bus passenger 108 to the closest street intersection 112 on the bus route 122. An update algorithm 208 may periodically ping the mobile device 110 to provide pickup updates to the prospective bus passenger 108 based on a request of the prospective bus passenger 108. A rally algorithm 210 may route multiple ones of the prospective bus passengers 108 in a neighborhood of a current geo-spatial vicinity 124 of the prospective bus passenger 108 to a common intersection point that is within a threshold distance 126 from each of the prospective bus passengers 108 of the neighborhood to minimize delays of the particular bus 502 on the bus route 122.

The closest street intersection 112 may be associated with an address that provides for safe navigation of the particular bus 502 on the bus route 122 (such that the particular bus 502 is able to make a pit stop 704 at a safe stopping location 706 when picking up the prospective bus passenger 108). A payment algorithm 212 may directly settle a bus fare 310 associated with a route of the bus 120 on the mobile device 110 of the prospective bus passenger 108 prior to the prospective bus passenger 108 boarding the bus 120. The bus fare 310 may be dependent upon a distance 308 desired to be travelled by the prospective bus passenger 108.

The prospective bus passenger 108 may select a drop off location 306 using the mobile device 110. The drop off location 306 may be a scheduled bus stop, a custom bus stop, and/or a shared ad-hoc bus stop with other current and prospective bus passengers 108 on the bus route 122. The prospective bus passenger 108 may pay a premium 702 when the prospective bus passenger 108 selects the custom bus stop on the bus route 122. The particular bus 502 may be routed to the closest street intersection 112 only when the bus fare 310 is paid on the mobile device 110. The particular bus 502 may open a door of the bus 120 when the prospective bus passenger 108 swipes the mobile device 110 on a reader 702 of the particular bus 502 when the bus fare 310 has been paid with the mobile device 110 by the prospective bus passenger 108.

An example embodiment will now be described. In one example embodiment, Jane may not have access to a car and/or may live in an area that makes use of a personal vehicle unnecessary (e.g., a metropolitan city center). She may rely on public transportation to get to and/or from work. Jane may live a long distance away from a standard bus stop and/or may not have time to wait at a location for a bus 120 that is often delayed and/or full.

Jane may be able to use her smart phone to request a pick up. She may receive a message 118 informing her that bus 2 is able to pick her up at the corner one block from her apartment in 10 minutes. Jane may be able to pay the bus fare 310 using her smart phone and/or quickly and easily get to work using the bus 120. In one embodiment, Jane may be in a hurry and/or request the bus 120 drop her off right outside of her office. Jane may be able to pay a premium 702 for the custom bus stop and/or get to work on time.

In another example embodiment, Jon may be visiting a new city. He may not want to take a taxi in order to save money. He may not know the bus 120 lines in the city and/or may not want to spend time studying bus 120 loops and/or determining which bus 120 and/or bus stop he should use. Jon may send a pick-up request 114 using his mobile device 110. He may request to be taken from a popular tourist attraction to a museum.

There may be several other prospective bus passengers 108 requesting pickups around Jon's location (e.g., other people leaving the popular tourist attraction). Jon may be directed to a shared ad-hoc bus stop along with other perspective bus 120 passengers. He may be picked up very close to the tourist attraction. Several passengers on the bus 120 may be going to the same museum as Jon and/or the bus 120 may drop Jon (along with the other passengers) off right outside of the museum. By using the regional transportation network, Jon may be able to get convenient bus 120 rides in a new city without having to travel long distances to find bus stops and/or become knowledgeable of the city's bus system.

Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. For example, the various devices, algorithms, analyzers, generators, etc. described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software and/or any combination of hardware, firmware, and/or software (e.g., embodied in a machine readable medium). For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits (e.g., application specific integrated ASIC circuitry and/or in Digital Signal; Processor DSP circuitry).

In addition, it will be appreciated that the various operations, processes, and methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer system), and may be performed in any order. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims

What is claimed is:

1. A method of a bus server, comprising:

analyzing a current geospatial location of a mobile device responsive to a pick up request of a prospective bus passenger;

associating a closest street intersection with the current geospatial location of the mobile device;

determining if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device;

communicating a message to the mobile device based on the determination of whether the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device,

wherein a bus fare associated with a route of the bus is settled directly on the mobile device of the prospective bus passenger prior to the prospective bus passenger boarding

a bus associated with the bus route to pick up the prospective bus passenger at the closest street intersection on the bus route,

wherein the bus fare is dependent upon a distance desired to be travelled by the prospective bus passenger,

wherein the prospective bus passenger to select a drop off location using the mobile device,

wherein the drop off location is at least one of a scheduled bus stop, a custom bus stop, and a shared ad-hoc bus stop with other current and prospective bus passengers on the bus route,

wherein the prospective bus passenger to pay a premium when the prospective bus passenger selects the custom bus stop on the bus route,

wherein a particular bus to be routed to the closest street intersection only when the bus fare is paid on the mobile device, and

wherein the particular bus to open a door of the bus when the prospective bus passenger swipes the mobile device on a reader of the particular bus when the bus fare has been paid with the mobile device by the prospective bus passenger.

2. The method of the bus server of claim 1, further comprising:

instructing the bus associated with the bus route to pick up the prospective bus passenger at the closest street intersection on the bus route,

wherein the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device; and

communicating an estimated time of arrival of the bus to the prospective bus passenger through the message.

3. The method of the bus server of claim 2:

wherein the bus only traverses the bus route in a unidirectional looping fashion such that the particular bus on the bus route for which the closest street intersection is in a forward path of the particular bus is closest is preferred, as compared to other buses on the bus route that have already departed from the closest street intersection in forward journey on the bus route, and

wherein the particular bus is at least one of an autonomously navigating vehicle, and a semiautonomously navigating vehicle.

4. The method of the bus server of claim 3 further comprising:

providing walking directions to the prospective bus passenger to the closest street intersection on the bus route.

5. The method of the bus server of claim 4, further comprising:

periodically pinging the mobile device to provide pickup updates to the prospective bus passenger based on a request of the prospective bus passenger; and

routing multiple ones of the prospective bus passengers in a neighborhood of a current geospatial vicinity of the prospective bus passenger to a common intersection point that is within a threshold distance from each of the prospective bus passengers of the neighborhood to minimize delays of the particular bus on the bus route.

6. The method of the bus server of claim 5:

wherein the closest street intersection is associated with an address that provides for safe navigation of the particular bus on the bus route, such that the particular bus is able to make a pit stop at a safe stopping location when picking up the prospective bus passenger.

7. A method of a bus sever, comprising:

instructing a bus associated with the bus route to pick up the prospective bus passenger at the closest street intersection on the bus route,

wherein when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device,

wherein a bus fare associated with the bus route is settled directly on the mobile device of the prospective bus passenger prior to the prospective bus passenger boarding the bus,

8. The method of the bus server of claim 7 further comprising:

communicating a message to the mobile device based on the determination of whether the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device; and

9. The method of the bus server of claim 8:

10. The method of the bus server of claim 9 further comprising:

11. The method of the bus server of claim 10 further comprising:

12. The method of the bus server of claim 11:

13. A system comprising:

a mobile device having a current geospatial location;

a network; and

a bus server configured to:

analyze the current geospatial location of the mobile device responsive to a pick up request of a prospective bus passenger,

associate a closest street intersection with the current geospatial location of the mobile device,

determine if a bus route traverses the closest street intersection associated with the current geospatial location of the mobile device,

communicate, through the network, a message to the mobile device based on the determination of whether the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device,

a payment algorithm to directly settle a bus fare associated with the bus route on the mobile device of the prospective bus passenger prior to the prospective bus passenger boarding

14. The system of claim 13, further comprising:

a pick-up algorithm to instruct the bus associated with the bus route to pick up the prospective bus passenger at the closest street intersection on the bus route,

wherein when the bus route traverses the closest street intersection associated with the current geospatial location of the mobile device; and

a time-of-arrival algorithm to communicate an estimated time of arrival of the bus to the prospective bus passenger through the message.

15. The system of claim 14:

16. The system of claim 15 further comprising:

a direction algorithm to provide walking directions to the prospective bus passenger to the closest street intersection on the bus route;

an update algorithm to periodically ping the mobile device to provide pickup updates to the prospective bus passenger based on a request of the prospective bus passenger; and

a rally algorithm to route multiple ones of the prospective bus passengers in a neighborhood of a current geospatial vicinity of the prospective bus passenger to a common intersection point that is within a threshold distance from each of the prospective bus passengers of the neighborhood to minimize delays of the particular bus on the bus route.

17. The system of claim 16: