JPH08102981A - Job distribution system - Google Patents

Abstract

PURPOSE: To distribute jobs and to aid checking for processing and matching performance efficiently by informing a job to a server in a job record form from each terminal equipment, allowing multiple address communication to terminal equipment groups being expert job groups of the job of the kind from the server and requesting the job only to a replied terminal equipment. CONSTITUTION: A job record generating means 11 of a terminal equipment 1 generates a job record 4 whose job content is set on the occurrence of a job and informs the record to a server 2. A job distribution means 3 of the server 2 makes multiple address communication of job request to all expert terminal equipments 1 and sends the record 4 to a terminal equipment 1 returning its reply to request the job. On the other hand, cancellation of job request is informed to other terminal equipments 1 not returning the reply. The terminal equipment 1 accepting the job request displays a content of the record on the screen or corrects or requests processing to an external device and returns the result to the server 2, which makes control and management of jobs. Thus, jobs are distributed to plural expert terminals, in which the jobs are processed efficiently and the matching performance is checked.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a business distribution system for distributing business to specialized terminals and supporting recognition of the status and consistency of the distributed business.

[0002]

2. Description of the Related Art Conventionally, from a point A to a point B like a broadcasting station.
Secure a line from time t1 to time t2,
Video signals are transmitted for live broadcasting. Normally, a program creation department such as a broadcasting station requests the application department to secure a line and NTT secures the line. There are various systems such as micro system, satellite system (SNG), FPU that wirelessly relays from automobiles, ENG that wirelessly relays from a TV camera to an ENG base, etc. Apply and secure these as necessary. There is a need to. Normally, in the application department, for example, an expert with expertise in micro-systems, satellite systems, etc. receives a request from the program-creation department, and applies for the use of the time zone designated for NTT etc. by telephone or FAX. I was trying to secure it.

[0003]

As described above, conventionally, a task is requested to each expert by telephone or FAX, and then the expert actually performs the task by telephone or FAX. Since it was asked to perform the processing, the distribution by business expert and the check of the distributed processing results depend on that expert, and it is impossible to process quickly, accurately and efficiently. There was a problem.

The present invention solves these problems.
From each terminal, make a business record of business and notify the server,
According to the type set in this business record, the server sends a broadcast notification to a group of terminals that specialize in that type of business, notifies the business record only to the responding terminals, and requests the business while responding to the terminals that do not respond. The terminal that receives the business request cancels the broadcast notification, displays the content of the business record on the screen, requests correction or external processing, returns the result to the server, and manages it comprehensively. The purpose is to distribute and process the work efficiently by distributing to other terminals and to support the consistency check.

[0005]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the terminal 1
Performs various kinds of processing. Here, it is configured by the business record creating means 11 or the like, or the notifying means 1
2, the correction means 13 and the application means 14 and the like.

The work record creating means 11 is for creating a work record 4 for setting work contents and requesting processing. The notifying means 12 notifies the server 2 of the result of the processing requested by the business record 4.

The correction means 13 is for correcting the business record 4. The application unit 14 applies (for example, applies to NTT to secure a line) for the processing requested by the business record 4.

The server 2 centrally manages a plurality of terminals 1, and is composed of a work distribution means 3, a work record 4, and the like. The work distribution means 3 receives a work request from the terminal 1 by the work record 4, passes the work record 4 to a specialized terminal, and distributes the work.

The business record 4 is a business content (reservation content)
Is a record for setting.

[0010]

According to the present invention, as shown in FIG. 1, in response to the occurrence of a work, the work record creating means 11 of the terminal 1 creates a work record 4 in which the work content is set and notifies the server 2 of this work record. The business distribution means 3 of the server 2 which has received the notification No. 4 broadcasts the business request to all the specialized terminals 1 and displays the business request on the screen. 4 is sent to request the work, while the other terminal 1 which does not return a response is notified of the cancellation of the work request.

At this time, the business record creating means 11 of the terminal 1 displays a list of candidates for setting the business content in the business record 4 in response to the business occurrence, and sets the selected candidate in the business record 4 to set the server. I notify 2 and request a job.

Further, the terminal 1 requests the server 2 for a list of business contents set in the business record 4, displays the returned list, and supports the schedule recognition of the business contents. .

