KR20160024054A

KR20160024054A - Apparatus for generating emergency message

Info

Publication number: KR20160024054A
Application number: KR1020140109625A
Authority: KR
Inventors: 김건; 이용훈; 김광용; 박소라; 이용태
Original assignee: 한국전자통신연구원
Priority date: 2014-08-22
Filing date: 2014-08-22
Publication date: 2016-03-04

Abstract

A device for generating a disaster message is disclosed. The apparatus for generating a disaster message includes a frame generator for generating a disaster message including disaster broadcast information according to a structure of a disaster message frame, and a transmission header and a transmission packet of the disaster message according to an EDI (Emergency Service Data Interface) And a data output unit for outputting the disaster message frame as an EDI frame. The layer of the disaster message frame includes a disaster broadcast information layer for transmitting disaster broadcast information, a disaster broadcast information layer for adding descriptive information on disaster broadcast information, A service layer (Emergency Broadcasting Service Layer), a segment layer where metadata and disaster broadcasting information are divided into a predetermined size, a payload which is divided data according to division, and a packet header which is division and multiplexing information for a payload Include the service packet layer (Service Packet Layer) and the packet header and payload A transmission frame layer (Layer Transmission Frame) including the transport header by including the transport packet, the transport header indicator indicating the presence or absence of emergency disaster information.

Description

[0001] Apparatus for generating emergency message [

The present invention relates to an apparatus for generating a disaster message.

Recently, the Korea Meteorological Administration has established a basic plan to build a national earthquake early warning system by 2020 in order to drastically reduce the time from earthquake observation to earthquake breaking or earthquake notification. As part of this plan, DMB (Terrestrial Digital Multimedia Broadcasting) broadcasting network, which is a personal portable broadcasting medium, which is being developed. If an earthquake early warning system and T-DMB disaster broadcasting system are possible, even if people do not watch broadcasting, the waiting receiver is automatically activated and earthquake and tsunami information can be transmitted early, Can be maximized.

However, this technology has not been proposed at present. Especially, due to the characteristics of earthquake disasters, there is a demand for a technology capable of transmitting disaster information more rapidly.

The present invention proposes a disaster message generating apparatus for generating a disaster message enabling a DMB receiver to automatically receive emergency broadcast information urgently.

According to an aspect of the present invention, an apparatus for generating a disaster message is disclosed.

The apparatus for generating a disaster message according to an exemplary embodiment of the present invention includes a frame generator for generating a disaster message including disaster broadcast information according to a structure of a disaster message frame and a transmission header of the disaster message and an EDI And a data output unit outputting an EDI frame according to an Emergency Service Data Interface standard, wherein the layer of the disaster message frame includes a disaster broadcast information layer for delivering the disaster broadcast information, The metadata and the disaster broadcasting information are divided into a predetermined size, a segmented data segment according to the segmentation, Load, a packet header that is division and multiplexing information for the payload Includes a transmission packet header including a transmission header including a service packet layer (Service Packet Layer), a transmission header indicator indicating whether the transmission packet including the packet header and the payload exists, Layer).

If the transmission header indicator indicates that the emergency disaster information exists, the transmission header includes the transmission header indicator and the disaster type code, and if the transmission header indicator does not indicate that the emergency disaster information exists, The transport header includes a disaster indicator field indicating whether a disaster occurred, a protection level field as a transmission related field, an SF field, and a service count field.

The disaster type code is calculated in binary form by associating the alphabet code according to the type of the disaster with the ASCII code value.

The EDI frame includes a Type field indicating the type of the EDI frame, and a Data field including the transmission header and the transport packet. The EDI frame type includes a first disaster message frame, a transmission status frame, and a second disaster message Wherein the Data field includes a transport header and a transport packet when the transport header indicator does not indicate that the emergency disaster information exists if the type of the EDI frame is the first disaster message frame And a value indicating whether the EDI frame is a transmission status frame or a transmission stop status if the type of the EDI frame is a second disaster message frame. Packet.

The metadata includes a field indicating the length of the metadata, an indicator field indicating whether a service label is present, a T-DMB channel switching state, and a disaster service existence indication, a disaster service type field, and an indicator field value A service label field, a T-DMB channel switching field, and a disaster service field.

