JP2010224771A - System, method and apparatus for processing information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing system, an information processing method and an information processing apparatus for flexibly setting the operation authority of a general user without increasing the workload of a host user in a virtual operation space where a plurality of users can perform simultaneous operations. <P>SOLUTION: A work space management part 110 of a server device SRV generates data 125 for a client from workspace data 124 stored by a data storage part 120 by referring to updated operation restriction information 123 stored by the data storage part 120 (step ST 26). In a command menu MBT on a work space displayed by an output device 6 of each of client devices CL1 and CL2, active display of all buttons 302, 304, 306, and 308 are carried out so as to be selected. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an information processing system, an information processing method, and an information processing apparatus that provide a virtual work space in which a plurality of users can work simultaneously.

  In recent years, a virtual work space (hereinafter also referred to as “work space”) capable of simultaneous work by a plurality of users has been proposed. This workspace is typically a virtual space similar to a virtual whiteboard, and each user also refers to materials such as handwritten characters, images, and photographs (hereinafter also referred to as “objects”). ) Can be interactively entered and manipulated. By using such a workspace, intellectual creation work (thinking ideas and communicating with other members) by individuals or groups is promoted.

  For example, Japanese Patent Laid-Open No. 11-025021 (Patent Document 1) discloses a virtual space communication system in which other users can always participate in a virtual space in the latest state.

  By the way, as an example of the work form in such a workspace, the operation authority given to the user who participates in the workspace is changed in stages, and the operable range corresponding to each operation authority is set in advance. It is assumed to be left. Typically, a higher-level user who has been given a higher operating authority and other general users are set, and only a higher-level user can be selected for specific items among the operation items provided on the workspace. Can be operated. For example, an operation that uses an external service (such as translation work or OCR processing of a document image) that generates a cost can be executed only by a higher-level user.

  As a technique related to such an operation authority, Japanese Patent Application Laid-Open No. 11-025021 (Patent Document 1) discloses a configuration in which a change in the state of an object is permitted only to a person who has the authority to change the object. Japanese Patent Laying-Open No. 2006-293486 (Patent Document 2) discloses an information processing apparatus that controls access to data for which access is restricted based on the access rights of each user. Furthermore, Japanese Patent Application Laid-Open No. 2007-188490 (Patent Document 3) discloses a system and method for conveniently sharing an electronic document with restricted use such as an electronic document with restricted access or a confidential electronic document.

Japanese Patent Laid-Open No. 11-025021 JP 2006-293486 A JP 2007-188490 A

  On the other hand, from the viewpoint of improving work efficiency and the like, there is a need for a general user to temporarily operate items that can be operated only by a higher-level user. In the system as described above, there are (1) a method in which a higher-level user approves each time in response to a request from a general user, and (2) a higher-level user who is a general user. A method of alleviating the operation authority in advance for all or a part of the above is conceivable. In the former case, there is a problem that operations such as setting change by an administrator increase. In the latter case, there is a problem that an unintended general user performs an operation, or a higher-level user forgets an operation to restore the operation authority.

  Therefore, the present invention has been made to solve such a problem, and the purpose of the present invention is a general user in a virtual work space where a plurality of users can work simultaneously without increasing the work amount of the upper user. Is to provide an information processing system, an information processing method, and an information processing apparatus that can flexibly set the operation authority.

  According to an aspect of the present invention, an information processing system that provides a virtual work space in which a plurality of users can work simultaneously is provided. The information processing system includes server means, a plurality of display means each for displaying a virtual work space, and a plurality of input means respectively associated with the plurality of display means. The server means includes a user registration means for registering a user who can participate in the virtual work space in association with an operation authority in the virtual work space given to the user, and a state management means for acquiring the participation state of the user in the virtual work space. And an operation authority management means that provides an operation according to the operation authority of the user so as to be executable for the user participating in the virtual work space. The operation authority management means is configured such that when a first user who is given an operation authority and a second user whose operation authority is limited by the first user are participating in the virtual workspace, the second user On the other hand, an operation according to an operation authority wider than that of the second user is provided to be executable.

  Preferably, when the first user leaves the virtual work space, the operation authority management unit returns the operation provided to the second user so as to be executable within a range corresponding to the operation authority of the second user.

  More preferably, the operation authority management means responds to the operation authority of the second user after the predetermined time has elapsed after the first user leaves the virtual workspace according to the operation authority of the second user. Return to range.

  Preferably, the server means further includes definition data management means for holding definition data for providing a virtual work space and an object existing in the virtual work space, and reflecting an operation performed by the user in the definition data. The operation authority management means generates client data for displaying the virtual workspace on the display means corresponding to the user from the definition data according to the operation authority of the user participating in the virtual workspace.

  More preferably, in the definition data, operation items that can be provided to the user are defined in association with the operation authority necessary for the execution. The operation authority management means is an operation item that is not permitted to be executed with the operation authority of the second user when the first and second users participate in the virtual work space, and the operation of the first user Operation items that are permitted to be executed by the authority are provided to the second user so as to be executable.

  Alternatively, more preferably, the definition data defines an operation authority necessary for performing an operation on the object in association with the definition of the object existing in the virtual work space. The operation authority management means is an object that cannot be operated with the operation authority of the second user with respect to the second user when the first and second users participate in the virtual workspace. In addition, objects that can be operated with the operation authority of the first user are displayed in an operable manner.

  Preferably, the server means further includes group registration means for registering a group of one or more users who can participate in the virtual work space. The operation authority management means can execute an operation according to an operation authority wider than the second operation authority for the second user only when the first and second users belong to the same group. To provide.

  According to another aspect of the present invention, an information processing method is provided that provides a virtual work space in which a plurality of users can work simultaneously. In the information processing method, the server device registers a user who can participate in the virtual work space in association with the operation authority in the virtual work space given to the user, and the server device stores the user in the virtual work space. A step of acquiring a participation state, and a step of providing the server device so that an operation according to the operation authority of the user can be executed for the user participating in the virtual work space. The step of providing the operation in an executable manner is performed when a first user who is given an operation authority and a second user whose operation authority is limited by the first user are participating in the virtual workspace. A step of providing an operation corresponding to an operation authority wider than that of the second user so as to be executable.

  According to still another aspect of the present invention, there is provided an information processing apparatus that provides a virtual work space in which a plurality of users can work simultaneously in a plurality of terminals connected so as to be capable of data communication. The information processing apparatus includes a user registration unit that registers a user who can participate in the virtual work space in association with an operation authority in the virtual work space given to the user, and a state in which the user participation state in the virtual work space is acquired. A management unit and an operation authority management unit that provides a user participating in the virtual work space in an executable manner according to the operation authority of the user. The operation authority management means is configured such that when a first user who is given an operation authority and a second user whose operation authority is limited by the first user are participating in the virtual workspace, the second user On the other hand, an operation according to an operation authority wider than that of the second user is provided to be executable.

  According to the present invention, it is possible to flexibly set the operation authority of a general user without increasing the work amount of a higher-level user in a virtual work space in which a plurality of users can work simultaneously.

It is a schematic block diagram of the information processing system for providing the work space according to embodiment of this invention. It is a schematic diagram showing a schematic hardware configuration of a personal computer that is a representative example of the information processing apparatus according to the embodiment of the present invention. It is a block diagram which shows the general | schematic control structure of the server apparatus according to embodiment of this invention. It is a block diagram which shows the general | schematic control structure of the client apparatus according to embodiment of this invention. It is a schematic diagram which shows a process in case a general user logs in to a workspace in the situation where the high-order user is not logged into the workspace in the information processing system according to the embodiment of the present invention. It is a figure which shows an example of the user management data according to embodiment of this invention. It is a figure which shows an example of the participation status information according to embodiment of this invention. It is a figure which shows an example of the operation restriction information according to embodiment of this invention. It is a figure which shows the relationship between the authority level of the user who is logging in to the workspace, and the value of the restriction level set. It is a figure which shows an example of the work space data according to embodiment of this invention. It is a figure which shows an example of the data for clients according to embodiment of this invention. It is a figure which shows the relationship between the permission level provided to each command of workspace data, and the restriction | limiting level set to each user of operation restriction information, and the value of an executable level. It is a schematic diagram which shows a process when a high-order user logs in to a workspace in the condition where the general user is logging in to the workspace in the information processing system according to the embodiment of the present invention. It is a figure which shows an example of the participation status information after having been updated in step ST24 shown in FIG. It is a figure which shows an example of the operation restriction information after it updated in step ST25 shown in FIG. It is a figure which shows an example of the data for clients produced | generated in step ST26 shown in FIG. It is a schematic diagram which shows a process when a high-order user logs out (leaves) from a workspace in the situation where the high-order user and the general user are logging in to the workspace in the information processing system according to the embodiment of the present invention. It is a flowchart which shows the process sequence in the server apparatus according to embodiment of this invention. It is a figure which shows an example of the workspace data according to the modification 1 of embodiment of this invention. It is a figure which shows an example of the data for clients according to the modification 1 of embodiment of this invention. It is a figure which shows the relationship between the permission level provided to each object of the workspace data according to the modification 1 of embodiment of this invention, and the value of the executable level in client data. It is a figure which shows an example of the user management data according to the modification 3 of embodiment of this invention. It is a figure which shows the influence range of the restriction | limiting level in the registration setting condition of the user management data shown in FIG. It is a figure which shows an example of the user management data according to the modification 3 of embodiment of this invention. It is a figure which shows the influence range of the restriction | limiting level in the registration setting condition of the user management data shown in FIG.

  Embodiments of the present invention will be described in detail with reference to the drawings. Note that the same or corresponding parts in the drawings are denoted by the same reference numerals and description thereof will not be repeated.

