Data synchronization mechanism for information browsing systems

• US 7,146,407 B2
• Filed: 10/22/2001
• Issued: 12/05/2006
• Est. Priority Date: 10/22/2001
• Status: Expired due to Fees

• Current Assignee: PhoneSpots, Inc. (UpSnap, Inc.)
• Original Assignee: PhoneSpots, Inc. (UpSnap, Inc.)
• Inventors: McNulty, John Edward, Mulford, Catherine Lee
• Primary Examiner(s): Najjah, Saleh
• Assistant Examiner(s): Hamza, Faruk
• Application Number:
  US10/037,489
• Publication Number:
  US 20030093495A1
• Time in Patent Office: 1,870 Days
• Field of Search: 709/248, 709/203, 709/217, 709/219, 709/213, 709/224, 707/3, 707/10, 455/412.1
• US Class Current: 709/217
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

Data objects are gathered and organized through a computer system and stored for subsequent access through a computer network by a mobile device such as a wireless telephone. The data objects have attributes and can be acted upon using predefined actions and associated types to greatly simplify user accessibility to such data objects through the limited user interface and bandwidth capabilities of a mobile device.

Claims

1. A method for managing information on behalf of a user, the method comprising:

receiving data representing the information from the user through a base system interface;

storing a data object representing the data in a database;

associating the data object with the user within the database;

associating the data object with a select one of two or more data object types wherein the selected data object type specifies the type of the data object;

parsing the data into one or more portions, each of which corresponds to the one or more data attributes defined for the selected data object type;

receiving a request from the user for retrieval of the data through a mobile system interface; and

sending the data to the user through the mobile system interface in accordance with one or more data attributes defined for the selected data object type; and

wherein storing the data object includes storing the one or more portions organized according to the data attributes defined for the selected data object type.

2. The method of claim 1 wherein each of the data object types is associated with a type identifier.

3. The method of claim 1 wherein the parsing is according to an attribute pattern specified for the selected data object type.

4. A method for managing information on behalf of a user, the method comprising:

receiving data representing the information from the user through a base system interface;

storing a data object representing the data in a database;

associating the data object with the user within the database;

associating the data object with a select one of two or more data object types wherein the selected data object type specifies the type of the data object;

receiving a request from the user for retrieval of the data through a mobile system interface; and

sending the data to the user through the mobile system interface in accordance with one or more data attributes defined for the selected data object type along with one or more user interface triggers by which the user can invoke one or more respectively associated actions defined for the selected object type to be taken with respect to the data.

5. The method of claim 4 wherein a selected one of the actions is to be performed by a mobile device used by the user to request the data.

6. The method of claim 5 wherein the selected action has a behavior defined by one or more instructions to be performed by the mobile device;

and

further wherein sending the data to the user includes sending the instructions with the data.

7. The method of claim 4 wherein a selected one of the actions is accessible to the user only if the selected data object type of the data object is one of one or more acceptable ones of the two or more data object types.

8. The method of claim 4 wherein performance of a selected one of the actions acts upon one or more of the data attributes of the data object.

9. The method of claim 4 wherein a selected one of the actions is accessible to the user depending upon user data representing characteristics of the user.

10. The method of claim 9 wherein the user data includes specification of a mobile data services provider.