KR101275637B1 - Method for integrated alerting to heterogeneous alerting system and system using the same - Google Patents

Abstract

PURPOSE: A method for integrated alerting to a heterogeneous alerting system and a system using the same are provided to protect the life of the public by removing an alerting dead area by sharing alerting in different alerting systems. CONSTITUTION: According to a method for integrated alerting, alerting is proclaimed. A message with data for the proclaimed alerting is delivered to an alerting system through an alerting gateway. The message includes one of an alerting code, a destination ID, alerting attributes and alerting area information. Configuration setting is requested to the alerting system through the alerting gateway. The alerting system sets a configuration. [Reference numerals] (100) Integrated prediction/alerting control system; (200) Integrated prediction/alerting gateway; (310) Prediction/alerting server-1; (320) Prediction/alerting server-2; (410) Prediction/alerting terminal-1; (420) Prediction/alerting terminal-1

Description

Heterogeneous Example / Integration Example for Alarm System / Method for Integrated Alerting to Heterogeneous Alerting System and System Using the Same

The present invention relates to a method / system for issuing an example / alarm, and more particularly to a method and system for issuing an example / alert to an example / alarm system.

Each different example / alarm system is developed and operated independently for its own purpose. For example, in the case of automatic rain warning / alarm systems, people will be notified of warnings and warnings for more than a certain amount of rainfall, and in the case of disaster message boards, it will also display citizenship and disaster / disaster warnings / alert texts.

These systems are operated by local government officials and disaster management agencies, and in some cases, one agency may operate two or more different example / alarm systems separately and issue examples / alerts.

In order to issue examples / alarms through different example / alarm systems, operation must be done through the issuing software and systems of each system. That is, if there is an A, B, C, D example / alarm system, commands must be issued through the issuing software of the A, B, C, and D systems, respectively, to operate the respective systems to issue the example / alarm.

This approach creates time delays, management difficulties, and many operational / management personnel problems in urgent situations where quick warnings / warnings of emergencies are needed.

The present invention has been made to solve the above problems, the object of the present invention is to solve the yes / warning blind spots by sharing the yes / warning information between heterogeneous yes / warning systems existing or to be developed in the future In addition to wars and other important disasters, different examples / alarms can be shared by other examples / alarms systems to inform the citizens, thus helping to save people's lives by resolving the squares. To provide a way to issue an alarm.

In accordance with an embodiment of the present invention for achieving the above object, an integrated example / alarm issuing method includes: issuing an example / alarm; And forwarding a message containing data on the issued example / alarm to the example / alarm system through the example / alarm gateway, wherein the message includes, yes / alarm code, destination ID, yes / alarm attribute and example. / At least one of the alarm area information.

The message may further include at least one of a type of an example / alarm medium and an example / alarm ID.

In addition, the message may further include at least one of a priority for a plurality of examples / alarms, an example / alarm issue time, and an example / alarm valid time.

And, the integrated example / alarm issuing method according to the present embodiment, the step of requesting a report for the example / alarm issuance to the example / alarm system; And transmitting, by the example / alarm system, a report response to the example / alarm issuance.

Also, the report request may include a yes / alarm ID and request data, and the report response may include a yes / alarm ID, request data, and a result.

In addition, according to the present embodiment, the integrated example / alarm initiation method may include: requesting configuration of the configuration from the example / alarm system; And performing, by the example / alarm system, the configuration setting. The configuration setting request may include a configuration variable and a configuration value.

In addition, the integrated example / alarm issuing method according to the embodiment, the step of requesting a configuration search to the example / alarm system; And reporting the configuration by the example / alarm system. The configuration report may include a configuration variable and a configuration value.

On the other hand, according to another embodiment of the present invention, the integrated example / alarm issuing system, Gateway for transmitting a message containing the data for the example / alarm issued by the example / alarm; And an example / alarm system for receiving and processing the message, wherein the message includes at least one of an example / alarm code, a destination ID, an example / alarm attribute, and an example / alarm area information.

As described above, according to the present invention, it is possible to consolidate the announcement through a number of examples / alarm system, it is possible to eliminate the blind / warning blind spots to inform people of the rapid disaster cases / alarms in the event of a disaster, the lives of the people Can protect.

In addition, it is difficult to eliminate yes / alarm blind spots in each existing example / alarm system, so it is often necessary to add additional systems and redundant installations, thereby eliminating costly and administrative inefficiencies. Can be.

