JP6437414B2 - Job management system - Google Patents

Description

  The present invention relates to a technique for managing jobs executed in a distributed manner by a plurality of terminal devices.

  Background of recent years, such as high performance of hardware such as client PCs (Personal Computers) and ultra-compact computers, higher functionality of software such as OS (Operating System) and applications, and expansion of infrastructure development such as wireless environment and cloud As a result, (a) using information detected by a terminal device such as a sensor, (b) the terminal device performs a part of work such as data processing and extraction performed by a conventional server, etc. In addition, business systems are being expanded and distributed.

  On the other hand, in a job management system that automatically executes jobs executed by a computer, a centralized management method in which a manager machine that manages jobs controls execution of jobs by issuing instructions to the machines that execute jobs is generally used. Has been used. When the centralized management method is used, there is a concern that the load on the manager machine increases. Further, there is a concern that man-hours for operating the job management system on the manager machine will increase as the job becomes more complicated.

  Patent Document 1 below discloses a system that reduces the amount of work when changing the job execution schedule and prevents work leakage.

Japanese Patent Laid-Open No. 2015-064848

  When centrally managing multiple terminal devices that execute jobs, if the terminal configuration changes due to expansion, replacement, or removal of terminal devices, the job administrator who manages the job definition Each time the job definition must be changed to match the changed terminal configuration. The greater the number of terminal devices, the greater the amount of work, and the greater the burden on humans and costs.

  Since the above-mentioned patent document 1 employs a method for centrally managing terminal devices, the above-described problem may occur. This document considers reducing the amount of work when changing the job execution schedule, but does not consider changing the configuration of the terminal device that executes the job. Therefore, even if the technique described in the document is used, it is considered that the above-mentioned problem relating to the configuration change of the terminal device remains.

  The present invention has been made in view of the problems as described above, and when there is a change in the configuration of the terminal device that executes jobs in a distributed manner, the change can be reflected efficiently. An object is to provide a job management system.

  In the job management system according to the present invention, a group member terminal that belongs to a group sends a message to the group that the user has newly entered or left the group, and distributes the job to the group member terminal. Manages the job distribution destination according to the message.

  According to the job management system of the present invention, when there is a change in the configuration of a terminal device that executes a job, an autonomous distributed job management system that efficiently reflects the change can be provided.

