JP6488809B2 - Web service session synchronization management system, web service session synchronization management method and program thereof - Google Patents

Description

  The present invention relates to a web service session synchronization management system, a web service session synchronization management method, and a web service session synchronization management program, and particularly in the field of a web service that manages a series of operations between a server and a client in a session. The present invention relates to a web service session synchronization management system, a web service session synchronization management method, and a web service session synchronization management program.

  Based on security requirements, the system controls that another person monitors the work content of a person who performs a certain role and performs some operation at the same time in another place. Had been implemented. For example, in the case of a dedicated control system used in the steel manufacturing process, it is built on a special protocol with an emphasis on reliability within the line network, and another person monitors the work content of the worker. It is possible to construct a mechanism for monitoring or automatically monitoring relatively easily.

  However, even for general systems, only the requirement of monitoring is required due to the development and maturity of open Web system technology built on TCP (Transmission Control Protocol) that does not necessarily guarantee the integrity of communication. For example, it has become possible to envisage implementation at a significantly lower cost without using a dedicated system.

  On a standard protocol used by a general Web system, normally, communication success is not guaranteed, and no specific relationship is assumed between the operations. In principle, the success or failure of the previous communication is separated from the subsequent communication. However, in actual operations, it may be necessary to manage a series of communications as a single operation. Therefore, such technology has developed and matured on an open Web system. The technology provided in the present invention has become feasible against the background of the technical development as described above.

  As a mechanism conventionally employed for the Web server to collect a series of operations, a general Web server has a session management mechanism. Here, a normal session is a concept that summarizes a series of operations from one client (one operating user), and between the start of a session such as login and the end of the session such as logout. The communication between the Web server and the Web server maintains some uniform relation.

  When an operator performs an important operation such as changing the settings of a system to be used, a server device, etc., for example, the content of the operation (or an operation to be performed in the future) ) May need to be confirmed. In such a case, conventionally, a Web system (workflow) in which an operator requests approval for the contents and the approver approves the system is widely used.

  However, such a Web system (workflow) has the following problems. Since it cannot be performed in real time, for example, even when an important change of the system is approved, it is usually approved in advance or afterwards. As a result, for example, in the case of pre-approval, it is not guaranteed that the approved content will always match the actual content, so changes that are actually different from the approved content may be made. obtain. Further, in the case of post-approval, even if it is determined that an incorrect operation is performed at the time of approval, since the actual processing has already been performed, the erroneous operation cannot be prevented in advance.

  Depending on the content of the operation, it may be necessary to ensure that the monitor is constantly monitoring all operations of the operator. For such applications, workflows that do not have real-time properties cannot be used. In addition, there is a case where real-time property is required for the content itself while requiring monitoring / permission such as editing / distribution of moving images, and the workflow cannot be used for such purposes.

  In particular, security requirements may require that the operator and a supervisor who monitors the operation of the operator are working simultaneously. Conventionally, in such a case, an operator who actually works and a monitor who checks the operation of the operator are in front of the same operation terminal, and the operator performs the work of the operator in real time while looking at the same screen. The method of checking is adopted. However, in this case, unless there are a plurality of persons at the same physical location, real-time monitoring of the operation cannot be guaranteed, which is very inconvenient. Furthermore, even if the operator and the supervisor are working while viewing the same screen, the operator only sees the operation performed by the operator, so the operator performs an incorrect operation. It is impossible for the observer to completely stop in real time from the side. In order for the monitor to perform complete control, the operation target Web system itself must include a technique for ensuring that the operator can execute the operation only after the monitor approves the operation. desired.

  In some cases, it is desirable to manage operations performed by a plurality of clients including a plurality of clients as one group. In order to realize such management, a technique for collecting or linking a plurality of sessions is necessary. As such a mechanism, in the prior art, for example, there is a technique disclosed in Japanese Patent Application Laid-Open No. 2009-230597 “Information Control System and Method in Web Service”. The technology of Patent Document 1 is configured to associate user actions in combination with two management units of a business session and a shared session, thereby handling a plurality of user actions collectively, and displaying them in a client view. It is a technology that tries to display a group.

  On the other hand, a technique for sharing the same screen on a plurality of clients has already been put into practical use by a method of using a dedicated client using a P2P (Peer to Peer) communication technique.

JP 2009-230597 A (page 6-8)

  Although the technique described in Patent Document 1 is a technique for strictly guaranteeing that there is no difference in the screens viewed by a plurality of clients, means for confirming operations of two related sessions on the client side Therefore, it cannot be used for an application that needs to guarantee that a plurality of clients are completely viewing the same screen without delay. Moreover, simply sharing the screen cannot completely stop the operator from performing an erroneous operation in real time. Further, since there is no means for reflecting the contents executed in each other session in the control of the contents executed in the other session, there is a problem that the other operation cannot be changed by one operation.

  Also, even with the conventional sharing technology that uses a dedicated client using the P2P communication technology, it is not possible to perform a joint operation while enjoying the service provided by the Web service, and there is always a delay due to communication. As a result, the contents displayed on the screens of a plurality of clients cannot be used for the purpose of using the Web service while ensuring that the contents are the same for each client. Further, there is a problem that the server side understands the role of each session and cannot control the operation of the other session in accordance with the operation of one session.

  In other words, in order to solve the above problems, the service provided by the Web system is connected to the operation target Web system, and the monitor stops or prompts the operation of the operator in real time. Technology to enjoy is necessary. In other words, the contents displayed on all the terminals participating in the common session are synchronized while linking multiple sessions and controlling the operation of the other session by the server according to the operation of one session. Therefore, there is a demand for a technology that guarantees that the user can enjoy the service provided by the Web service at the same time.

(Object of the present invention)
The present invention has been made in view of such circumstances, and a Web service session synchronization management system and Web service session synchronization capable of guaranteeing complete control of an operator's operation in real time even from a remote location An object of the present invention is to provide a management method and a Web service session synchronization management program.

  In order to solve the above-described problems, the Web service session synchronization management system, the Web service session synchronization management method, and the Web service session synchronization management program according to the present invention mainly adopt the following characteristic configuration.

(1) A Web service session synchronization management system according to the present invention includes:
A server device that provides a Web service; a first client device that includes means for enjoying the Web service via a session with the server device; a unit that transmits and receives information to and from the first client device; A second client device comprising means for transmitting and receiving information to and from the server device via a session associated with a session of one client device, and both the first client device and the second client device A web service session synchronization management system for synchronizing the sessions of
The server device
When creating a session with the first client device, check whether a session with the second client device associated with the session has been created,
If a session with the second client device has not yet been generated when a session with the first client device is generated, it is impossible to operate as a response to the first client device. Return an empty screen,
In addition, after the session with the first client device is generated, when the session with the second client device is generated, or the session with the second client device already exists. In this case, when a session with the first client device is generated, an operation screen that can be operated is transmitted to the first client device, and at the same time, to the second client device. The same operation screen as the operation screen transmitted to the first client device is returned.

