JP2024151741A - Information processing device - Google Patents

Abstract

[Problem] According to the present invention, it is possible to automatically set the usage time of a PC while achieving both convenience for the system administrator and the user. [Solution] The present invention is characterized by having an acquisition means 111 that acquires the usage status of a terminal 110 from an arbitrary program, a detection means 31 that detects whether the usage status acquired by the acquisition means 111 satisfies a specific condition 121, and a registration means that registers usage extension information of the terminal 110 based on the detection of the specific condition 121 by the detection means 31. [Selected Figure] Figure 8

Description

The present invention relates to an information processing device equipped with labor management software that controls the usage time of a PC.

In recent years, information processing devices equipped with labor management software that controls PC usage time to prevent use outside of working hours and overtime work have become widespread. As disclosed in Patent Literature 1, a technology is known in which a management server sets the permitted PC usage time and controls PC usage. Also, as disclosed in Patent Literature 1, an information processing device is known that displays on the PC a request for extension of the permitted usage time to the user of the PC before the end of the permitted usage time. At this time, the extension request from the user is sent to the management server, which then processes the extension.

In recent years, with the spread of telecommuting and other trends, information processing devices equipped with labor management software that acquires PC operation history in order to visualize work content are also known. As disclosed in Patent Document 1, the PC operation history includes information on the use of applications, the operation of pointing devices, and the sending and receiving of emails.

JP 2014-160488 A

However, in Patent Document 1, the policy applied during automatic extension is set based on the basic management policy registered in the management server, so the permitted usage time may be extended longer than expected, which poses issues of compromising the effect of preventing overtime work and security. In addition, when work start and end times vary from person to person, various basic management policies must be applied, which is time-consuming for the system administrator.

In consideration of the above problems, the present invention aims to automatically set the permitted usage time of a PC while balancing convenience for system administrators and users, without compromising security or the effect of preventing overtime work.

In view of the above, the information processing device according to the present invention comprises:
An acquisition means for acquiring a usage status of a terminal from an arbitrary program;
a detection means for detecting whether the usage status acquired by the acquisition means satisfies a specific condition;
and a registration means for registering an extension of the usage time of the terminal based on the detection of the specific condition by the detection means.

According to the present invention, it is possible to automatically set the PC usage time while achieving convenience for both the system administrator and the user.

A system configuration diagram showing an example of the configuration of an information processing system. FIG. 1 is a hardware configuration diagram showing a client terminal device 110. A hardware configuration diagram of a server device 120. FIG. 13 is a diagram showing an example of setting information 121. FIG. 13 is a diagram showing an example of setting information 121. Flowchart showing the process of the client terminal device 110 Flowchart showing automatic extension time registration Flowchart showing automatic extension time registration FIG. 13 is a diagram showing an example of a PC operation history; FIG. 13 is a diagram showing an example of a PC operation history; Flowchart showing automatic extension time registration A diagram showing an example of an extension application history Flowchart showing automatic extension time registration Diagram showing an example of an audit log Flowchart showing automatic extension time registration Figure showing an example of calendar information from a schedule management service Flowchart showing automatic extension time registration FIG. 13 is a diagram showing an example of Web conference information.

The following describes a preferred embodiment of the present invention with reference to the drawings. Note that the embodiment described below is an example of a specific implementation of the present invention, and is one specific example of the configuration described in the claims.

<System configuration diagram>
First, the information processing system configuration according to this embodiment will be described with reference to the system configuration diagram of FIG. 1. As shown in FIG. 1, the information processing system according to this embodiment has information processing devices 110 and 120, and each information processing device is connected to a network 140 such as a LAN or the Internet. Hereinafter, the information processing device 110 may be referred to as a client terminal device, and the information processing device 120 may be referred to as a server device. Note that there may be multiple client terminal devices 110 and server devices 120. Also, the client terminal device 110 and the server device 120 may be any device such as a PC or a mobile terminal device that can execute each process described later as being performed by the information processing device. Also, the client terminal device 110 is connected via the network 140, but may be a standalone device that does not use the network 140.

The information processing system may be configured to utilize a thin client (e.g., a terminal service). A thin client is a computer architecture in which an information processing device (client terminal device 110) remotely connects to a server computer and executes an application program on the server computer using a virtual desktop environment generated on the server computer.

<Client Terminal Device 110>
The hardware configuration of the client terminal device 110 according to this embodiment will be described with reference to Fig. 2. The client terminal device 110 and the server device 120 will be described as having the same hardware configuration. The hardware configuration will be described using the client terminal device 110 as an example. A CPU (Central Processing Unit) 11 executes various processes using computer programs and data stored in a RAM 12 and a ROM 13, thereby controlling the operation of the entire device and executing each process described below as being performed by the device.