1 is a system configuration diagram of a job management system 1000. FIG. It is a functional block diagram explaining the structure of client terminal 300A-300I. It is a block diagram of the group to which the client terminal 300 belongs. It is a figure which shows the structure and data example of the own terminal data 350 which the client terminal 300 hold | maintains. It is a figure which shows the structure and data example of the group data 360 which the client terminal 300 hold | maintains. It is a figure which shows the structure and example of data of the member list 370 which the client terminal 300 hold | maintains. 5 is a diagram illustrating a configuration of a destination list 334 and data examples. FIG. 3 is a diagram illustrating a configuration of a job distribution data 800 and an example of data. FIG. 2 is a diagram illustrating a configuration of job definition data 900 and an example of data. FIG. It is a sequence diagram explaining the procedure for a child terminal to newly enter and leave a group. It is a sequence diagram explaining the procedure which takes over the role of the terminal which a leader uses to another terminal, and withdraws from a group. FIG. 10 is a sequence diagram illustrating a procedure for distributing a job by a parent terminal. It is a sequence diagram explaining the procedure which the terminal which a reader uses requests substitution to other terminals, and returns after that.

  FIG. 1 is a system configuration diagram of a job management system 1000 according to the present invention. The information system department 100 centrally manages the operation of the job management system 1000. The data center / cloud 200 hosts various servers such as a database server and a Web server, and these servers hold data managed by the job management system 1000. Each of the client terminals 300A to 300I accesses a server hosted by the data center / cloud 200 and uses a business system provided by these servers. An autonomous distributed job management program is installed in the client terminals 300A to 300I. The information system department 100 assigns a job to each client terminal, and each client terminal executes the job in a distributed manner.

  In the system configuration shown in FIG. 1, let us consider that the client terminals 300A to 300I execute a job such as collecting log files every night in a distributed manner. In order to execute a distributed job, it is necessary to define a job to be executed by each client terminal in the information system department 100. However, the configuration of the client terminal may be frequently changed by adding, replacing, or removing devices. Therefore, it may take an enormous amount of time for the information system department 100 to sequentially grasp the configuration of the client terminals 300A to 300I and reflect the change in the job definition.

  Therefore, in the present invention, the client terminal 300A is regarded as a representative terminal, and the information system department 100 manages only the client terminal 300A. That is, the information system department 100 distributes a job that the job management system 1000 wants to execute only to the client terminal 300A. Furthermore, the client terminal 300A manages only the client terminal 300B. That is, the client terminal 300A distributes the received job only to the client terminal 300B.

  In this way, in the job management system 1000, each terminal manages a group composed of its own terminal and a lower-level terminal that is a management target thereof. Therefore, even when the device configuration of the client terminal is changed, the change only needs to be managed between the client terminals forming the group, and the information system department 100 can grasp only the change of the client terminal 300A. It will be enough. Accordingly, the job management system 1000 can have autonomy to manage the terminal configuration within the group of the client terminals 300 in addition to executing the job in a distributed manner.

  FIG. 2 is a functional block diagram illustrating the configuration of the client terminals 300A to 300I. Since each client terminal has the same configuration, the alphabetic suffix is omitted when referring to them collectively. The client terminal 300 includes a user interface unit 310, a job execution control unit 320, a group configuration management unit 330, and a cooperation unit 340.

  The user interface unit 310 provides a GUI (Graphical User Interface) for a user to operate the client terminal 300 on a display terminal such as a display provided in the client terminal 300, for example. The user can create a definition of a new job using the GUI. Examples of job types include: (a) jobs related to business (log acquisition, etc.), (b) jobs that distribute jobs to other client terminals 300, (c) new entry or withdrawal from groups, (d There are jobs such as :) suspension and return from suspension, (e) taking over of role. Details of the above (b) to (e) will be described later in FIG. Instead of the GUI, other user interfaces such as a command line interface may be used, or these may be used in combination.

  The job execution control unit 320 is a functional unit that executes an assigned job. The job execution control unit 320 includes a definition reading unit 321, a schedule calculation unit 322, and a job execution processing unit 323.

  The definition reading unit 321 reads the job definition input from the user interface unit 310. The schedule calculation unit 322 calculates a job execution schedule according to the job definition. The job execution processing unit 323 executes the job according to the schedule and outputs the result as an execution result log 324. Details of the job definition will be described later with reference to FIGS.

  The group configuration management unit 330 is a functional unit that manages the groups of the client terminals 300. The group configuration management unit 330 includes a table reading unit 331, a table update unit 332, and a destination list generation unit 333.

  The table reading unit 331 reads each table described with reference to FIGS. The table updating unit 332 updates each table according to an operation sequence described in FIG. The destination list generation unit 333 recognizes the client terminals 300 belonging to the group according to the description of each table, and generates a destination list 334 describing a list of client terminals 300 to which a message is to be transmitted.

  The cooperation unit 340 is a functional unit that transmits and receives messages to and from other client terminals 300. The cooperation unit 340 includes a destination list reading unit 341 and a message communication unit 342. The destination list reading unit 341 reads the destination list 334. The message communication unit 342 transmits a message via the network 400 to the destinations described in the destination list 334. A message is received via the network 400.

  Each functional unit of the client terminal 300 is configured as a software module that forms part of an autonomous distributed job management program, for example, and can be realized by an arithmetic device such as a CPU (Central Processing Unit) executing the software module. Instead, all or some of the functional units can be implemented by hardware such as a circuit device.

  FIG. 3 is a configuration diagram of a group to which the client terminal 300 belongs. Groups can also be organized hierarchically. Each client terminal 300 can belong to a plurality of groups. Here, an example is shown in which the client terminals 300 used by each user belonging to the department of the company are grouped according to the organizational structure of the department.

  The client terminal 300B used by the supervisor B belongs to the group 510 corresponding to the first group (hereinafter referred to as 1G) to which the supervisor B belongs. The boss B is a leader of a second unit (hereinafter referred to as second U) that is a subgroup in the first G. Accordingly, the client terminals 300B to 300E belong to the group 511 that is a lower group of the group 510. Reflecting the above group structure, the client terminal 300B has the client terminal 300A as a parent terminal, and the client terminals 300C to 300E used by the responsible CEs belonging to the second U as child terminals.

  Chief B and responsible C to E also belong to the labor union Yokohama area. Therefore, the client terminals 300B to 300E belong to the group 520 corresponding thereto. The head of the labor union Yokohama area is foreman X. The client terminal 300X used by the foreman X is a parent terminal of the client terminals 300B to 300E.

  FIG. 4 is a diagram illustrating a configuration of the own terminal data 350 held by the client terminal 300 and a data example. The own terminal data 350 is data describing the attributes of the own terminal that does not depend on the configuration of the terminal group. The own terminal data 350 includes an own terminal ID 351, an own terminal name 352, an IP address 353, a mail address 354, and a profile 355.

  The own terminal ID 351 is an ID for uniquely identifying the client terminal 300 in the job management system 1000. The own terminal name 352 is the name of the client terminal 300. The IP address 353 is a network address of the client terminal 300 in the job management system 1000. The mail address 354 is an electronic mail address of a user who uses the client terminal 300. The profile 355 is a parameter that describes other attributes of the client terminal 300. For example, the location where the client terminal 300 is installed can be described. The profile 355 preferably describes attributes that do not depend on the configuration of the terminal group.

  The contents of the own terminal data 350 can be set by the user who uses the client terminal 300, or may be set in advance when the information system department 100 distributes the client terminal 300 to the user.

  FIG. 5 is a diagram illustrating a configuration of the group data 360 held by the client terminal 300 and a data example. The group data 360 is data describing information related to the group to which the terminal belongs. The group data 360 is data input by the user when newly entering the group, as will be described later with reference to FIG. The group data 360 includes a group name 361, a leader group name 362, a parent terminal ID 363, a proxy terminal ID 364, and a profile 365.

  The group name 361 is the name of the group to which the own terminal belongs. The leader group name 362 is the name of the group whose own terminal is the leader. The parent terminal ID 363 is an ID of the parent terminal of the own terminal. The proxy terminal ID 364 is an ID of a proxy terminal that acts on behalf of the own terminal when the own terminal stops operating. The profile 365 is a parameter that describes other attributes of the terminal, and can describe, for example, a job title in the group.

  The data example shown in FIG. 5 is for the client terminal 300B. Since the boss B belongs to the 1G and the labor union Yokohama area, and the client terminal 300B also belongs to the groups 510 and 520 corresponding thereto, information on these two groups is described in each record.

  The record on the first line relates to the first G. Since the chief B is the second U leader, the leader group name 362 describes that fact. The parent terminal ID 363 is the ID of the client terminal 300A. The representative terminal ID 364 can be arbitrarily set by the supervisor B when newly entering the group. Here, the ID of the client terminal 300C is used.

  The record on the second line relates to the labor union Yokohama area. Since the chief B is not a leader in the labor union Yokohama area, the leader group name 363 is not set. The parent terminal ID 363 is an ID of the client terminal 300X.

  FIG. 6 is a diagram illustrating a configuration and data example of the member list 370 held by the client terminal 300. The member list 370 is data listing client terminals 300 belonging to the same group as the own terminal. Each record in the member list 370 corresponds to each terminal belonging to the group. The member list 370 has a group name 371, a leader group name 372, a terminal ID 373, a proxy terminal ID 374, and a state 375.

  The group name 371 is the name of the group to which the terminal belongs. For terminals belonging to a plurality of groups, respective group names may be described. The leader group name 372 is a name of a group in which the terminal is a leader. The terminal ID 373 is the ID of the terminal. The proxy terminal ID 374 is an ID of a terminal acting on behalf of the terminal. A state 375 indicates whether or not the terminal is operating.

  The data example shown in FIG. 6 is for the client terminal 300B. According to the group configuration shown in FIG. 3, records relating to 300A, 300C, 300D, 300E, and 300X held by the client terminal 300 are described.

  It is assumed that the member list 370 does not hold records relating to other terminals belonging to the same hierarchy as the own terminal. For example, the client terminal 300C belonging to the second U does not have a record regarding the client terminals 300D and 300E belonging to the second U.

  The member list 370 can hold information related to the parent terminal as well as information related to the child terminal for convenience of processing. In the data example shown in FIG. 6, information about client terminals 300A and 300X that are parent terminals of the client terminal 300B is also described. This eliminates the need to refer to the group data 360 one by one in order to identify the other party with which the terminal is to communicate, which is convenient from the viewpoint of simplification of processing.

  Further, in the member list 370, in addition to the ID of each terminal, the attributes of the user of the terminal (that is, the group name 371 and the leader group name 372) are also described, so that the group on the organization can be described. Work to distribute jobs can be performed efficiently.

  The member list 370 is mainly meaningful for enumerating child terminals of its own terminal. However, for the convenience of processing, it is possible to hold a record for the parent terminal. Which terminal in the member list 370 is the parent terminal can be determined by referring to the group data 360.

  FIG. 7 is a diagram illustrating a configuration of the destination list 334 and data examples. The destination list 334 is data describing communication destination addresses of other terminals with which the client terminal 300 communicates. The destination list 334 includes a terminal ID 3341, a terminal name 3342, an IP address 3343, and a mail address 3344.

  Terminal ID 3341 and terminal name 3342 are the ID and name of the destination terminal, respectively. The IP address 3343 and the mail address 3344 are addresses of destination terminals, respectively. These addresses only need to hold addresses corresponding to the communication means. For example, if only e-mail is used as the communication means, a mail address 3344 is sufficient. When connecting directly to the IP address of the destination terminal, the IP address 3343 is required. When other communication means are used, an address corresponding to the means may be described. The specific value of the address can be notified in accordance with a sequence described later with reference to FIG. 10 when each terminal newly enters.

  Records to be held in the destination list 334 (that is, a list of destination terminals) can be extracted from the group data 360 and the member list 370. The client terminal 300 communicates with the proxy terminal as described in a sequence diagram described later. Therefore, the proxy terminal ID 364 can be used as the ID of the destination terminal. Further, the client terminal 300 communicates with each member terminal of the group. Therefore, the terminal ID 373 can be used as the ID of the destination terminal.

  The destination list 334 can be created each time a destination is enumerated when a message is transmitted, or can be created in advance by enumerating all terminals that are candidates for destination.

  FIG. 8 is a diagram showing the configuration of the job distribution data 800 and an example of data. The job distribution data 800 is data distributed to each client terminal 300 by a terminal that distributes a job. The job distribution data 800 includes a distribution job 801, a distribution destination group 802, a distribution destination profile 803, and a distribution success condition 804.

  The distribution job 801 is the name of the job to be distributed. The distribution destination group 802 is a name of a destination group to which the job is distributed. The distribution destination profile 803 is a profile of a terminal that should receive the job. The distribution success condition 804 is, for example, (a) what percentage of terminals belonging to the distribution destination group 802 can be considered to be successful if the job can be distributed, and (b) how many terminals belong to the distribution destination group 802. On the other hand, it is possible to describe a condition such as whether the distribution is considered successful if the job can be distributed.

  The user who distributes the job inputs data as illustrated in FIG. 8 through the user interface unit 310 of the client terminal 300 used by the user. The terminal distributes the job distribution data 800 together with the job to be distributed to terminals belonging to the group designated by the distribution destination group 802. A list of terminals belonging to the group can be acquired from the member list 370. The client terminal 300 that has received the job distribution data 800 executes the job if, for example, the profile of the terminal matches the distribution destination profile 803, and does not execute the job if the profile does not match. As the distribution destination profile 803, only one of the profile 355 and the profile 365 can be designated, or both can be designated. When both are specified, the job may be executed only when both match, or the job may be executed when either one matches.

  FIG. 9 is a diagram illustrating a configuration of the job definition data 900 and a data example. The job definition data 900 is data that defines the contents of a job to be distributed. A user who distributes a job inputs a job definition as illustrated in FIG. 9 via the user interface unit 310 of the client terminal 300 used by the user.

  The job definition can be described by, for example, an execution schedule and a job flow, but is not limited thereto. The execution schedule can be defined by an execution date and an execution time, for example. The job flow is defined by connecting processes to be executed in the job on the user interface unit 310 according to the execution order. A program describing the contents of each process can be distributed together with the job, or can be distributed in advance.

  FIG. 10 is a sequence diagram illustrating a procedure for a child terminal to newly enter and leave a group. Here, an example in which the client terminal 300E newly enters the group 511 and then withdraws from the group 511 will be described.

