KR100910997B1 - Apparatus of transforming multimedia service format, system of providing multimedia service - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to a multimedia service format conversion apparatus and a multimedia service providing system using the same.

2. The technical problem to be solved by the invention

The present invention analyzes a multimedia service packet (for example, TPEG service packet, etc.), extracts the corresponding event information for each service, and converts the extracted event information into an XML file according to a document format of an XML (eXtensible Markup Language) file. An object of the present invention is to provide a multimedia service format converting device and a multimedia service providing system using the same, which can easily provide a multimedia service through an Internet browser.

3. Summary of Solution to Invention

The present invention provides a multimedia service format conversion apparatus, comprising: event extracting means for extracting corresponding event information for each service by analyzing a multimedia service packet; And XML file generating means for converting the extracted event information into an XML (eXtensible Markup Language) file.

4. Important uses of the invention

The present invention is used for converting a multimedia service format and providing a multimedia service using the same.

POI, News, TPEG, XML, DTD, ENTITY, xsl, PTI, RTM, Internet Browser, Terrestrial DMB, TPEG Service Packet, Multimedia Service Packet

Description

Apparatus of transforming multimedia service format, system of providing multimedia service

1 is a configuration diagram of an embodiment of a TPEG service providing system according to the present invention;

2 is a block diagram of an embodiment of an apparatus for converting a TPEG service format according to the present invention;

3 is a diagram illustrating an embodiment of a binary TPEG service packet separation process in the TPEG packet analyzer of FIG. 2 according to the present invention;

4 is a diagram illustrating an embodiment of a TPEG packet analysis process in the TPEG packet analyzer of FIG. 2 according to the present invention;

5 is a structural diagram of an embodiment of a TPEG frame in binary form according to FIG. 4 according to the present invention;

FIG. 6 is a diagram for explaining a process of dividing a service component frame of FIG. 5 by service according to the present invention; FIG.

7 is a diagram illustrating an embodiment of an XML file generation process applied to the present invention;

FIG. 8 is a diagram illustrating an embodiment of a POI event component and an XML file to be generated during the XML file generation process of FIG. 7 applied to the present invention; FIG.

FIG. 9 is a diagram illustrating an embodiment of a news event component and an XML file to be generated during the XML file generation process of FIG. 7 according to the present invention; FIG.

10 is a diagram illustrating an embodiment of a process of outputting an XML file applied to the present invention to an internet browser in association with an entity.

11 is a diagram illustrating an embodiment of a process of providing a TPEG service for news information through a TPEG service providing system according to the present invention;

12 is a diagram illustrating an embodiment of a process of providing a TPEG service for branch information through a TPEG service providing system according to the present invention.

* Explanation of symbols on the main parts of the drawing

101: packet receiver 102: TPEG service format converter

103: expression unit 20: event extraction unit

210: TPEG packet analyzer 211: TPEG packet deframer

212: TPEG frame error check unit 213: TPEG frame storage unit

220: TPEG frame decoding unit

221: service component frame extraction unit

222: service component frame analysis unit

223: service component frame decoding unit

230: XML file generation unit

The present invention relates to a multimedia service format converting apparatus and a multimedia service providing system using the same. More particularly, the present invention extracts and extracts corresponding event information for each service by analyzing a multimedia service packet (for example, a TPEG service packet). A multimedia service format converting apparatus and a multimedia service providing system using the same, by converting event information into an XML file according to a document format of an XML (eXtensible Markup Language) file, to easily provide a multimedia service through an Internet browser. It is about.

Application services related to traffic and travel information (TTI) are provided using TPEG messages. TPEG messages are produced in the form of byte-based streams and used to convey application information related to traffic and travel information (TTI) from the service provider's database to the end user's equipment. Binary-based TPEG services are used in multimedia broadcasting environments and were initially designed from the European Broadcasting Union's Broadcast Management Committee to develop new protocols for traffic and travel information. Based on this, the TPEG application service protocol is being developed and is being tested through DMB (Digital Multimedia Broadcasting). This TPEG application service protocol can be efficiently used in networks around 10kbps / s, such as DAB or Internet. Various application protocols have recently been developed and utilized.

Among the TPEG application service protocols, the news information application protocol provides the information to the end consumers to easily search for the information they want based on the various classification systems such as politics, economy, society, and entertainment from the latest news information collected from various media. The purpose. In the news information application protocol, news component data includes a message management container for managing news messages and a news event container for transmitting news information. do. The News Information Event Container is a "Classification" that identifies the nature of the news, "Time Information" associated with the news, "Article" to be actually sent, and "Authorship". "Includes. At this time, the news information component actually transmitted includes a text, an image, and a related link.

