Geotemporal web and mobile service system and methods
First Claim
1. A computer-based method of organizing and structuring electronically stored information comprising:
- receiving data at a central database comprising one or more server computers executing on one or more processors, from a computing device or one or more web service server computers executing on one or more processors in communication with the central database, the received data related to content types stored on the computing device or the web service server computers, the content types comprising text, videos, photos, audio recordings, notes, calendar entries, contact entries, and GPS location data;
extracting at the central database any people, date, place, event, and related descriptor data from the received data regardless of the content types to which the received data relate and storing the extracted data in the central database;
determining at the central database if the place data has a GPS value and an estimate of error for the GPS value;
determining if the central database has any other data having a deterministic relationship to the place data that indicates a place where a moment or event took place when there is no GPS value for the place data or the estimate of error for the GPS value is above a maximum allowed error and using the other data, data received from a venue database aggregator and a geocoder service server computer in communication with the central database or the computing device to compute a valid GPS value for the place data to update the place data;
generating a plurality of nodes comprising portions of the extracted data in a plurality of formats corresponding to the generated nodes, the generated nodes comprising a person node, an event node, a date node, a place node, and related descriptor node;
generating, by the one or more processors of the central database, a plurality of composite moment records from the generated nodes, wherein each composite moment record comprises linked nodes having at least three of a person node type, date node type, place node type, event node type, and related descriptor node;
receiving at the central database a request from the computing device or from one or more web service server computers executing on one or more processors in communication with the central database or the computing device to display on the computing device a slice of data related to the extracted data, wherein the slice comprises one or more of date, person, place, or event data, weak links, slice attributes or relationship records related to the extracted data;
identifying or receiving an ordering for the requested slice at the central database;
ordering, at the central database the composite moment records to identify a sorted list of the composite moment records based on a comparison of the ordering and corresponding data of the composite moment records;
obtaining from the central database data and content on the computing device or the web service servers in communication with the computing device or the central database, data and the content corresponding to the requested slice of data related to the extracted data; and
displaying from the central database or the one or more servers in communication with the central database a display of the requested slice on the computing device.
1 Assignment
0 Petitions
Accused Products
Abstract
A system and a method are presented for providing a data schema for managing people'"'"'s important relationships to other people and businesses, past-present-future plans and events, places, activities, memorable life moments and any information about anything that exists or occurred in the earth'"'"'s time-space reality, as well as a set of Internet services and transactions that allow people to make plans for the future, discover what to do and where to go for their present and future, discover content and commercial offerings for places in which they are or may be interested, and let them organize, share, recall and relive their history in useful and powerful ways.
62 Citations
17 Claims
-
1. A computer-based method of organizing and structuring electronically stored information comprising:
-
receiving data at a central database comprising one or more server computers executing on one or more processors, from a computing device or one or more web service server computers executing on one or more processors in communication with the central database, the received data related to content types stored on the computing device or the web service server computers, the content types comprising text, videos, photos, audio recordings, notes, calendar entries, contact entries, and GPS location data; extracting at the central database any people, date, place, event, and related descriptor data from the received data regardless of the content types to which the received data relate and storing the extracted data in the central database; determining at the central database if the place data has a GPS value and an estimate of error for the GPS value; determining if the central database has any other data having a deterministic relationship to the place data that indicates a place where a moment or event took place when there is no GPS value for the place data or the estimate of error for the GPS value is above a maximum allowed error and using the other data, data received from a venue database aggregator and a geocoder service server computer in communication with the central database or the computing device to compute a valid GPS value for the place data to update the place data; generating a plurality of nodes comprising portions of the extracted data in a plurality of formats corresponding to the generated nodes, the generated nodes comprising a person node, an event node, a date node, a place node, and related descriptor node; generating, by the one or more processors of the central database, a plurality of composite moment records from the generated nodes, wherein each composite moment record comprises linked nodes having at least three of a person node type, date node type, place node type, event node type, and related descriptor node; receiving at the central database a request from the computing device or from one or more web service server computers executing on one or more processors in communication with the central database or the computing device to display on the computing device a slice of data related to the extracted data, wherein the slice comprises one or more of date, person, place, or event data, weak links, slice attributes or relationship records related to the extracted data; identifying or receiving an ordering for the requested slice at the central database; ordering, at the central database the composite moment records to identify a sorted list of the composite moment records based on a comparison of the ordering and corresponding data of the composite moment records; obtaining from the central database data and content on the computing device or the web service servers in communication with the computing device or the central database, data and the content corresponding to the requested slice of data related to the extracted data; and displaying from the central database or the one or more servers in communication with the central database a display of the requested slice on the computing device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A system for storing and managing personal information comprising:
-
a central database executing on one or more processors and one or more servers in communication with computing device, one or more web service server computers, a venue database aggregator service server, and a geocoder service server executing on one or more processors, the central database programmed or configured to receive data from the computing device or the servers in communication with the central database, the received data related to content types stored on the computing device or the one or more web service server computers, the content types comprising text, video, audio recordings, photos, calendar entries, GPS location data, and contact entries; extract any people, date, place, event and related descriptor data from the received data regardless of the content types to which the received data relate; determine if the place data has a GPS value and an estimate of error for the GPS value; determine if the central database has any other data having a deterministic relationship to the place data that indicates a place where a moment or event took place if there is no GPS value for the place data or the estimate of error is above a maximum allowed error, and use the other data, data received from the venue database aggregator server, and the geocoder service server to compute a valid GPS value for the extracted place data; generate a plurality of nodes comprising portions of the extracted data in a plurality of formats corresponding to the generated nodes, the generated nodes comprising a person node, an event node, a date node, a place node, and related descriptor node; generate a plurality of composite moment records from the generated nodes, wherein each composite moment record comprises linked nodes having at least three of a person node, date node, and related descriptor node; receive at the central database a request from the computing device or from one or more web service server computers executing on one or more processors in communication with the computing device or the central database to display on the computing device a slice of data related to the extracted data, wherein the slice comprises one or more of date, person, place, or event data, weak links or relationship records, or slice attributes related to the extracted data; identify or receive an ordering for the requested slice at the central database; order, at the central database the composite moment records to identify a sorted list of the composite moment records based on a comparison of the ordering characteristic and the corresponding data of the composite moment records; obtain from the central database the data and content on the computing device or the web service servers in communication with the computing device or the central database the data and the content corresponding to the requested slice of the extracted data; and display from the central database or from the one or more server computers in communication with the central database a display of the requested slice on the computing device in a textual display, a calendar display, or a timeline display. - View Dependent Claims (10, 11, 12)
-
-
13. A method for automatically generating and storing moment templates for creating a composite moment record in a central database for managing electronic personal information comprising:
-
receiving at a central database data from a computing device a date, time, and location of the computing device; retrieving and analyzing previously stored moment templates of composite moment records from the central database or the computing device based on the time and the location of the computing device; generating behavioral filters of multiple record moments to predict moment attributes; automatically generating a moment template for person, place, date, and event information based on comparing the date, time, and location of the computing device or recently created composite moment records with previously created composite moment records and the predicted moment attributes; receiving at the central database edited or additional person, place, date, and event data and content associated with the moment template from the computing device or one or more web service computers executing on one or more processors, the content comprising content types including one or more of text, video, audio recordings, photos, calendar entries, GPS location data, social media feeds, weather, traffic, or contact entries; updating the moment template with the edited or additional data, regardless of the content types; and creating and storing in the central database the composite moment record, wherein each composite moment record comprises linked nodes having at least a person node type, place node type, and date node type, and comprising normalized data associated with a particular node type from the updated template. - View Dependent Claims (14, 15, 16, 17)
-
Specification