(2) A Web service session synchronization management method according to the present invention includes:
A server device that provides a Web service; a first client device having a step of enjoying the Web service via a session with the server device; a step of transmitting / receiving information to / from the first client device; And a second client device having a step of transmitting and receiving information to and from the server device via a session associated with the session of the client device, and a session between both the first client device and the second client device. A web service session synchronization management method in a web service session synchronization management system that performs synchronization of
The server device
When creating a session with the first client device, check whether a session with the second client device associated with the session has been created,
If a session with the second client device has not yet been generated when a session with the first client device is generated, it is impossible to operate as a response to the first client device. Return an empty screen,
In addition, after the session with the first client device is generated, when the session with the second client device is generated, or the session with the second client device already exists. In this case, when a session with the first client device is generated, an operation screen that can be operated is transmitted to the first client device, and at the same time, to the second client device. Returning the same operation screen as the operation screen transmitted to the first client device;
It is characterized by that.

  (3) A Web service session synchronization management program according to the present invention is characterized in that the Web service session synchronization management method described in (2) is implemented as a program executable by a computer.

  According to the web service session synchronization management system, web service session synchronization management method, and web service session synchronization management program of the present invention, the following effects can be obtained.

  First, in order to enjoy the Web service, the operation and the monitoring work must be divided into separate workers (operator and monitoring person). Even if you are far away from each other, the same screen is displayed synchronously for the operator and the supervisor, so the system can guarantee that both are working at the same time in real time. it can.

  Secondly, since the monitor can monitor the operation of the operator in real time and adopt a mechanism for giving approval of the operation content, the operator can prevent an erroneous operation from occurring. be able to.

1 is a system configuration diagram illustrating an example of a system configuration of a Web service session synchronization management system according to the present invention. FIG. In the Web service session synchronization management system shown in FIG. 1, when the operator who uses the second client device logs in to the session where the operator who uses the first client device logs in, the operator and the monitor It is a sequence diagram which shows the flow until it displays the operation screen synchronized with respect to both. The monitoring situation of the monitor using the second client device when the operator using the first client device performs an operation on the operation screen of the logged-in session in the Web service session synchronization management system shown in FIG. It is a sequence diagram for demonstrating. It is a table which shows an example of the user correlation table with which the service provision means of the server apparatus shown in FIG. 1 was equipped. It is a table which shows an example of the session information table with which the service provision means of the server apparatus shown in FIG. 1 was equipped. It is a state transition diagram which shows an example of the state transition which confirms the presence or absence of the related session of a request transmission session in the confirmation means of the server apparatus shown in FIG. It is a state transition diagram which shows an example of the state transition which confirms the presence or absence of the related session regarding the request transmission session of a 2nd client apparatus in the confirmation means of the server apparatus shown in FIG. It is a state transition diagram which shows an example of the state transition regarding the presence or absence of the related session regarding a request transmission session in the service provision means of the server apparatus shown in FIG. It is a state transition diagram which shows an example of the state transition regarding the screen collation operation | movement in the confirmation means of the client apparatus shown in FIG. It is a schematic diagram which shows the example of a screen structure of the server setting screen displayed on a screen as an example of an operation screen on the display part of the client apparatus shown in FIG. It is a table which shows an example of the required authority setting table hold | maintained inside the determination means of the server apparatus shown in FIG. It is a state transition diagram which shows an example of the state transition which confirms the presence or absence of the related session regarding a screen information transmission session in the service provision means of the server apparatus shown in FIG. FIG. 4 is a schematic diagram schematically showing the flow of screen information transmitted / received among the server device, the first client device, and the second client device in the operations from sequence Seq21 to sequence Seq28 in FIG. 3. It is a system configuration | structure figure which shows the system configuration example different from FIG. 1 of the web service session synchronous management system by this invention. It is a schematic diagram which shows the example of a screen structure different from FIG. 10 of the server setting screen displayed on a screen as an example of an operation screen on the display part of the 1st client apparatus shown in FIG. FIG. 15 is a schematic diagram illustrating a screen configuration example different from FIG. 10 of a server setting screen displayed as an example of an operation screen on the display unit of the second client device illustrated in FIG. 14. It is a state transition diagram which shows an example of the state transition in the synchronous operation control means in the determination means of the server apparatus shown in FIG. It is a table which shows an example of the required authority setting table hold | maintained inside the determination means of the server apparatus shown in FIG.

  Preferred embodiments of a web service session synchronization management system, a web service session synchronization management method, and a web service session synchronization management program according to the present invention will be described below with reference to the accompanying drawings. In the following description, a web service session synchronization management system and a web service session synchronization management method according to the present invention will be described. However, the web service session synchronization management method is implemented as a web service session synchronization management program that can be executed by a computer. Needless to say, the Web service session synchronization management program may be recorded on a computer-readable recording medium. In addition, it is needless to say that the drawing reference numerals attached to the following drawings are added for convenience to the respective elements as an example for facilitating understanding, and are not intended to limit the present invention to the illustrated embodiments. Yes.

(Features of the present invention)
Prior to the description of the embodiments of the present invention, an outline of the features of the present invention will be described first. The present invention provides a confirmation unit for ensuring that the server device and the client device are synchronized with each other so that a plurality of users can view the same screen at the same time without delay even if they are in different locations. The main feature is that work contents can be guaranteed in real time by providing at least each of them. In addition, the server device recognizes the operations of a plurality of users separately, and links the plurality of operations to each other, thereby changing the contents that can be operated in the other session according to the operation by each session. The main feature is to be able to. Thus, it is possible to ensure that the operation of the operator is completely controlled in real time even from a remote location.

  To explain further, the present invention is different from the conventional technology such as Patent Document 1 described above in that a plurality of continuous logins are performed on a Web service, a plurality of user sessions are managed, and an operation is performed for each session. The main feature is that the operations in each session are related to each other, and the operation content that can be operated from the other session (the other user) can be changed according to the operation of one session (the other user). Yes.

  More specifically, the main feature of the present invention is that it has the following configuration. A server apparatus that provides a Web service, a first client apparatus that operates the Web service, and a second client apparatus that is operated by a user different from the first client apparatus. Each of the first client device and the second client device includes a confirmation unit. The first client device includes a communication unit with the server device and the second client device. The second client device also includes: Similarly, the main feature is that it includes means for communicating with the server device and the second client device.

  Thus, when the user A generates a session a from the first client device (for example, by logging in), the other user B transmits a session b related to the session a from the second client device. Can be generated. At this time, the same screen information transmitted from the server device to the first client device is also transmitted to the second client device, and at the same time, the first client device is notified of the first information. An instruction is given to transmit the screen information of the client device to the second client device, and the screen information of the first client device is transmitted from the first client device to the second client device.

  Therefore, the second client device collates two pieces of screen information, that is, the screen information of the first client device received from the server device and the screen information of the first client device received from the first client device. Using the result, it is possible to generate its own screen so as to be the same screen as the first client device. Thus, the other user B of the second client device can always check the latest screen of the first client device.