In addition, the POI application protocol not only overcomes the limitation of the diversity of the existing TTI services provided through the TPEG protocol, but also transmits point of interest information, which is a high value-added service, while maintaining compatibility with the existing TPEG protocol. Serviced POI service is designed to provide necessary information such as travel information, cultural information, public facilities, accommodation, medical care, reservation information, parking information, etc. for drivers, pedestrians or people who want to go to a specific destination. It became.

The POI message is a message management container that manages the POI message, an event container that transmits POI information, and items transmitted through the POI event container are "Classification" indicating the classification of the POI. "Description" indicating "," "Reservation Information" indicating reservation related information, "Time Information" indicating POI related time information, "Parking Information" item indicating parking lot information operated by POI and "Guide position" related position information Etc., and transmits the corresponding detail items.

The POI information is divided into 14 major categories by "Classification", and the text information about the point of interest is displayed along with image information such as building photographs, food menus, movie posters, and directions.

On the other hand, binary-type Binary-TPEG service includes Public Transport Information (PTI), Road Traffic Message (RTM), and Location Information (LOC) specified by the European Broadcasting Union (EBU). Only the specification that describes the XML file for is defined. According to the XML technical specification, a technical specification for converting a binary TPEG service packet into an XML file is not defined. Therefore, there is a problem that it is difficult to provide a TPEG service regardless of the user terminal using the conventional XML technical standards.

Furthermore, no XML technical standard for branch office information (POI) and news information (News) is defined among the TPEG services, and no technical standard for converting TPEG service packets into XML files is defined. Therefore, there is a problem that there is a limit to conveniently using the TPEG service in such a mobile terminal in consideration of the gradually spreading portable terminal market and the portable Internet market.

On the other hand, a document type in an XML document is used as a Document Type Definition (DTD) and a schema file, and the document expression is used as an eXtensible Style Language (XSL) and a cascading style sheets (CSS) file. That is, the XML document can be converted into an XML (eXtensible Markup Language) file simply by building the DTD, schema file, XSL, and CSS file in the terminal in advance, in charge of the document content related to the contents of the TPEG service. In conventional HTML (Hyper Text Markup Language) documents, there is a problem that a file is complicated and a file is not easily generated by putting together a document format, a document content, and a document representation in one file.

The present invention has been proposed to solve the above problem, and analyzes a multimedia service packet (for example, a TPEG service packet, etc.), extracts corresponding event information for each service, and extracts the extracted event information from an XML (eXtensible Markup Language) file. It is an object of the present invention to provide a multimedia service format converting apparatus and a multimedia service providing system using the same, which can easily provide a multimedia service through an internet browser by converting it into an XML file according to a document format.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. It will also be appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

In accordance with an aspect of the present invention, there is provided a multimedia service format converting apparatus comprising: event extracting means for extracting corresponding event information for each service by analyzing a multimedia service packet; And an XML file generating means for converting the extracted event information into an XML (eXtensible Markup Language) file.

On the other hand, the system of the present invention for achieving the above object, the multimedia service providing system, packet receiving means for receiving a multimedia service packet; A multimedia service format converting means for analyzing the received multimedia service packet to extract corresponding event information for each service and converting the extracted event information into an XML file; And output means for displaying the converted XML file.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, whereby those skilled in the art may easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of an embodiment of a TPEG service providing system according to the present invention.

The present invention relates to a multimedia service format conversion apparatus for receiving a multimedia service packet as well as a TPEG service packet and converting the multimedia service format, and a multimedia service providing system using the same.

As shown in FIG. 1, the TPEG service providing system according to the present invention includes a packet receiver 101, a TPEG service format conversion device 102, and a representation unit 103.

The packet receiver 101 receives a binary TPEG service packet (unit packet of transmission).

The TPEG service format converter 102 analyzes the TPEG service packet received by the packet receiver 101, extracts corresponding event information for each TPEG service, and converts the extracted event information into an XML file. That is, the TPEG service format conversion device 102 generates an XML file through error checking (error checking), decoding, and XML conversion. At this time, the TPEG service format converter 102 converts the binary TPEG service packet into an XML file using an ENTITY file (* .ent) and a DTD file (* .dtd).

In addition, the expression unit 103 outputs the XML file generated by the TPEG service format conversion device 102 through an Internet browser. At this time, the expression unit 103 outputs the XML file through an Internet browser using an XSL file (* .xsl). That is, the expression unit 103 provides the user with the TPEG service through an internet browser.

FIG. 2 is a diagram illustrating an embodiment of an apparatus for converting a TPEG service format according to the present invention, wherein the apparatus for converting a TPEG service format is included in the XML-based TPEG service providing terminal of FIG. 1.

