JP2015165425A - Information processing device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To preliminarily generate an application execution environment corresponding to a type of a client device according to a preregistered schedule, even when a user uses a plurality of types of client devices.SOLUTION: A management server 1 determines whether a clock-time reaches a predetermined period before a preset activation start clock-time for various types of client devices which a user uses, and requests a server 2 to generate an application execution environment corresponding to one client device used by the user, if it is determined that the clock-time reaches the predetermined period before the activation start clock-time for the one client device. The server 2 discards unnecessary application execution environments from a storage device and generates the requested application execution environment. The management server 1 performs time adjustment so as to delay the preset activation start clock-time for the one client device if another client device used by the user is currently connected.

Description

  The present invention relates to a server device that generates an application execution environment of a client device, a client device that uses the application execution environment generated by the server device, a remote connection system in which the server device and the client device are remotely connected, and a program And about.

  In recent years, thin client systems that manage resources such as application software and files on the server computer side have been used in an information system of a company, etc., with a computer (client computer) used by employees having only minimum functions. ing.

  Generally, a thin client system includes a server computer and a plurality of client computers that are remotely connected to the server computer. The server computer generates an application execution environment of each client computer, and the client computer is remotely connected to the server computer and executes various tasks in the application execution environment of the server computer. At this time, the process for generating and making the application execution environment available on the server computer takes time, and the server resources (CPU, memory, etc.) continue to be occupied while the application execution environment is alive.

  Patent Document 1 discloses a technique for a remote connection system that allows a client computer that makes a remote connection request to immediately use a virtual desktop environment without wasting resources of a server computer that provides a terminal service. Yes. Specifically, the operation schedule (start time and end time) of the application execution environment (virtual desktop environment) of the client computer connected to the server computer is registered in the management server, and the management server is based on this operation schedule. The startup time of each client computer is monitored, and a remote connection request is made to the server computer before the startup time of the client computer to generate a virtual desktop environment in advance. When the server computer actually receives a remote connection request from the client computer at the start time, the server computer immediately connects and uses the already generated virtual desktop environment. In addition, the management server checks the connection state with the client computer after the end time set in the operation schedule of each client computer, and if the remote connection is disconnected, the server computer displays the virtual desktop of the client computer. Destroy the environment and free up resources. As a result, the virtual desktop environment can be used immediately when connecting remotely from the client according to the operation schedule, resources for the application execution environment that is no longer needed are released, and multiple client computers connect to the server computer. Even in this case, efficient operation can be achieved.