Further, the consistency of the business content set in the business record 4 notified or returned to the server 2 is checked, an error list is output, and error recognition of the business content is supported.

Further, each terminal is provided with two logical destinations and each server is provided with two logical destinations corresponding to each terminal, and each terminal and the server have a first logical destination of each terminal and a first logical destination of the server.
The business record 4 is transmitted and the resulting response is sent between the server and the terminal using the logical destination of the above, and the server uses the second logical destination of each terminal and the second logical destination of the server from the server. The terminal sends a business request notification and a business request cancellation notification, and each terminal that receives the business request notification displays it in a window, and each terminal that receives the business request cancellation notification clears the window. I'm trying to do.

At this time, in response to the notification of the work request being displayed on the window using the second logical destination, the first logical destination of the terminal is changed to the first logical destination when the request to process the work is generated. It is used to notify the server of the request via the server's first logical destination.

Therefore, each terminal 1 notifies the server 2 of the business as a business record 4, and the server 2 broadcasts the business according to the type set in the business record 4 to a group of terminals 1 specialized in the business of that type. The business record 4 is notified only to the terminal 1 that has notified and responded, and the business request is issued, while the broadcast notification is canceled to the terminal 1 that does not respond, and the terminal 1 that received the business request displays the content of the business record 4 on the screen. Or
By correcting or requesting processing to the outside and returning the result to the server 2 for centralized management, the work is distributed to the terminals 1 of a plurality of specialists for efficient distribution and processing of the work, and matching. It becomes possible to perform a sex check.

[0017]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be sequentially described in detail with reference to FIGS. here,
As the business record 4, a reservation record will be described below as an example.

FIG. 1 shows a block diagram of an embodiment of the present invention.
In FIG. 1, the notification terminal master 5 registers a status (for example, a status such as monitoring) and a notification message type (for example, business A, business B, business C, etc.) in association with a terminal ID (see FIG. 10). (See (a)). By referring to the notification terminal master 5, it becomes clear which terminal is in what state and what kind of work is a specialized terminal. For example, a micro system line,
It is determined whether the terminal is a terminal that applies to, or a terminal that applies a satellite line to KDD or the like.

The notification message management record 6 manages the notification message type (business type). The terminal-specific notification message record 7 manages the display status of each terminal (transmitting, waiting for transmission, selected, etc.).

Next, the operation of the configuration of FIG. 1 will be described in detail according to the order shown in the flowchart of FIG. In FIG. 2, a request occurs in S1. For this reason, for example, a booking (request for acquisition of a line for TV relay) from the start station to the end station occurs in the terminal (service A) in FIG.

In step S2, a reservation record is created. This is the business record creation means 11 of the terminal (business A) in FIG.
Creates a reservation record in which the business content (for example, booking from start station A to end station B) is set.

In step S3, notification processing is performed. This is because the server 2 receiving the notification of the reservation record created in S2
In step S5, a notification destination terminal ID group is obtained by referring to the notification terminal master 5 based on the line type in the reservation record. In step S5, the reservation occurrence is broadcast to the notification destination terminal ID group. In step S6, each terminal is notified. The occurrence of reservation (occurrence of business request) is displayed on the screen.
In response to this, the server 2 receives a response from one terminal in S7. As a process for the responding terminal, S8 to S
Perform 19. On the other hand, as a process for the other terminal which does not respond, the server 2 notifies the other broadcast destination of the cancellation in S21, erases the display of the screen of the other terminal in S22, and ends (END).

In S8, the server 2 transmits the reservation record to the terminal (responding terminal) and requests a job. S9 displays a screen. Displays the business content (reservation content) set in the reservation record.

In S10, an expert operator visually checks the contents of the reservation record displayed in S9. In S11, it is determined whether or not there is a correction. This is to display the contents of the reservation record in S10, and determine whether the operator of the expert who saw the reservation record has a problem in correcting the contents of the displayed reservation record. If so, the reservation record is modified in S12, and the reservation record modified in S13 is returned to the server for storage. On the other hand, if it is determined that the reservation record has not been modified, the process proceeds to S14.

In S14, an application is made (application is made using the NTT mascot). This is the NTT mascot based on the reservation contents (for example, start date and time of use, end date and time of use, line type (micro system, satellite system, dedicated telephone, etc.)) set in the reservation record by the application means 14 of the terminal 1. Request the acquisition of the line using the system.