(FIG. 10: Step S1001)
The person in charge E executes a job for newly entering the group via the user interface unit 310 of the client terminal 300E. At this time, (a) the IP address 3343 or mail address 3344 of the client terminal 300B as the parent terminal, (b) the name of the group to newly join, and (c) the leader group name if the own terminal is the leader terminal are designated. . In the process of executing the job, the client terminal 300E transmits a message to the effect that a new entry is made to the group to the client terminal 300B. In the message, the contents of the own terminal data 350 of the client terminal 300E, and the specified group name and leader group name are described.

(FIG. 10: Step S1002: Part 1)
When receiving the new entry message, the client terminal 300B adds the content of the own terminal data 350 of the client terminal 300E described in the message to the destination list 334. Furthermore, the client terminal 300B adds the specified group name and leader group name and the terminal ID of the client terminal 300E as records in the member list 370. The state 375 of the added record is set to “active”. The client terminal 300B transmits a confirmation message to the client terminal 300E.

(FIG. 10: Step S1002: Part 2)
In the confirmation message transmitted by the client terminal 300B, the contents of the own terminal data 350 of the client terminal 300B and the contents of the group data 360 of the client terminal 300B are described. Upon receiving the confirmation message, the client terminal 300E adds the content of the own terminal data 350 of the client terminal 300B described in the message to the destination list 334. Furthermore, the client terminal 300E adds the contents of the group data 360 of the client terminal 300B and the terminal ID of the client terminal 300B as records in the member list 370. The state 375 of the added record is set to “active”.