JP 2006-91954 A

  However, the above-described remote connection system in Patent Document 1 aims to generate and destroy an application execution environment corresponding to one type of client computer with a set of operation schedules (start time, end time). When the user uses different types of client computers (terminals) with different application execution environments according to time (for example, using a personal computer (PC) in the office in the morning, using a mobile terminal in the afternoon, and then returning to the office) In the case of using a PC), there is a problem that it is impossible to quickly cope with the proper use of each client computer.

  An object of the present invention is to enable pre-generation of an application execution environment according to a type of a client device in accordance with a pre-registered schedule even when a user uses a plurality of types of client devices (client computers). That is.

  The invention according to claim 1 is a server device that generates an execution environment of applications of various client devices used by a user, and each of the various client devices used by the user has a startup start time set in advance. When it is determined by the time determination means that determines whether or not a predetermined time has passed before and the time determination means that the predetermined time has passed before the activation start time for one client device used by the user, Generating means for generating an execution environment of an application corresponding to the client device.

  According to a second aspect of the present invention, in the server device according to the first aspect, when it is determined by the time determination means that one client device used by the user is a predetermined time before the activation start time, It comprises connection determination means for determining whether any of various client devices used by a user is connected to a server device, and the generating means uses various clients used by the user by the connection determination means When it is determined that none of the devices is connected to the server device, an execution environment for an application corresponding to the one client device is generated.

  According to a third aspect of the present invention, in the server device according to the second aspect, the execution environment storage unit for each user that stores the execution environment data of the application of the client device generated for each user, and the connection determination unit When it is determined that none of the various client devices used by the user is connected to the server device, when the data corresponding to the user is stored in the user-specific execution environment storage unit, the user-specific execution environment And a discarding unit for discarding data corresponding to the user from the storage unit.

  According to a fourth aspect of the present invention, in the server device according to the second or third aspect, the connection determination unit determines that any of various client devices used by the user is connected to the server device. In this case, a time adjustment unit is provided that sets a predetermined activation start time for the one client device to be delayed by a predetermined time to obtain a new activation start time.

  According to a fifth aspect of the present invention, in the server device according to any one of the first to fourth aspects, the server device includes an application execution environment storage unit that stores data related to an execution environment of the application for each type of client device, and the generation The means generates an application execution environment adapted to the type of client device based on the data stored in the application execution environment storage means.

  According to a sixth aspect of the present invention, in the server device according to any one of the first to fifth aspects, when receiving a connection request from a client device, receiving means for receiving data indicating the type of the client device; When the data indicating the type of the client device is received by the receiving unit, if the execution environment of the application adapted to the type is already generated by the generating unit, screen data corresponding to the execution environment is transmitted to the client device. And when the data indicating the type of the client device is received by the receiving means, if the execution environment of the application adapted to the type is not generated by the generating means, the generating means Generate an application execution environment adapted to.

  According to a seventh aspect of the present invention, there is provided transmission means for transmitting data indicating a type of a client device to the server device when connected to the server device, and screen data corresponding to an execution environment of an application adapted to the type of the server device. Receiving means from the apparatus, and when connecting to the server according to a preset operation schedule, the receiving means corresponds to the execution environment of the application generated in advance in the server apparatus before the connection Receive screen data.

  The invention according to claim 8 is a server apparatus according to any one of claims 1 to 6 and a client apparatus that is remotely connected to the server apparatus and uses an execution environment of an application generated by the server apparatus. And a remote connection system configured by

  According to a ninth aspect of the present invention, there is provided a time determination means for determining whether or not a predetermined time before the start-up time set in advance for each of the various client devices used by the user. When it is determined by the means that the one client device used by the user is a predetermined time before the activation start time, it serves as a generating means for generating an execution environment of the application corresponding to the one client device. It is a program.

  According to the tenth aspect of the present invention, there is provided a transmitting means for transmitting data indicating a type of a client device to the server device when the computer is connected to the server device, and screen data corresponding to an execution environment of an application adapted to the type. When the client device connects to the server according to a preset operation schedule, the receiving device is generated in advance in the server device before the connection. A program for receiving screen data corresponding to an application execution environment.

  According to the present invention, even when one user uses a plurality of types of client devices, an application execution environment corresponding to the client device is generated in advance according to the start start time set in advance for each client device. Thus, each client device can immediately use the application execution environment, and the use environment of the client device for the user can be improved.