In S15, the result of applying in S14 is OK,
Alternatively, either NG is determined. If OK, S
Proceed to 17. In the case of NG, retry is made in S16.
In S17, it is determined whether or not there is a correction. If yes, S1
In step 8, the information at the time of application OK is set in the reservation record (the information at the time of application OK is set in the reservation record in order to notify the terminal (work A) 1 of the correction), and the process proceeds to step S19. On the other hand, if there is none, the process proceeds to S19.

In step S19, the reservation state is confirmed and the server is notified. This sets the reservation state in the reservation record to “confirmed” (sets that the reservation has been confirmed) and notifies the server 4.

As a result of the above, a request is generated in the terminal 1, the request (business contents, reservation contents) is set in the reservation record and notified to the server 2, and the server 2 processes the request by referring to the notification terminal master record. When a group of terminals to be operated are found and displayed on the screen which broadcast notification of occurrence of reservation (occurrence of business request) to these terminals and any terminal 1 returns a response indicating that processing is to be performed, this server 2 A reservation record is sent to this terminal, the contents are displayed on the screen, the operator of the specialist visually checks, and if necessary, the reservation record is corrected and the reservation is applied to NTT or the like (processing of business), OK
If the line reservation has been obtained, the reservation state in the reservation record is notified to the server 2 as “confirmed”. On the other hand, when one of the terminals 1 returns a response to the server 2 to perform the processing, the server 2 sends a cancellation notice to the other terminals.

FIG. 3 shows a flowchart for creating reservation record candidates according to the present invention. This is an example of creating the reservation record in S2 of FIG. In FIG. 3, a request is input in S31. For example, booking from the start station to the end station is performed.
That is, an operator (for example, a news program producer) inputs a request to acquire a line by designating from the start station to the end station for live TV broadcasting.

In step S32, line type route candidates are displayed. This displays the line type route candidates from the start station to the end station input in S31. S33 makes a selection. This is because the operator selects one of the line type route candidates displayed in S32.

In step S34, the data is transferred to the server. This is S
The line type route selected in 33 is set in the already-described reservation record, transferred to the server 2, and a processing request (reservation application request) is made.

As described above, from the terminal 1, the operator sets the reservation contents in the reservation record each time by relying on his / her specialized knowledge, and if the start station and the end station are designated by S31 to S34, the line type route Candidates are displayed, so when selected, they are automatically set in the reservation record, transferred to the server 2, and reservation request (business processing request)
You can now do.

FIG. 4 shows an example of the reservation record of the present invention.
The reservation record sets the content of the terminal 1 requesting a reservation (business) to the server 2, and sets the following content shown in the figure.

[0034] FIG. 5 shows a flow chart of the schedule confirmation of the present invention.

In FIG. 5, S41 requests a schedule list for each program. This is because the terminal 1 uses S1 in FIG.
In S2, the reservation record is notified to the server 2 to make a reservation request, and in order to know the reservation state, for example, a request for a program-specific schedule list is made to the server 2.

In S42, the server 2 receiving the request in S41
Searches by the program name code. This is because the "program name code" is set in the reservation record of FIG. 4 described above, and a search is performed with the program name code to retrieve all matching reservation records.

A step S43 displays a list. This is S4
In step 2, a list of reservation records with the same program name code is displayed on the terminal. In S44, a selection is made from the list displayed in S43.

In step S45, details of the reservation record selected in step S44 are displayed. As described above, it becomes possible to easily confirm the schedule of the reservation for which the request is set in the reservation record and the reservation request (work request) is made to the server 2.

FIG. 6 shows a flow chart of the consistency check of the present invention. In FIG. 6, in S51, a consistency check is performed. This is because, for example, the terminal 1 uses S1, S2 in FIG.
A reservation record is created by the user and a reservation request (business request) is made to the server 2, and the consistency of the reservation is checked, for example, two lines are reserved for a line from the start point A to the relay point B and from the relay point B to the end point C Make a reservation record and server 2
If the line is acquired and only one of these two reservation records can be acquired and the other one cannot be acquired, the consistency check determines that there is no consistency and an error occurs.