1 shows an integrated example / alarm command system to which the present invention is applicable;
FIG. 2 shows the structure of a message delivered between the gateway and example / alarm servers shown in FIG. 1;
3 is a diagram provided in the description of the connection process between the integrated example / alarm gateway and the example / alarm server;
4 is a diagram provided in the description of the reconnection process between the integrated example / alarm gateway and the example / alarm server;
5 is a view provided to explain the process of disconnection between the integrated example / alarm gateway and the example / alarm server;
6 is a diagram provided in the description of the process of adding / modifying / removing registration between the integrated example / alarm gateway and the example / alarm server;
7 is a diagram provided in the description of the process of transferring the example / alarm data from the integrated example / alarm gateway to the example / alarm server,
8 is a diagram provided in the description of a process of requesting a report on an example / alarm issuance by the integrated example / alarm gateway to the example / alarm server;
FIG. 9 is a diagram provided to explain a process of sending event data to an integrated example / alarm gateway by the example / alarm server,
10 is a view provided to explain a configuration setting process for an integrated example / alarm system, and
11 is a diagram provided to explain a configuration search procedure for an integrated example / alarm system.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

1. Integrated yes / alarm command system

1 is a diagram illustrating an integrated example / alarm command system to which the present invention is applicable. The integrated example / alarm initiation system shown in FIG. 1 may issue an integrated example / alarm for heterogeneous example / alarm systems.

The integrated example / alarm command system to which the present invention is applicable includes, as shown in FIG. 1, the integrated example / alarm control system 100, the integrated example / alarm gateway 200, and heterogeneous example / alarm servers 310. 320 and heterogeneous example / alarm terminals 410 and 420 may be connected to each other and configured to communicate with each other.

The integrated example / alarm gateway 200 delivers the issued example / alarm through the integrated example / alarm control system 100 to the corresponding heterogeneous example / alarm systems 310 & 410, 320 & 420.

Hereinafter, the message format and the message flow in the integrated example / alarm command system shown in FIG. 1 will be described in detail. In particular, common message formats transmitted and received between the example / alarm servers 310 and 320 and the integrated disaster example / alarm gateway 200 and message flows such as connection, registration, transmission, and reporting between them will be described in detail.

2. Message Structure

FIG. 2 is a diagram illustrating the structure of a message transferred between the gateway 200 and the example / alarm servers 310 and 320 shown in FIG. 1. As shown in FIG. 2, a message may be composed of a message header and a message body.

The Message Header includes: 1) Message Name, 2) Message ID, 3) Message Header Length, 4) Receiver ID, and 5) Sender ID. ID), 6) Sent Time, 7) Message Length, and 8) Authentication Information.

Since the structure of the message header shown in FIG. 2 is merely exemplary, it is possible to omit some fields, replace some fields with other fields, or add another field.

The message shown in FIG. 2 can be expressed in XML format as follows.

<IDANP>

<MessageHeader>

<MessageName> messagename </ MessageName>

<MessageID> messageid </ MessageID>

<MessageHeaderLength> messageheaderlength </ MessageHeaderLength>

<ReceiverID> receiverid </ ReceiverID>

<SenderID> senderid </ SenderID>

<SentTime> time </ SentTime>

<MessageLength> messagelength </ MessageLength>

<AuthenticationInformation> key </ AuthenticationInformation>

</ MessageHeader>

<MessageBody> messagebody </ MessageBody>

</ IDANP>

3. Message header

3.1 Message Name

The Message Name is a field that contains the name of the message transmitted and received between the integrated example / alarm gateway 200 and the example / alarm servers 310 and 32.

The Message Name is determined according to the message type.The message type is 1) Connection Request, 2) Connection Response, 3) Registration Request, 4) Registration Response, 5) Alert Data Transmission, 6) Data Request, 7) Data Response, 8) Data Ack, 9) Data Report, and 10) Keepalive.

3.2 Message ID

Message ID is a field that contains an ID functioning as a separator for distinguishing messages transmitted and received between the integrated example / alarm gateway 200 and the example / alarm servers 310 and 32.

3.3 Message Header Length

The Message Header Length is a field that contains information about the length of the message header.

3.4 Receiver ID

The Receiver ID is a field in which an ID of a receiver to receive a message is stored, and the Receiver ID may be expressed as "location information. System name. #". Here, the location information may be an address or geographical information (latitude and longitude) in the administrative district.

3.5 Sender ID

The Sender ID is a field that contains the ID of the sender to which the message is to be sent. The Sender ID may be expressed as "location information. System name. #" Similarly to the Receiver ID. Here, the location information may be an address or geographical information (latitude and longitude) in the administrative district.