The figure which shows the whole structure of the remote connection system which concerns on embodiment of this invention. The block diagram which shows the principal part structure of the management server which concerns on this embodiment. The figure which shows the data structure of the user schedule memorize | stored in the memory | storage device of the management server. The figure which shows an example of the setting content of a user schedule. The figure which shows the data structure of the execution environment schedule memorize | stored in the memory | storage device of the management server. The block diagram which shows the principal part structure of the server which concerns on this embodiment. The figure which shows the data structure of the execution environment table memorize | stored in the memory | storage device of the server. The figure which shows the data structure of the session state table memorize | stored in the memory | storage device of the server. The block diagram which shows the principal part structure of the client apparatus which concerns on this embodiment. The flowchart which shows the process performed in a client apparatus at the time of the connection to a server. The flowchart which shows the process performed in a server when receiving a connection request from a client apparatus. 12 is a flowchart showing details of application execution environment generation processing shown in FIG. 11. The flowchart which shows the process performed in a management server. The flowchart which shows the process performed in a server, when the inquiry of a session state is received from a management server. The flowchart which shows the detail of the application execution environment destruction process shown in FIG. The figure which shows an example of transition of a user's application execution environment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
First, the configuration in the present embodiment will be described.

  FIG. 1 shows an overall configuration of a remote connection system 100 according to an embodiment of the present invention. As shown in FIG. 1, the remote connection system 100 includes a management server 1, a server 2, and client devices 3 to 5, which are connected to a communication network N such as a LAN (Local Area Network) or a WAN (Wide Area Network). Connected through.

  The server 2 is a device that generates an application execution environment (hereinafter referred to as an application execution environment) used by the client devices 3 to 5. Here, the “application execution environment” is an environment for executing an application program on the server 2 in accordance with input data (command or the like) transmitted from the client device. The client devices 3 to 5 are terminals such as PCs (Personal Computers), portable terminals, and barcode readers used by users (for example, employees of the company) for business, and use the application execution environment generated by the server 2 To do. The management server 1 is a computer that manages the server 2 and the client devices 3 to 5.

  In the present embodiment, a single user uses a plurality of types of client devices (for example, a PC, a portable terminal, a barcode reader, etc.) for business purposes, and each client device is selectively used according to a time zone. The type and number of client devices used by one user for business are not particularly limited. The number of client devices connected to one server 2 via the communication network N is not particularly limited.

  FIG. 2 shows a main part configuration of the management server 1. As illustrated in FIG. 2, the management server 1 includes a communication unit 10, an input unit 11, a display unit 12, a control unit 13, and a storage device 14, and each unit is connected via a bus 15.

  The communication unit 10 performs communication control for connecting the management server 1 to the communication network N. The input unit 11 includes input devices such as a mouse and a keyboard, and outputs an operation signal from the input device to the control unit 13. The display unit 12 includes a display such as an LCD (Liquid Crystal Display), and performs a required display process in accordance with a control signal input from the control unit 13.

  The control unit 13 includes a CPU (Central Processing Unit) and the like, and controls the operation of each unit of the management server 1 according to various programs stored in the storage device 14.

  The storage device 14 stores various programs executed by the control unit 13, data used when the pro program is executed, and the like. As shown in FIG. 2, the storage device 14 includes a user schedule storage unit 16 and an execution environment schedule storage unit 17.

  The user schedule storage unit 16 stores business schedule data for each user (user A, user B,...). The schedule data of each user is registered in the user schedule storage unit 16 as needed by operating the input unit 11 of the management server 1 or from the client device via the communication network N.

  FIG. 3 shows the data structure of the user schedule stored in the user schedule storage unit 16. FIG. 4 shows an example of setting contents (setting screen) of the user schedule.

  The user schedule represents the operation schedule of the use terminal for each use terminal (client device) of the user, and as shown in FIG. 3, the user schedule includes items of date, start time, end time, use place, and use terminal. The In the user schedule, the date item is the date of the schedule to be registered, the start time item is the start start time of the terminal, the end time item is the time to end use of the terminal, the use place item is the use place of the terminal, and the use terminal The item indicates the type of terminal to be used. The setting contents shown in FIGS. 4A and 4B are stored in the user schedule storage unit 16 as indicated by 161 and 162 in FIG.

  The execution environment schedule storage unit 17 stores, for each user (user A, user B,...), Execution environment schedule data indicating a schedule for generating / destroying the application execution environment of each client device to be used. The execution environment schedule data is created based on the user schedule registered in the user schedule storage unit 16.

  FIG. 5 shows an example of data in the process of creating a user execution environment schedule based on the user schedule shown in FIG. 3 and data after creation. As shown in FIG. 5, the execution environment schedule is composed of items of default setting, terminal used, start time, and end time. In FIG. 5, the default setting item indicates whether or not other corresponding items (use terminal, start time, and end time items) are default settings. A default setting item with a circle indicates a default setting, and a blank item indicates a setting corresponding to a user schedule.

  As shown in FIG. 5 (a), the execution environment schedule storage unit 17 has default data for the PC used at the office desk with a start time of 9:00 and an end time of 17:00 corresponding to the user's working hours. Is preset. In FIG. 5A, when the schedule of 161 in FIG. 3 (schedule of using a barcode reader terminal at 10:00 to 12:00) is reflected, as shown in FIG. Settings are split. Similarly, in FIG. 5B, when the schedule of 162 in FIG. 3 (schedule for using the portable terminal at 13: 00 to 15:00) is reflected, the result is as shown in FIG.

  Note that even if two different schedules with continuous time are used in the same terminal, the execution environment schedule is regarded as one schedule. For example, if there is a schedule for using a portable terminal at a destination c at 10:00 to 12:00 and a schedule for using the same portable terminal at a destination d at 12:00 to 14:00, It is put together into one schedule of using a portable terminal from 10:00 to 14:00.

  FIG. 6 shows a main part configuration of the server 2. As shown in FIG. 6, the server 2 includes a communication unit 20, a control unit 21, and a storage device 22, and each unit is connected via a bus 23.

  The communication unit 20 performs communication control for connecting the server 2 to the communication network N. The control unit 21 includes a CPU and the like, and controls the operation of each unit of the server 2 according to various programs stored in the storage device 22.

  The storage device 22 stores various programs executed by the control unit 21, data used when the pro program is executed, and the like. As illustrated in FIG. 6, the storage device 22 includes an authentication information storage unit 24, an application execution environment storage unit 25, an application storage unit 26, a session state storage unit 27, and a user-specific application execution environment storage unit 28.

  The authentication information storage unit 24 stores user ID and password data for each user as authentication information when each user's client device connects to the server 2.

  The application execution environment storage unit 25 has an execution environment table that stores data related to the application execution environment according to the type (terminal type) of the client device connected to the server 2. FIG. 7 shows the data configuration of the execution environment table stored in the application execution environment storage unit 25. As shown in FIG. 7, the execution environment table stores items of application, width, and height in association with each terminal type. In the execution environment table, the application item indicates an application executed on the corresponding terminal, and the width item and the height item indicate the width and height of the screen size of the corresponding terminal, respectively. When the server 2 generates the application execution environment of the connected client device, the server 2 starts an application adapted to the terminal type of the client device in accordance with the screen size having the width and height specified in the execution environment table. Generate.

  The application storage unit 26 stores data of applications (word processors, mailers, barcode readers, etc.) adapted to various types of client devices.

  The session state storage unit 27 has a session state table indicating the session state (connection state) of the client device for each user. FIG. 8 shows the data structure of the session state table stored in the session state storage unit 27. As shown in FIGS. 8A and 8B, the session state table stores the user name, execution environment, and session state items in association with each other. In the session state table, the user name item indicates data (for example, user ID) for identifying the user, and the execution environment item is an identifier of the application execution environment stored in the user-specific application execution environment storage unit 28 described later. The session status item indicates the session status of the client device used by the user.

  Here, when no application execution environment is generated for any of various client devices used by a single user, there is no data corresponding to the user in the session state table. On the other hand, when the application execution environment of the client device used by the user is generated and the client device is connected to the server 2, as shown in FIG. 8A, the session status item corresponding to the user includes “ "Connected" is set. When the application execution environment is generated but the client device is not connected to the server 2, as shown in FIG. 8B, “disconnected” is set in the session state item corresponding to the user.

  When the authenticated user data exists in the session state table, the server 2 immediately performs a remote connection operation using the user application execution environment stored in the user-specific application execution environment storage unit 28. be able to.

  The user-specific application execution environment storage unit 28 stores the generated application execution environment data for each user (user A, user B,...). As shown in FIG. 8B, the data of the application execution environment in which “disconnected” is set in the session state item of the session state table is deleted from the application execution environment storage unit 28 for each user. Thereby, the resources of the server 2 are released.

  FIG. 9 shows a main part configuration of the client apparatus 3. Since the other client apparatuses 4 and 5 have the same configuration, description thereof is omitted here. As shown in FIG. 9, the client device 3 includes a communication unit 30, an input unit 31, a display unit 32, a control unit 33, and a storage device 34, and each unit is connected via a bus 35.

  The communication unit 30 performs communication control for connecting the client device 3 to the communication network N. The input unit 31 includes a mouse, a keyboard, a touch panel, a barcode reader, and the like, and outputs operation signals generated by these operations to the control unit 33. The display unit 32 includes a display such as an LCD, and performs a required display process in accordance with a control signal input from the control unit 33.

  The control unit 33 includes a CPU and the like, and controls the operation of each unit of the client device 3 according to various programs stored in the storage device 34.

  The storage device 34 stores various programs executed by the control unit 33, data used when the pro program is executed, and the like. The storage device 34 includes a terminal type storage unit 36 that stores data of the type (terminal type) of the client device 3, and a display content storage unit 37 that stores screen data received from the server 2 as an execution result of the application. Have.

