US20160005239A1 - Location-Aware Selection of Public Transportation - Google Patents
Location-Aware Selection of Public Transportation Download PDFInfo
- Publication number
- US20160005239A1 US20160005239A1 US14/844,348 US201514844348A US2016005239A1 US 20160005239 A1 US20160005239 A1 US 20160005239A1 US 201514844348 A US201514844348 A US 201514844348A US 2016005239 A1 US2016005239 A1 US 2016005239A1
- Authority
- US
- United States
- Prior art keywords
- transportation
- public transportation
- user
- information
- mobile device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 4
- 238000001914 filtration Methods 0.000 claims description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 2
- 230000000644 propagated effect Effects 0.000 claims 1
- 238000004891 communication Methods 0.000 description 6
- 238000005457 optimization Methods 0.000 description 6
- 238000007796 conventional method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000013481 data capture Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 235000012054 meals Nutrition 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000029305 taxis Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
- G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
- G07B15/02—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/30—Transportation; Communications
-
- G06Q50/40—
Definitions
- a mobile device such as a mobile phone, smart phone, personal music player, handheld game device, and the like, that is configured to be location-aware through GPS (Global Positioning System), cell tower positioning, or other means of determining location, is provided with a public transportation selector functionality (e.g., implemented using a software application) that interfaces with one or more on-line public transportation schedule services.
- GPS Global Positioning System
- cell tower positioning or other means of determining location
- public transportation selector functionality e.g., implemented using a software application
- the public transportation selector passes the location of a user of the mobile device, the user's destination, and the targeted arrival time to the schedule services which responsively return information including, for example, station/stop location information, route identifier (e.g., bus number, subway line, etc.), departure and arrival times, and fare costs relating to the available transportation options which may include bus, train, subway, ferry, and other forms of public transportation.
- the public transportation selector aggregates schedule information provided by the services for presentation to the user through a user interface (“UI”) on the mobile device. The user can then select the desired public transportation option and be provided with directions to the appropriate station or stop.
- UI user interface
- the user inputs a desired destination through the UI.
- the destination may be identified automatically through an interface with the user's scheduling tool (e.g., appointment book or calendar application) on the mobile device.
- Actual transit times may be collected and stored in a route database so that the public transportation selector may optimize the transportation options presented to the user. Published route information from the public transportation schedule services, stored user preferences, appointment and contact data, and/or user profile information may also be utilized when performing the optimization.
- the public transportation selector may utilize such information when generating suggested points of interest that the user may wish to visit on the way to the station or along the route from the station to the destination.
- the public transportation selector may also be configured with a functionality to enable the user to pay for the public transportation fare or make a reservation right from the mobile device.
- the present location-aware selection of public transportation provides users with an easy to use way to find public transportation that meets their needs.
- the interfaces between the public transportation selector and other functionalities on the mobile device, such as scheduling applications and user preferences/profile data stores, further enable effective route selection and optimization options to be automatically and transparently generated for the user.
- the user can thus effectively utilize public transportation in a way that suits their particular needs and preferences.
- FIG. 1 shows an illustrative public transportation environment in which the present location-aware selection of public transportation may be practiced
- FIG. 2 is a simplified functional block diagram of a transportation application that is configured to run on a mobile device
- FIG. 3 shows an illustrative communication flow between the transportation application and a transportation schedule service in an example usage scenario
- FIG. 4 shows an illustrative communication flow between the transportation application and the mobile device user in an example usage scenario
- FIG. 5 shows an illustrative public transportation route that is annotated with points of interest.
- FIG. 1 shows an illustrative public transportation environment 100 in which the present location-aware selection of public transportation may be practiced.
- a user 102 employs a location-aware mobile device 105 such as a mobile phone, smart phone, PDA (personal data assistant), handheld game device, handheld computer, pocket PC (personal computer), portable media player such as those which can play MP3 (Moving Pictures Expert Group, MPEG-1, audio layer 3) files, or device which integrates several of such functions.
- a location-aware mobile device 105 such as a mobile phone, smart phone, PDA (personal data assistant), handheld game device, handheld computer, pocket PC (personal computer), portable media player such as those which can play MP3 (Moving Pictures Expert Group, MPEG-1, audio layer 3) files, or device which integrates several of such functions.
- MP3 Motion Picture Expert Group
- MPEG-1 Motion Picture Expert Group
- the mobile device 105 may be configured with location-awareness using a variety of conventional techniques. These may include, for example, the use of GPS in which location is determined through a triangulation calculation based on signals from a network of satellites (as representatively indicated by reference numeral 112 ).
- cell tower positioning may be utilized to approximate the position of the mobile device 105 by comparing the relative signal strength between the mobile device and multiple antenna towers (as representatively indicated by reference numeral 116 ). While cell tower positioning is a less accurate technology compared with GPS, it may still provide sufficient accuracy in many cases to provide location-awareness to the mobile device 105 in the present application. In addition, cell tower positioning often provides superior location determination compared with GPS when mobile devices are used indoors. In some implementations, it may be desirable to use both GPS and cell tower positioning technologies. It is emphasized that the foregoing examples of location-awareness are intended to be illustrative only and that other methodologies may also be utilized as may be required to meet the needs of a particular implementation.
- the mobile device 105 is further configured for wireless communication using a mobile data network to gain access to resources that are located on a public network such as the Internet 120 .
- the mobile data network could be arranged, for example, in accordance with GPRS (General Packet Radio Service), EVDO (Evolution Data Optimized), UMTS (Universal Mobile Telecommunications System), or other known arrangements.
- the resources may be accessed via private network infrastructure such as VPN (virtual private networks).
- the Internet-accessible resources include public transportation schedule services 124 which include, in this illustrative example, a bus schedule service 124 1 , a train schedule service 124 2 , and transportation schedule service 124 N named “other” which is intended to represent a service that covers other forms of public transportation.
- public transportation schedule services 124 include, for example (but are not necessarily limited to) trains, light rail conveyances, subway, trams, trolleys, streetcars, ferries, water taxis, and similar types of transportation that may be provided by public or private entities for the benefit of the general public.
- the transportation services 124 are configured to support databases of information that pertain to their respective type of transportation. So, for example, the bus schedule service 124 1 will typically have access to bus routes, schedules, fare, and other information (e.g., general passenger, station, or accessibility information, the availability of special services, etc.) for one or more bus lines or providers that may service a particular geographic region. Such data can be populated into the databases using any of a variety of conventional methods including manual and automated data capture methods using schedule information that is typically published by the transportation provider.
- schedule services 124 are shown in FIG. 1 , in some implementations, the services may be combined or consolidated. For example, a single schedule service 124 might be used to provide information about more than one type of transportation. There is no requirement that schedule services be implemented on a one-to-one basis with the available types of transportation.
- the location-aware mobile device 105 can interact with the transportation services 124 to receive schedule, public transportation station or stop locations, route identifiers (e.g., bus number, subway line, ferry dock number, etc.), fare or ticket price, and other information from the services in response to a query or request from the device.
- the query will typically specify the location of the user, the user's destination, and the desired time of arrival.
- the mobile device 105 can thus receive, for example, a list of transit options, directions to route the user 102 (as indicated by reference numeral 130 ) to the station or stop 136 of a train, bus, subway, etc., that is near to the location of the user 102 and identify the appropriate line, number, or route that can take him or her to the destination in the desired timeframe, and fare information.
- the mobile device 105 includes a transportation application 202 that is configured to interact with one or more of the transportation services 124 to enable the present public transportation selection feature set when run on the device.
- the transportation application 202 will run as software code on the mobile device 105 , although it can also be implemented using firmware and/or hardware-based solution, or combinations of software, firmware, and hardware in some implementations.
- the transportation application 105 can be supported by the mobile device 105 under various “software as services” models where all or a portion of the application runs on a remote server.
- the transportation application is architected, as shown in FIG. 2 , using a number of components.
- FIG. 2 the particular components shown in FIG. 2 and described below are intended to be illustrative and that the functionality supported therein may be provided by components or modules other than those shown, or be allocated among the components in a different manner than that described.
- the transportation application 202 includes a public transportation selector 209 that is configured to provide the core location-aware selection functionality.
- the user 102 interacts with the public transportation selector through a UI 211 , typically through support of a graphical display and a means for input capture.
- a location module 215 provides the interface to the location-aware hardware in the mobile device such as GPS or cell tower positioning components.
- a group of service adapters 223 provide interfaces 225 over the wireless data network to the respective schedule services 124 on the Internet 120 ( FIG. 1 ).
- a service adapter (bus) 223 1 provides an interface 225 1 to the bus schedule service 124 1 .
- the service adapter (train) 223 2 provides an interface 225 2 to the train schedule service 124 2 .
- the service adapter (other) 223 N provides an interface 225 N to the other schedule service 124 N .
- the particular number and type of service adapters 223 utilized in any given implementation can vary from that shown in FIG. 2 .
- service adapters can be created by third parties (i.e., parties other than a mobile device maker, transportation application provider, or schedule service provider) and utilized to enhance the capabilities of the present arrangement in some applications.
- a route database 230 is utilized locally on the mobile device 105 to store route information that is downloaded from the schedule services as well as to provide a store for actual transit times experienced by the user 102 when following a particular transportation route.
- the actual transit times can be collected for other users for a variety of routes at some central collection point (such as a data server) and then uploaded to the route database.
- some central collection point such as a data server
- such historical transit times can be utilized by the public transportation selector, alone or in combination with other data, as part of the optimization of transportation options that are presented to the user 102 through the UI 211 .
- a scheduling module 235 is configured to provide an interface to the user's scheduling or appointment application that may be running on the mobile device 105 .
- the user may be running an instance of Microsoft Outlook® Mobile on the mobile device 105 to manage e-mail, calendars, contacts, and tasks.
- the scheduling module 235 enables the public transportation selector 209 to obtain information about the user's schedule and appointments. Typically the user will be provided with an opportunity to synchronize such information with the transportation application.
- Knowledge of the user's schedule and appointments, including for example, the time and location of such appointments, can assist the public transportation selector 209 to transparently (i.e., without requiring an affirmative or explicit action on the part of the user 102 ) recognize a need for the user to be at a particular place at a particular time.
- the public transportation selector 209 can then provide an appropriate set of transportation options that are responsive to such need.
- a user profile 241 may be optionally utilized (as indicated by its dashed outline) to further enhance the public transportation selector's ability to provide transportation options to the user 102 that suits the user's needs.
- the user 102 will typically be provided with an opportunity to opt in to the collection of data regarding the user's usage of the mobile device 105 .
- user preferences may be explicitly solicited by the transportation application, or may be set, modified or updated by the user 102 . For example, if the user profile or preference indicates that buses are most preferred by the user, and subways least preferred, the public transportation selector 209 can act appropriately when providing transportation options for a given usage scenario.
- the payment module 248 can be used in those implementations where infrastructure is in place to facilitate secure payment transactions to the transportation providers (either directly or via third party service) using the mobile device 105 . Such transactions can utilize a pre-payment system or be tied to a traditional credit card, for example. Alternatively, the use of other known electronic payment systems such as near field communications (“NFC”) may also be facilitated by the payment module 248 using the mobile device 105 as a delivery mechanism. In some implementations, it may be desirable to collect a fee for facilitating the ticket purchase transaction using the mobile device 105 . The recipient of the fee may be one of the schedule service providers, or a third party, for example.
- NFC near field communications
- FIG. 3 an illustrative flow of communications between the transportation application 202 and a schedule service 124 is shown for an example usage scenario.
- the scenario starts by a service adapter 223 in the transportation application 202 registering with its corresponding schedule service 124 (as indicated by reference numeral 310 ).
- the service adapter (bus) 2231 will register with the bus schedule service 1241 and so forth.
- the service adapter 223 will typically perform the registration using a simple handshake with the service 124 when there is need to pull schedule data or status updates about service affecting issues.
- the user 102 may work through the UI 211 to explicitly make a request to locate public transportation.
- the scheduling module 235 may identify an upcoming appointment at a distant location which the public transportation selector 209 uses as an automatic trigger to initiate the registration in a manner that is transparent to the user.
- the location module 215 determines the current location of the mobile device 105 (and hence the location of the user 102 ) which is relayed via the service adapter 223 along with the destination and desired arrival time to the schedule service 124 ( 320 ). In response, the schedule service 124 will return a selection of possible transportation routes with associated schedules for the particular public transportation type and the corresponding fee information back to the service adapter 223 ( 330 ).
- the route identifies the starting and destination points and, in most cases, schedule information that includes published or approximate departure and arrival times for each route.
- the number, line, route, or other identifying information will also be provided (e.g., bus #6, the yellow subway line, ferry slip 3, etc.)
- the transportation application 202 may assemble a multi-segment route out of segments provided by different types of transportation—for example, a leg of the route by ferry, then by bus, then by subway.
- schedule service 124 Other types of information can also be returned by a schedule service 124 . While it may vary by implementation, the information may be drawn from the information databases supported by the schedule service 124 and include general passenger, station, or accessibility information, the availability of special services, etc., as noted above.
- the public transportation selector 209 is responsible for taking the route and schedule information returned from the schedule services 124 and presenting it to the user through the UI 211 .
- the information can aggregate a multi-segment route using different public transportation types.
- FIG. 4 shows an illustrative flow of communications between the transportation application 202 and the user 102 for the example usage scenario shown in FIG. 3 and described above.
- the public transportation selector 209 can apply rules or heuristics to sort or rank order the returned information.
- the public transportation selector 209 can optimize the routes and schedules to present the user 102 with a select subset of all the available transportation options (as indicated by reference numeral 410 ).
- the optimization can be performed remotely by one of the schedule services 124 or by another remote service. Optimization may also be shared between the locally running transportation application and a remote service.
- the public transportation selector 209 will consider locally stored information such as historic transit times from the route database 230 , or profile and/or user preferences from the user profile 241 .
- the stored historical transit times for a particular route enable the public transportation selector 209 to determine the likelihood of a transportation option getting the user 102 to the destination by the desired time.
- published schedule information may indicate that a bus running on a city's west side route is supposed to arrive at the central station at 2 pm, the historical data may show that this bus typically runs late.
- the historical transit time information may also be particularly useful for public transportation that does not provide published departure and arrival times. With some subway lines, for example, subway cars arrive at each station on a periodic basis but not at a set time. In this case, the historical transit time information will typically help the public transportation selector 209 in determining whether that particular subway route is an appropriate option to present to the user 102 and further enable the public transportation selector to provide approximate departure and/or arrival times.
- the public transportation selector 209 may use data from the user profile 241 to optimize route selection by filtering or weighting transportation options based on explicitly generated user preferences or preferences that may be inferred from the collected user profile data.
- transportation by subway may be considered a more optimized solution for the user 102 in light of the profile or preference, even if a bus stop, for example, may be physically closer to the user's current location at the time of the query.
- the public transportation selector 209 will typically rank order subway routes over bus routes when presenting transportation options to the user 102 when it is determined that subways are the user's preferred type of transportation.
- the user 102 can work through the UI to pick an option that is desired and meets the user's needs ( 420 ). Responsively to the user's selection of the transportation option, station route information (i.e., direction) will be provided through the UI 211 ( 430 ). The user 102 may also be optionally presented with the ability to make an electronic payment for the fare associated with the selected transportation option, or make a reservation ( 440 ). In this case, the functionality from the payment module 248 will typically be invoked.
- the actual transit time associated with the route will be collected so that the route database 230 can be updated.
- the transit time can be calculated once the location module 215 indicates that the mobile device 105 (and hence the user 102 as well) has arrived at the destination.
- the public transportation selector 209 can annotate the station route information 530 (i.e., the directions to the station or stop 136 ) with various points of interest 535 1, 2 . . . N along the route.
- the points of interest 535 may vary by implementation and may include, for example, friends of the user 102 , retail stores, museums, restaurants, and the like.
- the points of interest 535 can be automatically generated by the public transportation selector 209 using locally available data. Alternatively, the points of interest 535 can be generated remotely using an external service.
- the public transportation selector 209 might determine from the user's contact list that is available from the scheduling module 235 that a friend or acquaintance of the user 102 resides or works near the route to the station 136 . If so, the UI 211 can include an annotation with the station route information 530 that there is an opportunity for a visit with the friend or acquaintance.
- the public transportation selector 209 may also include an annotation with the station route information 530 that a restaurant that the user 102 may like is along the route to the station 136 .
- the public transportation selector 209 may use data from the user profile 241 when making this annotation.
- the public transportation selector 209 can make an annotation that an appropriate retail store is along the route to the station 136 .
- Data from the user profile 241 or scheduling module 235 may be used in a similar manner as in the examples above to generate annotations about other points of interest for the user 102 (e.g., museums, memorials, historical sites, recreation and entertainment, and the like). Should the user 102 wish to take time to accommodate a point of interest, the public transportation selector 209 can re-query the schedule services 124 , if necessary and then determine additional transportation options that may be presented to the user 102 that take into account the additional time.
- the public transportation selector 209 can re-query the schedule services 124 , if necessary and then determine additional transportation options that may be presented to the user 102 that take into account the additional time.
- the constellation of potential points of interest 535 can be stored locally in the mobile device 105 and be periodically updated through interaction with a remote service, for example, so that the annotations reflect current and valid information.
- the points of interest 535 can be dynamically received in real time by an appropriate query to the remote service.
- the public transportation selector 209 can also be configured to generate annotations that are applicable to the route taken by the selected mode of public transportation.
- the transportation route information 541 may include annotations of various points of interest 547 1, 2 . . . N that the user 102 may wish to visit along the transportation route to the destination 550 .
- the public transportation selector 209 can utilize a similar methodology, as described above for annotating station route information, when generating annotations for points of interest 547 to the transportation route information 541 . That is, the public transportation selector 209 can take into account locally available information such as data from the scheduling module 235 and user profile 241 when making the annotation for the points of interest 547 .
- the public transportation selector 209 can re-query the schedule services 124 , if necessary, and determine additional transportation options that may be presented to the user 102 that take into account the additional time required to accommodate a point of interest 547 .
Abstract
Description
- People often rely on public transportation in many parts of the world as a safe, efficient, and cost effective way to travel in increasingly crowded urban and suburban areas. But it can often be difficult to quickly identify the available means of public transportation, particularly, for example, in unfamiliar geographic areas, or at times of the day that are not typical or usual for the traveler. Even if the traveler can find a bus or subway station, it is not always straightforward to determine which route to take that will ensure that the traveler will arrive at the desired destination at the desired time.
- A mobile device such as a mobile phone, smart phone, personal music player, handheld game device, and the like, that is configured to be location-aware through GPS (Global Positioning System), cell tower positioning, or other means of determining location, is provided with a public transportation selector functionality (e.g., implemented using a software application) that interfaces with one or more on-line public transportation schedule services. The public transportation selector passes the location of a user of the mobile device, the user's destination, and the targeted arrival time to the schedule services which responsively return information including, for example, station/stop location information, route identifier (e.g., bus number, subway line, etc.), departure and arrival times, and fare costs relating to the available transportation options which may include bus, train, subway, ferry, and other forms of public transportation. The public transportation selector aggregates schedule information provided by the services for presentation to the user through a user interface (“UI”) on the mobile device. The user can then select the desired public transportation option and be provided with directions to the appropriate station or stop.
- In various illustrative examples, the user inputs a desired destination through the UI. Alternatively, the destination may be identified automatically through an interface with the user's scheduling tool (e.g., appointment book or calendar application) on the mobile device. Actual transit times may be collected and stored in a route database so that the public transportation selector may optimize the transportation options presented to the user. Published route information from the public transportation schedule services, stored user preferences, appointment and contact data, and/or user profile information may also be utilized when performing the optimization. In addition, the public transportation selector may utilize such information when generating suggested points of interest that the user may wish to visit on the way to the station or along the route from the station to the destination. The public transportation selector may also be configured with a functionality to enable the user to pay for the public transportation fare or make a reservation right from the mobile device.
- Advantageously, the present location-aware selection of public transportation provides users with an easy to use way to find public transportation that meets their needs. The interfaces between the public transportation selector and other functionalities on the mobile device, such as scheduling applications and user preferences/profile data stores, further enable effective route selection and optimization options to be automatically and transparently generated for the user. The user can thus effectively utilize public transportation in a way that suits their particular needs and preferences.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
-
FIG. 1 shows an illustrative public transportation environment in which the present location-aware selection of public transportation may be practiced; -
FIG. 2 is a simplified functional block diagram of a transportation application that is configured to run on a mobile device; -
FIG. 3 shows an illustrative communication flow between the transportation application and a transportation schedule service in an example usage scenario; -
FIG. 4 shows an illustrative communication flow between the transportation application and the mobile device user in an example usage scenario; and -
FIG. 5 shows an illustrative public transportation route that is annotated with points of interest. - Like reference numerals indicate like elements in the drawings.
-
FIG. 1 shows an illustrativepublic transportation environment 100 in which the present location-aware selection of public transportation may be practiced. In theenvironment 100, auser 102 employs a location-awaremobile device 105 such as a mobile phone, smart phone, PDA (personal data assistant), handheld game device, handheld computer, pocket PC (personal computer), portable media player such as those which can play MP3 (Moving Pictures Expert Group, MPEG-1, audio layer 3) files, or device which integrates several of such functions. It is noted that these types of mobile devices are intended to be illustrative and that other types of mobile devices may also be used in the present arrangement as may be required to meet the needs of a particular implementation. - The
mobile device 105 may be configured with location-awareness using a variety of conventional techniques. These may include, for example, the use of GPS in which location is determined through a triangulation calculation based on signals from a network of satellites (as representatively indicated by reference numeral 112). - Alternatively, cell tower positioning may be utilized to approximate the position of the
mobile device 105 by comparing the relative signal strength between the mobile device and multiple antenna towers (as representatively indicated by reference numeral 116). While cell tower positioning is a less accurate technology compared with GPS, it may still provide sufficient accuracy in many cases to provide location-awareness to themobile device 105 in the present application. In addition, cell tower positioning often provides superior location determination compared with GPS when mobile devices are used indoors. In some implementations, it may be desirable to use both GPS and cell tower positioning technologies. It is emphasized that the foregoing examples of location-awareness are intended to be illustrative only and that other methodologies may also be utilized as may be required to meet the needs of a particular implementation. - The
mobile device 105 is further configured for wireless communication using a mobile data network to gain access to resources that are located on a public network such as the Internet 120. The mobile data network could be arranged, for example, in accordance with GPRS (General Packet Radio Service), EVDO (Evolution Data Optimized), UMTS (Universal Mobile Telecommunications System), or other known arrangements. In alternative implementations, the resources may be accessed via private network infrastructure such as VPN (virtual private networks). - The Internet-accessible resources include public
transportation schedule services 124 which include, in this illustrative example, abus schedule service 124 1, atrain schedule service 124 2, andtransportation schedule service 124 N named “other” which is intended to represent a service that covers other forms of public transportation. These include, for example (but are not necessarily limited to) trains, light rail conveyances, subway, trams, trolleys, streetcars, ferries, water taxis, and similar types of transportation that may be provided by public or private entities for the benefit of the general public. - The
transportation services 124 are configured to support databases of information that pertain to their respective type of transportation. So, for example, thebus schedule service 124 1 will typically have access to bus routes, schedules, fare, and other information (e.g., general passenger, station, or accessibility information, the availability of special services, etc.) for one or more bus lines or providers that may service a particular geographic region. Such data can be populated into the databases using any of a variety of conventional methods including manual and automated data capture methods using schedule information that is typically published by the transportation provider. - It is noted that while
separate schedule services 124 are shown inFIG. 1 , in some implementations, the services may be combined or consolidated. For example, asingle schedule service 124 might be used to provide information about more than one type of transportation. There is no requirement that schedule services be implemented on a one-to-one basis with the available types of transportation. - The location-aware
mobile device 105 can interact with thetransportation services 124 to receive schedule, public transportation station or stop locations, route identifiers (e.g., bus number, subway line, ferry dock number, etc.), fare or ticket price, and other information from the services in response to a query or request from the device. The query will typically specify the location of the user, the user's destination, and the desired time of arrival. Themobile device 105 can thus receive, for example, a list of transit options, directions to route the user 102 (as indicated by reference numeral 130) to the station or stop 136 of a train, bus, subway, etc., that is near to the location of theuser 102 and identify the appropriate line, number, or route that can take him or her to the destination in the desired timeframe, and fare information. - More specifically, as shown in
FIG. 2 , themobile device 105 includes atransportation application 202 that is configured to interact with one or more of thetransportation services 124 to enable the present public transportation selection feature set when run on the device. Typically, thetransportation application 202 will run as software code on themobile device 105, although it can also be implemented using firmware and/or hardware-based solution, or combinations of software, firmware, and hardware in some implementations. In addition, thetransportation application 105 can be supported by themobile device 105 under various “software as services” models where all or a portion of the application runs on a remote server. - In this example, the transportation application is architected, as shown in
FIG. 2 , using a number of components. However, it is emphasized that the particular components shown inFIG. 2 and described below are intended to be illustrative and that the functionality supported therein may be provided by components or modules other than those shown, or be allocated among the components in a different manner than that described. - The
transportation application 202 includes apublic transportation selector 209 that is configured to provide the core location-aware selection functionality. Theuser 102 interacts with the public transportation selector through aUI 211, typically through support of a graphical display and a means for input capture. Alocation module 215 provides the interface to the location-aware hardware in the mobile device such as GPS or cell tower positioning components. - A group of service adapters 223 provide interfaces 225 over the wireless data network to the
respective schedule services 124 on the Internet 120 (FIG. 1 ). In particular, as shown, a service adapter (bus) 223 1 provides an interface 225 1 to thebus schedule service 124 1. Similarly, the service adapter (train) 223 2 provides an interface 225 2 to thetrain schedule service 124 2. And, the service adapter (other) 223 N provides an interface 225 N to theother schedule service 124 N. The particular number and type of service adapters 223 utilized in any given implementation can vary from that shown inFIG. 2 . In addition, service adapters can be created by third parties (i.e., parties other than a mobile device maker, transportation application provider, or schedule service provider) and utilized to enhance the capabilities of the present arrangement in some applications. - A
route database 230 is utilized locally on themobile device 105 to store route information that is downloaded from the schedule services as well as to provide a store for actual transit times experienced by theuser 102 when following a particular transportation route. Alternatively, the actual transit times can be collected for other users for a variety of routes at some central collection point (such as a data server) and then uploaded to the route database. As described in more detail below, such historical transit times can be utilized by the public transportation selector, alone or in combination with other data, as part of the optimization of transportation options that are presented to theuser 102 through theUI 211. - A
scheduling module 235 is configured to provide an interface to the user's scheduling or appointment application that may be running on themobile device 105. For example, the user may be running an instance of Microsoft Outlook® Mobile on themobile device 105 to manage e-mail, calendars, contacts, and tasks. Thescheduling module 235 enables thepublic transportation selector 209 to obtain information about the user's schedule and appointments. Typically the user will be provided with an opportunity to synchronize such information with the transportation application. Knowledge of the user's schedule and appointments, including for example, the time and location of such appointments, can assist thepublic transportation selector 209 to transparently (i.e., without requiring an affirmative or explicit action on the part of the user 102) recognize a need for the user to be at a particular place at a particular time. Thepublic transportation selector 209 can then provide an appropriate set of transportation options that are responsive to such need. - In a similar manner as with the scheduling module, a
user profile 241 may be optionally utilized (as indicated by its dashed outline) to further enhance the public transportation selector's ability to provide transportation options to theuser 102 that suits the user's needs. As above, theuser 102 will typically be provided with an opportunity to opt in to the collection of data regarding the user's usage of themobile device 105. - Various techniques and heuristics can be employed to infer a user preference from collected profile data. In some cases, user preferences may be explicitly solicited by the transportation application, or may be set, modified or updated by the
user 102. For example, if the user profile or preference indicates that buses are most preferred by the user, and subways least preferred, thepublic transportation selector 209 can act appropriately when providing transportation options for a given usage scenario. - Also optionally utilized in the
transportation application 202 is thepayment module 248. This module can be used in those implementations where infrastructure is in place to facilitate secure payment transactions to the transportation providers (either directly or via third party service) using themobile device 105. Such transactions can utilize a pre-payment system or be tied to a traditional credit card, for example. Alternatively, the use of other known electronic payment systems such as near field communications (“NFC”) may also be facilitated by thepayment module 248 using themobile device 105 as a delivery mechanism. In some implementations, it may be desirable to collect a fee for facilitating the ticket purchase transaction using themobile device 105. The recipient of the fee may be one of the schedule service providers, or a third party, for example. - Turning now to
FIG. 3 , an illustrative flow of communications between thetransportation application 202 and aschedule service 124 is shown for an example usage scenario. The scenario starts by a service adapter 223 in thetransportation application 202 registering with its corresponding schedule service 124 (as indicated by reference numeral 310). Thus, for example, the service adapter (bus) 2231 will register with thebus schedule service 1241 and so forth. The service adapter 223 will typically perform the registration using a simple handshake with theservice 124 when there is need to pull schedule data or status updates about service affecting issues. For example, theuser 102 may work through theUI 211 to explicitly make a request to locate public transportation. Or, thescheduling module 235 may identify an upcoming appointment at a distant location which thepublic transportation selector 209 uses as an automatic trigger to initiate the registration in a manner that is transparent to the user. - The
location module 215 determines the current location of the mobile device 105 (and hence the location of the user 102) which is relayed via the service adapter 223 along with the destination and desired arrival time to the schedule service 124 (320). In response, theschedule service 124 will return a selection of possible transportation routes with associated schedules for the particular public transportation type and the corresponding fee information back to the service adapter 223 (330). - The route identifies the starting and destination points and, in most cases, schedule information that includes published or approximate departure and arrival times for each route. The number, line, route, or other identifying information will also be provided (e.g., bus #6, the yellow subway line, ferry slip 3, etc.) Typically, as multiple service adapters are used to interface with multiple transportation schedule services, the steps of registration, reporting, and information return are performed with each service adapter and schedule service pair, and the
transportation application 202 may assemble a multi-segment route out of segments provided by different types of transportation—for example, a leg of the route by ferry, then by bus, then by subway. Depending upon the particular circumstances, it may be possible for a relatively large amount of information to be passed back from the varioustransportation schedule services 124 to thetransportation application 202 running on themobile device 105. That is, there may be multiple ways for theuser 102 to get to a particular destination using different forms of public transportation that traverse different routes, and within some reasonable interval to the desired arrival time. - Other types of information can also be returned by a
schedule service 124. While it may vary by implementation, the information may be drawn from the information databases supported by theschedule service 124 and include general passenger, station, or accessibility information, the availability of special services, etc., as noted above. - The
public transportation selector 209 is responsible for taking the route and schedule information returned from theschedule services 124 and presenting it to the user through theUI 211. In some cases, as noted above, the information can aggregate a multi-segment route using different public transportation types.FIG. 4 shows an illustrative flow of communications between thetransportation application 202 and theuser 102 for the example usage scenario shown inFIG. 3 and described above. - Generally in most implementations it will be desirable for the
public transportation selector 209 to apply rules or heuristics to sort or rank order the returned information. In this way thepublic transportation selector 209 can optimize the routes and schedules to present theuser 102 with a select subset of all the available transportation options (as indicated by reference numeral 410). Alternatively, the optimization can be performed remotely by one of theschedule services 124 or by another remote service. Optimization may also be shared between the locally running transportation application and a remote service. - The optimization techniques may vary by implementation. In some cases, the
public transportation selector 209 will consider locally stored information such as historic transit times from theroute database 230, or profile and/or user preferences from theuser profile 241. - With the
route database 230, the stored historical transit times for a particular route (or any other information provided by the user) enable thepublic transportation selector 209 to determine the likelihood of a transportation option getting theuser 102 to the destination by the desired time. Thus, for example, while published schedule information may indicate that a bus running on a city's west side route is supposed to arrive at the central station at 2 pm, the historical data may show that this bus typically runs late. - The historical transit time information may also be particularly useful for public transportation that does not provide published departure and arrival times. With some subway lines, for example, subway cars arrive at each station on a periodic basis but not at a set time. In this case, the historical transit time information will typically help the
public transportation selector 209 in determining whether that particular subway route is an appropriate option to present to theuser 102 and further enable the public transportation selector to provide approximate departure and/or arrival times. - The
public transportation selector 209 may use data from theuser profile 241 to optimize route selection by filtering or weighting transportation options based on explicitly generated user preferences or preferences that may be inferred from the collected user profile data. Thus, transportation by subway may be considered a more optimized solution for theuser 102 in light of the profile or preference, even if a bus stop, for example, may be physically closer to the user's current location at the time of the query. Accordingly, thepublic transportation selector 209 will typically rank order subway routes over bus routes when presenting transportation options to theuser 102 when it is determined that subways are the user's preferred type of transportation. - When presented with the transportation options, the
user 102 can work through the UI to pick an option that is desired and meets the user's needs (420). Responsively to the user's selection of the transportation option, station route information (i.e., direction) will be provided through the UI 211 (430). Theuser 102 may also be optionally presented with the ability to make an electronic payment for the fare associated with the selected transportation option, or make a reservation (440). In this case, the functionality from thepayment module 248 will typically be invoked. - As the
user 102 makes the trip using the selected transportation option, the actual transit time associated with the route will be collected so that theroute database 230 can be updated. The transit time can be calculated once thelocation module 215 indicates that the mobile device 105 (and hence theuser 102 as well) has arrived at the destination. - Additional value-added features may also be advantageously implemented using the present location-aware public transportation selection arrangement. As shown in
FIG. 5 , thepublic transportation selector 209 can annotate the station route information 530 (i.e., the directions to the station or stop 136) with various points of interest 535 1, 2 . . . N along the route. The points of interest 535 may vary by implementation and may include, for example, friends of theuser 102, retail stores, museums, restaurants, and the like. The points of interest 535 can be automatically generated by thepublic transportation selector 209 using locally available data. Alternatively, the points of interest 535 can be generated remotely using an external service. - So, for example, the
public transportation selector 209 might determine from the user's contact list that is available from thescheduling module 235 that a friend or acquaintance of theuser 102 resides or works near the route to thestation 136. If so, theUI 211 can include an annotation with thestation route information 530 that there is an opportunity for a visit with the friend or acquaintance. - If the current time is close to a meal time, the
public transportation selector 209 may also include an annotation with thestation route information 530 that a restaurant that theuser 102 may like is along the route to thestation 136. Thepublic transportation selector 209 may use data from theuser profile 241 when making this annotation. - If the
scheduling module 235 indicates that theuser 102 has created a task to purchase a gift, for example, for a friend's upcoming birthday, thepublic transportation selector 209 can make an annotation that an appropriate retail store is along the route to thestation 136. - Data from the
user profile 241 orscheduling module 235 may be used in a similar manner as in the examples above to generate annotations about other points of interest for the user 102 (e.g., museums, memorials, historical sites, recreation and entertainment, and the like). Should theuser 102 wish to take time to accommodate a point of interest, thepublic transportation selector 209 can re-query theschedule services 124, if necessary and then determine additional transportation options that may be presented to theuser 102 that take into account the additional time. - The constellation of potential points of interest 535 can be stored locally in the
mobile device 105 and be periodically updated through interaction with a remote service, for example, so that the annotations reflect current and valid information. Alternatively, the points of interest 535 can be dynamically received in real time by an appropriate query to the remote service. - The
public transportation selector 209 can also be configured to generate annotations that are applicable to the route taken by the selected mode of public transportation. As shown inFIG. 5 , thetransportation route information 541 may include annotations of various points ofinterest 547 1, 2 . . . N that theuser 102 may wish to visit along the transportation route to thedestination 550. Thepublic transportation selector 209 can utilize a similar methodology, as described above for annotating station route information, when generating annotations for points ofinterest 547 to thetransportation route information 541. That is, thepublic transportation selector 209 can take into account locally available information such as data from thescheduling module 235 anduser profile 241 when making the annotation for the points ofinterest 547. And, as with the example above, thepublic transportation selector 209 can re-query theschedule services 124, if necessary, and determine additional transportation options that may be presented to theuser 102 that take into account the additional time required to accommodate a point ofinterest 547. - Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/844,348 US20160005239A1 (en) | 2008-10-02 | 2015-09-03 | Location-Aware Selection of Public Transportation |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/244,656 US9159238B2 (en) | 2008-10-02 | 2008-10-02 | Location-aware selection of public transportation |
US14/844,348 US20160005239A1 (en) | 2008-10-02 | 2015-09-03 | Location-Aware Selection of Public Transportation |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/244,656 Continuation US9159238B2 (en) | 2008-10-02 | 2008-10-02 | Location-aware selection of public transportation |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160005239A1 true US20160005239A1 (en) | 2016-01-07 |
Family
ID=42076429
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/244,656 Active 2031-01-20 US9159238B2 (en) | 2008-10-02 | 2008-10-02 | Location-aware selection of public transportation |
US14/844,348 Abandoned US20160005239A1 (en) | 2008-10-02 | 2015-09-03 | Location-Aware Selection of Public Transportation |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/244,656 Active 2031-01-20 US9159238B2 (en) | 2008-10-02 | 2008-10-02 | Location-aware selection of public transportation |
Country Status (1)
Country | Link |
---|---|
US (2) | US9159238B2 (en) |
Families Citing this family (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9177472B2 (en) * | 2006-06-08 | 2015-11-03 | Lg Electronics Inc. | Method and apparatus for providing and using public transportation information |
US8467957B2 (en) * | 2008-06-11 | 2013-06-18 | Clever Devices, Ltd. | Method and apparatus for generating routes using real-time public transportation information |
CA2782611C (en) | 2009-12-04 | 2018-07-10 | Uber Technologies, Inc. | System and method for arranging transport amongst parties through use of mobile devices |
US9230292B2 (en) | 2012-11-08 | 2016-01-05 | Uber Technologies, Inc. | Providing on-demand services through use of portable computing devices |
US8645050B2 (en) | 2010-09-09 | 2014-02-04 | Google Inc. | Transportation information systems and methods associated with degradation modes |
US20120253878A1 (en) * | 2011-03-29 | 2012-10-04 | Trapeze Software Inc. | Method and system for scheduling paratransit service |
US9222788B2 (en) * | 2012-06-27 | 2015-12-29 | Microsoft Technology Licensing, Llc | Proactive delivery of navigation options |
DE102012016119A1 (en) | 2012-08-15 | 2014-02-20 | Lawo Informationssysteme Gmbh | Method for processing and displaying timetable information |
US9671233B2 (en) | 2012-11-08 | 2017-06-06 | Uber Technologies, Inc. | Dynamically providing position information of a transit object to a computing device |
KR101504663B1 (en) * | 2013-02-14 | 2015-03-30 | 주식회사 케이티 | Method and apparatus for providing domestic transit card service subscriber with overseas transit card service |
US9547917B2 (en) | 2013-03-14 | 2017-01-17 | Paypay, Inc. | Using augmented reality to determine information |
US20140343974A1 (en) * | 2013-05-14 | 2014-11-20 | Google Inc. | Selecting a Subset of Transit Trips Based on Time and Duration |
US10971009B2 (en) * | 2013-06-28 | 2021-04-06 | International Business Machines Corporation | Extracting events and assessing their impact on a transportation network |
US9232350B2 (en) | 2013-07-02 | 2016-01-05 | Fortis Riders Acquisition Corporation | Mobile application using facilitating dedicated communication between specific users |
US10055752B2 (en) * | 2013-07-30 | 2018-08-21 | Here Global B.V. | Method and apparatus for performing real-time out home advertising performance analytics based on arbitrary data streams and out of home advertising display analysis |
US20150070131A1 (en) * | 2013-09-11 | 2015-03-12 | Here Global B.V. | Method and apparatus for detecting boarding of a means of transport |
US20150176997A1 (en) * | 2013-12-22 | 2015-06-25 | Andreas Kurt PURSCHE | Adaptive transportation framework |
CN105450583B (en) | 2014-07-03 | 2019-07-05 | 阿里巴巴集团控股有限公司 | A kind of method and device of authentification of message |
CN105446992A (en) | 2014-07-08 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Method and device for building goods object recovery information database and determining value information |
CN105450411B (en) | 2014-08-14 | 2019-01-08 | 阿里巴巴集团控股有限公司 | The method, apparatus and system of authentication are carried out using card feature |
CN105719183A (en) | 2014-12-03 | 2016-06-29 | 阿里巴巴集团控股有限公司 | Directional transfer method and apparatus |
CN105869043A (en) | 2015-01-19 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Disperse hot spot database account transfer-in and transfer-out accounting method and device |
CN105989467A (en) * | 2015-02-03 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Wireless payment method, apparatus, vehicle ride fee check method and system |
US10620010B2 (en) | 2015-02-05 | 2020-04-14 | Moovit App Global Ltd | Public and ordered transportation trip planning |
WO2016175821A1 (en) * | 2015-04-30 | 2016-11-03 | Hewlett Packard Enterprise Development Lp | Journey and charge presentations at mobile devices |
US9799221B2 (en) * | 2015-05-06 | 2017-10-24 | Global Traffic Technologies, Llc | Trip determination for managing transit vehicle schedules |
AU2015101437B4 (en) * | 2015-10-06 | 2017-06-29 | Transportme Pty Ltd | Systems and methods for a conveyance |
CN106570009B (en) | 2015-10-09 | 2020-07-28 | 阿里巴巴集团控股有限公司 | Navigation category updating method and device |
US20170186114A1 (en) * | 2015-12-29 | 2017-06-29 | Mastercard International Incorporated | Systems and Methods for Use in Identifying Effective Purchase Options for Travel |
US10527736B2 (en) * | 2016-03-17 | 2020-01-07 | Cm Hk Limited | Methods and mobile devices with electric vehicle transportation detection |
US10337876B2 (en) | 2016-05-10 | 2019-07-02 | Microsoft Technology Licensing, Llc | Constrained-transportation directions |
US10386197B2 (en) | 2016-05-17 | 2019-08-20 | Microsoft Technology Licensing, Llc | Calculating an optimal route based on specified intermediate stops |
US10060752B2 (en) | 2016-06-23 | 2018-08-28 | Microsoft Technology Licensing, Llc | Detecting deviation from planned public transit route |
CN106023583B (en) * | 2016-07-27 | 2018-09-07 | 合肥指南针电子科技有限责任公司 | A kind of public transit system Reduction of Students' Study Load method |
CN106251616B (en) * | 2016-07-27 | 2018-10-12 | 合肥指南针电子科技有限责任公司 | A kind of passenger applied to public transport regulation and control shares system |
US10817806B2 (en) * | 2016-07-29 | 2020-10-27 | Xerox Corporation | Predictive model for supporting carpooling |
US11120641B2 (en) | 2016-12-14 | 2021-09-14 | Conduent Business Services, Llc | System for public transit fare collection, decomposition and display |
US9741178B1 (en) * | 2016-12-14 | 2017-08-22 | Conduent Business Services, Llc | Fare collection system in a public transit network |
SG10201705665PA (en) * | 2017-07-10 | 2019-02-27 | Nec Corp | Method and apparatus for optimizing efficiency of a transport provider |
CN107958316B (en) * | 2018-01-17 | 2020-12-01 | 深圳技术大学 | Train stop optimization method and system for rail transit line |
CN108734371A (en) | 2018-02-12 | 2018-11-02 | 阿里巴巴集团控股有限公司 | A kind of processing method, device and equipment for air control instruction |
CN108632348B (en) | 2018-03-19 | 2020-02-18 | 阿里巴巴集团控股有限公司 | Service checking method and device |
CN109391901A (en) * | 2018-06-12 | 2019-02-26 | 湖南国科防务电子科技有限公司 | Passing control method and system, computer equipment and storage medium |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030040944A1 (en) * | 2001-08-22 | 2003-02-27 | Hileman Ryan M. | On-demand transportation system |
US20030098802A1 (en) * | 1999-03-01 | 2003-05-29 | Jones Martin Kelly | Base station apparatus and method for monitoring travel of a mobile vehicle |
US20030153330A1 (en) * | 2000-05-19 | 2003-08-14 | Siamak Naghian | Location information services |
US20030193413A1 (en) * | 1993-05-18 | 2003-10-16 | Jones M. Kelly | Business methods for notification systems |
US20040032393A1 (en) * | 2001-04-04 | 2004-02-19 | Brandenberg Carl Brock | Method and apparatus for scheduling presentation of digital content on a personal communication device |
US20040049424A1 (en) * | 2002-06-21 | 2004-03-11 | Murray Thomas A. | System and method for facilitating ridesharing |
US20040078424A1 (en) * | 2002-10-16 | 2004-04-22 | Nokia Corporation | Web services via instant messaging |
US20040243430A1 (en) * | 2003-05-28 | 2004-12-02 | Horstemeyer Scott A. | Notification systems and methods enabling a response to cause connection between a notified PCD and a delivery or pickup representative |
US20050182538A1 (en) * | 2003-05-06 | 2005-08-18 | Joseph Phelan | Motor vehicle operating data collection and analysis |
US20060074545A1 (en) * | 2004-09-17 | 2006-04-06 | Kim Jae-Ho | System and method for controlling public transportation |
US20060157563A1 (en) * | 2004-06-17 | 2006-07-20 | Marshall David A | Smart card systems in connection with transportation services |
US20060265264A1 (en) * | 2005-05-23 | 2006-11-23 | Oracle International Corporation | Scheduling with layovers and layover charge computation in transportation planning |
US20060267794A1 (en) * | 2005-05-27 | 2006-11-30 | Lg Electronics Inc. | Encoding and decoding traffic information using encoding fields |
US20060271552A1 (en) * | 2005-05-26 | 2006-11-30 | Venture Capital & Consulting Group, Llc. | Targeted delivery of content |
US20070038506A1 (en) * | 2005-06-09 | 2007-02-15 | Emercent Solutions, Llc | Systems and methods for facilitating product and service transactions |
US20080027772A1 (en) * | 2006-07-31 | 2008-01-31 | Gernega Boris | System and method for optimizing a transit network |
WO2008108530A1 (en) * | 2007-03-07 | 2008-09-12 | Thinkware Systems Corporation | Method for managing schedule using user's location information and system thereof |
US20090312947A1 (en) * | 2008-06-11 | 2009-12-17 | Clever Devices, Ltd. | Method and apparatus for generating routes using real-time public transportation information |
US20100017118A1 (en) * | 2008-07-16 | 2010-01-21 | Apple Inc. | Parking & location management processes & alerts |
US20110112759A1 (en) * | 2009-11-11 | 2011-05-12 | Google Inc. | Transit routing system for public transportation trip planning |
US20120253863A1 (en) * | 2011-03-29 | 2012-10-04 | Trapeze Software Inc. | Method and system for paratransit run-cutting |
US20130304378A1 (en) * | 2012-05-09 | 2013-11-14 | Google Inc. | Public Transportation Journey Planning |
US20150045068A1 (en) * | 2012-03-29 | 2015-02-12 | Telmap Ltd. | Location-based assistance for personal planning |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3385657B2 (en) * | 1993-08-10 | 2003-03-10 | トヨタ自動車株式会社 | Car navigation system |
US5948040A (en) * | 1994-06-24 | 1999-09-07 | Delorme Publishing Co. | Travel reservation information and planning system |
US6006159A (en) * | 1995-08-14 | 1999-12-21 | Schmier; Kenneth J. | Public transit vehicle arrival information system |
US5799263A (en) * | 1996-04-15 | 1998-08-25 | Bct Systems | Public transit system and apparatus and method for dispatching public transit vehicles |
US6184802B1 (en) * | 1998-10-13 | 2001-02-06 | Robert Goodman Lamb | Autonomous estimator of vehicle arrival time |
US6208934B1 (en) * | 1999-01-19 | 2001-03-27 | Navigation Technologies Corp. | Method and system for providing walking instructions with route guidance in a navigation program |
DE60010993T2 (en) * | 1999-08-17 | 2005-06-09 | Toyota Jidosha K.K., Toyota | Route guidance device |
AU2001276992A1 (en) * | 2000-07-20 | 2002-02-05 | Aeptec Microsystems, Inc. | Method, system, and protocol for location-aware mobile devices |
CA2618495C (en) * | 2005-08-10 | 2016-11-01 | Lg Electronics Inc. | Method and apparatus for providing public traffic information |
KR101183918B1 (en) * | 2005-08-10 | 2012-09-26 | 엘지전자 주식회사 | Method and apparatus for providing public traffic information and using the information |
US7667646B2 (en) * | 2006-02-21 | 2010-02-23 | Nokia Corporation | System and methods for direction finding using a handheld device |
US7519470B2 (en) * | 2006-03-15 | 2009-04-14 | Microsoft Corporation | Location-based caching for mobile devices |
US7571050B2 (en) * | 2006-03-27 | 2009-08-04 | Microsoft Corporation | Transit-coordinated local search |
AR054821A1 (en) * | 2006-07-06 | 2007-07-18 | Rosario Bus S A | PROVISION FOR INFORMATION, POSITIONING CONTROL AND PASSENGER TRANSPORTATION VEHICLE SCHEDULE. |
KR100862574B1 (en) * | 2006-09-18 | 2008-10-09 | 엘지전자 주식회사 | Method and apparatus for providng information on availability of public transportation and method and apparatus for using said information |
US20090119001A1 (en) * | 2007-11-07 | 2009-05-07 | Public Routes. Com, Llc | Method and system for finding multimodal transit route directions based on user preferred transport modes |
US20090239552A1 (en) * | 2008-03-24 | 2009-09-24 | Yahoo! Inc. | Location-based opportunistic recommendations |
-
2008
- 2008-10-02 US US12/244,656 patent/US9159238B2/en active Active
-
2015
- 2015-09-03 US US14/844,348 patent/US20160005239A1/en not_active Abandoned
Patent Citations (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030193413A1 (en) * | 1993-05-18 | 2003-10-16 | Jones M. Kelly | Business methods for notification systems |
US20030098802A1 (en) * | 1999-03-01 | 2003-05-29 | Jones Martin Kelly | Base station apparatus and method for monitoring travel of a mobile vehicle |
US20030153330A1 (en) * | 2000-05-19 | 2003-08-14 | Siamak Naghian | Location information services |
US20040032393A1 (en) * | 2001-04-04 | 2004-02-19 | Brandenberg Carl Brock | Method and apparatus for scheduling presentation of digital content on a personal communication device |
US20030040944A1 (en) * | 2001-08-22 | 2003-02-27 | Hileman Ryan M. | On-demand transportation system |
US20040049424A1 (en) * | 2002-06-21 | 2004-03-11 | Murray Thomas A. | System and method for facilitating ridesharing |
US20040078424A1 (en) * | 2002-10-16 | 2004-04-22 | Nokia Corporation | Web services via instant messaging |
US20050182538A1 (en) * | 2003-05-06 | 2005-08-18 | Joseph Phelan | Motor vehicle operating data collection and analysis |
US20040243430A1 (en) * | 2003-05-28 | 2004-12-02 | Horstemeyer Scott A. | Notification systems and methods enabling a response to cause connection between a notified PCD and a delivery or pickup representative |
US20060157563A1 (en) * | 2004-06-17 | 2006-07-20 | Marshall David A | Smart card systems in connection with transportation services |
US20060074545A1 (en) * | 2004-09-17 | 2006-04-06 | Kim Jae-Ho | System and method for controlling public transportation |
US20060265264A1 (en) * | 2005-05-23 | 2006-11-23 | Oracle International Corporation | Scheduling with layovers and layover charge computation in transportation planning |
US20060271552A1 (en) * | 2005-05-26 | 2006-11-30 | Venture Capital & Consulting Group, Llc. | Targeted delivery of content |
US20060267794A1 (en) * | 2005-05-27 | 2006-11-30 | Lg Electronics Inc. | Encoding and decoding traffic information using encoding fields |
US20070038506A1 (en) * | 2005-06-09 | 2007-02-15 | Emercent Solutions, Llc | Systems and methods for facilitating product and service transactions |
US20080027772A1 (en) * | 2006-07-31 | 2008-01-31 | Gernega Boris | System and method for optimizing a transit network |
WO2008108530A1 (en) * | 2007-03-07 | 2008-09-12 | Thinkware Systems Corporation | Method for managing schedule using user's location information and system thereof |
KR20090000609A (en) * | 2007-03-07 | 2009-01-08 | 팅크웨어(주) | Method for managing schedule using user' location information and system thereof |
US20100106404A1 (en) * | 2007-03-07 | 2010-04-29 | Kim Bo Young | Method for managing schedule using user's location information and system thereof |
US20090312947A1 (en) * | 2008-06-11 | 2009-12-17 | Clever Devices, Ltd. | Method and apparatus for generating routes using real-time public transportation information |
US20100017118A1 (en) * | 2008-07-16 | 2010-01-21 | Apple Inc. | Parking & location management processes & alerts |
US20110112759A1 (en) * | 2009-11-11 | 2011-05-12 | Google Inc. | Transit routing system for public transportation trip planning |
US20120253863A1 (en) * | 2011-03-29 | 2012-10-04 | Trapeze Software Inc. | Method and system for paratransit run-cutting |
US20150045068A1 (en) * | 2012-03-29 | 2015-02-12 | Telmap Ltd. | Location-based assistance for personal planning |
US20130304378A1 (en) * | 2012-05-09 | 2013-11-14 | Google Inc. | Public Transportation Journey Planning |
Also Published As
Publication number | Publication date |
---|---|
US9159238B2 (en) | 2015-10-13 |
US20100088026A1 (en) | 2010-04-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9159238B2 (en) | Location-aware selection of public transportation | |
US11821737B2 (en) | Public and ordered transportation trip planning | |
US20170300848A1 (en) | System and Method for Transportation | |
US9377319B2 (en) | Estimating times to leave and to travel | |
US20140074757A1 (en) | Estimating taxi fare | |
US20130054139A1 (en) | Location of Available Passenger Seats in a Dynamic Transporting Pool | |
US20130024249A1 (en) | Public transport optimization | |
JP4114881B2 (en) | Meeting place determination device and method | |
US20080046298A1 (en) | System and Method For Travel Planning | |
US20100268450A1 (en) | Pedestrian navigation systemand method integrated with public transportation | |
JP4538536B2 (en) | Route search apparatus and route search method | |
EP2031570B1 (en) | Route search system, route search server, terminal, and route search method | |
JP4538537B2 (en) | Route search apparatus and route search method | |
JP2007052729A (en) | Taxi dispatch system | |
WO2009087489A1 (en) | Networking system | |
JP2004227490A (en) | Community management system and method thereof | |
EP1703450A1 (en) | Mileage service system using positional information of mobile communication terminals and method therefor | |
US20200132494A1 (en) | Data generating apparatus, data generating system, data generation method, and non-transitory recording medium | |
JP4538510B2 (en) | Information processing apparatus and route processing method | |
JP2002092193A (en) | Method and system for information guide | |
JP2002342890A (en) | Customer information providing system for commercial vehicle | |
JP7393100B2 (en) | Information processing device, information processing method, and program | |
JP2010055646A (en) | Information processor and route processing method | |
TW200918857A (en) | Navigation system and method combining public transportation resources | |
JP2002251583A (en) | System, method, and program for planning collection of rental car and computer-readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:052835/0951 Effective date: 20141014 Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MANOLESCU, DRAGOS A.;REEL/FRAME:052835/0862 Effective date: 20080930 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |