JP3943504B2 - SBC collaboration system and proxy server for realizing SBC collaboration - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to SBC (server-based computing) collaboration technology, and in particular, a centralized system including a proxy server that enables a plurality of remote users to share an application screen running on an SBC server and perform collaborative work. Type SBC collaboration technology.
[0002]
[Prior art]
In recent years, a so-called SBC (server-based computing) technology has developed a system in which a user can 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 by a server instead of a client terminal, and only the execution screen is transmitted to the client. The user can use the application in the server as if executing the application installed in his / her terminal. The relationship between the user and the server is basically one-to-one, and each user uses an application in the server independently. Since the client terminal only receives an execution screen corresponding to the input operation from the server, it is possible to execute a complex 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 capable of installing an arbitrary application, and an SBC client 106 that can access the SBC server 3 via the network 4. The SBC client 106 includes an SBC browser 105, and the application 1 on the SBC middleware 2 is remotely used 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 input operation information by the user to the SBC middleware 2 operating on the SBC server via the network 4 (ST1).
[0006]
The SBC middleware 2 delivers 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 processing based on the user's input operation information, 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]
Note that the application 1 on the SBC server 3 may be, for example, editor software, DTP (desktop publishing) software, CAD (computer aided), as long as the application can operate on an operating system (OS) supported by the SBC middleware 2. Basically, any application such as design) software and 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), etc. 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 alone uses the application 1 on the SBC server 3. Therefore, collaboration such as displaying the screen of the application 1 running on the SBC server 3 on the SBC browser 105 of the plurality of SBC clients 106 and mutually using the application 1 or performing collaborative work in real time. It is not easy to realize.
[0011]
On the other hand, a technique is known in which an application that can be used on the web is shared by a plurality of people and collaborative work is performed (for example, see Patent Documents 1 and 2). In addition, there is known a technology that enables collaborative work by limiting the number of application software that actually runs on a server to one and distributing execution screens by client key operations to a plurality of clients (for example, patents). Reference 3).
[0012]
[Patent Document 1]
JP 2000-112862 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 collaboration based on server-based computing (SBC) that assumes parallel remote use of advanced and complex applications and centralized management of data.
[0016]
Therefore, the present invention provides a novel SBC collaboration that enables an arbitrary application in an SBC server to be shared and collaborated between a plurality of SBC clients and an SBC server using an existing SBC system. Provide a system.
[0017]
[Means for Solving the Problems]
In order to solve the above 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. To each SBC client. In addition, any SBC client participating in collaborative work (session) can intervene in the application operation by dynamically switching the location of the operation right that can operate the application by the proxy server in response to the request of the SBC client. Enable.
[0018]
More specifically, in the first aspect of the present invention, an SBC server having SBC middleware capable of introducing an arbitrary application, and the application can be used remotely by being connected to the SBC server via a network. Provided is an SBC collaboration system including a plurality of SBC clients and a proxy server arranged in an arbitrary area on the network and connecting between the SBC server and the plurality of SBC clients. In this SBC collaboration system, the proxy server (a) grants the first SBC client an operation right to permit execution of the application, and (b) 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 receiving the execution screen from the plurality of SBC clients. Deliver to.
[0019]
A plurality of SBC clients form a session group for performing cooperative work using an application on the SBC server. The proxy server manages the transfer of operation rights 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. However, by coordinating the location of the operation right among the plurality of SBC clients, the plurality of SBC clients can cooperate with each other. It becomes possible to operate one application on the server.
[0020]
The proxy server copies and distributes the application execution screen 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 the proxy server receives an operation right acquisition request from the second SBC client that does not have the 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]
As described above, by adjusting the transfer of the application operation right through the proxy server, the existing SBC middleware can be used as it is, and a collaborative work among a plurality of SBC clients becomes possible.
[0023]
In the second aspect of the present invention, 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 remotely using the application are provided. Provides a proxy server to be inserted into The proxy server includes: (a) an operation right management unit that grants an operation right to permit execution of the application to the first SBC client; and (b) a first operation for executing the application from the first SBC client. Receiving an input operation information of 1 and 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; An execution screen distribution unit that transmits the execution screen to a plurality of SBC clients.
[0024]
The execution screen distribution unit has a copy unit that copies 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, the communication speed and responsiveness between the SBC client and the SBC server can be maintained high.
[0025]
When receiving the operation right acquisition request from the second SBC client that does not have the 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 notice is received from the first SBC client, the operation right is transferred to the second SBC client.
[0026]
Since the operation right management unit manages the transfer of the application operation right among a plurality of SBC clients, the collaborative 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]
DETAILED DESCRIPTION OF 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 the network 4, and a proxy server 10 installed in an arbitrary area on the network 4. .
[0029]
The SBC server 3 has SBC middleware 2 into which an arbitrary application can be introduced. The SBC middleware 2 is an existing SBC middleware. Each SBC client 6 includes an SBC browser 5 and an SBC collaboration assistant unit 7, and the user can remotely use the application 1 on the SBC middleware 2 from the SBC browser 6 via the network 4. The SBC collaboration assistant unit 7 assists the SBC collaboration process by the proxy server 10 from the SBC client 6 side.
[0030]
The proxy server 10 is installed between the SBC server 3 and the SBC clients 6A to 6C, and includes an operation information processing unit 11 and a collaboration control unit 12. The operation information processing unit 11 processes information related to application operations 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 assisting 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 constitute a group for performing a session using the application 1 on the SBC middleware 2. For example, this is session group I. In FIG. 2, for convenience of illustration, three SBC clients 6A to 6C are illustrated. Of course, a session group may be configured by a larger number of 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 collaborate by remotely using the application 1 in parallel for each session group.
[0032]
The session ID for the entire group and the user IDs of users who participate in the session in this group are registered in advance in the proxy server by contract or the like. It is assumed that the IP address and port number of the proxy server for performing cooperative work are given to the SBC client 6 by 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 how many SBC clients belong to the session group I and it does not matter which SBC client in the group is currently executing the application. The application is actually 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 when viewed from the SBC server 3, the session group I is only A state where the application 1 is used is established. Therefore, by using the one-to-one correspondence application operation that is the basic mode of the existing SBC middleware 2, the collaborative work by a plurality of SBC clients can be performed within the group I.
[0034]
FIG. 3 is a detailed block diagram of the proxy server 10. The proxy server 10 receives inputs from the SBC clients 6A, 6B, and 6C in addition to the operation information processing unit 11 and the collaboration control unit 12 described above, and receives inputs from the client input receiving unit 15 and the SBC server 3. A server input receiving unit 16 and a client information database 18 for storing client information are included. Examples of the client information include a session ID, a participating user ID, a password, an IP of the SBC server 3, a port number, and the like. Part or all of the client information is also set in the SBC server 3.
[0035]
The client input reception 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 executed in the SBC server 3 based on the operation information relay unit 25 that relays the input operation by one SBC client 6 belonging to the session group I to the SBC server 3 and the input operation information. An SBC browser screen distribution unit 21 that distributes the execution screen to each of the SBC clients 6A to 6C is provided. The SBC browser screen distribution unit 21 has a copy unit 22 and copies the application execution screen for the participating users prior to distribution.
[0037]
The operation information relay unit 25 determines whether or not the packet sent from the client input reception unit 15 is a packet from an SBC client (hereinafter referred to as “privileged user”) to which an operation right is currently given. It has the packet judgment part 26 to judge. If the packet is from a privileged user, the packet transmitter 27 transmits this packet to the SBC server 3. If the packet is from a user other than the current privileged user (hereinafter referred to as “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 includes an SBC browser 5 and an SBC collaboration assistant unit 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 view the current execution screen in real time on the SBC browser 5.
[0040]
The SBC collaboration assistant unit 7 includes a session information display unit 42 and an active control unit 43. As an example, the session information display unit 42 includes a participant list screen 52 that indicates the location of the session participants and the current operation right, and a message display screen 53 that displays an operation history of the system. The active control unit 43 has an operation right acquisition request button 54. When 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 operation right change by the operation right acquisition request button will be described later.
[0041]
In the example of FIG. 4, for example, an operation right is given to Tanabe, who is a user of the SBC client 6A, and users of other SBC clients 6B and 6C have only a viewing right. The viewing right is automatically given to all participating users, and of course the user who has 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 for the other application viewers.
[0042]
As for the location of the operation right at the start of the session, for example, the operation right may be given to the person who convened the session in the session group I and first accessed the proxy server 10, or the person who was given the operation right at the start. May be determined in advance.
[0043]
FIG. 5 is a diagram showing a collaboration processing sequence using the SBC system β of FIG. It is assumed that the SBC clients 6A to 6C, the proxy server 10, and the SBC server 3 are all started up (ST11 to ST14).
[0044]
In this state, for example, a user (privileged user) of the SBC client 6A connects to a port (not shown) of the proxy server 10 designated in advance, and requests an SBC collaboration service (ST15). This connection request is made from the SBC collaboration assistant 7 of the SBC collaboration browser 41 shown in FIG. The proxy server 10 performs client authentication for the accessed 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 reception 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 a reserved session ID from the port number of the accessed proxy server 10, and searches a participation scheduled user ID from the extracted session ID. If the user ID of the SBC client 6A is included in the planned participation user ID, the collaboration user authentication unit 31 confirms the password and completes the authentication (YES in ST16), and the authentication completion information is sent to the SBC client 6A. Is transmitted (ST17).
[0046]
On the other hand, if the user authentication unit 31 succeeds in user authentication, the collaboration session management unit 32 updates session information such as a session ID, a user ID, and a client IP address. As the session information is updated, the collaboration operation right management unit 33 grants the operation right to the SBC client 6A that first requested a connection, and updates the operation right information.
[0047]
At this time, on the participant list screen 52 (see FIG. 4) of the SBC collaboration assistant 7A of the SBC client 6A, the user name (for example, Tanabe) of the SBC client 6A that is the first participant is the privilege that has the operation right. The user is displayed with the IP address (192.168.10.1). And it will be in a standby state until the authentication of other session participants 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 authentication of the SBC clients 6B and 6C is completed, authentication completion information is transmitted from the proxy server 10 to all the SBC clients 6 that have already participated (ST21). As a result, the user names that have been authenticated are sequentially displayed on the participant list screen 52 of the SBC collaboration assistant unit 7. For example, if the authentication for the participation request of the SBC client 6B is completed, 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 privileged user's name (Tanabe) and his / her own name (Nakamura) are displayed on the participant list screen 52 of the SBC client 6B (ST22b). Then, it waits until all participants are authenticated (ST22a, ST22b).
[0049]
Next, the SBC client 6A (privileged user) transmits an SBC collaboration start command to the 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 in response to a service request (session start request) from the proxy server 10 (ST26). If the authentication is successful (YES in ST26), a collaboration start notification is sent to the proxy server 10. Transmit (ST27). The proxy server 10 receives this collaboration start notification and transmits it to the SBC clients 6A to 6C of all participants participating in the session (ST28). In response to this, as shown in FIG. 4, the message display screen 53 of the SBC clients 6A to 6C displays that the collaboration has started (ST29, ST30).
[0051]
In parallel with the start of collaboration, the SBC server 3 transmits full screen information of the application 1 to the proxy server 10 (ST31). When the proxy server 10 receives the full screen information (ST32), the proxy server 10 copies the full screen information by the number of participating users, and distributes the copy 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 and 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 system operation. First, in FIG. 6, the SBC collaboration assistant unit 7A of the SBC client 6A having the operation right transmits a collaboration start request to the proxy server 10 (arrow (1)). The collaboration start request 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 assistant unit 7A of the SBC client 6A to which the operation right is given. In this case, the right to start collaboration is included in the operation right of the application given to the privileged user. Or it is good also as a structure which displays a collaboration start confirmation screen on SBC collaboration auxiliary | assistance part 5 of all the participating users who 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 confirmation process by the collaboration user authentication unit 31 and the collaboration operation right management unit 33 is rejected. A privileged user will start a 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 the session ID from the port number to which the collaboration start request is input, and the searched session ID is the ID of a session that is not currently activated (that is, newly started from now on). Make sure. Then, the ID of the user who 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 location of the operation right for this session is the user who requested the start of the collaboration (arrow (4)). After confirmation, the password of the user who requested the start of the collaboration is acquired from the collaboration user authentication unit 31 (arrow (5)).
[0056]
After acquiring the password, the collaboration session management unit 32 requests the SBC server 3 to start an SBC session, and the SBC server 3 authenticates the client from the user ID, password, port number of the SBC server 3, and the like, and responds to the session start request. Is returned (arrow (6)). For convenience of illustration, the process (6) is indicated by a bidirectional arrow, but the response from the SBC server 3 is supplied to the collaboration session management unit 32 via the server input reception unit 16.
[0057]
Collaboration session management unit 32 transmits a session start notification to proxy input receiving units 8A to 8C of SBC clients 6A to 6C (arrow (7)). The session start notification is sent to the SBC collaboration assistant 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 started” is displayed.
[0058]
On the other hand, the SBC middleware 2 activates 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 applies equally to full screen output immediately after the start of a session and to output of an execution screen that is an execution result of an application. The only difference is that all screen information is copied and distributed during full screen output, whereas in the case of an application execution screen, only the portion changed by the execution operation is copied and distributed, so see FIG. The full screen output operation will be described.
[0060]
First, the application 1 started up in the SBC server 3 in response to the session start request opens a full 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 server input reception unit 16 of the proxy server 10 supplies the received full screen and attributes together with the port number to the copy 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 with respect to the collaboration session management unit 32. The collaboration session management unit 32 searches the session ID and the IP addresses of all SBC clients participating in this session from the port number, and supplies the search result of the screen output destination to the SBC browser screen distribution unit 21 (arrow ( Four)). The SBC browser screen distribution unit 21 copies the entire screen information by the number of copies corresponding to the number of screen output destinations in the copy unit 22, and distributes this to each of the SBC clients 6A to 6C (arrow (5)).
[0062]
The proxy input reception units 8A to 8C of the SBC clients 6A to 6C supply the received full screen information to the SBC browsers 5A to 5C (arrow (6)), and display the first full screen on the SBC browsers 5A to 5C. To do.
[0063]
Returning to FIG. 5, when all the screens are displayed on the SBC browsers 5A to 5C of all the participants and the collaborative state is enabled, the privileged user of the SBC client 6A to whom the application operation right is given is Use the keyboard or the like to operate the application on the SBC browser 5A (ST36). Input operation information such as a mouse / keyboard is supplied to the operation information relay unit 25 of the operation information processing unit 11 from the client input receiving unit 15 of the proxy server 10.
[0064]
The packet determination unit 26 (see FIG. 3) of the operation information relay unit 25 determines whether or not the packet including the input operation information is from a privileged user having an operation right (ST37). If the packet is from a normal user (NO in ST37), the operation information discarding unit 28 discards this input operation information. On the other hand, if the packet is from a privileged user (YES in ST37), the packet transmission unit 27 transmits this packet to the SBC server 3 (ST38).
[0065]
For packet determination, the packet determination unit 26 confirms the session ID, participation user ID, and location of the current operation right (privileged user ID) regarding the received packet with the collaboration session management unit 32 and the collaboration operation right management unit 33. Is done by. Based on such 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. The reason for discarding packets from normal users who do not have operation rights is to prevent application execution operations from being complicated due to incorrect operation of mouse / keyboard, etc. is there.
[0066]
When the SBC server 3 receives 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 about the updated part (changed part) to the proxy server 10 (ST40). As described above, when the application execution is actually started, unlike the session start, it is not necessary to transmit the full screen information, and only the difference information as the execution result needs to be transmitted.
[0067]
When the proxy server 10 receives the screen update information at the server input reception unit 16, the proxy server 10 supplies the screen update information to the SBC browser screen distribution unit 21. When the SBC browser screen distribution unit 21 receives the screen update information (ST41), the copy unit 22 copies the screen update information for the participating users, and distributes this to the SBC clients 6A to 6C (ST42). The SBC clients 6A to 6C incorporate the screen update information into all the already displayed screens, and display the execution results of the applications by the privileged users on the SBC browsers 5A to 5C (ST43, ST44).
[0068]
The screen update information copy and distribution operations are the same as the full screen information copy and distribution operations described with reference to FIG. As long as the privileged user continues to execute the application, the processing of ST36 to ST44 is repeated, and the execution screen is displayed in real time on each of the SBC clients 6A to 6C.
[0069]
As long as the SBC client has a display function, it is possible to remotely view the execution of a complex application in real time, and the operation management cost of the application in each SBC client can be reduced. Further, after the transmission of the full screen information at the start of the session, only the screen update information due to the execution of the application is transmitted, so the communication amount 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 for application execution.
[0070]
An SBC client of a privileged user having an operation right also executes a complex and sophisticated application installed in the SBC server as if it operates an application installed in the SBC client itself, as long as there is a display device and an input device. 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 illustrating a processing sequence of operation right delivery among a plurality of session participating users. All of the SBC clients 6A to 6C, the proxy server 10, and the SBC server 3 of the session participating users are in the session state (ST51 to ST54).
[0072]
First, when a normal user of either the SBC client 6B or 6C clicks the operation right acquisition request button 54 (see FIG. 4) of the SBC collaboration assistant unit 7, the application operation right acquisition request is sent to the proxy server 10. (ST55). When receiving the operation right acquisition request (ST56), the proxy server 10 issues an application operation right transfer request to the SBC client 6A of the current privileged user (ST57).
[0073]
The SBC client 6A inquires the privileged user as to whether or not to permit the application operation right transfer request (ST58). The inquiry is made, for example, by displaying the operation right transfer request screen shown in FIG. 11A on the SBC collaboration assistant 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 assistant unit 7A of the current privileged user (SBC client 6A). It is good also as a structure which displays an operation right transfer request | requirement screen on SBC collaboration auxiliary | assistance part 7A-7C of -6B. In this case, the operation of the permission button 71 or the rejection button 72 by a person other than the privileged user is discarded after the privileged user ID is confirmed on the proxy server 10.
[0075]
By operating the button on the operation right transfer request screen, the SBC client 6A transmits an answer to the transfer request to the proxy server 10 (ST59). When proxy server 10 receives an answer from the privileged user (ST60), proxy server 10 determines whether or not the operation right has been transferred (ST61), and transmits the transfer request result to SBC clients 6A to 6C (ST62).
[0076]
The transfer request result is displayed on the SBC collaboration assistant 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 assistant unit 7C of the SBC client 6C that has made the operation right acquisition request. When the transfer request is permitted, the participant list screen 52 (see FIG. 4) of all the SBC clients 6A to 6C is, for example, “view: Tanabe (192.168.10.1), view: Nakamura (192.168.10.2), The operation right is changed to “Suzuki (192.168.10.3)”. If it is clearly indicated that the location of the operation right has been changed, the display order is not limited. The location of the operation right may be highlighted, for example, displayed 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 in the session history of the message display screen 53 together with the time.
[0077]
FIG. 10 is a diagram for explaining an operation right change procedure from the aspect of system operation. For example, the SBC client 6C transmits an operation right acquisition request from the SBC collaboration assistant unit 7C to the proxy server 10 (arrow (1)). The client input receiving unit 15 of the proxy server 10 supplies this operation right acquisition request together with the port number and client IP address to the collaboration operation right management unit 33 (arrow (2)). The collaboration operation right management unit 33 confirms the session ID and 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 assistant unit 7A (arrow (6)). The SBC collaboration assistant 7A displays, for example, the operation right transfer request screen shown in FIG. The SBC client 6A transmits an answer 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 response result is permission to transfer 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 response result is rejection of the operation right transfer, the current privileged user ID is maintained and a notification of the operation right rejection is transmitted to the SBC client 6C.
[0080]
The proxy input receiving 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, the new privileged user, for example, the user of the SBC client 6C, operates the application on the SBC browser 5C using the 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 or not the input operation information is a packet from a privileged user (ST66). If the packet is from a privileged user (YES in ST66), the input operation information is relayed to the 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 discarding unit 28 discards the packet.
[0082]
The SBC server 3 transmits screen update information, which is an 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 and ST73).
[0083]
The system operation for copying and distributing the screen update information is as described in connection with FIG. The operation of the application by the new privileged user is continued until the next operation right acquisition request button is clicked and the transfer of the operation right is permitted, and ST65 to ST73 are repeated.
[0084]
In this way, only a privileged user having the application operation right can actually execute the application 1 in the SBC server 3, but the operation right is located between the privileged user and a 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]
Regardless of the location of the operation right, the execution screen of the application 1 is duplicated and distributed by the proxy server 10 and 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 basic specifications of the existing SBC middleware 2 that has a 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 scheduled participants have been prepared. However, a configuration may be adopted in which users belonging to the session group I can participate in the session halfway. In this case, a privileged user having an operation right can start a collaboration by issuing a collaboration start command according to his / her own intention while confirming the login state of another session participant. The SBC clients 6B and 6C also wait until a collaboration start command is issued by a privileged user without waiting for the participation of all the clients scheduled to participate. Furthermore, it is also possible to adopt a configuration in which a privileged user having an operation right permits or disallows the participation of new users belonging to the group.
[0087]
As a processing sequence, after starting a session, an SBC client 6D (not shown) that requests 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. If it is during a session, the current privileged user is confirmed with the collaboration operation right management unit 33, and a collaboration participation request request is transmitted to the SBC client 6A which is a privileged user. The SBC client 6A receives the participation request, and the collaboration participation request screen shown in FIG. 12A, for example, is displayed on the SBC collaboration assistant 7A.
[0088]
The privileged user clicks the allow button 81 or the reject button 82 on the collaboration participation request screen, thereby permitting or not permitting user participation during the session. In the case of disapproval, the collaboration session management unit 32 of the proxy server 10 transmits a disapproval notice to the SBC client 6D that has requested participation. For example, a collaboration participation refusal screen shown in FIG. 12B is displayed on the SBC collaboration assistant 7D of the SBC client 6D.
[0089]
When session participation 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 transmits the current full screen information to the proxy server 10. The SBC browser screen distribution unit 21 of the proxy server 10 distributes the entire screen information to the SBC client 6D that is permitted to participate in the session, 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 assistants 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 “view: Maeda (192.168.10.4)” is added to the participant list screen 52, and the participation of the SBC client 6D is displayed along with the time in the session history of the message display screen 53.
[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) can be considered. In the latter case, for example, by right-clicking on the screen of the SBC client 6, the collaboration cancellation menu is displayed and selected.
[0092]
When the proxy server 10 receives the session cancel 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, collaboration can be continued from the state of the application when disconnected.
[0093]
In the above-described embodiment, the user ID of the privileged user is used for connection from the proxy server 10 to the SBC server 3. However, in the proxy server 10, a unique user ID is associated with the application 1 on the SBC server 3. And a password may be stored.
[0094]
The SBC collaboration system β can be applied to arbitrary fields such as education, medical care, design, and architecture. In any case, it is only necessary to prepare the SBC client 6 having a display function and a simple input device at the site where the cooperative work is performed. A high-load application is executed in the SBC server 3, and the proxy server 10 distributes the execution screen to all SBC clients participating in the session in real time. Further, since the location and change of the session history and 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 auxiliary unit 7 used in the present invention to such an SBC browser function, SBC collaboration using any application in the SBC server 3 remotely becomes possible.
[0096]
The processing operation of the SBC collaboration assistant 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 assistant unit 7 is realized by software, the SBC collaboration assistant program may be recorded and distributed on any computer-readable recording medium, or may be distributed from the proxy server 10 to the SBC client via the network 4. You may distribute.
[0097]
The SBC collaboration auxiliary program installed in the SBC client includes the following procedure.
(A) When the proxy server grants the operation right of the application to the first SBC client, the location of the operation right is displayed on the SBC client
(B) When the first SBC client executes an application on the SBC server, the SBC client displays an execution screen transmitted via the proxy server.
(C) When the second SBC client acquires the operation right of the application, the transfer of the operation right is displayed on the SBC client.
[0098]
The SBC collaboration assistance program further includes a procedure for causing the SBC client to request acquisition of an operation right as necessary.
[0099]
By simply introducing a collaboration assistance program into an existing SBC client terminal, a collaborative work can be performed using an arbitrary application in a remote SBC server.
[0100]
When 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 procedures.
(A) The proxy server is given an operation right for 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 is caused to transfer the first input operation information to the SBC server.
(C) When the execution screen of the application is received 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】
According to the present invention, it becomes possible to share an application in the SBC server and perform cooperative work among a plurality of SBC clients while using the existing SBC middleware.
[0103]
During collaboration, only the screen update information that accompanies the execution of the application is replicated and distributed, resulting in excellent responsiveness.
[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, and shows a network configuration including a proxy server that enables sharing of applications on the SBC server and collaboration work among a plurality of SBC clients. FIG.
FIG. 3 is a block configuration diagram of a proxy server used in the system of FIG. 2;
FIG. 4 is a diagram illustrating 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 the operation of the system at the start of SBC collaboration.
FIG. 7 is a diagram illustrating an example of a collaboration start confirmation screen.
FIG. 8 is a diagram for explaining the operation of the system when an SBC screen is output in SBC collaboration.
FIG. 9 is a diagram illustrating a processing sequence for transferring an application operation right.
FIG. 10 is a diagram for explaining the operation of the system when an operation right is transferred.
FIG. 11 is a diagram illustrating an example of an operation right transfer request screen and an operation right transfer rejection screen.
FIG. 12 is a diagram illustrating 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 for proxy input reception
10 Proxy server
11 Operation Information Processing Unit
12 Collaboration control unit
15 Client input reception
16 Server input reception part
18 Client information database
21 SBC browser screen distribution unit (execution screen distribution unit)
22 Copying Department
25 Operation information relay part
26 Packet judgment part
27 Packet transmitter
28 Operation information discard unit
31 Collaboration User Authentication Department
32 Collaboration Session Management Department
33 Collaboration Operation Rights Management Department
41 SBC collaboration browser
42 Session information display area
43 Active control unit
52 Participant List Screen
53 Message display screen
54 Operation right acquisition request button

Claims (14)

An SBC server having SBC middleware capable of installing any application;
A plurality of SBC clients belonging to one session group of a plurality of session groups connected to the SBC server via a network and capable of remotely cooperating and using the application;
A proxy server that is arranged in an arbitrary area on the network and connects between the SBC server and the plurality of SBC clients;
An input receiving unit that receives a session connection request from any SBC client belonging to the one session group;
When a privileged user ID indicating which SBC client is set with a single operation right that allows execution of the application for each session group is received and the session connection request is received , An operation right management unit that sets a user ID indicating a predetermined first SBC client in the session group as a privileged user ID ;
An operation information relay unit for transferring the first input operation information to the SBC server when the input receiving unit receives the first input operation information for executing the application from the first SBC client; An operation screen distribution unit that receives an execution screen of an application based on the transferred input operation information from the SBC server, and distributes the execution screen to a plurality of SBC clients configuring the one session group;
The operation right management unit of the proxy server includes the first SBC client when the input reception unit receives an operation right acquisition request from any second SBC client in the first session group. An SBC collaboration system, characterized in that a message for inquiring whether or not to grant the operation right is transmitted.   2. The SBC collaboration system according to claim 1, wherein the operation screen distribution unit includes a duplication unit that duplicates an application execution screen by the number of a plurality of SBC clients configuring the one session group. The operation information relay unit is
Whether identification information is extracted from the input operation information received via the input receiving unit, and the input operation information is transmitted from the first SBC client having the operation right with reference to the operation right information. A determination unit for determining
The operation information discarding unit that discards the input operation information when the determination result is not transmitted from the first SBC client having the operation right. SBC collaboration system.   The SBC collaboration system according to claim 1, wherein the operation right management unit receives a response to the inquiry message from the first SBC client via the input reception unit. The operation right management unit sets a user ID indicating the second SBC client as a privileged user ID when receiving an operation right transfer permission notification from the first SBC client via the input receiving unit. The SBC collaboration system according to claim 4. An SBC server having an SBC middleware capable of installing an arbitrary application, and the application can be remotely and cooperatively belonged to one session group among a plurality of session groups connected to the SBC server via a network A proxy server inserted between a plurality of SBC clients,
An input receiving unit that receives a session connection request from any SBC client belonging to the one session group;
Holds a privileged user ID indicating to which SBC client in the first session group a single operation right that permits execution of the application is set to which SBC client, and receives the session connection request when the operation right management unit for setting a user ID indicating a predetermined first SBC client in the first session group as a privileged user ID,
An operation information relay unit for transferring the first input operation information to the SBC server when the input receiving unit receives the first input operation information for executing the application from the first SBC client; An operation screen distribution unit that receives an execution screen of an application based on the transferred input operation information from the SBC server, and distributes the execution screen to a plurality of SBC clients included in the one session group;
The operation right management unit includes the operation right management unit when the input reception unit receives an operation right acquisition request from any second SBC client in the first session group. A proxy server that transmits a message inquiring whether or not the transfer is permitted.   The proxy server according to claim 6, wherein the operation screen distribution unit includes a copy unit that copies the execution screen of the application by the number of a plurality of SBC clients that form the one session group. The operation information relay unit is
Whether identification information is extracted from the input operation information received via the input receiving unit, and the input operation information is transmitted from the first SBC client having the operation right with reference to the operation right information. A determination unit for determining
The proxy server according to claim 6, further comprising: a discard unit that discards the received operation information when the determination unit determines that the input operation information is not the first input operation information.   The operation information relay unit further includes a transmission unit that transfers the received operation information to the SBC server when the determination unit determines that the received operation information is the first input operation information. The proxy server according to claim 8.   The proxy server according to claim 6, wherein the operation right management unit receives a response corresponding to the inquiry message from the first SBC client via the input reception unit. The operation right management unit sets a user ID indicating the second SBC client as a privileged user ID when receiving an operation right transfer permission notification from the first SBC client via the input receiving unit. The proxy server according to claim 10. An SBC server having an SBC middleware capable of installing an arbitrary application, and the application can be remotely and cooperatively belonged to one session group among a plurality of session groups connected to the SBC server via a network A proxy server between multiple SBC clients,
Wherein the proxy server, and stores the privileged user ID that indicates a single operation right is set to allow execution of the application in any of the SBC client for each of the session group,
The proxy server receives a session connection request from any SBC client belonging to the one session group,
When the session connection request is received , a user ID indicating a predetermined first SBC client in the first session group is set as a privileged user ID ,
In the proxy server, when the first input operation information for executing the application is received from the first SBC client, the first input operation information is relayed to the SBC server and transmitted to the SBC server. Run the application
In the proxy server, the execution screen of the application is received from the SBC server,
In the proxy server, the received execution screen is duplicated, and the duplicated execution screen is transmitted to a plurality of SBC clients belonging to the one session group,
In the proxy server, when an operation right acquisition request is received from an arbitrary second SBC client belonging to the one session group, a message is sent to the first SBC client as to whether or not the transfer of the operation right is permitted. And
When receiving a notification permitting transfer of the operation right from the first SBC client, the proxy server changes the privileged user ID from the user ID indicating the first SBC client to the second SBC client. The SBC collaboration method, wherein the setting is changed to a user ID indicating   In the proxy server, when receiving the second input operation information from the second SBC client before updating the operation right information and changing the setting of the operation right to the second SBC client, The SBC collaboration method according to claim 12, wherein the second input operation information is discarded. An SBC server having an SBC middleware capable of installing an arbitrary application, and the application can be remotely and cooperatively belonged to one session group among a plurality of session groups connected to the SBC server via a network An SBC collaboration processing program executed by a proxy server inserted between a plurality of SBC clients,
Causing the proxy server to receive a session connection request from any SBC client belonging to the session group;
When the session connection request is received , the proxy server is caused to update the privileged user ID of the proxy server, and a user ID indicating a predetermined first SBC client in the first session group is assigned to the privileged user ID. A procedure for setting as a user ID ;
A step of causing the proxy server to relay the first input operation information to the SBC server when the proxy server receives first input operation information for executing the application from the first SBC client; ,
A procedure for causing the proxy server to receive an execution screen of the application from the SBC server and distributing the execution screen to a plurality of SBC clients belonging to the session group;
A procedure for causing the proxy server to receive an operation right acquisition request from an arbitrary second SBC client belonging to the one session group;
When receiving the operation right acquisition request, the proxy server, a procedure for transmitting a message inquiring whether to permit operation right transfer to the first SBC client,
In the proxy server, when a notification permitting transfer of the operation right is received from the first SBC client, the privileged user ID is indicated from the user ID indicating the first SBC client to indicate the second SBC client. An SBC collaboration processing program characterized in that setting is changed to a user ID .

Images