JP5722476B2 - SYSTEM USE TIME MANAGEMENT DEVICE, SYSTEM USE TIME MANAGEMENT METHOD, AND SYSTEM USE TIME MANAGEMENT PROGRAM - Google Patents

Description

  The present invention relates to a system use time management device, a system use time management method, and a system use time management program.

  Up to now, a function for setting the usage time of a system for each user (for example, domain management in Windows (registered trademark)) and a function for setting a usage time of the entire system (for example, task management of an application in Windows (registered trademark)) Each existed independently. Further, the setting of the system usage time for each day of the week and the setting for each date can be performed by only one of them.

  Further, Patent Documents 1 to 6 are given as conventional techniques related to access and login control and authentication. Patent Document 1 discloses a technique related to an access control device and the like for preventing leakage of confidential information due to unauthorized access performed on a file under system management from a certain terminal in a computer system having a plurality of terminals. Patent Document 2 sets up a mask table that specifies whether or not to allow input of a user ID and password, and logs in by double checking input permission while using the original user ID and password. A technology relating to a user authentication device and the like for increasing the security level at the time is disclosed. Patent Document 3 discloses a technology related to a network device unauthorized use prevention device or the like that effectively prevents unauthorized use of a computer and a mobile terminal using a network system. Patent Document 4 discloses a technique related to a user authentication system that can prevent a client computer from being used with an account of another group without inputting a user ID, a password, or the like. Patent Document 5 discloses a technique related to a user authentication program or the like that improves the convenience of a user who makes a login request while ensuring security. Patent Document 6 discloses a technology related to a web login restriction system capable of performing flexible login restrictions.