[Definition of terms]
In this embodiment, “work space” means a virtual work space provided on an information processing apparatus and capable of adding or editing a visually recognizable object and capable of simultaneous work by a plurality of users. To do.

  In the present embodiment, “object” means general data that can be generated or added to a workspace. Examples of this object include graphics, text documents, worksheet cells, images, audio, logs, tags, bookmarks, annotations, user information, and the like.

  In the present embodiment, for convenience of explanation, the user is classified into “upper user” and “general user” according to the difference in the operation authority. That is, the “upper user” can log in to the target workspace and perform various operations on the target workspace (typically, creation, deletion, modification of objects, saving and reading of the workspace itself, etc.). Means a user who can perform On the other hand, the “general user” can log in to the target workspace and can perform operations on the workspace, but the operable range is more limited than the upper user's operable range. Means user.

  In the user registration, it is not always necessary to clearly distinguish between “upper user” and “general user”. That is, the terms “upper user” and “general user” are terms for distinguishing users according to their relative operational authority differences. Therefore, it is possible to operate even among a plurality of users who are regarded as “higher users” for all “general users” (or “general users” for all “higher users”). The range may be different.

[overall structure]
FIG. 1 is a schematic configuration diagram of an information processing system for providing a work space according to an embodiment of the present invention.

  Referring to FIG. 1, the information processing system according to the present embodiment is a plurality of information processing apparatuses connected to each other via a network NW (typically Ethernet (registered trademark)) so as to be able to perform data communication. A plurality of client devices CL1 to CLN (hereinafter also collectively referred to as “client device CL”) and a server device SRV are included. That is, in the present embodiment, a configuration that realizes an information processing system according to the present embodiment by using a so-called server client configuration is illustrated. Note that the information processing system according to the present embodiment may be realized by a so-called peer-to-peer configuration. When the peer-to-peer configuration is adopted, a function substantially equal to the function provided by the server SRV is mounted on at least one terminal side.

  Although not shown, a hub, router, or the like that is a data relay device is appropriately arranged on the network NW. Further, the network NW may include not only a LAN (Local Area Network) but also a WAN (Wide Area Network) such as the Internet.

  The server SRV holds information for providing a workspace (“workspace data” to be described later), and provides it to the client devices CL1 to CLN. In addition, the content that the user performs some operation on each of the client devices CL1 to CLN is reflected in the work space data held by the server device SRV as needed. For example, when a user adds some object on the workspace on any client device CL, information describing the added object is transmitted from the client device CL to the server device SRV, and the server device SRV Based on the information, the work space data held by the own device is updated, and information for displaying the work space on the client devices CL1 to CLN is transmitted based on the updated work space data. In this way, in any of the client devices CL1 to CLN, a substantially equivalent work space is provided, thereby sharing information among users.

  Further, the server SRV can communicate with an external device that is a request destination of an external service described later.

[Hardware configuration]
FIG. 2 is a schematic diagram showing a schematic hardware configuration of a personal computer which is a representative example of the information processing apparatus according to the embodiment of the present invention.

  Referring to FIG. 2, server SRV, which is an information processing apparatus according to the present embodiment, temporarily stores CPU 2 that executes various programs including an operating system, and data necessary for execution of the program by CPU 2. A memory 14 as a storage unit and a hard disk (HDD) 12 that stores a program executed by the CPU 2 in a nonvolatile manner are included. Such a program is read from a CD-ROM 16a or a flexible disk 18a by a CD-ROM (Compact Disk-Read Only Memory) drive 16 or a flexible disk (FDD) drive 18, respectively.

  The CPU 2 receives a user operation request via the input device 10 including a keyboard, a mouse, a tablet, and the like, and outputs screen data generated by executing the program to the output device 6.

  The output device 6 is a device for displaying the state of the workspace to the user, and typically includes a monitor or a projector.

  The CPU 2 performs data communication with the client device CL via the communication interface 8 including a LAN card. These parts are connected to each other via the internal bus 4.

  Further, client device CL according to the present embodiment is also an information processing device, and the hardware configuration thereof is the same as the hardware configuration of server device SRV shown in FIG. 2, and therefore detailed description thereof will not be repeated.

[Outline of processing]
In the information processing system according to the present embodiment, the operation authority of each user who participates (logs in) the workspace can be set independently. In the information processing system according to the present embodiment, as a general rule, if the upper user can manage the general user, the general user is given the operation authority equivalent to the operation authority given to the upper user. It is done. More specifically, as long as any higher-level user is participating (logged in) in the workspace, all or part of the operation authority given to the higher-level logged-in user can be transferred to the same workspace at the same time. This is for general users who are logged in.

  Typically, considering the case of performing intellectual creation work in a certain group, the leader of the group becomes the “upper user” and the other members become “general users”. And while the leader is logged into the workspace, the operations of the members of the group can be managed, so as long as the operation authority given to the members is equal to or Part of it is given temporarily. That is, as long as it is considered that the general user can grasp the operation content of the general user, the operation authority is assigned. As a result, for example, another member can act on behalf of all or part of the work of the leader, or the member can perform more advanced work. Thereby, working efficiency can be improved.

  Further, when the upper user leaves (logs out) from the workspace, the authority of the upper user given to the general user is lost. That is, the general user can only perform operations within the range of operation authority given to him. Therefore, it is possible to avoid an operation that is not intended by a general user outside the management of the upper user.

  Items that can only be operated by the upper level users include paid external services such as translation work, OCR processing of document images, company surveys, color printing with relatively high printing costs, and access to external networks. Is done. In addition to these, items such as new user invitations, browsing confidential documents, and connecting to other devices are also assumed.