(FIG. 10: Step S1003)
The person in charge E executes a job for leaving the group via the user interface unit 310 of the client terminal 300E. At this time, the group name of the group to be withdrawn is specified. In the process of executing the job, the client terminal 300E transmits a message indicating withdrawal from the group to the client terminal 300B. In the message, the terminal ID 351 of the client terminal 300E, the group name 361 of the group data 360 held by the client terminal 300E, and the leader group name 362 are further described when the own terminal is a leader terminal.

(FIG. 10: Step S1004: Part 1)
When the client terminal 300B receives the withdrawal message, the client terminal 300B deletes, from the member list 370, a record that matches the own terminal ID, group name, and leader group name of the client terminal 300E described in the message. Furthermore, the client terminal 300 </ b> B deletes from the destination list 334 records relating to terminals that do not exist in the group data 360 and the member list 370. Thereafter, the client terminal 300B transmits a confirmation message to the client terminal 300E.

(FIG. 10: Step S1004: Part 2)
When the client terminal 300E receives the confirmation message, the client terminal 300E deletes the record regarding the group to be withdrawn from the group data 360, and deletes the record regarding the parent terminal from the member list 370. Further, when there is no record related to the parent terminal in the group data 360 and the member list 370, the client terminal 300E deletes the record related to the parent terminal from the destination list 334.

  FIG. 11 is a sequence diagram illustrating a procedure for taking over the role of a terminal used by a leader to another terminal and withdrawing from the group. Here, an example will be described in which the client terminal 300B takes over the role of the client terminal 300E and leaves the group 511. For example, the situation as in this example occurs when the supervisor B is transferred to another group. Since the client terminal 300B in the group 511 is the parent terminal of the client terminals 300C to 300E, the client terminal 300B has a role of distributing jobs to these terminals.

