Source: http://www.google.com/patents/US20010020255?ie=ISO-8859-1&dq=7,496,943
Timestamp: 2015-08-30 19:59:59
Document Index: 107097131

Matched Legal Cases: ['art 230', 'art 120', 'art 120', 'art 120', 'art 230', 'art 120']

Patent US20010020255 - Method and system for remote control and interaction with a run time ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA user device, a first computer system, includes a lightweight component that receives user input actions for a runtime environment component that is executing on a second computer system. The lightweight component sends a remote input action command to a user interface infrastructure that is executing...http://www.google.com/patents/US20010020255?utm_source=gb-gplus-sharePatent US20010020255 - Method and system for remote control and interaction with a run time environment componentAdvanced Patent SearchPublication numberUS20010020255 A1Publication typeApplicationApplication numberUS 09/759,786Publication dateSep 6, 2001Filing dateJan 12, 2001Priority dateJan 14, 2000Also published asEP1117035A1Publication number09759786, 759786, US 2001/0020255 A1, US 2001/020255 A1, US 20010020255 A1, US 20010020255A1, US 2001020255 A1, US 2001020255A1, US-A1-20010020255, US-A1-2001020255, US2001/0020255A1, US2001/020255A1, US20010020255 A1, US20010020255A1, US2001020255 A1, US2001020255A1InventorsRalf Hofmann, Torsten SchulzOriginal AssigneeSun Microsystems, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (26), Referenced by (26), Classifications (37), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetMethod and system for remote control and interaction with a run time environment component
[0045] where N is the size of runtime environment component 112 in bytes, CB is the average bandwidth in bits per second of the network connection between first computer system 100 and second computer system 102i, and t1 is the time needed to initialize runtime environment component 112 in its respective local environment on first computer system 100. In today's commonly available network connections between servers and clients, time t is typically be about ten seconds. [0046] When using networks commonly used at present for the connection of clients and servers, this time condition gives a lightweight component 230, which is-measured in necessary storage space-less than ten or even less than five percent of the scope of the totality of the runtime environment components 120, which can be requested by lightweight component 230, including any auxiliary software programs which these runtime environment components need to be executed in first computer system 100. [0047] Correspondence of lightweight component 230 with runtime environment component 112 means, in this context, that lightweight component 230 must offer the second computer system 102i access to the runtime environment component service made available by component 112. If a plurality of runtime environment component services 120 is made available by the lightweight component 230, which will frequently be the case, lightweight component 230, in this embodiment, corresponds to this plurality of runtime environment component services in the explained sense. [0048] Hence, in this embodiment, the software system includes two parts, a first part 230 executed on a client device 102i, and a second part 120 residing and executed on server computer system 100. Second part 120 on server 100 makes up the runtime environment, which, in this embodiment, comprises a plurality of runtime environment components, which are able to provide services. Furthermore, second part 120 on server computer system 100 provides the necessary communication tools in order to communicate with client device 102i, sometimes called user device 102i. [0049] The other part 230, being executed on client device 102i, performs communication between client device 102i in requesting a runtime environment component service being executed on server 100. The server's part of the software system is by far larger in size than the client's part thereof. This latter part is referred to as lightweight component 230. A typical size of the software system's part 120 on server computer system 100 may be 50 to 100 Megabyte, e.g., an office software package, whereas lightweight component 230 on client device 102i has a typical size of 400 Kilobyte, and uses minimal system resources (CPU power, memory). [0050] Lightweight component 230 provides an application-programming interface (API) for any application program the implementation of which on client device 102i is allowed by an implementation framework on server computer system 100. Various types of lightweight components 230 are possible. In one embodiment, the lightweight component accesses a particular functionality, e.g., a mathematical calculator on server 100, which provides a specific result to user device 102i for use. In another embodiment, lightweight component 230 handles visual functionality. [0051] Hence, in more general terms, runtime environment component services are presented by a first computer system 100 to a second computer system 102i over a communication network 103/106. Upon receiving a request for a runtime environment component service transmitted by second computer system 102i over communication network 103/106, first computer system 100 executes a runtime environment component 112 for producing a result according to the received request, and transmits, over network 103/106, a response comprising the result to the second computer system 102i. [0052] Herein, computer software programs and parts thereof, which are called during execution of a lightweight component 230, are herein referred to as runtime environment components 120. The functionality provided by runtime environment components 120 to lightweight component 230 are herein referred to as runtime environment component services. The size of runtime environment components 120 renders a distribution over Internet 106 difficult. Runtime environment components 120 may be implemented in any suitable form. Runtime environment components 120 may consist of compiled software program code to be executed or of script code in any programming language to be interpreted before execution by a compiler. Runtime environment components 120 are typically stored and administrated on server computer system 100. [0053] Lightweight component 230 makes runtime environment component services, that means the functionalities provided by runtime environment components 120, available for use without integrating components 120 into lightweight component 230 and without distributing components 120 together with lightweight component 230 to the place of execution of lightweight component 230, for example, client device 102i. [0054] Further, the full functionality of the runtime environment components 120 is available for all kinds of client devices independent of whether the client devices are powerful enough to store or to execute a runtime environment component 112. Further, the user of a client device is not charged with the problem of whether a specific runtime environment component 112 is available on client device 102i. [0055] The holding, maintaining and administrating runtime environment components 120, as well as executing runtime environment components 120, is placed on first computer system 100. Nevertheless, second computer system 102i can profit from these runtime environment component services as if the corresponding runtime environment components <