In step S52, the error list is output. S
53 determines whether there is an error. If YES, S
At 54, the administrator corrects (route change, etc.), recreates a reservation record, and requests the server 2 for reservation. On the other hand, in the case of none, it is found that the reservation was normally applied and the line was acquired.

As described above, the terminal 1 creates the reservation record, requests the server 2 for the reservation (business request), checks the consistency if necessary, outputs the error list, and if there is an error, makes the reservation. The contents of the record are displayed, the reservation record in which the route change or the like is corrected is recreated, and the reservation request (business request) is made to the server 2. This allows
It is possible to check the consistency from time to time and improve certainty.

FIG. 7 shows a reservation record correction flowchart of the present invention. This shows the details of the correction in S12 of FIG. In FIG. 7, S61 displays a list of candidate line routes.

In S62, the route is selected. These S6
In 1, S62, the correction unit 13 of the terminal 1 displays a list of circuit route candidates, and an operator who is an expert selects a route that is the most appropriate from the candidate list.

In S63, the application is made. For the route selected from the candidate list in S62, the system called NTT mascot is used in S65 to apply for a line acquisition request for the selected route. For this application,
If you can get the route, it will be OK, otherwise you will get NG.

In S64, it is determined whether it is OK or NG. This is an application for acquisition of the selected route using the system called S65 NTT mascot, and the result is OK.
It is determined whether (the line has been acquired) or NG (the line has not been acquired). In the case of OK, since the line has been acquired, the process ends. In the case of NG, the next candidate is selected and repeated in S62.

FIG. 8 shows an explanatory view of another embodiment of the present invention. In FIG. 8, S81 stores the business data input from the terminal. This is done by setting the business data input from the terminal in the reservation record, and updating the "status" of the notification terminal master in the notification status management information file to "monitor".

In step S82, a notification request is made. S83 is S8
In response to the notification request of No. 2, the notification message transmission control task refers to the notification state management information file and notifies that there are reservations to the corresponding terminals in S84.

In S86, S85 corresponds to the notification in S84.
When there is a response from any of the terminals, the terminal communication task updates the notification state management information file and
A deletion request is made at 87.

In S88, the notification message transmission control task, which receives the deletion request in S87, refers to the notification state management information file, and S8 is sent to the other terminals notified in S84.
The deletion is notified at 9. The terminal that has received this deletion notification deletes the notification message from the screen.

In S91, the terminal refers to the reservation record,
Modify or apply. In S92, the reservation record is updated with the result of the correction or application (application to NTT for line reservation) in S91.

FIG. 9 shows an example of a business message for communication of the present invention. This shows an example of a telegram for exchanging data between the terminal and the server and between the server and the terminal. Here, the following items shown in the figure are set in the message.

-Communication header-Message type: Notification message delivery request message Notification message selection message Terminal unit notification request message Business data creation notification message transmission request-Response type: Display, delete, select, select OK, select NG-Notify message Content: Notification message identifier + Message content Notification message identifier: Notification message identification + Management number FIG. 10 shows an example of a notification status monitoring file for a notification message of the present invention.

FIG. 10A shows a notification terminal master. The notification terminal master 5 sets the following items shown in the figure. -Terminal ID: -Status: -Notification message type: There can be multiple notification message types. The business content performed by the terminal is registered according to this notification message type.

FIG. 10B shows a relational type. This shows an example in which the notification terminal master 5 of FIG. 10A is set in a relational database. Here, for example, the respective settings are made as shown below.

[0055] FIG. 10C shows a network type. This shows an example in which the notification terminal master 5 of FIG. 10A is set in the network type database. Here, for example, the setting is made as illustrated.

FIG. 11 shows an example of the notification message storage file of the present invention. FIG. 11A shows a notification message management record. This sets the following items as shown. This notification message management record is for numbering the management number of the notification message identifier.

Notification message type: Latest management number: FIG. 11B shows a notification message record. This sets the following items as shown.

Notification message identifier: Notification status: transmitting, erasing Notification content FIG. 11C shows a notification message record for each terminal. This sets the following items as shown.

