|Publication number||US5822543 A|
|Application number||US 08/677,675|
|Publication date||Oct 13, 1998|
|Filing date||Jul 8, 1996|
|Priority date||Jul 8, 1996|
|Publication number||08677675, 677675, US 5822543 A, US 5822543A, US-A-5822543, US5822543 A, US5822543A|
|Inventors||James Michael Dunn, Edith Helen Stern, Barry Willner|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (13), Non-Patent Citations (8), Referenced by (76), Classifications (11), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention concerns a method and apparatus for gathering timing statistics in non-synchronous data communication networks; particularly statistics pertaining to data transmission times and reaction times of users at receiving stations.
The term "non-synchronous data communication networks", as used herein, is meant to connote networks in which internal clocks of sending and receiving stations are essentially not synchronizable. Typical examples of such networks are the Internet and World Wide Web; wherein transmitted data may be subject to indefinite delays due to varied routing (depending upon traffic conditions) and due to conditions encountered at individual switching nodes in any route (depending upon traffic conditions and operating speed of equipment at respective nodes). Accordingly, such networks do not lend themselves easily to gathering of timing statistics indicative of transmission time delays between sending and receiving stations. Even assuming that receiving stations send notifications of reception to origin/sending stations, such notifications would necessarily arrive at indefinite times due to indeterminate delays caused by routing and other conditions (like those encountered by transmitted data).
Furthermore, at receiving stations in such networks, the timing of user reactions to received data is generally indefinite, and, assuming receiving stations send notifications of such reaction times to origin/sending stations, times at which such notifications arrive at sending stations are necessarily indefinite due to network delays of the same type as those encountered by transmitted data.
Nevertheless, statistics indicative of data transmission times over the network and user reaction times at receiving stations may be very useful for enabling data senders to evaluate their communication needs and the effectiveness of their transmitted data. This is particularly true of public networks like the Internet, in which transmitted data may have commercial or advertising significance.
It is generally known that in such networks transmission delays are not measurable or inferrable simply from acknowledgements returned by receiving stations; inasmuch as transmitted data would encounter indeterminate routing and/or switching delays, and corresponding acknowledgements would also encounter indeterminate routing and/or switching delays generally different from those encountered by associated transmitted data. Similarly, it is understood that timing of user reactions to transmitted data, at receiving stations, is not inferrable simply from returned acknowledgements or equivalent signals inasmuch as such reaction times per se have indefinite timing relative to instants of reception and return transmissions of acknowledgements would be subject to indeterminate delays due to the network construction.
Nevertheless, information about data transmission delays, and delays in respect to user reactions to transmitted data at receiving stations, could be quite useful. For instance, the sender of an advertisement might want to know how long it took for the advertisement to reach the average receiver, and what interest is generated by the received advertisement or even specific portions thereof. Knowledge of the average transmission delay could enable senders to evaluate their communication needs and upgrade or downgrade accordingly. Similarly, knowledge of how times elapsed on average between reception of advertisements and actions indicating user interest (or even disinterest) therein could enable senders to evaluate the effectiveness of such advertisements.
In general then, for data representing various displayable offerings, advertisements, or the like, time statistics indicative of transmission delays and reactions to the received data could be of interest to senders; at least as a means for evaluating the effectiveness of transmission facilities currently being utilized and effectiveness of the data per se.
In accordance with the invention, means located at server and client nodes of a data communication network--particularly, a network in which data is subject to being transmitted over varied routes depending upon time of day, traffic, class of service, etc.--enable a computer at the server node, when transmitting data to a computer or "intelligent" terminal at the client node, to receive feedback messages from the client node containing timing useful timing statistics. More specifically, timing statistics provided in the feedback messages are useful for indicating the types and frequencies of transmission delays that are attributable to network routing, as well as indicating user reactions to transmitted data at client terminals. Thus, the owner of the transmitted data can use such statistics to determine if their network service has to be upgraded, to select optimal times of day for transmitting their data, to determine the effectiveness of the data per se in respect to those viewing the data at client stations, etc.
To induce actions at client stations resulting in return of such feedback messages, a "timing script" is incorporated into the data transmitted to each client station. This script is interpretable by an interpreter operating at the client station. For instance, on the Internet, the timing script could be written in the script language associated with the Java™ programming language (Java is a Trademark of Sun Microsystems) commonly used in Internet communications, and at the client station the timing script could be interpreted by a Java interpreter of the type commonly provided in so-called "web browsers" like Netscape's "Navigator". It should be understood that elements of the Java language are cited here only as examples; and that other script languages and their interpreters could be used for the same purpose of inducing message feedback actions.
In addition to the foregoing timing script, information added to the transmitted data (at the server) includes a "data ID" term uniquely associated to the data being transmitted, and a starting time value ST0 representing the time at which transmission of the associated data began (based on the state of the server's internal clock).
On receipt of the data at a client station, the timing script acts as instructions to the client's interpreter program causing the latter to: (a) immediately return a first message ("MSG1") to the server, and (b) start a client timer ("CT") to effectively measure elapsed time from reception of the data to one or more events specified in the timing script. MSG1 includes ST0 and the data ID.
On receiving MSG1, the server creates a current time stamp ST1, calculates the difference between ST1 and ST0, and saves the result in association with the data ID as a measure of "round-trip transmission time" taken for transfer of the data and return of MSG1. The saved result is useful for further analysis of the effectiveness of network access services then being received by the data sender. Furthermore, if MSG1 is accompanied by address information indicating the routing of that message, such address information could also be saved and used by the sender for evaluating the transmission time taken for sending the original data as well as the effectiveness of network services then being used by the sender.
Upon occurrence of a said specified event, the client computer: (a) extracts the then instantaneous value of its timer count CT as a representation "ET" of the time elapsed between receipt of the data and occurrence of the respective event; and (b) sends a second message, MSG2, to the server, this message containing the value of ET as well as the data ID and ST0. On receiving MSG2, the server creates a current time stamp ST2, calculates the difference between ST2 and ST0, and saves the result along with the value of ET, in association with the data ID, for further analysis. This second saved result is indicative of the aggregate time taken for transmission of the data, client handling of the data up to the respective event, and return transmission of MSG2; i.e. it is indicative of the aggregate round trip transmission times of the data and MSG2 plus the elapsed time ET from client reception of the data to the aforesaid event. Incidentally, it should be noted that elapsed time between transmission of the data and multiple events, the latter representing various reactions of a viewer to the transmitted data, could be determined in this manner by having the client station return additional messages MSG3, MSG4, etc.
Upon subtraction of ET from the above second result, the remainder is a useful indication of aggregate round trip transmission times for the data and MSG2. Also, comparison of that remainder with the "round trip" time derived from MSG1 may provide useful insights as to differences in return transmission routes allocated to MSG1 and MSG2. The average of these differences in return routing can be subtracted from the remainder to arrive at a reasonable measure of the transmission time of the originally sent data; i.e. as a measure of the effectiveness of network service provided for that transmission. The saved value of ET, and other values of ET derived from other feedback messages--e.g. from messages responsive to other events at the same client and/or from messages generated by other clients receiving the same data--can be used to provide the data owner (e.g. advertiser) with information indicative of various reactions to the data of end users at client stations e.g. information that could be used to evaluate the effectiveness of data constituting different advertisements of a product as an aid in selection of a most effective advertisement.
These and other features, advantages, objectives and benefits of the present invention will be more fully understood by considering the following detailed description and claims.
FIG. 1 is a schematic illustrating an aspect of problems dealt with presently in respect to gathering information about network delays encountered by transmitted data in non-synchronous data communication networks wherein data is subject to indefinite routing and switching delays.
FIG. 2 illustrates other aspects of problems dealt with presently in respect to gathering information about network delays encountered by transmitted data based on signals returned from receiving stations as soon as the latter receive the data, and about delays in timing of user reactions to the transmitted data, at receiving stations, based on other sign sent when such reactions occur.
FIG. 3 is a block diagram of an embodiment of the present invention, and its deployment at server and client nodes of a network exemplified by the Internet.
FIG. 4 is a flow diagram describing operations performed in accordance with the invention to effect transmission of data from a server station to a client station, in a form enabling the server station to gather time statistics pertaining to the time taken for the data to reach client station as well as other time statistics presently pertinent.
FIG. 5 is a flow diagram describing operations at client stations in respect to data received in the form indicated in FIG. 4, which operations result in return of messages to the server station from which presently pertinent time statistics can be calculated and saved at the client station.
1. Problems Solved By The Present Invention
A network environment in which the invention can be used to advantage is suggested in FIG. 1, and problems pertaining to gathering of delay timing statistics in such networks are explained with reference to FIG. 1 and a timing diagram in FIG. 2.
FIG. 1 shows a wide area non-synchronous data communication network 1 linking server 2 to client computer 3. It is understood that in addition to the stations containing server 2 and client system 3 the network shown may serve many other stations, both servers and clients. A presently relevant characteristic of such networks is that data is subject to indeterminate transmission delays due to either or both of: varied routing of the data (through switching equipment variably located in the network) and/or conditions encountered at network switching nodes. Such delays are necessitated by traffic volume and other circumstances both throughout the network and at individual switching nodes. Consequently, data transmitted from server 2 to client station 3 would encounter indeterminate or indefinite delays in such transmission, depending upon the number of switching nodes traversed by the data, cumulative distances between traversed switching nodes, conditions encountered within individual switching nodes (traffic conditions, operating speed of switch equipment, etc.), etc. The Internet and World Wide Web represent typical networks of this type.
Another pertinent characteristic of this type of network is that signals returned from stations receiving data to stations sending the data (e.g. from station 3 to server 1 in the illustration of FIG. 1) encounter indeterminate or indefinite network delays in their transfers that further complicate the problem of gathering or inferring timing statistics.
Referring to the timing diagram in FIG. 2, line 4 denotes time and the direction of increasing time is suggested by the arrow indicated at 4a. Broken portions of line 4 represent time intervals of indefinite or indeterminate duration.
A first time of present interest in this figure, that indicated at 5, is the time of reception of transmitted data (e.g. in FIG. 1, data received by client 3 from server 2). As noted in the discussion of FIG. 1, this time is indeterminate due to network delays that depend on network routing conditions and/or queueing delays at network switching nodes.
Now, assuming that a signal or message effectively acknowledging reception is returned from a station receiving data to the data's origin station (e.g. from client 3 to server 2 in FIG. 1), a second time of present interest would be the time elapsed between the transmission of that (acknowledging) signal or message and its arrival at its destination; i.e. the time elapsed between time points 5 and 6 in FIG. 2. As indicated by the broken line between times 5 and 6, this arrival time is also indefinite or indeterminate as suggested by the broken line between time points 5 and 6).
A third time of present interest is that elapsed between time points 5 and 7, FIG. 2. This is the elapsed time between reception of data and occurrence of a predetermined user reaction to all or part of that data; e.g. could be one of: discarding a viewable page of data evoked by a user action calling for loading of new data, selection of a particular term or symbol, in a viewable page, that effectively constitutes a "hyperlink" for initiating a predetermined communication to the origin data server, sending of a reply to data constituting an E-Mail note, etc.). As indicated by the dotted line between time points 5 and 7, this elapsed time also is of indeterminate or indefinite duration inasmuch as it depends upon unpredictable behavior of a user/viewer of the data.
Finally, assuming that the client station sends a signal or message to the origin server at user reaction time 7 (that signal or message effectively constituting an acknowledgement of occurrence of the predetermined user reaction), a fourth time of present interest would be the time elapsed between transmission of this signal or message and its arrival at the origin server (the latter time shown at 8, FIG. 2). As indicated by the dotted line between times 7 and 8, this elapsed time is also of indeterminate or indefinite duration due e.g. to unpredictable network delays and/or unpredictable queueing (traffic) conditions at network switching nodes.
A point to note in respect to reception times 6 and 8 is that although FIG. 2 shows respective signals/messages reaching the server in the same order as they were sent, they could conceivably arrive in reverse order; inasmuch as they would in general traverse different routes through switching nodes of the network and/or different aggregate queueing delays in transit through such nodes. Thus, the signal representing notification of data reception could traverse a lengthier network route than the signal representing notification of user reaction, and thereby incur a lengthier transmission delay than the user reaction notification, and/or the former signal could incur encounters lengthier aggregate queueing delays than the latter signal in transit through switching nodes of respective routes.
In an environment like the Internet, representative transmitted data could be pages displayable at the receiving client station, and a typical user reaction that could be the subject of the above notification of reaction could be one of: filling in a particular item in a form displayed in a page, selection of a highlighted text term or symbol within a displayed page (such selection e.g. effecting a hyperlink request to have a related page downloaded from the origin server), or discarding the displayed page by requesting another unrelated page, etc. Also, it is generally understood that in an environment such as the Internet, sending and receiving stations have internal clocks that are neither synchronous to each other nor synchronizable as such; and this inability to synchronize clocks further complicates the gathering of presently relevant delay timing statistics.
Referring again to FIG. 2, and considering the indefiniteness or indeterminateness of elapsed times between times 5 and 6, times 5 and 7, and times 7 and 8, it is easy to understand why it is difficult in such networks to gather timing statistics indicative of such elapsed times and of transmission and user reaction delays related to such.
Nevertheless, such statistics could be quite useful. For example, a sender of Internet pages representing commercial offerings or advertisements, might want to know the average transmission delay encountered in transmittal of their pages, and/or times of specific user reactions to items contained in their pages. Knowledge of average transmission delays could enable the sender to determine if their network access facilities are adequate for intended purposes or need upgrading. Knowledge of user reactions to specific page items might enable senders to modify their offerings or advertisements to maximize user interest and ultimately increase associated sales.
The present invention provides means for enabling senders to gather such time statistics.
2. Preferred Embodiment of the Invention
The general attributes of the invention are described below with reference to FIG. 3, and specific server and client operations pertinent to the invention are described below with reference to flow diagrams contained in FIGS. 4 and 5.
As indicated in FIG. 3, server 2', adapted in accordance with the present invention, includes means for incorporating into (or attaching to) transmitted data certain control information; the latter including a unique data identity (ID) function, a transmission start time (hereafter denoted ST0), and a "timing script" (discussed below) for inducing equipment at the receiving station to return messages containing statistically pertinent time information in a desired manner.
As indicated further in FIG. 3, client station 3', as presently adapted, contains means for interpreting the above-mentioned timing scripts and for transmitting certain return messages to servers that sent data to which respective timing scripts were attached.
The means mentioned above preferably are embodied in application programs installed at the server and client stations. The timing scripts mentioned above could be written in a script language, and the interpreter for the timing script could be contained in browser applications commonly installed at client stations. As noted earlier, a suitable script language for application of the invention to the Internet would be the script language associated with the Java™ (Trademark of Sun Microsystems) programming language, and a suitable corresponding interpreter facility for client stations could be a function that is presently available in a number of existing browser applications. For example, the Netscape Navigator™ (trademark of Netscape Corporation) is one such browser application.
Although transmission of scripted instructions is not new per se, functions evoked by the present timing script are considered novel. It should be noted that any script language and associated interpreter could be employed in the present manner. It also should be noted that it would be possible for a server to send timing scripts in any form that is likely to be interpreted at a client station (even, for instance, in multiple different script language forms tailored to different interpreters). Furthermore, users of the Internet will appreciate that script, such as that in the presently used timing script, and interpreters associated therewith, can be installed in computers at network stations (both client and server stations) in various forms; e.g. via computer readable media such as storage disks or via the network itself.
Pertinent operations of server and client stations in accordance with the invention are described next with reference to FIGS. 4 and 5.
FIG. 4 shows relevant processes performed at an Internet type server station, during retrieval and transmission of a data page requested by a client station. In response to reception of a page request from a client station (action 30, FIG. 4), the server retrieves the requested page and attaches certain information to it (actions 32, FIG. 4). The attached information includes a timing script, an initial time stamp designated ST0, a page identity (ID), and a first return message designated MSG1 (or instructions for generating such). MSG1 may include the initial time stamp ST0.
The page and attached information are sent to a network access point (action 34, FIG. 4) at which a route (or a portion of a route) is selected for transmitting the respective data and attachments to the requesting client. It is understood that such a route may consist of variably located switching nodes of the network (nodes at which data from many network sources is switchably handled relative to many network destinations).
Selection of the foregoing route is effected in the manner suggested at 36-42. In this process, partial route segments or legs are tested, and chosen or not chosen (operations 38 and 40) depending upon their instantaneous accessibility. Successive segments or legs are chosen in this manner until a complete route is formed from the initial access point to the requesting client. These tests and selections may all be made at the initial access point or distributively at that point and switching nodes between that point and the final destination. As shown at 38 and 40, if a tested leg is currently inaccessible or unavailable, an alternate leg is tried. As shown at 42, if the leg tested at 38 is available, an additional determination is made as to whether this leg is an intermediate route segment or a last one (i.e. one linking directly to the requesting client). If the determination at 42 is that the currently tested leg is intermediate, a next leg is tested as suggested by the line leading from the "N" (no) termination of 42 to the input of decision 38. If the determination at 42 is that the leg just tested is the last one of a route, the route selection is complete and the page with its additions is transferred over the route to the client station (operation 44).
As suggested at 46, upon receipt of the page and additions a number of device processes are initiated at the client station. Pertinent details of these processes are shown in FIG. 5.
At reception of the page with attached information, the attached timing script prompts computer apparatus at the client station to start an internal timer/clocked counter (operation 60) and concurrently to initiate transmission of MSG1 to a network access point (operation 61). Concurrently, the received page is displayed at the client station (operation 62), assuming that its contents are displayable in a meaningful form, and viewable by a user at that station. What occurs thereafter at the client station depends at least in part upon actions taken by such a user in respect to the displayed page or a specific portion thereof (these activities represented at 63).
While these actions are occurring, a route for transferring MSG1, from the network access point to the origin server (the server that sent the page now being displayed), is chosen by selection processes 70-73 similar to processes 36, 38, 40 and 42 of FIG. 2; and MSG1 is transmitted to the origin server over that route. Upon receiving MSG1, the origin server creates a current time stamp ST1, and stores it and ST0 for use in subsequent (transmission delay) calculations described below (operation 74). In such calculations, a difference result obtained by subtracting ST0 from ST1, would be indicative of the "round trip" transmission delays incurred in transmission of the presently displayed page to the client and return transmission of MSG1 from the client to the server.
Returning to consideration of client activities 63 occurring after formation of the display of the received page, the timing script prepares the client station to detect occurrence of one or more specific events relevant to use of the displayed page (detection action 80). Upon detection of a stipulated event, the timer started at 60 is stopped (action 81). The state of the timer counter at that instant, which represents the time elapsed since the page was received, is incorporated into a second message, MSG2, which is transferred to the network addressed to the server (operation 82), and transmitted to the server over a variable route selected by processes 70-73.
Upon receiving MSG2, the server performs operations 74 related to the contents of that message. These operations include creating and saving a time stamp ST2, representing the server's time of reception of MSG2. Differences between ST1 and ST0, and between ST2 and the sum of ST0 and ET, may be used to develop statistically relevant indications of round trip delays incurred by transmitted data and associated return messages, as well as indications of delays incurred only by transmitted data.
Relevant operations at the client station may either conclude after transmission of MSG2, or as suggested at 90 and 91, may be followed by additional operations for detecting additional user actions or subsequent to the event giving rise to MSG2. Each detection of such an additional event can be used to generate a corresponding message MSGn (n=3, 4, . . . ) to be transmitted to the server and time stamped by the latter upon reception. As indicated at 90, the number of such operations can be determined by restricting n to a value "p" predefined in the timing script (where p is equal to or greater than 2, the initial value of n). As suggested at 91, when additional activities are monitored the value of n needs to be incremented and the timer stopped at 81 needs to be restarted.
It should be appreciated that time stamps resulting from handling of more than two return messages can be used--as in the foregoing discussion of the possible statistical treatment of time values ET, ST0, ST1, and ST2 --to develop additional statistically relevant indications of round trip delays as well as delays incurred only for data transmission. These indications can be used therefore to enhance the accuracy of average indications statistically inferred from time stamps applied to only two return messages.
3. Alternate Embodiments of the Invention
The following observations, although possibly having no direct relevance to the present invention, are considered noteworthy.
Since interpreters are not standard, it may be useful to transmit redundant versions of the timing script in script languages compatible with several popular interpreters.
Alternatively, the timing script could be provided in a preselected script language and transmitted along with an "applet" (mini-application) that: self installs at the client station; then executes automatically without dependence upon any program resident at that station; and ultimately is discarded after the associated data is discarded by the client station.
Other variations, for ensuring client execution of the timing script, should be readily apparent to those skilled in presently relevant arts.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4905171 *||Nov 9, 1987||Feb 27, 1990||International Business Machines Corporation||Workstation controller performance monitor|
|US5081680 *||Nov 8, 1989||Jan 14, 1992||General Instrument Corporation||Initial reporting of remotely generated data|
|US5131848 *||Sep 19, 1990||Jul 21, 1992||Doron Precision Systems, Inc.||Testing method and apparatus|
|US5163054 *||Dec 31, 1990||Nov 10, 1992||International Business Machines Corp.||Method for data transmission using a modified high level data link control protocal|
|US5293463 *||Mar 10, 1992||Mar 8, 1994||Canon Kabushiki Kaisha||Image processing apparatus|
|US5446733 *||Feb 4, 1994||Aug 29, 1995||Fujitsu Limited||Congestion processing mode and congestion processing circuit in frame relay exchange apparatus|
|US5457806 *||Nov 29, 1993||Oct 10, 1995||Kabushiki Kaisha Toshiba||Computer system including LAN analyzer and method of analyzing communication procedure|
|US5550807 *||Sep 27, 1994||Aug 27, 1996||Fujitsu Limited||Method of measuring distance between equipments on lan and distance measuring apparatus|
|US5602992 *||Nov 29, 1993||Feb 11, 1997||Intel Corporation||System for synchronizing data stream transferred from server to client by initializing clock when first packet is received and comparing packet time information with clock|
|US5668800 *||May 2, 1994||Sep 16, 1997||International Business Machines Corporation||Path testing in communications networks|
|US5696904 *||May 31, 1995||Dec 9, 1997||Honda Giken Kogyo Kabushiki Kaisha||Data transmission method and system therefor|
|US5699511 *||Oct 10, 1995||Dec 16, 1997||International Business Machines Corporation||System and method for dynamically varying low level file system operation timeout parameters in network systems of variable bandwidth|
|US5712982 *||Sep 20, 1995||Jan 27, 1998||Alcatel Cit||TDMA point-to-multipoint transmission network with a multiframe which includes a single continuous stream of data subframes and a single free period for response-time measurements|
|1||*||IBM Technical Disclosure Bulletin; General Purpose Data Collection Method, vol. 16, No. 6, Nov. 1973, pp. 1796 1798.|
|2||IBM Technical Disclosure Bulletin; General Purpose Data Collection Method, vol. 16, No. 6, Nov. 1973, pp. 1796-1798.|
|3||*||IBM Technical Disclosure Bulletin; Network Monitor, vol. 25, No. 2, Jul. 1982, pp. 543 547.|
|4||IBM Technical Disclosure Bulletin; Network Monitor, vol. 25, No. 2, Jul. 1982, pp. 543-547.|
|5||*||IBM Technical Disclosure Bulletin; Realtime Throughput Measurement, vol. 26, No. 10B, Mar. 1984, pp. 5688 5698.|
|6||IBM Technical Disclosure Bulletin; Realtime Throughput Measurement, vol. 26, No. 10B, Mar. 1984, pp. 5688-5698.|
|7||*||IBM Technical Disclosure Bulletin; Serial Channel Utilization Distribution, vol. 22, No. 1, Jun. 1979, pp. 245 247.|
|8||IBM Technical Disclosure Bulletin; Serial Channel Utilization Distribution, vol. 22, No. 1, Jun. 1979, pp. 245-247.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US5961599 *||Oct 15, 1997||Oct 5, 1999||Lucent Technologies Inc.||Apparatus and method for computing the processing delay of adaptive applications network terminals and applications thereof|
|US6038596 *||May 23, 1997||Mar 14, 2000||International Business Machines Corporation||Method and system in a network for decreasing performance degradation triggered by multiple user redundant input events|
|US6061722 *||Dec 23, 1996||May 9, 2000||T E Network, Inc.||Assessing network performance without interference with normal network operations|
|US6131122 *||Jun 1, 1998||Oct 10, 2000||Nortel Networks Corporation||Programmable internet automation|
|US6175872 *||Dec 12, 1997||Jan 16, 2001||Gte Internetworking Incorporated||Collaborative environment for syncronizing audio from remote devices|
|US6332164 *||Oct 24, 1997||Dec 18, 2001||At&T Corp.||System for recipient control of E-mail message by sending complete version of message only with confirmation from recipient to receive message|
|US6347350 *||Dec 22, 1998||Feb 12, 2002||Intel Corporation||Driving the last inbound signal on a line in a bus with a termination|
|US6411998 *||Sep 8, 1997||Jun 25, 2002||International Business Machines Corporation||World wide web internet delay monitor|
|US6449635||Apr 21, 1999||Sep 10, 2002||Mindarrow Systems, Inc.||Electronic mail deployment system|
|US6487593 *||Apr 27, 1999||Nov 26, 2002||International Business Machines Corporation||Data processing with distributed messaging problem determination|
|US6571344 *||Dec 21, 1999||May 27, 2003||Koninklijke Philips Electronics N. V.||Method and apparatus for authenticating time-sensitive interactive communications|
|US6629171||Jan 14, 2002||Sep 30, 2003||Intel Corporation||Driving the last inbound signal on a line in a bus with a termination|
|US6717915 *||Jul 10, 1998||Apr 6, 2004||Openwave Systems, Inc.||Method and apparatus for dynamically configuring timing parameters for wireless data devices|
|US6738844||Dec 23, 1998||May 18, 2004||Intel Corporation||Implementing termination with a default signal on a bus line|
|US6754704||Jun 21, 2000||Jun 22, 2004||International Business Machines Corporation||Methods, systems, and computer program product for remote monitoring of a data processing system events|
|US6810503 *||Feb 11, 1998||Oct 26, 2004||Microsoft Corporation||Method and apparatus for controlling the timing of the invocation of events within a computer runtime environment|
|US6971094 *||Feb 22, 2000||Nov 29, 2005||Hewlett-Packard Development Company, L.P.||Deployed agent used in the installation and maintenance of software|
|US6978224||Apr 16, 2004||Dec 20, 2005||Hydrogenics Corporation||Alarm recovery system and method for fuel cell testing systems|
|US7069304 *||Jun 5, 1998||Jun 27, 2006||International Business Machines Corporation||Customizable web filler for alleviation of network latency and delay|
|US7149641||Sep 14, 2004||Dec 12, 2006||Hydrogenics Corporation||System and method for controlling a fuel cell testing device|
|US7185084 *||Sep 5, 2001||Feb 27, 2007||Intel Corporation||Server-side measurement of client-perceived quality of service|
|US7542471||Oct 29, 2003||Jun 2, 2009||Citrix Systems, Inc.||Method of determining path maximum transmission unit|
|US7616638||Jul 28, 2004||Nov 10, 2009||Orbital Data Corporation||Wavefront detection and disambiguation of acknowledgments|
|US7630305||Jul 28, 2004||Dec 8, 2009||Orbital Data Corporation||TCP selective acknowledgements for communicating delivered and missed data packets|
|US7656799 *||Jul 28, 2004||Feb 2, 2010||Citrix Systems, Inc.||Flow control system architecture|
|US7698453||Jul 28, 2004||Apr 13, 2010||Oribital Data Corporation||Early generation of acknowledgements for flow control|
|US7814225||Aug 31, 2006||Oct 12, 2010||Rumelhart Karl E||Techniques for delivering personalized content with a real-time routing network|
|US7930362||Aug 15, 2005||Apr 19, 2011||Shaw Parsing, Llc||Techniques for delivering personalized content with a real-time routing network|
|US7962482||Apr 27, 2006||Jun 14, 2011||Pandora Media, Inc.||Methods and systems for utilizing contextual feedback to generate and modify playlists|
|US7969876||Apr 24, 2009||Jun 28, 2011||Citrix Systems, Inc.||Method of determining path maximum transmission unit|
|US8006248||May 4, 2006||Aug 23, 2011||International Business Machines Corporation||Method, apparatus and computer program for facilitating communication between a client application and a server application|
|US8233392||Jul 28, 2004||Jul 31, 2012||Citrix Systems, Inc.||Transaction boundary detection for reduction in timeout penalties|
|US8238241||Jul 28, 2004||Aug 7, 2012||Citrix Systems, Inc.||Automatic detection and window virtualization for flow control|
|US8259729||Sep 25, 2009||Sep 4, 2012||Citrix Systems, Inc.||Wavefront detection and disambiguation of acknowledgements|
|US8270423||Mar 12, 2007||Sep 18, 2012||Citrix Systems, Inc.||Systems and methods of using packet boundaries for reduction in timeout prevention|
|US8306976||May 16, 2011||Nov 6, 2012||Pandora Media, Inc.||Methods and systems for utilizing contextual feedback to generate and modify playlists|
|US8310928||Dec 9, 2009||Nov 13, 2012||Samuels Allen R||Flow control system architecture|
|US8356305||Aug 31, 2006||Jan 15, 2013||Shaw Parsing, L.L.C.||Thread boundaries comprising functionalities for an event by a single thread and tasks associated with the thread boundaries configured in a defined relationship|
|US8397237||Aug 15, 2005||Mar 12, 2013||Shaw Parsing, L.L.C.||Dynamically allocating threads from a thread pool to thread boundaries configured to perform a service for an event|
|US8407722||Mar 30, 2006||Mar 26, 2013||Shaw Parsing L.L.C.||Asynchronous messaging using a node specialization architecture in the dynamic routing network|
|US8411560||Oct 28, 2009||Apr 2, 2013||Citrix Systems, Inc.||TCP selection acknowledgements for communicating delivered and missing data packets|
|US8432800||Mar 12, 2007||Apr 30, 2013||Citrix Systems, Inc.||Systems and methods for stochastic-based quality of service|
|US8437284||Mar 12, 2007||May 7, 2013||Citrix Systems, Inc.||Systems and methods for additional retransmissions of dropped packets|
|US8462630||May 21, 2010||Jun 11, 2013||Citrix Systems, Inc.||Early generation of acknowledgements for flow control|
|US8505024||Aug 31, 2006||Aug 6, 2013||Shaw Parsing Llc||Storing state in a dynamic content routing network|
|US8553699||Aug 31, 2012||Oct 8, 2013||Citrix Systems, Inc.||Wavefront detection and disambiguation of acknowledgements|
|US8824490||Jun 14, 2012||Sep 2, 2014||Citrix Systems, Inc.||Automatic detection and window virtualization for flow control|
|US8903939 *||Nov 14, 2006||Dec 2, 2014||Upc Konsultointi Oy||Communication control|
|US9008100||Oct 3, 2013||Apr 14, 2015||Citrix Systems, Inc.||Wavefront detection and disambiguation of acknowledgments|
|US9043635||Aug 15, 2005||May 26, 2015||Shaw Parsing, Llc||Techniques for upstream failure detection and failure recovery|
|US9071543||Apr 3, 2013||Jun 30, 2015||Citrix Systems, Inc.||Systems and methods for additional retransmissions of dropped packets|
|US9071648||Sep 14, 2012||Jun 30, 2015||Shaw Parsing L.L.C.||Asynchronous messaging using a node specialization architecture in the dynamic routing network|
|US9170979 *||Mar 23, 2012||Oct 27, 2015||Arm Limited||Converging interconnect node controlling operation related to associated future item in dependence upon data predicted based on current transaction data item passing through|
|US9496991||Jul 9, 2012||Nov 15, 2016||Citrix Systems, Inc.||Systems and methods of using packet boundaries for reduction in timeout prevention|
|US20030046384 *||Sep 5, 2001||Mar 6, 2003||Sudheer Sirivara||Server-side measurement of client-perceived quality of service|
|US20030131093 *||Jan 9, 2002||Jul 10, 2003||International Business Machines Corporation||System for generating usage data in a distributed information processing environment and method therefor|
|US20040054483 *||Sep 17, 2002||Mar 18, 2004||Hydrogenics Corporation||System and method for controlling a fuel cell testing device|
|US20040229954 *||May 13, 2004||Nov 18, 2004||Macdougall Diane Elaine||Selective manipulation of triglyceride, HDL and LDL parameters with 6-(5-carboxy-5-methyl-hexyloxy)-2,2-dimethylhexanoic acid monocalcium salt|
|US20040267467 *||Apr 16, 2004||Dec 30, 2004||Gopal Ravi B||Alarm recovery system and method for fuel cell testing systems|
|US20050005024 *||Oct 29, 2003||Jan 6, 2005||Allen Samuels||Method of determining path maximum transmission unit|
|US20050058131 *||Jul 28, 2004||Mar 17, 2005||Samuels Allen R.||Wavefront detection and disambiguation of acknowledgments|
|US20050060426 *||Jul 28, 2004||Mar 17, 2005||Samuels Allen R.||Early generation of acknowledgements for flow control|
|US20050063303 *||Jul 28, 2004||Mar 24, 2005||Samuels Allen R.||TCP selective acknowledgements for communicating delivered and missed data packets|
|US20050063307 *||Jul 28, 2004||Mar 24, 2005||Samuels Allen R.||Flow control system architecture|
|US20050075816 *||Sep 14, 2004||Apr 7, 2005||Hydrogenics Corporation||System and method for controlling a fuel cell testing device|
|US20060041681 *||Aug 15, 2005||Feb 23, 2006||Shaw Parsing, Llc||Techniques for delivering personalized content with a real-time routing network|
|US20060075279 *||Aug 15, 2005||Apr 6, 2006||Shaw Parsing, Llc||Techniques for upstream failure detection and failure recovery|
|US20060117318 *||Aug 15, 2005||Jun 1, 2006||Shaw Parsing, Llc||Modular event-driven processing|
|US20060212444 *||Apr 27, 2006||Sep 21, 2006||Pandora Media, Inc.||Methods and systems for utilizing contextual feedback to generate and modify playlists|
|US20060259545 *||May 4, 2006||Nov 16, 2006||International Business Machines Corporation||Method, Apparatus and Computer Program for Facilitating Communication Between a Client Application and a Server Application|
|US20070061811 *||Aug 31, 2006||Mar 15, 2007||Shaw Parsing, L.L.C.||Modular Event-Driven Processing|
|US20070239822 *||Mar 30, 2006||Oct 11, 2007||Timothy Tuttle||Asynchronous messaging using a node specialization architecture in the dynamic routing network|
|US20100088393 *||Nov 14, 2006||Apr 8, 2010||Upc Konsultointi Oy||Communication control|
|US20130254145 *||Mar 23, 2012||Sep 26, 2013||Sean James SALISBURY||Integrated circuit converging interconnect mode control|
|WO2000058904A1 *||Mar 31, 2000||Oct 5, 2000||Mathias Client Management Software Company||System and method for enterprise client relationship and product management|
|WO2006122857A1 *||Apr 12, 2006||Nov 23, 2006||International Business Machines Corporation||Method, apparatus and computer program for facilitating communication between a client application and a server application|
|U.S. Classification||709/224, 709/235, 370/252, 709/231|
|Cooperative Classification||H04L43/0864, H04L43/00, H04L12/2602, H04L43/106|
|European Classification||H04L43/00, H04L12/26M|
|Sep 9, 1996||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUNN, JAMES MICHAEL;STERN, EDITH HELEN;WILLNER, BARRY;REEL/FRAME:008161/0886;SIGNING DATES FROM 19960718 TO 19960719
|Apr 30, 2002||REMI||Maintenance fee reminder mailed|
|Oct 15, 2002||LAPS||Lapse for failure to pay maintenance fees|
|Dec 10, 2002||FP||Expired due to failure to pay maintenance fee|
Effective date: 20021013