JP2012181795A - Event management system and event management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To simply achieve an event management system and an event management method for exchanging event information corresponding to multimedia.SOLUTION: An event management system 1 according to the invention includes a transmission terminal P for transmitting event information, an event management server X for receiving the event information from the transmission terminal P, and a reception terminal S for receiving the event information from the event management server X. The transmission terminal P stores contents T1 and T2 capable of expressing multimedia and transmits the event information in association with the contents T1 and T2. The reception terminal S receives and previously registers the contents T1 and T2 through the event management server X. When receiving the event information from the transmission terminal P, the reception terminal S simultaneously performs processing and display of the event information and the contents T1 and T2 associated with the event information.

Description

  The present invention relates to an event management system and an event management method.

  Conventionally, event information is started between information terminal devices connected via a network. For example, there is an event management system that can exchange event information between information terminal devices in real time via a predetermined server.

  Patent Document 1 discloses an event management system that manages event information between information terminal devices. This event management system can transmit and receive event information between information terminal devices via an event management server.

JP 2007-531092 A

  However, according to the conventional event management system, the event information is limited to plain text including only characters and symbols. That is, the event information does not correspond to ruled lines, decorative characters, images, or the like. For this reason, there has been a problem that the method of describing event information is limited.

  It is an object of the present invention to easily construct an event management system and an event management method for exchanging event information corresponding to multimedia.

  In order to solve the above problems, an event management system of the present invention includes a transmission terminal that transmits event information, an event management server that receives event information from the transmission terminal, and a reception terminal that receives event information from the event management server. An event management system comprising: a content that the transmitting terminal can express multimedia in, and transmitting the event information in association with the content, wherein the receiving terminal manages the content in the event management system Receiving and registering in advance through a server, and receiving the event information from the calling terminal, simultaneously processing and displaying the event information and the content associated with the event information. Features.

  According to this configuration, a transmission terminal that transmits event information, an event management server that receives event information from the transmission terminal, and a reception terminal that receives event information from the event management server are connected by a network. The transmission terminal stores content that can express multimedia, and transmits event information to the event management server in association with the content. The receiving terminal receives the content via the event management server and registers in advance. When receiving event information from the transmitting terminal, the event information and the content associated with the event information are processed and displayed at the same time.

  In the event management system configured as described above, the present invention is characterized in that the content is described in HTML (HyperText Markup Language). According to the present invention, in the event management system configured as described above, the content is described in a script language.

  In the event management system configured as described above, the present invention includes a plurality of at least one of the transmitting terminal and the receiving terminal. According to this configuration, the number of transmitting terminals and receiving terminals may be 1: N (N: natural number), N: 1, or N: N.

  In the event management system configured as described above, the present invention is characterized in that the event management server performs event management by a pubsub (publish-subscribe) function of XMPP (eXtensible Messaging and Presence Protocol).

  In order to solve the above problems, an event management method of the present invention includes a transmission terminal that transmits event information, an event management server that receives event information from the transmission terminal, and event information from the event management server. An event management method comprising: a receiving terminal for storing content that the transmitting terminal can express multimedia, and transmitting the event information in association with the content; and Is received via the event management server and registered in advance, and when receiving the event information from the transmitting terminal, the event information and the content associated with the event information are processed simultaneously. And a step of displaying.

  Further, the present invention is characterized in that in the event management method having the above configuration, the content is described in HTML. Further, the present invention is the event management method configured as described above, wherein the content is described in a script language.

  According to the present invention, it is possible to easily construct an event management system and an event management method for exchanging event information corresponding to multimedia.