3.6 Sent Time

Sent Time is a field that contains information on the time the sender sent a message. Sent Time may be expressed as "year / month / day / hour / minute / second".

3.7 Message Length

Message Length This field contains information about the length of the entire message.

3.8 Authentication Information

Authentication Information is a field that contains the authentication key required for authentication.

4.Message Body

The message body has different contents according to the message type. Hereinafter, the contents of the message body according to the message type will be described in detail.

4.1 Connection Request

The connection request is a message sent by the example / alarm server 310 or 320 when a connection request is made to the integrated example / alarm gateway 200, and may include init connections, reconnections, and disconnections as sub-elements.

4.2 Connection Response

The connection response is a message sent by the integrated example / alarm gateway 200 in response to the connection request from the example / alarm servers 310 and 320. The result is included as a lower element, and the result may include a result value and a result description. have.

4.3 Registration Request

The Registration Request is a message sent by the example / alarm server 310 or 320 to the integrated example / alarm gateway 200 for a registration request, and may include Type and Content as sub-elements.

Type includes Init Registration, Update Registration, Delete Registration, and Content may include Profile. Profiles may include ASname, ASpurpose, ManagedATInformation, ManagedATCount, ManagedATLocation, and ASSupportMedia.

Here, ASname is the name of the example / alarm system, ASpurpose is the purpose of the example / alarm system, ManagedATInformation is the managed example / alarm terminal information, and ManagedATCount is the number of managed example / alarm terminals.

In addition, ManagedATLocation is a managed example / alarm terminal location, and ASSupportMedia is a media format supported by the example / alarm system, and includes text, audio, image, and video.

4.4 Registration Response

The registration response is a message sent by the integrated example / alarm gateway 200 in response to a registration request of the example / alarm servers 310 and 320, and a result may be included as a lower element. Result may include ResultValue and Result Description.

4.5 Alert Data Transmission

Alert Data Transmission is a message sent by the integrated example / alarm gateway 200 to the example / alarm servers 310 and 320 when the example / alarm origination data is transmitted, and as the lower element, Alert Media Type, Alert ID, Data, Priority, IssueTime. , ValidTime may be stored.

Alert Media Type can be Code, Text, Audio, Video, Image as an example / alert media type, and Alert ID can be defined in the form of "Commander.AlertCode. #" As a unique ID of the issued example / alert.

Data consists of Alert Code as an example / alarm code, Target ID as a destination ID, Alert Status as an example / alert attribute, Resource URL as a resource address, Alert Description as a description of the example / alert, and Alert Area as an example / alert area. Can be.

Priority refers to the priority, and when a plurality of examples / alarms are issued, priority may be set. Issue Time is the issue time and is expressed as "Year / Month / Day / Hour / Minute / Second", and Valid Time is the effective time of Yes / Alarm as "Year / Month / Day / Hour / Minute / Second".

4.6 Data Request

The data request is a message sent from the integrated example / alarm gateway 200 and the example / alarm servers 310 and 320 to each counterpart when requesting data, and type and data may be included as lower elements.

Type refers to a format for requesting data and may include Data Request, Report Request, Configuration Set, and Configuration Get, and Data may include Alert ID, Configuration Variable, Configuration Value, and Request Data.

4.7 Data Response

The data response is a message sent to each counterpart in response to the data request by the integrated example / alarm gateway 200 and the example / alarm servers 310 and 320, and may include Type, Data, and Result as sub-elements.

Type refers to a format for requesting data and may include a data request, a report request, a configuration set, and a configuration get, and the data may include an alert ID, a configuration variable, a configuration value, and a response data. Result may include Result Value and Result Description.

4.8 Data Ack

The Data Ack is a response message for data transmission between the integrated example / alarm gateway 200 and the example / alarm servers 310 and 320 and has no child elements.

4.9 Data Report

The data report is a message used by the example / alarm server 310 or 320 to report data to the integrated example / alarm gateway 200, and may include report transmission type, type, data, and result as sub-elements.

Report Transmission Type is a transmission format of a report, which is Event, Periodic, and Type can be a Data Report or Alert Report. According to the type, Data contains Alert ID and ReportData, and Result may include Result Value and Result Description.

4.10 Keepalive

Keepalive is a message used when checking the connection status between the integrated example / alarm gateway 200 and the example / alarm servers 310 and 320, and has no child elements.

5. Message Flow

Hereinafter, a process of transferring the above-described messages between the integrated example / alarm gateway 200 and the example / alarm servers 310 and 320 will be described in detail. Hereinafter, for convenience of notation and explanation, the example / alarm server 310 or 320 will be collectively referred to as the representative number "300".