(FIG. 11: Step S1101)
The chief B executes a job for taking over the role via the user interface unit 310 of the client terminal 300B. At this time, (a) the group name to be withdrawn and (b) the ID of the terminal requesting to take over the role are designated. In the process of executing the job, the client terminal 300B transmits a takeover request message to the client terminal 300E. In the message, all records related to the group among the records of the group data 360, the member list 370, and the destination list 334 held by the client terminal 300B are extracted and described.

(FIG. 11: Step S1102)
When the client terminal 300E receives the takeover request message, the client terminal 300E adds the records described in the message to the data held by the terminal, and transmits a confirmation message to the client terminal 300B.

(FIG. 11: Step S1103)
When the client terminal 300B receives the confirmation message, the client terminal 300B notifies each terminal described in the destination list 334 (except for the client terminal 300E that is the takeover destination) that the role has been taken over by the client terminal 300E. Send. Each terminal that has received the message overwrites the record relating to the client terminal 300B with the record relating to the client terminal 300E. As a result, the role performed by the client terminal 300B is taken over by the client terminal 300E.

  FIG. 12 is a sequence diagram illustrating a procedure for distributing a job by the parent terminal. Here, an example will be described in which the client terminal 300A distributes a job according to the job definition illustrated in FIGS.

(FIG. 12: Step S1201: Part 1)
The section manager A inputs the job definition and the like exemplified in FIGS. 8 to 9 via the user interface unit 310 of the client terminal 300A, and instructs to distribute the job (that is, job distribution data 800 and job definition data 900). To do. The client terminal 300A identifies its own client terminal 300B according to the description of the group data 360 and the member list 370, and distributes job distribution data 800 and job definition data 900 thereto. Here, as shown in the data example of FIG. 8, it is assumed that only the profile 355 is designated as the distribution destination profile 803.