The disaster service field includes a field indicating an earthquake occurrence time, a latitude and a longitude of an earthquake occurrence area, and a field indicating the earthquake occurrence time is a 24-hour date expressed in binary using MJD (modified Julian date) A time represented by a binary number, and a minute represented by a binary number of 60 minutes.

The packet header includes a field indicating a service ID, a service type, a service priority, and a service packet number.

The present invention can generate a disaster message that enables the DMB receiver to automatically receive disaster broadcast information in an urgent manner.

1 schematically illustrates a configuration of a device for generating a disaster message;
2 shows a hierarchical structure of a disaster message frame;
Figure 3 illustrates a metadata structure;
4 is a diagram illustrating a structure of a packet header;
5 illustrates a transport header structure;
6 is a diagram illustrating an EDI (Emergency Service Data Interface) frame structure;

While the present invention has been described in connection with certain exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and similarities. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. In addition, numerals (e.g., first, second, etc.) used in the description of the present invention are merely an identifier for distinguishing one component from another.

Also, in this specification, when an element is referred to as being "connected" or "connected" with another element, the element may be directly connected or directly connected to the other element, It should be understood that, unless an opposite description is present, it may be connected or connected via another element in the middle.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate a thorough understanding of the present invention, the same reference numerals are used for the same means regardless of the number of the drawings.

1 is a view schematically illustrating a configuration of a device for generating a disaster message.

Referring to FIG. 1, the apparatus for generating a disaster message includes a frame generation unit 10 and a data output unit 20.

The frame generation unit 10 generates a disaster message including disaster broadcasting information according to the disaster message frame structure. Here, the disaster broadcast information may include text, audio, XML, image, and the like.

Hereinafter, a frame structure of a disaster message will be described with reference to FIG. 2 to FIG.

2 is a diagram showing a hierarchical structure of a disaster message frame.

Referring to FIG. 2, a layer of a disaster message frame includes an Emergency Broadcasting Layer, an Emergency Broadcasting Service Layer, a Segment Layer, a Service Packet Layer, And a frame layer (Transmission Frame Layer).

The disaster broadcasting information layer is a layer for delivering contents of disaster broadcasting information. For example, the disaster broadcast information layer may correspond to one file, and one file may be a text file, an image file, an audio file, or the like. Disaster broadcast information in the form of text, images, alarms, etc. can be transmitted using the transmission of such a file.

The disaster broadcasting service layer is a layer including contents of disaster broadcasting information and descriptive information of disaster broadcasting information. That is, in the disaster broadcasting service layer, meta data, which is explanatory information on the disaster broadcasting information, is added.

For example, FIG. 3 is a diagram illustrating a metadata structure. Referring to FIG. 3, the metadata includes an indicator field indicating a length of a metadata field, a presence or absence of a service label, a T-DMB channel switching state, and a presence of a disaster service, a disaster service type field, A T-DMB channel switching field, and a disaster service field. The meaning of each field is shown in Table 1 below.

