JPH11232220A - Method for distributing event data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the delay of message processing successively generated in real time without changing a transmitting side communication program even when the contents of operation on a receiving side are changed or added by adding event ID to the event data of various events generated in a facility, informing of all active programs of the reception of event data and entrusting the processing of the data to those active programs. SOLUTION: Upon receiving event data from a front accounting machine, an information processor 2 adds event ID to the received event data and stores the event data and the added event ID together in an event data file 208 through a DB management AP 205. An event code and the event ID included in the event data are set up in respective input buffers corresponding to all operation programs indicated in an active program list(AFL) stored similarly to the preset data of the event ID. Then all operation programs are informed of the generation of the event to entrust the processing of the event to those application programs.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event management system for managing sales information relating to rooms of a facility for lodging and resting, and more particularly to a plurality of events for processing various events occurring in a facility for lodging and resting. The present invention relates to an event data distribution method for an event management system device having a business program.

[0002]

2. Description of the Related Art Conventionally, various events that occur in facilities for lodging and resting are operated by a communication program that has acquired such events by means of communication or the like, by dividing event data included in the event data. A business program that requires data processing is determined from a plurality of business programs in the middle, and the event is delivered only to the business program that is deemed necessary.

[0003] For example, Japanese Patent Application Laid-Open No. 5-197684 (I
As seen in PC G06F 15/00 310), the business program adds, as a parameter, distribution information specifying the processing subject business program of the message at the time, and uses the distribution information as the parameter in the message receiving program. There is a method in which the message is specified and distributed to the processing subject business program. For example, see Japanese Patent Application Laid-Open
No. 73432 (IPC G06F 15/00 3)
As can be seen in 10), a business program for processing the received data is determined and the received data is stored in the business program in order to improve the performance and speed of the processing of the received data in the online distributed system. Performs the online control process to be delivered, and collects one or more pieces of received data to be processed by the same business program from the received data in the processing waiting state, and collects the data into the business program by one processing request.
In such a case, the processing time is reduced in direct proportion to the number of received data. In such a conventional example, the business program on the receiving side when transmitting a message is designated by a parameter to simplify the determination and reduce the time required for sorting the message on the receiving side,
It is also intended to reduce the processing time by determining whether received data generated on the receiving side is processed by the same business program and reducing the number of processing requests by collecting the received data. Therefore, in the former conventional example, the dispatching method is a distribution method realized only by familiarizing the business program on the receiving side with the message sending side, and the parameter on the transmitting side is changed every time the business content on the receiving side is changed or added. In the latter conventional example, there is a need to change the received data, and the processing of the received data is burdened by determining whether the received data is processed by the same business program. Delays can occur.

[0004]

However, the prior art as described above has the following problems.
In the former case, it is necessary for the sending side of the message to be familiar with the business program of the receiving side, and it is necessary to change the parameter of the transmitting side every time the business contents of the receiving side are changed or added. If the parameters are neglected, the process related to the change or addition of the business content on the receiving side will not operate correctly, and the program change or addition of the business content on the receiving side and the change of the parameters on the sending side will cause multiple program changes. Is always needed. Also, in the latter case, in order to determine whether the received data is processed by the same business program on the sending side that processes the received data, the processing of messages that occur one after another in real time must be interrupted by a certain number of processes and summarized. However, it is not possible to collectively transfer one or more pieces of received data processed by the same business program to the business program by a single processing request. Not only does the load of determining whether the received data is the data to be processed occur, but it also causes a delay in the processing of electronic messages that occur one after another in real time. The present invention has been made in order to solve the above-described problem, and even if the content of work on the receiving side is changed or added, the parameter of the transmitting side does not change, and the business program of the receiving side is changed. A facility management system that reduces the delay of electronic message processing that occurs one after another in real time without the load of determining whether the received data is processed by the same business program on the transmitting side that processes received data. It is an object of the present invention to provide a method of sorting event data.

[0005]