(FIG. 12: Step S1201: Part 2)
The client terminal 300B compares the distribution destination profile 803 of the received job distribution data 800 with the profile 355 of its own terminal. In the data example shown in FIGS. 4 and 8, since the distribution destination profile 803 is “in charge”, it can be understood that a person whose job title is “in charge” should receive the job. Since the profile 355 is “chief”, the client terminal 300B is not the destination of the job. Therefore, the client terminal 300B further transmits the received job to its own child terminal.

(FIG. 12: Step S1202)
According to the group data 360 and the member list 370 held by the client terminal 300B, the child terminals of the client terminal 300B are the client terminals 300C to 300E. The client terminal 300B distributes the received job to these terminals.

(FIG. 12: Step S1203)
Since the profile 355 is “in charge”, the client terminals 300 </ b> C to 300 </ b> E consider the received job to be executed by the own terminal, and register it on the own terminal as an execution scheduled job according to the execution schedule. The client terminals 300C to 300E transmit a message indicating that the job reception has been completed to the client terminal 300B.

(FIG. 12: Step S1204)
When receiving the job acceptance completion message from the child terminal, the client terminal 300B determines whether or not the distribution success condition 804 is satisfied. For example, when the job acceptance completion message is received from all the child terminals, the distribution success rate is 100%. The client terminal 300B notifies the determination result to the client terminal 300A that is the job distribution source. The client terminal 300A receives the notification. If the distribution is successful, the job distribution is completed. If the distribution is unsuccessful, for example, redistribution is performed after a predetermined time interval.

  FIG. 13 is a sequence diagram for explaining a procedure in which a terminal used by a reader requests another terminal for substitution and then returns. Here, an example will be described in which the client terminal 300B requests the client terminal 300C for substitution in accordance with the record in the first line of FIG.

(FIG. 13: Step S1301)
When the supervisor B temporarily stops the second U job due to a business trip or the like, for example, the client terminal 300C acts as the parent terminal of the client terminal 300B via the user interface unit 310 of the client terminal 300B. Run the job. The client terminal 300B transmits a proxy request message to the client terminal 300C during the job execution process. In the message, (a) the ID of the client terminal 300A that is the parent terminal of the client terminal 300B, and (b) the IDs of the client terminals 300D and 300E belonging to the same group in the member list 370 are described. Information about the client terminal 300C itself is not necessary.

(FIG. 13: Step S1302)
Upon receiving the proxy request message, the client terminal 300C reflects the terminal ID described in the message on the group data 360 and the member list 370, and returns a confirmation message.

(FIG. 13: Step S1303: Part 1)
When the client terminal 300B receives the confirmation message from the client terminal 300C, the client terminal 300B notifies the parent terminal (300A) and the child terminals (300D and 300E) of the own terminal that the operation of the own terminal is stopped and taken over to the client terminal 300C. Send. In the message, the content of the own terminal data 350 of the client terminal 300C is described.

(FIG. 13: Step S1303: Part 2)
Each terminal that receives the stop message from the client terminal 300B changes (a) the state 375 of the client terminal 300B in the member list 370 to “stopped”, and (b) changes to the proxy terminal ID 374 of the client terminal 300B in the member list 370. The ID of the client terminal 300C is set, and (c) the content of the own terminal data 350 of the client terminal 300C is added to the destination list 334.

(FIG. 13: Step S1304)
Assume that section manager A distributes a job in the same manner as described in FIG. In principle, the client terminal 300A distributes the job to the client terminal 300B, which is its own child terminal, according to the description of the member list 370, but here the state 375 of the client terminal 300B is “stopped”. Instead, the job is distributed to the client terminal 300C in accordance with the description of the proxy terminal ID 374.