The figure which shows the whole structure of the event management system of 1st Embodiment of this invention. The block diagram which shows the structure of the transmission terminal of 1st Embodiment of this invention. The block diagram which shows the structure of the receiving terminal of 1st Embodiment of this invention. The block diagram which shows the structure of the event management server of 1st Embodiment of this invention. The timing chart figure which shows operation | movement until the event information of 1st Embodiment of this invention is displayed The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the content described by HTML of 1st Embodiment of this invention The figure which shows the content described by Javascript of 1st Embodiment of this invention The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure which shows the XMPP control data of 1st Embodiment of this invention. The figure by which the content and event information of 1st Embodiment of this invention are displayed simultaneously The figure which shows the whole structure of the event management system of 2nd Embodiment of this invention.

  Embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram for explaining an event management system 1 according to an embodiment of the present invention. An event management server X is arranged in the network net. The sending terminal P and the receiving terminal S do not need to be arranged on the network net. The transmission terminal P transmits an event via the event management server X, and the reception terminal S receives event information via the event management server X. The transmitting terminal P and the receiving terminal S are communication terminals such as a mobile phone, a PDA (Personal Digital Assistant), a personal computer, and a smartphone.

  FIG. 2 is a block diagram showing the configuration of the transmitting terminal P. The transmission terminal P includes a control unit 22 that controls each unit. The control unit 22 is connected to a communication unit 21, a PubSub processing unit 23, a storage unit 24, an input unit 25, an event management unit 26, and a content processing unit 27.

  The communication unit 21 has a configuration capable of wired or wireless communication, and can perform protocol communication defined in XMPP via the control unit 22.

  XMPP (eXtensible Messaging and Presence Protocol) is a protocol based on XML (eXtensible Markup Language) that is being standardized and standardized by XSF (XMPP Standards Foundation) independent of the XMPP working group of IETF (Internet Engineering Task Force). . XMPP dynamically controls applications such as instant messaging, presence ("what the person is now"), multi-person chat, voice or video phone, collaborative work, content syndication, generalized routing of XML data . This enables real-time communication in an event management system such as the Internet. Also, it consists of a plurality of extension protocols (XEP: XMPP Extension Protocol) standardized according to each purpose.

  The Pubsub unit 23 manages event information using a function defined in XEP-0060 (Publish-Subscribe).

  XEP-0060 has two functions, a Subscribe function and a Publish function. The Subscribe function is a function for prescribing a contract for transmitting a change notification from the transmission terminal P to the reception terminal S when the event information is changed in the transmission terminal P (subscribe). The Publish function is a function of transmitting (publishing) the changed event information to the receiving terminal S and the change terminal P transmitting the change notification.

  The storage unit 24 includes a ROM, a RAM, and the like, and stores predetermined content created by the user. The input unit 25 receives various instructions input by the user and given to the calling terminal P. The event management unit 26 transmits event information.

  The content processing unit 27 performs processing for receiving predetermined content created by the user and processing for outputting content to the receiving terminal S. The content processing unit 27 includes an HTML processing unit 27A and a Javascript processing unit 27B. The HTML processing unit 27A processes content described in HTML. The Javascript processing unit 27B processes the content described in Javascript. The JavaScript processing unit 27B is not limited to Javascript, and may process a script language such as VBSscript or JScript. Further, content transferred from another device may be processed so as to be applicable in the present embodiment.

  FIG. 3 is a block diagram showing the configuration of the receiving terminal S. The receiving terminal S includes a control unit 32 that controls each unit. The control unit 32 is connected to a communication unit 31, a PubSub processing unit 33, a storage unit 34, an input unit 35, a display unit 36, and a content processing unit 37.

  The communication unit 31 has a configuration capable of wired or wireless communication, and can perform protocol communication defined by XMPP via the control unit 32.

  The Pubsub unit 33 receives event information based on the contents defined in XEP-0060.

  The storage unit 34 is configured by a ROM, a RAM, and the like, and stores content created by the transmission terminal P, data input by a user input operation, and the like via the content processing unit 37. The input unit 25 receives various instructions input by the user and given to the receiving terminal S. The display unit 36 displays the event information and the content associated with the event information at the same time.

  The content processing unit 37 processes content transferred from the transmission terminal P, and includes an HTML processing unit 37A and a Javascript processing unit 37B. The HTML processing unit 37A processes content described in HTML. The Javascript processing unit 37B processes the content described in Javascript. The JavaScript processing unit 37B is not limited to Javascript, and may process a script language such as VBSscript or JScript.

  FIG. 4 is a block diagram showing the configuration of the event management server X. The event management server X includes a control unit 42 that controls each unit. The control unit 42 is connected to a communication unit 41, a PubSub node management unit 43, a storage unit 44, an input unit 45, and a PubSub interface 46.

  The communication unit 41 can be wired or wirelessly communicated, and can perform protocol communication defined by XMPP via the control unit 42.

  The Pubsub node management unit 33 manages event information from the transmission terminal P and the reception terminal S based on the contents defined in XEP-0060.

  The storage unit 44 is configured by a ROM, a RAM, and the like, and stores event information and the like. The input unit 45 is operated and input by the user. The PubSub interface unit 46 processes input / output of event information from the transmission terminal P and the reception terminal S.

  FIG. 5 is a timing chart showing the operation of the event management system 1. For example, a system that notifies event information (body temperature) to a doctor in charge or a nurse in charge when taking a temperature measurement of a patient in a hospital is taken as an example. The sending terminal P is held by the patient, and the receiving terminal S is held by the doctor in charge or the nurse in charge.

  In step S1, the PubSub processing unit 23 of the calling terminal P creates XMPP control data m1 as shown in FIG. 6 and transmits it to the event management server X. As a result, a node expressing event information is generated. In the XMPP control data m1, the <iq> tag is information of the transmission terminal P that is the transmission source ("P @ domain / mobile"), an identifier of the XMPP control data m1 ("cr561nd0"), and the event management server X that is the transmission destination. Information ("X.domain"), the type attribute ("set") of the XMPP control data m1, and the name of the node ("temperature_of_publisher") representing the event information are described.

  In step S2, a reply to the effect that the XMPP control data m1 has been received from the event management server X to the calling terminal P is made.

  In step S3, the content T1 described in HTML as shown in FIG. 7 is transferred by the HTML processing unit 27A. In addition to still images, the content T1 can describe multimedia content that can be expressed in HTML, such as video and audio.

  In step S4, the content T2 described by Javascript as shown in FIG. 8 is transferred by the Javascript processing unit 27B. Since the content T2 is described by Javascript, dynamic content can be expressed. Moreover, you may describe by other script languages, such as VBSscript and Jscript, instead of Javascript.

  In step S5, the PubSub processing unit 23 of the transmitting terminal P creates XMPP control data m2 as shown in FIG. 9 and transmits it to the event management server X. Thereby, event information is set.

  Here, only plain text can be described in the conventional XEP-0060 rules. Therefore, it is impossible to describe multimedia contents. However, as shown in FIG. 9, XMPP control data m2 adds the contents created in steps S3 and S4 as plain text.

  As shown in FIG. 9, <field "var = pubsub # html" type = "text"> from <value> to </ value> is described in plain text as in the past. However, since the description is described in HTML or Javascript, it is possible to express multimedia contents such as images and sounds and dynamic contents.

  In step S6, a reply to the effect that the XMPP control data m2 has been received from the event management server X to the calling terminal P is made.

  In step S7, the receiving terminal S searches the event management server X using a protocol defined in XMPP XEP-0030 (Service Discovery). Then, the event management server X is discovered, and XMPP control data m3 as shown in FIG. 10 is created from the PubSub processing unit 33 and transmitted to the event management server X.

  In the XMPP control data m3, the <iq> tag is information on the receiving terminal S that is the transmission source ("S @ domain / mobile"), an identifier of the XMPP control data m3 ("gh921nx3"), and the event management server X that is the transmission destination. Information (“X.domain”), type attribute (“set”) of XMPP control data m3, and node name (“temperature_of_publisher”) are described.

  In step S8, XMPP control data m4 as shown in FIG. 11 is transmitted from the event management server X to the calling terminal P, and an additional acceptance request is made. Since there is an additional reception request part mm4 in FIG. 11, event information related to the node name ("temperature_of_publisher") can be additionally received.

  In step S9, the receiving terminal S creates XMPP control data m5 as shown in FIG. 12, transmits the XMPP control data m5 to the event management server X, and requests for addition.

  In step S10, XMPP control data m6 as shown in FIG. 13 is transmitted from the event management server X to the receiving terminal S. At this time, the contents T1 and T2 stored in the event management server X are transmitted from the transmitting terminal P to the receiving terminal S in association with the node name (“temperature_of_publisher”).

  In step S11, the content T2 described by Javascript is registered in the Javascript processing unit 37B of the receiving terminal S. In step S12, the content T1 written in HTML is registered in the HTML processing unit 37A of the receiving terminal S.

  This completes the preparation for notifying event information among the transmission terminal P, the event management server X, and the reception terminal S. The procedure when an event actually occurs is described below.

  In step S <b> 13, an event associated with the node name (“temperature_of_publisher”) is generated from the event management unit 21 from the patient terminal P of the hospital. For example, a patient takes a temperature using a thermometer.

  In step S14, the PubSub processing unit 23 of the transmission terminal P creates XMPP control data m7 as shown in FIG. 14 and transmits it to the event management server X. As shown in FIG. 14, in the XMPP control data m7, it is described as <publish node = "temperature_of_publisher"> that it is associated with the name of the node ("temperature_of_publisher") representing the event information.

  In step S15, a reply to the effect that the XMPP control data m7 has been received from the event management server X to the calling terminal P is made.

  In step S16, the event management server X searches for event subscribers of event information associated with the node name ("temperature_of_publisher"). In step S7, the event management server X can determine that the receiving terminal S is a subscriber of event information associated with the node name ("temperature_of_publisher").

  In step S 17, the event management server X creates XMPP control data m 8 as shown in FIG. 15 and transmits it to the receiving terminal S.

  In step S18, processing of the XMPP control data m8 and the Javascript content T2 associated therewith is started from the Javascript processing unit 37B. As a result, the event information message is dynamically expressed by JavaScript. In step S19, processing of the XMPP control data m8 and the content T1 associated therewith is started from the HTML processing unit 37A.

  In step S20, as shown in FIG. 16, the contents T1 and T2 processed in steps S18 and S19 are simultaneously processed and displayed on the display unit 36. Thereby, the doctor in charge or the nurse in charge who has the receiving terminal S can grasp the temperature measurement result of the patient.

  As described above, according to the present embodiment, the transmission terminal P that transmits event information, the event management server X that receives event information from the transmission terminal P, the reception terminal S that receives event information from the event management server X, The content management system 1 includes the contents T1 and T2 that the transmitting terminal P can express multimedia, and transmits the event information in association with the contents T1 and T2, and the receiving terminal S transmits the contents T1 and T2. T2 is received via the event management server X and registered in advance. When receiving event information from the calling terminal P, the event information and the contents T1 and T2 associated with the event information are processed simultaneously. indicate.

  Therefore, it is possible to easily construct an event management system and an event management method for exchanging event information corresponding to multimedia.

  Further, since the content T1 is described in HTML, the description content can be expressed flexibly. Further, since the content T2 is described in a script language, dynamic content can be easily expressed.

  In addition, the event management server X performs event management by the XMPP Pubsub function. This facilitates event management among a plurality of terminals.