JP 2000-259567 A JP 2001-101136 A JP 2003-14928 A JP 2006-285818 A JP 2007-164661 A JP 2008-242676 A

  However, since the system usage time cannot be set flexibly by combining the functions and settings described above, the workload for managing the setting of the system usage time according to the system operation that changes from day to day increases. There was a problem. Specifically, in the case of setting an individual usage time for each logged-on user account, there is a problem that the workload for batch setting or setting change increases as the number of users increases. In addition, when the start / stop time of the application itself is managed using the task scheduling function of the system, there is a problem that the use time for each user cannot be set and flexibility is low.

  The present invention has been made in view of the above problems, and not only can prevent unauthorized access by the user, but also reduces the work load for managing the setting of the system usage time and manages the setting. It is an object of the present invention to provide a system usage time management device, a system usage time management method, and a system usage time management program that can improve convenience.

  In order to solve the above-described problems and achieve the object, a system usage time management device according to the present invention is a system usage time management device including a control unit and a storage unit, and User management information including user identification information for uniquely identifying and user attribute information related to the user attribute, and usage time information regarding the time when the system can be used and / or the time when the system cannot be used are set for each day of the week. The system-wide usage time information applicable to the user and the usage time information are set by date, and the system-wide usage time information applicable to all the users and the usage time information are set by day of the week. The usage time information for each day of the week applicable to the user corresponding to the specific attribute and the usage time information are set for each date. A pair of individual date usage time information applicable to the user corresponding to the specific attribute, to which individual setting identification information for uniquely identifying the pair is assigned, and the individual setting Individual setting management information including identification information and the user attribute information, usage time information for the entire system day of the week, usage time information for the entire system date, usage time information for the individual day of the week, and usage time information for the individual date Priority information regarding priority when applied to the user, and the control unit receives the login operation when receiving a login operation to the system including an input of the user identification information. Based on the acquisition means for acquiring the date, day of the week and time, and the user identification information and the user management information input at the time of the login operation Extraction means for extracting the user attribute information corresponding to other information, the date and day of the week acquired by the acquisition means, the user attribute information extracted by the extraction means, the individual setting management information, and the priority information Based on the system-wide day-by-day usage time information, the system-wide day-by-day usage time information, the individual day-by-day usage time information, and the individual date-by-date usage time information, the user who has performed the login operation has the highest priority. The selection means for selecting what to apply, and the login to the system at the time of the user who performed the login operation based on the time selected by the selection means and the time acquired by the acquisition means And determining means for determining whether or not to permit.

  Further, the system usage time management device according to the present invention is the system usage time management device described above, wherein the priority information includes the usage time information for each individual date and the system whole date in descending order of priority. Use time information, use time information for each individual day of the week, and use time information for the entire system day of the week are used.

  A system usage time management method according to the present invention is a system usage time management method executed in an information processing apparatus including a control unit and a storage unit, wherein the storage unit uniquely identifies a user. User management information including user identification information and user attribute information related to the user's attributes, and usage time information related to the time when the system can be used and / or the time when the system cannot be used are set for each day of the week, and can be applied to all the users System-wide usage time information for each day of the week and the usage time information are set for each date, and the system-wide usage time information for all dates applicable to all the users and the usage time information are set for each day of the week. The usage time information for each individual day applicable to the user corresponding to the attribute and the usage time information are set for each date. A pair of individual date usage time information applicable to the user corresponding to the specific attribute, to which individual setting identification information for uniquely identifying the pair is assigned, and the individual setting identification information; Individual setting management information including the user attribute information, system-wide day-of-day usage time information, system-wide day-by-system usage time information, individual day-of-week usage time information, and individual date-specific usage time information to the user Priority information regarding the priority at the time of application, and when the login operation to the system including the input of the user identification information is executed in the control unit, the login operation is received. Based on the acquisition step of acquiring the date, day of the week, and time, and the user identification information and the user management information input during the login operation An extraction step for extracting the user attribute information corresponding to the user identification information, the date and day of the week acquired in the acquisition step, the user attribute information extracted in the extraction step, the individual setting management information, and the priority Based on the information, among the use time information for the entire system day of the week, the use time information for the entire system date, the use time information for the individual day of the week, and the use time information for the individual date, the user who performed the login operation Based on the selection step for selecting the one to be applied with the highest priority, and the time selected in the selection step and the time acquired in the acquisition step, to the system at the time of the user who performed the login operation And a determination step for determining whether or not to permit the login.

  The system usage time management method according to the present invention is the system usage time management method as described above, wherein the priority information includes the usage time information by individual date, the system-wide date, in descending order of priority. Use time information, use time information for each individual day of the week, and use time information for the entire system day of the week are used.

  A system usage time management program according to the present invention is a system usage time management program to be executed by an information processing apparatus including a control unit and a storage unit, and the storage unit uniquely identifies a user. User management information including user identification information for the user and user attribute information related to the user's attributes, and usage time information related to the time when the system can be used and / or the time when the system cannot be used are set for each day of the week. Available system-wide usage time information for each day of the week and said usage time information are set by date, and system-wide usage time information by date applicable to all users and the usage time information are set by day of the week. The usage time information for each day of the week applicable to the user corresponding to the attribute of the A pair of usage time information by individual date that is set separately and applicable to the user corresponding to the specific attribute, and is provided with individual setting identification information for uniquely identifying the pair, and Individual setting management information including individual setting identification information and the user attribute information, usage time information for the entire system day of the week, usage time information for the entire system date, usage time information for the individual day of the week, and usage time for the individual date In the case of receiving a login operation to the system including the input of the user identification information for storing the priority information about the priority when applying the information to the user and causing the control unit to execute the information. The acquisition step of acquiring the date, day of the week, and time of receiving the login operation, the user identification information input during the login operation, and the Extracting the user attribute information corresponding to the user identification information based on the user management information; the date and day of the week acquired in the acquisition step; the user attribute information extracted in the extraction step; Based on the individual setting management information and the priority information, among the system-wide day-of-day usage time information, the system-wide day-by-day usage time information, the individual day-of-day usage time information, and the individual date-specific usage time information, The selection step of selecting the one to be applied with the highest priority to the user who performed the login operation, and the user who performed the login operation based on the selection at the selection step and the time acquired at the acquisition step Determining whether to permit login to the system at that time. And features.

  Further, the system usage time management program according to the present invention is the system usage time management program described above, wherein the priority information includes, in descending order of priority, the usage time information for each individual date and the date for the entire system. Use time information, use time information for each individual day of the week, and use time information for the entire system day of the week are used.

  According to the present invention, when a login operation to the system including input of user identification information is received, (1) the date, day of the week, and time when the login operation is received are acquired, and (2) the login operation is performed. The user attribute information corresponding to the user identification information is extracted based on the user identification information input in advance and the user management information stored in advance, and (3) the acquired date and day of the week, the extracted user attribute information, stored in advance Based on the stored individual setting management information and the priority information stored in advance, the system-wide usage time information by day of the week, the system-wide usage time information by date, the usage time information by individual day of the week, and the usage time by individual date Of the information, the one that is applied with the highest priority to the user who performed the login operation is selected, and (4) the login operation based on the selected item and the acquired time It determines whether or not to permit the login to the system in the time of the user who performed. As a result, it is possible not only to prevent unauthorized access by the user, but also to reduce the workload for managing the setting of the system usage time and improve the convenience of managing the setting. . Specifically, the system usage time can be set flexibly by combining the settings for each system or user with the settings for each day of the week or each day, so the system usage time can be set according to the daily system operation. There is an effect that the work load for managing can be reduced.

  Further, according to the present invention, the priority information is, in descending order of priority, the use time information by individual date, the use time information by system date, the use time information by individual day of the week, and the use time information by system day of the week. Therefore, it is possible to determine whether or not to allow login by giving priority to exceptional usage time settings such as holidays.

FIG. 1 is a diagram showing an outline of the present embodiment. FIG. 2 is a block diagram illustrating an example of the configuration of the system usage time management device 100. FIG. 3 is a diagram illustrating an example of information stored in the user management file 104a. FIG. 4 is a diagram illustrating an example of information stored in the system-wide day-by-day usage time file 104b. FIG. 5 is a diagram illustrating an example of information stored in the system-wide date-based usage time file 104c. FIG. 6 is a diagram illustrating an example of information stored in the individual day usage time file 104d. FIG. 7 is a diagram illustrating an example of information stored in the individual date use time file 104e. FIG. 8 is a diagram illustrating an example of information stored in the individual setting management file 104f. FIG. 9 is a diagram illustrating an example of information stored in the priority file 104g. FIG. 10 is a flowchart illustrating an example of the system usage time management process.

  Embodiments of a system usage time management apparatus, a system usage time management method, and a system usage time management program according to the present invention will be described below in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. Overview]