RAM (Random Access Memory) 12 has an area for temporarily storing computer programs and data loaded from storage device 16, and an area for temporarily storing various data received from external devices via I/F (interface) 17. RAM 12 also has a work area used by CPU 11 when executing various processes. In this way, RAM 12 can provide various areas as appropriate. ROM (Read Only Memory) 13 stores the setting data and boot program of this device, etc.

The operation unit 14 is made up of a mouse, keyboard, etc., and can be operated by the operator of the device to input various instructions to the CPU 11. The display unit 15 is made up of a CRT, LCD screen, OLED, etc., and can display the results of processing by the CPU 11 using images, text, etc.

The storage device 16 is a large-capacity information storage device, such as a hard disk drive device. This storage device 16 stores an OS (operating system), as well as computer programs and data for causing the CPU 11 to execute each process described below as being performed by this device. In addition, this computer program includes labor management software 111. The labor management software 111 is a program for security management that ensures the safety of the data, programs, etc. of the client terminal device 110, and has a function, for example, of limiting the startup time of the client terminal device 110.

Computer programs and data stored in the storage device 16 are loaded into the RAM 12 as appropriate under the control of the CPU 11 and are processed by the CPU 11.

I/F 17 is composed of various interfaces. It includes a network interface for connecting to network 140 and a device interface for connecting to external storage device 130. All of the above components are connected to bus 18.

<Server device 120>
3, the hardware configuration of the server device 120 is the same as that of the client terminal device 110 described above. That is, the CPU 31 of the server device 120 uses computer programs and data stored in the storage device 36 of the server device 120 to perform data communication with external devices via the I/F 37 of the server device 120, and executes each process described below as being performed by the server device 120. When executing each process, the computer programs and data stored in the storage unit 16 are expanded and stored in the RAM 32 or the ROM 33 based on operations on the operation unit 34 or control instructions from the outside, and each process is executed using the work area of the RAM 32.

Furthermore, setting information 121 is registered in the storage device 36 of the server device 120. The contents of the control to be executed on the client terminal device 110 are set in this setting information 121. Figures 4 and 5 are diagrams showing an example of the setting information 121. Specifically, as shown in Figure 4, the permitted use time of the client terminal device 110 and the control method outside the permitted use time (shutdown, logoff, lock, message, etc.) are registered. For example, the setting information 121 in the client terminal device 110 is registered in association with information on the client terminal device 110, the permitted use time, and the control method. As an example, in the upper part of FIG. 4, the PC name "PCName1", domain name "Test.domain.com", account name "Admin1", permitted usage time "2020/11/10 7:30 to 2020/11/10 16:30", and control method "shutdown" outside the permitted usage time are registered as one piece of linked setting information. Note that these are only examples, and other information may be added to the setting information or may be replaced with other information. In addition, the control method and permitted usage time settings of the setting information 121 may be set as weekly settings (Monday to Wednesday 7:30 to 16:30, Thursday and Friday 8:00 to 17:00, and unavailable all day on Saturdays and Sundays) as shown in FIG. 5.

In addition, instead of the setting information 121 in the client terminal devices 110 being collectively managed by the storage device 36 of the server device 120, each client terminal device 110 may store its own setting information 121. In such a case, however, the server device 120 is not essential.

In addition, this setting information 121 may also store settings for displaying the alert time and outputting a message requesting an extension.

<Processing of the Client Terminal Device 110>
Next, the operation of the labor management software 111 stored in the storage device 16 of the client terminal device 110 will be described with reference to the flowchart of Fig. 6. Here, the operation of the labor management software 111 that controls the permitted usage time of the client terminal device 110 in accordance with the setting information 121 of the server device 120 will be described.

The labor management software 111 is software for controlling the usage time of the device itself (here, the client terminal device 110). In this embodiment, the client terminal device 110 runs, for example, a Windows (registered trademark) operating system, and programs are executed under its management. Note that the operating system is not limited to Windows, and may be MacOS (registered trademark), Linux (registered trademark), or another operating system.

The CPU 11 loads the labor management software 111 from the storage device 16 to the RAM 12 and starts the loaded labor management software 111. The labor management software 111 may be set to start automatically as a service program, or may be set to start arbitrarily in response to an operation instruction from the user. The CPU 11 monitors the usage time of the client terminal device 110 in accordance with the labor management software 111 (S601). If the usage is within the permitted usage time (Yes in S602), the process returns to the beginning without controlling the client device 110. If the usage is outside the permitted usage time (No in S602), the client device 110 is controlled in accordance with the setting information 121 (S603).