According to the present invention, there is provided an event data distribution method, comprising: an event data file for recording event data relating to various events together with an event code indicating the type of the event data; Event management system comprising: a group of business programs; an active program list showing a list of executable programs among the plurality of business programs; and a communication program for transmitting and receiving information related to the event to an external computer. In the apparatus, the communication program includes:
The event data received together with the event code includes an event ID as unique index information in the event code.
And records the event code and the event ID in the event data to each input buffer corresponding to all the business programs indicated in the active program list. By setting, the occurrence of the event is notified to all business programs indicated in the active program list, and the processing of the event data is entrusted to each business program, and the input buffer When the business program in which the event code and the event ID are set determines that the event is not an event to be processed by the event code, the business program sets the event code and the event ID in the input buffer. Is deleted, and if it is determined that the event is an event to be processed by the And reading the contents of the event data file using the event ID and the event ID as keys, and performing the necessary business processing, and deleting the event code and the event ID in the input buffer. Further, the communication program, if the event code and the event ID set in the input buffer of each business program have not been erased within a predetermined time, the communication program The business program is deleted.

[0006]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the drawings showing the embodiments. "Data Base" is abbreviated as "DB" to simplify the description,
"Software" is abbreviated as "SW",
“A” for “Application Program”
"P". In addition, information relating to an event to be computer-processed as information among events that have occurred in a room that is a facility provided for lodging and rest is hereinafter referred to as “event data”.

