JP5021894B2 - Event information management system and event information management method used therefor - Google Patents

Description

The present invention relates to event information management method for use in the event information management system and it particularly relates to an information communication system using an XML (eXtensible Mark-up Language) technology.

  Conventionally, in an event notification system or event management system, data can be generalized by converting internal event information into an XML file, and various applications can be used by using the data from other systems or registering it in a server database. A system that can be used from is proposed.

  As the above system, taking advantage of the feature of XML that does not depend on the order of data arrangement, event information generated in one system is XML documented and transmitted to another system, and information analyzed in the other system is used. There is a system (see, for example, Patent Document 1).

  As another system, an apparatus that manages a database converts information received from another apparatus or information read from an input apparatus into an XML document, and then classifies the information for each type and stores the information in a database. There is a system for extracting necessary information from a computer equipped with a computer (for example, see Patent Document 2).

  However, in order to provide a function for documenting information in XML, a suitable processing capability is required, and the processing load when a function for documenting internal information in an existing information communication terminal is incorporated is considered. Absent.

  In addition, since information output from various information communication terminals cannot be simply converted to XML, the information communication terminal changes the internal information to data having a structure suitable for XML to some extent and notifies the server. There is a need to.

  Furthermore, when the structure of XML data notified from the information communication terminal changes frequently, maintenance work of the XML database frequently occurs or a high-performance and expensive XML database having a structure conversion function is required. Installation is required.

JP 2002-82817 A JP 2002-175297 A

  In the conventional event notification system or event management system described above, since the event information is information closed inside the information communication terminal, it is necessary for a person at the designer level to extract the information, and if the program is complicated The more work is required. The extraction work and the reflection work to the database take time, and it is difficult to cope with it easily in a short period of time, and it is necessary to rely on a high-performance XML database that automatically analyzes the changed XML data.

  Therefore, the conventional event notification system or event management system requires frequent maintenance work and a high-performance and expensive XML database in order to prevent the deterioration in maintainability when the XML data structure of the information communication terminal changes. There is a problem of doing.

  In addition, with the conventional event notification system or event management system, if XML conversion software (XML parser) is incorporated, XML analysis and creation can be simplified and new development time can be reduced. On the other hand, since a considerable amount of storage area and processing capacity are required for processing, the information communication terminal uses an XML parser to convert the internal information into an XML file, thereby reducing the storage capacity of the information communication terminal. However, there is a problem of increasing the processing load.

  Even if the system is newly designed, if an event information notification function is to be added to an existing system, the event information notification function may have to be abandoned due to hardware limitations.

Accordingly, an object of the present invention is to solve the above-mentioned problems, and an event information management system capable of improving maintainability without requiring frequent maintenance work or a high-performance and expensive XML database, and an event used therefor It is to provide an information management method .

Another object of the present invention is to provide an event information management system and an event information management method used therefor that can suppress the compression of the storage capacity and the increase in processing load due to the addition of the event generation function to the information communication terminal side that generates the event information. It is to provide.

An event information management system according to the present invention includes an information communication terminal that includes a firmware update function, converts each of a plurality of event information constituting one operation into XML (extensible Mark-up Language) data, and notifies the data.
An event information management system comprising a server for storing event information converted into the XML data in the information communication terminal in a database,
The information communication terminal is
In an initialization process at the time of startup after updating the firmware, an XML structure definition file indicating the structure of the XML data that changes as the event information is added or changed based on the type of event information disclosed to the outside Means for creating an XML structure definition table necessary for creation;
Means for transmitting the XML structure definition table to the server after completion of the initialization process;
The server includes means for creating the XML structure definition file based on an XML structure definition table received from the information communication terminal;
The server centrally manages the structure of the XML data for each information communication terminal that notifies the event information.