(Second Embodiment)
In the first embodiment, there is one transmission terminal P and one reception terminal S, but there may be a plurality of transmission terminals P and reception terminals S as shown in FIG. The transmission terminals P1 to P4 are communication terminals that are attached to a train track and have a new sensor function. Trains TR1 to TR3 run on the track.

  The transmission terminals P1 to P4 are discovered by the sensor function every time the trains TR1 to TR3 pass, and the event information of the transmission terminal is transmitted to the event management server X. The event information includes identification information of the transmission terminals P1 to P4, train identification information, transit time, and the like. Then, the event management server X aggregates the predetermined information and transmits it to the receiving terminals S1 and S2. By having the receiving terminals S1 and S2 function as a railway operation command center, the operation status of the trains TR1 to TR3 can be grasped in real time and a predetermined instruction can be given to the trains TR1 to TR3.

  According to the present embodiment, it is possible to easily construct a more convenient event management system than having a plurality of transmission terminals P1 to P4.

  In addition, when the terminal environment of the receiving terminals S1 and S2 cannot process content corresponding to multimedia, plain text may be displayed as it is as before.

DESCRIPTION OF SYMBOLS 1 Event management system 23, 33 PubSub processing part 27, 37 Content processing part 46 PubSub interface P, P1-P4 Transmission terminal S, S1-S2 Reception terminal m1-m8 XMPP control data X Event management server