As shown in FIG. 2, the TPEG service format conversion device 102 according to the present invention includes an event extractor 20 and an XML file generator 230. Here, the event extractor 20 includes a TPEG packet analyzer 210 and a TPEG frame decoder 220. In addition, the TPEG packet analyzer 210 includes a TPEG packet deframer 211, a TPEG frame error checker 212, and a TPEG frame storage 213. In addition, the TPEG frame decoder 220 includes a service component frame extractor 221, a service component frame analyzer 222, and a service component frame decoder 223.

Hereinafter, the components of the event extractor 20 will be described in detail.

The TPEG packet analyzer 210 receives a TPEG service packet and analyzes the received TPEG service packet to separate the information into TPEG frame units, which are information units. At this time, the TPEG packet analysis unit 210 performs an error check (CRC: Cycle Redundancy Check) on a frame basis as an information unit to extract a frame without an error. The components of the TPEG packet analyzer 210 are described in detail as follows.

In order to deframe the received TPEG service packet, the TPEG packet deframer 211 stores the TPEG packet in a memory and deframes the stored TPEG service packet into frames. That is, the TPEG packet deframer 211 separates the TPEG service packet into TPEG frame units. At this time, the separated TPEG frame is stored in a buffer.

Thereafter, the TPEG packet error checker 212 checks an error of the TPEG frame separated by the TPEG packet deframer 211 and stores a frame without errors in a buffer. At this time, the TPEG packet error check unit 212 deletes the TPEG frame in which the error occurred from the buffer.

The TPEG frame decoder 220 extracts a service component frame by decoding the TPEG frame separated by the TPEG packet analyzer 210 and divides the extracted service component frame for each service. The components of the TPEG frame decoding unit 220 will be described in detail as follows.

The service component frame extractor 221 extracts the service component frame by decoding the TPEG frame.

The service component frame analyzer 222 checks the field length using the field length in the service component frame extracted by the service component frame extractor 221, and determines the service component frame based on the identified field length. Separate. In addition, the service component frame analyzer 222 performs an error check (CRC check) for each service component frame using the CRC of the service component frame.

The service component frame analyzer 222 classifies which service corresponds to which service a component frame corresponds to by using a service component identifier of a service component frame in which an error does not occur, based on an error check result. That is, the service component frame analyzer 222 may convert the component frame into POI (Point of Interest, 0x03) component data, news information (News, 0x04) component data, PTI (Public Transport Information, 0x02) component data, or RTM (Road Transport). Message, 0x01) It is divided into any one component data among component data. Meanwhile, the service component frame analyzer 222 deletes (discards) a service component frame in which an error occurs in the error check result from the buffer.

The service component frame decoder 223 extracts the component data by decoding the service component frames classified for each TPEG service by the service component frame analyzer 222, and extracts the corresponding event information from the extracted component data. In this case, the service component frame decoding unit 223 analyzes a message identifier (MID) of the message management container from the extracted component data to determine whether the MID is a duplicate MID. In one example, the message identifier may be 2 bytes in size. In addition, the service component frame decoding unit 223 ascertains the property of the component when the MID is a duplicated MID as a result of checking the message identifier. In addition, the service component frame decoding unit 223 checks the version information of the message management container when the MID is a duplicate MID, and checks whether the upper version is a higher version and the property of the component in the upper version. The service component frame decoding unit 223 deletes the component data from the buffer when the version information is not the higher version as a result of the checking.

Looking at the XML file generator 230 in detail, the XML file generator 230 uses the event information extracted by the service component frame decoder 223 according to a document format defined in a document type definition (DTD). Convert to At this time, the XML file generator 230 checks whether the TPEG-LOC component is needed, and converts the event information into an XML document format using the TPEG-LOC component and DTD (Document Type Definition) when the TPEG-LOC component is required. Create an XML file. That is, the XML file generation unit 230 generates an XML file by converting the event container element contents into the contents of the corresponding XML file, respectively, under the control of the message management container. On the other hand, when the TPEG-LOC component is not needed, the XML file generator 230 converts the event information into an XML document format using a document type definition (DTD) and generates the XML file. The TPEG-LOC component contains location information related to the TPEG service.

3 is a diagram illustrating an embodiment of a binary TPEG service packet separation process in the TPEG packet analyzer of FIG. 2 according to the present invention.

As shown in FIG. 3, the TPEG service packet is divided into a sync word 301, a field length 302, a CRC 303, a frame type 304, and a service frame 305. The TPEG packet analyzer 210 analyzes such a TPEG service packet to obtain a field length 302, and separates the TPEG service packet into binary TPEG frame units for each field length 302. The CRC 303 is used in the error checking process, and the frame type 304 is used to determine the type of frame. The service frame 305 includes a service component frame.