<Processing of the server device 120 when extending the permitted usage time>
Next, a conventional process of manually extending the permitted usage time of a PC based on an extension request sent from a user of the client terminal device 110 to the server device 120 will be described with reference to the flowchart in Fig. 7. First, the server device 120 receives the extension request input and sent by the user of the client terminal device 110 (S701). If the system administrator approves the extension request, he or she registers the specified extension time in the server device 120 (S703). If the system administrator does not approve the extension request, the system administrator does not register the extension time (S704). Note that the method of registering the extension time is a publicly known technique as described in Patent Document 1, and therefore a description thereof will be omitted.

The registered extended time is recorded in the labor management software 111 of the client terminal device 110 via the network 140. The extended time may be applied for via an application system (workflow) or verbally. The extended time may be applied for by specifying the time in hours or by date and time.

Specific aspects of automatic registration of extended time are described below, but some of them can be combined with other aspects or replaced with other aspects. It is also possible to replace the aspects described below with methods other than those described below.

<Process 1 for automatic registration of extended time>
The process of automatically extending the PC usage time using the PC operation history such as mouse/keyboard operation, login/logoff, process start/end, file operation, etc. acquired by the labor management software 111 of the client terminal device 110 will be described with reference to the flowchart in Fig. 8. In the following example, the setting information 121 is collectively managed by the storage device 36 of the server device 120, and the analysis of the PC operation history is performed on the server device 120 side. However, if the client device 110 holds the setting information 121, the analysis of the PC operation history is performed by the labor management software 111 of the client device 110 or another application. The process after the analysis is also similarly performed on the client device 110 side, and data transmitted from the server device 120 is transmitted and received within the client device 110.

First, the client terminal device 110 transfers the PC operation history of the client terminal device 110 collected by the labor management software 111 stored in the storage device 16 to the server device 120 via the network 140. The storage device 36 of the server device 120 that receives the PC operation history analyzes the collected PC operation history (S801) and detects an extended work pattern, which is a work pattern that may result in an extension of the usage time (S802). If an extended work pattern exists (Yes in S802), the extended time is registered in the server device 120 (S803); if an extended work pattern does not exist (No in S802), the extended time is not registered (S804).

The detection process of the extended work pattern in S802 will be described with reference to FIG. 9. FIG. 9 is an example of the PC operation history of the client terminal device 110 collected by the labor management software 111. As a method of detecting the extended work pattern, for example, a specific application process name (process name) used at the settlement time is recorded in the server device 120, and when a start log (operation content "START" in FIG. 9) of the specific process name (in FIG. 9, accounting system.exe) is detected in the PC operation history, the usage time is extended. In addition, the extension time may be registered using the date, day of the week, subject of sent or received email, application window title name, mouse operation, extension application history, etc. as a trigger. In other words, when preset attribute information is included in the PC operation history, the extension time set for each attribute information may be registered. For example, if there is first attribute information (e.g., accounting system.exe 30 minutes before regular time on Friday) that links the day of the week, time, and operation content, the extension time of two hours set for the first attribute information is registered. In addition, when a specific character string is added to the subject of an incoming email, or when an incoming email from a specific user outside the company is set as the second attribute information, and when account information, a process name, or a specific mouse operation is set as the third attribute information, the extension time set for each attribute information may be registered.

These triggers are just examples, and multiple triggers may be combined. The extension time may be calculated statistically from past PC operation history recorded in the server device 120, or a configuration file or an extension time determined in advance by a system administrator may be registered.

The above describes the processing on the server device 120, but the processing may also be performed on the client terminal device 110 side using the operation history stored in the client terminal device 110.

As shown in Figure 10, if there is a history of receiving an email with a specific subject (for example, "Request for extension application" on the third line), the sender's permitted usage time may be automatically extended. In addition, the user's PC usage time may be extended based on the window title, mouse/keyboard operation history, and text input history.

In addition, the company's organizational information may be imported into the server device 120, and the supervisor may extend the PC usage time of the subordinate based on an email received by the supervisor. Similarly, the extended time may be registered for the target user based on the PC operation history of other users linked to the target user, even if they are not the supervisor.

The extension time mentioned above may be a specific time unit such as two hours, or it may be the end time of the permitted usage time. In either case, it means the setting of a time or a time that extends the original permitted usage time.