Field name Field size
(bit) Meaning of field Meta Data Length 8 It indicates the length of the metadata, and the unit is byte (meaning the length after the metadata length field, up to 256 bytes) Service Lable Indicator One Indicates whether a service label field exists in the metadata.
0: Service label field does not exist
1: Service label field exists A channel change indicator (T-DMB Channel Change Indicator) One Indicates whether to switch to existing DMB broadcasting
0: Do not switch (T-DMB channel switching field does not exist)
1: Switching (T-DMB channel switching field exists) Emergency Service Indicator One Indication of disaster service existence
0: Disaster service field does not exist,
1: Disaster service field exists Emergency Service Type 3 0: Disaster service does not exist (ignored)
1: AEAS (Automatic Emergency Alert Service, T-DMB Disaster Alert Broadcast Service)
2: KEEW (Korean earthquake early warning, earthquake early warning service)
3-7: Define later
※ Structure of disaster service field varies according to value of disaster service type Rfu 2 Reserved for Future Use (set to 0x00) Service Label field
(Service Lable Field) Service Lable Length 6 Number of characters in the service label (name of disaster broadcasting information) (unit: 2 bytes, up to 64 characters (128 bytes)) Rfu 2 Reserved for Future Use (set to 0x00) Service Label (Service Lable) n × 16 Name of the disaster broadcasting information (UTF-16_Big endian is expressed as 2 bytes in Korean) The channel switching field (T-DMB Channel Change Field) Linked Ensemble Channel 6 Used for channel switching to switch to T-DMB broadcasting channel
Channel mapping depends on country-specific channel settings
※ In Korea, 0: 7A, 1: 7B, 2: 7C, 3: 8A, 4: 8B, 5: 8C, ... , 18: 13A, 19: 13B, 20: 13C, 21-63: Reserved The sub-channel designation (Linked Sub Channel) 6 To select subchannels for the selected ensemble, use the subchannels 0 to 63 of DAB standard as is Rfu 4 Reserved for Future Use (set to 0x00) Emergency service field
Service Field) Earthquake ID 20 Seismic code is represented by (ordinarily 4-digit integer) and serial number (6-digit integer). In this specification, serial number 6-digit integer value is represented by 20-bit binary value.
※ For example, only 397201 is used in 2013397201, and its value is represented by 0110 000 111 1001 0001 (binary number). Jinwon Vision
(Earthquake Time) 28 Indicate the time of earthquake occurrence
※ We use short form in UTC (co-ordinated universal time) of en 300 401 v1.4.1, year MJD (17bits) + hour (5bits) + minutes (6bits) Magnitude 7 Indicate scale of earthquake
※ When the magnitude is 7.1, it is expressed as 71: 47 (16), 100 0111 (2), it can be expressed from 0 to 12.7 Rfu 2 Reserved for Future Use (set to 0x00) Latitude 15 Indicate latitude value for earthquake occurrence area
※ When 37.24N: 0001110 1000 1100 (2), or 0x0E8C, this value is converted into decimal number and converted into decimal number by using 3724 (10) divided by 100 (MSB 1bit means north latitude 0 and south latitude 1 box) Longitude 16 Indicate latitude value for earthquake occurrence area
※ In the case of 128.20E: 0011 0010 0001 0100 (2) or 0x3214, and this value is converted into decimal number by dividing 12820 (10) by 100 (MSB 1 bit means Tokyo 0, West 1 box)

For example, an example of the display of the longitude, latitude and longitude is as follows.

- Original time: MJD (modified Julian date) (17bits) + hour (5bits) + minutes (6bits)

MJD 50 000: expressed as October 10, 1995, the value of MJD is incremented by 1 (when used within the range of 0-99 to 999)

ex) MJD 50 010 → October 20, 1995

City: 24-hour representation in 5-bit

ex) 23:00 to 0x17 or 1 0111 (2)

Minute: Express 60 minutes in 6 bits

ex) 58 minutes → 0x3A or 11 1010 (2)

- Latitude

Latitude values range from 0 to 90 degrees. Therefore, since it is necessary to express from 0 to 90 degrees 00 minutes, 14 bits are required as the maximum number of bits that can express 9000 as a binary number. In case of latitude (N), the latitude value is +, and in case of south latitude (S), 1 bit (0 is added to the first byte, 1 is added to the first byte) If added, a total of 15 bits are allocated to represent the latitude

ex) For 89.59S: 110 0010 1111 1111 (2)

For 37.24N: 000 1110 1000 1100 (2)

→ When the value received from the receiver (37.24N, 000 1110 1000 1100 (2)) is received, the value of 3724 (10) converted to decimal is divided by 100 and used

- Hardness

Hardness values range from 0 to 180 degrees. therefore. Since it is necessary to express from 0 to 180 degrees 00 minutes, 15 bits are required as the maximum number of bits that can express 18000 as a binary number. In the case of longitude (E), 1 bit (0 is added to the first byte, 1 is added to the first byte) is added so that the latitude value is + and the west value is W If added, a total of 16 bits are allocated to represent the longitude

ex) For 179.59W: 1100 0110 0010 0111 (2)

128.20E: 0011 0010 0001 0100 (2)

→ It is used in the same way as above latitude.

Referring again to FIG. 2, the partition layer only divides the metadata and the disaster broadcast information into a predetermined size, and management of the actual partition related information is performed in the service packet layer. For example, if the metadata and the disaster broadcast information are divided into 179 bytes in the partition layer, if the length of the metadata and the disaster broadcast information is not an integral multiple of 179 bytes, 0x00 is padded at the end of the disaster broadcast information, Is an integral multiple of 179 bytes.

The service packet layer includes information related to the division related information and the multiplexing, and includes information capable of quickly determining whether or not to parse the information of the higher layer, the disaster broadcasting service layer, in order to reduce the load of the receiver.

