JP2004005396A - Sbc collaboration system and proxy server for realizing the sbc collaboration - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To conduct collaborative operation which makes use of optional applications in an SBC server, among a plurality of SBC clients using a conventional SBC middleware. <P>SOLUTION: A proxy server, which is inserted between the SBC server equipped with the SBC middleware capable of introducing an optional application and a plurality of SBC clients, who are connected with the SBC server via a network and remotely operate the application, is provided with an operation right control part giving an operation authority which allows a first SBC client to execute the application, an operation information relay part which receives first inputting operation information to execute the application from the first SBC client and forwards the first input operation information thus received to the SBC server to execute the application and an execution screen transmitting part, which receives the execution screen of the application from the SBC server and transmits the execution screen to a plurality of SBC clients. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to server-based computing (SBC) collaboration technology, and more particularly, to a centralized centralized server that includes a proxy server that enables a plurality of remote users to share an application screen running on an SBC server and perform cooperative work. Type of SBC collaboration technology.
[0002]
[Prior art]
In recent years, a system has been developed by so-called SBC (server-based computing) technology that allows a user to remotely use an arbitrary application running on an SBC server in a network from an SBC browser of a single SBC client connected to the network. ing.
[0003]
In the SBC system, a high-load application is executed not on the client terminal but on the server, and only the execution screen is transmitted to the client. The user can use the application in the server as if the user installed the application on his terminal. The relationship between the user and the server is basically one-to-one, and each user independently uses the application in the server. Since the client terminal only receives the execution screen corresponding to the input operation from the server, it becomes possible to execute a complicated application even from a low-performance terminal such as a PDA.
[0004]
FIG. 1 is a network configuration diagram for explaining an outline of an SBC system currently used. The current SBC system α includes an SBC server 3 having an SBC middleware 2 in which an arbitrary application can be installed, and an SBC client 106 capable of accessing the SBC server 3 via a network 4. The SBC client 106 includes an SBC browser 105, and remotely uses the application 1 on the SBC middleware 2 from the SBC browser 105 via the network 4.
[0005]
When the user (not shown) of the SBC client 106 uses the application 1 on the SBC server 3 remotely, an input operation is performed using a mouse, a keyboard, a tablet, a joystick, or any other input device (not shown). The SBC browser 105 transmits the input operation information by the user to the SBC middleware 2 running on the SBC server via the network 4 (ST1).
[0006]
The SBC middleware 2 transfers the input operation information received from the SBC browser 105 via the network 4 to the application 1 running on the SBC middleware 2 (ST2). The application 1 executes a process based on the input operation information of the user, and supplies screen update information as an execution result to the SBC middleware 2 (ST3). The SBC middleware 2 transfers the screen update information received from the application 1 to the SBC client 106 via the network, and displays the contents of the screen update information on the screen of the SBC browser 105 (ST4).
[0007]
By repeating such an operation, the user can use the application 1 on the SBC server 3 like an application installed in the SBC client 106.
[0008]
The application 1 on the SBC server 3 is an application that can run on an OS (operating system) corresponding to the SBC middleware 2, for example, editor software, desktop publishing (DTP) software, CAD (computer aided). Basically, almost any application such as design software or game software can be operated.
[0009]
As the SBC middleware 2, for example, MetaFrame (registered trademark of Citrix), VNC (Virtual Network Computing; AT & T), Tarantella (registered trademark of SCO), GO-Global (registered trademark of GraphOn) and the like are applied. be able to.
[0010]
By the way, the SBC middleware 2 in the current SBC system α is based on the premise that each user uses the application 1 on the SBC server 3 alone. Therefore, the screen of the application 1 running on the SBC server 3 is displayed on the SBC browsers 105 of the plurality of SBC clients 106, and the user can use the application 1 mutually or collaborate in real time. It is not easy to realize.
[0011]
On the other hand, there is known a technique in which an application usable on the web is shared by a plurality of people and cooperative work is performed (for example, see Patent Documents 1 and 2). Also, there is known a technology that limits application software actually running on a server to one, distributes an execution screen by a key operation of a client to a plurality of clients, and enables cooperative work (for example, see Patent Reference 3).
[0012]
[Patent Document 1]
JP 2000-112852 A
[0013]
[Patent Document 2]
JP-A-11-25042
[0014]
[Patent Document 3]
JP-A-3-273443
[0015]
[Problems to be solved by the invention]
However, these technologies cannot be immediately applied to server-based computing (SBC) collaboration, which presumes parallel remote use of highly complex applications and centralized data management.
[0016]
Therefore, the present invention provides a new SBC collaboration that enables an existing SBC system to share an arbitrary application in an SBC server between a plurality of SBC clients and an SBC server and perform a cooperative operation. Provide system.
[0017]
[Means for Solving the Problems]
In order to solve the above-mentioned problem, a proxy server is arranged in an arbitrary area of a network connecting an SBC server and a plurality of SBC clients, and an application screen on the SBC server executed by one SBC client is copied by the proxy server. And distributes it to each SBC client. In addition, in response to a request from the SBC client, the location of the operation right for operating the application is dynamically switched by the proxy server, so that any SBC client participating in the cooperative work (session) intervenes in the application operation. Enable.
[0018]
More specifically, according to the first aspect of the present invention, an SBC server having SBC middleware capable of introducing an arbitrary application is connected to the SBC server via a network, and the application can be used remotely. Provided is an SBC collaboration system including a plurality of SBC clients and a proxy server arranged in an arbitrary area on a network and connecting between the SBC server and the plurality of SBC clients. In this SBC collaboration system, the proxy server (a) gives the first SBC client an operation right for permitting the execution of the application, and (b) the first SBC client executes the first application that executes the application from the first SBC client. Receiving the input operation information, transferring the first input operation information to the SBC server to execute the application, and (c) receiving an execution screen of the application from the SBC server, and displaying the execution screen of the plurality of SBC clients. Deliver to.
[0019]
The plurality of SBC clients constitute a session group for cooperative work using an application on the SBC server. The proxy server manages the transfer of the operation right among a plurality of SBC clients constituting the session group. The operation right is given to one SBC client among the plurality of SBC clients, but by coordinating the location of the operation right among the plurality of SBC clients, the plurality of SBC clients cooperate with each other, One application on the server can be operated.
[0020]
The proxy server copies and distributes the execution screen of the application corresponding to the input operation of the SBC client having the operation right by the number of the plurality of SBC clients participating in the session.
[0021]
When receiving the operation right acquisition request from the second SBC client having no operation right, the proxy server transmits an operation right transfer request to the first SBC client. Then, when the operation right transfer permission notification is received from the first SBC client, the operation right is transferred to the second SBC client.
[0022]
In this way, by adjusting the transfer of the application operation right via the proxy server, it is possible to cooperate with a plurality of SBC clients using the existing SBC middleware as it is.
[0023]
According to a second aspect of the present invention, an SBC server having SBC middleware capable of introducing an arbitrary application is connected to a plurality of SBC clients connected to the SBC server via a network and capable of remotely using the application. Provide a proxy server to be inserted into the. The proxy server includes: (a) an operation right management unit that gives an operation right to permit execution of the application to the first SBC client; and (b) a second operation right for executing the application from the first SBC client. Receiving the first input operation information, transferring the first input operation information to the SBC server, and executing the application; and (c) receiving an execution screen of the application from the SBC server. An execution screen distribution unit that transmits the execution screen to a plurality of SBC clients.
[0024]
The execution screen distribution unit includes a copy unit that duplicates the execution screen of the application by the number of the plurality of SBC clients. Since the copied execution screen is uniformly distributed to the SBC clients participating in the session, it is possible to maintain a high communication speed and high responsiveness between the SBC client and the SBC server.
[0025]
When receiving the operation right acquisition request from the second SBC client having no operation right, the operation right management unit transmits an operation right transfer request to the first SBC client. Then, when the operation right transfer permission notification is received from the first SBC client, the operation right is transferred to the second SBC client.
[0026]
The operation right management unit manages the transfer of the application operation right among the plurality of SBC clients, so that the cooperative work using the existing SBC system is enabled.
[0027]
Other configurations and features will become apparent from the detailed description given below with reference to the drawings.
[0028]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 2 is a schematic configuration diagram of the SBC collaboration system β according to an embodiment of the present invention. The SBC collaboration system β includes an SBC server 3, a plurality of SBC clients 6A, 6B, 6C connected to the SBC server 3 via a network 4, and a proxy server 10 installed in an arbitrary area on the network 4. .
[0029]
The SBC server 3 has the SBC middleware 2 into which an arbitrary application can be introduced. The SBC middleware 2 is existing SBC middleware. Each SBC client 6 has an SBC browser 5 and an SBC collaboration auxiliary unit 7, and a user can remotely use the application 1 on the SBC middleware 2 from the SBC browser 6 via the network 4. The SBC collaboration assisting unit 7 assists the SBC client 6 in the SBC collaboration process by the proxy server 10.
[0030]
The proxy server 10 is installed between the SBC server 3 and the SBC clients 6A to 6C, and has an operation information processing unit 11 and a collaboration control unit 12. The operation information processing unit 11 processes information related to an application operation input via the SBC browser 5 of each SBC client 6. On the other hand, the collaboration control unit 12 processes information input via the SBC collaboration auxiliary unit 7 of the SBC client, and controls a collaboration operation among the plurality of SBC clients 6.
[0031]
The SBC clients 6A to 6C connected to the SBC server 3 via the network 4 and the proxy server 10 form a group for performing a session using the application 1 on the SBC middleware 2. This is, for example, a session group I. Although three SBC clients 6A to 6C are illustrated in FIG. 2 for convenience of illustration, a session group may be composed of more SBC clients. Although not shown, a plurality of session groups are connected to the SBC server 3 via the network 4 and the proxy server 10, and can cooperate by remotely using the application 1 for each session group.
[0032]
The session ID of the entire group and the user IDs of the users participating in the session in this group are reserved and registered in the proxy server in advance by contract or the like. It is assumed that the IP address and the port number of the proxy server for performing the cooperative work are assigned to the SBC client 6 by the reservation registration.
[0033]
The proxy server 10 is a virtual SBC server when viewed from the SBC client 6, and is a virtual SBC client when viewed from the SBC server 3. For the server 3, the client that uses the application 1 is the session group I, and it does not matter how many SBC clients belong to the session group I and which SBC client in the group is currently executing the application. Actually, the application is executed by one SBC client in the session group I. However, the location of the operation right is managed by the proxy server 10, and from the viewpoint of the SBC server 3, the session group I is The state where the application 1 is used is established. Therefore, it is possible to perform cooperative work by a plurality of SBC clients within the group I by directly using the one-to-one application operation, which is a basic aspect of the existing SBC middleware 2.
[0034]
FIG. 3 is a detailed block configuration diagram of the proxy server 10. The proxy server 10 accepts inputs from the SBC clients 6A, 6B, 6C, accepts inputs from the client input accepting unit 15, and accepts inputs from the SBC server 3, in addition to the operation information processing unit 11 and the collaboration control unit 12 described above. It has a server input receiving unit 16 and a client information database 18 for storing client information. Examples of the client information include a session ID, a scheduled user ID, a password, the IP and port number of the SBC server 3, and the like. Part or all of the client information is also set in the SBC server 3.
[0035]
The input-to-client receiving unit 15 distributes the packet received from the SBC client 6 to either the operation information processing unit 11 or the collaboration control unit 12 according to the type of information included in the packet.
[0036]
The operation information processing unit 11 is an operation information relay unit 25 that relays an input operation by one SBC client 6 belonging to the session group I to the SBC server 3, and is executed in the SBC server 3 based on the input operation information. It has an SBC browser screen distribution unit 21 that distributes the execution screen to each of the SBC clients 6A to 6C. The SBC browser screen distribution unit 21 has a copy unit 22, and copies the execution screen of the application for the participating users before distribution.
[0037]
The operation information relay unit 25 determines whether the packet transmitted from the client input reception unit 15 is a packet from an SBC client (hereinafter, referred to as a “privileged user”) to which the operation right is currently given. It has a packet determining unit 26 for determining. If the packet is from a privileged user, the packet transmitting unit 27 transmits the packet to the SBC server 3. If the packet is from a user other than the current privileged user (hereinafter, referred to as a “normal user”), it is regarded as an input due to an erroneous operation, and the operation information discarding unit 28 discards the packet.
[0038]
On the other hand, the collaboration control unit 12 includes a collaboration user authentication unit 31, a collaboration session management unit 32, and a collaboration operation right management unit 33. Details of the operation of these elements will be described later.
[0039]
FIG. 4 shows an example of the SBC collaboration browser 41 displayed on the SBC client 6. The SBC collaboration browser 41 has the SBC browser 5 and the SBC collaboration assistant 7. The SBC browser 5 is executed by the server 3 and displays an execution screen (SBC browser screen) copied and distributed by the proxy server 10. All participating users can browse the current execution screen on the SBC browser 5 in real time.
[0040]
The SBC collaboration auxiliary unit 7 has a session information display unit 42 and an active control unit 43. The session information display unit 42 has, as an example, a session participant list screen 52 indicating the session participants and the location of the current operation right, and a message display screen 53 displaying the operation history of the system. The active control unit 43 has an operation right acquisition request button 54. If an arbitrary SBC client wants to participate in the execution of the application 1 during the cooperative work using the application 1 on the SBC middleware 2, the operation right acquisition request button 54 is clicked. The change of the operation right by the operation right acquisition request button will be described later.
[0041]
In the example of FIG. 4, for example, the operation right is given to the user of the SBC client 6A, Tanabe, and the users of the other SBC clients 6B, 6C have only the viewing right. The viewing right is automatically given to all participating users, and of course, the user having the operation right also has the viewing right. Therefore, between the SBC client 6 and the proxy server 10, two-way communication is given to the application operation right holder, and one-way communication is established to other application viewers.
[0042]
Regarding the location of the operation right at the start of the session, for example, the person who convened the session within the session group I and first accessed the proxy server 10 may be given the operation right, or the person who is given the operation right at the start. May be determined in advance.
[0043]
FIG. 5 is a diagram showing a processing sequence of collaboration using the SBC system β of FIG. It is assumed that all of the SBC clients 6A to 6C, the proxy server 10, and the SBC server 3 have been started (ST11 to ST14).
[0044]
In this state, for example, the user (privileged user) of the SBC client 6A connects to a port (not shown) of the proxy server 10 specified in advance and requests an SBC collaboration service (ST15). This connection request is made from the SBC collaboration auxiliary unit 7 of the SBC collaboration browser 41 shown in FIG. The proxy server 10 performs client authentication for the accessing SBC client 6A (ST16).
[0045]
In the client authentication procedure, the collaboration user authentication unit 31 of the proxy server 10 receives the user ID, password, client IP address, and the like of the SBC client 6A from the client input receiving unit 15. The collaboration user authentication unit 31 requests the collaboration session management unit 32 to confirm the session ID. The collaboration session management unit 32 searches the client information database 18, extracts the reserved session ID from the accessed port number of the proxy server 10, and searches for the participation scheduled user ID from the extracted session ID. If the user ID of SBC client 6A is included in the scheduled user ID, collaboration user authentication unit 31 confirms the password and completes the authentication (YES in ST16), and provides authentication completion information to SBC client 6A. Is transmitted (ST17).
[0046]
On the other hand, when the user authentication is successful in the user authentication unit 31, the collaboration session management unit 32 updates the session information such as the session ID, the user ID, and the client IP address. With the update of the session information, the collaboration operation right management unit 33 assigns the operation right to the SBC client 6A that has first requested the connection, and updates the operation right information.
[0047]
At this point, the participant list screen 52 (see FIG. 4) of the SBC collaboration auxiliary unit 7A of the SBC client 6A displays the user name (for example, Tanabe) of the first participant SBC client 6A with the privilege having the operation right. The user is displayed with the IP address (192.168.10.1). Then, it waits until the authentication of another session participant is completed (ST18).
[0048]
Similarly, the other SBC clients 6B and 6C also request connection to the proxy server 10 (ST19), and receive client authentication (YES in ST20). Each time the authentication of the SBC clients 6B and 6C is completed, the proxy server 10 transmits the authentication completion information to all the SBC clients 6 that have already participated (ST21). As a result, the names of the users whose authentication has been completed are sequentially displayed on the participant list screen 52 of the SBC collaboration auxiliary unit 7. For example, when the authentication is completed in response to the participation request of the SBC client 6B, the user name (for example, Nakamura) of the SBC client 6B is additionally displayed as a new participant on the participant list screen 52 of the SBC client 6A ( ST22a). At the same time, the participant list screen 52 of the SBC client 6B displays the name of the privileged user (Tanabe) and the name of the self (Nakamura) (ST22b). Then, it waits until all participants have been authenticated (ST22a, ST22b).
[0049]
Next, SBC client 6A (privileged user) transmits an SBC collaboration start command to proxy server 10 (ST23). The proxy server 10 receives the collaboration start command (ST24), and requests the SBC server 3 to start the SBC service (ST25).
[0050]
The SBC server 3 performs client authentication on the service request (session start request) from the proxy server 10 (ST26). If the authentication is successful (YES in ST26), the SBC server 3 sends a collaboration start notification to the proxy server 10. It transmits (ST27). The proxy server 10 receives the collaboration start notification and transmits it to the SBC clients 6A to 6C of all participants participating in the session (ST28). In response, as shown in FIG. 4, a message indicating that the collaboration has been started is displayed on message display screen 53 of SBC clients 6A to 6C (ST29, ST30).
[0051]
In parallel with the start of the collaboration, the SBC server 3 sends the full screen information of the application 1 to the proxy server 10 (ST31). Upon receiving the full screen information (ST32), the proxy server 10 copies the full screen information by the number of participating users, and distributes the copied screen to each of the SBC clients 6A to 6C (ST33). The distributed full screen information is displayed on the SBC browsers 5A to 5C of the SBC clients 6A to 6C (ST34, ST35).
[0052]
6 and 8 are diagrams showing the above-described collaboration start processing (ST23 to ST30) and full screen output processing (ST31 to ST35) from the side of the system operation. First, in FIG. 6, the SBC collaboration assisting unit 7A of the SBC client 6A having the operation right transmits a collaboration start request to the proxy server 10 (arrow (1)). The request for starting the collaboration is executed, for example, by clicking the start button 61 on the collaboration start confirmation screen shown in FIG.
[0053]
The collaboration start confirmation screen is configured to be displayed only on the SBC collaboration auxiliary unit 7A of the SBC client 6A to which the operation right has been given. In this case, the right to operate the application given to the privileged user also includes the right to start collaboration. Alternatively, a configuration may be adopted in which a collaboration start confirmation screen is displayed on the SBC collaboration auxiliary unit 5 of all participating users who have completed authentication. In the latter case, even if a normal user who does not have the operation right clicks the collaboration start request button, the user is rejected in the confirmation processing by the collaboration user authentication unit 31 and the collaboration operation right management unit 33. The privileged user will start the collaboration.
[0054]
The collaboration start request is received by the client input reception unit 15 of the proxy server 10 and sent to the collaboration session management unit 32 (arrow (2)). The collaboration session management unit 32 searches for a session ID from the port number to which the collaboration start request has been input, and the searched session ID is the ID of a session that is not currently activated (that is, newly started). Make sure that Then, the ID of the user who has activated the collaboration start request is confirmed (process (3)).
[0055]
The collaboration session management unit 32 confirms with the collaboration operation right management unit 33 that the user who has requested the start of the collaboration has the operation right of this session (arrow (4)). After the confirmation, the password of the user who has requested the start of the collaboration is acquired from the collaboration user authentication unit 31 (arrow (5)).
[0056]
After obtaining the password, the collaboration session management unit 32 requests the SBC server 3 to start an SBC session, and the SBC server 3 performs client authentication based on the user ID, the password, the port number of the SBC server 3, and the like, and responds to the session start request. (Arrow (6)). For convenience of illustration, the process (6) is indicated by a two-way arrow, but a response from the SBC server 3 is supplied to the collaboration session management unit 32 via the server input receiving unit 16.
[0057]
The collaboration session management unit 32 transmits a session start notification to the proxy input reception units 8A to 8C of the SBC clients 6A to 6C (arrow (7)). The session start notification is sent to the SBC collaboration assisting units 7A to 7C of each SBC client (arrow (8)) and displayed on the message display unit 53 in FIG. In the example of FIG. 4, "17:25 Collaboration has started" is displayed.
[0058]
On the other hand, the SBC middleware 2 starts the application 1 in response to the session start request (arrow (9)). The application 1 outputs the full screen of the application (arrow (10)), and the SBC server 3 transmits the full screen to the server input receiving unit 16 of the proxy server 10 (arrow (11)).
[0059]
FIG. 8 is a system operation diagram when the SBC screen is output. The operation shown in FIG. 8 is equally applied to the full screen output immediately after the start of the session and to the output of the execution screen which is the execution result of the application. The difference is that all screen information is copied and delivered at the time of full screen output, whereas only the changed part by the execution operation is copied and delivered in the case of the application execution screen, so see FIG. Next, the full-screen output operation will be described.
[0060]
First, the application 1 started in the SBC server 3 in response to the session start request opens the entire screen on the SBC middleware 2 (arrow (1)). The SBC middleware 2 transmits the entire screen together with its attributes to the proxy server 10 (arrow (2)). The input-to-server accepting unit 16 of the proxy server 10 supplies the received entire screen and the attributes together with the port number to the copying unit 22 of the SBC browser screen distribution unit 21 (arrow (3)).
[0061]
The SBC browser screen distribution unit 21 confirms the screen output destination to the collaboration session management unit 32. The collaboration session management unit 32 searches the port ID for the session ID and the IP addresses of all the SBC clients participating in this session, and supplies the search result of the screen output destination to the SBC browser screen distribution unit 21 (arrow ( 4)). The SBC browser screen distribution unit 21 copies all screen information by the number of copies corresponding to the number of screen output destinations in the copying unit 22, and distributes this to each of the SBC clients 6A to 6C (arrow (5)).
[0062]
The proxy input accepting units 8A to 8C of the SBC clients 6A to 6C supply the received full screen information to the SBC browsers 5A to 5C (arrows (6)) and display the first full screen on the SBC browsers 5A to 5C. I do.
[0063]
Returning to FIG. 5, when the full screen is displayed on the SBC browsers 5A to 5C of all the participants and the collaborative state is substantially achieved, the privileged user of the SBC client 6A to which the operation right of the application has been given is designated by a mouse. The application is operated on the SBC browser 5A using a keyboard or the like (ST36). Input operation information such as a mouse / keyboard is supplied from the client input receiving unit 15 of the proxy server 10 to the operation information relay unit 25 of the operation information processing unit 11.
[0064]
The packet determination unit 26 (see FIG. 3) of the operation information relay unit 25 determines whether the packet including the input operation information is from a privileged user having the operation right (ST37). If the packet is from a normal user (NO in ST37), the operation information discard unit 28 discards the input operation information. On the other hand, if the packet is from a privileged user (YES in ST37), packet transmitting section 27 transmits this packet to SBC server 3 (ST38).
[0065]
For packet determination, the packet determination unit 26 checks the session ID, the participating user ID, and the location of the current operation right (privileged user ID) of the received packet with the collaboration session management unit 32 and the collaboration operation right management unit 33. This is done by: With such a determination, the input operation information is relayed to the SBC server 3 only when the received packet is a packet from a privileged user who has the correct operation right. Discarding packets from normal users who do not have the operation right is intended to prevent complicated operation of application execution due to erroneous operation of the mouse / keyboard or unintentional operation despite the lack of operation right. is there.
[0066]
Upon receiving the input operation information from the privileged user, the SBC server 3 executes the application 1 based on the input operation information (ST39). As a result of executing the application 1, the execution screen is updated. The SBC server 3 transmits screen update information on the update part (change part) to the proxy server 10 (ST40). As described above, when the execution of the application is actually started, unlike when the session is started, it is not necessary to transmit the full screen information, and only the difference information that is the execution result need be transmitted.
[0067]
When the proxy server 10 receives the screen update information at the server input receiving unit 16, it supplies this screen update information to the SBC browser screen distribution unit 21. Upon receiving the screen update information (ST41), the SBC browser screen distribution unit 21 copies the screen update information for the participating users by the copying unit 22, and distributes it to each of the SBC clients 6A to 6C (ST42). The SBC clients 6A to 6C incorporate the screen update information into all the screens already displayed, and display the execution results of the application by the privileged user on the SBC browsers 5A to 5C (ST43, ST44).
[0068]
The operation of copying and distributing the screen update information is the same as the operation of copying and distributing the full screen information described with reference to FIG. As long as the privileged user continues to execute the application, the processes in ST36 to ST44 are repeated, and the execution screen is displayed on each of the SBC clients 6A to 6C in real time.
[0069]
The SBC client can remotely view the execution of a complex application in real time as long as it has a display function, and can reduce the operation management cost of the application in each SBC client. Further, after transmission of all screen information at the start of the session, only the screen update information by the execution of the application is transmitted, so that the communication volume is light and a sufficient communication speed can be secured. Furthermore, since only the screen information to be distributed to the SBC client is copied, the processing in the proxy server 10 is fast, and the SBC collaboration system as a whole has high responsiveness and operability to application execution.
[0070]
The SBC client of the privileged user having the operation right also executes the complicated and sophisticated application mounted on the SBC server as if the application installed on the SBC client itself is operated, as long as the display device and the input device are provided. be able to. Since the execution history is centrally managed by the SBC server, the resource management burden on the SBC client is greatly reduced.
[0071]
FIG. 9 is a diagram showing a processing sequence for transferring the operation right among a plurality of session participants. All of the SBC clients 6A to 6C, the proxy server 10, and the SBC server 3 of the session participating user are in the session state (ST51 to ST54).
[0072]
First, when one of the normal users of the SBC clients 6B and 6C clicks the operation right acquisition request button 54 (see FIG. 4) of the SBC collaboration auxiliary unit 7, an application operation right acquisition request is issued to the proxy server 10. Is performed (ST55). Upon receiving the operation right acquisition request (ST56), the proxy server 10 issues a request to transfer the application operation right to the SBC client 6A of the current privileged user (ST57).
[0073]
The SBC client 6A inquires of the privileged user whether to permit the transfer request of the application operation right (ST58). The inquiry is made by, for example, displaying the operation right transfer request screen shown in FIG. 11A on the SBC collaboration auxiliary unit 7A of the SBC client 6A. The privileged user clicks the permission button 71 when permitting the transfer of the application operation right (YES in ST58), and clicks the reject button 72 when rejecting the transfer of the operation right (NO in ST58).
[0074]
In the example of FIG. 9, the operation right transfer request screen is configured to be displayed only on the SBC collaboration auxiliary unit 7A of the current privileged user (SBC client 6A). However, as a notice of the change of the operation right, all the SBC clients 6A are notified. The operation right transfer request screen may be displayed on the SBC collaboration assisting units 7A to 7C of 6C to 6B. In this case, the operation of the permission button 71 or the reject button 72 by a person other than the privileged user is abandoned after the proxy server 10 confirms the privileged user ID.
[0075]
By operating a button on the operation right transfer request screen, the SBC client 6A transmits a response to the transfer request to the proxy server 10 (ST59). When receiving the answer from the privileged user (ST60), the proxy server 10 determines whether or not the transfer of the operation right has been established (ST61), and transmits the transfer request result to the SBC clients 6A to 6C (ST62).
[0076]
The transfer request result is displayed on the SBC collaboration auxiliary unit 7 of the SBC clients 6A to 6C (ST63, ST64). When the transfer request is rejected, for example, an operation right transfer rejection screen shown in FIG. 11B is displayed on the SBC collaboration auxiliary unit 7C of the SBC client 6C that has made the operation right acquisition request. When the transfer request is permitted, the participant list screens 52 (see FIG. 4) of all the SBC clients 6A to 6C are displayed as, for example, “Browsing: Tanabe (192.168.10.1), Browsing: Nakamura (192) .168.10.2), operation right: Suzuki (192.168.10.3). If it is specified that the location of the operation right has been changed, the order of display does not matter. The location of the operation right may be highlighted, for example, by highlighting it or displaying it in a different color. Further, the change of the operation right may be displayed on the participant list screen 52, and the transfer of the operation right may be displayed together with the time in the session history of the message display screen 53.
[0077]
FIG. 10 is a diagram for explaining the procedure for changing the operation right from the aspect of the system operation. For example, the SBC client 6C transmits an operation right acquisition request from the SBC collaboration auxiliary unit 7C to the proxy server 10 (arrow (1)). The input-to-client receiving unit 15 of the proxy server 10 supplies the operation right acquisition request to the collaboration operation right management unit 33 together with the port number and the client IP address (arrow (2)). The collaboration operation right management unit 33 confirms the session ID and the user ID with the collaboration session management unit 32. The collaboration session management unit 32 extracts the session ID and the user ID from the port number, and supplies the extraction result to the collaboration operation right management unit 33 (arrow (3)). The collaboration operation right management unit 33 retrieves the current privileged user ID from the session ID (process (4)), and transmits an operation right transfer request to the current privileged user (user of the SBC client 6A) (arrow (5) )).
[0078]
The proxy input receiving unit 8A of the SBC client 6A supplies the received operation right transfer request to the SBC collaboration auxiliary unit 7A (arrow (6)). The SBC collaboration assisting unit 7A displays, for example, an operation right transfer request screen shown in FIG. The SBC client 6A transmits a response to the transfer request to the proxy server 10 (arrow (7)). The client input reception unit 15 of the proxy server 10 supplies the transfer request result to the collaboration operation right management unit 33 (arrow (8)).
[0079]
If the answer result is permission for transfer of the operation right, the collaboration operation right management unit 33 updates the current privileged user ID and transmits the updated privileged user information to all the SBC clients 6A to 6C (arrows). (9)). If the answer is rejection of the transfer of the operation right, the current privileged user ID is maintained and a notification of the rejection of the operation right is transmitted to the SBC client 6C.
[0080]
The proxy input accepting units 8A to 8C of the SBC clients 6A to 6C supply the new privileged user or the rejection result of the operation right transfer request to the SBC collaboration auxiliary units 7A to 7C and display them (arrow (10)).
[0081]
Returning to FIG. 9, as a result of the transfer of the operation right, a new privileged user, for example, the user of the SBC client 6C operates the application on the SBC browser 5C using a mouse / keyboard or the like (ST65). The input operation information is transmitted to the proxy server 10, and the operation information relay unit 25 of the proxy server 10 determines whether the input operation information is a packet from a privileged user (ST66). If the packet is from a privileged user (YES in ST66), this input operation information is relayed to SBC server 3 (ST67). The SBC server 3 executes the application according to the input operation information (ST68). If the packet is not from a privileged user (NO in ST66), the operation information discard unit 28 discards the packet.
[0082]
The SBC server 3 transmits screen update information, which is the execution result of the application, to the proxy server 10 (ST69). The proxy server 10 copies the received screen update information for the participating users and distributes it to all the SBC clients 6A to 6C participating in the session (ST70, ST71). The SBC clients 6A to 6C display the updated execution screen on the SBC browsers 5A to 5C (ST72, ST73).
[0083]
The system operation of copying and distributing the screen update information is as described with reference to FIG. 8, and the description is omitted. The operation of the application by the new privileged user continues until the operation right acquisition request button is clicked next and the transfer of the operation right is permitted, and ST65 to ST73 are repeated.
[0084]
As described above, only the privileged user having the operation right of the application can actually execute the application 1 in the SBC server 3, but the operation right is located between the privileged user and the normal user in the group. It can be changed at any time by negotiation. Since the collaboration operation right management unit 33 of the proxy server 10 collectively manages the change and location of the operation right, the burden on the SBC client 6 is small.
[0085]
In addition, regardless of the location of the operation right, the execution screen of the application 1 is copied and distributed by the proxy server 10, so that it is displayed in real time on all the SBC clients 6 participating in the session. From the viewpoint of the SBC server 3, the client that executes the application 1 is the session group I, and the existing basic specifications of the SBC middleware 2 that has one-to-one correspondence between the client and the application can be used as they are.
[0086]
In the above, the processing sequence and the system operation have been described based on an example in which a session is started after all prospective session participants have been prepared. However, a configuration may be employed in which a user belonging to the session group I can participate in the session halfway. In this case, the privileged user who has the operation right can issue a collaboration start command according to his / her own intention while confirming the login state of another session participant, and start the collaboration. Also, the SBC clients 6B and 6C do not wait until all clients scheduled to participate, but wait until a privileged user issues a collaboration start command. Furthermore, it is also possible to adopt a configuration in which a privileged user having an operation right permits or denies participation of a new user belonging to the group.
[0087]
As a processing sequence, after the session starts, an SBC client 6D (not shown) requesting participation in the session starts up the SBC collaboration browser 41 and makes a connection request to the proxy server 10. After the client authentication, the collaboration session management unit 32 of the proxy server 10 searches for the session ID from the input port number, and determines whether the searched session is currently in session. During the session, the current privileged user is confirmed to the collaboration operation right management unit 33, and a collaboration participation request request is transmitted to the SBC client 6A, which is the privileged user. The SBC client 6A receives the request for participation, and a collaboration participation request screen shown in FIG. 12A is displayed on the SBC collaboration assisting unit 7A.
[0088]
The privileged user clicks the permission button 81 or the rejection button 82 on the collaboration participation request screen to permit or prohibit the user's participation during the session. In the case of non-permission, the collaboration session management unit 32 of the proxy server 10 transmits a non-permission notification to the SBC client 6D that has made the participation request. For example, a collaboration participation rejection screen shown in FIG. 12B is displayed on the SBC collaboration auxiliary unit 7D of the SBC client 6D.
[0089]
When the participation in the session is permitted by clicking the permission button 81, the collaboration session management unit 32 of the proxy server 10 adds a new user ID to the list of user IDs participating in the session. At the same time, the proxy server 10 requests the current full screen information from the SBC server 3. The SBC server 3 sends the current full screen information to the proxy server 10. The SBC browser screen distribution unit 21 of the proxy server 10 distributes the full screen information to the SBC client 6D whose session participation has been recognized, and the current application execution screen is displayed on the SBC browser 5D of the SBC client 6D.
[0090]
The collaboration session management unit 32 further transmits updated session participant information to all the SBC clients 6A to 6D. In the SBC collaboration assisting units 7A to 7D of the SBC clients 6A to 6D, the participant list screen 52 and the message display screen 53 (see FIG. 4) are updated. That is, for example, information such as “Browsing: Maeda (192.168.10.4)” is added to the participant list screen 52, and the participation of the SBC client 6D is displayed in the session history of the message display screen 53 together with the time. .
[0091]
Regarding the termination of the session, a method in which the privileged user forcibly terminates the SBC client 6 and a method in which the session is terminated on a screen different from the collaboration start confirmation screen (see FIG. 7) are considered. In the latter case, for example, by right-clicking on the screen of the SBC client 6, a collaboration stop menu is displayed and selected.
[0092]
Upon receiving the session stop request, the proxy server 10 disconnects the connection with the SBC server 3. In the SBC server 3, the application is stored in an activated state, and when the connection is made again from the proxy server 10, the collaboration can be continued from the state of the application at the time of disconnection.
[0093]
In the above-described embodiment, the user ID of the privileged user is used for the connection from the proxy server 10 to the SBC server 3. However, the proxy server 10 associates the unique user ID with the application 1 on the SBC server 3. And a password may be held.
[0094]
The SBC collaboration system β is applicable to any field such as education, medical care, design, and architecture. In any case, at the site where the cooperative work is performed, it is only necessary to prepare the SBC client 6 having the display function and the simple input device. The high-load application is executed in the SBC server 3, and the proxy server 10 distributes the execution screen to all the SBC clients participating in the session in real time. In addition, since the session history and the location and change of the operation right are centrally managed by the proxy server 10, the load on the SBC client 6 is small.
[0095]
As the SBC client, a terminal device such as a desktop PC, a notebook personal computer, a PDA, or a mobile phone having an existing SBC browser can be used. By simply adding the SBC collaboration assisting unit 7 used in the present invention to such an SBC browser function, SBC collaboration using an arbitrary application in the SBC server 3 remotely is enabled.
[0096]
The processing operation of the SBC collaboration auxiliary unit 7 of the SBC client 6 and the processing operation of the proxy server 10 may be realized by any of hardware, software, and firmware. When the SBC collaboration assisting unit 7 is realized by software, the SBC collaboration assisting program may be recorded on an arbitrary computer-readable recording medium and distributed, or may be transmitted from the proxy server 10 to the SBC client via the network 4. May be delivered.
[0097]
The SBC collaboration auxiliary program installed on the SBC client includes the following procedure.
(A) When the proxy server gives the first SBC client the operation right of the application, the SBC client displays the location of the operation right.
(B) When the first SBC client executes an application on the SBC server, the SBC client displays an execution screen sent via the proxy server.
(C) When the second SBC client acquires the operation right of the application, the second SBC client causes the SBC client to display the transfer of the operation right.
[0098]
The SBC collaboration auxiliary program further includes a procedure for requesting the SBC client to acquire an operation right as necessary.
[0099]
By simply introducing the collaboration assisting program into an existing SBC client terminal, cooperative work can be performed using an arbitrary application in a remote SBC server.
[0100]
If the proxy server is realized by software, an SBC collaboration processing program executed by the proxy server may be installed. The SBC collaboration processing program includes the following procedure.
(A) The proxy server is given the operation right of the application to the first SBC client.
(B) When the first input operation information for executing the application on the SBC server is received from the first SBC client, the proxy server transfers the first input operation information to the SBC server.
(C) When receiving the execution screen of the application from the SBC server, the proxy server distributes the execution screen to the plurality of SBC clients.
[0101]
By installing such a function in the proxy server, SBC collaboration using an existing SBC system can be realized.
[0102]
【The invention's effect】
ADVANTAGE OF THE INVENTION According to this invention, sharing of the application in an SBC server and cooperative work between several SBC clients are possible, using the existing SBC middleware.
[0103]
During the collaboration, only the screen update information associated with the execution of the application is copied and distributed, so that the responsiveness is excellent.
[Brief description of the drawings]
FIG. 1 is a schematic configuration diagram of a general SBC system.
FIG. 2 is a schematic configuration diagram of an SBC collaboration system according to an embodiment of the present invention, showing a network configuration including a proxy server that enables sharing and cooperative work of applications on an SBC server among a plurality of SBC clients. FIG.
FIG. 3 is a block diagram of a proxy server used in the system of FIG. 2;
FIG. 4 is a diagram showing an example of an SBC collaboration browser displayed on an SBC client.
FIG. 5 is a diagram showing an SBC collaboration start processing sequence.
FIG. 6 is a diagram for explaining an operation of the system at the start of SBC collaboration.
FIG. 7 is a diagram showing an example of a collaboration start confirmation screen.
FIG. 8 is a diagram for explaining an operation of the system when an SBC screen is output in SBC collaboration.
FIG. 9 is a diagram showing a processing sequence of application operation right transfer.
FIG. 10 is a diagram for explaining the operation of the system at the time of transferring the operation right.
FIG. 11 illustrates an example of an operation right transfer request screen and an operation right transfer rejection screen.
FIG. 12 is a diagram showing an example of a collaboration participation request screen and a collaboration participation rejection screen.
[Explanation of symbols]
α SBC system
β SBC Collaboration System
1 application
2 SBC middleware
3 SBC server
4 Network
5A, 5B, 5C SBC browser
6A, 6B, 6C SBC client
7A, 7B, 7C SBC Collaboration Assistant
8A, 8B, 8C proxy input receiving unit
10 Proxy server
11 Operation information processing unit
12 Collaboration control unit
15 Client input reception unit
16 Server input reception unit
18 Client information database
21 SBC browser screen distribution unit (execution screen distribution unit)
22 Copier
25 Operation information relay unit
26 Packet judgment unit
27 Packet Transmitter
28 Operation information discarding section
31 Collaboration User Authentication Department
32 Collaboration Session Management Department
33 Collaboration Operation Right Management Department
41 SBC Collaboration Browser
42 Session information display section
43 Active control unit
52 Participant list screen
53 Message display screen
54 Operation right acquisition request button