<Processing 2 for automatic registration of extended time>
Next, a process of automatically extending the operating time of a PC in server device 120 based on the history of extension requests from users will be described with reference to the flowchart of FIG.

The server device 120 stores the history of extension requests from users. The extension request content collected by the server device 120 is analyzed (S1101) to detect which extension request pattern it corresponds to (S1102). If an extension request pattern exists, the extension time corresponding to that extension request pattern is registered in the server device 120 (S1103), and if no extension request pattern exists, the extension time is not registered (S1104). The process of analyzing the extension request content may be performed every day, or at any timing.

The process of detecting extension request patterns in S1102 will be described with reference to FIG. 12. The contents of an extension request from a user include the date and time of the request, account name, domain name, PC name, request contents, and request time, etc. For example, when an extension request with the same request contents is made at the end of the month from the same account name, domain name, and PC name, as in No. 3, 5, 7, and 9 in FIG. 12, the target user's PC usage time may be extended in advance by the average extension time of the past requested times. In addition, whether the extension request contents have been approved by the system administrator may be recorded together with the extension request contents history, and the result may also be used in the detection process.

The above is just one example, and when not all of the listed items are the same, but some or other items are the same, it may be detected as an extension application pattern, or each item may be weighted for detection. Here, the last date of the month, the account name, the domain name, and the PC name are used as triggers, but the date, the day of the week, or the application content may also be used as triggers, for example. Mouse and keyboard operation history and text input history acquired by the client terminal device 110 may also be used. The above triggers are just one example, and multiple triggers may be combined.

In addition, the above example illustrates a case where processing is performed by the server device 120, but processing may also be performed by the client terminal device 120 using the extension application history stored in the client terminal device 120.

The extension time can also be registered using a configuration file or an extension time previously determined by the system administrator.

In addition, the company's organizational information can be imported into the server device 120, and the history of whether the superior approved the extension request can be added to the extension request history, and this can be used as a trigger condition.

<Processing 3 for automatic registration of extended time>
Next, a process for automatically extending the usage time of a PC based on the audit log of the system administrator stored in server device 120 will be described with reference to the flowchart of FIG.

The system administrator's audit log is stored in the server device 120. The system administrator's audit log collected by the server device 120 is analyzed (S1301) to detect which extended work pattern it is (S1302). If an extended work pattern exists, the extended time corresponding to that extended work pattern is registered in the server device 120 (S1303), and if it does not exist, the extended time is not registered (S1304). The analysis process of the extension application contents may be performed every day or at any timing.

The process of detecting extended work patterns in S1302 will be described with reference to FIG. 14. The system administrator's audit log records the extended time application account name, domain name, PC name, approval result, and the extended time processed. For example, as in No. 3, 5, 7, and 9 in FIG. 14, if an extension application is made from the same account name, domain name, and PC name at the end of the month and approved, the previously set extended processing time can be set in advance to extend the PC usage time.

Here, the last day of the month, the account name, the domain name, and the PC name are used as triggers, but the date, the day of the week, or the processing content may also be used as triggers. Also, the mouse/keyboard operation history and text input history acquired by the client terminal device 110 may also be used. Also, the above triggers are just examples, and multiple triggers may be combined.

Although the above describes the processing on the server device 120, the processing may also be performed on the client terminal device 120 side using the extension application history stored on the client terminal device 120.

The extension time may be calculated from the extension application history, or may be registered using a configuration file or an extension time previously determined by the system administrator.

<Process 4 for automatic registration of extended time>
Next, the process of automatically extending the usage time by importing calendar information from a schedule management service will be described with reference to the flowchart of FIG.

The server device 120 imports calendar information from the schedule management service (S1501) and detects schedules that may require an extension of the PC usage time (S1502). If there is a schedule that requires an extension of the PC usage time, the server device 120 registers the extension time for the client terminal device 110 linked to the user who registered the schedule (S1503). If there is no such schedule, the server device 120 does not register the extension time (S1504). The import process may be performed every morning, or at any timing.

The process of detecting a schedule that requires extension (S1502) will be described with reference to FIG. 16. The imported schedule includes scheduled outings and scheduled meetings (here referred to as "meetings"). Meetings and outings are detected from the schedule contents, and if the schedule extends beyond the set permitted PC usage time, the schedule is deemed to require extension and the PC usage time is extended (in this case, the set time is until 6 p.m., but the meeting is scheduled until 7 p.m., so the extension process is performed for one hour).

Here, plans to go out or plans to have a meeting are used as triggers, but the trigger may be determined arbitrarily. Also, the above triggers are just examples, and multiple triggers may be combined. Also, what is used as a trigger may be set in the server device 120 or the client terminal device 110.