Other event information management system according to the present invention, in addition to the above configuration, the information communication terminal,
Means for notifying event information of the event together with information indicating which stage of the operation the event continues in a case where an event occurs, and storing the plurality of event information as event unit information in the event information storage means When,
Means for sandwiching each event information of the unit of operation stored in the event information storage means at the time of completion of the operation with a tag and converting the information into the XML data;
Means for transmitting the converted XML data to the server as a data packet,
The server includes means for converting XML data received from the information communication terminal into an XML file and registering it in the database .

An event information management method according to the present invention includes an information communication terminal that includes a firmware update function, converts each of a plurality of event information constituting one operation into XML (extensible Mark-up Language) data, and notifies the data.
An event information management method used in a system including a server that stores event information converted into XML data in the information communication terminal in a database,
In the initialization process when the information communication terminal is started after updating the firmware, the structure of the XML data that changes as the event information is added or changed based on the type of event information disclosed to the outside A process of creating an XML structure definition table necessary for creating an XML structure definition file to be shown, and a process of sending the XML structure definition table to the server after completion of the initialization process;
The server executes a process of creating the XML structure definition file based on the XML structure definition table received from the information communication terminal;
The server centrally manages the structure of the XML data for each information communication terminal that notifies the event information.

Other event information management methods according to the present invention include, in addition to the above processing,
When the information communication terminal reports an event, the event information of the event is notified together with information indicating a stage of the operation in which the event continues, and the plurality of event information is used as the operation unit information. A process of storing in the storage means, a process of interposing each event information of the operation unit stored in the event information storage means at the time of completion of the operation with a tag and converting the data into the XML data, and the converted XML data Processing to send to the server as a data packet,
The server executes processing for converting XML data received from the information communication terminal into an XML file and registering it in the database .

  That is, the main cause of poor maintainability is a change in the XML (extensible Mark-up Language) file structure accompanying addition / change of event information. When new functions are added to the information communication terminal that notifies the event information and the event information stored in the server increases, the server-side database usually needs to be changed. In addition, even in the same information communication terminal, the event information to be notified may differ depending on the firmware version, and enormous effort is required to manage the contents and correct the server side.

  The XML file structure in the event information management system is usually determined by extracting information that the information communication terminal wants to provide to the outside, and a DTD (Document Type Definition) file (XML data structure definition file) is created based on the extracted information. The

  The event information management system according to the present invention provides a structure of event information provided in the information communication terminal in an information communication terminal having a firmware update function and capable of function expansion in the future, that is, for creating a DTD file. This information is automatically generated and notified to the database server, so that the event information provided by the information communication terminal can be notified to the database server regardless of the firmware version.

  More specifically, in the event information management system of the present invention, first, the terminal control unit registers the type of internal processing information to be disclosed to the outside at the time of initialization in the event information management unit, and the event information management unit creates a DTD file. The necessary table is created and stored in the event information storage unit. After completion of initialization of the terminal control unit, the event information management unit transmits the DTD table to an external database server.

  The operation information management unit passes the received DTD table to the DTD file creation unit, and creates a DTD file. Thereby, in the event information management system of the present invention, it is easy to update the DTD file even when the firmware of the information communication terminal is updated.

  The number of events to be processed inside the information communication terminal varies depending on the provision function of the information communication terminal. However, if the event information is converted into XML one by one and transmitted to the database server, the processing load of the information communication terminal In addition to increasing network traffic, it also increases the communication load on the network.

  If it is necessary to analyze the event information generated inside the information communication terminal in detail, the external application that uses the information stored in the database server is not the event unit information but the operation unit unit. Use information. For example, taking an exchange system as an example, there is a call management application for managing telephone call information. Such applications are not individual event information such as “call”, “dial”, “end call”, but event information from “call” to “end call” and information generated during the operation (call duration) , Fees, etc.).

  Of course, if the event information generated individually is stored in the database of the server, and the event information required by the application is collected and used as operation information, there is no inconvenience on the application side. However, it is obvious that the processing load and network load of the information communication terminal increase in the process until the data is stored in the database.

  If there is no difference in the information that can be used, event information that occurs in the information communication terminal should be finally sent to the server side as operation unit information used by the application. Since the service provided by the information communication terminal always has a predetermined operation, and the start and end of the service are managed by the information communication terminal, it is possible to determine a plurality of event information as operations.

  Therefore, in the event information management system of the present invention, the terminal control unit registers event information in the event information management unit when an internal process (event) occurs due to an operation of the input unit or a command received from the network. In addition, at this time, the event information management unit notifies a plurality of internal event information in units of operations by notifying which stage (start, intermediate processing, end) of the continuous operation the registered event indicates. Is stored in the event information storage unit.

  When the operation ends, the event information management unit converts the operation information stored in the event information storage unit into XML. The XML data is not converted into a file using an XML parser, but the data (conforming to XML) in which the stored event information is sandwiched between tags is sent as a simple data packet to the database server, and the operation information management unit uses XML. Create a file and register it in the XML database.

  Thus, in the event information management system of the present invention, information is managed by reducing the number of XML processes by managing event information in units of operations, reducing packets sent to the network, and reducing the processing load by not using an XML parser. Event information can be extracted without imposing a heavy load on the communication terminal or network, and since the data packet is already in XML format on the database server side, it is easy to create a file and register it in the XML database Is possible.

  The event information management system according to the present invention can be improved in maintainability without requiring frequent maintenance work and a high-performance and expensive XML database by adopting the configuration and operation as described below. An effect is obtained.

  In addition, another event information management system of the present invention is configured and operated as described below, thereby reducing the storage capacity and processing load by adding an event generation function to the information communication terminal side that generates event information. The effect that increase can be suppressed is acquired.

  Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the configuration of an event information management system according to an embodiment of the present invention. In FIG. 1, an event information management system according to an embodiment of the present invention is configured by connecting an information communication terminal 1 and a database server 2 via an IP (Internet Protocol) network 100.

  The information communication terminal 1 includes a data transmission / reception unit 11 that transmits and receives IP data, an event information processing unit 12, a terminal control unit 13 that controls the information communication terminal 1, and a display unit 14 such as a display / LCD (Liquid Crystal Display). And an input unit 15 such as a keyboard / button, and a storage unit 16 for storing information in the information communication terminal 1.

  The event information processing unit 12 includes an event information management unit 121, an event information storage unit 122, an XML (extensible Mark-up Language) data conversion unit 123, a DTD (Document Type Definition: XML data structure definition) table creation unit 124, It is composed of

  The terminal control unit 13 of the information communication terminal 1 describes in advance a process for notifying the event information management unit 121 of the tag information of the event information notified to the database server 2 and the data registered in the tag. In addition, the event information storage unit 122 uses an empty area of the storage unit 16 that the information communication terminal 1 has.

  The database server 2 includes a data transmission / reception unit 21 that transmits / receives IP data, an operation information processing unit 22, and an XML database 23. The operation information processing unit 22 includes an operation information management unit 221, a reception information storage unit 222, an XML file creation unit 223, and a DTD file creation unit 224.

  Each of the above parts operates as follows. That is, the terminal control unit 13 notifies the event information management unit 121 of tag information of data to be registered when an event occurs in the initialization process at the time of activation. The event information management unit 121 requests the DTD table creation unit 124 to update the table every time tag information is registered. The DTD table creation unit 124 transmits the created DTD table to the database server 2 when the initialization process of the terminal control unit 13 is completed.

  The operation information management unit 221 of the database server 2 passes the received DTD table to the DTD file creation unit 224. The DTD file creation unit 224 creates a DTD file based on the DTD table, and registers the created DTD file in the XML database 23. To do.

  When an event occurs in the information communication terminal 1, the terminal control unit 13 registers data in the event information management unit 121. The event information management unit 121 stores the registered event information in the event information storage unit 122 until the operation is completed.

  When the operation is completed, the event information management unit 121 requests the XML data conversion unit 123 to convert the operation information into XML. The XML data conversion unit 122 sandwiches the data stored in the event information storage unit 122 with the tag information stored in the event information storage unit 122, creates data in a format conforming to the XML format, and transmits the data to the database server 2. .

  The operation information management unit 221 of the database server 2 passes the received XML data to the XML file creation unit 223, and the XML file creation unit 223 creates an XML file based on the XML data, and registers the created XML file in the XML database 23. To do.

  2 is a diagram showing operation information in the XML format notified in one embodiment of the present invention, and FIG. 3 is a diagram showing a DTD file required by the database server 2 in one embodiment of the present invention. FIG. 4 is a diagram showing a DTD file creation table created in an embodiment of the present invention.

  FIG. 5 is a flowchart showing the tag information registration operation in the information communication terminal 1 of FIG. 1, and FIG. 6 is a flowchart showing the DTD table creation operation in the information communication terminal 1 of FIG. The operation of the DTD file creation process according to an embodiment of the present invention will be described with reference to FIGS. 5 and 6 is realized by the terminal control unit 13 executing the program in the storage unit 16 and controlling the event information processing unit 12.

  When the information communication terminal 1 is to notify the database server 2 of operation information having the XML structure shown in FIG. 2, the DTD file shown in FIG. 3 is required in order to analyze the data structure on the database server 2 side. The minimum information necessary for creating the DTD file shown in FIG. 3 is the tag “key”, “tag name”, “link key”, and “data presence / absence” in the DTD table shown in FIG.

  In the present embodiment, by adding a “tag type” to this, the start and end of the event are determined and managed in units of operations. As a result, in this embodiment, it is possible to efficiently notify event information by combining fixed information and a plurality of event information as operation information.

  The information necessary for creating the DTD table shown in FIG. 4 can be obtained from the information managed by the terminal control unit 13 of the information communication terminal 1. Information necessary for creating the DTD table in the initialization process is notified to the DTD table creating unit 124 via the event information management unit 121.

  For example, when the <terminal type> tag shown in FIG. 2 is registered, the terminal control unit 13 first has a tag name “terminal type”, a link key “0 (no link)”, data presence / absence “False”, and tag type “fixed”. Are registered (steps S1 to S4 in FIG. 5).

  As shown in FIG. 6, the DTD table creation unit 124 confirms that there is no character string “terminal type” in the DTD table, and registers the received information in the new key “1”. After the registration is completed, the DTD table creation unit 124 notifies the registered key number “1” to the terminal control unit 13 via the event information management unit 121.

  Next, the terminal control unit 13 registers the tag information of the data by using the registered “terminal type” key number. <Identification information 1> When registering a tag, tag name “identification information 1”, link key “1 (“ terminal type key number ”)”, data presence / absence “True”, and tag type “data” are registered respectively. (Steps S11 to S14 in FIG. 6). With this link key information, it can be defined that “identification information 1” is an element of “terminal type”.

  After the registration is completed, the DTD table creation unit 124 notifies the key number “2” registered in the terminal control unit 13 via the event information management unit 121 (step S15 in FIG. 6). The terminal control unit 13 stores this key number “2” as a key of “identification information 1” and uses it when registering data when an event occurs.

  Thus, when the terminal control unit 13 completes tag information registration (initialization is completed), the event information management unit 121 instructs the DTD table creation unit 124 to transmit the DTD table. The DTD table creation unit 124 saves the created DTD table in the event information storage unit 122, and then transmits information on the DTD table to the database server 2.

  The operation information management unit 221 of the database server 2 passes the received DTD table to the DTD file creation unit 224, and the DTD file creation unit 224 creates a DTD file based on the link key information of the DTD table and stores it in the XML database 23. sign up.

  FIG. 7 is a diagram showing an XML data creation table created in one embodiment of the present invention, and FIG. 8 is a flowchart showing an event information generation operation in the information communication terminal 1 of FIG. With reference to FIG. 1, FIG. 2, FIG. 7, and FIG. 8, the operation of the event information generation process according to an embodiment of the present invention will be described. The process shown in FIG. 8 is realized by the terminal control unit 13 executing the program in the storage unit 16 and controlling the event information processing unit 12.

  When the event A occurs in the information communication terminal 1 and the data “DATA1” of “information a1” and the data “DATA2” of “information a2” can be acquired, the terminal control unit 13 detects the event information management unit 121. Register data in. Data registration of “information a1” is performed by notifying the event information management unit 121 of the registered key number of “information a1” and the data “DATA1”. Even when the event B or the event C occurs, the terminal control unit 13 performs the registration process in the same manner as described above.

  The content that the terminal control unit 13 processes for event generation is only to notify the event information management unit 121 of the registered key number and data every time an event occurs, so that the control of the information communication terminal 1 is affected. It is characteristic that there are few.

  The operation of the event information processing unit 12 will be described with reference to the flowchart shown in FIG. As shown in FIG. 8, the event information management unit 121 stores the registered event information in the event information storage unit 122 until the operation is completed (steps S21 to S26 in FIG. 8).

  The event information management unit 121 stores the XML data conversion table shown in FIG. 7 in the event information storage unit 122 based on the DTD table created by the DTD table creation unit 124. When the tag type of the event information notified by the terminal control unit 13 is “start”, the data unit other than the data whose tag type is “fixed” in the XML data conversion table shown in FIG. Register the data on the basis.

  When an event with the tag type “intermediate” occurs, data registration is repeated based on the key number. If the tag type is “end”, data is registered based on the key number, and then the XML data conversion unit 123 is requested to create and transmit XML data.

  Based on the XML data conversion table (see FIG. 7) stored in the event information storage unit 122, the XML data conversion unit 122 sandwiches each data with tag information, and stores data in a format conforming to the XML format shown in FIG. It is created and transmitted to the database server 2 (steps S27 and S28 in FIG. 8).

  The operation information management unit 221 of the database server 2 passes the received XML data to the XML file creation unit 223, and the XML file creation unit 223 creates an XML file based on the XML data, and registers the created XML file in the XML database 23. To do.

  As described above, in this embodiment, each information communication terminal 1 notifies the database server 2 of the structure of XML data transmitted by itself when the information communication terminal 1 is started up, so that information communication terminals having different firmware versions or information communication terminals of other systems are used. Can be identified on the database server 2 side. As a result, the database server 2 can centrally manage the data structure of each information communication terminal 1 that notifies the event information, and can improve maintainability.

  Also, in this embodiment, the XML data creation processing within the information communication terminal 1 is streamlined by collecting information in units of operations, and event information is transmitted without using an XML parser that is normally used for creating an XML file. Therefore, it is possible to minimize the storage capacity and processing load when adding the event information notification function to the existing information communication system. As a result, in this embodiment, various applications using the internal event information of the existing system can be provided, and the convenience of the existing system can be improved.