An outline of the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an outline of the present embodiment. First, in a management database prepared in advance, (A) user group affiliation information, (B) system-wide day-by-day usage time information and system-wide day-by-system usage time information, and individual day-by-day usage time information and time by individual date At least one pair of information, (C) individual setting management information, and (D) priority information are stored.

  The user group affiliation information is information including a preset user group for collectively managing system users who can log in to the system, and a configuration of system users belonging to each user group. In the user group affiliation information shown in FIG. 1, system users “administrator A” and “administrator B” belong to a user group “administrator user group” and “general user” belongs to a user group “general user group”. It shows that system users such as “a” and “general user b” belong.

  The system-wide usage time information for each day of the week is usage time information applicable to all system users and is set for each day of the week, and is a normal system operation schedule. The system-wide usage time information by date is usage time information applicable to all system users and is set by date. The usage time information is information relating to the availability setting of the system in a predetermined time unit such as one hour unit. In the system-wide usage time information for each day of the week, which is shown as “system as a whole (by day of the week)” in FIG. 1, the symbol “◯” indicating that the system can be used and that the system cannot be used is shown. The symbol “x” is shown for each day of the week in units of 6 hours. In the system-wide date-based usage time information indicated as “entire system (by date)” in FIG. 1, the symbol “◯” and the symbol “x” are shown by date in units of 6 hours.

  The individual day usage time information is usage time information applicable to system users belonging to a specific user group, and is set for each day of the week. The usage time information by individual date is usage time information applicable to system users belonging to a specific user group, and is set by date. In the usage time information for each day of the week, which is indicated as “administrator setting (by day of the week)” in FIG. 1, the symbol “◯” and the symbol “x” are shown for each day of the week in units of 6 hours. In the usage time information by individual date shown as “administrator setting (by date)” in FIG. 1, the symbol “◯” and the symbol “x” are shown by date in units of 6 hours. The usage time information for each individual day of the week and the usage time information for each individual date are managed in pairs, and each pair is assigned a usage time ID for uniquely identifying the pair.

  The individual setting management information is information related to a usage time ID and a user group to which a pair of usage time information for each day of the week and usage time information for each individual date corresponding to the usage time ID is applied. In the individual setting management information shown in FIG. 1, the notation “administrator setting” indicates that there is a pair of usage time information for each day of the week and usage time information for each individual date to which “administrator user group” is applied. In addition, it is indicated by “None” that there is no pair of usage time information for each day of the week and usage time information for each individual date to which “general user group” is applied.

  The priority information is information relating to the priority (priority order) when various types of usage time information are applied to the system user who performed the login operation. In the priority information shown in FIG. 1, the usage time information by individual date, the usage time information by whole system date, the usage time information by individual day of the week, and the usage time information by whole system day of the week in order from the highest priority. It is shown.

  Next, an outline of a process flow for determining whether or not a system user can log in based on the above-described various information stored in the management database will be described by taking a specific situation as an example.

[Situation 1] When administrator A performs a login operation at 12:00 on Monday, November 3 [Step 11] The user group to which administrator A belongs is confirmed by referring to the user group affiliation information. As a result of the confirmation, it can be seen that the administrator A belongs to the “administrator user group”.

[Step 12] Refer to the individual setting management information as to whether or not there is a pair of the usage time information for each day of the week and the usage time information for each individual date to which the “manager user group” to which the administrator A belongs is applied. And confirm. As a result of the confirmation, there is a pair of usage time information for each day of the week and usage time information for each individual date that applies to the “administrator user group” as shown in FIG. I understand.

[Step 13] The priority at the time of applying various types of usage time information to the “manager user group” is confirmed with reference to the priority information. As a result of the confirmation, in order from the highest priority, the usage time information for each individual date indicated as “administrator setting (by date)” in FIG. 1 and “system as a whole (by date)” are shown. Use time information by system-wide date, use time information by individual day of the week indicated as “Administrator settings (by day of the week)”, and use time information by day of the week of the system as indicated by “System overall (by day of the week)” I know that there is.

[Step 14] Based on the fact that the login operation of the administrator A was performed at 12:00 on Monday, November 3, various types of usage time information are referred to in descending order of priority. First, referring to the usage time information for each individual date indicated as “administrator setting (by date)” in FIG. 1, it can be seen that the availability setting for November 3 (Monday) is registered therein. . Then, based on the fact that the login operation of the administrator A was performed at 12:00 on Monday, November 3 and the usage time information by individual date indicated as “administrator setting (by date)” It is determined whether the person A can log in at 12:00 on Monday, November 3rd. As a result of the determination, it is understood that the administrator A can log in (login OK) at 12:00 on Monday, November 3rd.

[Situation 2] When administrator A performs a login operation at 12:00 on Saturday, November 15, the description of [Step 21] to [Step 23] is the above-mentioned [Step 11] to [Step 13] and will be omitted.