Next, the operation in this embodiment will be described.
First, processing executed under the control of the control unit 33 in the client device (the client device 3 used by the user A) when connecting to the server 2 will be described with reference to the flowchart of FIG.

  First, the user ID and password of user A necessary for authentication at the time of connection are input by the input unit 31 and transmitted to the server 2 (step S1). When an error message indicating that the authentication result is NG is notified from the server 2 (step S2; NO), this process ends. On the other hand, when it is notified from the server 2 that the authentication result is OK (step S2; YES), the terminal type data stored in the terminal type storage unit 36 is read out and transmitted to the server 2 ( Step S3).

  After transmitting the terminal type data, the client apparatus 3 waits for reception of screen data from the server 2 (step S4). When screen data corresponding to the application execution environment adapted to the terminal type of the client device 3 is received from the server 2 (step S4; YES), the screen data is stored in the display content storage unit 37 and displayed on the display unit 32. (Step S5).

  Here, when the client device 3 is connected to the server 2 in accordance with the execution environment schedule stored in the execution environment schedule storage unit 17 of the management server 1, the application execution environment corresponding to the client device 3 has already been generated in the server 2. Therefore, the time until the screen data is received from the server 2 after transmitting the terminal type data is shortened.

  There is an input operation from the input unit 31 while the screen data received from the server 2 is being displayed (step S6; YES, step S4; NO), and the input operation does not request session disconnection (step S7; NO) ), Input data (command or the like) by the input operation is transmitted to the server 2 (step S8).

  When screen data indicating the execution result of the application corresponding to the input data is received from the server 2 (step S4; YES), the screen data is stored in the display content storage unit 37 and displayed on the display unit 32. (Step S5). While there is no input operation from the input unit 31 (step S6; NO), the same screen data is continuously displayed.

  When the input operation from the input unit 31 requests session disconnection (step S7; YES), a message requesting the session disconnection is transmitted to the server 2 (step S9), and this process ends.

  Next, referring to the flowchart of FIG. 11, processing that is executed in the server 2 under the control of the control unit 21 when receiving a connection request from a client device (the client device 3 used by the user A). Will be described.

  When the user ID and password of the user A are received from the client device 3 of the user A (step S20; YES), an authentication process is performed by collating with the data stored in the authentication information storage unit 24 (step S21). ). If the authentication result in step S21 is NG (step S22; NO), an error message is transmitted to the client device 3, and this process ends. On the other hand, when the authentication result in step S21 is OK (step S22; YES), a message notifying that the authentication result is OK is transmitted to the client device 3 (step S24).

  Next, data indicating the terminal type is received from the client device 3 that has confirmed that the authentication result is OK (step S25). Next, by referring to the user-specific application execution environment storage unit 28, it is determined whether or not an application execution environment adapted to the terminal type of the client device 3 of the user A has been generated (step S26).

  In step S26, when it is determined that the application execution environment has not been generated (step S26; NO), processing for generating the application execution environment is performed (step S27), and the generated application execution environment corresponds to the generated application execution environment. The screen data is transmitted to the client device 3 (step S29). The application execution environment generation process in step S27 will be described in detail later with reference to FIG.

  If it is determined in step S26 that the application execution environment has been generated (step S26; YES), the session state item corresponding to the user A application execution environment is “connected” in the session state table of the session state storage unit 27. (Step S28), and screen data corresponding to the application execution environment is transmitted to the client device 3 (step S29).

  If input data is received from the client device 3 after transmission of the screen data in step S29 (step S30; YES), if the input data does not request session disconnection (step S31; NO), the input data Is passed to the activation application and processed (step S32). Then, the screen data representing the execution result of the application in step S32 is transmitted to the client device 3 (step S33), the process returns to step S30, and a waiting state for data received from the client device 3 is entered.

  When the input data from the client device 3 requests session disconnection (step S31; YES), the session state item corresponding to the user A application execution environment is “disconnected” in the session state table of the session state storage unit 27. (Step S34), and this process ends.

  Next, the application execution environment generation process in step S27 of FIG. 11 will be described with reference to the flowchart of FIG.

  First, an application execution environment adapted to the terminal type received in step S25 of FIG. 11 is acquired from the execution environment table stored in the application execution environment storage unit 25 (step S40).

  Next, a resource (such as a storage area of the user-specific application execution environment storage unit 28) for the application execution environment acquired in step S40 is acquired, and the application storage unit has a screen size with the width and height specified in the execution environment table. The application execution environment is generated by starting the application stored in 26 (step S41). The application execution environment data generated in step S41 is stored in the user-specific application execution environment storage unit 28.

  When the application execution environment is generated, the session state item corresponding to the corresponding user application execution environment is set to “connected” in the session state table of the session state storage unit 27 (step S42). Processing ends.

  Next, processing executed under the control of the control unit 13 in the management server 1 will be described with reference to the flowchart of FIG.

  In the following, it is assumed that the management server 1 monitors each user's execution environment schedule stored in the execution environment schedule storage unit 17 at predetermined time intervals (δ (minutes)). Further, even if there is a difference depending on the contents of the execution environment, a sufficient time required for the application execution environment generation processing in the server 2 is defined as α (minute).

  In the management server 1, at the monitoring time, by referring to the execution environment schedule of each user stored in the execution environment schedule storage unit 17, has the start time −α been reached for each client device used by each user? It is determined whether or not (step S50). If it is determined in step S50 that one client device used by user A (referred to as client device 3) has reached the start time -α (step S50; YES), the server 2 corresponds to user A. A session status inquiry is made (step S51).

  When there is no session state data corresponding to the user A in the server 2, the application execution environment is the same as the discarded state, and therefore a message notifying the completion of discarding is received from the server 2 as the inquiry result of step S 51. Then, a message requesting an application execution environment adapted to the terminal type of the client device 3 of the user A is transmitted to the server 2 (step S58).

  If the server 2 has a session state that is being connected to the user A (that is, if there is a connected client device used by the user A), the server 2 indicates that the server 2 cannot discard it as a result of the inquiry in step S51. A message to be notified is received (step S53; YES), and time adjustment is performed by delaying the start time of the client device 3 by δ to be a new start time (step S54). By delaying the start time by δ, the session status is inquired again at the next monitoring time (after δ).

  When the disconnected session state exists for the user A in the server 2, a message notifying that the disconnected session state exists is received from the server 2 as the inquiry result of step S51 (step S55). After receiving the notification in step S55, a message requesting destruction of the application execution environment whose session state is set to disconnected is transmitted to the server 2 (step S56).

  When the server 2 completes the destruction of the corresponding application execution environment and receives a message from the server 2 indicating the completion of the destruction (step S57; YES), the application execution environment corresponding to the client device 3 of the user A is generated. The requested message is transmitted to the server 2 (step S58). The processes of steps S51 to S58 are performed for all users whose execution environment schedules are registered in the execution environment schedule storage unit 17, and when the processes of steps S51 to S58 are completed for all users (step S59; YES), Processing ends.

  Next, processing executed under the control of the control unit 21 in the server 2 when receiving an inquiry about the session state from the management server 1 will be described with reference to the flowchart of FIG.

  When there is an inquiry about the session state of the user (user A) from the management server 1 (step S60; YES), the session state of the user A is referred to by referring to the session state table stored in the session state storage unit 27. It is determined whether there is any data (step S61).

  If it is determined in step S61 that the session state data of user A does not exist (step S61; NO), the application execution environment is the same as the discarded state, so the management server 1 is notified of the completion of the destruction. Is transmitted (step S67).

  If it is determined in step S61 that there is data on the session state of user A (step S61; YES), it is determined whether or not the session state is set during connection (step S62). In step S62, when it is determined that the session state is set to be connected (step S62; YES), a message is sent to the management server 1 to notify the user A that the connected application execution environment cannot be discarded. (Step S63), and this process ends.

  If it is determined in step S62 that the session state is set to disconnected (step S62; NO), a message notifying that the session state of the user A is disconnected is transmitted to the management server 1 ( Step S64).

  After the notification in step S64, when a message is received from the management server 1 requesting the destruction of the application execution environment whose session state is set to disconnect for the user A (step S65; YES), the application execution environment storage for each user is stored. Processing for discarding the user A application execution environment stored in the unit 28 is performed (step S66). The application execution environment discarding process in step S66 will be described in detail later with reference to FIG.

  When the application execution environment discarding process is completed, a message notifying the completion of discarding is transmitted to the management server 1 (step S67). When a message requesting generation of the application execution environment corresponding to the user A's client device 3 is received from the management server 1 after the discard completion notification in step S67 (step S68; YES), the terminal type of the client device 3 is set. An adaptive application execution environment generation process is performed (step S69), and this process ends. Since the process in step S69 is the same as the process shown in FIG. 12, a description thereof is omitted here.

  Next, the application execution environment discarding process in step S66 of FIG. 14 will be described with reference to the flowchart of FIG.

  First, the application execution environment data of the user corresponding to the discard request is discarded (deleted) from each user's application execution environment stored in the user-specific application execution environment storage unit 28 (step S80). As a result, resources for the application execution environment that are no longer needed are released. After step S80, the user data is deleted from the session state table stored in the session state storage unit 27 (step S81), and the application execution environment discarding process ends.

  FIG. 16 shows the transition of the application execution environment according to the execution environment schedule shown in FIG. In FIG. 16, the horizontal axis represents the time axis, and reference numerals 71 to 76 indicate the generation / destroy timing of the application execution environment.

  As described above, according to the remote connection system 100 of this embodiment, even when one user uses a plurality of types of client devices, each of the users can be dynamically changed according to the execution environment schedule registered in the management server 1. By generating an appropriate application execution environment corresponding to the client device in advance (before the start time set in the schedule), each client device immediately creates the application execution environment generated by the server 2. It can be used. Thereby, the utilization environment of the client apparatus for the user can be improved.

  Further, when none of the various client devices used by the user is connected to the server 2, an efficient generation process can be performed by generating an application execution environment corresponding to one client device whose start time is approaching. It becomes possible.

  Further, by discarding the application execution environment that is no longer needed, the resources of the server 2 are released, and the resources of the server 2 can be used efficiently and effectively.

  Furthermore, when the start time of one client device used by the user approaches the other client device used by the user, the execution environment schedule is set for the one client device. By delaying the start time and making it possible to inquire about the user's session status again at the next monitoring time, the actual start time of the client device becomes later than the start time set in the execution environment schedule. Can also respond flexibly.

  Also, by generating in advance an application execution environment adapted to the type of client device, the client device can immediately use an application execution environment that is optimal for the device.