For example, FIG. 4 is a diagram illustrating the structure of a packet header. Referring to FIG. 4, the divided real data may be a payload, and the division and multiplexing information for each payload may be a packet header. The packet header and payload pair can be service packets. CRC-16 (length: 16 bits, polynomial: x16 + x12 + x5 + 1) can be inserted at the end of each payload. The meanings of the fields of the packet header are shown in Table 2 below.

Field name Field size
(bit) Meaning of field Service ID 8 Unique ID of the service
The receiver collects and parses the same service packet.
For disaster service, 0 ~ 7 can be fixedly assigned Service Type 3 Type of service (parser and decoder are determined according to each service type)
0: reserved
1: Text (disaster message / additional data)
2: Text (G-zip compression)
3: Audio
4: XML (Rich Text)
5: Image
6-7: reserved Service Priority 2 Fields to consider priorities when sending services
0: Unknown
1: Normal
2: Emergency
3: very urgent Service Packet Number 7 Indicates the number of the current service packet (counted from 0 to 127) First packet flag (First Flag) One Flag indicating first packet
0: Not the first packet
1: First packet End packet flag (Last Flag) One Flag indicating last packet
0: Not the last packet
1: the last packet
* If Last Flag = 1, valid data length exists only in case of last packet Rfu 2 Reserved for Future Use (set to 0x00) Useful data length 8 Actual data length in the last packet, existence of this field only when the current packet is an end packet (Last Flag = 1) (optional)

Referring again to FIG. 2, the transport frame layer is a layer for adding transport related information, each transport frame including a transport header and a transport packet, and a transport packet including one service packet. For example, the transport header may include a disaster indicator field, a protection level field, a SF field, and a service count field, which are transport related fields, which enable a disaster to be identified as quickly as possible for a disaster.

For example, FIG. 5 is a diagram illustrating a transport header structure. Referring to FIG. 5, transmission headers may be configured differently when transmission header indicators are even or odd, respectively. If the transmission header indicator is an even number, the transmission header may include a disaster type code to urgently transmit the disaster type code. If the transmission header indicator is an odd number, the transmission header may be configured as before, Lt; RTI ID = 0.0 > a < / RTI > disaster type code or an existing transport header. By constructing the transmission header in this way, the receiver can quickly interpret and display the disaster type code. In particular, when an earthquake-related disaster occurs, it is possible to secure a golden time to cope by spreading the present situation very quickly to the user.

When the transmission header indicator is 0, the meaning of each field of the transmission header (total length: 4 bytes) is as shown in Table 3 below.

Field name Field size
(bit) Meaning of field Transport Header Indicator One A field indicating whether emergency disaster information exists in the current transmission frame
0: emergency disaster information (disaster type code)
1: transport header Disaster Type Code 1
(Emergency Code 1) 7 Means the first ASCII code value Disaster Type Code 2
(Emergency Code 2) 8 Means the second ASCII code value (MSB 1bit is fixed to 0) Disaster Type Code 3
(Emergency Code 3) 8 Represents the third ASCII code value (MSB 1bit fixed at 0) Transport header CRC 8 CRC-8 (polynomial: x8 + x2 + x + 1, initial value: 0x00)
※ Application of CRC value limited to transmission header

When the transmission header indicator is 1, the meaning of each field of the transmission header (total length: 4 bytes) is as shown in Table 4 below.