[Step 24] Based on the fact that the login operation of the administrator A was performed at 12:00 on November 15 (Saturday), various types of usage time information are referred to in descending order of priority. First, referring to the usage time information for each individual date shown as “Administrator settings (by date)” in FIG. 1, then the usage time by system date shown as “System overall (by date)” Although the information is referred to, it can be seen that the availability setting for November 15 (Saturday) is not registered. Then, referring to the individual day use time information indicated as “manager setting (by day of the week)”, it can be seen that the availability setting for Saturday is registered therein. Then, based on the fact that the login operation of the administrator A was performed at 12:00 on Saturday, November 15 and the usage time information by individual day of the week indicated as “administrator setting (by day)” It is determined whether or not the person A can log in at 12:00 on Saturday, November 15th. As a result of the determination, it can be seen that the administrator A can log in (login OK) at 12:00 on November 15 (Saturday).

[Situation 3] When general user a performs login operation at 12:00 on Monday, November 3 [Step 31] The user group to which general user a belongs is confirmed with reference to the user group affiliation information. As a result of the confirmation, it can be seen that the general user a belongs to the “general user group”.

[Step 32] Referring to the individual setting management information, whether or not there is a pair of the usage time information for each day of the week and the usage time information for each individual date to which the “general user group” to which the general user a belongs is applied. To confirm. As a result of the confirmation, as shown in FIG. 1 as “none”, it can be seen that there is no pair of the usage time information for each individual day and the usage time information for each individual date to which the “general user group” is applied.

[Step 33] Priorities for applying various types of usage time information to the “general user group” are checked with reference to the priority information. As a result of the confirmation, in order from the highest priority, the usage time information by date for the entire system, which is indicated as “system as a whole (by date)” in FIG. 1, is indicated as “system as a whole (by day of the week)”. It turns out that it is the usage time information according to the day of the week for the entire system.

[Step 34] Based on the fact that the login operation of the general user “a” was performed at 12:00 on Monday, November 3, various types of usage time information are referred to in descending order of priority. First, referring to the system-wide date-based usage time information indicated as “system-wide (by date)” in FIG. 1, it can be seen that the availability setting for November 3 (Monday) is registered there. . Then, based on the fact that the login operation of the general user a was performed at 12:00 on Monday, November 3, and the system-wide date-based usage time information indicated as “the entire system (by date)”, It is determined whether or not the user a can log in at 12:00 on Monday, November 3rd. As a result of the determination, it is understood that the general user a cannot log in (login NG) at 12:00 on Monday, November 3rd.

[Situation 4] When a general user a performs a login operation at 12:00 on Monday, November 10 Here, the description of [Step 41] to [Step 43] is the above-mentioned [Step 31] to [Step]. 33] and will be omitted.

[Step 44] Based on the fact that the login operation of the general user a was performed at 12:00 on Monday, November 10, various types of usage time information are referred to in descending order of priority. First, reference is made to the system-wide date usage time information indicated as “system-wide (by date)” in FIG. 1, but the availability setting for Monday, November 10 is not registered. I understand. Then, referring to the system-wide usage time information for each day of the week, which is indicated as “system-wide (by day of the week)”, it can be seen that the availability setting for Monday is registered in this. Then, based on the fact that the login operation of the general user a was performed at 12:00 on Monday, November 10 and the system-wide usage time information for each day of the week indicated as “the whole system (by day of the week)” It is determined whether or not the login operation of the user a is possible at 12:00 on Monday, November 10th. As a result of the determination, it is understood that the login operation of the general user a is possible to log in (login OK) at 12:00 on Monday, November 10th.

[Situation 5] When general user a performs a login operation at 12:00 on Saturday, November 15, the description of [Step 51] to [Step 53] is the above-mentioned [Step 31] to [Step 33] and will be omitted.

[Step 54] Based on the fact that the login operation of the general user a was performed at 12:00 on November 15 (Saturday), various types of usage time information are referred to in descending order of priority. First, reference is made to system-wide date usage time information, which is indicated as “system-wide (by date)” in FIG. 1, but the availability setting for November 15 (Saturday) is not registered in this. I understand. Then, referring to the system-wide usage time information for each day of the week, which is indicated as “system-wide (by day of the week)”, it can be seen that the availability setting for Saturday is registered in this. Then, based on the fact that the login operation of the general user “a” was performed at 12:00 on Saturday, November 15, and the usage time information for each day of the entire system indicated as “the whole system (by day of the week)” It is determined whether or not the login operation of the user a is possible at 12:00 on Saturday, November 15th. As a result of the determination, it is understood that the login operation of the general user a is not possible to log in (login NG) at 12:00 on Saturday, November 15th.

  As described above, in this overview, the usage time of the entire system (login possible time) and the usage time of each logged-in user account are managed. Specifically, the day-by-day usage time (a) and the date-specific usage time (b) of the entire system are stored in the management database in predetermined time units (for example, in units of one hour). Also, a use time ID for individual setting is assigned, and the use time by day of the week (c) and the use time by date (d) for each use time ID are stored in the management database in a predetermined time unit (for example, one hour unit). . Further, a user group for collectively managing login users of the system and configuration information of users belonging to the user group are stored in the management database. Further, the use time ID for individual setting and the allocation information of the user group to which the setting is applied are stored in the management database.

  In this overview, when the user performs a login operation, information on the belonging user group stored in the management database is checked, and settings (a), (b), (c) and (d) of the usage time are checked. ) In order of priority, (d), (b), (c) and (a) are checked according to the priority of the usage time setting, and the highest priority among the usage time settings corresponding to the current time is checked. Determine whether login is possible or not based on what is expensive. In the present embodiment, an error may be displayed for a user who is determined to be unable to log in, and the user may not be allowed to perform any subsequent operations.

  By managing the login time in this way, unauthorized access by the user can be prevented. In addition, by using the entire system setting, individual setting, day-of-week setting, and date-specific setting for the usage time, management workload can be reduced and convenience can be improved. In other words, the system usage time can be flexibly set by combining the entire system setting, individual setting, day of the week setting, and date setting, and the setting of the system usage time is managed according to the system operation that changes every day. Therefore, the work load can be reduced. In addition, simply combining the conventional user-specific settings function for usage time settings with the system-wide settings function will not allow users to use the system during times when the system is not running, According to this outline, the user can use the system even during a time period when the system is not activated. Also, in this overview, the priority of usage time setting is, for example, (d), (b), (c) and (a) in descending order of priority. It is possible to determine whether or not to allow login by giving priority to the setting.

  For example, when it is desired to set the same login available time for a large number of users, the usage times (a) and (b) of the entire system may be set. In addition, when it is desired to set a login possible time different from that for other users to a small number of users, the usage time (c) and (d) for individual setting may be set. In addition, when it is desired to set the usage time according to the operation schedule in units of one week, the usage time (a) and (c) for each day of the week may be set. Furthermore, when it is desired to set an exceptional usage time such as a holiday, the usage times (b) and (d) for each date may be set.