4 is a diagram illustrating an embodiment of a TPEG packet analysis process in the TPEG packet analyzer of FIG. 2 according to the present invention.

The TPEG packet analyzer 210 receives a TPEG packet and performs an error check (CRC: Cycle Redundancy Check) according to a frame that is an information unit to distinguish a frame without an error.

Referring to the error checking process, the TPEG packet analyzer 210 receives the TPEG packet and stores the received TPEG packet in memory (402) for deframed.

The TPEG packet deframer 211 of the TPEG packet analyzer 210 divides the TPEG packets stored in the memory into frame units and divides them into TPEG frames (404), and the separated TPEG frames are stored in a buffer (406).

Thereafter, the TPEG packet error checker 212 of the TPEG packet analyzer 210 performs an error check by checking the CRC of the TPEG frame stored in step 406 (408), and there is no error in the check result 408. The frame is stored in the buffer (410).

Meanwhile, the TPEG frame in which the error occurred in step 408 is deleted from the buffer (412).

The frame stored in step 410 is a binary TPEG frame and is decoded by the TPEG frame decoding unit 220.

5 is a structural diagram of an embodiment of a TPEG frame in binary form in FIG. 4 according to the present invention.

As shown in FIG. 5, the binary TPEG frame in FIG. 4 includes a sync word, field length, CRC, frame type, and service frame 511. Here, the service frame 511 includes a service identifier A, a service identifier B, a service identifier C, an encryption indicator, and a service component multiplex 521. Here, the service component multiplex 521 includes a plurality of service component frames 531.

In particular, service component frame 531 includes service component identifier 541, field length 542, CRC 543, and component data 544, where component data 544 for each TPEG service is a message management container. 551, an event container 552, and a TPEG-LOC component 553.

FIG. 6 is a diagram for explaining a process of dividing a service component frame of FIG. 5 according to services according to an embodiment of the present invention.

As shown in FIG. 6, the service component frame extractor 221 of the TPEG frame decoder 220 extracts the service component frame 531 by decoding the TPEG frame of FIG. 5 (602).

The service component frame analyzer 222 confirms the overall field length using the field length 542 of the extracted service component frame (604), and based on the result of the check (604), the service component frame (531). ).

The service component frame analyzer 222 performs an error check (CRC check) for each service component frame using the CRC 543 (606).

The error check result 606 and the service component frame analyzer 222 classifies which service corresponds to which service the component frame 544 corresponds to using the service component identifier 541 of the service component frame in which no error occurs. (608 to 614). That is, the service component frame analyzer 222 may convert the component frame 544 into the POI (Point of Interest, 0x03) component data 608, news information (News, 0x04) component data 610, and public transport information (PTI). 0x02) component data 612 or component data of one of the RTM (Road Transport Message, 0x01) component data 614. Here, the PTI component data 612 and the RTM component data 614 necessarily include the TPEG-LOC component 553, and in particular, the POI component data 608 and the news information component data 610 may include the TPEG-LOC component ( 553) may be included as needed.

On the other hand, the error check result 606, the service component frame analyzer 222 deletes the service component frame in which the error occurs in the buffer (616).

7 is a diagram illustrating an embodiment of an XML file generation process applied to the present invention.

As illustrated in FIG. 7, the XML file generation process is divided into a validation process 70 for validating component data using a message management container and an XML file generation process 71 using an event container. Hereinafter, each process will be described in detail.

Referring to the process of validating the component data 70, the service component frame decoding unit 223 analyzes a message identifier (MID: 2 byte message identification) of the message management container 551 in component data classified for each service. In step 702, it is checked whether the MID is a duplicate MID.

As a result of the check 702, the service component frame decoding unit 223 detects the property of the component when the MID is a non-overlapping MID (704). On the other hand, if the MID is a duplicate MID, the service component frame decoding unit 223 checks the version information of the message management container 551 (706), and performs the process "704" if the higher version. Delete from the buffer (707).

The XML file generator 230 checks whether the TPEG-LOC component 553 is needed (708). As a result of the check 708, when the TPEG-LOC component 553 is needed, the XML file generator 230 uses the TPEG-LOC component 553 and the document type definition (DTD) to send the event component 552. The included event information is generated as an XML file (710). That is, the XML file generator 230 generates an XML file by filling the event container 552 element contents (event information) with the contents of the XML file under the control of the message management container 551.

Meanwhile, when the TPEG-LOC component 553 is not needed, the XML file generator 230 generates event information included in the event component 552 as an XML file using a document type definition (DTD) (712). ).