[Control structure]
Next, referring to FIG. 3 and FIG. 4, the control structure of server device SRV and client device CL constituting the information processing system according to the present embodiment will be described. FIG. 3 is a block diagram showing a schematic control structure of server SRV according to the embodiment of the present invention. FIG. 4 is a block diagram showing a schematic control structure of client device CL according to the embodiment of the present invention.

  Referring to FIG. 3, server SRV includes a workspace management unit 110, a client management unit 112, a data transmission / reception unit 114, and a data storage unit 120 as a control structure. Typically, the workspace management unit 110 and the client management unit 112 are executed after the CPU 2 (FIG. 2) develops a program stored in advance in the hard disk 12 (FIG. 2) or the like in the memory 14 (FIG. 2). To be provided. The data storage unit 120 is provided as a part of the HDD 12. Further, the data transmission / reception unit 114 is provided in cooperation with the communication interface 8 (FIG. 2) and a driver application related thereto.

  The data storage unit 120 holds user management data 121, participation state information 122, operation restriction information 123, work space data 124, and client data 125. These data are typically held as files. However, since the participation state information 122 includes information indicating the login status of the user at each time point as will be described later, it is preferable to hold the participation state information 122 in a format that can be easily updated.

  In the user management data 121, an account that can log in to the workspace, an operation authority associated with each account, and the like are recorded. That is, in the user management data 121, users who can participate in the workspace are registered in association with the operation authority in the workspace given to the user. In the user management data 121, a password may be further recorded.

  In the participation status information 122, the participation status (typically during login / logout) of each user managed by the server SRV is recorded.

  In the operation restriction information 123, the operation authority given to the user who is logged in to the workspace managed by the server SRV is recorded.

  The workspace data 124 is definition data for providing a workspace and an object existing in the workspace. The workspace data 124 includes information for displaying a user interface on the workspace. That is, in the workspace data 124, operation items that can be provided to the user are defined in association with the operation authority necessary for the execution.

  The client data 125 is definition data for drawing a work space on the output device 6 (FIG. 2) of the client device CL. In order to make it possible to change the operation items to be provided according to the operation authority of the destination user, a plurality of client data 125 for each user (client device CL) logged in to the workspace. May be generated. The client data 125 may be once generated and then deleted after being transmitted to the destination client device CL.

  The data transmission / reception unit 114 selectively receives a packet destined for the own apparatus among packets flowing on the network NW. Then, the data transmission / reception unit 114 extracts necessary data from the received packet, and filters whether the information is necessary for the server SRV. If the extracted data is information necessary for the server SRV and is a processing command for a work space related to the server SRV, the data transmission / reception unit 114 transmits the extracted data to the work space management unit 110. On the other hand, if the extracted data is information necessary for the server SRV and is a processing command related to a user such as login to the server SRV, the extracted data is transmitted to the client management unit 112.

  Note that the data transmitter / receiver 114 holds information related to the client device CL (for example, unique destination information such as an IP address for specifying a transmission destination, logged-in user information, and the like). When the data transmission / reception unit 114 receives a data transmission request from the workspace management unit 110 or the client management unit 112, the data transmission / reception unit 114 generates a packet based on the information held by the data transmission / reception unit 114 and the target client device Send to CL.

  The client management unit 112 mainly manages users who log in to the workspace. More specifically, the client management unit 112 includes a registration / deletion unit 116, a participation state management unit 117, and an operation restriction management unit 118.

  The registration / deletion unit 116 manages users (user accounts) who can log in to the workspace. More specifically, the registration / deletion unit 116 updates the contents of the user management data 121 held by the data storage unit 120 when the user is instructed to add, change, delete, and the operation restriction information 123. Also update the corresponding description.

  The participation state management unit 117 refers to the user management data 121 in response to a processing command related to login from any of the client devices CL, and determines whether or not login is permitted. In addition, the participation state management unit 117 updates the participation state information 122 according to the login state of the user with respect to the workspace to be managed periodically or at some event occurrence timing.

  The operation restriction management unit 118 changes the operation authority given to the user who is logged in to the workspace according to the participation status of the user. More specifically, the operation restriction management unit 118 refers to the user management data 121 and the participation state information 122 and changes the operation authority of the general user as necessary. That is, the operation restriction management unit 118 updates the contents of the operation restriction information 123 so as to change the operation authority of the general user according to the login status of the upper user in the workspace.

  The workspace management unit 110 updates the workspace data 124 and the client data 125 held by the data storage unit 120 in response to a processing command for the workspace from the client device CL. That is, the workspace management unit 110 reflects the operation performed by the user in the workspace data 124. Further, the work space management unit 110 transmits client data 125 to the client device CL to draw the work space on each output device 6 (FIG. 2). More specifically, the workspace management unit 110 has a registration function, an output function, a deletion function, a read function, a storage function, and a data creation function.

  The registration function, output function, and deletion function of the workspace management unit 110 are the workspace data held by the data storage unit 120 in response to a processing command corresponding to the content operated by the user on the logged-in client device CL. 124 is for registering new data, deleting existing data, updating existing data, and the like. The read function and the save function of the workspace management unit 110 are for reading various data to be stored in the data storage unit 120 from different storage areas or writing to the storage areas. The output function of the workspace management unit 110 includes the operation restriction information 123 and the work stored in the data storage unit 120 for the client data 125 to be transmitted to each client device CL logged in the workspace. It is for generating based on the space data 124.

  Referring to FIG. 4, client device CL includes a workspace management unit 140, a drawing unit 142, a data transmission / reception unit 144, and a data storage unit 150 as a control structure. Typically, the work space management unit 140 and the drawing unit 142 are executed by the CPU 2 (FIG. 2) developing a program stored in advance in the hard disk 12 (FIG. 2) or the like in the memory 14 (FIG. 2). Provided in. The data storage unit 150 is provided as a part of the HDD 12. In addition, the data transmission / reception unit 144 is provided in cooperation with the communication interface 8 (FIG. 2) and the associated driver application.

  The data transmission / reception unit 144 selectively receives packets destined for the own apparatus among packets flowing on the network NW. Then, the data transmitting / receiving unit 144 extracts necessary data from the received packet, and filters whether the information is necessary for the own device. If the extracted data is information necessary for the own device and is a processing command related to the own device, the data transmission / reception unit 144 transmits the extracted data to the work space management unit 140.

  Note that the data transmission / reception unit 144 holds information about the server SRV and other client devices CL (for example, unique destination information for specifying a transmission destination such as an IP address). When receiving a data transmission request from the work space management unit 140, the data transmission / reception unit 144 generates a packet based on the information held therein and sends the packet to the server SRV or the like.

  Upon receiving the client data 125 from the server SRV, the workspace management unit 140 temporarily stores it in the data storage unit 150 and displays the workspace based on the stored client data 125. Data for transmission is transmitted to the drawing unit 142. In addition, when the logged-in user operates input device 10 and performs some operation in the workspace, workspace management unit 140 transmits data indicating the operation content to server SRV. More specifically, the workspace management unit 140 has a user interface function, an output function, a deletion function, a reading function, an input function, and a storage function.

  The user interface function of the workspace management unit 140 is for displaying user interfaces such as various dialogs on the output device 6. More specifically, as a user interface function of the workspace management unit 140, the contents of the dialog to be displayed are changed based on the description contents of the received client data 125, as will be described later. The output function of the workspace management unit 140 is for outputting data for displaying the workspace based on the client data 125 stored in the data storage unit 150. The deletion function of the workspace management unit 140 is used to delete the client data 125 stored in the data storage unit 150 after the user who has logged in to the device logs out (leaves the workspace). Is. The read function and the save function of the workspace management unit 140 store the client data 125 received from the server SRV in the data storage unit 150 or read out the client data 125 stored in the data storage unit 150. Is for. The input function of the workspace management unit 140 is for generating a processing command indicating an operation on the workspace in response to a user operation logged in to the own device.

  The drawing unit 142 performs rendering (drawing process) to display the workspace on the output device 6 based on the data from the workspace management unit 140. The rendering result is stored in a display graphic memory (not shown). The contents stored in the drawing graphic memory are reflected and output to the output device 6.

  The workspace management unit 140 temporarily saves the contents of the operation of the input device 10 by the user in the data storage unit 150, and then outputs a control command to the drawing unit 142 and / or the server device SRV as necessary. The data transmission may be performed. For example, information indicating an operation on a GUI (Graphical User Interface) provided by an operating system executed on each client device CL is output to the drawing unit 142 without being transmitted to the server device SRV, The screen display on the output device 6 is updated.

  As described above, the operation content on the workspace performed by the user on a certain client device CL is transmitted to the server device SRV through the data transmission / reception unit 144. When the server SRV receives this operation content, the server SRV updates the work space data 124 held by the data storage unit 120 of the own device and also updates the client data 125. Furthermore, the server SRV transmits the updated client data 125 to the client CL. Then, in each client device CL, a work space reflecting the operation content performed by the certain user is displayed. Through such a series of processes, a synchronized work space is provided between the client apparatuses CL.

[Overall procedure]
Hereinafter, a processing procedure in the information processing system according to the present embodiment will be described. In order to make understanding easier, (1) Processing when a general user logs in to a workspace in a situation where a higher-level user is not logged in to the workspace, (2) A general user is logged in to the workspace Processing when the upper user logs in to the workspace in the situation, (3) Processing when the upper user logs out (leaves) from the workspace when the upper user and the general user are logged in to the workspace, Each of the three situations will be described.

