Mechanism for dependably organizing and managing information for web synchronization and tracking among multiple browsers

• US 5,951,643 A
• Filed: 10/06/1997
• Issued: 09/14/1999
• Est. Priority Date: 10/06/1997
• Status: Expired due to Term

• Current Assignee: NCR Voyix Corporation
• Original Assignee: NCR Corporation
• Inventors: Ingrassia, Jr., Michael I., Rowland, Thomas M., Shelton, James A.
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US08/944,124
• Time in Patent Office: 708 Days
• Field of Search: 707/104, 707/500, 395/200.33, 395/200.57, 395/200.54, 395/200.48, 709/227, 709/224, 709/223, 709/248
• US Class Current: 709/227
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 2216/15 Synchronised browsing

Abstract

Described is a mechanism for dependably organizing and managing information for web synchronization and tracking among multiple consumer browsers. A session is created for each of one of the consumer browsers when an individual consumer downloads an initial web page from an HTTP server. A unique ID is assigned to that session. After the session has been created for an individual browser, the information about the all activities from that consumer browser will be recorded into the session. Such a mechanism overcomes the difficulty to organize and manage the activities from the multiple consumer browsers that are in stateless nature.

Claims

1. A method of establishing a session to manage activities being performed to pages at a first terminal, comprising the steps of:

(a) receiving an initial request from said first terminal for retrieving an initial page;

(b) creating a session for said first terminal in response to said initial request;

(c) receiving subsequent requests from said first terminal for retrieving subsequent pages;

(d) monitoring activities performed to any of said initial and subsequent pages at said first terminal;

(f) storing information about said activities performed to any of said initial and subsequent pages at said first terminal into said session created for said first terminal.

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

sending said initial page to said first terminal in response to said initial request; and

sending subsequent pages to said first terminal in response to said subsequent requests.

3. The method of claim 2, further comprising the step of:

setting a session interval for said session created for said first terminal;

maintaining said session created for said first terminal, if within said session interval;

(i) at least one activity at said first terminal is performed to said initial page and subsequent pages, or (ii) a new request from said first terminal is received for retrieving a new page; and

purging said session created for said first terminal, if within said session interval created for said first terminal;

(i) no activities are performed to said initial page and subsequent pages at said first terminal, and (ii) no new requests from said first terminal are received for retrieving new pages.

4. The method of claim 2, further comprising the step of:

receiving a request from a second terminal to join said session created for the first terminal;

displaying said activities that are stored at step (g) at the second terminal; and

synchronizing subsequent activities between said first and second terminals.

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

storing said subsequent activities into said session created for said first terminal.

6. The method of claim 1, wherein the activities include:

loading a page, unloading a page, and changing a data field on a page.

7. The method of claim 1, comprising maintaining a participant list of each of the users browser participating in a session wherein a session is a collection of web page interactions that occur over a given period of time from a specific browser.

8. The method of claim 7, comprising assigning a session ID to each of the plurality of user browsers.

9. The method of claim 8, comprising maintaining a session list including information about a session, a URL history list for maintaining information about all web pages visited by all participants in a session, a data list for maintaining information about the data fields visited by all participants in a session and a command list for maintaining all commands issued to the administrative server during a session.

10. The method of claim 1, comprising bi-directionally synchronizing the administrative browser and each of the user browsers.

11. The method of claim 1, comprising loading a master applet, a DTS applet and a session ID applet on to a computer on which each of the user browsers reside.

12. The method of claim 1, comprising detecting that a change has been made to a web page and forwarding such change to the administrative browser.

13. The method of claim 1, comprising establishing a dedicated socket connection between each of the user browsers and the administrative browser.

14. The method of claim 13, comprising recognizing, at the administrative browser, which of the user browsers made a change to the web page.

15. The method of claim 1, comprising recording the URL and an update of a data field into a data list.

16. The method claim of 1, comprising assigning a session ID to each of the plurality of user browsers.

17. The method of claim 15, comprising maintaining a session list including information about a session, a URL history list for maintaining information about all web pages visited by all participants in a session, a data list for maintaining information about the data fields visited by all participants in a session and a command list for maintaining all commands issued to the administrative server during a session.

18. The method of claim 16, comprising bi-directionally synchronizing the administrative browser and each of the user browsers.

19. A method of establishing sessions to manage activities being performed to pages at a plurality of user terminals, comprising the steps of:

(a) receiving an initial request from each one of said user terminals for retrieving an initial page for said each one of said user terminals;

(b) creating a session for each one of said user terminals in response to initial requests sent from said user terminals;

(c) receiving subsequent requests from each one of said user terminals for retrieving subsequent pages for each one of said user terminals;

(d) monitoring activities performed to any of said initial and subsequent pages at each one of said user terminals;

(e) storing information about the activities performed to any of said initial and subsequent pages at each one of said user terminals into sessions created for each one of said user terminals.

20. The method of claim 19, further comprising the steps of:

(c) sending an initial page to each one of said user terminals in response to said initial request; and

(e) sending subsequent pages to each one of said user terminals in response to said subsequent requests.

21. The method of claim 19, further comprising the step of:

setting a session interval for each one of said sessions created for said user terminals;

maintaining sessions created for each one of said one of said user terminals, if within a session interval created for one of said user terminals;

(i) at least one activity is performed to said initial page and subsequent pages at said one user terminal, or (ii) a new request is received for a new page from said one user terminal; and

purging the session created for said one user terminal, if within the session interval created for said one user terminal;

(i) no activities are performed to said initial page and subsequent pages at said one user terminal, and (ii) no new requests from said one user terminal are received for new pages.

22. The method of claim 19, further comprising the step of:

receiving a request from an administrative terminal to select one of the sessions for a selected one of said user terminals;

displaying the activities of said selected session created for said selected terminal that are stored at step (g); and

synchronizing subsequent activities between the administrative terminal and said selected one user terminal.

23. The method of claim 22, further comprising the step of:

storing said subsequent activities into said session created for said first terminal.