Meanwhile, in order to generate an XML file for news information and POI protocol applied to the present invention, an ENTITY value for each information is specified, and a DTD for news information and POI protocol is configured based on the ENTITY value. do. The XML files generated by the traffic-related information source at the sender are transmitted through transmission media such as DMB and the Internet after the DTD format is verified, and the receiver is referred to the screen by referring to the xsl file for screen composition. XML information is output. The message management container 551 of the TPEG service packet transmitted from the transmitting side includes a message identifier (MID), version information, and component attributes.

Hereinafter, the XML files for the POI service will be described.

FIG. 8 is a diagram illustrating an embodiment of a POI event component and an XML file to be generated during the XML file generation process of FIG. 7 according to the present invention.

As shown in FIG. 8, the POI event container 810 includes a TPEG-LOC 811, a Classification 812, a Description 813, a Reservation 814, and time information. (Time Information) 815 and Parking Information 816. Elements 811 through 815 of the POI event container 810 are converted into element contents 821 through 826 of the corresponding POI_XML generated file having a document format of a Definition Type Document (DTD) poiML.dtd (80), respectively. That is, TPEG-LOC 811, Classification 812, Description 813, Reservation 814, Time Information 815, Parking Information 816 denotes TPEG-LOC element content 811, classification element content 822, content description element content 823, reservation information element content 824, and time information element content, respectively, corresponding to the document format of the DTD. 825, the parking information element content 826 is converted.

The message management container 551 related to the branch office information (POI) service is represented as an attribute of a POI component (PoiComponent) of an XML file to be generated as shown in Table 1 below. Attributes of the attribute are represented by "#REQUIRED" and "#IMPLIED". That is, "#REQUIRED" is used when an attribute must be defined, and "#IMPLIED" is used when an attribute can be defined.

In the process of generating the XML file for the POI of FIG. 7, the message management container has information about the entire contents such as time and importance of the service rather than the contents. "Severity_factor" of [Table 1] indicating the importance of information refers to poi23_x of [Table 2], and "unverified_information" of [Table 1] indicating unidentified information refers to poi24_x of [Table 2] .

FIG. 8 is a diagram illustrating an embodiment of a POI event component and an XML file to be generated during the XML file generation process of FIG. 7 according to the present invention.

In [Table 1], the element (ELEMENT) of the POI components (PoiComponents) includes event information (point information event information) for the point information converted into an XML file. Here, the event information converted from the XML file generator 230 into an XML file includes a "Classification" element indicating classification information, a "Description" element indicating content description information, a "Reservation" element indicating reservation information, and time information. There is a "TimeInformation" element, a "ParkingInformation" element representing parking information, and a "TPEG_Loc" element representing location information. As shown in FIG. 8, the element of the POI component is converted into an XML file for POI having a Document Type Definition (DTD) format shown in Table 3 below.

As shown in FIG. 8, a DTD (poiML.dtd) for generating an XML file for the POI of [Table 3] and an entity (ENTITY, poiML.ent) for POI for output to the Internet browser of FIG. The relationship with is described below.

[Table 4] shows POI classification information (POI_Classification) in the DTD for generating the XML file for the POI. The classification information POI_Classification includes an "Classification_of_POI" element indicating a POI classification and a "sub_classification" element indicating a subclass. Here, the "sub_classification" element representing the subclass is intended to be classified in more detail.

Tables 5a to 5e show POI-ENTITY for POI classification. As shown in [Table 5a] to [Table 5e], the entity (ENTITY) for the POI classification includes a POI table (poi_table) for each category. That is, the POI table (poi_table 01) related to the POI classification includes an item-specific POI table (poi01_x) (for example, "unknown", "car", leisure / tourism, etc.). Here, the classification attribute (classification_of_poi) of [Table 4] is made possible by referring to poi01_x of [Table 5a] to [Table 5e], and the subclassing attribute (sub_classification) of [Table 4] is accordingly 6].

[Table 7] shows a DTD item for POI content description information (POI_Description), and attributes for POI content description information are shown in [Table 8]. Content description information about the POI has a language code (language_code) and a description type (type_of_description) as attributes. The language code refers to the POI table (poi_table 25) for the language code in [Table 8] above, and the description type (type_of_description) refers to the POI table (poi_table 17) for the description type in [Table 8] above. .

The content description information (Description) for the POI includes a description (str_Description) element (ELEMENT) for describing the point information service in the form of a string, and an image data (ImageData) element for the linked image file. POI description information (POI_Description) information in the language (poi25_x) in the [Table 8] shows the description (description) of the current message in the form of a string (str_Description element) of the [Table 7]. For the content of the string type (type_of_description attribute), refer to poi17_x of the above [Table 8]. In addition, information on the image file associated with the description (Description element) is shown in "type_of_graphic_file" in Table 8 above, and the image file name is shown in "ImageData" in Table 8 above.