Notification message identifier: Terminal ID: Display status: transmitting, waiting for transmission, selected FIG. 12 shows the configuration of another embodiment of the present invention. this is,
Each terminal is provided with a logical destination LU1 and LU2, and the host (server) 21 is provided with a logical destination LU corresponding to each terminal.
1 and LU2 are provided respectively, and both LU1 are used to send a reservation message (reservation record in the message format) between both APLs and receive its response, and both LU2 are used for host Between the message task and the subwindow of the terminal, the subwindow displays the fact that there is a reserved record, and the fact that the reserved record is deleted erases the display to that effect from the subwindow. . This will be described in detail below.

In FIG. 12, terminals A, B, C and D are
Various business processes are performed, and logical destinations LU1 and L
U2, each of which has two,
Sub-window, communication QUE, LUI communication, and LU
It is composed of two communications.

The business APL (business application) of the terminal is for performing various business. The sub-window (sub-window task) is used for various displays. Here, the fact that there is a reservation record notified via the LU2 from the message task of the host is displayed or a keyboard (not shown) is used. Read the input indicating that the reservation record has been accepted, display the read acceptance, and write the read acceptance (acceptance notification) to the communication QUE and send it to the LU1 communication of the host via the LU1 communication. It is something to let you know.

The communication QUE is for enqueuing (connecting) a message transmitted to the host via the LU1 communication. The LU1 communication of the terminal uses the logical destination LU1 of the terminal to mutually transmit and receive data to and from the LU1 communication of the host (for example, receiving a reserved message and transmitting a message storing the result).

LU2 communication of the terminal is the logical destination LU of the terminal.
2 is used to send and receive data to and from the LU2 communication of the host. The host (server) 21 centrally controls a plurality of terminals, and is composed of business APL, message task, LU1 communication, LU2 communication, and the like.

The business APL (business application) of the host performs various business. Here, the fact that there is a reservation record is notified to the LU2 communication of the terminal via a message task, LU2 communication, or here. Although it is not explained in the above, the reservation record is sent to the terminal that responded to the reservation record acceptance notification
1 Message task to delete the fact that the reservation record exists to the terminal that does not respond to the reception notification
For example, notification is made via U2 communication.

The message task is for notifying the terminal of various messages (messages such as the presence of reserved records) via the LU2 communication, and is composed of message edit, hold release, message storage type file and the like. is there.

In message editing, a message to be notified to the terminal via LU2 communication (a message such as having a reservation record) is edited, stored in a message storage type file, and transmitted to the terminal 2 as a message via LU2 communication. It is a thing. The sub-window of the terminal which received this message displays the fact.

Releasing the hold causes the LU2 communication to retrieve the message message from the message storage type file and send it to the terminal. The subwindow of the terminal that receives this message displays or deletes the message.

The message storage file stores messages. The LU1 communication of the host uses the logical destination LU1 of the host to exchange data with the LU1 communication of the terminal (for example, transmission of a reservation message, reception of a message storing the result, reception of a reservation record acceptance notification). Etc.).

The LU2 communication of the host uses the logical destination LU2 of the host to transmit / receive data to / from the LU2 communication of the terminal. Next, according to the order shown in FIG.
The procedure for displaying the sub-window in the configuration of FIG. 12 will be described in detail.

FIG. 13 shows an overall flowchart of the subwindow display of the present invention. Here, a case where terminal A transmits a reservation message to the host and terminals B, C, and D display a reservation message (a request for reservation) is displayed on the sub-window will be described as an example.

In FIG. 13, S1 is the work A of the terminal A.
PL (a) writes the reservation message in the communication QUE. S2
Is the LU1 communication (c) of the terminal A from the communication QUE to S1.
Read the reserved telegram written in.

S3 is transmitted to LU1 communication (q) of the host. In S4, in response to the transmission in S3, the host waits for a message from LU1 communication.

In S5, the LU1 communication (q) on the host side receives the reservation message transmitted in S3. S6 is S5
LU1 communication (q) receives the reservation message received by
Send to (y).

In S7, the business APL (y) receives the reservation message transmitted in S6. In S8, the notification type is transmitted to the message task (z). This sends to the message task (z) the notification type (for example, any of the circuit types micro upstream, downstream, SNG, etc., see FIG. 4) set in the reservation message received by the business APL in S7.

In S9, the message task (z) receives the notification type transmitted in S8. In S10, the logical destination LU of the terminal that processes the notification type received in S9 is selected. Here, for example, the logical destination LU (for example, the logical destination of the terminals B, C, D) of all the corresponding terminals is selected by referring to the notification terminal master 5 of FIG.

