Architecture for distributing transit data
First Claim
Patent Images
1. A non-transitory machine-readable medium storing a program executable by at least one processing unit, the program comprising sets of instructions for:
- receiving from a plurality of data providers transit system data and user interface (UI) definitions of different transit-system graphical representations specifying the manner the transit system data is presented in a particular locality when the transit system data is displayed in commute applications operating at the particular locality; and
storing the transit system data and UI definitions of transit-system graphical representations on a set of servers for later retrieval and transmission to different commute applications operating in different localities.
1 Assignment
0 Petitions
Accused Products
Abstract
Some embodiments provide a program that receives from several data providers route data and graphical representation of route data (e.g., transit systems, schedules, stops, etc.) for different localities. The program also stores this data on a set of servers for later retrieval and transmission to commute applications operating in different localities. The program further retrieves from external vendors location data of transit vehicles that traverse routes based on the route data and schedule data. The location data is for transmitting to commute applications.
31 Citations
27 Claims
-
1. A non-transitory machine-readable medium storing a program executable by at least one processing unit, the program comprising sets of instructions for:
-
receiving from a plurality of data providers transit system data and user interface (UI) definitions of different transit-system graphical representations specifying the manner the transit system data is presented in a particular locality when the transit system data is displayed in commute applications operating at the particular locality; and storing the transit system data and UI definitions of transit-system graphical representations on a set of servers for later retrieval and transmission to different commute applications operating in different localities. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A non-transitory machine-readable medium storing a program which when executed by at least one processing unit processes schedule and route data requests for commute applications, the program comprising sets of instructions for:
-
identifying, upon receiving a request from a particular commute application for schedule and route data, a locality of the particular commute application; retrieving schedule and route data for transit vehicles for the identified locality; from a plurality of different sets of user interface (UI) graphical representations for a plurality of different localities, identifying one set of UI graphical representations for the identified locality; and providing to the particular commute application the retrieved schedule and route data and the identified UI graphical representation set for the particular commute application to display the retrieved schedule and route data according to the retrieved UI graphical representation set for the identified locality. - View Dependent Claims (10, 11, 12, 13)
-
-
14. A system for managing data for commute applications, the system comprising:
-
a first set of servers for handling static data by receiving from a plurality of data providers route data and schedule data for the route data and storing the route data and the schedule data for later retrieval and transmission to commute applications; and a second set of servers for handling dynamic data by retrieving from external vendors location data of transit vehicles that traverse routes based on the route data and schedule data, the location data for transmission to commute applications. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27)
-
Specification