[Table 9] shows a DTD item for POI reservation information (POI_Reservation), and attributes for POI reservation information are shown in [Table 10]. The POI reservation information indicates reservation status information (status_of_POI) with reference to POI table 18 (poi18_x) of the above [Table 10]. The reservation description element is represented by POI table 25 (poi25_x) relating to the language and POI table 27 (poi27_x) relating to the description type (type_of_description) attribute in [Table 10]. In other words, the reservation information (Reservation) has a reservation status (status_of_POI) as an attribute, and includes a reservation description element having a language code (language_code) and a kind of reservation detailed information as an attribute.

POI time information in Table 11 indicates time information related to POI. The time information (TimeInformation) has an expected schedule (scheduled_or_predicted) as an attribute, and includes a predetermined time instance element, a type of service day (ServiceDayType) element, a time table type (TimeTableType) element.

POI table 20 (poi20_x) of Table 12 has a time_type of time of Table 11 as an attribute, and a TimeIncludingLocalOffset element including a local offset of Table 11 as an attribute. Indicates the type of time. POI table 21 (poi21_x) of [Table 12] has a service day type (service_day_type) of [Table 11] as an attribute, and time information of time (TimeIncludingLocalOffset) including local offset of [Table 11]. Assist. The POI table 22 (poi22_x) of Table 12 indicates the type of message time information as a time table type (TimeTableType) attribute of Table 11 above.

Table 13 shows a DTD related to POI parking information. POI parking information has a parking space (ParkingSpace), the parking cost (RateInformation) as an element. The ParkingSpace element represents the number of parkings available for the parking lot. The RateInformation element represents the parking cost in the case of paid parking. In other words, the parking information includes a parking space element and a rate information element, and the included charge information element has a currency type (currency_type) as an attribute, a basic rate element, and a parking time. It includes a (TimeLimit) element and an AdditionalRate element.

With reference to POI table 16 (poi16_x) shown in [Table 14], the parking lot type ("type_of_parking_place" attribute of [Table 13]) appears. The type of payment currency (Currency_type) is determined with reference to POI table 16 (poi26_x) of [Table 14], and the basic parking rate (BasicRate), parking time (TimeLimit), and additional cost (AdditionalRate) of [Table 13]. Appears.

POI_TPEG_Loc represents location information of POI. If location information is needed, a value can be specified by the contents of the TPEG-Loc element shown in [Table 15].

Hereinafter, the XML files for the news information service will be described.

FIG. 9 is a diagram illustrating an embodiment of a news event component and an XML file to be generated during the XML file generation process of FIG. 7 according to the present invention.

As illustrated in FIG. 9, the news information event container 910 includes event information (news information event information) about news information converted into an XML file. Here, the news information event information converted from the XML file generator 230 into an XML file includes classification information (911), time information (time information) 912 of the article, and article information (Article). 913, Authorship information 914. The classification information 911, the time information 912, the article information 913, and the authoring information 914 which are the elements 911 to 914 of the news information event container 910 correspond to the document format of the DTD 80, respectively. The classification element contents 921, the time information element contents 922, the article information element contents 923, and the authoring information element contents 924 are converted.

The TPEG frame of FIG. 5 determines that the TPEG frame is a news information service by using 1 byte (0x04) of a service component frame identifier in a service component multiplex. do. If it is determined as the news information service, an XML file is generated by filling the XML file content of the news information with the contents of an event container element under the control of the message management container of FIG. 4.

The message management container of FIG. 6 is represented as a NewsComponent component of the XML file for news information to be generated as shown in Table 16 below. Attributes of the attribute are represented by "#REQUIRED" and "#IMPLIED".

[Table 16] has information such as the time and importance of the service when the XML file for news information is generated. "Severity_factor" of [Table 16] indicating the importance of information refers to news information table 3 (News03_x) of [Table 17], and "unverified_information" of [Table 16] indicating unidentified information is [Table 17] Refer to news information table 4 (news04_x).

The element of Table 16 includes "Classification" representing a classification, "TimeInformation" representing time information, "Article" representing actual article information, and "Authorship" representing authoring information. As shown in FIG. 9, an XML file for news information having a DTD (Document Type Definition) format shown in Table 18 below is provided.

As shown in FIG. 9, a DTD (newsML.dtd) for generating an XML file for the news information of [Table 18] and an entity (ENTITY, newsML. ent) will be described below.

[Table 19] shows a classification (news_Classification) among DTDs for generating an XML file for news information. Classification includes " type_of_news " representing a news type, " sub_type_of news " representing a subclass according to a classification, and " status_of_news " representing a news status. The subclass contains "sub_type_of news" to indicate a more detailed classification. In other words, the classification information has a type of news type_of_news, a subtype of news for each type of news, sub_type_of_news, and a status of news (status_of_news).