Note that the description in the present embodiment can be changed as appropriate without departing from the spirit of the present invention.
For example, in the present embodiment, the present embodiment has a configuration in which the management server 1 and the server 2 are provided separately, but the functions of both servers may be realized by a single device (server device). In this case, in FIG. 13 and FIG. 14, processing such as a session state inquiry, a discard impossible notification, a discard completion notification, an execution environment discard request, and an execution environment generation request is omitted.

DESCRIPTION OF SYMBOLS 1 Management server 2 Server 3, 4, 5 Client apparatus 10, 20, 30 Communication part 11, 31 Input part 12, 32 Display part 13, 21, 33 Control part 14, 22, 34 Storage apparatus 16 User schedule memory | storage part 17 Execution Environment schedule storage unit 24 Authentication information storage unit 25 Application execution environment storage unit 26 Application storage unit 27 Session state storage unit 28 User-specific application execution environment storage unit 36 Terminal type storage unit 37 Display content storage unit 100 Remote connection system

The present invention relates to an information processing apparatus.

An object of the present invention is to enable appropriate processing to be performed in a time corresponding to each of a plurality of time zones .

The invention according to claim 1 is an information processing device that controls generation of information for a plurality of terminal devices, and stores terminal type information of the terminal device used in each time zone for each of a plurality of different time zones. A time zone storage unit; a determination unit that determines whether the current time has approached a start time of any one of the plurality of time zones stored in the time zone storage unit; and the determination unit When it is determined that any of the time zones has been approached, the terminal type information stored in the time zone storage means corresponding to the time zone is acquired, and a plurality of types of terminal devices are acquired based on the terminal type information. A terminal device of any type is specified, and control is performed so that information specific to the terminal type specialized for the specified type of terminal device is generated prior to the start time of the time period. Production control means and the production means The information, characterized by comprising a transmitting means for transmitting to the terminal device identified by the terminal type information.