5.1 Connection

3 is a diagram provided to explain the connection process between the integrated example / alarm gateway 200 and the example / alarm server 300.

As shown in FIG. 3, when the example / alarm server 300 that wants to connect transmits a connection request (Init Connection) to the integrated example / alarm gateway 200, the integrated example / alarm gateway 200 receives the example / alarm. The authentication / registration procedure for the server 300 is performed. Connection Request (Init Connection) is a message sent when an initial connection request is made.

After completion of the authentication / registration procedure, the integrated example / alarm gateway 200 transmits a Connection Response (Success / Fail, Description) to the example / alarm server 300. Success / Fail is the processing result of Connection Request, and Description is the description of the processing result.

5.2 Reconnection by Keepalive

4 is a diagram provided to explain a reconnection process between the integrated example / alarm gateway 200 and the example / alarm server 300.

As shown in FIG. 4, if the yes / alarm server 300 does not receive an Ack even though the yes / alarm server 300 transmits the Keepalive to the integrated yes / alarm gateway 200, the yes / alarm server 300 may be the integrated yes / alarm gateway 200. Send Connection Request (Reconnection) to.

Keepalive is a message used when checking the connection status between the integrated example / alarm gateway 200 and the example / alarm server (310, 320), Connection Request (Reconnection) is a message sent when the reconnection request.

Thereafter, the integrated example / alarm gateway 200 performs an authentication / registration procedure for the example / alarm server 300 and transmits a connection response (Success / Fail, Description) to the example / alarm server 300.

5.3 Disconnect

5 is a diagram provided to explain a process for disconnecting between the integrated example / alarm gateway 200 and the example / alarm server 300.

When the example / alarm server 300 that wants to release the connection transmits a connection request (disconnection) to the integrated example / alarm gateway 200, the integrated example / alarm gateway 200 checks / confirms the example / alarm server 300. Perform the delete procedure. Connection Request (Disconnection) is a message sent when a connection release request is made.

Thereafter, the integrated example / alarm gateway 200 transmits a Connection Response (Result, Description) to the example / alarm server 300. Result is the processing result for disconnection, and Description is a description of the processing result.

5.4 Add / Modify / Remove Registrations

6 is a diagram provided to explain the registration addition / modification / removal process between the integrated example / alarm gateway 200 and the example / alarm server 300.

If the example / alarm server 300 that wants to add / modify / remove a registration sends a registration request (Add / Update / Delete, Profile) to the integrated example / alarm gateway 200, the integrated example / alarm gateway 200 is yes. Process the registration add / modify / remove requested by the alarm server 300.

Thereafter, the integrated example / alarm gateway 200 transmits a Registration Response (Success / Fail, Description) to the example / alarm server 300. Success / Fail is the result of processing the Registration Request, and Description is the description of the processing.

5.5 Yes / alarm data transmission

FIG. 7 is a diagram provided to explain a process of transmitting example / alarm data from the integrated example / alarm gateway 200 to the example / alarm server 300.

When the yes / alarm is issued from the integrated yes / alarm control system 100 and the yes / alarm data is delivered to the integrated yes / alarm gateway 200, the integrated yes / alarm gateway 200 is connected to the yes / alarm server 300. Send an Alert Data Transmission containing yes / alert data.

The example / alarm server 300 receiving the alert data transmission transmits the alert data transmission to the example / alarm terminals 410 and 420.

Alert Data Transmission may include Alert Media Type, Alert ID, Yes / Alarm Data, Priority, Issue Time, Valid Time.

Alert Media Type can be Code, Text, Audio, Video, Image as an example / alert media type, and Alert ID can be defined in the form of "Commander.AlertCode. #" As a unique ID of the issued example / alert.

The example / alarm data consists of an example / alert code, an alert code, a destination ID, a target ID, an example / alert attribute, an alert status, a resource address, a resource URL, an example / alarm technology, an alert description, and an example / alert area, an alert area. Can be.

Priority is the priority for a plurality of examples / alarms, Issue Time is the issue time, and Valid Time is the valid time of the yes / alarm.

5.6 Report request for yes / alert issuance

8 is a diagram provided to explain the process of the integrated example / alarm gateway 200 to request the report for the example / alarm issued to the example / alarm server 300.

If there is a report request from the integrated example / alarm control system 100, the integrated example / alarm gateway 200 transmits a data request for a report request to the example / alarm server 300.