Tables 20a to 20c show the news-ENTITY for news information classification. The classification (type_of_news attribute of [Table 19]) is made possible by referring to news information table 5 (news05_x) of [Table 20a] to [Table 20c], and the sub_classification of [Table 19]. Is shown in Table 21 below. In addition, the news information reporting status (status_of_news in [Table 19]) refers to the news information table 1 (news01_x) in [Table 20a] to [Table 20c].

Time information about news information (news_Time Information) has the time information the news was created. That is, the article occurrence time information (TimeInformation) displays the time information in which the news was created in the form of a string. Time information is indicated by the "TimeInformation" element of Table 22.

Article information has a language code as an attribute and includes an article title (TitleOfArticle) element, an article content (RealArticle) element, and an article component element. The article component includes an ImageData element related to the news and a RelatedLink element.

"Article" indicating the article information of the news information has the language information of the article ("language_code" in [Table 23]) with reference to the news information table 15 (news15_x) in the above-mentioned [Table 24]. Article information includes the article title (TitleOfArticle element) and article content (RealArticle element) of the above [Table 23] using language information. You can extend it to include an image of the article (ImageData), and add details needed for the article in conjunction with information such as the actual Internet article (OriginalTextWeb), other related articles (RelatedArticle), and location information (TPEG_Loc).

Author information (news_Authorship) represents copyright information of a news information article. With reference to the news information table 2 (news02_x) of [Table 26], the kind (authorship_type) of [Table 25] is represented as an attribute, and the author is an element content of the authorship information (AuthorshipInformation) of [Table 25]. appear. That is, authorship related information (Authorship) includes a copyright information (AuthorshipInformation) element, the included copyright information (AuthorshipInformation) element has a copyright type (Authorship_type) as an attribute.

FIG. 10 is a diagram illustrating an embodiment of a process of outputting an XML file applied to the present invention to an internet browser in association with an entity.

As shown in FIG. 10, the XML file 1010 has a form for outputting to the browser with reference to the entity file for POI and news information from the time of generation. For example, the XML file for POI has an entity to be referenced (ENTITY, &poi01_1;). In addition, the XML file for news information has an entity (ENTITY, &news01_1;) to be referenced.

The process of outputting to the internet browser is performed by the user selecting the XML file (generated from the contents of the TPEG service information) (1002), and outputting to the internet browser. Referring to the entity 1020, the entity 1010 is referred to. Replace with a word or sentence in). For example, the entity file 1020 stores entity values such as! ENTITY news01_1 "breaking news" through the DTD, and entity values such as! ENTITY poi01_1 "car". At this time, the process of outputting to the Internet browser indicates the XML file 1010 to the browser as "breaking news", "car", etc. included in the entity file 1020 according to the user's selection.

On the other hand, XML files that have not been selected by the user still wait with an entity to refer to as a file in the storage device.

11 is a diagram illustrating an embodiment of a process of providing a TPEG service for news information through a TPEG service providing system according to the present invention.

As shown in FIG. 11, the XML-based TPEG service providing terminal according to the present invention of FIG. 1 provides a main screen 1101 for selecting a news information service to a user through an internet browser included in the terminal.

When the user selects the 'News' menu 111 displayed in the square area (1111), the XML-based TPEG service providing terminal classifies and displays the news information service according to the classification of the news information service (1102). For example, the classification of news information service includes a 'social' menu and a 'politics' menu 112. At the top of the browser on the screen of "1102", there is an upper link to the screen of "1101".

Here, the 'politics' menu 112 is linked to the sub_classification of the screen "1103", and includes a menu that is directly moved to the news information service contents of the screen "1104". When the user selects the 'politics' menu 112 displayed in the square area (1112), the XML-based TPEG service providing terminal displays the small category of the 'politics' menu 112 on the Internet browser (1103).

In addition, when the user selects the item [[Top News] anti-diplomacy, "European lawmakers ..." "113 on the screen" 1103 "(1113), the terminal of the XML-based TPEG service providing terminal is" 1104 ". As indicated on the screen, the actual news information service content is browsed to the user (1104). At the top of the browser of the screen "1104", the upper link is linked to the screen "1103".

12 is a diagram illustrating an embodiment of a process of providing a TPEG service for branch information through a TPEG service providing system according to the present invention.

As shown in FIG. 12, the XML-based TPEG service providing terminal according to the present invention of FIG. 1 provides a main screen 1101 for selecting a branch information service to a user through an internet browser included in the terminal.

When the user selects the 'POI' menu 121 displayed in the square area (1211), the XML-based TPEG service providing terminal distinguishes and displays the branch information service according to the classification of the branch information service (1202). For example, the classification of the branch information service includes a 'car' menu and a 'leisure / tourist' menu 122. At the top of the browser on screen "1202", there is an upper link to screen "1201".

Here, the 'car' menu 122 is linked to a sub_classification of the "1203" screen, and includes a menu that is directly moved to the point information service contents of the "1204" screen. When the user selects the 'leisure / tourist' menu 122 displayed in the square area (1212), the XML-based TPEG service providing terminal displays the sub-categories of the 'leisure / tourist' menu 112 in the Internet browser (1203). ).