[2. Constitution]
The configuration of the system usage time management apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 2 is a block diagram illustrating an example of the configuration of the system usage time management device 100.

  The system usage time management apparatus 100 includes a control unit 102, a storage unit 104, a communication interface unit 106, and an input / output interface unit 108, and these units are communicably connected via an arbitrary communication path. .

  The communication interface unit 106 connects the system usage time management device 100 to a network 200 such as the Internet or a LAN (Local Area Network) via a communication device such as a router and a wired or wireless communication line such as a dedicated line. To do. That is, the communication interface unit 106 has a function of communicating data with other devices via a communication line.

  The input / output interface unit 108 is connected to the input device 112 and the output device 114. Here, in addition to a monitor (including a home television), a speaker or a printer can be used as the output device 114 (hereinafter, the output device 114 may be described as the monitor 114). As the input device 112, a monitor that realizes a pointing device function in cooperation with a mouse can be used in addition to a keyboard, a mouse, and a microphone.

  The storage unit 104 stores various databases, tables, files, and the like. The storage unit 104 is a storage unit, and for example, a memory device such as a RAM / ROM, a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used. The storage unit 104 stores a computer program for giving instructions to the CPU and performing various processes in cooperation with an OS (Operating System). The storage unit 104 includes a user management file 104a, a system-wide day-by-day usage time file 104b, a system-wide day-by-system usage time file 104c, an individual day-by-day usage time file 104d, an individual date-by-date usage time file 104e, an individual setting management file 104f, A priority file 104g is stored.

  The user management file 104a stores user management information including user identification information for uniquely identifying a user and user attribute information regarding a user attribute. Here, an example of information stored in the user management file 104a will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of information stored in the user management file 104a. The user management file 104a shown in FIG. 3 stores a user ID as user identification information and a group ID as user attribute information for uniquely identifying a group to which the user belongs in association with each other.

  Returning to FIG. 2, the system-wide day-by-day usage time file 104b has system-wide day-of-day usage hours applicable to all users, with usage time information relating to the time when the system can be used and / or the time when the system cannot be used being set for each day of the week. Stores information. Here, an example of information stored in the system-wide day-by-day usage time file 104b will be described with reference to FIG. FIG. 4 is a diagram illustrating an example of information stored in the system-wide day-by-day usage time file 104b. The system-wide usage time file 104b shown in FIG. 4 stores the availability setting related to the availability of the system for each day of the week in a predetermined time unit (for example, one hour unit).

  Returning to FIG. 2, in the system-wide date-based use time file 104c, usage time information regarding the time when the system can be used and / or the time when the system cannot be used is set for each date, and the system-wide use time by date applicable to all users. Stores information. Here, an example of information stored in the system-wide date-based usage time file 104c will be described with reference to FIG. FIG. 5 is a diagram illustrating an example of information stored in the system-wide date-based usage time file 104c. The system-wide usage date file 104c shown in FIG. 5 stores the availability setting related to the availability of the system for each date in a predetermined time unit (for example, one hour unit).

  Returning to FIG. 2, in the usage time file 104d for each day of the week, usage time information related to the time when the system can be used and / or the time when the system cannot be used is set for each day of the week. It stores usage time information to which individual setting identification information is added. The individual setting identification information is information for uniquely identifying a pair of individual day usage time information and individual date usage time information. Here, an example of information stored in the individual day usage time file 104d will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of information stored in the individual day usage time file 104d. The usage time file 104d for each day of the week shown in FIG. 6 is provided with a usage time ID as individual setting identification information, and stores the availability setting regarding the availability of the system for each day of the week in a predetermined time unit (for example, one hour unit). doing.

  Returning to FIG. 2, in the usage time file 104e for each individual date, usage time information related to the time when the system can be used and / or the time when the system cannot be used is set for each date, and for each individual date applicable to a user corresponding to a specific attribute. It stores usage time information to which individual setting identification information is added. Here, an example of information stored in the individual date usage time file 104e will be described with reference to FIG. FIG. 7 is a diagram illustrating an example of information stored in the individual date use time file 104e. The usage time file 104e for each individual date shown in FIG. 7 is provided with a usage time ID as individual setting identification information, and stores the availability setting related to the availability of the system for each date in a predetermined time unit (for example, one hour unit). doing.

  Returning to FIG. 2, the individual setting management file 104f stores individual setting management information including individual setting identification information and user attribute information. Here, an example of information stored in the individual setting management file 104f will be described with reference to FIG. FIG. 8 is a diagram illustrating an example of information stored in the individual setting management file 104f. The individual setting management file 104f shown in FIG. 8 stores a use time ID as individual setting identification information and at least one group ID as user attribute information in association with each other.

  Returning to FIG. 2, the priority file 104g relates to the priority when the system-wide usage time information by day, system-wide usage time information, individual day-by-day usage time information, and individual date-specific usage time information are applied to the user. Stores priority information. Here, an example of information stored in the priority file 104g will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of information stored in the priority file 104g. The priority file 104g shown in FIG. 9 has a numerical value “1” as the priority in order from the highest priority with respect to the four combinations of “day of the week” and “date” and “individual” and “whole”. , “2”, “3” and “4” are stored. The numerical value given to the combination of “date” and “individual” represents the priority of the usage time information by individual date, and the numerical value given to the combination of “date” and “whole” is the usage time by system whole date Represents the priority of information, the numerical value assigned to the combination of “day of the week” and “individual” represents the priority of the usage time information by individual day of the week, and the numerical value assigned to the combination of “day of the week” and “whole” is the system This shows the priority of the usage time information for all days of the week.

  Returning to FIG. 2, the control unit 102 is a CPU (Central Processing Unit) or the like that comprehensively controls the system usage time management apparatus 100. The control unit 102 has an internal memory for storing a control program such as an OS (Operating System), a program that defines various processing procedures, and necessary data, and performs various information processing based on these programs. Run. The control unit 102 includes a login monitoring unit 102a, an acquisition unit 102b, an extraction unit 102c, a selection unit 102d, a determination unit 102e, a display execution unit 102f, and an operation management unit 102g in terms of functional concept.

  The login monitoring unit 102a monitors the login operation to the system including the input of the user identification information, and when receiving the login operation, notifies the acquisition unit 102b and the extraction unit 102c to that effect.

  When receiving the notification that the login operation sent from the login monitoring unit 102a has been received, the acquiring unit 102b acquires the date, day of the week, and time when the login operation is received.

  When the extraction unit 102c receives a notification indicating that the login operation sent from the login monitoring unit 102a has been received, the extraction unit 102c is stored in the user identification information and the user management file 104a input at the time of the login operation. Based on the user management information, user attribute information corresponding to the user identification information is extracted.

  Based on the date and day of the week acquired by the acquisition unit 102b, the user attribute information extracted by the extraction unit 102c, and the priority information stored in the priority file 104g, the selection unit 102d Of the usage time information by whole date, the usage time information by individual day of the week, and the usage time information by individual date, the one that is applied with the highest priority to the user who performed the login operation is selected.

  The determination unit 102e determines whether or not to permit the user who performed the login operation to log in to the system at the time based on what is selected by the selection unit 102d and the time acquired by the acquisition unit 102b.

  If the determination result in the determination unit 102e indicates that login is not possible, the display execution unit 102f displays a predetermined error notification indicating that login is not possible on the output device 114.

  When the determination result in the determination unit 102e indicates that login is not possible, the operation management unit 102g does not allow the user who performed the login operation determined to be unable to log in to the operation after the login operation. (Ban).