The integrated example / alarm gateway 200 that receives the report request from the integrated example / alarm control system 100 transmits a data request for the report request. The transmitted Data Request includes Alert ID and Request Data.

Then, the yes / alarm server 300 obtains data for the requested Alert ID from the yes / alarm terminals 410 and 420 and transmits a data response for the report response to the integrated yes / alarm gateway 200. The transmitted Data Response includes Alert ID, Response Data, and Result.

5.7 Event Data Transfer

FIG. 9 is a diagram provided to explain a process of sending event data to the integrated example / alarm gateway 200 by the example / alarm server 300.

When the example / alarm server 300 transmits the data report to the integrated example / alarm gateway 200, the integrated example / alarm gateway 200 transmits the received data report to the example / alarm control system 100.

The Data Report may include a Report Transmission Type, a Type (Data Report, Alert Report) and a Result indicating a transmission format (Event, Periodic) of an Event and a Report.

5.8 Configuration

10 is a diagram provided to explain a configuration setting process for an integrated example / alarm system.

If there is a configuration setting request from the integrated example / alarm control system 100, the integrated example / alarm gateway 200 transmits a data request for the configuration set to the example / alarm server 300. The Data Request to be sent contains a Configuration Variable and a Configuration Value.

The example / alarm server 300 instructs / checks the configuration setting in the example / alarm terminals 410 and 420, and then transmits a data response for reporting the configuration setting result to the integrated example / alarm gateway 200. In addition to the Configuration Variable and Configuration Value, the transmitted Data Response may further include Success / Fail and Description.

The integrated example / alarm gateway 200 receiving the data response from the example / alarm server 300 reports the configuration setting result to the integrated example / alarm control system 100.

5.9 Configuration Search

11 is a diagram provided to explain a configuration search procedure for an integrated example / alarm system.

If there is a configuration search request from the integrated example / alarm control system 100, the integrated example / alarm gateway 200 transmits a data request for configuration search to the example / alarm server 300. The Data Variable to be sent contains a Configuration Variable.

The example / alarm server 300 inquires / acquires the configuration from the example / alarm terminals 410 and 420 and transmits a data response for the configuration report to the integrated example / alarm gateway 200. The transmitted Data Response may include a Configuration Variable and a Configuration Value.

The integrated example / alarm gateway 200 that receives the data response from the example / alarm server 300 reports the configuration to the integrated example / alarm control system 100.

While the above has been shown and described with respect to preferred embodiments of the present invention, the present invention is not limited to the specific embodiments described above, it is usually in the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

100: integrated example / alarm control system
200: integration example / alarm gateway
310, 320: Heterogeneous example / alarm server
410, 420: heterogeneous example / alarm terminal

Claims (8)

Issuing a yes / alarm; And
And forwarding a message containing data on the issued example / alarm to the example / alarm system through the example / alarm gateway.
The message is
At least one of an example / alarm code, a destination ID, an example / alarm attribute, and an example / alarm area information,
Requesting configuration of the configuration of the example / alarm system through the example / alarm gateway; And
And performing the configuration setting by the example / alarm system.
The method of claim 1,
The message is
Yes / alarm medium and example / alarm ID further comprising at least one.
The method of claim 1,
The message is
An integrated example / alarm issuing method further comprising at least one of a priority for a plurality of examples / alarms, an example / alarm issuing time and an example / alarm validity time.
The method of claim 1,
Requesting a report of an yes / alert issuance from the yes / alarm system; And
And sending, by the example / alarm system, a report response to the example / alarm issuance.
5. The method of claim 4,
In the report request,
Yes / alert ID and request data,
In the report response,
An integrated example / alarm issuing method characterized by including an example / alarm ID, request data, and result.
The method of claim 1,
In the configuration setting request,
Integration example / alarm issuing method characterized by containing configuration variable and configuration value.
The method of claim 1,
Requesting a configuration search from the yes / alarm system; And
And reporting, by the example / alarm system, a configuration.
In the Configuration report,
Integration example / alarm issuing method characterized by containing configuration variable and configuration value.
Yes / alarm control system to issue yes / alarm;
A gateway for transmitting a message including data on an example / alarm issued by the example / alarm control system; And
An example / alarm system for receiving and processing the message;
The message is
At least one of an example / alarm code, a destination ID, an example / alarm attribute, and an example / alarm area information,
The example / alarm control system,
Request configuration setting of the example / alarm system through the example / alarm gateway,
The example / alarm system,
Integration example / alarm command system, characterized in that for performing the configuration setting according to the request.

Images