FIG. 1 is a schematic diagram showing a block configuration of a front accounting machine according to an embodiment of the event management system apparatus of the present invention. FIG. 2 is a block diagram of an information processing apparatus according to an embodiment of the event management system apparatus of the present invention. It is a schematic diagram which shows a block structure. FIG. 1 shows a front checkout machine and its peripheral devices installed at the front of a facility, and a plurality of sets of these front checkout machines and their peripheral devices may be installed. Fig. 2 shows the front accounting machine and RS232C in Fig. 1.
And the like and the peripheral devices connected to the facility by communication means. The front checkout machine 1 shown in FIG.
It has an information storage unit 103 for storing information such as a current use state, a past use state, and a future reservation of a room of a facility used for lodging and rest. And the information storage unit 103
Is a room information file 1031 having information about each room, such as its class, usage fee, and current usage status, and the check-in and check-out times of customers who use each room, and the information of the refrigerator installed in each room. Usage status file 1 containing usage status of information related to sales to customers
032 and the sales having room information relating to the use of each room and the sales of each product in the refrigerator, which are accumulated information such as a daily total as a daily closing process and a monthly total as a monthly closing process. Information file 1033. The front accounting machine 1 includes terminals 104, 104,..., Such as telephones, refrigerators, or currency exchange machines, installed in each room of the facility by a communication network. . . , 104.
The information processing apparatus 2 shown in FIG.
An information input unit 201 that provides various instructions related to business support related to work and the like and management support such as sales totalization and room occupancy.
Information display unit 202 for visually displaying various information
, Communication program 203, message transmitting / receiving component 20
4. DB management AP 205, various AP groups 206 as various business program groups, DB access components 2
07 and various event data files 208, 208,. . . , 208 and the index information file 20 of these event data files 208
81, and various data files such as various AP group data files 209 for various AP groups 206. Each AP group 206 has an input buffer group 2061 of each AP in each AP. The communication program 203 is a program for realizing transmission and reception of various event data with the front accounting machine 1, and has an active program list 2031 as a list of business programs that deliver these various event data. The communication program 203 buffers the data sent from the front accounting machine 1 and records the buffered data in an DB called an event data file 208 by passing the data received to a message transmitting / receiving component described later as event data. I do. The hierarchical structure of the communication program 203 is such that the network layer and the transport layer are omitted from the OSI model seven layer, and the physical layer (RS232C), the data link layer, the session layer including the buffering function of the requested data, the file transfer, and the AP ( OSI model presentation layer and application
(Corresponding to layers). DB access component 2
07 is an event data file 208 for storing the various event data and a data file 2 for various AP groups.
For DB files such as 09 (hereinafter referred to as DBF),
A SW component that performs an operation on the DBF by using a DB access object provided by a general DB engine for constructing the DBF. The DB access component 207 is a DB that does not depend on the DB engine at all.
An SW component that provides an access program. The DB access component 207 includes a DB access general-purpose SW component that can be used in a plurality of APs that the information processing apparatus 2 may have, and a DB access specialization program specialized for an AP unique to various AP groups 206 and the like. It is composed of The DB access general-purpose SW component has a DB connection function (connection / disconnection function), a record operation function (record addition / update / deletion function), a search execution to the DBF, and a search result management function. . The DB access specialization program is composed of the following four SW components. The first is a system management data access SW component for obtaining system management information such as addition, update, and deletion of system management data and a desired search result. Second, there is a system history management data access SW component for adding, updating, and deleting system history management data and obtaining a search result. Third, add, update, and delete event-related data.
And an event data access SW component for obtaining a search result. Fourth, there is a constant data access SW component for adding, updating, and deleting constant data unique to the system and obtaining a search result. Message transmission / reception component 204
Are SW components, which mediate transmission and reception of information between each AP of the information processing apparatus 2. Communication program 203
Receives the event data from the front accounting machine 1, the reception of the event data is transmitted to all the APs of the information processing device 2 through the message transmitting / receiving component 204. The message transmission / reception component 204 is a “data exchange so-called“ DATA EXCHANGE ”” (hereinafter referred to as “DATA EXCHANGE”) between APs in the information processing apparatus 2.
ANGE "is abbreviated as DX) General DX for building
A program for transmitting and receiving messages between the APs is provided by using a DX object which is a SW provided by an engine. For example, when a certain AP transmits a message to another AP, it adds transmission information called a socket corresponding to each AP and delivers it to the message transmitting / receiving component 204. Deliver the message. Each AP determines from the content of the added socket whether the delivered message should be processed by itself. Then, when it is determined that the message should be processed, a message indicating that the message has been received is delivered to the message transmitting / receiving component 204.
The source AP confirms the reception status at the target AP by using the reply message. Front accounting machine 1
These event data are transmitted from the front accounting machine 1 to the information processing device 2 via a communication line (for example, RS232C) to notify the occurrence of the event. In the information processing apparatus 2, the DB management AP 205 and various AP groups 206 in the information processing apparatus 2 are operated by the communication program 203.
The event data is passed through the message transmission / reception component 204. DB management AP 205 and various AP groups 206
Checks the delivered event data and performs necessary processing only on the event data determined to need to be processed by itself. That is, the communication program 203 does not determine whether or not each AP in the information processing device 2 needs to process the event data, and unconditionally sends all generated event data to each AP in the information processing device 2. And hand it over. For example, the DB management AP 205 notified of the occurrence of the event data via the message transmitting / receiving component 204 determines that the event data is event data to be processed by itself, and records the event data in the event data file 208 via the DB access component 207. Event data is classified into various data formats according to the data format of each event (for example, entry, cleaning / work,
The data format of the event corresponding to each task occurring in the facility such as settlement, discount, etc.) is always set at the head of the event data, and the event code indicating the content of the event data is set. It is determined whether or not it is necessary to perform processing based on the event code. Furthermore, in the data format of the event data, the date and time when the event occurred in the front accounting machine 1 is always set. However, depending on the type of the data format, the date and time when the event entered the room or the settlement of the room is performed. It is also treated as the date and time or the date and time when the room cleaning ends. FIG. 3 is a schematic diagram showing a recording format of the index information file 2081, and FIG. 4 is a schematic diagram showing a recording format of the recording start date and time and the recording end date and time recorded in each event data file 208. In order to manage each event data file 208, the recording start date and time, the recording end date and time, and the name of the event data file are recorded in the index information file 2081 for each event data file. Information relating to division of the event data file 208 itself is managed by the recording start date and time and the recording end date and time of each event data file 208 recorded in the index information file 2081 and the name of the event data file. in use.

FIG. 5 shows a control procedure of a method for distributing the event data received from the front accounting machine 1 to each business program in the event management system apparatus of the present embodiment configured as described above. This will be described based on a flowchart. STEP01: In this STEP01, it waits for event data to be transmitted from the front accounting machine 1. This is a so-called standby STEP, and when event data is received, the ST
Proceed to EP02. STEP02; In STEP02, the event ID of the received event data is added. The event ID is assigned to each event code indicating the type of event set in the event data. For example, a serial number or the like for each event code is stored as preset data in a hard disk, RAM, or the like of the information processing apparatus 2. The event ID corresponding to the event code is read from the preset data when the event data is received, updated, and stored again. Then, the updated event ID is added to the event data. STEP03; In this STEP03, the added event I
The event data is recorded together with D in the event data file 208 via the DB management AP. The event data file 208 is divided into a plurality of files and stored in the information processing apparatus 2 of the present invention. By dividing and storing the divided event data files 2 in the index information file 2081, the file capacity is reduced in small units.
The index 08 is managed to facilitate recovery from a failure such as a DB down, and to reduce the time required to read each record in the DB. STEP04; In this STEP04, an active program list (Active ProgramList) stored in the same manner as the preset data in STEP02 is stored.
t; hereinafter referred to as APL, the format of which is shown in FIG. 6). In preparation for the LOOP processing shown in STEP05 to STEP10 below, the LOOP counter for APL is cleared to 1 and the number of effective APs described below. Get it. The APL is an AP name 60 relating to a business program (AP) executable in the information processing apparatus 2.
1, a list having information such as an input buffer address 602 of the AP, an active flag 603 as a flag indicating whether the AP is in an executable standby state (a so-called active state), etc. for each AP. . The APL is reset when the information processing apparatus 2 is started up, and the number of active APs in the APL is changed to the effective AP.
The number is set as 600. STEP05: In this STEP05, the LOOP counter is compared with the number of valid APs 600, and if the LOOP counter is larger than the number of valid APs 600, all APs are
Since the notification of the reception of the event data to has been completed,
The process returns to STEP 01 and waits for the next event data to be transmitted from the front accounting machine 1 again. If the LOOP counter is not greater than 600 effective APs, the next S
Proceed to TEP06. STEP06: In this STEP06, the input buffer of the AP is read from the input buffer address 602 in the APL corresponding to the number indicated by the LOOP counter, and the contents are checked. If the contents of the input buffer are empty (that is, if the processing of the event data notified up to the previous time has been completed), STEP
Go to 09. If the contents of the input buffer are not empty (that is, the processing of the event data notified up to the previous time has not been completed), the process proceeds to STEP07. FIG. 7 shows the contents of the input buffer of each such AP. Each time event data is generated, an event code 701 and an event ID 70
2 and the set time 703 for the input buffer are 1 SE
As T, information for m-set is set in the input buffer of each AP. When each AP processes the event data using one SET of the event code 701, the event ID 702, and the set time 703 for the input buffer, the information of the one SET is cleared. STEP07: In this STEP07, in the input buffer in the APL corresponding to the number indicated by the LOOP counter,
Since this is the case where the SET relating to the event data notified up to the previous time remains, the set time 703, which is the time at which this 1 SET is set, is checked. And the set time 70
If it is determined that the predetermined time has not elapsed from 3, the process proceeds to STEP09, and the next 1 SET is additionally set in the input buffer. If it is determined that the predetermined time has elapsed from the set time 703, the corresponding AP proceeds to STEP08. STEP08; In this STEP08, since the AP corresponding to the number indicated by the LOOP counter is not active,
The active flag for the AP corresponding to the number indicated by the LOOP counter in the APL is turned off.
All input buffers for the AP corresponding to the number indicated by the P counter are cleared, and the process returns to STEP05. STEP09: In this STEP09, the active flag 6 of the AP corresponding to the number indicated by the LOOP counter is set.
Only when 03 is ON, the event code 7 is stored in the input buffer of the AP corresponding to the number indicated by the LOOP counter.
01, the event ID 702, and the set time 703 for the input buffer are set as 1 SET. Set time 7
For 03, the current time held by the information processing apparatus 2 is used. When setting this 1 SET, it is set to a free area in the input buffer. STEP10: In STEP10, the LOOP counter is counted up by +1 and the process returns to STEP05. The various APs always wait for the set time of the above event code, event ID, and these event codes and event IDs in the buffer to be set as a set in an input buffer unique to each AP. When these sets of information are set in the AP, it is determined whether the event needs to be processed by its own AP, and the necessary processing is executed by its own AP. For example, in the case of a member-managed AP, processing unique to each AP is performed, such as updating information of the corresponding member in the corresponding data file 209. Then, regardless of whether or not these necessary processes are executed, the information of the processed set in its own input buffer is cleared, so that the communication program 203 can process the set event data by the input data. It is determined that the process is completed in the AP corresponding to the buffer. Here, the recording method of the event data file 208 will be supplemented.
In the present invention, for example, the event data file 208 closes the event data file 208 in which event data that occurred earlier at a certain time every day is recorded,
The event data file 208 is newly created and opened after the time, and the event data generated after the event data is referred to as the newly created event data. In file 208. Therefore, the closed event data file 208 is not duplicated and stored. Closed event data file 20
8 is treated as a read-only file without any write processing thereafter.