(FIG. 13: Steps S1305 to S1307)
The client terminal 300C considers the received job to be executed by the own terminal according to the description of the distribution destination profile 803, and registers it on the own terminal as an execution scheduled job according to the execution schedule. Furthermore, the client terminal 300C distributes the job to the client terminals 300D and 300E that are the child terminals of the client terminal 300B according to the description of the member list 370. The job reception completion message (S1306) and determination result notification (c) S1307) are the same as steps S1203 to S1204 in FIG. 12 except that the operating subject is the client terminal 300C.

(FIG. 13: Step S1308)
When the supervisor B resumes the work of the second U, it executes a job for returning the role of the client terminal 300B as the parent terminal via the user interface unit 310 of the client terminal 300B. The client terminal 300B transmits a return message to each terminal during the job execution process. Each terminal that has received the return message changes the state 375 of the client terminal 300B in the member list 370 to “active” and clears the proxy terminal ID 374.

(FIG. 13: Step S1309)
Upon receiving the return message, the client terminal 300C transmits a record related to the child terminal described in the member list 370 to the client terminal 300B. This is because the state 375 of these terminals, the proxy terminal ID 374, and the like may be changed while the client terminal 300B is stopped. For example, when the client terminal 300B carries out the same takeover to 300E while the client terminal 300B is stopped, the state 375 and the proxy terminal ID 374 of these terminals reflect the takeover, so this is notified. There is a need to.

<Summary of the present invention>
In the job management system 1000 according to the present invention, the client terminals 300 are divided into groups having a hierarchical structure, and the configurations of the terminals belonging to the group are managed by new entry messages and withdrawal messages in the group. This eliminates the need for centralized management of the terminal configuration within the group, and can be delegated to the autonomous operation of each group. Therefore, the job management system can be configured in an autonomous and distributed manner.

  In the job management system 1000 according to the present invention, a terminal that distributes a job to a group member terminal can take over the role of another terminal. The takeover may be temporary (FIG. 13), or may be taken over definitely (FIG. 11) when, for example, the user moves. This takeover operation is performed only within the group and with the parent terminal of the leader terminal. Accordingly, the terminal configuration can be flexibly changed without impairing the autonomous decentralization of the job management system 1000.

  In the job management system 1000 according to the present invention, the member list 370 can describe the profile of the user of the terminal together with the ID of the group member terminal. As a result, the user who distributes the job can designate the distribution destination while referring to the profile on the organization, so that the efficiency of job distribution work can be improved. In other words, work can be performed while referring to parameters that are easily understood by the user, rather than referring to parameters provided for mechanical operation such as the ID of the terminal. There are advantages.

<Modification of the present invention>
The present invention is not limited to the embodiments described above, and includes various modifications. The above embodiment has been described in detail for easy understanding of the present invention, and is not necessarily limited to the one having all the configurations described.

  In the above embodiment, the child terminal can also send a message to the terminals belonging to other groups via the parent terminal. For example, the client terminal 300E can transmit a message to the client terminals 300 belonging to the first U via the client terminal 300B. When the client terminal 300B temporarily stops the operation and the client terminal 300C is acting on its behalf, the message can be similarly transmitted via the 300C instead of the client terminal 300B.

  In the above embodiment, the group hierarchy can be configured in multiple layers. For example, as shown in FIG. 1, the client terminal 300B can manage the client terminals 300C and 300F as child terminals, and the client terminal 300C can manage the client terminal 300D as child terminals. In any case, the parent terminal manages only the configuration of its own child terminal, and the higher-order terminals of the parent terminal are not involved in the configuration of the child terminal. Therefore, for example, the member list 370 held by the client terminal 300A does not hold information about the child terminals of the client terminal 300B. Thereby, the structure of each terminal group will be completed within the said group, and autonomous operability can be improved.

  In the said embodiment, although the profile 355 and the profile 365 are provided as a profile of a terminal device, you may integrate these either (for example in the own terminal data 350).

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized in hardware by designing a part or all of them, for example, with an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function can be stored in a recording device such as a memory, a hard disk, an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

  100: information system department, 200: data center / cloud, 300: client terminal, 310: user interface unit, 320: job execution control unit, 330: group configuration management unit, 340: cooperation unit, 350: own terminal data, 360 : Group data, 370: Member list, 1000: Job management system.

Claims (9)