It is a block diagram which shows the structure of the event information management system by one Example of this invention. It is a figure which shows the operation information of the XML format notified in one Example of this invention. It is a figure which shows the DTD file which a database server requires in one Example of this invention. It is a figure which shows the table for DTD file creation created in one Example of this invention. FIG. 5 is a flowchart showing an operation of tag information registration in the information communication terminal of FIG. It is a flowchart which shows the operation | movement of DTD table preparation in the information communication terminal of FIG. It is a figure which shows the table for XML data creation produced in one Example of this invention. It is a flowchart which shows the operation | movement of the event information generation in the information communication terminal of FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Information communication terminal 2 Database server 11 Data transmission / reception part 12 Event information processing part 13 Terminal control part 14 Display part 15 Input part 16 Storage part 21 Data transmission / reception part 22 Operation information processing part 23 XML database 100 IP network 121 Event information management part 122 Event information storage unit 123 XML data conversion unit 124 DTD table creation unit 221 Operation information management unit 222 Reception information storage unit 223 XML file creation unit 224 DTD file creation unit

Claims (10)

An information communication terminal that includes a firmware update function, converts each of a plurality of pieces of event information constituting one operation into XML (extensible Mark-up Language) data, and notifies the information.
An event information management system comprising a server for storing event information converted into the XML data in the information communication terminal in a database,
The information communication terminal is
In an initialization process at the time of startup after updating the firmware, an XML structure definition file indicating the structure of the XML data that changes as the event information is added or changed based on the type of event information disclosed to the outside Means for creating an XML structure definition table necessary for creation;
Means for transmitting the XML structure definition table to the server after completion of the initialization process;
The server includes means for creating the XML structure definition file based on an XML structure definition table received from the information communication terminal;
An event information management system, wherein the server centrally manages the structure of the XML data for each information communication terminal that notifies the event information. The information communication terminal is
Means for notifying event information of the event together with information indicating which stage of the operation the event continues in a case where an event occurs, and storing a plurality of event information as event unit information in the event information storage means; ,
Means for sandwiching each event information of the unit of operation stored in the event information storage means at the time of completion of the operation with a tag and converting the information into the XML data;
Means for transmitting the converted XML data to the server as a data packet,
2. The event information management system according to claim 1, wherein the server includes means for converting XML data received from the information communication terminal into an XML file and registering it in the database. The means for creating the structure of the XML data creates the XML structure definition table on the basis of information on the tag of data to be registered when the event occurs in the initialization process,
3. The event information management system according to claim 2, wherein the means for transmitting the XML structure definition table notifies the server of the XML structure definition table at the end of the initialization process.   When the information communication terminal creates the XML structure definition table, the information communication terminal updates the XML structure definition table each time the tag information of data to be registered when the event occurs is notified. The event information management system according to claim 3. The information communication terminal includes a means for managing the plurality of event information in the operation unit of the application to determine the start and end and the events based on XML structure definition table is available, the operation of the plurality of event information Means for combining as information to create the XML data,
5. The event information management system according to claim 2, wherein the XML data is notified from the information communication terminal to the server. An information communication terminal that includes a firmware update function, converts each of a plurality of pieces of event information constituting one operation into XML (extensible Mark-up Language) data, and notifies the information.
An event information management method used in a system including a server that stores event information converted into XML data in the information communication terminal in a database,
In the initialization process when the information communication terminal is started after updating the firmware, the structure of the XML data that changes as the event information is added or changed based on the type of event information disclosed to the outside A process of creating an XML structure definition table necessary for creating an XML structure definition file to be shown, and a process of sending the XML structure definition table to the server after completion of the initialization process;
The server executes a process of creating the XML structure definition file based on the XML structure definition table received from the information communication terminal;
An event information management method comprising: centrally managing the structure of the XML data for each information communication terminal to which the server notifies the event information. When the event occurs, the information communication terminal notifies the event information of the event together with information indicating which stage of the operation the event continues, and stores a plurality of event information as the operation unit information. A process for storing in the means, a process for interposing the event information for each operation stored in the event information storage means at the time of completion of the operation with tags, and converting the data into the XML data, and the converted XML data as data Processing to send to the server as a packet,
The event information management method according to claim 6, wherein the server executes a process of converting XML data received from the information communication terminal into an XML file and registering the XML file in the database. In the process of creating the structure of the XML data, the XML structure definition table is created based on the tag information of the data registered when the event occurs in the initialization process of the information communication terminal,
8. The event information management method according to claim 7, wherein in the process of transmitting the XML structure definition table, the XML structure definition table is notified to the server at the end of the initialization process.   When the information communication terminal creates the XML structure definition table, it updates the XML structure definition table each time the tag information of the data to be registered when the event occurs is notified. The event information management method according to claim 8. The information communication terminal, a process of managing a plurality of event information in the operation unit application of the event information to determine the start and end and the event based on the XML structure definition table is utilized, the plurality of Processing to combine the event information as operation information to create the XML data,
The event information management method according to any one of claims 7 to 9, wherein the XML data is notified from the information communication terminal to the server.

Images