(Configuration example of embodiment)
Next, an example of the system configuration of the Web service session synchronization management system according to the present invention will be described with reference to FIG. FIG. 1 is a system configuration diagram showing an example of a system configuration of a Web service session synchronization management system according to the present invention.

  A web service session synchronization management system shown in FIG. 1 as an embodiment of the present invention includes a server apparatus 1 including a service providing unit 11 that provides an existing web service, and the first client apparatus used by a user A. The configuration includes at least the client device 2 that enjoys the service and the client device 3 that enjoys the Web service as the second client device used by the user B.

  In addition, the server device 1 includes a confirmation unit 12 for managing a session from the client device 2 and a session from the client device 3 in association with each other, and further, one of the client device 2 and the client device 3 When the result is returned to the apparatus, the transmission unit 13 for transmitting the same contents to the other client apparatus that generates the related session, and reception for receiving information from each of the client apparatus 2 and the client apparatus 3 Part 14.

  The client device 2 (first client device) receives input from the user A who uses the client device 2 in addition to the transmission unit 22 and the reception unit 23 for communicating with the server device 1. Means 21, transmission means 26 for transmitting information received by itself to client apparatus 3, and reception means 27 for receiving information from client apparatus 3, and further, information received from server apparatus 1 and the client apparatus 3 is provided with a confirmation means 25 for confirming consistency with the information received from 3 and a display unit 24 for displaying the confirmed information.

  Similarly to the client device 2, the client device 3 (second client device) is a user who uses the client device 3 in addition to the transmission unit 32 and the reception unit 33 for communicating with the server device 1. B includes an input unit 31 for receiving information from B, a transmission unit 36 for transmitting information received by itself to the client device 2, and a reception unit 37 for receiving information from the client device 2. A confirmation unit 35 for confirming consistency between the information received from the client apparatus 2 and the information received from the client apparatus 2 and a display unit 34 for displaying the confirmed information.

  By adopting the configuration illustrated in FIG. 1, when the user A generates a session a from the one client device 2 (first client device) to the server device 1 (for example, by logging in), the other The user B who uses the client apparatus 3 (second client apparatus) can generate a session b related to the session a generated by the user A.

  At this time, when the screen information of the client device 2 (first client device) is transmitted from the server device 1 to the client device 2 (first client device), the server device 1 simultaneously transmits the transmission unit 13. The client device 3 (second client device) transmits the same screen information as the client device 2 (first client device) to the client device 2 (first client device). ) To send the screen information of the client device 2 (first client device) to the client device 3 (second client device). The client device 2 (first client device) that has received the instruction from the server device 1 uses the transmission unit 26 to transmit the screen information of the client device 2 to the client device 3 (second client device). To do.

  The client device 3 (second client device) receives the screen information received from the server device 1 as the same screen information as the client device 2 (first client device) via the receiving unit 33, and the client device 2 (first client device). Using the two pieces of information of the client apparatus 2 (first client apparatus) received via the receiving means 37 from the client apparatus). Thus, the other client device 3 (second client device) can always check the latest screen of one client device 2 (first client device).