In S11, the message task (z) is S1.
Write the message to the logical destination selected with 0 (the fact that there is a reserved telegram) to the message storage type file. S12
The message task (z) notifies the logical destination (for example, the logical destination of the terminals B, C, and D) to the hold release, and the LU2 communication (t) (v) on the host side of the logical destination notified of the hold release is notified. ) And (x), the transmission hold release message is transmitted.

In S13, the LU2 communications (t), (v), and (x) receive the transmission hold release message transmitted in S12. In S14, the LU2 communications (t), (v), and (x) received in S13 read the message from the message storage type file, respectively.

In S15, the message read in S14 is transferred to LU2 communication (t), (v) and (x) to LU2 communication (h), (l) and (p) of terminals B, C and D which are logical destinations. Send.

In step S16, the LU2 communication (h), (l), of the terminals B, C, D of the message transmitted in step S15 is transmitted.
(P) receives each. In S17, LU2 communication (h), (l), and (p) of the message received in S16 is performed by the sub-windows (f), (j), and (n) of the terminals B, C, and D.
To send to each.

In S18, the sub-windows (f), (j) and (n) receive the message transmitted in S17. In S19, each sub-window of the type of message received in S18 is displayed (here, the fact that the reservation message is accepted is displayed in each sub-window).

Further, 20 in FIG. 13 is a business AP on the host side which has sent the notification type to the message task (z) in S8.
L (y) sends screen display message to host side LU1 communication (q)
Send to.

In S21, the LU1 communication (q) receives the screen display message transmitted in S20. S22 is S2
LU1 communication (q) receives the screen display message received in step 1 from terminal A.
To LU1 transmission (c) (return).

In S23, the LU1 communication (c) on the terminal side receives the screen display message transmitted in S22. S24
Transmits the screen display message received in S23 to LU1 communication (c)
Transmits to the work APL (a).

In S25, in response to the transmission in S24, the LU1 communication (c) waits for the data of the communication QUE. In step S26, the business APL (a) receives the screen display message transmitted in step S24.

In step S27, the screen display message received in step S26 is displayed on the screen. In step S28, a series of processes is completed in response to the screen display in step S27.
(A) waits for input.

From the above, the work APL (a) of the terminal A
In response to writing the reservation message in the communication QUE and requesting processing, this reservation message is transmitted via the LU1 communication on the terminal side-the LU1 communication on the host side, and the work APL (y) on the host side.
, The business APL (y) looks at the type notified by the reservation message, extracts all the logical destinations of the terminal that processes the type of business, and instructs the message task (z) to send the logical destination of the terminal. Message (Reservation message received)
Message is displayed on the sub-window via LU2 communication on the host side-LU2 communication on the terminal side. On the other hand, the job APL (y) of the host sends a response to the received message, LU1 communication on the host side-the screen display message (corresponding to a response message) to the terminal job A via LU1 communication of the terminal.
PL (a) is notified and the screen is displayed. By these,
Even if half-duplex communication is performed between the terminal and the host, two logical destinations LU1 and LU2 are provided, LU1 is used for communication between business APLs, and another LU2 is used as a sub-window indicating that message reception is available. By using it for displaying, it became possible to communicate with each other independently and asynchronously, and to efficiently perform business processing.

FIG. 14 shows an overall flow chart of the sub-window deletion of the present invention. Here, an example will be described in which the reservation acceptance is input to the terminal C and the sub-windows of the terminals B and D are deleted.

In FIG. 14, in S31, the sub window (j) of the terminal C reads the input of the reception from the keyboard (not shown). In S32, the reception notification message is written in the communication QUE of the terminal C in response to the input of the reception read in S31.

In S33, the LU1 communication (k) of the terminal C reads the acceptance notification message written in the communication QUE in S32. In S34, the reception notification message read in S33 is transmitted to the LU1 communication (u) on the host side.

In S35, the LU1 communication (k), which has transmitted the reception notification message in S34, waits for a message from the host. S
In 36, the LU1 communication (u) on the host side receives the reception notification message transmitted in S34.

In S37, the LU1 communication (u) transmits the acceptance notification message received in S36 to the work APL (y). S
38 receives the reception notification message sent in S37 from the job A
PL (y) receives.