Claims (8)

An event management system comprising: a transmission terminal that transmits event information; an event management server that receives event information from the transmission terminal; and a reception terminal that receives event information from the event management server,
The transmitting terminal stores content that can express multimedia, transmits the event information in association with the content,
The receiving terminal receives the content via the event management server and registers in advance, and when receiving the event information from the transmitting terminal, the event information and the content associated with the event information An event management system which processes and displays, simultaneously.   The event management system according to claim 1, wherein the content is described in HTML.   The event management system according to claim 1, wherein the content is described in a script language.   The event management system according to claim 1, comprising a plurality of at least one of the transmitting terminal and the receiving terminal.   The event management system according to claim 1, wherein the event management server performs event management by a XMPP Pubsub function. An event management method comprising: a transmission terminal that transmits event information; an event management server that receives event information from the transmission terminal; and a reception terminal that receives event information from the event management server,
Storing content capable of expressing multimedia by the transmitting terminal, and transmitting the event information in association with the content;
The receiving terminal receives the content via the event management server and registers in advance, and when receiving the event information from the transmitting terminal, the event information and the content associated with the event information , Simultaneously processing and displaying,
An event management method characterized by comprising:   The event management method according to claim 6, wherein the content is described in HTML.   The event management method according to claim 6, wherein the content is described in a script language.

Images