(Description of operation of embodiment)
Next, as an example of an embodiment according to the present invention, a user A (operator A) who uses the client device 2 (first client device) in the operation example of the Web service session synchronization management system shown in the system configuration diagram of FIG. 2) and FIG. 3 as an example of the use of a Web service that guarantees that the user B (monitoring person B) using the client apparatus 3 (second client apparatus) is monitoring the operation of This will be described in detail with reference to the drawings.

  FIG. 2 shows a client device 3 (second client device) in a session logged in by a user A (operator A) who uses the client device 2 (first client device) in the Web service session synchronization management system shown in FIG. Is a sequence diagram showing a flow until a synchronized operation screen is displayed for both the operator A and the monitor B when the user B (monitorer B) who uses) logs in. In the sequence diagram of FIG. 2, the client device 2 (first client device), the confirmation unit 25, the client device 3 (second client device), the confirmation unit 35, the service providing unit 11 in the server device 1, The flow of signals transmitted and received between the confirmation means 12 and the operations of the user A (operator A) who uses the client device 2 and the user B (monitorer B) who uses the client device 3 are shown.

  In the sequence diagram of FIG. 2, when a user A (operator A) first logs in by entering authentication information from the display unit 24 using the input means 21 of the client device 2 (sequence Seq1), the authentication information is The login information is transmitted from the transmission unit 22 of the client device 2 to the server device 1 (sequence Seq2). When the server device 1 receives the authentication information of the user A (operator A) as the login information via the receiving unit 14, the service providing means 11 that provides the existing service authenticates the authentication information of the user A, and the user A session for A (operator A) is generated (sequence Seq3). Here, in the present embodiment, it is assumed that the user A (operator A) cannot perform any operation related to the web service unless the user A (operator A) is under the real-time monitoring of the user B (monitorer B). Assumes.

  In addition, the service providing means 11 of the server device 1 can monitor login, in which each user may be a monitoring target, such as association between the user A (operator A) and the user B (monitoring person B). A user association table as shown in FIG. 4 in which users are registered in advance for each user is held, and session information relating to the generated session is held as a session information table as shown in FIG.

  FIG. 4 is a table showing an example of a user association table provided in the service providing unit 11 of the server apparatus 1 shown in FIG. The user association table 200 shown in FIG. 4 includes a user ID 201 and a user ID 202 that can be monitored and logged in. Which user can be monitored by each user registered in the user ID 201 as a monitor. This is registered in advance as a monitorable user ID 202 as a monitorable operator.

  FIG. 5 is a table showing an example of a session information table provided in the service providing unit 11 of the server apparatus 1 shown in FIG. The session information table 100 in FIG. 5 includes, for example, a session ID 101 indicating a generated session, terminal identification information 102 (for example, an IP (Internet Protocol) address) identifying a client device that has generated the session, and any other session. Related information 103 that indicates whether or not there is a relationship, and relevance information 104 that indicates what kind of relationship is present when there is a relationship with another session.

  The service providing unit 11 stores the session ID indicating the session of the user A (operator A) and the information indicating the client device 2 (for example, the IP address) in the session information table 100 illustrated in FIG. After registering with the information 102, the presence or absence of the session of the user B (monitoring person B) is confirmed using the confirmation means 12 provided in the server device 1 (sequence Seq4). At this time, the confirmation unit 12 confirms the session information table 100 shown in FIG. 5, and the user B (monitoring person B) who should monitor the operation of the user A (operating person) is not logged in yet. As shown in a state transition diagram of FIG. 6 to be described later, the logged-in user A (operator A) determines that there is nothing that can be operated at the present time. Accordingly, based on the determination result, the service providing unit 11 returns an empty screen that does not include the operation content to the client device 2 (sequence Seq5). The client apparatus 2 displays the returned empty screen on the display unit 24 and notifies the user A (operator A) that the user B (monitoring person B) has not logged in yet.

  FIG. 6 is a state transition diagram illustrating an example of state transition in which the confirmation unit 12 of the server apparatus 1 illustrated in FIG. 1 confirms the presence / absence of a session related to a request transmission session. As illustrated in FIG. 6, the confirmation unit 12 of the server device 1 first displays the related information 103 of the session information table 100 illustrated in FIG. 5 for the request transmission session with the client device 2 in the state ST31, for example. Referring to it, it is confirmed whether there is a related session for the request transmission session (state ST31).

  When there is no related session, the process transits to the state ST32, and it is confirmed whether or not the request of the request transmission session is due to the operation of the user B (monitorer B) of the client device 3 (state ST32). When the request of the request transmission session is not due to the operation of the user B (monitoring person B), the process transits to the state ST36 so that an empty screen not including the operation content is returned to the client device 2. Then, the service requesting means 11 of the confirmation request source is instructed (state ST36). Therefore, as shown in the sequence Seq5 of FIG. 2, the service providing unit 11 performs an operation of returning an empty screen not including the operation content to the client device 2.

  Here, the user B (monitoring person B) inputs the authentication information from the display unit 34 using the input means 31 of the client device 3, and logs in as the monitoring person of the user A (operator A) (sequence Seq6). ) And information indicating that the user is the supervisor of the user A (operator A) is transmitted as login information from the transmission unit 32 of the client device 3 to the service providing means 11 of the server device 1 (sequence Seq7). . When the server apparatus 1 receives the authentication information of the user B (monitorer B) and the information for opening the monitoring session of the user A (operator A) as login information via the receiving unit 14, the server apparatus 1 provides an existing service. The service providing unit 11 authenticates the authentication information of the user B (monitoring person B) and generates a session for the user B (monitoring person B) (sequence Seq8).

  Furthermore, the service providing means 11 of the server device 1 stores the session ID indicating the session of the user B (operator B) and the information indicating the client device 2 (for example, IP address) in the session information table 100 shown in FIG. In addition to registering in the session ID 101 and the terminal identification information 102, the fact that the session ID of the monitoring target user A (operator A) is monitored is set and registered in the related information 103 and the related information 104. Further, regarding the user A (operator A) in the session information table 100 shown in FIG. 5, the fact that monitoring is performed by the session ID of the user B (monitoring person B) is set and registered in the related information 103 and the related information 104. .

  Thereafter, the service providing means 11 confirms the presence / absence of a session of the user A (operator A) to be monitored using the confirmation means 12 provided in the server device 1 (sequence Seq9). At this time, the confirmation unit 12 refers to the session information table 100 shown in FIG. 5 and confirms that the user A (operator A) to be monitored by the user B (monitorer B) has been logged in. Therefore, as shown in a state transition diagram of FIG. 7 to be described later, the operation of the user A (operator A) to be monitored is monitored and the screen synchronization between the user A (operator A) and the user B (monitorer B) is performed. Is determined to be started.

  Therefore, since the service providing means 11 knows that the user B (monitorer B) who monitors the operation of the user A (operator A) is logged in based on the determination result, the user B (monitoring) The client B) transmits an operable screen to the client device 2 used by the user A (operator A) and transmits the screen information of the client device 2 to the client device 3. The apparatus 2 is instructed (sequence Seq10). The client device 2 displays the returned operable screen on the display unit 24 and presents it to the user A (operator A).

  FIG. 7 is a state transition diagram illustrating an example of state transition in which the confirmation unit 12 of the server apparatus 1 illustrated in FIG. 1 confirms the presence / absence of a related session related to the request transmission session of the client apparatus 3 (second client apparatus). As shown in FIG. 7, the confirmation unit 12 of the server device 1 first refers to the related information 103 of the session information table 100 shown in FIG. 5 for the request transmission session with the client device 3 in the state ST21. Thus, it is confirmed whether or not there is a related session for the request transmission session (state ST21).

  If there is no related session, nothing is done and the confirmation process is terminated, but if there is a related session, the process proceeds to the state ST22 and the relevance information 104 of the session information table 100 shown in FIG. , And confirms the related type of request in the request transmission session (state ST22). If the related type is a monitoring session, the process transits to the state ST23 to check whether the request is an operation by the user B (monitoring person B) (state ST23). With reference to the terminal identification information 102 of the session information table 100 shown in FIG. 5, when the operation is performed by the user B (monitoring person B), the state transitions to the state ST26.

  When the state transitions to the state ST26, the service providing means determines that the user B (monitoring person B) should start monitoring the operation of the user A (operating person A) to be monitored and returns a normal response. 11 is instructed. Therefore, as shown in the sequence Seq10 of FIG. 2, the service providing unit 11 uses the client A 2 (operator A) to use a screen that can be operated under the monitoring of the user B (monitor B). And starts the operation of the next sequence Seq11 in order to start screen synchronization between the user A (operator A) and the user B (monitorer B).

  In other words, the service providing means 11 of the server device 1 transmits to the client device 2 at the same time to the client device 3 used by the user B (monitorer B) as shown in a state transition diagram of FIG. The same screen as the screen that can be operated is transmitted (sequence Seq11). Note that the service providing means 11 of the server device 1 also passes terminal information (for example, IP address) of the client devices related to each other to each of the related client devices in the sequence Seq10 and the sequence Seq11.

  That is, since the client apparatus 2 and the client apparatus 3 are set with session IDs related to the related information 103 of the session information table 100, the service providing unit 11 sets the terminal identification information 102 of the session information table 100. The mutual terminal information (for example, IP address) can be delivered to the client device 2 and the client device 3. Accordingly, the client device can transmit its own screen information to the client device to be synchronized, and when receiving image information from any client device, the client device to be synchronized It is also possible to identify whether or not the screen information is from.

  FIG. 8 is a state transition diagram illustrating an example of state transition regarding the presence / absence of a related session regarding the request transmission session in the service providing unit 11 of the server apparatus 1 illustrated in FIG. 1. As illustrated in FIG. 8, the service providing unit 11 of the server device 1 confirms whether a session related to the request transmission session exists for the request transmission session with the client device 2 in the state ST1. (State ST1). If there is a related session, the state transits to the state ST2, and the same data as the response of the request transmission session with the client device 2 is also transmitted for the related session set with the client device 3. Is instructed to the transmission unit 13 (state ST2). Accordingly, the same screen information as the screen information transmitted to the client device 2 is also transmitted to the client device 3.

  In the sequence Seq11, the client device 3 receives the information on the screen (represented as α screen here) returned from the server device 1 at the receiving unit 33, but at this time, the screen is still on the display unit 34. Do not show. On the other hand, the client device 2 responds to the client device 2 in response to an instruction to transmit the current screen information of the client device 2 to the client device 3 received from the service providing unit 11 of the server device 1 in the sequence Seq10. The currently displayed screen information, that is, the screen information received from the server device 1 in the sequence Seq10 is transmitted to the client device 3 using the transmission means 26 (sequence Seq12).

  When the client device 3 obtains the screen information from the client device 2 (represented as β screen here) by the receiving means 37, the client device 3 outputs it to the confirmation means 35 (sequence Seq13), and the state transition diagram of FIG. As shown in FIG. 3, the α screen returned from the server device 1 is compared with the β screen transmitted from the client device 2. As a comparison result, when the α screen and the β screen are the same screen, the client device 3 is a screen in a state of being synchronized with the client device 2 and is the user B (monitoring person). B) It is determined that the screen should be displayed for presentation, and the α screen returned from the server device 1 is displayed on the display unit 34 and presented to the user B (monitor B) (sequence). Seq14).

  FIG. 9 is a state transition diagram showing an example of state transition related to the screen collation operation in the confirmation unit 25 of the client device 2 shown in FIG. 1, and the response (received by the receiving unit 23 from the service providing unit 11 of the server device 1). An operation example is shown in which a response screen (α screen)) and a page (response screen (β screen)) received by the receiving unit 27 from the client apparatus 3 are collated. As shown in FIG. 9, the confirmation unit 25 of the client device 2 receives the response (response screen (α screen)) received from the service providing unit 11 of the server device 1 by the receiving unit 23 and the client device 3 in the state ST41. It is confirmed whether or not the page (response screen (β screen)) received by the receiving means 27 is the same screen (state ST41).

  When the α screen and the β screen are the same screen, the screen transits to the state ST42, and the α screen returned from the server device 1 is displayed on the display unit 34 (state ST42). On the other hand, if the α screen and the β screen are not the same screen, the state transits to the state ST43 and the next data from the server device 1 or the client device 3 is sent to the receiving unit 23 or the receiving means 27. To wait for reception (state ST43).

  With the above operation, the screen viewed by the user A (operator A) and the screen viewed by the user B (monitorer B) are synchronized with each other and become the same screen. In addition, the operation of the user A (operator A) can be restricted depending on whether or not the user B (monitoring person B) is monitoring.

  Next, the sequence diagram shown in FIG. 3 will be described. FIG. 3 shows a case where a user A (operator A) who uses the client device 2 (first client device) in the Web service session synchronization management system shown in FIG. It is a sequence diagram for demonstrating the monitoring condition in the user B (monitoring person B) who uses this client apparatus 3 (2nd client apparatus). In addition, also about the sequence diagram of FIG. Similar to the sequence diagram of FIG. 2, the client device 2 (first client device), the confirmation unit 25, the client device 3 (second client device), the confirmation unit 35, the service providing unit 11 in the server device 1, the confirmation unit 12 shows the flow of signals transmitted and received between the user 12 and the operation of the user A (operator A) who uses the client device 2 and the user B (monitorer B) who uses the client device 3.

  In the sequence diagram of FIG. 3, first, the user A (operator A) uses the input unit 21 of the client device 2 to input some information on a certain form on the operation screen displayed on the display unit 24. Then (sequence Seq21), the input information is transmitted as an input screen from the transmission unit 22 to the service providing means 11 of the server device 1 (sequence Seq22). In addition, as an operation screen displayed on the display part 24, there exists a server setting screen regarding the server apparatus 1 as shown in FIG. 10, for example. FIG. 10 is a schematic diagram illustrating a screen configuration example of a server setting screen displayed as an example of an operation screen on the display unit 24 of the client apparatus 2 illustrated in FIG. 1, and an example in which a setting form related to a mail server is displayed. Is shown.

  When the server apparatus 1 receives the input information of the user A (operator A) via the receiving unit 14 as an input screen, the service providing means 11 that provides the existing service receives the input information from the user A (user A ( After generating a response screen to be returned to the client device 2 of the operator A), the operation content (request) from the client device 2 of the user A (operator A) is further allowed to the confirmation means 12. It is confirmed whether or not it is an operation (sequence Seq23).

  The confirmation unit 12 refers to the necessary authority setting table illustrated in FIG. 11 to determine whether or not the operation content (request) from the client device 2 of the user A (operator A) is an allowed operation. Check. FIG. 11 is a table showing an example of the necessary authority setting table 110 held in the confirmation unit 12 of the server apparatus 1 shown in FIG. The required authority setting table 110 shown in FIG. 11 includes a resource (URI) 111, an operation (method) 112, and a required authority 113, and the authority required for the operation 112 for each resource 111 is required for each resource 111. 113 is set in advance.

  When the operation of the user A (operator A) is an allowed operation, the service providing unit 11 of the server device 1 causes the other client device associated with the session to return the generated response screen. That is, it is confirmed whether or not the client device 3 of the user B (monitoring person B) who monitors the operation of the user A (operating person A) exists. When the presence of the client device 3 of the user B (monitoring person B) is confirmed, the service providing means 11 displays the generated response screen as a client of the user A (operator A) as shown in a state transition diagram of FIG. At the same time, the service providing means 11 transmits the same response screen to the client device 3 of the user B (monitoring person B) associated with the session as well as returning to the device 2 (sequence Seq24). (Sequence Seq25).

  FIG. 12 is a state transition diagram illustrating an example of state transition in which the service providing unit 11 of the server apparatus 1 illustrated in FIG. 1 confirms the presence / absence of a related session related to the screen information transmission session. As shown in FIG. 12, the service providing means 11 of the server device 1 determines whether or not there is a related session of the screen information transmission session for the screen information transmission session with the client device 2 in the state ST11. Confirm (state ST11). If there is a related session, the process transits to the state ST12 and the related session that is set with the client device 3 has the same screen information as the screen information of the screen information transmission session with the client device 2. Is also instructed to transmit to the transmitter 13 (state ST12).

  Accordingly, the same screen as that transmitted to the client device 2 is also transmitted to the client device 3. That is, the client device 2 of the user A (operator A) receives the response screen returned from the service providing means 11 of the server device 1 at the receiving unit 23 and displays it on the display unit 24 to display the user A ( User B (monitoring person B) who monitors the operation of the user A (operator A) by using the transmission means 26 while presenting the response screen displayed on the display unit 24 while presenting to the operator A) To the client apparatus 3 (sequence Seq26).

  On the other hand, the client device 3 of the user B (monitoring person B) receives the response screen returned from the service providing means 11 of the server device 1 at the receiving unit 23, but unlike the client device 2 side at this time, The received response screen is merely temporarily stored, and the received response screen is not displayed on the display unit 34 yet. After that, when the response screen transmitted from the client device 2 is received by the receiving unit 37, the client device 3 receives the response screen received from the server device 1 temporarily held (here, expressed as an α screen). The response screen received from the client device 2 (here expressed as β screen) is transferred to the confirmation means 35 to check whether both screens (α screen, β screen) are the same screen (sequence Seq27). ).

  When the confirmation unit 35 confirms that both screens (α screen, β screen) are the same screen, the response screen (α screen) received from the server device 1 is displayed for the user B (monitor B). The display unit 34 is instructed to do so, and the response screen (α screen) is displayed on the display unit 34 and presented to the user B (monitoring person B) (sequence Seq28).

  With the above operation, even if the user A (operator A) performs some operation, the operation as schematically shown in FIG. 13 is performed, so the screen that the user A (operator A) is viewing and the user B The screen that the (monitoring person B) is looking at is synchronized with each other and becomes the same screen. FIG. 13 shows screen information transmitted / received among the server apparatus 1, the client apparatus 2 (first client apparatus), and the client apparatus 3 (second client apparatus) in the operations from sequence Seq21 to sequence Seq28 in FIG. It is the schematic diagram which showed typically the flow of this.

  In the schematic diagram of FIG. 13, when the user A (operator A) of the client apparatus 2 performs some operation using the input means 21, an input screen as shown in the sequence Seq22 of FIG. The data is transmitted from the device 2 to the server device 1. When the server device 1 receives the screen 1 from the client device 2, the server device 1 generates a response screen as shown in the sequences Seq 24 and Seq 25 in FIG. 3 as the screen 2 and transmits it to both the client device 2 and the client device 3. To do. When receiving the screen 1 from the server device 1, the client device 2 displays the screen on the display unit 24 and transmits the same screen as the screen 2 displayed on the screen as the screen 3 to the client device 3. The client device 3 confirms that the screen 2 received from the server device 1 and the screen 3 received from the client device 2 are the same screen, and displays the screen 2 received from the server device 1 on the display unit 34. To do.

  Next, an operation when the user B (monitoring person B) approves the operation content of the user A (operator A) will be described. When the user B (monitoring person B) approves the operation content of the user A (operator A), the user B (monitoring person B) presses the approval button on the operation screen displayed on the display unit 24 using the input unit 31 of the client device 3. When an operation such as operation is performed (sequence Seq31), it is transmitted as monitoring confirmation operation information from the transmission unit 32 of the client device 3 to the service providing means 11 of the server device 1 (sequence Seq32).

  When the server apparatus 1 receives the monitoring confirmation operation information of the user B (monitorer B) via the receiving unit 14, the service providing unit 11 that provides the existing service responds to the received monitoring confirmation operation information by the user B. After generating a confirmation screen to be returned to the client device 3 of (monitoring person B), the client device 3 further relates to another client device associated with the session to which the confirmation screen 12 is to be returned to the confirmation unit 12, that is, It is confirmed that the client device 2 of the user A (operator A) whose operation is monitored by the user B (monitorer B) is present (sequence Seq33). Here, the confirmation screen displays information indicating that the previous operation of the user A (operator A) has been approved by the user B (monitoring person B), and a confirmation button for confirming the operation Is generated as a screen that can be pressed by the user A (operator A).

  When the confirmation unit 12 confirms that the client device 2 of the user A (operator A) whose operation is monitored by the user B (monitorer B), the confirmation unit 12 notifies the service providing unit 11 of the user. The client apparatus 2 of A (operator A) is instructed to transmit the same screen.

  When the presence of the client device 2 of the user A (operator A) is confirmed, the service providing unit 11 returns the generated confirmation screen to the client device 3 of the user B (monitoring person B) (sequence Seq34). At the same time, the service providing unit 11 transmits the same confirmation screen to the client device 2 of the user A (operator A) associated with the session (sequence Seq35).

  The client device 3 of the user B (monitoring person B) receives the confirmation screen returned from the service providing means 11 of the server device 1 at the receiving unit 33 and displays it on the display unit 34 to display the user B (monitoring person). B) and the confirmation screen displayed on the display unit 34 using the transmission means 36, the client of the user A (operator A) who is monitoring the operation of the user B (monitorer B) It transmits to the apparatus 2 (sequence Seq36).

  On the other hand, the client device 2 of the user A (operator A) receives the confirmation screen returned from the service providing means 11 of the server device 1 at the receiving unit 23, but at this time, unlike the client device 3 side. The received confirmation screen is only temporarily stored, and the received confirmation screen is not displayed on the display unit 24 yet. After that, when the reception unit 27 receives the confirmation screen transmitted from the client device 3, the client device 2 receives the confirmation screen (herein referred to as a γ screen) received from the temporarily held server device 1. The confirmation screen received from the client device 3 (here expressed as δ screen) is transferred to the confirmation means 25 to confirm whether both screens (γ screen, δ screen) are the same screen (sequence Seq37). ).

  When the confirmation unit 25 confirms that both screens (γ screen, δ screen) are the same screen, the confirmation screen (γ screen) received from the server device 1 is displayed for the user A (operator A). The display unit 24 is instructed to do so, and the confirmation screen (γ screen) is displayed on the display unit 24 and presented to the user A (operator A) (sequence Seq38).

  By performing the operation as described above, the user B (operator A) and the user B (monitorer B) are visually confirming that the screens viewed by the user A (operator A) are synchronized with the user B ( The monitoring person B) can monitor the operation of the user A (operator A) in real time, and the user B (monitoring person B) confirms that the operation of the user A (operator A) has been approved. The screen can also be distributed to both the user A (operator A) and the user B (monitorer B), and can be confirmed on the same confirmation screen.

  Note that the service providing means 11 (or the confirmation means 12 in some cases) of the server device 1 does not always perform the operation shown in the state transition diagram of FIG. 12 in the screen information transmission session. Only for the screen for each point committed to the user, the screen confirmation can be performed between the client device 2 of the user A (operator A) and the client device 3 of the user B (monitoring person B). You may make it employ | adopt a mechanism. In such a case, the transmission operation of the same screen from the server device 1 such as the sequences Seq24 and Seq25 in the sequence diagram of FIG. 3 may not always be performed in real time, and the user A (operator A) There is a case where real-time screen sharing between the client device 2 and the client device 3 of the user B (monitor B) cannot be performed. However, at a point committed as an important operation, the screen is synchronized between the client device 2 of the user A (operator A) and the client device 3 of the user B (monitorer B). The operation of the user A (operator A) can be monitored by the user B (monitorer B).

