WO1998035300A1 - Procede de gestion d'une connexion reseau - Google Patents

Procede de gestion d'une connexion reseau Download PDF

Info

Publication number
WO1998035300A1
WO1998035300A1 PCT/US1998/001367 US9801367W WO9835300A1 WO 1998035300 A1 WO1998035300 A1 WO 1998035300A1 US 9801367 W US9801367 W US 9801367W WO 9835300 A1 WO9835300 A1 WO 9835300A1
Authority
WO
WIPO (PCT)
Prior art keywords
client computer
client
data
host
computer
Prior art date
Application number
PCT/US1998/001367
Other languages
English (en)
Other versions
WO1998035300A9 (fr
Inventor
Bram Ambrose
James R. Weatherwax
Original Assignee
Tggh, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tggh, Inc. filed Critical Tggh, Inc.
Priority to AU58281/98A priority Critical patent/AU5828198A/en
Publication of WO1998035300A1 publication Critical patent/WO1998035300A1/fr
Publication of WO1998035300A9 publication Critical patent/WO1998035300A9/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • This invention relates to the field of computing, and more particularly describes a method for managing a network connection between host and client computers.
  • the Internet is a network of thousands of large, sophisticated computers connected together with high-speed data transmission lines. These sophisticated "host” computers each typically comprise hundreds or thousands of data ports, each data port either permanently connected to another smaller, personal computer, or more likely, connected to a modem. Each modem is connected to a telephone line so that an authorized user, using a communications program running on their own “client” computer, may dial into the larger computer system using a modem attached to the client computer, thus gaining access to the network.
  • LAN Local Area Networks
  • intranets which often connect multiple LAN's together so groups of people such as employees in one division of a company may intelligently communicate and pass data between themselves and other related groups of people, such as people in a different division of the same company.
  • ISP's Internet Service Providers
  • ISP's Internet Service Providers
  • a properly managed host computer modem data port may support approximately forty or more client connections, with each client computer being connected to the network approximately 18 or fewer hours each month, taking into account a twenty-four hour day.
  • a modem-based host-client connection typically begins with the client computer initiating a telephone connection to the host using the client computer modem, and once the telephone connection is established, client and host computer modems negotiate data rates and the respective computers swapping other important data, such as login identification and password.
  • client and host computer modems negotiate data rates and the respective computers swapping other important data, such as login identification and password.
  • Some ISP's provide a service wherein, once a connection is established between the client and host computers, the connection is allowed to remain intact indefinitely. While this unlimited connection is in use, the modem line and data port is unusable for other connections, thus limiting the number of client computers that particular modem and telephone line (“modem connection”) would support.
  • modem connection modem connection
  • allowing a user unlimited connectivity time may provide flexibility to the user of a client computer, it may be less than optimally efficient in that by allowing a user to remain on line indefinitely regardless of the amount or content of activity taking place, a user may dominate a valuable host computer modem connection regardless of whether the user is actively using that modem connection for data transmission.
  • ISP's manage their client-host-modem connections by monitoring the activity over the respective data port, and terminate the modem connection if a designated interval of time passes without any activity.
  • an ISP host computer sets and starts a countdown timer for a reasonable period of time, for instance 10 minutes, and resets the countdown timer each time data of any type is transmitted to and/or received from the host computer. If the time remaining on the countdown timer counts down to zero, the ISP host computer terminates the connection.
  • this type of monitoring reacts to any activity, regardless of what that activity comprises. It would be beneficial to provide a method for managing a network connection which takes into account the particular type of data being transmitted and received between client and host computers.
  • Yet a further object and advantage of the present invention is to provide a method for causing a client computer to display a message on a display associated with the client computer while the client computer is connected to the host computer, and terminating such connection if the client computer ceases to display the message.
  • FIG. 1 is a flow chart illustrating a conventional method of managing a network connection.
  • FIG. 2 is a schematic representation of a host-client computer connection and associated equipment according to a presently preferred embodiment of the present invention.
  • FIGS. 3 A and 3B are a flow chart illustrating the steps for managing the host computer side of a network connection according to a presently preferred embodiment of the present invention.
  • FIGS. 4 A and 4B is a flow chart illustrating the steps for managing the client side of a network connection according to a presently preferred embodiment of the present invention.
  • FIG. 5 is a schematic representation of a client computer display window according to an alternate embodiment of the present invention.
  • FIG. 6 is a flow chart illustrating the steps for utilizing tracking of disk caching data received over a network connection according to a presently preferred embodiment of the present invention.
  • FIG. 1 is a flow chart illustrating a conventional method of managing a network connection.
  • a connection between host and client computers is established in step 10.
  • the host computer performs some housekeeping functions, one of which in step 12, is to set one or more timers which, by counting up or down, track the connection time and the time between periods of activity over the host- client connection.
  • the timers are set for the maximum allowable time for inactivity, and maximum connection time respectively, and that the timers count down to zero.
  • step 14 tests to see if the connection time has exceeded the maximum allowable time. If yes, the connection is terminated by the host computer in step 16. If the maximum allowable time has not been exceeded, however, the method proceeds to step 18 where the host computer decides if any activity has occurred since the last reset of the activity timer. If yes, the host computer resets the activity timer in step 20 and restarts the process again by checking the connection timer in step 14. However, if no activity has occurred, the host computer then looks at the activity timer in step 22 to see if the activity timer has expired, i.e. counted down to zero. If the activity timer has expired, the user has exceeded allowable limits of inactivity, and the method proceeds to step 16 and terminates the network connection between client and host computers.
  • a connection between client and host computers may be more efficient and provide more utility to the user if managed by taking into account details such as whether the user is sitting at the computer, whether a specific display window is open on the client computer display for the display of messages which may be beneficial to the user, and so forth.
  • the present invention provides a method of managing a network connection wherein the connection remains intact only if certain specific conditions are met.
  • the client computer requests window presentation data from the host computer at periodic intervals, and that window presentation data, when received by the client computer, is displayed on the client computer display. If the client computer fails to request window presentation data within a particular time period, the host computer terminates the connection.
  • FIG. 2 is a schematic representation of a host-client computer connection and associated equipment according to a presently preferred embodiment of the present invention.
  • a completed host-clientcomputer connection 24 comprises a host computer 26 with data port (not shown) connected to a modem 28.
  • a modem is an interface between the digital information the computer uses, and the audio tones commonly transmitted over telephone lines, and performs the conversion from digital form to analog form and back again, thus enabling computers to communicate over telephone lines.
  • Modem 28 is connected to telephone or other data line 30, which is usually coupled through switching units to client computer modem 32.
  • the client modem performs a similar function as the host computer modem, translating data from analog form to digital form and back again.
  • Modem 32 is connected to client computer 34, which itself is connected to a mouse 36, and a video display 138.
  • client computer 34 which itself is connected to a mouse 36, and a video display 138.
  • a display window 40 is caused to open and window presentation data in video display 38.
  • the window presentation data to be displayed is provided by the host computer at regular intervals during the time the host-client connection is intact. It is preferred that the display window on the client computer be configured such that it remains on top of all other windows, regardless of when those other windows were opened.
  • window-on-top bit for the client computer display window must be reasserted at regular intervals. The presently preferred interval is between approximately 20 to about 40 seconds.
  • the order of many of the steps may be modified, and some steps removed, and still accomplish the same effect.
  • the inactivity timer and the connection timer on the host computer may be removed in favor of asking a question in the video display which the user must respond to in order to keep the host-client connection intact.
  • FIGS. 3A and 3B are a flow chart illustrating the steps for managing the host computer side of a network connection according to a presently preferred embodiment of the present invention.
  • the presently preferred embodiment of the present invention proceeds similar to the conventional method where, in step 10, the connection between host and client computers is established, and proceeding to step 12, where the connection timer and the activity timer are set.
  • the host computer software and client computer software have new unique features, as described below.
  • step 42 the host computer software causes an additional "data" timer to be set up for tracking the time between requests by the client computer for window presentation data.
  • Step 14 verifies if the connection time has been exceeded, and, if true, proceeds to step 16 to terminate the connection. If, in step 44, the maximum duration between client computer requests for window presentation are exceeded, the host computer terminates the host-client connection in step 16. If the time limit for requesting window presentation data is not exceeded, the activity timer is checked in step 22, with the same results as in the conventional method. If all conditions for keeping the connection intact have been satisfied, the method proceeds in FIG. 3B, verifying if activity has taken place over the host-client connection in step 18.
  • One use for ensuring that a client computer requests window presentation data on a regular basis occurs in the advertising industry. If a client computer is connected to a host computer subsidized by advertising companies desiring to cause a particular message to be displayed on a client computer screen, the advertising company might wish to ensure that a new advertising message is requested by the client computer regularly. Once the resulting window presentation data is received from the host computer by the client computer, the message is displayed in a window on the client computer display. If a new message isn't requested frequently enough, or if the display window is closed or otherwise altered, the host computer terminates the connection.
  • step 46 the host computer determines if a request for window presentation data has been received. If yes, the data timer is reset in step 48, and the requested data is sent to the client computer in step 50. If no, the method returns to step 14, where the connection time is compared to allowable time limits.
  • An alternative embodiment further comprises the host computer tracking the activity of the client computer which are distinct from network management, such activities as FTP, TELNET, and Web Browsing.
  • Web Browsing refers to the activity performed by the user of a client computer using a computer program, commonly called a browser, such as Netscape ® 3.0 or Microsoft ® Internet Explorer ® , to view information presented by publicly accessible Internet computer sites. This information is often interesting to a user, and a significant amount of information on nearly every topic imaginable is available.
  • FTP is a method used to transfer data within the internet, and the address information provided in the link information associated with window presentation data might cause the client computer to download a particular file useful to those users of client computers who desire further information about the data being displayed when the user selected the window.
  • IRC is a method used throughout the internet by many thousands of users to communicate to each other in "real time”, sending messages to each other on public and private "channels". A user selecting a display window presenting data related to an IRC channel might then cause the IRC application to load and open communication to a particular channel on IRC.
  • the host computer would, using the standard TCP message structure, isolate the destination port used to execute a particular request, and add that port information to the user profile of the client computer.
  • the destination port of a TCP request provides information as to the type of activity, i.e. (File transfer Protocol (FTP), TELNET, etc., being performed. Port numbers currently range from 1 to 65535, and any acceptable port number will work with the present invention.
  • FTP File transfer Protocol
  • TELNET TELNET
  • Port numbers currently range from 1 to 65535, and any acceptable port number will work with the present invention.
  • the window presentation data sent by the host computer might be different for frequent FTP users than it is for frequent users of web browsers.
  • a seperate display window for presenting data need not be opened on the client computer display seperate and distinct from other windows present on the client computer display.
  • the "display window" could instead be built into a Web Browser, an FTP application, an IRC application such as MIRC, or any other host- client interaction software.
  • FIGS. 4 A and 4B is a flow chart illustrating the steps for managing the client side of a network connection according to a presently preferred embodiment of the present invention.
  • the client computer is expected to display the data received from the host computer.
  • the host-client connection is established in step 52.
  • the client computer in step 54, is caused to request window presentation data from the host computer. Recall that this is the expected data request that will reset the data timer in the host computer, thus keeping the host-client connection intact, assuming all other conditions are met.
  • a data timer is set up in the client computer so that the maximum allowable time between data requests as set on the host computer data timer will not be exceeded.
  • the client computer data timer can be set to any interval from 1 to approximately 1000 seconds and be effective in controlling the network connection, it is preferred that a host-client system requires that a window presentation data request be performed at least once every two minutes, further requiring that the client data timer should be set between approximately 30 to about 100 seconds. Setting the client computer data timer at approximately 30 seconds is preferred when the host computer data timer is set at approximately two minutes because that timing arrangement provides an opportunity for recovery in the event that the data request isn't immediately honored by the host computer. It is wise to set the data timer on the client computer to a time period which is approximately one-half of the maximum allowable time between data requests set on the host computer or less.
  • step 58 the client computer determines if the data request has been honored by the host computer, and if the requested data type has been sent. If not, the method proceeds again with step 54, where the request is again sent from the client computer to the host. If the data request is honored and the data is subsequently transmitted to the client computer, the client computer is caused to perform step 60 and verifies whether a display window specifically designated for displaying the received data is open. If not, a suitable window is initialized and opened on the client computer display in step 62. If the window was opened previously, step 62 isn't performed, and the data is displayed in step 64.
  • step 66 it is determined whether the user of the client computer has selected the display window with the mouse. Typically, the selection takes place by the user clicking a mouse button one or more times in quick succession while the mouse pointer is positioned on the client computer display within the confines of the display window.
  • link information may be found within each packet of window presentation data received from the host computer. The user, by selecting the display window as described above, may utilize that link information to perform tasks associated with the particular information.
  • Such a link information could be an HTTP address, pointing to a web page where further information related to the window presentation data might be stored.
  • the link information may include a FTP address, Internet Relay Chat (IRC) channel, TELNET data, or any other application-related data usable on the client computer.
  • IRC Internet Relay Chat
  • TELNET data
  • the window presentation data in the display window on the client computer might involve the company annual report.
  • the link information in step 68, might cause an application on the client computer to load, and then, in step 70, further cause an electronic version of the annual report to be transmitted from a different division and acted upon using the previously loaded application.
  • a Web Page is a collection of text, graphics, and sometimes sound bites, put together into viewable form, and accessible to users of Web Browsers.
  • the information is generally stored on various host computers which are connected together throughout the world, the host computers which are usually identified as the "internet" as defined earlier.
  • step 72 verifies that the user of the client computer has not caused the window to close, and if so, step 74 terminates the host-client connection. However, if the window remains open, step 76 loops until the data timer on the client computer counts down to zero, and then initiates a new data request in step 54, beginning the client process again.
  • the data type be text, a graphical display, or other type of display.
  • the presently preferred embodiment of the present invention involves the client computer periodically requesting and receiving data from the host computer in order that the connection between the two computers remain intact.
  • An alternative embodiment instead comprises the host computer periodically requesting certain data from the client computer.
  • the client computer may have a device such as an infrared camera or other sensory device for detecting if the user of the client computer is actually sitting at the desk or table containing the computer system.
  • the client computer would send that status information to the host computer when requested, and the host computer would maintain the host-client connection so long as certain predefined conditions were satisfied.
  • FIG. 5 is a schematic representation of a client computer display window according to an alternate embodiment of the present invention.
  • a display window 78 comprises a viewing area 80, with an optional border 82, and user select buttons 84a through 84e. Although five buttons are shown, it is feasible to utilize from approximately 1 to about ten user select buttons 84a-84j per display window.
  • User select buttons 84a-84j may be be defined in one of more data packet types received from the host computer as a result of the client request for window presentation data in step 54 of FIG. 4a, or instead be predefined in client software to display certain information and accomplish certain tasks. An advertising company subsidizing the host computer operations might wish to use these buttons as miniature displays of company logos or other company material.
  • buttons may be selected from one or more of these window presentation data-defined buttons to be immediately taken to a web page of the company whose logo appeared in the button.
  • Those of ordinary skill int he art will readily recognize many uses for these buttons that are within the scope and spirit of the presnet invention.
  • FIG. 6 is a flow chart illustrating the steps for utilizing tracking of disk caching data received over a network connection according to a presently preferred embodiment of the present invention.
  • window presentation data is received in 86 by the client computer as a result of a request such as seen in step 54 in FIG. 4a.
  • step 88 it is determined if the received data contains all of the required information for display, i.e. whether it is the larger, more complete data ready for display, or rather the smaller referring data packet. If the data received contains all data required for display, that data is stored on the client computer in step 90, displayed in step 92, and then it is determined, in step 94, if there are too many data files stored on the client computer storage media. If yes, step 96 deletes one or more data files, this file deletion may occur by deleting all data files at once, deleting one or more files based on how long the file has existed on the client computer, or any other suitable method.
  • step 88 we assumed that all required data for display was contained in the data received from the host computer. If however, the smaller, more compact data packet was received, in step 98 it is determined if the more complete data file is already stored on the client computer storage media. If so, the data is retrieved, in step 100, and displayed in step 92. If not, the more complete data packet is requested from the host computer in step 110, received in step 112, and stored on the client computer in step 114. the method then proceeds by displaying the more complete data packet in step 92.

Abstract

Au moment d'établir une connexion réseau entre des ordinateurs hôte (26) et client (34), l'ordinateur client (34) est configuré de manière à ouvrir une fenêtre d'affichage qui reste visible au-dessus d'autres fenêtres d'affichage, tout le long de la connexion réseau. L'ordinateur client (34) est programmé pour qu'il demande périodiquement l'affichage, dans les fenêtres d'affichage, de nouvelles données sur la présentation des fenêtres. Un logiciel de l'ordinateur hôte (26) contrôle (42) le temps s'écoulant entre les différentes demandes de nouvelles données sur la présentation des fenêtres provenant de l'ordinateur client (34), mettant fin à la connexion (16) si celle-ci dépasse un temps prédéterminé (14). Un autre aspect de la présente invention, permet non seulement de contrôler l'activité (18) de la connexion réseau, mais également de choisir les données sur la présentation des fenêtres devant être affichées dans la fenêtre d'affichage, en fonction de certaines fonctions (66, 68, 70) effectuées par le client ou de certaines données ou certains types de données qu'il consulterait à nouveau. Dans encore un autre aspect de la présente invention, l'ordinateur client (34) peut procéder à la mise en antémémoire des données sur la présentation des fenêtres, afin d'accélérer d'autres opérations réseau.
PCT/US1998/001367 1997-01-23 1998-01-23 Procede de gestion d'une connexion reseau WO1998035300A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU58281/98A AU5828198A (en) 1997-01-23 1998-01-23 Method for managing a network connection

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US78812897A 1997-01-23 1997-01-23
US08/788,128 1997-01-23

Publications (2)

Publication Number Publication Date
WO1998035300A1 true WO1998035300A1 (fr) 1998-08-13
WO1998035300A9 WO1998035300A9 (fr) 1999-01-07

Family

ID=25143524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/001367 WO1998035300A1 (fr) 1997-01-23 1998-01-23 Procede de gestion d'une connexion reseau

Country Status (2)

Country Link
AU (1) AU5828198A (fr)
WO (1) WO1998035300A1 (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6351745B1 (en) 1996-02-28 2002-02-26 Netzero, Inc. Communication system for distributing such message as advertisement to user of terminal equipment
US6366298B1 (en) 1999-06-03 2002-04-02 Netzero, Inc. Monitoring of individual internet usage
US6463468B1 (en) 1999-06-01 2002-10-08 Netzero, Inc. Targeted network video download interface
US6639608B1 (en) 1996-01-23 2003-10-28 Yuichiro Itakura System for displaying two independent images received from network
US6711551B1 (en) 1996-06-05 2004-03-23 Netzero, Inc. Information provider, terminal and system and recording medium for the terminal
US6757661B1 (en) 2000-04-07 2004-06-29 Netzero High volume targeting of advertisements to user of online service
US6766369B1 (en) 1998-03-09 2004-07-20 Net Zero, Inc. Internet service error tracking
US6928615B1 (en) 1999-07-07 2005-08-09 Netzero, Inc. Independent internet client object with ad display capabilities
US7020690B1 (en) 1999-10-19 2006-03-28 Netzero, Inc. Inactivity timer for an internet client
US7054900B1 (en) 2000-08-18 2006-05-30 Netzero, Inc. Automatic, profile-free web page recommendation
US7353267B1 (en) 2000-04-07 2008-04-01 Netzero, Inc. Targeted network video download interface
US8645856B1 (en) 2000-08-04 2014-02-04 Netzero, Inc. Ticker for internet client

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5351240A (en) * 1992-05-08 1994-09-27 Scientific-Atlanta, Inc. Communication link having dynamically allocatable auxiliary channel for data bursts
US5696901A (en) * 1993-01-08 1997-12-09 Konrad; Allan M. Remote information service access system based on a client-server-service model

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5351240A (en) * 1992-05-08 1994-09-27 Scientific-Atlanta, Inc. Communication link having dynamically allocatable auxiliary channel for data bursts
US5696901A (en) * 1993-01-08 1997-12-09 Konrad; Allan M. Remote information service access system based on a client-server-service model

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6639608B1 (en) 1996-01-23 2003-10-28 Yuichiro Itakura System for displaying two independent images received from network
US6351745B1 (en) 1996-02-28 2002-02-26 Netzero, Inc. Communication system for distributing such message as advertisement to user of terminal equipment
US6711551B1 (en) 1996-06-05 2004-03-23 Netzero, Inc. Information provider, terminal and system and recording medium for the terminal
US7240110B2 (en) 1998-03-09 2007-07-03 Netzero, Inc. Internet service error tracking
US6766369B1 (en) 1998-03-09 2004-07-20 Net Zero, Inc. Internet service error tracking
US6463468B1 (en) 1999-06-01 2002-10-08 Netzero, Inc. Targeted network video download interface
US6505201B1 (en) 1999-06-03 2003-01-07 Net Zero, Inc. Apparatus for monitoring individual internet usage
US6366298B1 (en) 1999-06-03 2002-04-02 Netzero, Inc. Monitoring of individual internet usage
US6928615B1 (en) 1999-07-07 2005-08-09 Netzero, Inc. Independent internet client object with ad display capabilities
US7020690B1 (en) 1999-10-19 2006-03-28 Netzero, Inc. Inactivity timer for an internet client
US6757661B1 (en) 2000-04-07 2004-06-29 Netzero High volume targeting of advertisements to user of online service
US7181415B2 (en) 2000-04-07 2007-02-20 Netzero, Inc. Targeting of advertisements to users of an online service
US7353267B1 (en) 2000-04-07 2008-04-01 Netzero, Inc. Targeted network video download interface
US7516213B2 (en) 2000-04-07 2009-04-07 Netzero, Inc. Automatic video display on a computer
US8645856B1 (en) 2000-08-04 2014-02-04 Netzero, Inc. Ticker for internet client
US7054900B1 (en) 2000-08-18 2006-05-30 Netzero, Inc. Automatic, profile-free web page recommendation

Also Published As

Publication number Publication date
AU5828198A (en) 1998-08-26

Similar Documents

Publication Publication Date Title
Gribble et al. System design issues for Internet middleware services: Deductions from a large client trace
US7013327B1 (en) Method and apparatus for computing within a wide area network
US8671192B2 (en) Internet use monitoring system
US6381635B1 (en) Method for displaying multiple performance measurements of a web site using a platform independent program
US6271752B1 (en) Intelligent multi-access system
US6639608B1 (en) System for displaying two independent images received from network
US20030174154A1 (en) User interface for interfacing with plural real-time data sources
WO1998035300A1 (fr) Procede de gestion d'une connexion reseau
WO1998035300A9 (fr) Procede de gestion d'une connexion reseau
EP0974900A2 (fr) Méthode pour la communication entre les frames dans une fenêtre d'un chercheur d'internet
US20040024910A1 (en) Adaptive synchronization of service data
CA2479615A1 (fr) Systeme d'affichage multiutilisateur et procede de commande connexe
US20070061869A1 (en) Access of Internet use for a selected user
US7516236B2 (en) Method to improve perceived access speed to data network content using a multicast channel and local cache
WO2000036807A2 (fr) Reseau prive virtuel chiffre servant a acceder a des detecteurs a distance
Cisco Managing Applications
Cisco Using Polling to Monitor Network Performance
EP2207328B1 (fr) Synchronisation adaptative de données de service
EP1242922A1 (fr) Procede permettant de telecharger des informations en arriere-plan depuis un reseau informatique
Cisco Monitoring Your Network Using Traffic Monitor and Protocol Monitor
Cisco Monitoring Your Network Using Traffic Monitor and Protocol Monitor
WO2001059551A2 (fr) Interface d'utilisateur concue pour interagir avec plusieurs sources de donnees en temps reel
Cisco Monitoring Your Network Using Traffic Monitor and Protocol Monitor
Cisco Monitoring Your Network Using Traffic Monitor and Protocol Monitor
Cisco Monitoring Your Network Using Traffic Monitor and Protocol Monitor

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM GW HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
COP Corrected version of pamphlet

Free format text: PAGES 1/8-8/8, DRAWINGS, REPLACED BY NEW PAGES 1/5-5/5; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: CA

122 Ep: pct application non-entry in european phase