Although the above describes the processing on the server device 120, it may also be executed on the client terminal device 120 to automatically apply for an extension.

The extension time can be calculated from the scheduled end time, or a previously set extension processing time can be applied, or a set time can be registered from the end time, or an extension time can be registered that has been determined in advance by a configuration file or a system administrator.

<Process 5 for automatic registration of extended time>
Next, the process of automatically extending the usage time based on the Web conference information will be described with reference to the flowchart of FIG.

Web conference information is obtained (S1701), and conditions that may cause the PC usage time to be extended are detected (S1702). If conditions that may cause the PC usage time to be extended exist, the extended time is registered in the server device 120 for the client terminal device 110 associated with the user who is scheduled to participate in the Web conference (S1703), and if no conditions exist, the extended time is not registered (S1704).

The process of detecting the extension conditions in S1702 will be described with reference to FIG. 18. The detected Web conference information includes the scheduled start time, scheduled end time, conference agenda, participants, etc. If the detected actual start time is 30 minutes or more later than the scheduled start time, the PC usage time is extended.

Note that here, the difference between the scheduled start time and the actual start time is used as the trigger, but the trigger can be determined arbitrarily. For example, the trigger can be determined when there are five or more participants, when an external participant is attending the meeting, or based on the agenda.

The above triggers are just examples, and multiple triggers may be combined.

Although the above describes the processing on the server device 120, it may also be executed on the client terminal device 120 to automatically apply for an extension.

The extension time can be calculated from the scheduled end time, or a previously set extension processing time can be applied, or a set time can be registered from the end time, or an extension time can be registered that has been determined in advance by a configuration file or a system administrator.

In addition, a known method for obtaining Web conference information can be used, such as detecting the execution status of a specific process.

This embodiment may be applied to the process of lifting some restrictions in functions that restrict the use of USB memory and other control functions, regardless of the process of extending the permitted usage time of the PC.

<Other embodiments>
The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

In the present invention described above, the process for automatically registering the extended time is as follows:
(1) Whether or not an extended work pattern exists as a result of analyzing the operation history of the client terminal 110; (2) Whether or not any extension application patterns are included in the extension request history from the client terminal device 110; (3) Whether or not any extension work patterns are included in the extension work history in response to the extension request from the client terminal device 110 included in the audit log in the server device 120; (4) Whether or not there is anything in the schedule of the user linked to the client terminal device 110 that seems to require extension; and (5) Whether or not the start time and end time of the Web conference of the user linked to the client terminal device 110 meet the conditions.

In other words, if it is detected that a "specific condition" is met based on information regarding the "usage status" of the client terminal device 110, the extended time is automatically registered.

"Usage status" includes PC operation history, extension application history, extended work history, schedule status, and Web conference usage status, and "specific conditions" include the operation history including an extended work pattern, the extension application satisfying the extension application pattern or being included in any of the extension application patterns, the extended work for the extension request satisfying the extended work pattern or being included in any of the extended work patterns, there being something in the schedule that seems to require extension, and the start and end times of the Web conference satisfying the conditions.

110 Client terminal device 111 Labor management software 120 Server device 121 Setting information 140 Network

Claims (6)

An acquisition means for acquiring a usage status of a terminal from an arbitrary program;
a detection means for detecting whether the usage status acquired by the acquisition means satisfies a specific condition;
and a registration means for registering an extension of the usage time of the terminal based on the detection of the specific condition by the detection means. The usage status is an operation history of the terminal,
2. The information processing system according to claim 1, wherein said detection means detects that said specific condition is satisfied when said operation history includes a specific extended task pattern. The usage status is a history of extension requests made from the terminal,
2. The information processing system according to claim 1, wherein the detection means detects that the specific condition is satisfied when a specific extension application pattern is included in the extension application history. a server device for receiving an extension application for extending the usage time of the terminal;
The usage status is a history of extension operations performed on the server device side in response to the extension application,
2. The information processing system according to claim 1, wherein the detection means detects that the specific condition is satisfied when the extended work history includes a specific extended work pattern. The usage status is a schedule of a user associated with the terminal,
2. The information processing system according to claim 1, wherein said detection means detects that said specific condition is satisfied when said schedule includes an extension-required schedule that requires an extension of a usage time. The usage status is that a Web conference is being held on the terminal;
The information processing system according to claim 1, characterized in that the detection means detects that the specific condition is met when the start time and end time of a Web conference being executed on the terminal match a preset condition that indicates that PC usage is likely to be extended.

Images