(Explanation of effect of embodiment)
As described in detail above, the following effects are obtained in the present embodiment.

  First, in order to enjoy the Web service, the operation and the monitoring work must be divided into separate workers (operator and monitoring person). Even if you are far away from each other, the same screen is displayed synchronously for the operator and the supervisor, so the system can guarantee that both are working at the same time in real time. it can.

  Secondly, since the monitor employs a mechanism for monitoring the operation of the operator in real time and giving approval of the operation content, it is possible to prevent the operator from performing an incorrect operation in advance. Can do.

  Third, the session synchronization management mechanism in the present embodiment can be realized simply by adding a synchronization operation mechanism between an operator and a monitor to a general Web service, so that the implementation is performed at a low cost. Can do.

(Other embodiments)
Next, a system configuration example different from the system configuration of the Web service session synchronization management system shown in FIG. 1 will be described with reference to FIG. FIG. 14 is a system configuration diagram showing a system configuration example different from FIG. 1 of the Web service session synchronization management system according to the present invention, and the synchronization shown by hatching in the confirmation means 12 of the server device 1 of FIG. The operation control means 121 is newly added. The parts other than the addition of the synchronization operation control unit 121 in the confirmation unit 12 are the same as those in the Web service session synchronization management system shown in FIG. In this other embodiment, by adding a new synchronous operation control means 121 in the confirmation means 12, a mechanism for controlling contents that cannot be executed unless the same operation is performed in both related sessions is realized. ing.

  In this other embodiment, for example, a confirmation button 40 is newly added and arranged on the server setting screen shown in FIG. 10 as an example of the operation screen in the previous embodiment, as shown in FIG. The case where the content set in the server setting screen is confirmed when the confirm button 40 is pressed is targeted. FIG. 15 is a schematic diagram showing a screen configuration example different from FIG. 10 of the server setting screen displayed as an example of the operation screen on the display unit 24 of the client device 2 (first client device) shown in FIG. As described above, the confirmation button 40 is newly added to the server setting screen of FIG.

  Here, in this embodiment, the user A (operator A) simply presses the confirmation button 40 on the server setting screen shown in FIG. 15 displayed on the client device 2 as the operation screen. 16 is displayed on the client device 3 by the user B (monitoring person B) who monitors the operation of the user A (operator A). Only when the confirm button 40 is pressed down, the operation result on the server setting screen can be reflected and set in the server device 1 for the first time. That is, in this other embodiment, the case where the operation result becomes effective for the first time by the synchronous operation of both the user A (operator A) and the user B (monitorer B) is shown. FIG. 16 is a schematic diagram showing a screen configuration example different from FIG. 10 of the server setting screen displayed as an example of the operation screen on the display unit 34 of the client device 3 (second client device) shown in FIG. The screen configuration is the same as the server setting screen shown in FIG. 15 displayed on the client device 2 (first client device).

  Next, an operation concept of the synchronous operation control means 121 newly added in the confirmation means 12 of the server device 1 of FIG. 14 will be described with reference to the state transition diagram of FIG. FIG. 17 is a state transition diagram illustrating an example of state transition in the synchronous operation control unit 121 in the confirmation unit 12 of the server apparatus 1 illustrated in FIG. 14. When the confirmation means 12 is called from the service providing means 11, the synchronous operation control means 121 confirms the request before the main body side of the confirmation means 12 operates in response to the request from the client devices 2 and 3. Judging.

  As shown in FIG. 17, the synchronous operation control means 121 in the confirmation means 12 of the server device 1 first determines whether or not the request for confirmation is an operation that requires resource synchronization in the state ST51. Determine (state ST51). Such determination processing is performed by referring to the necessary authority setting table 110A shown in FIG. 18, for example. FIG. 18 is a table showing an example of the necessary authority setting table 110A held in the confirmation unit 12 of the server device 1 shown in FIG. As shown by hatching, the necessary authority setting table 110A shown in FIG. 18 includes “session: simultaneous operation” in the necessary authority 113 as compared to the necessary authority setting table 110 shown in FIG. "Has been added as a new required authority. That is, the necessary authority setting table 110A shown in FIG. 18 includes all the associated users (that is, the book) for operations related to a specific resource 111 (in the case of FIG. 18, “/ res8”) among the resources 111. In the case of another embodiment, it is defined that simultaneous operation by both user A (operator A) and user B (monitorer B) is necessary.

  When it is determined in the state ST51 of FIG. 17 that simultaneous operation is not necessary, the state transitions to the state ST52, and subsequent confirmation processing is delegated to the body of the confirmation unit 12 (state ST52). The transferred confirmation means 12 performs an operation as shown in the state transition diagrams of FIGS. 6 and 7 as in the case described in the previous embodiment.

  On the other hand, when it is determined in the state ST51 of FIG. 17 that the simultaneous operation is necessary, the state transitions to the state ST53 to check whether or not there is a synchronization target session (state ST53). . If there is no session to be synchronized, the synchronization operation cannot be performed in the first place, so the state transitions to the state ST55 and a response indicating that the requested operation cannot be performed is returned to the request source. To the service providing means 11 (state ST55).

  On the other hand, if there is a synchronization target session, the state transitions to the state ST54, and whether or not the corresponding synchronization target session is performing the same operation, that is, accessing the same resource by the same method. Is confirmed (state ST54). As will be described later, the confirmation that the session on the side that performed the operation is in a waiting state indicating that it waits for the operation of the session that will be performed later, as described later. This is done by confirming that it is in a standby state.

  Here, if the session to be synchronized has not performed the confirmation operation first and is not in the standby state, the session transits to the state ST56, and its own session enters the standby state to perform the resource operation. A certain thing is held in the session (using a session variable or the like) and waits (that is, loop processing returning to the confirmation operation of state ST54 is repeated). On the other hand, if the session to be synchronized has transitioned to the operation standby state where the operation is waited for, the process transits to the state ST57 to indicate that the session is in the operation execution state for performing the resource operation. After being held (state ST57), the state transitions to state ST58, and the service providing means 11 is instructed to perform the resource operation (state ST58).

  After that, when the state transitions to the state ST59 and the operation of the synchronous operation control unit 121 ends, the service providing unit performs the resource operation and returns the generated response to all clients to be synchronized (state ST59). Thus, all the users who need the synchronization operation (that is, in the case of this other embodiment, both the user A (operator A) and the user B (monitoring person B)) do not operate, It is possible to realize processing that cannot be operated, and to maintain synchronization with a return screen that displays the response returned from the server device 1 on the screen.

  The configuration of the preferred embodiment of the present invention has been described above. However, it should be noted that such embodiments are merely examples of the present invention and do not limit the present invention in any way. Those skilled in the art will readily understand that various modifications and changes can be made according to a specific application without departing from the gist of the present invention.