Field name Field size
(bit) Meaning of field Transport Header Indicator One A field indicating whether emergency disaster information exists in the current transmission frame
0: emergency disaster information (disaster type code)
1: transport header Emergency indicator One A field indicating whether emergency disaster information exists in the current transmission frame
0: Emergency Disaster Information
1: Additional data Protection Level 3 Transmission-related protection level
0: Reserved
1 to 2: Reserved
3: CC R = 1/2
4 to 6: Reserved
7: CC R = 4/5 SF (Spreading Factor) 2 Spreading factor applied to the disaster broadcast transmission channel in which the transmission packet is transmitted
0: Reserved
1: Reserved
2: SF = 128
3: Reserved Rfu One Reserved for Future Use (set to 0x00) Number of Services
(Service Number) 8 Number of services currently being transmitted (256 serviceable Rfu 8 Reserved for Future Use (set to 0x00) Transport header CRC 8 CRC-8 (polynomial: x8 + x2 + x + 1, initial value: 0x00)
※ Apply CRC value limited to transmission header (from Disaster Indicator ~ Rfu field)

For example, earthquake disaster codes and ASCII code tables are shown in Tables 5 and 6 below, respectively.

Alarm item Disaster Code Code pool Tsunami warning TSA Tsunami Watch Tsunami warning TSW Tsunami Warning Earthquake evacuation broadcast TSE Tsunami Evacuate Tsunami alert TSP Tsunami Precaution Alarm Earthquake Hazard Warning TSH Tsunami Hazardous Alarm Tsunami TSO Tsunami Occurrence Earthquake occurrence stage 1 EOA Earthquake Occurrence Watch Earthquake occurrence stage 2 EPA Earthquake Occurrence Precaution Alarm Three phases of earthquake EHA Earthquake Occurrence Hazardous Alarm Earthquake warning EQW Earthquake Warning

Decimal number Hexadecimal Binary number ASCII code value 65 0x41 0100 0001 A 66 0x42 0010 B 67 0x43 0100 0011 C 68 0x44 0100 0100 D 69 0x45 0100 0101 E 70 0x46 0100 0110 F 71 0x47 0100 0111 G 72 0x48 0100 1000 H 73 0x49 0100 1001 I 74 0x4A 0100 1010 J 75 0x4B 0100 1011 K 76 0x4C 0100 1100 L 77 0x4D 0100 1101 M 78 0x4E 0100 1110 N 79 0x4F 0100 1111 O 80 0x50 0101 0000 P 81 0x51 0101 0001 Q 82 0x52 0101 0010 R 83 0x53 0101 0011 S 84 0x54 0101 0100 T 85 0x55 0101 0101 U 86 0x56 0101 0110 V 87 0x57 0101 0111 W 88 0x58 0101 1000 X 89 0x59 0101 1001 Y 90 0x5A 0101 1010 Z

For example, in Table 5, if a disaster type code for a tsunami occurrence is sent, the disaster type code can be set as the ASCII code for the alphabet TSO, which is the disaster code of the tsunami occurrence. That is, the disaster type code 1 can be set to the ASCII code value 0x54 corresponding to T, the disaster type code 2 can be set to the ASCII code value 0x53 corresponding to S, and the disaster type code 3 can be set to ASCII The code value can be set to 0x4F. The MSB of all the binary values of the ASCII code represented by the alphabet is set to 0. Therefore, when the transmission header indicator is set to the emergency disaster information, the MSB of the disaster type code 1 automatically handles the transmission header indicator as 0 can do.

Referring again to FIG. 1, the data output unit 20 outputs a transmission header and a transmission packet in an EDI frame according to an EDI (Emergency Service Data Interface) standard. That is, the output format of the transport header and the transport packet has the EDI standard. EDI's physical interface specification is TCP / IP.

For example, FIG. 6 is a diagram illustrating an EDI (Emergency Service Data Interface) frame structure. Referring to FIG. 6, an EDI frame includes an STX field, a Type field, a Data field, a CRC field, and an ETX field.

The STX field is a synchronization field indicating the start of the EDI frame, and its value can be set to 0xA55A.

The Type field is a field indicating the EDI frame type. The EDI frame can be divided into three types: a disaster message frame A (existing transmission header + transmission packet), a transmission status frame, and a disaster message frame B (transmission header including emergency disaster information + transmission packet). The meaning of the Type field is as shown in Table 7 below.

Type field value EDI frame type 0x0 One disaster message frame A (one existing transmission header (4 bytes) and one transmission packet (187 bytes)) 0x1 Transmission status frame 0x2 One disaster message frame B (a bundle of a transport header (4 bytes) and one transport packet (187 bytes) including one emergency disaster information) 0x03 to 0xFF Future use

As shown in Table 7, the configuration of the Data field varies depending on the Type field value. That is, the meaning of the Data field value is as follows.

- If the Type field value is Disaster Message Frame A (Type = 0x0)

A. SEQ_ID (1 byte): unique number of multiplexed transmission frame

B. SEQ_SIZE (4 bytes): total number of multiplexed transmission frames

C. SEQ_NO (4 bytes): Sequence number of multiplexed transmission frame (starting with 0)

D. Value (191 bytes): one transmission frame (a bundle of existing transmission header and transmission packet)

Here, the transmission header (4 bytes) includes a disaster indicator (1 bit), a protection level (3 bits), a transmission packet SF (2 bits), Rfu (2 bits), a service number (8 bits), Rfu And the transmission packet can be 187 bytes.

- If the Type field value is a transmission status frame (Type = 0x1)

A. SEQ_ID (1 byte): unique number of multiplexed transmission frame

B. SEQ_SIZE (4 bytes): total number of multiplexed transmission frames

C. SEQ_NO (4 bytes): Fixed to 0

D. Value (1 byte): Transmission status frame

Here, the meaning of the value of the transmission status frame is shown in Table 8 below.

Transmission status frame value Transmission status Meaning 0x0 STOP 0x1 to 0xFF Not defined

- If the Type field value is Disaster Message Frame B (Type = 0x2)

A. SEQ_ID (1 byte): unique number of multiplexed transmission frame

B. SEQ_SIZE (4 bytes): total number of multiplexed transmission frames

D. Value (191 bytes): one transmission frame (a bundle of transport header and transport packet containing emergency disaster information)

Here, the transmission header (4 bytes) including the emergency disaster information includes a transmission header indicator (1 bit), a disaster type code 1 (7 bits), a disaster type code 2 (8 bits), a disaster type code 3 ), And the transmission packet may be 187 bytes.