[0009]

The event management system apparatus of the present invention has an active program list showing a list of executable programs in a plurality of business program groups, and adds an event ID to event data relating to various events occurring in the facility. Event data distribution using each input buffer corresponding to all business programs indicated in the active program list, notifying the reception of event data to all active programs and entrusting the processing of the event data. The method is adopted. With this event data distribution method, even if the content of work on the receiving side is changed or added, no change in the communication program on the sending side occurs, only the change or addition of the business program on the receiving side becomes necessary, and the received data is processed. On the sending side, there is no load of determining the contents of the received data such as whether the received data is processed by the same business program, and the effect is that the delay of the message processing that occurs one after another in real time can be reduced. In the event management system apparatus according to the present invention, it is not necessary to provide a communication program with information in the form of parameters or the like and to distribute the information.

[Brief description of the drawings]

FIG. 1 is a schematic diagram showing a block configuration of a front accounting machine according to an embodiment in an event management system device of the present invention.

FIG. 2 is a schematic diagram illustrating a block configuration of an information processing apparatus according to an embodiment of the event management system apparatus of the present invention.

FIG. 3 is a schematic diagram showing a recording format of an index information file according to an embodiment in the hotel management system apparatus of the present invention.

FIG. 4 is a schematic diagram showing a recording format of an index information record of an event data file according to an embodiment in the hotel management system device of the present invention.