[3. processing]
An example of a system usage time management process performed by the system usage time management apparatus 100 configured as described above will be described in detail with reference to FIG. FIG. 10 is a flowchart illustrating an example of the system usage time management process.

  First, when receiving a login notification indicating that a login operation to the system including an input of a user ID has been received from the login monitoring unit 102a, the acquiring unit 102b acquires the date, day of the week, and time of receiving the login operation (step SA1).

  Further, when the extraction unit 102c receives a login notification from the login monitoring unit 102a, the extraction unit 102c corresponds to the user ID based on the user ID input during the login operation and the user management information stored in the user management file 104a. The group ID to be extracted is extracted (step SA2).

  Next, the selection unit 102d selects the date and day of the week acquired in step SA1, the group ID extracted in step SA2, the individual setting management information stored in the individual setting management file 104f, and the priority stored in the priority file 104g. System-wide day-by-system usage time information stored in the system-wide day-of-system usage time file 104b, system-wide day-by-system usage time information stored in the system-wide date usage time file 104c, and individual day of the week Of the usage time information by individual day stored in the separate usage time file 104d and the usage time information by individual date stored in the usage time file by individual date 104e, the highest priority is applied to the user who performed the login operation. What to do (in other words, applicable to the user who performed the login operation Highest priority ones) elect (step SA3).

  Specifically, first, by referring to the individual setting management information based on the group ID, it is confirmed whether or not there is a usage time ID associated with the group ID. As a result of the confirmation, if there is a usage time ID, it means that there is a pair of usage time information by individual day and usage time information by individual date corresponding to the usage time ID. In addition to the system-wide usage time information by date, reference is made to the usage time information by individual day of the week and usage time information by individual date corresponding to the usage time ID, in descending order of priority, against the acquired date and day of the week. To do. In addition, if there is no usage time ID as a result of the confirmation, there is no pair of usage time information by individual day and usage time information by individual date corresponding to the usage time ID. The time information and the system-wide usage time information by date are referred to in order from the highest priority while checking the acquired date and day of the week. As a result of the reference, the highest priority that is applicable to the user who performed the login operation is selected.

  Next, the determination unit 102e selects at step SA3 (any one of system-wide day-of-day usage time information, system-wide day-by-day usage time information, individual day-of-day usage time information, and individual date-specific usage time information) and step Based on the time acquired in SA1, it is determined whether or not the user who performed the login operation is permitted to log in to the system at the time (step SA4).

  Next, when the determination result in step SA4 is that login is impossible (step SA5: Yes), the display execution unit 102f displays a predetermined error notification on the output device 114 that login is impossible. (Step SA6) The operation management unit 102g prohibits the user who has performed the login operation that is determined to be unable to log in from the login operation after the login operation (Step SA7).