According to the present invention, it is possible to automatically perform appropriate processing at a time corresponding to each of a plurality of time zones .

Claims (10)

A server device that generates an application execution environment of various client devices used by a user,
For each of the various client devices used by the user, time determination means for determining whether or not a predetermined time before the preset start time is reached,
A generating unit configured to generate an execution environment of an application corresponding to the one client device when the time determining unit determines that the one client device used by the user is a predetermined time before the activation start time;
A server device comprising: If it is determined by the time determination means that one client device used by the user is a predetermined time before the start time, any one of various client devices used by the user is connected to the server device. Connection determination means for determining whether or not
The generation unit generates an execution environment for an application corresponding to the one client device when the connection determination unit determines that none of the various client devices used by the user is connected to the server device. The server device according to claim 1. A user-specific execution environment storage unit that stores data of an application execution environment of the client device generated for each user;
When it is determined by the connection determination means that none of the various client devices used by the user is connected to the server device, data corresponding to the user is stored in the user-specific execution environment storage means A discarding unit for discarding data corresponding to the user from the execution environment storage unit for each user;
The server device according to claim 2, comprising:   When it is determined by the connection determination means that any of the various client devices used by the user is connected to the server device, the startup start time set in advance for the one client device is delayed by a predetermined time. The server device according to claim 2, further comprising time adjustment means for setting a new start time. Application execution environment storage means for storing data related to the application execution environment for each type of client device,
5. The server device according to claim 1, wherein the generation unit generates an application execution environment adapted to a type of client device based on data stored in the application execution environment storage unit. Receiving means for receiving data indicating the type of the client device at the time of a connection request from the client device;
When the data indicating the type of the client device is received by the receiving unit, if the execution environment of the application adapted to the type is already generated by the generating unit, screen data corresponding to the execution environment is transmitted to the client device. Transmission means for
When the data indicating the type of client device is received by the receiving unit, if the application execution environment adapted to the type is not generated by the generation unit, the generation unit executes the application execution environment adapted to the type The server apparatus as described in any one of Claim 1 to 5 which produces | generates. Transmitting means for transmitting data indicating the type of the client device to the server device when connected to the server device;
Receiving means for receiving screen data corresponding to an execution environment of an application adapted to the type from the server device,
When connecting to the server according to a preset operation schedule, the receiving unit receives screen data corresponding to an execution environment of an application generated in advance in the server device before the connection.   A remote connection system comprising: the server device according to any one of claims 1 to 6; and a client device that is remotely connected to the server device and uses an execution environment of an application generated by the server device. . Computer
Time determination means for determining whether or not a predetermined time before the preset start time for each of the various client devices used by the user,
A generating unit configured to generate an execution environment of an application corresponding to the one client device when it is determined by the time determining unit that the predetermined time has elapsed from the activation start time for the one client device used by the user;
Program to function as. Computer
Transmitting means for transmitting data indicating the type of client device to the server device when connected to the server device;
Function as receiving means for receiving screen data corresponding to the execution environment of the application adapted to the type from the server device;
When the client device connects to the server according to a preset operation schedule, the receiving unit receives screen data corresponding to an application execution environment generated in advance in the server device before the connection .

Images