US20040075619A1 - Screen sharing - Google Patents
Screen sharing Download PDFInfo
- Publication number
- US20040075619A1 US20040075619A1 US10/609,009 US60900903A US2004075619A1 US 20040075619 A1 US20040075619 A1 US 20040075619A1 US 60900903 A US60900903 A US 60900903A US 2004075619 A1 US2004075619 A1 US 2004075619A1
- Authority
- US
- United States
- Prior art keywords
- screen sharing
- remote device
- session
- sharing session
- viewing
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
- G06F3/1454—Digital output to display device ; Cooperation and interconnection of the display device with other functional units involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Definitions
- This invention relates generally to sharing screen information from one device with another device and, more particularly, to using a separate host device to mediate a screen sharing session between the two devices.
- GUI graphical user interface
- the invention is directed to a method, which includes receiving an indication of a screen sharing condition from a remote device, receiving data from a viewing device, and hosting a screen sharing session between the remote device and the viewing device. Capabilities associated with the screen sharing session are based on the screen sharing condition.
- a host device may be used to host the screen sharing session between the remote device and the viewing device.
- the host device may be located outside of a firewall or internal network on which the remote device resides, making the host device accessible to both the remote device and the viewing device.
- use of the host device reduces the need to address the remote device directly to perform screen sharing.
- Screen sharing thus can be implemented over a public network, such as the Internet, and in cases where the remote device is located behind a firewall or other security system.
- Another advantage results from capabilities associated with the screen sharing session being based on the screen sharing condition. More specifically, the amount of control a viewing device has over a remote device in a screen sharing session may be dictated by conditions (e.g., screen sharing conditions) on the remote device.
- a blood analyzer having an associated computer with display screen
- operational conditions of the blood analyzer may limit the amount that a viewing device can change the configuration of the blood analyzer.
- the viewing device may be limited, e.g., to viewing the display screen of the blood analyzer.
- the viewing device may reconfigure the blood analyzer via the blood analyzer's computer during a screen sharing session with the computer.
- the indication of a screen sharing condition may be an indication of an alarm condition in the remote device.
- the alarm condition may indicate a problem with the remote device and/or may be timing data.
- the indication may be received as a series of pings output by the remote device. The pings may decrease in frequency over time.
- the data received from the viewing device may identify the viewing device and the remote device.
- Hosting the screen sharing session may include determining an extent to which the viewing device is permitted to share the screen of (e.g., control) the remote device based on one or more predetermined rules.
- the screen sharing condition may include a state of the remote device.
- Hosting the screen sharing session may include determining an extent to which the viewing device is permitted to share the screen of the remote device based on the state of the remote device.
- Hosting the screen sharing session may include transmitting information associated with the screen sharing session between the remote device and the viewing device.
- Hosting may also include transferring a file between the remote device and the viewing device.
- Information prior to (e.g., during set-up), and during, the screen sharing session may be transmitted using HTTP.
- the information may encrypted.
- Hosting the screen sharing session may include transmitting graphics changes between the remote device and the viewing device.
- the graphics changes may include only portions of graphics on the remote device that are changed.
- Hosting the screen sharing session may include storing, in an audit log, information relating to the screen sharing session.
- Hosting may also include making a session key available to the remote device and to the viewing device, the session key providing access to the screen sharing session, receiving session keys from both the remote device and the viewing device, and establishing the screen sharing session in response to receiving the session keys.
- the session keys may be made available by providing the session keys directly to the remote device and to the viewing device.
- the session keys may be made available by posting the session keys on a Web page.
- Hosting the screen sharing session may include changing capabilities associated with the screen sharing session dynamically in response to a change in the screen sharing condition. Changing the capabilities associated with the screen sharing session may include terminating the screen sharing session or reducing an amount of control over the remove device via the screen sharing session.
- Hosting the screen sharing session may include directing communications transmitted during the screen sharing session to one of multiple hosts.
- a report relating to the screen sharing session may be generated.
- the invention is directed to a method, which includes outputting an indication to a host device that a screen sharing condition has occurred and establishing a screen sharing session via the host device.
- the screen sharing session includes receiving user inputs via the host device and providing graphics changes to the host device.
- the indication may be an alarm condition indicative of a problem and/or time data.
- the screen sharing session may be established by obtaining a session key made available by the host device and providing the session key to the host device. Information relating to the screen sharing session may be transmitted via the host device using HTTP.
- the user inputs may include mouse data and keyboard data and the graphics changes may include updates that occurred since transmitting a previous graphics change.
- the invention is directed to a method, which includes receiving an indication from a remote device that a screen sharing condition has occurred and establishing a screen sharing session with the remote device via the host device. All communications with the remote device associated with the screen sharing session are via the host device.
- the indication may be an alarm condition indicative of a problem and/or time data.
- the screen sharing session may be established by obtaining a session key made available by the host device and providing the session key to the host device.
- the invention is directed to method, performed by a remote device, of controlling a screen sharing session with a viewing device.
- the method includes receiving information from the viewing device and determining if the viewing device is permitted to enter into a screen sharing session with the remote device. If the viewing device is permitted to enter into a screen sharing session with the remote device, the screen sharing session between the remote device and the viewing device is controlled based on a state of the remote device.
- FIG. 1 is a block diagram of a network containing a viewing device, a remote device that shares its screen information with the viewing device, and a host device through which a screen sharing session is implemented;
- FIG. 2 shows flowcharts of a process for performing a screen sharing session on the network of FIG. 1.
- FIG. 1 shows a network 10 .
- Network 10 includes multiple devices 14 to 17 .
- Each of these devices may be connected to (and monitored or controlled by) a computer with a display screen.
- each of these devices may include an embedded controller (or a non-embedded associated controller) and a display screen.
- An embedded controller is a microprocessor or other circuitry, which monitors and/or controls the device and which displays graphics relating to the device on a corresponding display screen.
- Devices 14 to 17 may be any type of apparatus or system including, but not limited to, computers, home appliances, office equipment, medical devices, industrial tools, robots, blood analyzers, multifunction copiers, and air conditioning systems.
- remote device 14 is shown in detail.
- remote device 14 is a server (i.e., a computer), which includes a processor 18 , a memory 20 , a display screen 21 , and a user interface 22 , such as a mouse and a keyboard.
- the other devices 15 to 17 may have similar, or different, configurations.
- Devices 14 to 17 are connected to an internal network 24 , which may be a wired or wireless network, serial data line, or power line(s) (e.g., such as a home network configured using AC (Alternating Current) power lines as communications media).
- Internal network 24 is connected to an external network 25 , such as the Internet, via a network gateway 26 or the like.
- Gateway 26 may be used to resolve internal IP (Internet Protocol) addresses and to maintain a firewall between internal network 24 and external network 25 . The firewall prevents (or limits) unauthorized access to devices on internal network 24 , including, but not limited to, devices on external network 25 directly accessing devices 14 to 17 on the internal network.
- a router or modem 27 couples internal network 24 to external network 25 . It is noted that the network gateway may be omitted from network 10 , leaving router or modem 27 to perform the gateway functions.
- External network 25 runs TCP/IP (Transmission Control Protocol/Internet Protocol) or some other suitable protocol. Communications between devices 14 to 17 on internal network 24 and devices (described below) on external network 25 may be via HTTP (HyperText Transfer Protocol). Network connections throughout internal network 24 and external network 25 may be via Ethernet, telephone line, wireless links, or other transmission media.
- External network 25 contains a viewing device (client) 30 , which is a computer, or any other processing device, that includes a processor 31 , a memory 32 , a display screen 34 , and a user interface 35 (e.g., a mouse and a keyboard).
- viewing device 30 accesses graphics displayed on remote device 14 via a host device 37 on external network 25 .
- Viewing device 30 may be used to control remote device 14 to an extent. This feature is also described below.
- Host device 37 is a computer that runs TCP/IP and HTTP and/or other suitable protocols.
- Host device 37 includes a processor 39 and a memory 40 , which stores software 41 (i.e., machine-executable instructions) and database 42 .
- Host device 37 executes software 41 to communicate over external network 25 and to perform the functions described below in FIG. 2 for establishing and mediating a screen sharing session between a device (e.g., viewing device 30 ) on external network 25 and a device (e.g., remote device 14 ) on internal network 24 .
- a device e.g., viewing device 30
- a device e.g., remote device 14
- Software 41 may also host a Web page associated with the host device.
- the Web page (not shown) may be displayed on the computer of a user, such as viewing device 30 , who may use the Web page to access data to establish a screen sharing session with devices on internal network 24 .
- Database 42 stores and retrieves data in database 42 using application logic (not shown).
- Database 42 may be stored in memory 40 , which may be inside of, or external to, host device 37 .
- Database 42 stores data associated with devices 14 to 17 , including, e.g., rules for controlling a screen sharing session with each device on internal network 24 .
- the screen sharing rules may be different for different devices.
- Database 42 may contain rules specifying how much control a user at viewing device 30 may have based on a state of remote device 14 . For example, if host device 37 detects that remote device 14 is in a “dangerous” state, the rules may limit the amount that a user at viewing device 30 can control (e.g., change the configuration of) remote device 14 via screen sharing. Similarly, if, for example, a blood analyzer is currently operating, the rules may limit the amount that the user at viewing device 30 can change its configuration.
- Host device 37 may also contain rules governing who can screen share with remote device 14 , when screen sharing may take place and/or end, how much and what types of data (e.g., files) may be transmitted to/from remote device 14 , and so forth. These rules may be stored beforehand in host device 37 , e.g., by remote device 14 or by a third party who controls/owns host device 37 .
- the rules may be stored in remote device 14 .
- remote device 14 may control at least some screen sharing aspects. These aspects are noted above and may include who can screen share with remote device 14 , when screen sharing may take place/end, how much and what types of data may be transmitted to/from remote device 14 , and so forth. As above, the rules may be stored in remote device 14 beforehand, e.g., by a party controlling screen sharing.
- Memory 40 on host device 37 also may contain an audit log file 44 (or simply an audit log, which need not necessarily be a file).
- the audit log contains information relating to a screen sharing session hosted by the host device.
- the audit log may contain the identities (e.g., IP addresses) of two devices engaged in the screen sharing session, the time and date of the session, a record of information, including files, graphics, and user inputs, that were transmitted between the two device, a state of the remote device at the time of the session, and the like. Any information associated with the screen sharing session that is available to host device 37 from either remote device 14 or viewing device 30 may be stored in the audit log.
- FIG. 2 shows a process 50 for establishing and running a screen sharing session between remote device 14 and viewing device 30 via host device 37 .
- FIG. 2 is broken-down into three portions based on the functions performed by the various devices.
- remote device 14 performs the functions set forth in the portion labeled “Remote Device (Server)”
- host device 37 performs the functions set forth in the portion labeled “Host Device”
- viewing device 30 performs the functions set forth in portion labeled “Viewing Device (Client)”.
- FIG. 2 The breakdown shown in FIG. 2 is but one way of implementing the processes described herein. The invention, however, is not limited by the implementation shown in FIG. 2 or any other described herein.
- Processor 18 in remote device 14 executes software (machine-executable instructions) 12 stored in memory 20 to perform its portion of process 50 .
- Processor 31 in viewing device 30 executes software (machine-executable instructions) 33 stored in memory 32 to perform its portion of process 50 .
- Processor 39 in host device 37 executes software (i.e., machine-executable instructions) 41 stored in memory 40 to perform its portion of process 50 .
- remote device 14 detects ( 51 ) that a screen sharing condition has occurred.
- the screen sharing condition may be an alarm condition, such as an indication that there is a problem with the device.
- the screen sharing condition may be time data, in which case screen sharing may be on a time schedule.
- remote device 14 may permit screen sharing at specified time intervals, in which case the time data indicates that it is time to permit screen sharing.
- Other types of screen sharing conditions may also be used.
- Remote device 14 notifies ( 52 ) viewing device 30 that a screen sharing condition has occurred.
- Remote device 14 may notify viewing device 30 “offline”, meaning via, e.g., pager, electronic mail, telephone, or any other means of communication.
- a user such as a technician or the like, acts in response to this notification, as described below.
- Remote device 14 also notifies ( 52 ) host device 37 that the screen sharing condition has occurred.
- remote device 14 “pings” host device 37 periodically when the screen sharing condition occurs. The pinging may decrease in frequency over time, eventually stopping (timing out) if a screen sharing session is not established with remote device 14 . Alternatively, the pinging may continue until a session is established. Other types of notifications may be used in lieu of “pings”.
- remote device 14 notifies host device 37 only when a screen sharing condition has occurred. Remote device 14 thus does not “ping” host device 37 absent a screen sharing condition. Sending a notification only in response to a screen sharing condition provides an advantage over other host-based screen sharing systems, since it reduce the amount of communications to the host, and thus its amount of used bandwidth.
- process 50 may control remote device 14 to notify host device 37 in circumstances other than just the occurrence of a screen sharing condition.
- Remote device 14 also identifies itself to host device 37 .
- Remote device 14 may identify itself during the initial notification ( 52 ) or it may identify itself following a response to the notification from the host device.
- Remote device 14 may provide host device 37 with the remote device's IP address or some other identifier.
- viewing device 30 In response to receiving ( 53 ) the notification from remote device 14 , viewing device 30 (which is operated by a user at viewing device 30 ) contacts ( 54 ) host device 37 to initiate a screen sharing session with remote device 14 . Specifically, viewing device 30 identifies itself to host device 37 (e.g., via its IP address) and identifies remote device 14 as the device with which viewing device 30 would like to establish a screen sharing session.
- Host device 37 receives ( 55 ) the identification information from remote device 14 and viewing device 30 and uses that information to establish a screen sharing session between remote device 14 and viewing device 30 .
- host device 37 receives, from remote device 14 , the indication of the screen sharing condition in remote device 14 , the identity of remote device 14 , and the state of remote device 14 .
- the state of the device may include information such as whether the device is operating normally and whether the device is operating under dangerous conditions that may limit viewing device 30 's control.
- Host device 37 receives, from viewing device 30 , a request to establish a screen sharing session with remote device 14 and the identity of viewing device 30 . In other embodiments, different information may be provided.
- host device 37 determines ( 56 ) if a screen sharing session can be established between remote device 14 and viewing device 30 . Host device 37 does this by examining the rules stored in database 42 . For example, host device 37 determines if viewing device 30 is permitted to share remote device 14 's screen. If so, host device 37 determines the extent to which viewing device 30 can share remote device 14 's screen, e.g., if viewing device 30 is restricted to viewing certain types of data, if viewing device 30 is restricted to screen sharing at certain times, if viewing device 30 cannot control certain functions on remote device 14 because of the current state of remote device 14 , etc.
- host device 37 may notify each of them that screen sharing is not permitted under the current circumstances. Assuming that screen sharing is permitted between remote device 14 and viewing device 30 , host device 37 assigns ( 57 ) a session key to the screen sharing session.
- the session key may be an alphanumeric code associated with the session that enables both remote device 14 and viewing device 30 to connect to the same screen sharing session via host device 37 .
- Host device 37 makes the session key available ( 58 ) to both remote device 14 and viewing device 30 .
- Host device 37 may make the session key available by providing the session key directly to remote device 14 and viewing device 30 .
- the session key may be transmitted via HTTP commands, along with an indication that a screen sharing session is permissible; although such an indication is not necessary.
- the session key may be published on a Web site. (not shown), which may be password-protected.
- Viewing device 30 and remote device 14 may obtain the session key via the Web site by entering the appropriate password and appropriate information to identify the screen sharing session. Other methods of providing the session key may also be used.
- remote device 14 and viewing device 30 obtain ( 59 , 60 ) the session key, they provide ( 61 , 62 ) the session key to host device 37 .
- the session key may be provided using HTTP commands.
- Host device 37 receives ( 63 ) the session key from remote device 14 and viewing device 30 .
- Host device 37 authenticates the session keys, determines which devices are associated with the session keys, and establishes ( 64 ) a screen sharing session between those devices.
- Host device 37 may provide an indication to remote device 14 and viewing device 30 once the screen sharing session has been established.
- Host device 37 also determines if there are any restrictions put on the screen sharing session associated with the session key. If there are any such restrictions, host device 37 may advise remote device 14 and viewing device 30 of the restrictions.
- remote device 14 may be performing an operation or function that should not be interrupted by a remote device.
- host device 37 may query remote device 14 to determine whether the remote device is in a “safe” state, i.e., a state that permits remote control. If the remote device is not in a safe state, rules stored on the host device may cause the host to device to allow screen sharing, but only in a “viewing” mode. In such a mode, the viewing device may be able to view events occurring on the remote device, but cannot operate, or otherwise change configurations or settings of, the remote device. File transfers may also not be permitted in some embodiments. If the remote device is in a safe state, the host device will host a normal screen sharing session, in which the viewing device can change and/or manipulate the remote device.
- remote device 14 itself may prevent or limit screen sharing (rather than via host 37 ). For example, if the remote device is not in a safe state, rules stored on remote device 14 may prevent screen sharing or may allow screen sharing only in the “viewing” mode. In such cases, remote device may notify the host device and/or the viewing device, or take the action on its own.
- the remote device and the host device may both include screen sharing rules.
- both devices may have control over the amount and type of screen sharing depending upon the circumstances.
- the remote device and the host device may communicate and decide cooperatively whether screen sharing should take place under given circumstances.
- the state of a remote device may change during a screen sharing session.
- host device 37 may dynamically change, mid-session, the amount of control over the remote device that it provides to the viewing device.
- the state of the remote device may be obtained by querying the remote device (e.g., periodically) or by receiving an indication (without a query) from the remote device.
- the viewing device is notified of the change in state of the viewing device as well as its reduced control capabilities.
- remote device 14 performs the functions of changing, mid-session, the amount of control over the remote device that is provided to the viewing device and/or notifying the viewing device of the change in state as well as its reduced control capabilities.
- host device 37 may terminate a screen sharing session. Rules stored on the host device determine the circumstances under which a screen sharing session should be terminated.
- remote device 14 performs the functions of terminating the session and/or notifying the viewing device of the reason for termination.
- Communications between remote device 14 and host device 37 , and between viewing device 30 and host device 37 may be via HTTP POST commands (for uploading information) and HTTP GET commands (for retrieving information).
- viewing device 30 may provide information to host device 37 using an HTTP POST command.
- Remote device 14 may retrieve this information from host device 37 using an HTTP GET command.
- Communications may be transmitted using HTTP version 1.1 with chunked output, single GET commands with a persistent connection, and/or HTTP version 1.0.
- the communications may also be encrypted using any appropriate encryption algorithm.
- remote device 14 transmits ( 65 ) the initial contents of its display screen 21 to viewing device 30 via host device 37 .
- a window 80 (FIG. 1) may be displayed on the display screen 34 of viewing device 30 , which contains the contents (e.g., the GUI) of the display screen 21 associated with remote device 14 .
- a user can view the screen display of remote device 14 and manipulate its contents via user inputs, such as mouse and/or keyboard inputs. As noted above, manipulation may be allowed in some circumstances and not allowed in other circumstances.
- User inputs from viewing device 30 may be transmitted ( 66 ) to remote device 14 (via host device 37 ).
- Remote device 14 receives ( 67 ) these user inputs and processes them as if they were entered locally (i.e., by a user at remote device 14 ). As a result of these user inputs, remote device 14 may modify its GUI.
- Remote device 14 may transmit ( 68 ) these modifications to viewing device 30 (via host device 37 ). In one embodiment, remote device 14 transmits only those portions of the graphics that have changed as a result of the user inputs. Accordingly, less data needs to be transmitted. In other embodiments, all graphics may be transmitted.
- Viewing device 30 receives ( 69 ) the graphics and updates ( 70 ) its window 80 containing the display screen contents of remote device 14 .
- files and other documents may be exchanged (via host device 37 ) between remote device 14 and viewing device 30 during the screen sharing session.
- These files may be transferred using HTTP, FTP (file transfer protocol), or any other suitable protocol.
- File transfer capability including the types of files that may be transmitted, who may transfer files, etc. is controlled by host device 37 , in particular, by the rules stored in database 42 . In alternative embodiments, file transfer capability may be controlled by rules stored in the remote device.
- a screen sharing session may be terminated by either remote device 14 or viewing device 30 by notifying host device 37 .
- Host device 37 may generate a report during, or following, a screen sharing session. The report correlates the screen sharing session with actions, states, and/or devices associated with the screen sharing session.
- Host device 37 may also be programmed to perform load balancing among various other host devices. That is, if the traffic on host device 37 exceeds a predetermined level, host device may direct communications to/from remote device 14 and viewing device 30 to another host device (not shown). That other host device, which may have access to database 42 , may then perform the same screen sharing session functions as host device 37 with respect to remote device 14 and viewing device 30 . Host device 37 will direct all communications relating to a single screen sharing session to a single other host device. Directing the communications to a single other host reduces the need for communication among different host devices.
- Process 50 is not limited to use with the hardware/software configuration of FIGS. 1 and 2; it may find applicability in any computing or processing environment. Each portion of process 50 may be implemented in hardware (e.g., an ASIC ⁇ Application-Specific Integrated Circuit ⁇ and/or an FPGA ⁇ Field Programmable Gate Array ⁇ ), software, or a combination of hardware and software running on one or more of remote device 14 , host device 37 , viewing device 30 , and/or any number of other devices.
- hardware e.g., an ASIC ⁇ Application-Specific Integrated Circuit ⁇ and/or an FPGA ⁇ Field Programmable Gate Array ⁇
- software or a combination of hardware and software running on one or more of remote device 14 , host device 37 , viewing device 30 , and/or any number of other devices.
- Each portion of process 50 may be implemented using one or more computer programs executing on one or more programmable computers that each includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices.
- Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. Also, the programs can be implemented in assembly or machine language. The language may be a compiled or an interpreted language.
- Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer or other machine for configuring and operating the computer when the storage medium or device is read by the computer to perform process 50 .
- a storage medium or device e.g., CD-ROM, hard disk, or magnetic diskette
- Each portion of process 50 may also be implemented as a machine-readable storage medium, configured with a computer program, where, upon execution, instructions in the computer program cause the computer or other machine to operate in accordance with process 50 .
- the invention is not limited to use with the protocols and standards described above.
- software may use Java servlets, ASP (Active Server Pages), ISAPI (Internet Server Application Programming Interface), and/or .NET interfaces to effect communications.
- the commands used to transmit information between viewing device 30 , host device 37 , and remote device 14 are not limited to HTTP GET and POST commands. Any commands and/or requests for requesting and receiving data may be used.
- Host device 37 and viewing device 30 are depicted as different devices in FIG. 1. However, their functionality may be included on one device, two devices, or more than two devices. Similarly, the functionality of remote device 14 may be spread out over numerous devices. The invention is not limited to the block ordering shown in the flowchart of FIG. 2. Rather, blocks may be executed out of order or omitted in other embodiments.
- the host device may act as merely a conduit for communications between the remote device and the host device.
- Actual control over screen sharing, file transfers, and the like may be implemented in the viewing device and/or the remote device.
- the example described above, in which the screen sharing rules are stored in the remote device, is but one example of such an alternative embodiment.
- sockets on the viewing device and the remote device transmit communications to the host device which, in this case, operates much like a router.
- remote device 14 may receive, from viewing device 30 , a request to establish a screen sharing session with remote device 14 and the identity of viewing device 30 . In other embodiments, different information may be provided.
- remote device 14 determines if a screen sharing session can be established between remote device 14 and viewing device 30 .
- Remote device 14 does this based on its current state (e.g., if a screen sharing condition has occurred) and the rules stored on remote device. If screen sharing is permitted under the circumstances, host remote device determines the extent to which viewing device 30 can share remote device 14 's screen, e.g., if viewing device 30 is restricted to viewing certain types of data, if viewing device 30 is restricted to screen sharing at certain times, if viewing device 30 cannot access certain functions on remote device 14 because of the current state of remote device 14 , etc. The screen sharing session then proceeds as described above.
- Remote device can also change the capabilities of a screen sharing session dynamically, as described above. Also, if a screen sharing session cannot be established between remote device 14 and viewing device 30 , remote device 14 may notify the viewing device that screen sharing is not permitted under the current circumstances.
Abstract
Description
- This application claims priority to U.S. Provisional Application No. 60/392,448, which was filed on Jun. 27, 2002. The contents of U.S. Provisional Application No. 60/392,448 are hereby incorporated by reference into this application as if set forth herein in full.
- This invention relates generally to sharing screen information from one device with another device and, more particularly, to using a separate host device to mediate a screen sharing session between the two devices.
- Oftentimes the need exists to view the graphical user interface (GUI) of one device on another device. For example, if a problem arises on remote device, a technician at a viewing device may be able to address the problem by signing onto a computer and viewing the GUT of the device with the problem. This eliminates the need for the technician to travel to the problem site.
- Products currently exist for sharing a device's GUI with another device. In such products, a client (the viewing device) links to a server (the remote sharing device) either directly or via a modem. Once a link is established, the remote device provides its graphics to the viewing device, where the graphics can be viewed. This type of screen sharing is common on private local area networks (LANs). However, because the remote device must be addressed directly, this type of screen sharing is generally not usable over a public network, such as the Internet, particularly in cases where the remote device is located behind a firewall or other security system.
- In general, in one aspect, the invention is directed to a method, which includes receiving an indication of a screen sharing condition from a remote device, receiving data from a viewing device, and hosting a screen sharing session between the remote device and the viewing device. Capabilities associated with the screen sharing session are based on the screen sharing condition.
- Advantageously, a host device may be used to host the screen sharing session between the remote device and the viewing device. The host device may be located outside of a firewall or internal network on which the remote device resides, making the host device accessible to both the remote device and the viewing device. As such, use of the host device reduces the need to address the remote device directly to perform screen sharing. Screen sharing thus can be implemented over a public network, such as the Internet, and in cases where the remote device is located behind a firewall or other security system.
- Another advantage results from capabilities associated with the screen sharing session being based on the screen sharing condition. More specifically, the amount of control a viewing device has over a remote device in a screen sharing session may be dictated by conditions (e.g., screen sharing conditions) on the remote device.
- By way of example, if a blood analyzer having an associated computer (with display screen) is currently operating, operational conditions of the blood analyzer may limit the amount that a viewing device can change the configuration of the blood analyzer. In this circumstance, the viewing device may be limited, e.g., to viewing the display screen of the blood analyzer. Under more favorable conditions, the viewing device may reconfigure the blood analyzer via the blood analyzer's computer during a screen sharing session with the computer.
- The foregoing aspect of the invention may also include one or more of the following features.
- The indication of a screen sharing condition may be an indication of an alarm condition in the remote device. The alarm condition may indicate a problem with the remote device and/or may be timing data. The indication may be received as a series of pings output by the remote device. The pings may decrease in frequency over time.
- The data received from the viewing device may identify the viewing device and the remote device. Hosting the screen sharing session may include determining an extent to which the viewing device is permitted to share the screen of (e.g., control) the remote device based on one or more predetermined rules. The screen sharing condition may include a state of the remote device. Hosting the screen sharing session may include determining an extent to which the viewing device is permitted to share the screen of the remote device based on the state of the remote device.
- Hosting the screen sharing session may include transmitting information associated with the screen sharing session between the remote device and the viewing device. Hosting may also include transferring a file between the remote device and the viewing device.
- Information prior to (e.g., during set-up), and during, the screen sharing session may be transmitted using HTTP. The information may encrypted.
- Hosting the screen sharing session may include transmitting graphics changes between the remote device and the viewing device. The graphics changes may include only portions of graphics on the remote device that are changed.
- Hosting the screen sharing session may include storing, in an audit log, information relating to the screen sharing session. Hosting may also include making a session key available to the remote device and to the viewing device, the session key providing access to the screen sharing session, receiving session keys from both the remote device and the viewing device, and establishing the screen sharing session in response to receiving the session keys. The session keys may be made available by providing the session keys directly to the remote device and to the viewing device. The session keys may be made available by posting the session keys on a Web page.
- Hosting the screen sharing session may include changing capabilities associated with the screen sharing session dynamically in response to a change in the screen sharing condition. Changing the capabilities associated with the screen sharing session may include terminating the screen sharing session or reducing an amount of control over the remove device via the screen sharing session.
- Hosting the screen sharing session may include directing communications transmitted during the screen sharing session to one of multiple hosts. A report relating to the screen sharing session may be generated.
- In general, in another aspect, the invention is directed to a method, which includes outputting an indication to a host device that a screen sharing condition has occurred and establishing a screen sharing session via the host device. The screen sharing session includes receiving user inputs via the host device and providing graphics changes to the host device. This aspect may include one or more of the following features.
- The indication may be an alarm condition indicative of a problem and/or time data. The screen sharing session may be established by obtaining a session key made available by the host device and providing the session key to the host device. Information relating to the screen sharing session may be transmitted via the host device using HTTP.
- The user inputs may include mouse data and keyboard data and the graphics changes may include updates that occurred since transmitting a previous graphics change.
- In general, in another aspect, the invention is directed to a method, which includes receiving an indication from a remote device that a screen sharing condition has occurred and establishing a screen sharing session with the remote device via the host device. All communications with the remote device associated with the screen sharing session are via the host device.
- This aspect may include one or more of the following features. The indication may be an alarm condition indicative of a problem and/or time data. The screen sharing session may be established by obtaining a session key made available by the host device and providing the session key to the host device.
- In general, in another aspect, the invention is directed to method, performed by a remote device, of controlling a screen sharing session with a viewing device. The method includes receiving information from the viewing device and determining if the viewing device is permitted to enter into a screen sharing session with the remote device. If the viewing device is permitted to enter into a screen sharing session with the remote device, the screen sharing session between the remote device and the viewing device is controlled based on a state of the remote device.
- These and other advantages of the invention will become apparent from the following description, including the drawings and claims.
- FIG. 1 is a block diagram of a network containing a viewing device, a remote device that shares its screen information with the viewing device, and a host device through which a screen sharing session is implemented; and
- FIG. 2 shows flowcharts of a process for performing a screen sharing session on the network of FIG. 1.
- FIG. 1 shows a
network 10.Network 10 includesmultiple devices 14 to 17. Each of these devices may be connected to (and monitored or controlled by) a computer with a display screen. Alternatively, each of these devices may include an embedded controller (or a non-embedded associated controller) and a display screen. - An embedded controller is a microprocessor or other circuitry, which monitors and/or controls the device and which displays graphics relating to the device on a corresponding display screen.
Devices 14 to 17 may be any type of apparatus or system including, but not limited to, computers, home appliances, office equipment, medical devices, industrial tools, robots, blood analyzers, multifunction copiers, and air conditioning systems. - Device14 (hereinafter “
remote device 14”) is shown in detail. In this embodimentremote device 14 is a server (i.e., a computer), which includes a processor 18, amemory 20, adisplay screen 21, and auser interface 22, such as a mouse and a keyboard. Theother devices 15 to 17 may have similar, or different, configurations. -
Devices 14 to 17 are connected to aninternal network 24, which may be a wired or wireless network, serial data line, or power line(s) (e.g., such as a home network configured using AC (Alternating Current) power lines as communications media).Internal network 24 is connected to anexternal network 25, such as the Internet, via anetwork gateway 26 or the like.Gateway 26 may be used to resolve internal IP (Internet Protocol) addresses and to maintain a firewall betweeninternal network 24 andexternal network 25. The firewall prevents (or limits) unauthorized access to devices oninternal network 24, including, but not limited to, devices onexternal network 25 directly accessingdevices 14 to 17 on the internal network. - A router or
modem 27 couplesinternal network 24 toexternal network 25. It is noted that the network gateway may be omitted fromnetwork 10, leaving router ormodem 27 to perform the gateway functions.External network 25 runs TCP/IP (Transmission Control Protocol/Internet Protocol) or some other suitable protocol. Communications betweendevices 14 to 17 oninternal network 24 and devices (described below) onexternal network 25 may be via HTTP (HyperText Transfer Protocol). Network connections throughoutinternal network 24 andexternal network 25 may be via Ethernet, telephone line, wireless links, or other transmission media. -
External network 25 contains a viewing device (client) 30, which is a computer, or any other processing device, that includes aprocessor 31, amemory 32, adisplay screen 34, and a user interface 35 (e.g., a mouse and a keyboard). As described below,viewing device 30 accesses graphics displayed onremote device 14 via ahost device 37 onexternal network 25.Viewing device 30 may be used to controlremote device 14 to an extent. This feature is also described below. -
Host device 37 is a computer that runs TCP/IP and HTTP and/or other suitable protocols.Host device 37 includes aprocessor 39 and amemory 40, which stores software 41 (i.e., machine-executable instructions) anddatabase 42.Host device 37 executessoftware 41 to communicate overexternal network 25 and to perform the functions described below in FIG. 2 for establishing and mediating a screen sharing session between a device (e.g., viewing device 30) onexternal network 25 and a device (e.g., remote device 14) oninternal network 24. -
Software 41 may also host a Web page associated with the host device. The Web page (not shown) may be displayed on the computer of a user, such asviewing device 30, who may use the Web page to access data to establish a screen sharing session with devices oninternal network 24. -
Software 41 stores and retrieves data indatabase 42 using application logic (not shown).Database 42 may be stored inmemory 40, which may be inside of, or external to,host device 37.Database 42 stores data associated withdevices 14 to 17, including, e.g., rules for controlling a screen sharing session with each device oninternal network 24. The screen sharing rules may be different for different devices.Database 42 may contain rules specifying how much control a user atviewing device 30 may have based on a state ofremote device 14. For example, ifhost device 37 detects thatremote device 14 is in a “dangerous” state, the rules may limit the amount that a user atviewing device 30 can control (e.g., change the configuration of)remote device 14 via screen sharing. Similarly, if, for example, a blood analyzer is currently operating, the rules may limit the amount that the user atviewing device 30 can change its configuration. -
Host device 37 may also contain rules governing who can screen share withremote device 14, when screen sharing may take place and/or end, how much and what types of data (e.g., files) may be transmitted to/fromremote device 14, and so forth. These rules may be stored beforehand inhost device 37, e.g., byremote device 14 or by a third party who controls/ownshost device 37. - Rather than storing the rules in
host 37, the rules may be stored inremote device 14. In some embodiments,remote device 14 may control at least some screen sharing aspects. These aspects are noted above and may include who can screen share withremote device 14, when screen sharing may take place/end, how much and what types of data may be transmitted to/fromremote device 14, and so forth. As above, the rules may be stored inremote device 14 beforehand, e.g., by a party controlling screen sharing. -
Memory 40 onhost device 37 also may contain an audit log file 44 (or simply an audit log, which need not necessarily be a file). The audit log contains information relating to a screen sharing session hosted by the host device. For example, the audit log may contain the identities (e.g., IP addresses) of two devices engaged in the screen sharing session, the time and date of the session, a record of information, including files, graphics, and user inputs, that were transmitted between the two device, a state of the remote device at the time of the session, and the like. Any information associated with the screen sharing session that is available to hostdevice 37 from eitherremote device 14 orviewing device 30 may be stored in the audit log. - FIG. 2 shows a process50 for establishing and running a screen sharing session between
remote device 14 andviewing device 30 viahost device 37. FIG. 2 is broken-down into three portions based on the functions performed by the various devices. For example,remote device 14 performs the functions set forth in the portion labeled “Remote Device (Server)”;host device 37 performs the functions set forth in the portion labeled “Host Device”; andviewing device 30 performs the functions set forth in portion labeled “Viewing Device (Client)”. - The breakdown shown in FIG. 2 is but one way of implementing the processes described herein. The invention, however, is not limited by the implementation shown in FIG. 2 or any other described herein.
- Processor18 in
remote device 14 executes software (machine-executable instructions) 12 stored inmemory 20 to perform its portion of process 50.Processor 31 inviewing device 30 executes software (machine-executable instructions) 33 stored inmemory 32 to perform its portion of process 50.Processor 39 inhost device 37 executes software (i.e., machine-executable instructions) 41 stored inmemory 40 to perform its portion of process 50. - In process50,
remote device 14 detects (51) that a screen sharing condition has occurred. The screen sharing condition may be an alarm condition, such as an indication that there is a problem with the device. Alternatively, the screen sharing condition may be time data, in which case screen sharing may be on a time schedule. For example,remote device 14 may permit screen sharing at specified time intervals, in which case the time data indicates that it is time to permit screen sharing. Other types of screen sharing conditions may also be used. -
Remote device 14 notifies (52)viewing device 30 that a screen sharing condition has occurred.Remote device 14 may notifyviewing device 30 “offline”, meaning via, e.g., pager, electronic mail, telephone, or any other means of communication. A user, such as a technician or the like, acts in response to this notification, as described below. -
Remote device 14 also notifies (52)host device 37 that the screen sharing condition has occurred. In one embodiment,remote device 14 “pings”host device 37 periodically when the screen sharing condition occurs. The pinging may decrease in frequency over time, eventually stopping (timing out) if a screen sharing session is not established withremote device 14. Alternatively, the pinging may continue until a session is established. Other types of notifications may be used in lieu of “pings”. - In this embodiment,
remote device 14 notifieshost device 37 only when a screen sharing condition has occurred.Remote device 14 thus does not “ping”host device 37 absent a screen sharing condition. Sending a notification only in response to a screen sharing condition provides an advantage over other host-based screen sharing systems, since it reduce the amount of communications to the host, and thus its amount of used bandwidth. In alternative embodiments, process 50 may controlremote device 14 to notifyhost device 37 in circumstances other than just the occurrence of a screen sharing condition. -
Remote device 14 also identifies itself to hostdevice 37.Remote device 14 may identify itself during the initial notification (52) or it may identify itself following a response to the notification from the host device.Remote device 14 may providehost device 37 with the remote device's IP address or some other identifier. - In response to receiving (53) the notification from
remote device 14, viewing device 30 (which is operated by a user at viewing device 30) contacts (54)host device 37 to initiate a screen sharing session withremote device 14. Specifically,viewing device 30 identifies itself to host device 37 (e.g., via its IP address) and identifiesremote device 14 as the device with whichviewing device 30 would like to establish a screen sharing session. -
Host device 37 receives (55) the identification information fromremote device 14 andviewing device 30 and uses that information to establish a screen sharing session betweenremote device 14 andviewing device 30. In this embodiment,host device 37 receives, fromremote device 14, the indication of the screen sharing condition inremote device 14, the identity ofremote device 14, and the state ofremote device 14. The state of the device may include information such as whether the device is operating normally and whether the device is operating under dangerous conditions that may limitviewing device 30's control.Host device 37 receives, from viewingdevice 30, a request to establish a screen sharing session withremote device 14 and the identity ofviewing device 30. In other embodiments, different information may be provided. - Using the foregoing information,
host device 37 determines (56) if a screen sharing session can be established betweenremote device 14 andviewing device 30.Host device 37 does this by examining the rules stored indatabase 42. For example,host device 37 determines if viewingdevice 30 is permitted to shareremote device 14's screen. If so,host device 37 determines the extent to whichviewing device 30 can shareremote device 14's screen, e.g., if viewingdevice 30 is restricted to viewing certain types of data, if viewingdevice 30 is restricted to screen sharing at certain times, if viewingdevice 30 cannot control certain functions onremote device 14 because of the current state ofremote device 14, etc. - If a screen sharing session cannot be established between
remote device 14 andviewing device 30,host device 37 may notify each of them that screen sharing is not permitted under the current circumstances. Assuming that screen sharing is permitted betweenremote device 14 andviewing device 30,host device 37 assigns (57) a session key to the screen sharing session. The session key may be an alphanumeric code associated with the session that enables bothremote device 14 andviewing device 30 to connect to the same screen sharing session viahost device 37.Host device 37 makes the session key available (58) to bothremote device 14 andviewing device 30. -
Host device 37 may make the session key available by providing the session key directly toremote device 14 andviewing device 30. The session key may be transmitted via HTTP commands, along with an indication that a screen sharing session is permissible; although such an indication is not necessary. Alternatively, the session key may be published on a Web site. (not shown), which may be password-protected.Viewing device 30 andremote device 14 may obtain the session key via the Web site by entering the appropriate password and appropriate information to identify the screen sharing session. Other methods of providing the session key may also be used. - Once
remote device 14 andviewing device 30 obtain (59, 60) the session key, they provide (61, 62) the session key tohost device 37. The session key may be provided using HTTP commands.Host device 37 receives (63) the session key fromremote device 14 andviewing device 30.Host device 37 authenticates the session keys, determines which devices are associated with the session keys, and establishes (64) a screen sharing session between those devices.Host device 37 may provide an indication toremote device 14 andviewing device 30 once the screen sharing session has been established.Host device 37 also determines if there are any restrictions put on the screen sharing session associated with the session key. If there are any such restrictions,host device 37 may adviseremote device 14 andviewing device 30 of the restrictions. - By way of example,
remote device 14 may be performing an operation or function that should not be interrupted by a remote device. In this case,host device 37 may queryremote device 14 to determine whether the remote device is in a “safe” state, i.e., a state that permits remote control. If the remote device is not in a safe state, rules stored on the host device may cause the host to device to allow screen sharing, but only in a “viewing” mode. In such a mode, the viewing device may be able to view events occurring on the remote device, but cannot operate, or otherwise change configurations or settings of, the remote device. File transfers may also not be permitted in some embodiments. If the remote device is in a safe state, the host device will host a normal screen sharing session, in which the viewing device can change and/or manipulate the remote device. - In embodiments where the screen sharing rules are stored on
remote device 14,remote device 14 itself may prevent or limit screen sharing (rather than via host 37). For example, if the remote device is not in a safe state, rules stored onremote device 14 may prevent screen sharing or may allow screen sharing only in the “viewing” mode. In such cases, remote device may notify the host device and/or the viewing device, or take the action on its own. - In further alternative embodiments, the remote device and the host device may both include screen sharing rules. In these embodiments, both devices may have control over the amount and type of screen sharing depending upon the circumstances. The remote device and the host device may communicate and decide cooperatively whether screen sharing should take place under given circumstances.
- The state of a remote device may change during a screen sharing session. In this case,
host device 37 may dynamically change, mid-session, the amount of control over the remote device that it provides to the viewing device. The state of the remote device may be obtained by querying the remote device (e.g., periodically) or by receiving an indication (without a query) from the remote device. The viewing device is notified of the change in state of the viewing device as well as its reduced control capabilities. - In embodiments where the screen sharing rules are stored on
remote device 14,remote device 14 performs the functions of changing, mid-session, the amount of control over the remote device that is provided to the viewing device and/or notifying the viewing device of the change in state as well as its reduced control capabilities. - In some cases, it may be undesirable to permit screen sharing of the remote device. In such cases,
host device 37 may terminate a screen sharing session. Rules stored on the host device determine the circumstances under which a screen sharing session should be terminated. - In embodiments where the screen sharing rules are stored on
remote device 14,remote device 14 performs the functions of terminating the session and/or notifying the viewing device of the reason for termination. - Communications between
remote device 14 andhost device 37, and betweenviewing device 30 andhost device 37 may be via HTTP POST commands (for uploading information) and HTTP GET commands (for retrieving information). Thus, for example,viewing device 30 may provide information tohost device 37 using an HTTP POST command.Remote device 14 may retrieve this information fromhost device 37 using an HTTP GET command. Communications may be transmitted using HTTP version 1.1 with chunked output, single GET commands with a persistent connection, and/or HTTP version 1.0. The communications may also be encrypted using any appropriate encryption algorithm. - During the screen sharing session, as during setup, all communications between
remote device 14 andviewing device 30 go throughhost device 37. At the start of the screen sharing session,remote device 14 transmits (65) the initial contents of itsdisplay screen 21 toviewing device 30 viahost device 37. A window 80 (FIG. 1) may be displayed on thedisplay screen 34 ofviewing device 30, which contains the contents (e.g., the GUI) of thedisplay screen 21 associated withremote device 14. - At
viewing device 30, a user can view the screen display ofremote device 14 and manipulate its contents via user inputs, such as mouse and/or keyboard inputs. As noted above, manipulation may be allowed in some circumstances and not allowed in other circumstances. - User inputs from viewing
device 30 may be transmitted (66) to remote device 14 (via host device 37).Remote device 14 receives (67) these user inputs and processes them as if they were entered locally (i.e., by a user at remote device 14). As a result of these user inputs,remote device 14 may modify its GUI.Remote device 14 may transmit (68) these modifications to viewing device 30 (via host device 37). In one embodiment,remote device 14 transmits only those portions of the graphics that have changed as a result of the user inputs. Accordingly, less data needs to be transmitted. In other embodiments, all graphics may be transmitted.Viewing device 30 receives (69) the graphics and updates (70) itswindow 80 containing the display screen contents ofremote device 14. - In addition to graphics and user inputs, files and other documents may be exchanged (via host device37) between
remote device 14 andviewing device 30 during the screen sharing session. These files may be transferred using HTTP, FTP (file transfer protocol), or any other suitable protocol. File transfer capability, including the types of files that may be transmitted, who may transfer files, etc. is controlled byhost device 37, in particular, by the rules stored indatabase 42. In alternative embodiments, file transfer capability may be controlled by rules stored in the remote device. - A screen sharing session may be terminated by either
remote device 14 orviewing device 30 by notifyinghost device 37.Host device 37 may generate a report during, or following, a screen sharing session. The report correlates the screen sharing session with actions, states, and/or devices associated with the screen sharing session. -
Host device 37 may also be programmed to perform load balancing among various other host devices. That is, if the traffic onhost device 37 exceeds a predetermined level, host device may direct communications to/fromremote device 14 andviewing device 30 to another host device (not shown). That other host device, which may have access todatabase 42, may then perform the same screen sharing session functions ashost device 37 with respect toremote device 14 andviewing device 30.Host device 37 will direct all communications relating to a single screen sharing session to a single other host device. Directing the communications to a single other host reduces the need for communication among different host devices. - Process50 is not limited to use with the hardware/software configuration of FIGS. 1 and 2; it may find applicability in any computing or processing environment. Each portion of process 50 may be implemented in hardware (e.g., an ASIC {Application-Specific Integrated Circuit} and/or an FPGA {Field Programmable Gate Array}), software, or a combination of hardware and software running on one or more of
remote device 14,host device 37,viewing device 30, and/or any number of other devices. - Each portion of process50 may be implemented using one or more computer programs executing on one or more programmable computers that each includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices.
- Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. Also, the programs can be implemented in assembly or machine language. The language may be a compiled or an interpreted language.
- Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer or other machine for configuring and operating the computer when the storage medium or device is read by the computer to perform process50.
- Each portion of process50 may also be implemented as a machine-readable storage medium, configured with a computer program, where, upon execution, instructions in the computer program cause the computer or other machine to operate in accordance with process 50.
- The invention is not limited to use with the protocols and standards described above. For example, software may use Java servlets, ASP (Active Server Pages), ISAPI (Internet Server Application Programming Interface), and/or .NET interfaces to effect communications. The commands used to transmit information between
viewing device 30,host device 37, andremote device 14 are not limited to HTTP GET and POST commands. Any commands and/or requests for requesting and receiving data may be used. -
Host device 37 andviewing device 30 are depicted as different devices in FIG. 1. However, their functionality may be included on one device, two devices, or more than two devices. Similarly, the functionality ofremote device 14 may be spread out over numerous devices. The invention is not limited to the block ordering shown in the flowchart of FIG. 2. Rather, blocks may be executed out of order or omitted in other embodiments. - In other embodiments, the host device may act as merely a conduit for communications between the remote device and the host device. Actual control over screen sharing, file transfers, and the like may be implemented in the viewing device and/or the remote device. The example described above, in which the screen sharing rules are stored in the remote device, is but one example of such an alternative embodiment. In these embodiments, sockets on the viewing device and the remote device transmit communications to the host device which, in this case, operates much like a router.
- The functions of FIG. 2 attributed to the host device in process50 may be distributed between the remote device and the viewing device, as appropriate. For example,
remote device 14 may receive, from viewingdevice 30, a request to establish a screen sharing session withremote device 14 and the identity ofviewing device 30. In other embodiments, different information may be provided. - Using the foregoing information,
remote device 14 determines if a screen sharing session can be established betweenremote device 14 andviewing device 30.Remote device 14 does this based on its current state (e.g., if a screen sharing condition has occurred) and the rules stored on remote device. If screen sharing is permitted under the circumstances, host remote device determines the extent to whichviewing device 30 can shareremote device 14's screen, e.g., if viewingdevice 30 is restricted to viewing certain types of data, if viewingdevice 30 is restricted to screen sharing at certain times, if viewingdevice 30 cannot access certain functions onremote device 14 because of the current state ofremote device 14, etc. The screen sharing session then proceeds as described above. - Remote device can also change the capabilities of a screen sharing session dynamically, as described above. Also, if a screen sharing session cannot be established between
remote device 14 andviewing device 30,remote device 14 may notify the viewing device that screen sharing is not permitted under the current circumstances. - Other embodiments not described herein are also within the scope of the following claims.
Claims (102)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/609,009 US7046134B2 (en) | 2002-06-27 | 2003-06-27 | Screen sharing |
US11/434,625 US20060208871A1 (en) | 2003-06-27 | 2006-05-16 | Screen sharing |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US39244802P | 2002-06-27 | 2002-06-27 | |
US10/609,009 US7046134B2 (en) | 2002-06-27 | 2003-06-27 | Screen sharing |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/434,625 Continuation US20060208871A1 (en) | 2003-06-27 | 2006-05-16 | Screen sharing |
Publications (2)
Publication Number | Publication Date |
---|---|
US20040075619A1 true US20040075619A1 (en) | 2004-04-22 |
US7046134B2 US7046134B2 (en) | 2006-05-16 |
Family
ID=30000872
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/609,009 Expired - Lifetime US7046134B2 (en) | 2002-06-27 | 2003-06-27 | Screen sharing |
Country Status (3)
Country | Link |
---|---|
US (1) | US7046134B2 (en) |
AU (1) | AU2003247842A1 (en) |
WO (1) | WO2004003724A2 (en) |
Cited By (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040172449A1 (en) * | 1999-12-02 | 2004-09-02 | Lambertus Hesselink | VCR webification |
US20050138186A1 (en) * | 1999-12-02 | 2005-06-23 | Lambertus Hesselink | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US20050144195A1 (en) * | 1999-12-02 | 2005-06-30 | Lambertus Hesselink | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US20060259604A1 (en) * | 2005-04-15 | 2006-11-16 | Uri Kotchavi | Apparatus and method for managing a network of intelligent devices |
US20070055941A1 (en) * | 2005-09-08 | 2007-03-08 | Bhakta Dharmesh N | Method and apparatus to selectively display portions of a shared desktop in a collaborative environment |
US20070136686A1 (en) * | 2005-12-08 | 2007-06-14 | International Business Machines Corporation | Pop-up repelling frame for use in screen sharing |
US20070198845A1 (en) * | 2006-02-20 | 2007-08-23 | Hiroshi Morikawa | Communication control device, communication control method, and communication control system |
US20080016155A1 (en) * | 2006-07-11 | 2008-01-17 | Igor Khalatian | One-Click Universal Screen Sharing |
US20110010629A1 (en) * | 2009-07-09 | 2011-01-13 | Ibm Corporation | Selectively distributing updates of changing images to client devices |
US20110252366A1 (en) * | 2010-04-08 | 2011-10-13 | International Business Machines Corporation | Discriminating among resources to share |
US20120317500A1 (en) * | 2011-06-07 | 2012-12-13 | At&T Intellectual Property I, L.P. | System and method for data visualization and user collaboration |
US8341275B1 (en) | 1999-12-02 | 2012-12-25 | Western Digital Technologies, Inc. | Access and control system for network-enabled devices |
US20130198336A1 (en) * | 2012-01-26 | 2013-08-01 | Michal Kridlo | System and method for zero-footprint screen capture |
US20130301953A1 (en) * | 2012-05-12 | 2013-11-14 | Roland Wescott Montague | Rotatable Object System For Visual Communication And Analysis |
JP2014146229A (en) * | 2013-01-30 | 2014-08-14 | Sharp Corp | Screen sharing system and central device |
US20140270128A1 (en) * | 2011-11-08 | 2014-09-18 | Nec Corporation | Content display terminal selection system |
WO2015010111A1 (en) * | 2013-07-18 | 2015-01-22 | Robb Fujioka | Time and sleep control system and method |
US20150095419A1 (en) * | 2013-09-30 | 2015-04-02 | Qualcomm Incorporated | Method and apparatus for real-time sharing of multimedia content between wireless devices |
US20150149504A1 (en) * | 2013-05-06 | 2015-05-28 | Veeva Systems Inc. | System and method for co-browsing |
CN104917799A (en) * | 2014-03-13 | 2015-09-16 | 中国移动通信集团广西有限公司 | Resource sharing method, resource gateway, first node and second node |
US20150341570A1 (en) * | 2014-05-21 | 2015-11-26 | Mersive Technologies, Inc. | Intelligent shared display infrastructure and associated methods |
JP2016071637A (en) * | 2014-09-30 | 2016-05-09 | Kddi株式会社 | Screen sharing system and screen sharing method |
US9535651B2 (en) | 2009-12-18 | 2017-01-03 | Oracle International Corporation | Co-browsing systems and methods |
EP3217278A4 (en) * | 2014-11-05 | 2017-09-13 | Samsung Electronics Co., Ltd. | Method and device for controlling screen sharing among plurality of terminals, and recording medium |
US9874990B2 (en) | 2012-02-10 | 2018-01-23 | Oracle International Corporation | System and method of concurrent unobstructed co-browsing and chat messaging |
US9967399B2 (en) | 2014-12-19 | 2018-05-08 | Oracle International Corporation | Co-browsing preview of queued customer contacts |
US10038788B1 (en) | 2017-05-09 | 2018-07-31 | Oracle International Corporation | Self-learning adaptive routing system |
US10140382B2 (en) | 2013-05-06 | 2018-11-27 | Veeva Systems Inc. | System and method for controlling electronic communications |
US10445051B1 (en) * | 2014-03-27 | 2019-10-15 | Amazon Technologies, Inc. | Recording and replay of support sessions for computing devices |
US10671337B2 (en) | 2015-09-25 | 2020-06-02 | Oracle International Corporation | Automatic sizing of agent's screen for html co-browsing applications |
US10860279B2 (en) * | 2009-11-24 | 2020-12-08 | Clearslide, Inc. | Method and system for browser-based screen sharing |
US10902081B1 (en) | 2013-05-06 | 2021-01-26 | Veeva Systems Inc. | System and method for controlling electronic communications |
US10936274B2 (en) * | 2017-05-19 | 2021-03-02 | Vmware, Inc. | Selective screen sharing |
US11539785B2 (en) * | 2019-02-22 | 2022-12-27 | Microsoft Technology Licensing, Llc | Simultaneous cross-device application platform |
US20230051262A1 (en) * | 2021-08-10 | 2023-02-16 | Dell Products L.P. | Systems and methods to manage screen sharing of displayed local system windows |
US11836412B1 (en) | 2023-02-20 | 2023-12-05 | International Business Machines Corporation | Screen sharing recall |
Families Citing this family (76)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7117239B1 (en) | 2000-07-28 | 2006-10-03 | Axeda Corporation | Reporting the state of an apparatus to a remote computer |
US7185014B1 (en) | 2000-09-22 | 2007-02-27 | Axeda Corporation | Retrieving data from a server |
US8108543B2 (en) | 2000-09-22 | 2012-01-31 | Axeda Corporation | Retrieving data from a server |
US7254601B2 (en) | 2001-12-20 | 2007-08-07 | Questra Corporation | Method and apparatus for managing intelligent assets in a distributed environment |
US7178149B2 (en) | 2002-04-17 | 2007-02-13 | Axeda Corporation | XML scripting of soap commands |
US8635254B2 (en) | 2002-08-08 | 2014-01-21 | Axeda Corporation | Maintaining independent states for multiple web browser instances |
US7966418B2 (en) | 2003-02-21 | 2011-06-21 | Axeda Corporation | Establishing a virtual tunnel between two computer programs |
US20060208871A1 (en) * | 2003-06-27 | 2006-09-21 | Hansen James R | Screen sharing |
US7920528B2 (en) * | 2003-09-23 | 2011-04-05 | Broadcom Corporation | View sharing between in-range devices |
US7706777B2 (en) * | 2003-09-23 | 2010-04-27 | Broadcom Corporation | Secure user interface in a shared resource environment |
US7424736B2 (en) | 2004-03-10 | 2008-09-09 | Combrio, Inc. | Method for establishing directed circuits between parties with limited mutual trust |
US7183906B2 (en) * | 2004-03-19 | 2007-02-27 | Lockheed Martin Corporation | Threat scanning machine management system |
US20050251398A1 (en) * | 2004-05-04 | 2005-11-10 | Lockheed Martin Corporation | Threat scanning with pooled operators |
US7212113B2 (en) * | 2004-05-04 | 2007-05-01 | Lockheed Martin Corporation | Passenger and item tracking with system alerts |
US20050251397A1 (en) * | 2004-05-04 | 2005-11-10 | Lockheed Martin Corporation | Passenger and item tracking with predictive analysis |
US8116286B2 (en) | 2004-07-06 | 2012-02-14 | Rockstar Bidco, LP | Combined user agent for packet-based communication clients |
US20060218267A1 (en) * | 2005-03-24 | 2006-09-28 | Khan Irfan Z | Network, system, and application monitoring |
US20070061460A1 (en) * | 2005-03-24 | 2007-03-15 | Jumpnode Systems,Llc | Remote access |
JP4839010B2 (en) * | 2005-03-29 | 2011-12-14 | シスメックス株式会社 | Analysis system, data processing apparatus, and application program |
US7684421B2 (en) * | 2005-06-09 | 2010-03-23 | Lockheed Martin Corporation | Information routing in a distributed environment |
US20060282886A1 (en) * | 2005-06-09 | 2006-12-14 | Lockheed Martin Corporation | Service oriented security device management network |
US7533189B2 (en) * | 2005-06-21 | 2009-05-12 | Microsoft Corporation | Enabling a graphical window modification command to be applied to a remotely generated graphical window |
US20080060910A1 (en) * | 2006-09-08 | 2008-03-13 | Shawn Younkin | Passenger carry-on bagging system for security checkpoints |
US8370479B2 (en) | 2006-10-03 | 2013-02-05 | Axeda Acquisition Corporation | System and method for dynamically grouping devices based on present device conditions |
US7896741B2 (en) * | 2006-10-16 | 2011-03-01 | Igt | Progressive controller |
US7934993B2 (en) * | 2006-10-16 | 2011-05-03 | Igt | Secure progressive controller |
JP5063610B2 (en) * | 2006-10-27 | 2012-10-31 | 株式会社日立メディコ | Medical diagnostic imaging apparatus and remote maintenance system |
US8065397B2 (en) | 2006-12-26 | 2011-11-22 | Axeda Acquisition Corporation | Managing configurations of distributed devices |
US8478861B2 (en) | 2007-07-06 | 2013-07-02 | Axeda Acquisition Corp. | Managing distributed devices with limited connectivity |
US20090183087A1 (en) * | 2008-01-10 | 2009-07-16 | Binfire Corpoartion | Method and Apparatus for Real Time Image Transfer Between Two or More Computers |
US8959200B2 (en) * | 2008-07-01 | 2015-02-17 | Ortho-Clinical Diagnostics, Inc. | Event-based communication in a clinical diagnostic analyzer |
US20110066470A1 (en) * | 2009-09-14 | 2011-03-17 | Vikas Goyal | System and method for providing context based remote advisor capabilities to users of web applications |
JP2011154478A (en) * | 2010-01-26 | 2011-08-11 | Canon Inc | Screen sharing apparatus, control method thereof, program and screen sharing system |
US10837974B2 (en) | 2010-03-30 | 2020-11-17 | Sysmex Corporation | System, apparatus and method for auto-replenishment and monitoring of a medical instrument |
US8554282B2 (en) | 2010-10-01 | 2013-10-08 | American Megatrends, Inc. | Methods, devices and computer program products for presenting screen content |
US9465803B2 (en) | 2011-09-16 | 2016-10-11 | Nasdaq Technology Ab | Screen sharing presentation system |
US8909641B2 (en) | 2011-11-16 | 2014-12-09 | Ptc Inc. | Method for analyzing time series activity streams and devices thereof |
US9576046B2 (en) | 2011-11-16 | 2017-02-21 | Ptc Inc. | Methods for integrating semantic search, query, and analysis across heterogeneous data types and devices thereof |
US9098312B2 (en) | 2011-11-16 | 2015-08-04 | Ptc Inc. | Methods for dynamically generating an application interface for a modeled entity and devices thereof |
JP2013176828A (en) * | 2012-02-29 | 2013-09-09 | Ebara Corp | Remote monitoring system of polishing end point detection device |
US9699271B2 (en) | 2013-01-29 | 2017-07-04 | Blackberry Limited | Method and apparatus for suspending screen sharing during confidential data entry |
EP2973047A4 (en) | 2013-03-15 | 2016-11-02 | Ptc Inc | Methods for managing applications using semantic modeling and tagging and devices thereof |
WO2014201876A1 (en) * | 2013-06-17 | 2014-12-24 | 华为技术有限公司 | Screen sharing method and relevant device, and communications system |
US11631496B2 (en) | 2013-09-12 | 2023-04-18 | Johnson & Johnson Surgical Vision, Inc. | Computer-based operating room support system |
US11715560B2 (en) | 2013-09-12 | 2023-08-01 | Johnson & Johnson Surgical Vision, Inc. | Computer-based operating room support system |
US9483156B2 (en) | 2014-02-26 | 2016-11-01 | Apple Inc. | Selectively broadcasting audio and video content |
US9762637B2 (en) | 2014-03-21 | 2017-09-12 | Ptc Inc. | System and method of using binary dynamic rest messages |
US9350812B2 (en) | 2014-03-21 | 2016-05-24 | Ptc Inc. | System and method of message routing using name-based identifier in a distributed computing environment |
US9467533B2 (en) | 2014-03-21 | 2016-10-11 | Ptc Inc. | System and method for developing real-time web-service objects |
US10313410B2 (en) | 2014-03-21 | 2019-06-04 | Ptc Inc. | Systems and methods using binary dynamic rest messages |
WO2015143416A1 (en) | 2014-03-21 | 2015-09-24 | Ptc Inc. | Systems and methods for developing and using real-time data applications |
US10025942B2 (en) | 2014-03-21 | 2018-07-17 | Ptc Inc. | System and method of establishing permission for multi-tenancy storage using organization matrices |
US9462085B2 (en) | 2014-03-21 | 2016-10-04 | Ptc Inc. | Chunk-based communication of binary dynamic rest messages |
US9560170B2 (en) | 2014-03-21 | 2017-01-31 | Ptc Inc. | System and method of abstracting communication protocol using self-describing messages |
US9350791B2 (en) | 2014-03-21 | 2016-05-24 | Ptc Inc. | System and method of injecting states into message routing in a distributed computing environment |
US9961058B2 (en) | 2014-03-21 | 2018-05-01 | Ptc Inc. | System and method of message routing via connection servers in a distributed computing environment |
WO2015171228A1 (en) * | 2014-05-05 | 2015-11-12 | Usablenet Inc. | Methods for facilitating a remote interface and devices thereof |
JP6217557B2 (en) * | 2014-07-31 | 2017-10-25 | 京セラドキュメントソリューションズ株式会社 | Display input device and display input system including the same |
US10291597B2 (en) | 2014-08-14 | 2019-05-14 | Cisco Technology, Inc. | Sharing resources across multiple devices in online meetings |
KR102294754B1 (en) | 2014-10-21 | 2021-08-27 | 삼성전자 주식회사 | Method for splitting a screen and an electronic device implementing the same |
US10116748B2 (en) | 2014-11-20 | 2018-10-30 | Microsoft Technology Licensing, Llc | Vehicle-based multi-modal interface |
US10542126B2 (en) | 2014-12-22 | 2020-01-21 | Cisco Technology, Inc. | Offline virtual participation in an online conference meeting |
US10073599B2 (en) | 2015-01-07 | 2018-09-11 | Microsoft Technology Licensing, Llc | Automatic home screen determination based on display device |
US10440757B2 (en) * | 2015-02-17 | 2019-10-08 | Google Llc | Second-screen control automatic pairing using push notifications |
US9948786B2 (en) | 2015-04-17 | 2018-04-17 | Cisco Technology, Inc. | Handling conferences using highly-distributed agents |
US9497412B1 (en) | 2015-07-27 | 2016-11-15 | Cisco Technology, Inc. | Video conference audio/video verification |
US11233758B2 (en) | 2015-11-23 | 2022-01-25 | Verizon Patent And Licensing Inc. | Selective screen sharing |
US10592867B2 (en) | 2016-11-11 | 2020-03-17 | Cisco Technology, Inc. | In-meeting graphical user interface display using calendar information and system |
US10516707B2 (en) | 2016-12-15 | 2019-12-24 | Cisco Technology, Inc. | Initiating a conferencing meeting using a conference room device |
US10440073B2 (en) | 2017-04-11 | 2019-10-08 | Cisco Technology, Inc. | User interface for proximity based teleconference transfer |
US10375125B2 (en) | 2017-04-27 | 2019-08-06 | Cisco Technology, Inc. | Automatically joining devices to a video conference |
US10375474B2 (en) | 2017-06-12 | 2019-08-06 | Cisco Technology, Inc. | Hybrid horn microphone |
US10477148B2 (en) | 2017-06-23 | 2019-11-12 | Cisco Technology, Inc. | Speaker anticipation |
US10516709B2 (en) | 2017-06-29 | 2019-12-24 | Cisco Technology, Inc. | Files automatically shared at conference initiation |
US10706391B2 (en) | 2017-07-13 | 2020-07-07 | Cisco Technology, Inc. | Protecting scheduled meeting in physical room |
US10091348B1 (en) | 2017-07-25 | 2018-10-02 | Cisco Technology, Inc. | Predictive model for voice/video over IP calls |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5583993A (en) * | 1994-01-31 | 1996-12-10 | Apple Computer, Inc. | Method and apparatus for synchronously sharing data among computer |
US5727155A (en) * | 1994-09-09 | 1998-03-10 | Intel Corporation | Method and apparatus for dynamically controlling a remote system's access to shared applications on a host system |
US5758110A (en) * | 1994-06-17 | 1998-05-26 | Intel Corporation | Apparatus and method for application sharing in a graphic user interface |
US5933597A (en) * | 1996-04-04 | 1999-08-03 | Vtel Corporation | Method and system for sharing objects between local and remote terminals |
US5970149A (en) * | 1996-11-19 | 1999-10-19 | Johnson; R. Brent | Combined remote access and security system |
US6029191A (en) * | 1997-03-31 | 2000-02-22 | Nec Corporation | Application sharing system which can dynamically change an operating condition of an application program of each terminal from a sole-mode to a share-mode and vice versa |
US6057856A (en) * | 1996-09-30 | 2000-05-02 | Sony Corporation | 3D virtual reality multi-user interaction with superimposed positional information display for each user |
US6185602B1 (en) * | 1998-06-29 | 2001-02-06 | Sony Corporation | Multi-user interaction of multimedia communication |
US20020064138A1 (en) * | 2000-07-12 | 2002-05-30 | Tsuyoshi Saito | Semiconductor manufacturing apparatus, remote control system therefor, and remote operation device |
US6570590B1 (en) * | 1999-03-02 | 2003-05-27 | Microsoft Corporation | Application sharing in a frame |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002015026A1 (en) * | 2000-08-10 | 2002-02-21 | Frank Morrison | Method for screen image sharing |
-
2003
- 2003-06-27 AU AU2003247842A patent/AU2003247842A1/en not_active Abandoned
- 2003-06-27 WO PCT/US2003/020581 patent/WO2004003724A2/en not_active Application Discontinuation
- 2003-06-27 US US10/609,009 patent/US7046134B2/en not_active Expired - Lifetime
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5583993A (en) * | 1994-01-31 | 1996-12-10 | Apple Computer, Inc. | Method and apparatus for synchronously sharing data among computer |
US5758110A (en) * | 1994-06-17 | 1998-05-26 | Intel Corporation | Apparatus and method for application sharing in a graphic user interface |
US6329984B1 (en) * | 1994-06-17 | 2001-12-11 | Intel Corporation | User input routing with remote control application sharing |
US5727155A (en) * | 1994-09-09 | 1998-03-10 | Intel Corporation | Method and apparatus for dynamically controlling a remote system's access to shared applications on a host system |
US5933597A (en) * | 1996-04-04 | 1999-08-03 | Vtel Corporation | Method and system for sharing objects between local and remote terminals |
US6057856A (en) * | 1996-09-30 | 2000-05-02 | Sony Corporation | 3D virtual reality multi-user interaction with superimposed positional information display for each user |
US5970149A (en) * | 1996-11-19 | 1999-10-19 | Johnson; R. Brent | Combined remote access and security system |
US6029191A (en) * | 1997-03-31 | 2000-02-22 | Nec Corporation | Application sharing system which can dynamically change an operating condition of an application program of each terminal from a sole-mode to a share-mode and vice versa |
US6185602B1 (en) * | 1998-06-29 | 2001-02-06 | Sony Corporation | Multi-user interaction of multimedia communication |
US6570590B1 (en) * | 1999-03-02 | 2003-05-27 | Microsoft Corporation | Application sharing in a frame |
US20020064138A1 (en) * | 2000-07-12 | 2002-05-30 | Tsuyoshi Saito | Semiconductor manufacturing apparatus, remote control system therefor, and remote operation device |
Cited By (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8793374B2 (en) * | 1999-12-02 | 2014-07-29 | Western Digital Technologies, Inc. | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US20050138186A1 (en) * | 1999-12-02 | 2005-06-23 | Lambertus Hesselink | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US20050144195A1 (en) * | 1999-12-02 | 2005-06-30 | Lambertus Hesselink | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US8341275B1 (en) | 1999-12-02 | 2012-12-25 | Western Digital Technologies, Inc. | Access and control system for network-enabled devices |
US8352567B2 (en) | 1999-12-02 | 2013-01-08 | Western Digital Technologies, Inc. | VCR webification |
US8688797B2 (en) | 1999-12-02 | 2014-04-01 | Western Digital Technologies, Inc. | Managed peer-to-peer applications, systems and methods for distributed data access and storage |
US9807147B1 (en) | 1999-12-02 | 2017-10-31 | Western Digital Technologies, Inc. | Program recording webification |
US20040172449A1 (en) * | 1999-12-02 | 2004-09-02 | Lambertus Hesselink | VCR webification |
US9071574B1 (en) | 1999-12-02 | 2015-06-30 | Western Digital Technologies, Inc. | Access and control system for network-enabled devices |
US10382526B2 (en) | 1999-12-02 | 2019-08-13 | Western Digital Technologies, Inc. | Program recording webification |
US20060259604A1 (en) * | 2005-04-15 | 2006-11-16 | Uri Kotchavi | Apparatus and method for managing a network of intelligent devices |
US9032091B2 (en) | 2005-04-15 | 2015-05-12 | Esprida Corporation | Apparatus and method for managing a network of intelligent devices |
US20070055941A1 (en) * | 2005-09-08 | 2007-03-08 | Bhakta Dharmesh N | Method and apparatus to selectively display portions of a shared desktop in a collaborative environment |
US20070136686A1 (en) * | 2005-12-08 | 2007-06-14 | International Business Machines Corporation | Pop-up repelling frame for use in screen sharing |
US8146002B2 (en) | 2005-12-08 | 2012-03-27 | International Business Machines Corporation | Screen sharing session with selective pop-ups |
US20110191440A1 (en) * | 2006-02-20 | 2011-08-04 | Ricoh Company, Ltd. | Communication control device, communication control method, and communication control system |
US20070198845A1 (en) * | 2006-02-20 | 2007-08-23 | Hiroshi Morikawa | Communication control device, communication control method, and communication control system |
US8527886B2 (en) | 2006-02-20 | 2013-09-03 | Ricoh Company, Ltd. | Communication control device, communication control method, and communication control system |
US7913171B2 (en) * | 2006-02-20 | 2011-03-22 | Ricoh Company, Ltd. | Communication control device, communication control method, and communication control system |
US7933955B2 (en) | 2006-07-11 | 2011-04-26 | Igor Khalatian | One-click universal screen sharing |
US20080016155A1 (en) * | 2006-07-11 | 2008-01-17 | Igor Khalatian | One-Click Universal Screen Sharing |
US20110010629A1 (en) * | 2009-07-09 | 2011-01-13 | Ibm Corporation | Selectively distributing updates of changing images to client devices |
US10860279B2 (en) * | 2009-11-24 | 2020-12-08 | Clearslide, Inc. | Method and system for browser-based screen sharing |
US9535651B2 (en) | 2009-12-18 | 2017-01-03 | Oracle International Corporation | Co-browsing systems and methods |
US8549413B2 (en) * | 2010-04-08 | 2013-10-01 | International Business Machines Corporation | Discriminating among resources to share |
US20110252366A1 (en) * | 2010-04-08 | 2011-10-13 | International Business Machines Corporation | Discriminating among resources to share |
US20120317500A1 (en) * | 2011-06-07 | 2012-12-13 | At&T Intellectual Property I, L.P. | System and method for data visualization and user collaboration |
US20140270128A1 (en) * | 2011-11-08 | 2014-09-18 | Nec Corporation | Content display terminal selection system |
US20130198336A1 (en) * | 2012-01-26 | 2013-08-01 | Michal Kridlo | System and method for zero-footprint screen capture |
US9215266B2 (en) * | 2012-01-26 | 2015-12-15 | Zoom International S.R.O. | System and method for zero-footprint screen capture |
US9874990B2 (en) | 2012-02-10 | 2018-01-23 | Oracle International Corporation | System and method of concurrent unobstructed co-browsing and chat messaging |
US20130301953A1 (en) * | 2012-05-12 | 2013-11-14 | Roland Wescott Montague | Rotatable Object System For Visual Communication And Analysis |
US9201561B2 (en) * | 2012-05-12 | 2015-12-01 | Roland Wescott Montague | Rotatable object system for visual communication and analysis |
JP2014146229A (en) * | 2013-01-30 | 2014-08-14 | Sharp Corp | Screen sharing system and central device |
US10902081B1 (en) | 2013-05-06 | 2021-01-26 | Veeva Systems Inc. | System and method for controlling electronic communications |
US11526573B1 (en) | 2013-05-06 | 2022-12-13 | Veeva Systems Inc. | System and method for controlling electronic communications |
US20150149504A1 (en) * | 2013-05-06 | 2015-05-28 | Veeva Systems Inc. | System and method for co-browsing |
US10831851B2 (en) * | 2013-05-06 | 2020-11-10 | Veeva Systems Inc. | System and method for co-browsing |
US10789324B2 (en) | 2013-05-06 | 2020-09-29 | Veeva Systems Inc. | System and method for controlling electronic communications |
US10140382B2 (en) | 2013-05-06 | 2018-11-27 | Veeva Systems Inc. | System and method for controlling electronic communications |
US10169480B2 (en) | 2013-05-06 | 2019-01-01 | Veeva Systems Inc. | System and method for controlling electronic communications |
WO2015010111A1 (en) * | 2013-07-18 | 2015-01-22 | Robb Fujioka | Time and sleep control system and method |
US9226137B2 (en) * | 2013-09-30 | 2015-12-29 | Qualcomm Incorporated | Method and apparatus for real-time sharing of multimedia content between wireless devices |
US20150095419A1 (en) * | 2013-09-30 | 2015-04-02 | Qualcomm Incorporated | Method and apparatus for real-time sharing of multimedia content between wireless devices |
CN104917799A (en) * | 2014-03-13 | 2015-09-16 | 中国移动通信集团广西有限公司 | Resource sharing method, resource gateway, first node and second node |
US10445051B1 (en) * | 2014-03-27 | 2019-10-15 | Amazon Technologies, Inc. | Recording and replay of support sessions for computing devices |
US20150341570A1 (en) * | 2014-05-21 | 2015-11-26 | Mersive Technologies, Inc. | Intelligent shared display infrastructure and associated methods |
US10965883B2 (en) * | 2014-05-21 | 2021-03-30 | Mersive Technologies, Inc. | Intelligent shared display infrastructure and associated methods |
JP2016071637A (en) * | 2014-09-30 | 2016-05-09 | Kddi株式会社 | Screen sharing system and screen sharing method |
US10671336B2 (en) | 2014-11-05 | 2020-06-02 | Samsung Electronics Co., Ltd. | Method and device for controlling screen sharing among plurality of terminals, and recording medium |
EP3217278A4 (en) * | 2014-11-05 | 2017-09-13 | Samsung Electronics Co., Ltd. | Method and device for controlling screen sharing among plurality of terminals, and recording medium |
US9967399B2 (en) | 2014-12-19 | 2018-05-08 | Oracle International Corporation | Co-browsing preview of queued customer contacts |
US10671337B2 (en) | 2015-09-25 | 2020-06-02 | Oracle International Corporation | Automatic sizing of agent's screen for html co-browsing applications |
US10038788B1 (en) | 2017-05-09 | 2018-07-31 | Oracle International Corporation | Self-learning adaptive routing system |
US10936274B2 (en) * | 2017-05-19 | 2021-03-02 | Vmware, Inc. | Selective screen sharing |
US20210173610A1 (en) * | 2017-05-19 | 2021-06-10 | Vmware, Inc. | Selective screen sharing |
US11593055B2 (en) * | 2017-05-19 | 2023-02-28 | Vmware, Inc. | Selective screen sharing |
US11539785B2 (en) * | 2019-02-22 | 2022-12-27 | Microsoft Technology Licensing, Llc | Simultaneous cross-device application platform |
US20230051262A1 (en) * | 2021-08-10 | 2023-02-16 | Dell Products L.P. | Systems and methods to manage screen sharing of displayed local system windows |
US11797320B2 (en) * | 2021-08-10 | 2023-10-24 | Dell Products L.P. | Systems and methods to manage screen sharing of displayed local system windows |
US11836412B1 (en) | 2023-02-20 | 2023-12-05 | International Business Machines Corporation | Screen sharing recall |
Also Published As
Publication number | Publication date |
---|---|
AU2003247842A1 (en) | 2004-01-19 |
US7046134B2 (en) | 2006-05-16 |
AU2003247842A8 (en) | 2004-01-19 |
WO2004003724A2 (en) | 2004-01-08 |
WO2004003724A3 (en) | 2004-04-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7046134B2 (en) | Screen sharing | |
US20060208871A1 (en) | Screen sharing | |
US10652745B2 (en) | System and method for filtering access points presented to a user and locking onto an access point | |
US8332464B2 (en) | System and method for remote network access | |
EP3155761B1 (en) | Systems and methods for secure communication over a network using a linking address | |
EP1454241B1 (en) | Method of secure transfer of data between firewall-protected devices | |
US7788404B2 (en) | Access and control system for network-enabled devices | |
US8200818B2 (en) | System providing internet access management with router-based policy enforcement | |
WO2007032852A1 (en) | Providing consistent application aware firewall traversal | |
WO2008147475A2 (en) | Providing a generic gateway for accessing protected resources | |
US20080127322A1 (en) | Solicited remote control in an interactive management system | |
US9325685B2 (en) | Authentication switch and network system | |
WO2008063360A2 (en) | Remote access | |
JP4492248B2 (en) | Network system, internal server, terminal device, program, and packet relay method | |
WO2005060202A1 (en) | Method and system for analysing and filtering https traffic in corporate networks | |
CN101399838A (en) | Method, apparatus and system for processing packet | |
US7840663B1 (en) | Desktop security in peer-to-peer networks | |
JP4429059B2 (en) | Communication control method and program, communication control system, and communication control related apparatus | |
WO2023020606A1 (en) | Method, system and apparatus for hiding source station, and device and storage medium | |
JP4972646B2 (en) | Providing consistent application-compatible firewall traversal | |
US20030204586A1 (en) | Intelligent data replicator | |
Cisco | Configuring the Device-Specific Settings of Network Objects | |
Cisco | Configuring the Device-Specific Settings of Network Objects | |
CN106453336B (en) | Method for internal network to actively provide external network host calling service | |
JP3893055B2 (en) | Network security system and security method therefor |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC., MASSACHUSET Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HANSEN, JAMES R.;REEL/FRAME:014745/0617 Effective date: 20031110 |
|
AS | Assignment |
Owner name: JMI EQUITY FUND V, L.P.,MARYLAND Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846 Effective date: 20050708 Owner name: JMI EQUITY FUND V (AI), L.P.,MARYLAND Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846 Effective date: 20050708 Owner name: JMI EQUITY FUND V (AI), L.P., MARYLAND Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846 Effective date: 20050708 Owner name: JMI EQUITY FUND V, L.P., MARYLAND Free format text: GRANT OF SECURITY INTEREST IN PATENTS AND TRADEMARKS;ASSIGNORS:AXEDA SYSTEMS, INC.;AXEDA SYSTEMS OPERATING COMPANY, INC.;AXEDA IP, INC.;REEL/FRAME:016274/0846 Effective date: 20050708 |
|
AS | Assignment |
Owner name: LAURUS MASTER FUND, LTD.,NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016551/0813 Effective date: 20050831 Owner name: LAURUS MASTER FUND, LTD., NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016551/0813 Effective date: 20050831 |
|
AS | Assignment |
Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC.,MASSACHUSETT Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043 Effective date: 20051202 Owner name: AXEDA IP, INC.,MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043 Effective date: 20051202 Owner name: AXEDA SYSTEMS INC.,MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043 Effective date: 20051202 Owner name: AXEDA SYSTEMS INC., MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043 Effective date: 20051202 Owner name: AXEDA SYSTEMS OPERATING COMPANY, INC., MASSACHUSET Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043 Effective date: 20051202 Owner name: AXEDA IP, INC., MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN TRADEMARKS AND PATENTS;ASSIGNOR:LAURUS MATER FUND, LTD.;REEL/FRAME:016871/0043 Effective date: 20051202 |
|
AS | Assignment |
Owner name: AXEDA CORPORATION,MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016875/0827 Effective date: 20051202 Owner name: AXEDA CORPORATION, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AXEDA SYSTEMS OPERATING COMPANY, INC.;REEL/FRAME:016875/0827 Effective date: 20051202 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK,CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:018420/0790 Effective date: 20061011 Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:018420/0790 Effective date: 20061011 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: AXEDA CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:028558/0744 Effective date: 20120713 |
|
AS | Assignment |
Owner name: AXEDA CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MMV CAPITAL PARTNERS INC.;REEL/FRAME:028563/0446 Effective date: 20120713 |
|
AS | Assignment |
Owner name: COMERICA BANK, MICHIGAN Free format text: SECURITY AGREEMENT;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:028629/0538 Effective date: 20120713 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: AXEDA CORPORATION, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:COMERICA BANK;REEL/FRAME:033608/0704 Effective date: 20140822 |
|
AS | Assignment |
Owner name: PTC INC., MASSACHUSETTS Free format text: MERGER;ASSIGNOR:AXEDA CORPORATION;REEL/FRAME:036480/0407 Effective date: 20150309 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNOR:PTC INC.;REEL/FRAME:037046/0930 Effective date: 20151104 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY INTEREST;ASSIGNOR:PTC INC.;REEL/FRAME:037046/0930 Effective date: 20151104 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553) Year of fee payment: 12 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNOR:PTC INC.;REEL/FRAME:047480/0888 Effective date: 20180913 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY INTEREST;ASSIGNOR:PTC INC.;REEL/FRAME:047480/0888 Effective date: 20180913 |