[4. Summary of this embodiment]
As described above, according to the present embodiment, when a login operation including an input of a user ID is received, (1) the date, day of the week and time when the login operation is received are acquired, and (2) during the login operation. The group ID corresponding to the user ID is extracted based on the input user ID and the user management information stored in advance, and (3) the acquired date and day of the week, the extracted group ID, and the individual setting management information stored in advance In addition, based on the priority information stored in advance, the login operation is performed among the pre-stored system-wide day-of-day usage time information, system-wide day-of-day usage time information, individual day-of-day usage time information, and individual date-specific usage time information. Select the one that has the highest priority for the user who performed, and (4) the time of the user who performed the login operation based on the selected one and the acquired time It determines whether or not to permit the login. As a result, it is possible not only to prevent unauthorized access by the user, but also to reduce the work load for managing the setting of the system usage time and to improve the convenience of management of the setting. Specifically, the system usage time can be set flexibly by combining the settings for each system or user with the settings for each day of the week or each day, so the system usage time can be set according to the daily system operation. Can reduce the workload for managing the system. For example, even when the number of users is large, it is possible to reduce the work load required for batch setting of usage time and setting change of usage time.

  Further, according to the present embodiment, the priority information includes the usage time information by individual date, the usage time information by the entire system date, the usage time information by the individual day of the week, and the usage time information by the system day of the week in descending order of priority. It is what. Thereby, it is possible to determine whether or not login is possible by giving priority to exceptional use time settings such as holidays.

  Finally, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the above-described embodiments. For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. Further, the processing procedure, control procedure, specific name, information including registration data and parameters of each processing shown in this specification and the drawings can be arbitrarily changed unless otherwise specified. Further, regarding the system usage time management apparatus 100, each illustrated component is functionally conceptual and does not necessarily need to be physically configured as illustrated. Further, the specific form of distribution / integration of the devices is not limited to that shown in the figure, and all or a part thereof may be functionally or physically in arbitrary units according to various additions or according to functional loads. It can be configured to be distributed and integrated.

  The system usage time management program according to the present invention is recorded on a computer-readable recording medium, which will be described later, and is mechanically read by the system usage time management apparatus 100 as necessary. That is, in the storage unit 104 such as a ROM or an HD, computer programs for giving instructions to the CPU in cooperation with the OS and performing various processes are recorded. The computer program is executed by being loaded into a RAM or the like, and constitutes the control unit 102 in cooperation with the CPU. Here, the “recording medium” is an arbitrary “portable physical medium” such as a flexible disk, a magneto-optical disk, a ROM, an EPROM, an EEPROM, a CD-ROM, an MO, and a DVD, and is incorporated in various computer systems. Program in a short time, such as a communication line or carrier wave when transmitting a program via any “fixed physical medium” such as ROM, RAM, HD, or a network such as LAN, WAN, or the Internet The “communication medium” that holds The “program” is a data processing method described in an arbitrary language or description method, and may be in any format such as source code or binary code. Note that the “program” is not necessarily limited to a single configuration, and functions are achieved in cooperation with a separate configuration such as a plurality of modules and libraries or a separate program represented by the OS. Including things. Note that a well-known configuration and procedure can be used for a specific configuration for reading a recording medium, a reading procedure, an installation procedure after reading, and the like in each device described in the embodiment.

  As described above, the system use time management apparatus, system use time management method, and system use time management program according to the present invention can be widely implemented in various fields such as the information processing industry and are extremely useful.

DESCRIPTION OF SYMBOLS 100 System use time management apparatus 102 Control part 102a Login monitoring part 102b Acquisition part 102c Extraction part 102d Selection part 102e Determination part 102f Display execution part 102g Operation management part 104 Storage part 104a User management file 104b System use time file according to day of week 104c System Use time file by whole date 104d Use time file by individual day of day 104e Use time file by individual date 104f Individual setting management file 104g Priority file 106 Communication interface unit 108 Input / output interface unit 112 Input device 114 Output device 200 Network