In addition, when the user selects the item [123] [Amusement Park] Daejeon Zoo (123) on the screen "1203" (1213), the XML-based TPEG service providing terminal displays the actual news information service content as shown on the screen "1204". Browse to user (1204). At the top of the browser on screen "1204", there is an upper link to screen "1203".

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. Since this process can be easily implemented by those skilled in the art will not be described in more detail.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

As described above, the present invention analyzes a multimedia service packet (eg, a TPEG service packet), extracts corresponding event information for each service, and extracts the extracted event information according to a document format of an XML (eXtensible Markup Language) file. In this case, the TPEG service can be easily provided through an Internet browser. For example, the present invention can easily provide the TPEG service through the Internet browser of the terminal independently in the terrestrial DMB currently being serviced, the mobile Internet (WIBRO, HSDPA), DVB-H, media flow and the Internet environment to be universally independent. It has the effect of making it possible.

In addition, the present invention converts the TPEG service packet received in binary form into an XML file, thereby receiving a low capacity binary TPEG service packet, thereby reducing the load on communication, increasing compatibility between wireless service terminals, and being easy in a portable Internet environment. It is effective to provide TPEG service.

Claims (17)

delete delete In the multimedia service format conversion apparatus, Event extraction means for analyzing the received binary type multimedia service packet and extracting corresponding event information for each service; And XML file generating means for converting the extracted event information into an XML (eXtensible Markup Language) file Including, The multimedia service packet is Transport Protocol Experts Group (TPEG) service packet. The event extraction means TPEG packet analyzing means for analyzing binary TPEG service packets and separating them into TPEG frame units; And TPEG frame decoding means for extracting a service component frame from the separated TPEG frame for each TPEG service and extracting corresponding event information from the separated service component frame Multimedia service format conversion device comprising a. The method of claim 3, wherein The XML file generating means, And converting the extracted event information into an XML file according to a document format defined in a document type definition (DTD). The method of claim 4, wherein The event information converted into the XML file by the XML file generating means is Device for converting a multimedia service format comprising event information for point information (POI) and event information for news information (news). The method of claim 5, wherein Event information for the point information, Multimedia service format conversion apparatus comprising location information (TPEG-LOC), classification information (Classification), content description information (Description), reservation information (Reservation), time information (TimeInformation), parking information (ParkingInformation) . The method of claim 6, The classification information (Classification), A multimedia service format conversion device characterized by having a classification (classification_of_POI) and a sub_classification of each of the classifications as attributes. The method of claim 6, The content description information (Description), And a point information service description (str_Description) described in a string form, and image data (ImageData) for the linked image file. The method of claim 6, The reservation information (Reservation), And a reservation status (status_of_POI), a language code (language_code), and a reservation detailed information type (type_of_description). The method of claim 6, The time information (TimeInformation), An apparatus for converting a multimedia service format comprising an expected schedule (scheduled_or_predicted), a time type (Time_type), a service day type (ServiceDayType), and a time table type (TimeTableType). The method of claim 6, The parking information (ParkingInformation), Parking space (ParkingSpace) information, parking type (Parking_place_type) and rate information (RateInformation), including the charge information (currency_type), basic rate (BasicRate), parking time (TimeLimit), additional rate (AdditionalRate) Multimedia service format conversion apparatus, characterized in that classified. The method of claim 5 Event information for the news information, Device for converting a multimedia service format, characterized in that it includes classification information (Classification), article occurrence time information (TimeInformation), article information (Article), authoring related information (Authorship). The method of claim 12, The classification information (Classification), And a news type (type_of_news), a subtype (sub_type_of_news), and a news status (status_of_news) for each of the types of news. The method of claim 12, The article information (Article), It includes a language code, a title title (TitleOfArticle), an article content (RealArticle), an article component (ArticleComponent), characterized in that the article component is classified into image data (ImageData), related links (RelatedLink) related to the news Multimedia service format conversion device. The method of claim 12, Authorization information (Authorship), And copyright information (AuthorshipInformation), wherein the copyright information (AuthorshipInformation) has a copyright type (Authorship_type) as an attribute. delete delete

Images