In S39, the notification type is transmitted to the message task (z) corresponding to the reception notification message received in S38. In S40, the message task (z) receives the notification type transmitted in S39.

In S41, the logical destination LU is selected based on the notification type received in S40. In S42, the message is written in the message storage type file. In S43, the message task (z) notifies the logical destination (for example, the logical destination of the terminals B and D) to the hold release, and the LU2 communication (t), (x) on the host side of the logical destination notified of the hold release. Send a transmission hold release message to.

In S44, the LU2 communications (t) and (x) respectively receive the transmission hold release message transmitted in S43. In S45, LU2 communication (t) received in S44,
(X) reads each message from the message storage type file.

In S46, the message read in S45 is transmitted to LU2 communication (t), LUx communication (h) and LU2 communication (h) of terminals B and D whose logical destinations are (x). S47 is S4
The LU2 communication (h) and (p) of the terminals B and D respectively receive the message transmitted at 6.

In S48, the LU2 communication (h) and (p) transmit the message received in S47 to the subwindows (f) and (n) of the terminals B and D, respectively. S49 is S4
The sub-windows (f) and (n) receive the message transmitted in 8.

In S50, the display of each subwindow received in S49 is erased (here, the display of the subwindow indicating that the reservation message is accepted is erased). Also,
In 51 of FIG. 14, the job APL (y) on the host side, which has transmitted the notification type to the message task (z) in S39, transmits a wait release message to the LU1 communication (u) on the host side.

In S52, the LU1 communication (u) receives the wait release message transmitted in S51. S53 is S5
LU1 communication (u) receives the wait release message received in 2 from terminal C
Is sent (replies) to LU1 transmission (k).

In S54, the LU1 communication (k) on the terminal side receives the wait release message transmitted in S53. S55
Ends a series of processes by the wait release message received in S54, and enters the data wait state of the communication QUE.

As described above, in response to the acceptance input from the sub-window of the terminal C, the job APL (y) of the host side is notified via the LU1 communication of the terminal C-LU1 communication of the host side, and the job APL (y). Sees the type notified by the reception notification message, instructs the message task (z) to take out all the logical destinations of other terminals of the type, and sends a message (erasing the subwindow display) to the logical destination of the terminal,
LU2 communication on the host side-Notify the subwindow via the LU2 communication on the terminal side to delete it. On the other hand, the job APL (y) of the host notifies the LU1 communication of the terminal C of a response to the received message by sending a wait release message (corresponding to a response message) to the LU1 communication of the host side-LU1 communication of the terminal, A series of message communication is completed, and a waiting state is entered.
As a result, even if half-duplex communication is performed between the terminal C and the host, two logical destinations LU1 and LU2 are provided.
Is used for communication with the host business APL of the reception notification message, and by using another LU2 to erase the subwindow, both can be communicated independently and asynchronously, and efficient business processing can be performed. Became.

[0101]

As described above, according to the present invention,
Each terminal 1 notifies the server 2 of a job as a job record, and the server 2 broadcasts a notification to the group of terminals 1 specialized in the job of that type according to the type set in this job record, and responds to the terminal 1 To the terminal 1 that does not respond, the terminal 1 that received the job request displays the contents of the job record on the screen, performs the process, Since the configuration is adopted in which the result is returned to the server 2 as a business record, the business can be distributed to the terminals 1 of a plurality of specialists and the business can be efficiently distributed and processed, and the consistency check can be performed. I can help. Further, by providing each terminal and server with two logical destinations LU1 and LU2 corresponding to each terminal, even in the case of half-duplex communication, the request notification to the plurality of terminals of the business record and the deletion of the request notification to the terminal, and the business It is possible to efficiently perform business processing by efficiently transmitting records and receiving responses to them.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a flowchart explaining the operation of the present invention.

FIG. 3 is a flowchart of creating reservation record candidates of the present invention.

FIG. 4 is an example of a reservation record of the present invention.

FIG. 5 is a flowchart of schedule confirmation according to the present invention.

FIG. 6 is a flowchart of the consistency check of the present invention.

FIG. 7 is a flowchart for modifying a reservation record according to the present invention.

FIG. 8 is an explanatory view of another embodiment of the present invention.

FIG. 9 is an example of a business message for communication of the present invention.