Claims (8)

A system usage time management device comprising a control unit and a storage unit,
The storage unit
Target identification information for uniquely identifying a target to which usage time information relating to a time when the system can be used and / or a time when the system cannot be used is applied;
The usage time information is set for each day of the week, and the system-wide usage time information applicable to all the objects and the usage time information are set for each day of the week, and the usage for each specific day applicable to the specific object set of time information or the usage time information applicable entire system by date use time information Ho及 beauty the usage time information is the specific is set by date for all the target is set by date A set of usage time information by individual date applicable to the target,
Store
The controller is
When receiving the operation to the system including the input of the object identification information, date Fumata is the day of the week, an acquisition unit for acquiring time,
The date Fumata acquired by the acquisition means on the basis of the day of the week, and the subject identification information input during the operation, among the information included in the set, selecting of selecting those that apply to the subject Means,
Determination means for determining whether to permit use of the system at the target time of the target based on what is selected by the selection means and the time acquired by the acquisition means;
A system usage time management device characterized by comprising: The storage unit further stores target management information including target attribute information related to the target attribute,
The target identification information is stored in the storage unit in a form included in the target management information,
Information applicable to a specific of the target included in the set are those applicable to the target corresponding to a particular said attribute,
The control unit further includes extraction means for extracting the target attribute information corresponding to the target identification information based on the target identification information and the target management information input at the time of the operation,
Wherein the selecting means, the target attribute information is used Rukoto extracted by the extraction means in place of the object identification information,
The system use time management apparatus according to claim 1 . The storage unit further stores priority information related to priority when the information included in the set is applied to the target,
The selection means further selects, based on the priority information, information that is applied to the target with the highest priority among information included in the set ;
The system use time management apparatus according to claim 2 . If included previous SL entire system by day use time information and the individual day of week usage time information to the set is in the set may be applied wherein the usage time information on all of the target is set by date System-wide use time information by date and / or the use time information set by date, and further include use time information by individual date applicable to the specific target, and the set is used by the system-wide date. when the time information and the Ru contains individual by date use time information is in the set is the usage time information applicable system entire day of week usage time to all of the target is set for each day of the week information And / or the usage time information is set for each day of the week and further includes usage time information for each individual day applicable to the specific target ,
The acquisition means acquires the day of the week and the date ,
Wherein the selecting means, Rukoto both are used in the day and the date obtained by the obtaining means,
The system usage time management apparatus according to claim 3 . The front Symbol set, the individual day of week use time information and the individual by date use time information is included,
Individual setting identification information for uniquely identifying a pair of the individual day usage time information and the individual date usage time information is given to the individual day usage time information and the individual date usage time information. And
The storage unit further stores individual setting management information including the individual setting identification information and the target attribute information,
Wherein the selecting means further the individual setting management information is used Rukoto,
The system usage time management apparatus according to claim 4 . The set includes usage time information for the entire system day of the week and usage time information for the entire system date,
The system use time management apparatus according to claim 4 or 5 . A system usage time management method executed in an information processing device including a control unit and a storage unit,
The storage unit
Target identification information for uniquely identifying a target to which usage time information relating to a time when the system can be used and / or a time when the system cannot be used is applied;
The usage time information is set for each day of the week, and the system-wide usage time information applicable to all the objects and the usage time information are set for each day of the week, and the usage for each specific day applicable to the specific object set of time information or the usage time information applicable entire system by date use time information Ho及 beauty the usage time information is the specific is set by date for all the target is set by date A set of usage time information by individual date applicable to the target,
Store
Executed in the control unit,
When receiving the operation to the system including the input of the object identification information, date Fumata is the day of the week, an acquisition step of acquiring time,
The date Fumata obtained by the obtaining step on the basis of the day of the week, and the subject identification information input during the operation, among the information included in the set, selecting of selecting those that apply to the subject Steps,
A determination step for determining whether to permit the use of the system at the target time of the target based on the selection at the selection step and the time acquired at the acquisition step;
A system usage time management method characterized by comprising: A system usage time management program for execution in an information processing apparatus including a control unit and a storage unit,
The storage unit
Target identification information for uniquely identifying a target to which usage time information relating to a time when the system can be used and / or a time when the system cannot be used is applied;
The usage time information is set for each day of the week, and the system-wide usage time information applicable to all the objects and the usage time information are set for each day of the week, and the usage for each specific day applicable to the specific object set of time information or the usage time information applicable entire system by date use time information Ho及 beauty the usage time information is the specific is set by date for all the target is set by date A set of usage time information by individual date applicable to the target,
Store
For executing in the control unit,
When receiving the operation to the system including the input of the object identification information, date Fumata is the day of the week, an acquisition step of acquiring time,
The date Fumata obtained by the obtaining step on the basis of the day of the week, and the subject identification information input during the operation, among the information included in the set, selecting of selecting those that apply to the subject Steps,
A determination step for determining whether to permit the use of the system at the target time of the target based on the selection at the selection step and the time acquired at the acquisition step;
A system usage time management program characterized by including:

Images