<1. Processing when a general user logs in to a workspace when a higher-level user is not logged in to the workspace>
FIG. 5 is a schematic diagram showing processing when a general user logs in to the workspace in a situation where the upper user is not logged in to the workspace in the information processing system according to the embodiment of the present invention. The login name of the upper user is “user1”, and the login name of the general user is “user2”.

  Referring to FIG. 5, first, consider a case where a general user attempts to log in to the workspace using the client device CL2. In this case, the general user operates the input device 10 of the client device CL2 to input identification information such as a login name and a password assigned to the user (step ST11).

  Then, the workspace management unit 140 (FIG. 4) of the client device CL2 transmits a login request to the workspace to the server SRV through the data transmission / reception unit 144 together with the input identification information of the general user ( Step ST12).

  In response to the login request from the client device CL2, the client management unit 112 of the server SRV refers to the user management data 121 held by the data storage unit 120 and is transmitted together with the login request (general user The log-in process for the log-in request is input (step ST13). More specifically, the client management unit 112 of the server SRV determines whether or not the received login name is registered in the user management data 121. Subsequently, when a login name is registered in the user management data 121, the client management unit 112 reads a password corresponding to the login name from a password holding unit (not shown) and receives it together with the login name ( It is determined whether or not it matches the password (entered by a general user). If it is determined that the passwords match, the general user is allowed to log in. On the other hand, if the login name is not registered in the user management data 121, or if the passwords do not match, the login is rejected. In this case, the client management unit 112 of the server apparatus SRV transmits a message to that effect to the client apparatus CL2.

  When the login is permitted, the client management unit 112 of the server SRV updates the contents of the participation state information 122 held by the data storage unit 120 (step ST14). More specifically, the client management unit 112 describes in the participation state information 122 information indicating that a general user is logged in to the workspace. Details of the participation state information 122 will be described later.

  Subsequently, the client management unit 112 of the server SRV refers to the user management data 121 and the participation state information 122 held by the data storage unit 120 and updates the contents of the operation restriction information 123 (step ST15). More specifically, the client management unit 112 determines the operation authority to be collectively granted to the target workspace according to the operation authority granted to each user who is logged in to the workspace. That is, an operation authority associated with the workspace described in the operation restriction information 123 is collectively given to a user who is logged in to a certain workspace. Details of the operation restriction information 123 will be described later.

  Subsequently, the work space management unit 110 of the server SRV refers to the updated operation restriction information 123 held by the data storage unit 120 and changes the client data 125 from the work space data 124 held by the data storage unit 120. Is generated (step ST16). As will be described later, the workspace data 124 includes tag information for displaying a command menu for accepting various operations on the workspace. Each of the tag information described in the workspace data 124 is set with an operation authority necessary for performing a corresponding operation. An operation that can be executed is dynamically determined by comparing the necessary operation authority with the operation authority granted to the workspace. In general, if a relatively high operation authority is given to the target workspace, a larger number of operation items corresponding to the tag information described in the workspace data 124 can be executed. It is described in the client data 125. On the other hand, if a relatively low operation authority is given to the target workspace, among the operation items corresponding to the tag information described in the workspace data 124, the executable items are more limited in the client. Is described in the data 125 for the client.

  Finally, the work space management unit 110 of the server SRV transmits the generated client data 125 to the client device CL2 through the data transmission / reception unit 114 (step ST17). Note that the client data 125 may be discarded after transmission to the client device CL2.

  Upon receiving the client data 125 from the server SRV, the work space management unit 140 of the client device CL2 saves the received client data 125 in the data storage unit 150 and draws the client data 125 into the drawing unit. 142. Then, the drawing unit 142 of the client device CL2 displays the workspace on the output device 6 (step ST18). A command menu MBT is displayed in the workspace displayed on the output device 6.

  The command menu MBT shown in FIG. 5 is, for example, an Open button 302 for opening an object, a Save button 304 for saving an object, an Invite button 306 for inviting a new user, and applying for a paid service. A Payservice button 308. In the example shown in FIG. 5, in the generation process of the client data 125 in step ST <b> 16 described above, a case where only a reading operation is permitted for a general user is shown. Therefore, in the command menu MBT, the Open button 302 is actively displayed so that it can be selected, while the remaining buttons 304, 306, and 308 are grayed out so that they cannot be selected.

  Through such a series of processes, a work space is provided to a general user who has logged into the client device CL2. Hereinafter, processing in each of the above steps will be described.

(User management data)
FIG. 6 shows an example of user management data 121 according to the embodiment of the present invention. As shown in FIG. 6, a markup language such as XML is typically used as a description format for defining the contents of the user management data 121 according to the present embodiment. By using such a markup language, the expandability of the system can be enhanced by freely setting tags (description surrounded by <> and </>).

  Referring to FIG. 6, user management data 121 defines users who can log in to the corresponding workspace in respective descriptions 203 enclosed by client tags 201 and 202 (<client> and </ client>). To do. The client tag 201 (<client>) has “id” as an attribute (property). The “id” attribute is identification information (a unique value in the information processing system) that identifies the corresponding user. 5 is assumed to be “1”, and the identification information of the general user shown in FIG. 5 is “2”.

  The description 203 includes a name tag 204 and an operation authority tag 205. The name tag 204 stores the login name assigned to the corresponding user, and the operation authority tag 205 stores the authority level assigned to the corresponding user. More specifically, when “0” is stored in the operation authority tag 205, it indicates that the operation authority is not given to the corresponding user, and when “1” is stored in the operation authority tag 205, Indicates that the user is authorized to operate.

  The contents of the user management data 121 are updated by the registration / deletion unit 116 (FIG. 4) of the client management unit 112.

  In step ST13 shown in FIG. 5, the client management unit 112 of the server SRV acquires the user name stored in the name tag 204 in response to the login request, and executes the login process.

(Participation status information)
FIG. 7 is a diagram showing an example of the participation state information 122 according to the embodiment of the present invention. As shown in FIG. 7, a markup language such as XML is also used for the contents of the participation state information 122 according to the present embodiment.

  Referring to FIG. 7, participation state information 122 is a user login to the corresponding workspace in each description 213 surrounded by workspace participation state tags 211 and 212 (<workspace_login> and </ workspace_login>). Define the state. The workspace participation state (workspace_login) tag 211 has “id” as an attribute (property). This “id” attribute is identification information (a unique value in the information processing system) that identifies the participation state information 122. This identification information is used to identify each of the plurality of participation state information 122 when there is a plurality of pieces of participation state information 122.

  The description 213 includes a target workspace (target_workspace) tag 214 and a client tag 215. The target workspace tag 214 stores identification information (a unique value in the information processing system) assigned to the target workspace. The client tag 215 stores identification information (id) that identifies the corresponding user, and the login status (status) of the corresponding user. In the identification information (id) for specifying the corresponding user, a value associated with the attribute value of the client tag 201 (FIG. 6) of the user management data 121 is stored. In the login status (status), either “1” indicating that the corresponding user is logging in or “0” indicating that the corresponding user is logging out is stored.

  In step ST14 shown in FIG. 5, the client management unit 112 of the server SRV changes the value of the login status (status) of the client tag 215 corresponding to the user name for which the login process has been successful.

(Operation restriction information)
FIG. 8 shows an example of the operation restriction information 123 according to the embodiment of the present invention. As shown in FIG. 8, a markup language such as XML is also used for the contents of the operation restriction information 123 according to the present embodiment.

  Referring to FIG. 8, the operation restriction information 123 indicates that the workspace operation right restriction tags 221 and 222 (<workspace_limit> and </ workspace_limit>) are respectively logged in the target workspace in the description 223. Define the operation authority granted to the user. The workspace operation right restriction (workspace_limit) tag 221 has “id” as an attribute (property). This “id” attribute is identification information (a unique value in the information processing system) that identifies the operation restriction information 123. This identification information is used to identify each of the plurality of operation restriction information 123 when there is a plurality of pieces of operation restriction information 123.

  The description 223 includes a target workspace (target_workspace) tag 224 and a client tag 225. The target workspace tag 224 stores identification information (a unique value in the information processing system) assigned to the target workspace. The client tag 225 stores identification information (id) that identifies the corresponding user and a restriction level (limitation) of the corresponding user. In the identification information (id) for specifying the corresponding user, a value associated with the attribute value of the client tag 201 (FIG. 6) of the user management data 121 is stored. The restriction level (limitation) is either “0” indicating that there is no restriction on the operation for the corresponding user, or “1” indicating that the operation for the corresponding user is restricted. Stored.

  In step ST15 shown in FIG. 5, the client management unit 112 of the server SRV indicates that the login status (status) of the client tags 215 recorded in the participation status information 122 is “1” (logged in). What is shown is extracted, and identification information (id) that is recorded in the extracted client tag 215 and that identifies the user is acquired. Then, the client management unit 112 includes the description 203 recorded in the user management data 121 that includes the identification information (id) that identifies the previously logged-in user. While specifying, the value (authority level) of the corresponding operation authority tag 205 is acquired. Further, the client management unit 112 acquires the highest authority level (the authority level maximum value) among the acquired authority levels for the logged-in user. Then, the restriction level corresponding to the highest authority level is set as the restriction level (limitation) for each user who is logged in to the workspace at that time.

  In the situation shown in FIG. 5, only the lower-level user (user2, id = “2”) is logged in to the workspace, and the authority level (authority) is “0” (no operation authority). (limitation) is set to “1” (with restrictions on the operation) (see FIG. 8).

  FIG. 9 shows the relationship between the authority level (authority) of the user who is logged in to the workspace and the limit level (limitation) value that is set. As shown in FIG. 9, the restriction level of each user is set according to the maximum authority level for the user who is logged in to the workspace.

(Workspace data)
FIG. 10 shows an example of workspace data 124 according to the embodiment of the present invention. As shown in FIG. 10, a markup language such as XML is also used for the contents of the workspace data 124 according to the present embodiment.

  Referring to FIG. 10, workspace data 124 defines an object on the workspace in a description 233 surrounded by workspace tags 231 and 232 (<workspace> and </ workspace>). The workspace tag 231 further includes a description 238 that is tag information for displaying a command menu.

  The workspace tag (workspace) 231 has “id” as an attribute (property). The “id” attribute is identification information (a unique value in the information processing system) that identifies the corresponding workspace.

  The description 233 includes object tags 234 and 235 (<object> and </ object>) corresponding to the objects, respectively. The object (object) tag 234 has “id” and “authorid” as attributes (properties). The “id” attribute is identification information (a unique value in the corresponding workspace) that identifies the corresponding object. The “authorid” attribute is identification information (a unique value in the information processing system) indicating the creator of the corresponding object.

  The object tag 234 includes an object name tag 236 and an object position tag 237. The object name (name) tag 236 is a name given to the corresponding object. The object position tag 237 is a display position of the corresponding object (typically defined by xy coordinate values).

  Each description 238 includes command tags 239 and 240 (<command> and </ command>) corresponding to the operation items provided in the workspace. The command tag 239 has “id” and “permission” as attributes (properties). The “id” attribute is identification information (a unique value in the corresponding workspace) that identifies the corresponding command. The “permission” attribute is a permission level indicating to which range of users the execution of the corresponding command is permitted. This permission level is set in advance by an administrator of the information processing system (or workspace) according to the present embodiment. As an example, the permission level (permission) is “0” indicating that execution of the corresponding command is not permitted, and “1” indicating that execution of the corresponding command is permitted only when the operation restriction is not set. ”And“ 2 ”indicating that the execution of the corresponding command is always permitted.

  The command tag 239 includes a command name tag 241. The command name (command) tag 241 is a name given to the corresponding command. In FIG. 10, as shown in the command menu MBT shown in FIG. 5, commands 1 to 4 correspond to the Open button 302, the Save button 304, the Invite button 306, and the Payservice button 308, respectively.

(Workspace data)
As described above, in step ST <b> 17 illustrated in FIG. 5, the work space management unit 110 of the server SRV generates client data 125 from the work space data 124. At this time, whether to execute a command corresponding to the operation item defined in the description 238 shown in FIG. 10 is determined based on the content of the operation restriction information 123.

  FIG. 11 shows an example of client data 125 according to the embodiment of the present invention. As shown in FIG. 11, a markup language such as XML is also used for the contents of the client data 125 according to the present embodiment.

  Comparing FIG. 10 with FIG. 11, in the client data 125 shown in FIG. 11, the command tag 239 shown in FIG. 10 is changed to the command tag 239 #. The command tag 239 # has “id” and “executable” as attributes (properties). The “id” attribute is identification information for identifying the corresponding command (a unique value in the corresponding workspace), and this value is the same as the value in the workspace data 124 shown in FIG. On the other hand, the “executable” attribute indicates the execution level of the corresponding command. That is, the “executable” attribute stores either “1” indicating that the corresponding command can be executed or “0” indicating that the corresponding command cannot be executed.

  In the situation shown in FIG. 5, only the lower-level user (user2, id = “2”) is logged in to the workspace. In this situation, the restriction level (limitation) corresponding to user2 is set in the operation restriction information 123. It is set to “1” (see FIG. 8). Therefore, among commands 1 to 4 shown in FIG. 10, execution is permitted for command 1 whose permission level (permission) is set to “2” (always allow command execution). On the other hand, execution is not permitted for commands 2 to 4 whose permission level (permission) is set to “1” (execution is permitted only when no operation restriction is set). As a result, in the command tag (command) 239 of the client data 125 shown in FIG. 11, only the executable level (executable) corresponding to command 1 is set to “1” (executable), and commands 2 to 4 are used. Is set to “0” (unexecutable).

  Finally, in step ST17 shown in FIG. 5, the client data 125 as shown in FIG. 11 is transmitted to the client device CL2, so that the command menu MBT as shown in FIG. 5 is displayed together with the work space. Is done.

  As described above, the client management unit 112 provides a user who participates in the workspace so that an operation according to the operation authority of the user can be executed.

  FIG. 12 shows the relationship between the permission level (permission) given to each command in the workspace data 124 and the restriction level (limitation) set for each user in the operation restriction information 123 and the executable level (executable) value. Indicates. As shown in FIG. 12, if the permission level (permission) is “2”, the executable level (executable) is always set to “1” (executable) regardless of the restriction level (limitation). If the permission level (permission) is “1”, the executable level (executable) is set to “1” (executable) or “0” (not executable) according to the restriction level (limitation). . Therefore, by dynamically changing the restriction level (limitation), it is possible to appropriately switch whether or not to execute a command whose permission level (permission) is initially set to “1”. Hereinafter, a procedure for changing the execution level (executable) of such a command in accordance with the login status of the upper user will be described.

<2. Processing when a general user logs in to the workspace while a general user logs in to the workspace>
FIG. 13 is a schematic diagram showing processing when a higher-level user logs in to a workspace in a situation where a general user is logged in to the workspace in the information processing system according to the embodiment of the present invention.

  Referring to FIG. 13, consider a case where a higher-level user attempts to log in to the workspace using the client device CL1. The upper user operates the input device 10 of the client device CL1 and inputs identification information such as a login name and a password assigned to the user (step ST21).

  Then, the work space management unit 140 (FIG. 4) of the client device CL1 transmits a log-in request to the work space to the server device SRV through the data transmission / reception unit 144 together with the inputted identification information of the upper user ( Step ST22).

  In response to the login request from the client device CL1, the client management unit 112 of the server SRV refers to the user management data 121 held by the data storage unit 120 and is transmitted together with the login request (the upper user The login process is executed in response to the login request (step ST23). More specifically, the client management unit 112 of the server SRV determines whether or not the received login name is registered in the user management data 121. Subsequently, when a login name is registered in the user management data 121, the client management unit 112 reads a password corresponding to the login name from a password holding unit (not shown) and receives it together with the login name ( It is determined whether or not the password matches the password entered by the upper user. If it is determined that the passwords match, the upper user is permitted to log in. On the other hand, if the login name is not registered in the user management data 121, or if the passwords do not match, the login is rejected. In this case, the client management unit 112 of the server apparatus SRV transmits a message to that effect to the client apparatus CL1.

  When the login is permitted, the client management unit 112 of the server SRV updates the contents of the participation state information 122 held by the data storage unit 120 (step ST24). More specifically, the client management unit 112 describes, in the participation state information 122, information indicating that the upper user is logging in to the workspace.

  FIG. 14 is a diagram showing an example of the participation state information 122 after being updated in step ST24 shown in FIG. Referring to FIG. 14, the client management unit 112 of the server SRV has the client assigned “1” to the identification information (id) corresponding to the upper user (user1) who has successfully logged in to the workspace. The tag 215 is extracted. Then, the client management unit 112 changes the value of the login state (status), which is the attribute value of the extracted client tag 215, from “0” (logged out) to “1” (logged in) (FIG. 14). (See “Changes”). Such update processing of the participation state information 122 indicates that the upper user is logged in to the workspace.

  Returning to FIG. 13, the client management unit 112 of the server SRV refers to the user management data 121 and the participation state information 122 held by the data storage unit 120 and updates the contents of the operation restriction information 123 (step ST25). ). That is, the client management unit 112 determines the operation authority to be collectively granted to the target workspace according to the operation authority given to the upper user and the general user who are logged in to the workspace. In the example shown in the present embodiment, as shown in the user management data 121 of FIG. 6 described above, the authority level (authority) of the upper user (user1) is “1” (with operation authority). Therefore, according to the correspondence shown in FIG. 9 described above, the restriction level (limitation) is set to “0” (no restriction on the operation).

  FIG. 15 is a diagram showing an example of the operation restriction information 123 after being updated in step ST25 shown in FIG. Referring to FIG. 15, the client management unit 112 of the server SRV has identification information (id) “1” corresponding to the upper user (user1) and the lower user (user2) who are logged in to the workspace. And client tag 225 to which “2” is assigned are extracted. The client management unit 112 changes the value of the restriction level (limitation), which is the attribute value of the extracted client tag 225, from “1” (operation is restricted) to “0” (operation is not restricted) ( (Refer to “Changed portion” in FIG. 15).

  Returning to FIG. 13, the workspace management unit 110 of the server SRV refers to the updated operation restriction information 123 (FIG. 15) held by the data storage unit 120, and the workspace data held by the data storage unit 120. Client data 125 is generated from 124 (step ST26). That is, the workspace management unit 110 compares the restriction level (limitation) set for each user in the operation restriction information 123 with the permission level (permission) of each command defined in the workspace data 124. , The executability level (executable) of each command is determined. In other words, the workspace management unit 110 determines the content of the client data 125 based on the operation restriction information 123 and the workspace data 124 according to the correspondence shown in FIG.

  FIG. 16 is a diagram showing an example of the client data 125 generated in step ST26 shown in FIG. In the example shown in the present embodiment, as shown in FIG. 16, the work space management unit 110 of the server SRV has “1” (executable) for each of the execution levels (executables) corresponding to the commands 1 to 4. (Refer to “changed part” in FIG. 16). In other words, when viewed from a general user, the execution level (executable) corresponding to each of the commands 2 to 4 is changed from “0” (executable) to “1” (high) by logging in to the common workspace. To be executable).

  As described above, the workspace management unit 110 of the server SRV is an operation item that is not permitted to be executed with the operation authority of the general user when the upper user and the general user log in to the workspace, and the upper user Operation items that are permitted to be executed with the operation authority are provided to general users so that they can be executed.

  Returning to FIG. 13, the work space management unit 110 of the server SRV transmits the generated client data 125 to the client device CL1 through the data transmission / reception unit 114 (step ST27). On the other hand, when the workspace management unit 140 of the client device CL1 receives the client data 125 from the server device SRV, the workspace management unit 140 stores the received client data 125 in the data storage unit 150 and at the same time, Data 125 is output to the drawing unit 142. Then, the drawing unit 142 of the client device CL1 displays the work space on the corresponding output device 6 (step ST28).

  Further, the work space management unit 110 of the server SRV transmits the generated client data 125 to the client device CL2 through the data transmission / reception unit 114 (step ST29). On the other hand, when the workspace management unit 140 of the client device CL2 receives the client data 125 from the server device SRV, the workspace management unit 140 stores the received client data 125 in the data storage unit 150 and also for the client. Data 125 is output to the drawing unit 142. Then, the drawing unit 142 of the client device CL2 displays the work space on the corresponding output device 6 (step ST30).

  As described above, in the client data 125 shown in FIG. 16, the executable level (executable) corresponding to each of the commands 1 to 4 is set to “1” (executable), so the client device CL1 In the command menu MBT on the workspace displayed on each output device 6 of CL and CL2, all buttons 302, 304, 306, and 308 are actively displayed so as to be selectable.

  As described above, when the general user is logged in to the workspace alone, the general user cannot execute the respective commands corresponding to the buttons 304, 306, and 308. When a higher-level user who is broad (that is, given higher operating authority) logs in to the same workspace, execution of these commands is permitted.

  That is, the workspace management unit 110 of the server SRV performs an operation according to a wider operation authority than the general user's operation authority when the upper user and the general user log in to the workspace. Provide executable.

<3. Processing when a higher-level user and a general user are logged in to the workspace and the higher-level user logs out (leaves) from the workspace>
FIG. 17 is a schematic diagram showing processing when the upper user logs out (leaves) from the workspace in a situation where the upper user and the general user log in to the workspace in the information processing system according to the embodiment of the present invention. is there.

  Referring to FIG. 17, consider a case where a higher-level user attempts to log out from a workspace using client device CL1. The upper user operates the input device 10 of the client device CL1 and inputs a logout request (step ST31).

  Then, the work space management unit 140 (FIG. 4) of the client device CL1 transmits a logout request from the work space to the server SRV through the data transmitting / receiving unit 144 together with the identification information of the upper user (step ST32).

  In response to the logout request from the client device CL1, the client management unit 112 of the server device SRV executes logout processing (step ST33). More specifically, the client management unit 112 of the server SRV extracts the client tag 215 corresponding to the upper user (user1) that is the transmission source of the logout request from the participation state information 122. Then, the client management unit 112 updates the value of the login state (status), which is the attribute value of the extracted client tag 215, from “1” (logged in) to “0” (logged out). The contents of the participation state information 122 after the change are as shown in FIG.

  Subsequently, the client management unit 112 of the server SRV refers to the user management data 121 and the participation state information 122 held by the data storage unit 120 and updates the contents of the operation restriction information 123 (step ST35). That is, the client management unit 112 determines the operation authority to be collectively granted to the target workspace according to the operation authority given to the general user who continues to log in to the workspace. The contents of the updated operation restriction information 123 are as shown in FIG.

  Subsequently, the workspace management unit 110 of the server SRV refers to the updated operation restriction information 123 (corresponding to FIG. 8) held in the data storage unit 120, and the workspace data 124 held in the data storage unit 120. Client data 125 is generated (step ST36). Note that the client data 125 generated in step ST36 is as shown in FIG. That is, only the executable level (executable) corresponding to command 1 is set to “1” (executable), and the executable level corresponding to commands 2 to 4 is set to “0” (not executable).

  Subsequently, the work space management unit 110 of the server SRV transmits a logout process completion notification to the client device CL1 through the data transmission / reception unit 114 (step ST37). On the other hand, when the work space management unit 140 of the client device CL1 receives the logout processing completion notification from the server device SRV, the work space displayed on the corresponding output device 6 is closed (step ST38).

  Further, the work space management unit 110 of the server SRV transmits the generated client data 125 to the client device CL2 through the data transmission / reception unit 114 (step ST39). On the other hand, when the workspace management unit 140 of the client device CL2 receives the client data 125 from the server device SRV, the workspace management unit 140 stores the received client data 125 in the data storage unit 150 and also for the client. Data 125 is output to the drawing unit 142. Then, the drawing unit 142 of the client device CL2 displays the workspace on the corresponding output device 6 (step ST40).

  As described above, in the client data 125 transmitted in step ST37, only the executable level corresponding to command 1 is set to “1” (executable), and the executable level corresponding to commands 2 to 4 is set. Is set to “0” (unexecutable). Therefore, after logout from the workspace of the upper user is completed, only the button 302 is actively displayed in the command menu MBT on the workspace displayed on the output device 6 of the client device CL2, while the remaining The buttons 304, 306, and 308 are grayed out so that they cannot be selected.

  As described above, when the upper user leaves the same workspace, the operable range of the general user returns to the range of the operation authority given to the general user.

  That is, when the higher-level user leaves the workspace, the work space management unit 110 of the server SRV returns the operation that is provided to the general user so as to be executable within the range according to the operation authority of the general user.

  In addition, as shown in FIG. 17, in the case of transmitting client data 125 in which the operable range is limited to a client device operated by a general user, any of the commands that will be limited If (processing) is being executed, transmission of the client data 125 may be waited until the execution of the command is completed.

[Processing procedure in server device]
Next, a processing procedure in the server SRV for realizing the processing procedure for the entire system described above will be described.

  FIG. 18 is a flowchart showing a processing procedure in server SRV according to the embodiment of the present invention. Each processing procedure shown in FIG. 18 is typically provided by the CPU 2 (FIG. 2) of the server SRV executing a program.

  Referring to FIG. 18, CPU 2 of server SRV determines whether or not a login request has been received from any of client devices CL (step ST100). If no login request is received from any client device CL (NO in step ST100), the process proceeds to step ST116.

  On the other hand, when a login request is received from any of the client devices CL (YES in step ST100), the CPU 2 refers to the user management data 121 for the user identification information transmitted together with the login request. An authentication process is executed (step ST102). Subsequently, the CPU 2 determines whether or not the authentication process is successful (step ST104).

  If the authentication process is successful (YES in step ST104), CPU 2 updates the contents of participation state information 122 held (step ST106). Subsequently, the CPU 2 refers to the stored user management data 121 and the participation state information 122 and updates the contents of the operation restriction information 123 (step ST108). That is, the CPU 2 determines the operation authority to be given to the user who is currently logged in to the workspace.

  Further, the CPU 2 refers to the updated operation restriction information 123 to generate client data 125 from the held work space data 124 (step ST110), and the generated client data 125 is stored in the workspace. To the client device CL currently logged in (step ST112). Then, the process proceeds to step ST116.

  If the authentication process has not succeeded (failed) (NO in step ST104), the CPU 2 notifies the client device CL that has transmitted the login request that the authentication has failed (step ST114). Then, the process proceeds to step ST116.

  In step ST116, the CPU 2 determines whether or not a logout request has been received from any of the client devices CL. If no logout request has been received from any of the client devices CL (NO in step ST116), the process returns.

  On the other hand, when a logout request is received from any client device CL (YES in step ST116), CPU 2 executes a predetermined logout process (step ST118). Subsequently, the CPU 2 updates the contents of the held participation state information 122 (step ST120). Subsequently, the CPU 2 refers to the held user management data 121 and the participation state information 122 and updates the contents of the operation restriction information 123 (step ST122). That is, the CPU 2 determines the operation authority to be given to those users based on the operation authority given to each user who continues to log in even after the target user logs out.

  Further, the CPU 2 refers to the updated operation restriction information 123 to generate the client data 125 from the retained workspace data 124 (step ST124), and the generated client data 125 is converted into the workspace. To the client device CL that is currently logged in (step ST126). Then, the process returns.

[Operations and effects of the embodiment]
According to the embodiment of the present invention, it is possible to automatically relieve operation authority for general users who are simultaneously logged in to a workspace in response to an event such as login of a higher-level user to the workspace. Therefore, even if the upper user requests the general user to perform an operation within the range exceeding the operation authority of the general user, no extra operation is required. Further, when the upper user logs out of the workspace, the operation items executable by the general user are returned to the range of the original operation authority, so that the general user can be prevented from performing an operation contrary to the intention of the upper user. .

[Modification 1]
In the above-described embodiment, the configuration in which the permission level (permission) is set in advance for each of various operations (commands) provided on the workspace is exemplified. However, the permission level may be set for each object on the workspace. Alternatively, a permission level may be set for each area on the workspace. That is, instead of various operations (commands) themselves, permission levels may be set for the targets of the operations.

  FIG. 19 shows an example of work space data 124A according to the first modification of the embodiment of the present invention. FIG. 20 shows an example of client data 125A according to the first modification of the embodiment of the present invention. FIG. 21 is a diagram showing a relationship between the permission level assigned to each object of the work space data 124 according to the first modification of the embodiment of the present invention and the executable level value in the client data.

  The workspace data 124A illustrated in FIG. 19 includes “id”, “authorid”, and “permission” as attributes (properties) of the object tag 234A.

  The “permission” attribute is a permission level indicating to which range of users the operation for the corresponding object is permitted. This permission level is set in advance by an administrator of the information processing system (or workspace) according to the present embodiment. In the permission level (permission) shown in FIG. 19, as an example, “0” indicating that no operation on the corresponding object is permitted, and the operation on the corresponding object is permitted only when the operation restriction is not set. Is stored, and “2” indicating that an arbitrary operation on the corresponding object is always permitted is stored.

  Since the “id” attribute and the “authorid” attribute have been described with reference to FIG. 10, detailed description thereof will not be repeated.

  As described above, the work space data 124A defines an operation authority necessary for executing an operation on the object in association with the definition of the object existing in the work space.

  An executable level (executable) can be set in units of objects for the workspace data 124A as shown in FIG. That is, the workspace management unit 110 of the server SRV is based on the permission level (permission) assigned to each object, the restriction level (limitation) set for each user, the creator information (authorid) of each object, and the like. Thus, the execution feasibility level for each object in the client data 125A transmitted to each user is determined. That is, the work space management unit 110 of the server SRV generates client data 125A as shown in FIG. 20 from the work space data 124A as shown in FIG.

  The client data 125A shown in FIG. 20 has “executable” as an attribute (property) of the object tag (object) 234 #. The “executable” attribute stores either “1” indicating that an operation on the corresponding object is possible or “0” indicating that an operation on the corresponding object is impossible.

  The execution level (executable) for each object is determined based on the correspondence shown in FIG. In the correspondence shown in FIG. 21, for an object created by the user himself (that is, the value of authorid matches the id of the user), an operation on the object is always executable. On the other hand, for an object created by a user other than the user (that is, the authorid value does not match the user's own id), the level of whether or not the operation can be performed on the object depends on the set permission level (permission) and each user. It is determined based on the relationship with the set limit level (limitation).

  As described above, the workspace management unit 110 of the server SRV is an object that cannot be operated with the general user's operation authority when the upper user and the general user log in to the workspace. The objects that can be operated with the operation authority of the upper user are displayed so as to be operable.

  According to Modification 1 according to the embodiment of the present invention, operation authority can be set in more detail as compared with the configuration according to the embodiment.

[Modification 2]
In the above-described embodiment, the configuration in which the user's restriction level is immediately changed when the upper user logs out of the workspace has been exemplified. However, the timing for changing this restriction level can be set more flexibly. It may be.

  For example, when the restriction level is changed with the logout of the upper user, the restriction level may be changed after notifying the general user beforehand.

  In this case, the change in the restriction level may be reflected after a predetermined time has elapsed after notifying the general user of the change in the restriction level. As a configuration for executing the change of the restriction level after a predetermined time has elapsed, a timer function may be added to the configuration according to the above-described embodiment. Specifically, the content of the participation state information 122 is updated with an event that the upper user logs out of the workspace, but the restriction level of the operation restriction information 123 is not updated. That is, instead of updating the restriction level of the operation restriction information 123, the timer function starts counting. Then, when the timer function counts up (reaches the set value of the count value), the limit level of the operation limit information 123 is updated for the first time. Note that it is preferable that the setting value of the timer function can be set freely. It is preferable to present the remaining count value up to the set value by the timer function to the general user.

  According to the second modification according to the embodiment of the present invention, it is possible to avoid a problem that an operation performed by a general user is interrupted halfway as compared with the configuration according to the embodiment.

[Modification 3]
In the above-described embodiment, the upper user and the general user are simply distinguished from each other. However, in the case of actually performing an intellectual creation work, etc., the above operation is often performed in units of groups. In some cases, it is desirable to change the authority in units of groups. Therefore, in the third modification according to the present embodiment, a configuration for managing a plurality of users as belonging to the same group is illustrated.

  As a typical example, a configuration in which a plurality of users logged in to the same workspace are managed as the same group will be described.

  FIG. 22 shows an example of user management data 121A according to the third modification of the embodiment of the present invention. FIG. 23 is a diagram illustrating an influence range of the restriction level in the registration setting situation of the user management data 121A illustrated in FIG.

  In the user management data 121A shown in FIG. 22, five users whose login names are “user1”, “user2”, “user3”, “user4”, “user5” are registered as belonging to the same group. Yes. Corresponding to these users, the user management data 121A includes five descriptions 203 surrounded by client tags 201 and 202 (<client> and </ client>).

  Furthermore, the user management data 121A includes a description 208 surrounded by group tags 206 and 207 (<group> and </ group>) for defining a group. This description 208 includes a client tag 209. Each client tag 209 has “id” as an attribute (property). The “id” attribute is identification information (a unique value in the information processing system) that identifies users belonging to the corresponding group. In this way, a group of one or more users who can participate in the workspace is registered.

  As shown in FIG. 22, only the authority level (authority) of user1 is “1”, and the authority levels (authority) of user2 to user5 are “0”. That is, user1 is an upper user, and user2 to user5 are general users.

  In the registration setting situation as described above, the upper level user1 logs in or logs out of the workspace, so that the restriction levels (limitation) of all other general users (user2 to user5) belonging to the same group are limited. ) Is changed. On the other hand, even if any general user logs in or logs out of the workspace, the restriction levels of other users belonging to the same group are not affected. That is, the influence on the restriction levels of general users (user2 to user5) has a relationship as shown in FIG.

  It is also possible to set a plurality of groups for users who can log in to the same workspace.

  FIG. 24 is a diagram showing an example of user management data 121B according to the third modification of the embodiment of the present invention. FIG. 25 is a diagram showing the influence range of the restriction level in the registration setting situation of the user management data 121B shown in FIG.

  In the user management data 121A shown in FIG. 24, users whose login names are “user1”, “user2”, and “user3” belong to the first group, and login names are “user4”, “user5”, and “user6”. A user is registered as belonging to the second group. More specifically, the group tag (group) 206A described in the user management data 121A has “id” as an attribute (property). The “id” attribute is identification information (a unique value in the information processing system) that identifies the corresponding group. The first group assigned “1” as its identification number (group id) has an identification number (client id) corresponding to each of the users whose login names are “user1”, “user2”, “user3”. Client tags 209 to which “1”, “2”, and “3” are assigned are defined. Further, in the second group to which “2” is assigned as the identification number (group id), identification numbers (client ids) respectively corresponding to users whose login names are “user4”, “user5”, and “user6”. Client tags 209 to which “4”, “5”, and “6” are assigned are defined.

  As shown in FIG. 24, the authority level (authority) of user1 and user6 is “1”, and the authority level (authority) of user2 to user5 is “0”. That is, user1 and user6 are upper users, and user2 to user5 are general users.

  Here, when user1 logs in or logs out of the workspace, the restriction level (limitation) is changed only for the other users (user2 and user3) belonging to the same group as user1, and the user ( The restriction levels of user4 to user6) are not affected.

  Similarly, when the user 6 logs in to the workspace or logs out of the workspace, the restriction level is changed only for other users (user4 and user5) belonging to the same group as the user 6, and users belonging to another group (user1 to user3). ) Restriction level is not affected. That is, the influence on the restriction levels of general users (user2 to user5) due to login / logout of the upper users user1 and user6 has a relationship as shown in FIG.

  That is, only when the upper user and the general user belong to the same group, the general user is provided with an operation according to an operation authority wider than that of the general user.

  According to the third modification of the embodiment of the present invention, when a plurality of groups perform different tasks in the same work space, it is possible to more suitably manage operation restrictions.

  In the above-described example, the configuration in which information for setting a group is included in the user management data has been illustrated, but it may be included in the workspace data. Or you may make it hold | maintain only the information for setting a group independently.

  As for the group setting as described above, (1) set in advance, (2) set all users logged in to a certain workspace as belonging to the same group at a predetermined timing, (3) A method of setting by specifying users belonging to the same group at an arbitrary timing can be employed.

  In addition, information for setting a group is retained only when the user who sets the group is logged in to the workspace, and when the user logs out of the workspace, the information for setting the group is discarded. It may be. As an alternative method, it may be stored in a nonvolatile manner so that it can be used even when logging in to the workspace after the next time.

[Modification 4]
In the above-described embodiment, when the upper user logs in to the workspace, the restriction level (limitation) of the general user is automatically updated. However, for such update of the restriction level, the upper user May be obtained.

  That is, in step ST25 shown in FIG. 13, when it is determined that the restriction level (limitation) for a general user should be changed in a direction that is relaxed, the client management unit 112 of the server SRV receives the data transmission / reception. Through the unit 114, a notification that the restriction level for the general user is changed to the same as that of the upper user is sent, and a message for accepting the permission is transmitted to the client device CL1. Then, the client management unit 112 updates the content of the operation restriction information 123 on condition that a permission for updating the restriction level is returned from the client device CL1. In other words, when a reply that the permission for updating the restriction level is rejected, the client management unit 112 does not relax the restriction level for general users.

Since other processes are the same as those in the above-described embodiment, detailed description will not be repeated. According to the fourth modification of the present invention, when a general user does not notice the login to the workspace by the general user. In addition, it is possible to avoid the problem that the operation authority of the general user is arbitrarily expanded without the knowledge of the upper user.

[Modification 5]
Note that it is possible to configure an information processing system in which the above-described embodiment and modifications 1 to 4 are arbitrarily combined.

[Other variations]
(1) In the above-described embodiment, a configuration in which the client data 125 is generated from the work space data 124 after updating the contents of the operation restriction information 123 according to the login status of the user to the work space. Illustrated. However, without creating the operation restriction information 123, the status of the user who is currently logged in to the workspace is acquired every time a predetermined event occurs, and the client data is obtained from the workspace data 124 based on the acquired login status. Data 125 may be generated.

  (2) In the above-described embodiment, the operation authority (authority value) and the restriction level (limitation value) are both exemplified as configurations that can be set in two stages. However, more stages are provided. It may be.

  (3) In the above-described embodiment, the configuration in which the restriction level (limitation) of the general user is automatically changed in response to the occurrence of an event such as login / logout of the upper user is illustrated. The upper user may be allowed to further change the restriction level of the general user.

  (4) In the above-described implementation, the configuration for managing login management and operation authority based on the identification number of the user has been illustrated, but these may be managed in units of client devices.

[Other embodiments]
Part or all of the functions realized by the program according to the present embodiment may be configured by dedicated hardware.

  In addition, the program executed by the CPU according to the present embodiment is a program module provided as a part of a computer operating system (OS) and calls a required module at a predetermined timing in a predetermined arrangement for processing. It may be executed. In that case, the program itself does not include the module, and the process is executed in cooperation with the OS. Therefore, a program that does not include such a module can also be included in the program according to the present invention.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  2 CPU, 4 internal bus, 6 output device, 8 communication interface, 10 input device, 12 hard disk, 14 memory, 16 CD-ROM drive, 16a CD-ROM, 18 flexible disk (FDD) drive, 18a flexible disk, 110 work Space management unit, 112 Client management unit, 114 Data transmission / reception unit, 116 Registration / deletion unit, 117 Participation state management unit, 118 Operation restriction management unit, 120 Data storage unit, 121, 121A, 121B User management data, 122 Participation state Information, 123 operation restriction information, 124, 124A workspace data, 125, 125A client data, 140 workspace management unit, 142 drawing unit, 144 data transmission / reception unit, 150 data storage unit, CL CL1~CLN client devices, NW network, SRV server device.

Claims (9)

An information processing system that provides a virtual work space in which multiple users can work simultaneously,
Server means;
A plurality of display means each for displaying the virtual workspace;
A plurality of input means respectively associated with the plurality of display means,
The server means includes
User registration means for registering a user who can participate in the virtual workspace in association with an operation authority in the virtual workspace given to the user;
State management means for acquiring the participation state of the user in the virtual workspace;
Operation authority management means for providing an operation according to the operation authority of the user so as to be executable for the user participating in the virtual workspace,
The operation authority management means is configured such that when a first user who is given an operation authority and a second user whose operation authority is limited by the first user are participating in the virtual workspace, An information processing system that provides an operation according to an operation authority wider than that of the second user so as to be executable for the second user.   When the first user leaves the virtual work space, the operation authority management unit returns an operation to be provided to the second user so as to be executable to a range corresponding to the operation authority of the second user. The information processing system according to claim 1.   The operation authority management means responds to an operation authority of the first user after the predetermined time has elapsed after the first user leaves the virtual workspace according to the operation authority of the first user. The information processing system according to claim 2, wherein the information processing system is returned to the range. The server means further includes definition data management means for holding definition data for providing the virtual work space and an object existing in the virtual work space, and reflecting an operation performed by a user in the definition data,
The operation authority management means is a client data for displaying the virtual work space on the display means corresponding to the user from the definition data in accordance with the operation authority of the user participating in the virtual work space. The information processing system according to any one of claims 1 to 3, wherein: In the definition data, the operation items that can be provided to the user are defined in association with the operation authority necessary for the execution,
The operation authority management means is an operation item that is not permitted to be executed with the operation authority of the second user when the first and second users participate in the virtual work space, and The information processing system according to claim 4, wherein an operation item that is permitted to be executed by the operation authority of the first user is provided to the second user so as to be executable. In the definition data, an operation authority necessary for performing an operation on the object is defined in association with the definition of the object existing in the virtual workspace.
The operation authority management means operates the second user with the operation authority of the second user when the first and second users participate in the virtual work space. The information processing system according to claim 4, wherein an object that cannot be operated and is operable with the operation authority of the first user is displayed in an operable manner. The server means further includes group registration means for registering a group of one or more users who can participate in the virtual work space,
The operation authority management means responds to an operation authority wider than the second operation authority for the second user only when the first and second users belong to the same group. The information processing system according to any one of claims 1 to 6, wherein the operation is provided to be executable. An information processing method for providing a virtual work space in which a plurality of users can work simultaneously,
A server device registers a user who can participate in the virtual workspace in association with an operation authority in the virtual workspace given to the user;
The server device acquiring a participation state of a user in the virtual workspace;
The server device includes a step of providing an operation according to the operation authority of the user so as to be executable for the user participating in the virtual work space,
In the step of providing the operation in an executable manner, a first user who is given a certain operation authority and a second user whose operation authority is limited by the first user are participating in the virtual workspace. In this case, the information processing method includes a step of providing the second user with an operation according to an operation authority wider than the operation authority of the second user. An information processing apparatus that provides a virtual work space capable of simultaneous work by a plurality of users in a plurality of terminals connected to be capable of data communication,
User registration means for registering a user who can participate in the virtual workspace in association with an operation authority in the virtual workspace given to the user;
State management means for acquiring the participation state of the user in the virtual workspace;
Operation authority management means for providing an operation according to the operation authority of the user to a user participating in the virtual work space in an executable manner,
The operation authority management means is configured such that when a first user who is given an operation authority and a second user whose operation authority is limited by the first user are participating in the virtual workspace, An information processing apparatus that provides an operation according to an operation authority wider than that of the second user to a second user so as to be executable.

Images