1 server device 2 client device (first client device)
3 Client device (second client device)
DESCRIPTION OF SYMBOLS 11 Service provision means 12 Confirmation means 13 Transmission part 14 Reception part 21 Input means 22 Transmission part 23 Reception part 24 Display part 25 Confirmation means 26 Transmission means 27 Reception means 31 Input means 32 Transmission part 33 Reception part 34 Display part 35 Confirmation means 36 Transmitting means 37 Receiving means 40 Confirm button 100 Session information table 101 Session ID
102 Terminal Identification Information 103 Related Information 104 Relevance Information 110 Required Authority Setting Table 110A Required Authority Setting Table 111 Resource (URI)
112 Operation (Method)
113 Required authority 121 Synchronous operation control means 200 User association table 201 User ID
202 User ID for monitoring login

Claims (10)

A server device that provides a Web service; a first client device that includes means for enjoying the Web service via a session with the server device; a unit that transmits and receives information to and from the first client device; A second client device comprising means for transmitting and receiving information to and from the server device via a session associated with a session of one client device, and both the first client device and the second client device A web service session synchronization management system for synchronizing the sessions of
The server device
When creating a session with the first client device, check whether a session with the second client device associated with the session has been created,
If a session with the second client device has not yet been generated when a session with the first client device is generated, it is impossible to operate as a response to the first client device. Return an empty screen,
In addition, after the session with the first client device is generated, when the session with the second client device is generated, or the session with the second client device already exists. In this case, when a session with the first client device is generated, an operation screen that can be operated is transmitted to the first client device, and at the same time, to the second client device. A Web service session synchronization management system, wherein the same operation screen as the operation screen transmitted to the first client device is returned. The server device
Whether or not there is a session of the second client device associated with the session of the first client device when receiving an input screen indicating that some operation has been performed from the first client device. check,
When a session of the second client device exists, a response screen serving as a response to the input screen from the first client device is generated and sent back to the first client device. 2. The Web service session synchronization management system according to claim 1, wherein the same screen as the response screen is transmitted to the second client device as a second client response screen. 3. The first client device is:
When the response screen is received from the server device, the received response screen is displayed on a display unit and presented to the user, and the response screen is transmitted to the second client device. The Web service session synchronization management system according to claim 2, wherein: The second client device is
The second client response screen received from the server device and the response screen transmitted from the first client device are collated and received from the server device when both are the same screen. The Web service session synchronization management system according to claim 3, wherein the second client response screen is displayed on the screen and presented to the user. The server device
For each operation target resource, the fact that the same operation from both the first client device and the second client device is required is held in advance as a session simultaneous operation, and either one of the first client device When receiving the input screen indicating the resource operation request, check whether the resource that is the target of the resource operation request corresponds to the resource of the session simultaneous operation,
When the resource that is the target of the resource operation request corresponds to the resource for the simultaneous session operation, an input screen that indicates a resource operation request for the same resource as the input screen from the first client device is displayed. Until receiving from the second client device, wait for the operation requested by the input screen,
When an input screen indicating a resource operation request related to the same resource as the input screen from the first client device is received from the second client device, an operation requested by the input screen is performed on the resource. 5. The Web service session synchronization management system according to claim 1, wherein A server device that provides a Web service; a first client device having a step of enjoying the Web service via a session with the server device; a step of transmitting / receiving information to / from the first client device; And a second client device having a step of transmitting and receiving information to and from the server device via a session associated with the session of the client device, and a session between both the first client device and the second client device. A web service session synchronization management method in a web service session synchronization management system that performs synchronization of
The server device
When creating a session with the first client device, check whether a session with the second client device associated with the session has been created,
If a session with the second client device has not yet been generated when a session with the first client device is generated, it is impossible to operate as a response to the first client device. Return an empty screen,
In addition, after the session with the first client device is generated, when the session with the second client device is generated, or the session with the second client device already exists. In this case, when a session with the first client device is generated, an operation screen that can be operated is transmitted to the first client device, and at the same time, to the second client device. And returning the same operation screen as the operation screen transmitted to the first client device. The server device
Whether or not there is a session of the second client device associated with the session of the first client device when receiving an input screen indicating that some operation has been performed from the first client device. check,
When a session of the second client device exists, a response screen serving as a response to the input screen from the first client device is generated and sent back to the first client device. The Web service session synchronization management method according to claim 6, wherein the same screen as the response screen is transmitted to the second client device as a second client response screen. The first client device is:
When the response screen is received from the server device, the received response screen is displayed on a display unit and presented to the user, and the response screen is transmitted to the second client device. The Web service session synchronization management method according to claim 7, wherein: The second client device is
The second client response screen received from the server device and the response screen transmitted from the first client device are collated and received from the server device when both are the same screen. The Web service session synchronization management method according to claim 8 , wherein the second client response screen is displayed on a screen and presented to the user. A Web service session synchronization management program for causing a computer to execute the Web service session synchronization management method according to claim 6.

Images