A job management system for managing jobs distributedly executed by a plurality of terminal devices,
The plurality of terminal devices belong to a group of the terminal devices and execute the job, a group management terminal that distributes the job to the group member terminals, and the group management terminal Including a job distribution terminal that distributes jobs,
The group management terminal holds a member list listing IDs of the group member terminals belonging to the group,
When the group management terminal receives a new entry message describing the message and the ID of the terminal device from the terminal device that newly enters the group, the ID of the terminal device is assigned to the member list. Add
When the group management terminal receives a message to that effect from the terminal device withdrawing from the group and a withdrawal message describing the ID of the terminal device, the group management terminal deletes the ID of the terminal device from the member list,
The group management terminal distributes the job received from the job distribution terminal to the terminal devices listed in the member list ;
The group management terminal holds the ID of the job distribution terminal and the ID of a proxy terminal that is another terminal device that acts as a proxy for the terminal itself.
When the group management terminal shifts to a stop state where the job is not received from the job distribution terminal, the group management terminal transmits a proxy request message to the proxy terminal, and performs a proxy as a response to the proxy request message from the proxy terminal. If a response indicating permission is received, a proxy notification describing the message, the ID of the terminal itself, and the ID of the proxy terminal is transmitted to the job distribution terminal,
When the job distribution terminal receives the proxy notification from the group management terminal, the job distribution terminal distributes the job to the proxy terminal instead of the group management terminal;
When the proxy terminal receives the job from the job distribution terminal, the proxy terminal distributes the job to the group member terminal . When the group management terminal returns to the distribution state for receiving the job from the job distribution terminal after transitioning to the stop state, the group management terminal transmits a return message describing the fact to the job distribution terminal,
The job distribution terminal, when receiving said return message from said group management terminal, the job management according to claim 1, wherein the distributing the job to the group management terminal instead of the agent terminal system. When the group management terminal receives a response indicating that the proxy is permitted as a response to the proxy request message from the proxy terminal, the group management terminal sends a proxy message describing that the proxy terminal will proxy the terminal itself. Send to
The group member terminal receives the proxy message from said group management terminal, the job management system of claim 1, wherein the holding the ID of the agent terminal in association with the ID of the group management terminal. When the group management terminal returns to the distribution state for receiving the job from the job distribution terminal after transitioning to the stop state, the group management terminal transmits a return message describing the fact to the proxy terminal,
The agent terminal, when receiving the return message from said group management terminal, a job management system according to claim 1, wherein the shifts to the state which does not distribute the job to the group member terminal. The group management terminal and the proxy terminal hold state data describing whether or not the group member terminal is operating,
When the proxy terminal receives the return message from the group management terminal, the proxy terminal transmits the status data to the group management terminal, and the group management terminal receives the status data received from the proxy terminal. The job management system according to claim 4 , wherein the status data is overwritten. Before SL terminal holds the user attribute data describing an attribute of the user using the own terminal,
The job distribution terminal distributes the job together with an executor specification message that specifies an attribute of a user who should execute the job,
The group member terminal executes the received job when the attribute described in the user attribute data matches the attribute specified by the executor-specified message, and receives the job when the attribute does not match The job management system according to claim 1, wherein the job management system is not executed. When the group member terminal does not hold the proxy terminal ID, the group member terminal sends a message to the terminal device not belonging to the group via the group management terminal,
4. The job management according to claim 3 , wherein, when the group member terminal holds an ID of the proxy terminal, the group member terminal transmits a message to a terminal device not belonging to the group via the proxy terminal. system. The plurality of terminal devices further belong to a second group of the terminal devices and execute the job, and a second group management terminal that distributes the job to the second group member terminals Including
The member list describes an ID of the second group management terminal as an ID of the group member terminal belonging to the group,
The second group management terminal maintains a second member list listing IDs of the second group member terminals belonging to the second group;
When the second group management terminal receives a message to that effect and a second new entry message describing the ID of the terminal device from the terminal device newly entering the second group, the second group management terminal sets the ID of the terminal device. Adding to the second member list;
When the second group management terminal receives a message to that effect from the terminal device withdrawing from the second group and a second withdrawal message describing the ID of the terminal device, the second group management terminal assigns the ID of the terminal device to the second member. Remove it from the list,
The group management terminal distributes the job received from the job distribution terminal to the second group management terminal according to the description of the member list;
The job management system according to claim 1, wherein the second group management terminal distributes the job received from the group management terminal to the terminal devices listed in the second member list. . The job management system according to claim 1, wherein the job distribution terminal receives the job to be executed by the job management system and distributes the job to the group management terminal.

Images