The CRC field is an error check field of the EDI frame, and the CRC error check target field is a Type field and a Data field.

The ETX field is a synchronization field indicating the end of the EDI frame, and its value can be set to 0x1AA1.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention as defined in the appended claims. It will be understood that the invention may be varied and varied without departing from the scope of the invention.

10: frame generation unit
20: Data output section

Claims

A frame generation unit for generating a disaster message including disaster broadcast information according to a structure of a disaster message frame; And
And a data output unit for outputting the transmission header and the transmission packet of the disaster message in an EDI frame according to an EDI (Emergency Service Data Interface) standard,
Wherein the layer of the disaster message frame comprises:
An Emergency Broadcasting Layer for delivering the disaster broadcast information;
An Emergency Broadcasting Service Layer to which metadata, which is descriptive information on the disaster broadcast information, is added;
A segment layer in which the metadata and the disaster broadcast information are divided into a predetermined size;
A service packet layer including a payload which is divided data according to the division, a packet header which is division and multiplexing information for the payload; And
And a transmission frame layer including the transmission header including the packet header and the payload and a transmission header indicator indicating whether or not the emergency disaster information is present. Message generating device.

The method according to claim 1,
If the transmission header indicator indicates that the emergency disaster information exists, the transmission header includes the transmission header indicator and the disaster type code,
When the transmission header indicator does not indicate that the emergency disaster information exists, the transmission header includes a disaster indicator field indicating whether a disaster occurred, a protection level field as a transmission related field, an SF field, and a service count field Disaster message generator.

3. The method of claim 2,
Wherein the disaster type code is calculated as a binary number by associating an alphabet code according to a disaster type with an ASCII code value.

3. The method of claim 2,
Wherein the EDI frame includes a Type field indicating a type of the EDI frame, and a Data field including the transport header and the transport packet,
Wherein the type of the EDI frame includes a first disaster message frame, a transmission status frame, and a second disaster message frame,
The Data field includes:
And a transmission header and a transmission packet when the transmission header indicator does not indicate that the emergency disaster information exists when the type of the EDI frame is the first disaster message frame,
When the type of the EDI frame is a transmission status frame,
And if the type of the EDI frame is a second disaster message frame, a transmission header and a transmission packet including the disaster type code are included.

The method according to claim 1,
The metadata includes a field indicating the length of the metadata, an indicator field indicating whether a service label exists, a T-DMB channel switching state, and a disaster service existence indication, a disaster service type field, and an indicator field value A service label field, a T-DMB channel switching field, and a disaster service field.

6. The method of claim 5,
Wherein the disaster service field includes a field indicating an earthquake occurrence time, a latitude and a longitude of an earthquake occurrence area,
The field indicating the time of occurrence of the earthquake includes a date represented by a binary number using a modified Julian date (MJD), a time represented by a binary number of 24 hours, and a minute expressed by a binary number of 60 minutes Message generating device.

The method according to claim 1,
Wherein the packet header includes a field indicating a service ID, a service type, a service priority, and a service packet number.