FIG. 10 is an example of a notification status monitoring file for notification messages of the present invention.

FIG. 11 is an example of a notification message storage file of the present invention.

FIG. 12 is a configuration diagram of another embodiment of the present invention.

FIG. 13 is an overall flowchart of subwindow display according to the present invention.

FIG. 14 is an overall flowchart of subwindow erasing according to the present invention.

[Explanation of symbols]

 1: Terminal 11: Business record creating means 12: Notification means 13: Correction means 14: Application means 2: Server 3: Business distribution means 4: Business record 5: Notification terminal master 6: Notification message management record 7: Notification message by terminal record

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Takaya Ohara 1-6-4 Osaki, Shinagawa-ku, Tokyo Inside Fujitsu Social Science Laboratory, Inc. (72) In-house Yoshinari Takahashi 1-6 Osaki, Shinagawa-ku, Tokyo No. 4 Stock Company, Fujitsu Social Science Laboratory (72) Inventor, Shohei Takahashi, 2-1-1 Mita, Meguro-ku, Tokyo System Plaza, Inc. (72) Inventor, Fumio Tashiro 1-6, Osaki, Shinagawa-ku, Tokyo No. Stock Company, Fujitsu Social Science Laboratory

Claims (8)

[Claims] 1. A terminal for creating and notifying a business record (4) in which the content of the business is set in response to the occurrence of a business is provided, and the business record (4) receives the notification of the business record (4). The business request is broadcast to the terminal group that specializes in the business set to, the business request is displayed on the screen, the business record (4) is sent to the terminal that returned the response, and the response is returned. A server (2) for notifying the cancellation of a business request is provided to another terminal that does not exist, and the terminal that receives the business record (4) displays the business content set in the business record (4), and the processing result Is set in the business record (4) or the business record (4) is corrected and returned to the server (2). 2. Corresponding to the occurrence of the business, a list of candidates for setting the business content in the business record (4) is displayed, the selected candidate is set in the business record (4), and the server (2) is set. The business distribution system according to claim 1, wherein the business distribution system is notified. 3. A terminal requests a list of business contents set in a business record (4) from the server (2), displays the returned list, and supports schedule recognition of the business contents. The business distribution system according to claim 1 or 2, characterized in that. 4. Supporting the error recognition of business contents by checking the consistency of the business contents set in the business record (4) notified or returned to the server (2) and outputting an error list. The business distribution system according to any one of claims 1 to 3. 5. The business distribution system according to claim 1, wherein the business is to secure a line for each line type. 6. Each of the terminals is provided with two logical destinations, and the server is provided with two logical destinations corresponding to the respective terminals, and each terminal and the server are provided with a first logical destination of each terminal and a first logical destination of the server. The business record (4) is transmitted between the server and the terminal by using the destination, and the resulting response is sent, and the server uses the second logical destination of each terminal and the second logical destination of the server. From the terminal to the above-mentioned business request notification and the above-mentioned business request cancellation notification, each terminal that received the business request notification displays in a window, and each terminal that receives the business request cancellation notification 6. The window is erased, and the window is erased.
Business distribution system described. 7. In response to the fact that the notification of the work request is displayed on the window using the second logical destination in claim 6, when a request to perform the work is issued, the terminal A business distribution system characterized in that a request is sent to a server via a first logical destination of the server using the first logical destination. 8. Each of the terminals is provided with two logical destinations and the server is provided with two logical destinations corresponding to each terminal, each terminal is provided with a business application, a sub-window task and a queue, and the server is provided with a business application. The terminal and the server use the first logical destination of each terminal and the first logical destination of the server to transmit the business record (4) between the business application of the server and the business application of each terminal, and The result is responded, and the business application of the server notifies the sub window task of each terminal of the business request and the cancellation of the business request using the second logical destination of each terminal and the second logical destination of the server. The subwindow task of each terminal that received the notification of the work request displays in the window and the subwindow task of each terminal that received the notification of cancellation of the work request. Deletes the window and stores the transmission data in the queue of the terminal when the transmission data from the business application on the terminal side to the business application on the server occurs, or processes the business in response to the window display. A business distribution system characterized in that the request is stored when a request to perform is generated, and the terminal transmits the contents of the queue from the first logical destination to the business application of the server.