US2008313309A1PendingUtilityA1

Client-server data transfer control

Assignee: BANERJEE PRADIPTA KUMARPriority: Jun 18, 2007Filed: Jun 18, 2007Published: Dec 18, 2008
Est. expiryJun 18, 2027(~0.9 yrs left)· nominal 20-yr term from priority
H04L 67/14
44
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Disclosed are a method, a client/server system and a computer program for controlling the data transfer from a server system to a client system that runs remotely an application on the server. The data transfer control is effected by defining a first trigger event and a second trigger event in the client system. The client system and the server are arranged so that an occurrence of a first trigger event terminates the transfer of at least one type of data from the server system to the client computer, while an occurrence of the second trigger event reintroduces the terminated data transfer.

Claims

exact text as granted — not AI-modified
1 . A method for controlling data transfer between a client system and a server system, the client system running an application remotely on the server system, the method comprising:
 defining a first trigger event and a second trigger event in the client system;   terminating the transfer of at least one type of data from the server system to the client system upon occurrence of the first trigger event; and   reintroducing the terminated data transfer from the server system to the client system upon occurrence of the second trigger event.   
   
   
       2 . The method of  claim 1 , wherein the first trigger event is defined by the application being inactive for a predetermined length of time. 
   
   
       3 . The method of  claim 1 , wherein the first trigger event is defined by the absence of an input signal to the client system for a predetermined length of time. 
   
   
       4 . The method of  claim 2 , wherein the first trigger event is the occurrence of minimisation of a window presented on the screen of the client system, the window corresponding to the application that is run remotely by the client system on the server system 
   
   
       5 . The method of  claim 1 , wherein the second trigger event is the occurrence of maximisation of the minimised window. 
   
   
       6 . The method of  claim 1 , wherein the first and the second trigger events are defined by an opening and closing of a window of another application, respectively. 
   
   
       7 . The method of  claim 1 , wherein the at least one type of data includes at least one of text, graphics, standard output and standard error data. 
   
   
       8 . A client/server system comprising a client system running an application remotely on a server system, the client/server system being arranged for controlling the data transfer from the server system to the client system by:
 defining a first trigger event and a second trigger event in the client system;   terminating the transfer of at least one type of data from the server system to the client system, upon occurrence of the first trigger event; and   reintroducing the terminated data transfer from the server system to the client system upon occurrence of the second trigger event.   
   
   
       9 . The system of  claim 8 , wherein the first trigger event is defined by the application being inactive for a predetermined length of time. 
   
   
       10 . The system of  claim 8 , wherein the first trigger event is defined by the absence of an input signal to the client system for a predetermined length of time. 
   
   
       11 . The system of  claim 9 , wherein the first trigger event is the occurrence of minimisation of a window presented on the screen of the client system, the window corresponding to the application that is run remotely by the client system on the server system. 
   
   
       12 . The system of  claim 8 , wherein the second trigger event is the occurrence of maximisation of the window. 
   
   
       13 . The system of  claim 8 , wherein the first and the second trigger events are defined by an opening and closing of a window of another application, respectively. 
   
   
       14 . The system of  claim 8 , wherein the at least one type of data includes at least one of text, graphics, standard output and standard error data. 
   
   
       15 . A computer program product comprising a computer usable medium including a computer readable program, wherein the computer readable program, when executed on a networked system including a client system and a server system, the client system remotely running an application on the server system, causes:
 defining a first trigger event and a second trigger event in the client system;   terminating the transfer of at least one type of data from the server system to the client system, upon occurrence of the first trigger event, and   reintroducing the terminated data transfer from the server system to the client system upon occurrence of the second trigger event.   
   
   
       16 . A signal bearing medium tangibly embodying a set of machine readable instruction when executed on a processor of a networked system including a client system and a server system, the client system configured to remotely execute an application on the server system, causes:
 defining a first trigger event and a second trigger event in the client system;   terminating the transfer of at least one type of data from the server system to the client system, upon occurrence of the first trigger event, and reintroducing the terminated data transfer from the server system to the client system upon occurrence of the second trigger event.   
   
   
       17 . The system of  claim 16 , wherein the first trigger event is defined by the application being inactive for a predetermined length of time. 
   
   
       18 . The system of  claim 16 , wherein the first trigger event is defined by the absence of an input signal to the client system for a predetermined length of time. 
   
   
       19 . The system of  claim 16 , wherein the at least one type of data includes at least one of text, graphics, standard output and standard error data.

Join the waitlist — get patent alerts

Track US2008313309A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.