Claims (18)

An SBC server having SBC middleware capable of introducing an arbitrary application,
A plurality of SBC clients connected to the SBC server via a network and capable of remotely using the application;
A proxy server arranged in an arbitrary area on the network and connecting between the SBC server and a plurality of SBC clients, wherein the proxy server comprises:
Giving the first SBC client an operation right to permit execution of the application,
Receiving, from the first SBC client, first input operation information for executing the application, transferring the first input operation information to the SBC server, and causing the SBC server to execute the application;
An SBC collaboration system receiving an execution screen of the application from the SBC server and delivering the execution screen to the plurality of SBC clients. The SBC collaboration system according to claim 1, wherein the proxy server manages the transfer of the operation right among the plurality of SBC clients. The SBC collaboration system according to claim 1, wherein the proxy server copies and distributes the execution screen of the application by the number of the plurality of SBC clients. 2. The proxy server according to claim 1, wherein the proxy server, when receiving the second input operation information from the second SBC client not having the operation right, discards the second input operation information. SBC collaboration system. The proxy server transmits an operation right transfer request to the first SBC client when receiving an operation right acquisition request from a second SBC client not having the operation right. Item 2. The SBC collaboration system according to item 1. The SBC collaboration according to claim 5, wherein the proxy server transfers the operation right to the second SBC client when receiving the permission notification of the transfer of the operation right from the first SBC client. system. An SBC server having SBC middleware capable of introducing an arbitrary application, and a proxy server inserted between a plurality of SBC clients connected to the SBC server via a network and capable of remotely using the application. hand,
An operation right management unit for giving an operation right to permit execution of the application to the first SBC client;
An operation information relay unit that receives, from the first SBC client, first input operation information for executing the application, transfers the first input operation information to the SBC server, and causes the SBC server to execute the application When,
A proxy server, comprising: an execution screen distribution unit that receives an execution screen of the application from the SBC server and transmits the execution screen to all of the plurality of SBC clients. The proxy server according to claim 7, wherein the execution screen distribution unit includes a copy unit that duplicates the execution screen of the application by the number of the plurality of SBC clients. The operation information relay unit,
A determining unit that determines whether the received input operation information is the first input operation information transmitted from the first SBC client to which the operation right has been given;
The proxy server according to claim 7, further comprising: a discarding unit that discards the received operation information when the received operation information is not the first input operation information. The said operation information relay part further has a transmission part which transfers the said received operation information to the said SBC server, when the said received operation information is the said 1st input operation information. Proxy server described in. The operation right management unit, when receiving an operation right acquisition request from a second SBC client not having the operation right, transmits an operation right transfer request to the first SBC client. The proxy server according to claim 7, characterized in that: 12. The operation right management unit according to claim 11, wherein the operation right management unit transfers the operation right to the second SBC client when receiving an operation right transfer permission notification from the first SBC client. Proxy server. A proxy server is installed between an SBC server having SBC middleware capable of introducing an arbitrary application, and a plurality of SBC clients connected to the SBC server via a network and capable of remotely using the application,
From the proxy server, granting an operation right for remotely executing an application on the SBC server to a first SBC client among the plurality of SBC clients;
Relaying the first input operation information by the first SBC client from the proxy server to the SBC server to execute the application;
An SBC collaboration method, wherein an execution screen of the application is copied by the proxy server, and the copied execution screen is transmitted to the plurality of SBC clients. Granting a viewing right to view the execution screen of the application to all of the plurality of SBC clients,
14. The proxy server according to claim 13, wherein when there is second input operation information by the second SBC client not having the operation right, the proxy server discards the second input operation information. SBC collaboration method. When the second SBC client requests the acquisition of the operation right, the proxy server issues a request to transfer the operation right to the first SBC client;
14. The method according to claim 13, wherein when the first SBC client permits the transfer of the operation right, the proxy server transfers the operation right from the first SBC client to a second SBC client. The described SBC collaboration method. An SBC server having SBC middleware capable of introducing an arbitrary application, and a proxy server connected between the SBC server via a network and a plurality of SBC clients that can remotely use the application and execute the application. SBC collaboration processing program,
Causing the proxy server to give the first SBC client an operation right for the application;
A step of, when receiving, from the first SBC client, first input operation information for executing the application, causing the proxy server to relay the first input operation information to the SBC server;
Causing the proxy server to distribute the execution screen to the plurality of SBC clients when the execution screen of the application is received from the SBC server. An SBC collaboration auxiliary program installed on each of a plurality of SBC clients connected via a network and a proxy server to an SBC server having SBC middleware capable of introducing an arbitrary application,
When the proxy server grants the first SBC client the operation right of the application, displaying the location of the operation right on each SBC client;
When the first SBC client executes the application, causing each SBC client to display an execution screen sent via the proxy server;
Causing the respective SBC clients to display the transfer of the operation right when the second SBC client acquires the operation right. 18. The SBC collaboration auxiliary program according to claim 17, further comprising a step of requesting each SBC client to acquire the operation right as needed.

Images