FIG. 5 is a flowchart illustrating a display processing procedure of a real-time monitor according to an embodiment in the event management system apparatus of the present invention.

FIG. 6 is a schematic diagram showing a recording format of an active program list according to an embodiment in the facility management system apparatus of the present invention.

FIG. 7 is a schematic diagram showing a recording format of an input buffer of each business program of the embodiment in the facility management system apparatus of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Front accounting machine 103 Information storage unit 1031 Room information file 1032 Usage status file 1033 Sales information file 104 Terminal 2 Information processing device 201 Information input unit 202 Information display unit 203 Communication program 204 Message transmission / reception part 205 DB management AP 206 Real-time monitor AP 207 DB access component 208 Event data file 2081 Index information file 600 Number of effective APs 601 Business program (AP) name 602 Address of input buffer of AP 603 AP active flag 701 Event code of received event data 702 Event of received event data ID 703 Set time to input buffer

Claims (3)

[Claims] An event data file for recording event data relating to various events together with an event code indicating the type of the event data; a plurality of business programs each having an input buffer; In an event management system device having an active program list showing a list of executable programs and a communication program responsible for transmitting and receiving information related to the event with an external computer, the communication program receives the event code together with the event code. To the event data, an event ID is added as unique index information in the event code, recorded in the event data file, and the event code and the event ID in the event data are Each entry corresponding to all business programs shown in the active program list Event buffer, by notifying all business programs indicated in the active program list of the occurrence of the event, and entrusting the processing of the event data to each business program, by setting How to sort. 2. The business program in which the event code and the event ID are set in the input buffer, if the event code determines that the event is not an event to be processed by itself, Deletes the event code and the event ID of the event data file. If the event code determines that the event is an event to be processed by itself, the event data file is used with the event code and the event ID as a key. 2. The event data distribution method according to claim 1, further comprising the steps of: reading the content of the event buffer and performing necessary business processing; and deleting the event code and the event ID in the input buffer. 3. The communication program according to claim 1, wherein the event code and the event ID set in the input buffer of each business program are not erased within a predetermined time. 3. The event data distribution method according to claim 1, wherein said business program is deleted.