KR100682851B1 - Data for contents description in data broadcasting service and apparatus for providing contents using the same - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to data for content description in a data broadcasting service and a content providing device using the same.

2. The technical problem to be solved by the invention

The present invention, by defining data describing the data broadcast content that can provide a voice and graphical user interface, by using the content description data and the content description for the broadcast receiver of the mobile environment to easily use the voice and graphical user interface at the same time The purpose is to provide a content providing device.

3. Summary of Solution to Invention

The present invention provides a content providing apparatus using content description data for content description in a data broadcasting service, comprising: content description data generating means for generating the content description data; Content authoring means for authoring content to be broadcasted using the content description data; User interface providing means for providing a voice and graphical user interface of a broadcast service; And content conversion means for converting the authored content into a form suitable for broadcasting to various receiving terminals.

4. Important uses of the invention

The present invention is used for data broadcasting service providing system.

Description

Data for content description in data broadcasting service and apparatus for providing content using the same {Data for Contents Description in Multimedia Broadcast Service and Apparatus for Contents Providing using it}             

1 is a configuration diagram of an embodiment of a content providing device using content description data according to the present invention;

2 is a structural diagram of an embodiment of content description data according to the present invention;

3 is a structure diagram of a document type declaration (DTD) schema of content description data describing news service content according to an embodiment of the present invention;

4 is a diagram illustrating a user interface according to an exemplary embodiment of the present invention.

* Description of the main parts of the drawings *

11: content description data generating means 12: content authoring means

13: UI providing means 14: Content conversion / transmission means

The present invention relates to data for content description in a data broadcasting service and a content providing device using the same. More specifically, content description data for broadcasting content technology supporting voice and graphic user interfaces in a digital broadcasting service and using the same It relates to a content providing device.

In the digital broadcasting system, various types of multimedia services such as graphics, sound, and data can be provided. In the conventional web-based data broadcasting, only a graphic (screen) user interface is supported, especially in an environment where a receiver is moving. There is a problem.

In order to support the voice and graphic user interfaces by overcoming the limitations of the conventional graphic data broadcasting, the following points are required.

First, interworking is required in the content production stage and the playback and reception stages, and a content description language that is a prerequisite for such a linkage mechanism, that is, definition of content description data and implementation of a content providing system using the same are required.

Second, the content description data should be able to be converted into a document capable of smoothly supporting voice and graphic interfaces in various receiving environments, and is required to be based on XML for such free conversion.

Third, the content description data is required to support a variety of data broadcasting services for the user's convenience.

Fourth, the content description data is required to support the bidirectional interworking method considering the next generation data broadcasting service.

The present invention has been proposed to meet the above demands, and by defining data describing data broadcast contents capable of providing a voice and graphic user interface, a broadcast receiver in a mobile environment can easily use the voice and graphic user interface simultaneously. Its purpose is to provide content description data and a content providing device using the same.

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. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

According to an aspect of the present invention, there is provided a content providing apparatus using content description data for content description in a data broadcasting service, comprising: content description data generating means for generating the content description data; Content authoring means for authoring content to be broadcast using the content description data; User interface providing means for providing a voice and graphical user interface of a broadcast service; And content conversion means for converting the authored content into a form suitable for broadcasting to various receiving terminals.

The present invention also provides a content description data for content description in a data broadcasting service, comprising: a metadata element for describing meta information of a document commonly required for data broadcasting; And a service content element for describing data of each service suitable for a broadcasting environment.

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 content providing device using content description data according to the present invention.

As shown in FIG. 1, the apparatus for providing content using the content description data according to the present invention includes: content description data generating means 11 for generating content description data describing content according to a service suitable for mobile data broadcasting; Content authoring means (12) for authoring content to be broadcast using the content description data; a user interface (UI) providing means (13) for providing a voice and graphic user interface of a service to be broadcast; and the authored content The user interface provided from the UI (User Interface) providing means 13 is converted into a type of voice XML (VoiceXML), X + V, HTML, voice EPGXML (VoiceEPGXML), SALT, or the like so as to be broadcast to various receiving terminals. And content converting / transmitting means (14) for transmitting to the broadcast listener via the.

2 is a structural diagram of an embodiment of content description data according to the present invention.

As shown in FIG. 2, the content description data for supporting a voice and a graphic user interface in a digital broadcasting service in a mobile environment according to an exemplary embodiment of the present invention includes meta information of a document commonly required for mobile data broadcasting. Head (111) element, which is the expressed metadata element, Body (112) element, which is a service content element representing data of each service suitable for data broadcasting in a mobile environment, and advertisement content data irrespective of the service content. It includes an Advertisement 113 element that is an advertisement content element.

Here, the head 111 element supports free metadata field expansion of the user.

In addition, the body 112 element may include a news body for news service content, a weather body for weather service content, and a traffic information body for traffic information related content, as shown. , LocalInfoBody for local information, EducationBody for education, QuizBody for quizzes, StockBody for securities, and AdvertiseBody for ads. In this case, a unique body element may be selected according to each service.

For example, a news body, a weather body, and a local information body among the unique body elements according to the above services will be described. The news body according to the present invention supports keyword search through graphic and voice input, and is urgent by assigning priorities. It supports the function of displaying from the news, weather body uses local zip code to classify each region, and the body of the body supports location-based services in connection with GPS information.

3 is a structure diagram of a document type declaration (DTD) schema of content description data describing news service content according to an exemplary embodiment of the present invention.

As shown in FIG. 3, the head 111 element supports production information such as creator, production date, and copyright, keywords that are index words for searching, content rating information, and user's free metadata field expansion. Contains custom data.

The NewsBody element is optionally a NewsBody 112 and consists of news items that support the narration of the headline and voice user interface, which represent the headings to be shown in this visual key news as shown. VoiceStream for the user, and keywords (Keywords) for recognizing the index keyword of the user during the narration, and the like.

The above-described content description data is based on XML for flexible conversion into a target language suitable for various broadcast receiving terminals, and is defined through DTD (Document Type Declaration) and XML Schema (Schema).

The DTD document of the content description data describing the news service content is as follows.

<? xml version = "1.0" encoding = "UTF-8"?>

<! ELEMENT NewsBody (NewsItem)>

<! ATTLIST NewsBody

numOfItems CDATA #REQUIRED>

<!-============================================== =================->

<!-News Item ELEMENTS->

<!-============================================== ================->

<! ELEMENT NewsItem (NewsInfo, KeyWords, TextStream, Contents)>

<!-============================================== =================->

<!-News info ELEMENTS->

<!-============================================== =================->

<! ELEMENT NewsInfo (HeadLine, RealtedInfo?)>

<! ATTLIST NewsInfo

source CDATA #REQUIRED

createDate CDATA #REQUIRED

creator CDATA #REQUIRED

version CDATA #REQUIRED

previousVersion CDATA #REQUIRED

priority (1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 0) #REQUIRED

type (report | column | special | focus) #REQUIRED

category (society | politics | economy | foreign | sports | entertain | digital) #REQUIRED>

<! ELEMENT HeadLine (#PCDATA)>

<! ATTLIST HeadLine

topic CDATA #REQUIRED

topicid CDATA #REQUIRED

headLineid CDATA #REQUIRED

>

<! ELEMENT RelatedInfo (Ref ?, BcRef ?, AdRef?)>

<!-++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++->

<!-News KeyWords Element->

<!-++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++->

<! ELEMENT KeyWords (#PCDATA)>

In addition, the XML schema of the content description data describing the news service content is as follows.

<? xml version = "1.0" encoding = "UTF-8"?>

<! DOCTYPE DMBML SYSTEM ". \ DTD \ dmbml.dtd">

<DMBML id = "" serviceType = "news">

 <Head>

   <ProductionInfo>

   <Producer />

   <ProductionDate />

  </ ProductionInfo>

  <Keywords />

  <ContentsRate />

 </ Head>

 <NewsBody numOfItems = "2">

  <NewsItem>

   <NewsInfo source = "" createDate = "" creator = "" version = "" previousVersion = "" priority = "0" type = "column" category = "digital">

   <HeadLine topic = "" topicid = "" headLineid = "">

</ HeadLine>

   </ NewsInfo>

   <KeyWords>

</ KeyWords>

   <TextStream> </ TextStream>

   <Contents>

   </ Contents>

     </ NewsItem>

   <NewsItem>

  <NewsInfo source = "YTN" createDate = "20040626" creator = "종주" version = "2004062603345" previousVersion = "2004062603330" priority = "5" type = "report" category = "foreign">

   <HeadLine topic = "Susk of Dragons" topicid = "12" headLineid = "1002"> Who shot Dragons? </ HeadLine>

<RelatedInfo>

</ RelatedInfo>

  </ NewsInfo>

  <KeyWords> Kim Sun-il, Iraq dispatch, Bush </ KeyWords>

  <TextStream> Kim Sun Il's body was taken to his homeland where he was so sad to return. The son of a cold carcass, the heart of the bereaved and the citizens, was pushed by tears of mourning. I am reporter Park Sung-hoon of Busan Broadcasting. </ TextStream>

      <Contents>

        <Ref src = "" type = "">

         </ Ref>

        <BcRef type = "" contact = "">

        <Ref src = "" type = "">

        </ Ref>

      <AdRef src = "">

    <Ref src = "" type = "">

   </ Ref>

  </ AdRef>

</ BcRef>

<AdRef src = "">

<Ref src = "" type = ""> </ Ref>

</ AdRef>

</ Contents>

</ NewsItem>

</ NewsBody>

</ DMBML>

4 is a view showing a user interface according to an embodiment of the present invention, showing an embodiment of the user interface of the weather information service.

Selecting each region interface shown in the drawing provides detailed information for each region.

XSLT template document which is in charge of converting authoring content for this is as follows.

<? xml version = "1.0" encoding = "UTF-8"?>

<xsl: stylesheetversion = "1.0" xmlns: xsl = "http://www.w3.org/1999/XSL/Transform">

 <xsl: output method = "xml" version = "1.0" indent = "yes" />

 <!-DMBML2MXML for weather information: Main MXML->

<xsl: paramname = "totalNumber" select = "count (// CurrentWeather / TotalArea / WideAreas / WideArea)" />

<xsl: template match = "/">

  <xsl: text disable-output-escaping = "yes">

  &lt;! DOCTYPE html PUBLIC "-// W3C // DTD XHTML + Voice1.0 / EN" "xhtml + voice.dtd" &gt;

  </ xsl: text>

   <html xmlns = "www.w3.org/1999/xhtml"

     xmlns: ev = "http://www.w3.org/2001/xml-events"

     xmlns: vxml = "http://www.w3.org/2001/vxml"

     xmlns: xv = "http://www.voicexml.org/2002/xhtml+voice">

  <head>

  <title> Weather </ title>

  <script type = "text / javascript">

   var docIsDoneLoading = false;

   var varListenSelect = undefined;

   var flagFirstTime = true;

  </ script>

  <script type = "text / javascript" id = "handleListenSelect">

   if (docIsDoneLoading) {

    if (varListenSelect == undefined) document.getElementById ('id_Listen'). focus ();

    else if (varListenSelect == "exit") document.getElementById ('id_DMBExit'). click ();

    else if (varListenSelect == "today") document.getElementById ('id_Today'). click ();

    else if (varListenSelect == "tomorrow") document.getElementById ('id_Tomorrow'). click ();

    else if (varListenSelect == "week") document.getElementById ('id_Week'). click ();

    else if (varListenSelect == "help") document.getElementById ('id_Help'). click ();

    else if (varListenSelect == "listen") document.getElementById ('id_Listen'). click ()

    else if (varListenSelect == "stop") document.getElementById ('id_Stop'). click ()

    else if (varListenSelect == "top menu") document.getElementById ('id_TopMenu'). click ();

    varListenSelect = undefined;

    document.getElementById ('id_Listen'). blur ();

   }

  </ script>

  <script type = "text / javascript">

   docIsDoneLoading = true;

  </ script>

  <vxml: form id = "voiceWeatherTop">

   <vxml: field name = "voiceWeatherTopSelect">

    <vxml: prompt>

      We have current weather, today forecast, tomorrow forecast and week forecast.

      You can say today, tomorrow, week, listen, exit, topmenu, help. What kind of service do you want?

    </ vxml: prompt>

    <vxml: grammar>

      <xsl: text disable-output-escaping = "yes">

      &lt;! [CDATA [

      #JSGF V1.0;

      grammar service;

      &lt; universal &gt; = exit | top menu;

      public &lt; service &gt; = &lt; universal &gt; | stop | help | today | tomorrow | week | listen;]] &gt;

      </ xsl: text>

     </ vxml: grammar>

    <vxml: filled>

     <vxml: assign name = "varListenSelect" expr = "voiceWeatherTopSelect" />

    </ vxml: filled>

   </ vxml: field>

  </ vxml: form>

  <vxml: form id = "voiceUrgentItems">

   <vxml: block>

   <xsl: call-template name = "forVoiceStream" />

  </ vxml: block>

   <vxml: field name = "voiceWeatherTopMenu">

   <vxml: grammar>

   <xsl: text disable-output-escaping = "yes">

      &lt;! [CDATA [

     #JSGF V1.0;

     grammar service;

     &lt; universal &gt; = exit | top menu;

     public &lt; service &gt; = &lt; universal &gt; | stop | help | today | tomorrow | week | listen;]] &gt;

    </ xsl: text>

    </ vxml: grammar>

    <vxml: filled>

     <vxml: assign name = "varListenSelect" expr = "voiceWeatherTopMenu" />

    </ vxml: filled>

   </ vxml: field>

  </ vxml: form>

  <vxml: form id = "voiceWeatherStop">

    <vxml: field name = "voiceSelect">

     <vxml: grammar>

      <xsl: text disable-output-escaping = "yes">

      &lt;! [CDATA [

      #JSGF V1.0;

      grammar service;

      &lt; universal &gt; = exit | top menu;

      public &lt; service &gt; = &lt; universal &gt; | stop | help | today | tomorrow | week | listen;

      ]] &gt;

      </ xsl: text>

     </ vxml: grammar>

     <vxml: filled>

     <vxml: assign name = "varListenSelect" expr = "voiceSelect" />

    </ vxml: filled>

   </ vxml: field>

  </ vxml: form>

  </ head>

 <body onload = "document.getElementById ('id_Listen'). focus ()">

  <table width = "490" height = "482" border = "1">

  <tr>

   <td height = "38">

    <strong> Weather </ strong>

   </ td>

  </ tr>

  <tr>

   <td height = "294">

   <xsl: call-template name = "forTextStream" />

   <xsl: call-template name = "forRegion" />

       <p>

     <input name = "var_Listen" id = "id_Listen" type = "submit" value = "Listen" />

    <ev: listener ev: event = "click" ev: handler = "# voiceUrgentItems" ev: observer = "id_Listen" ev: propagate = "stop" />

     <ev: listener ev: event = "focus" ev: handler = "# voiceWeatherTop" ev: observer = "id_Listen" ev: propagate = "stop" />

     <ev: listener ev: event = "vxmldone" ev: handler = "# handleListenSelect" ev: observer = "id_Listen" ev: propagate = "stop" />

     <input name = "var_Stop" id = "id_Stop" type = "submit" value = "Stop" />

     <ev: listener ev: event = "click" ev: handler = "# voiceWeatherStop" ev: observer = "id_Stop" ev: propagate = "stop" />

     <ev: listener ev: event = "vxmldone" ev: handler = "# handleListenSelect" ev: observer = "id_Stop" ev: propagate = "stop" />

    </ p>

   </ td>

  </ tr>

  <tr>

   <td height = "57" align = "center">

<a href="weatherToday.mxml"> <input name = "var_Today" type = "submit" id = "id_Today" value = "Today" /> </a>

   <a href="weatherTomorrow.mxml"> <input name = "var_Tomorrow" type = "submit" id = "id_Tomorrow" value = "Tomorrow" /> </a>

   <a href="weatherWeek.mxml"> <input name = "var_Week" type = "submit" id = "id_Week" value = "Week" /> </a>

   </ td>

  </ tr>

  <tr>

   <td align = "center">

     <a href="main.mxml" id="returnMain"> <input name = "var_TopMenu" type = "submit" id = "id_TopMenu" value = "Top Menu" /> </a>

     <a href="dmbExit.mxml"> <input name = "var_DMBExit" type = "submit" id = "id_DMBExit" value = "Exit" /> </a>

     <a href="WeatherHelp.mxml" id="goHelp"> <input name = "var_Help" type = "submit" id = "id_Help" value = "Help" /> </a>

   </ td>

  </ tr>

 </ table>

</ body>

 <ev: listener ev: event = "vxmldone" ev: handler = "# handleListenSelect" ev: observer = "id_Event" ev: propagate = "stop" />

</ html>

</ xsl: template>

 <xsl: template name = "forTextStream">

 <xsl: for-each select = "// CurrentWeather">

    <xsl: text disable-output-escaping = "yes"> &lt; strong &gt;

    [Current Weather] &lt; / strong &gt; </ xsl: text> <xsl: value-of select = "TotalArea / ReportAnnotation" />

     <xsl: text disable-output-escaping = "yes"> &lt; br / &gt; </ xsl: text>

    <xsl: text disable-output-escaping = "yes"> &lt; strong &gt;

    [Warning / Advisory] &lt; / strong &gt; </ xsl: text> <xsl: value-of select = "../ WeatherMessages / WeatherMessage" />

    <xsl: text disable-output-escaping = "yes"> &lt; br / &gt; </ xsl: text>

    <xsl: text disable-output-escaping = "yes"> &lt; strong &gt;

    [KwangYeokSi] &lt; / strong &gt; </ xsl: text>

   </ xsl: for-each>

 </ xsl: template>

  <xsl: template name = "forVoiceStream">

  <xsl: for-each select = "// CurrentWeather">

   <xsl: text disable-output-escaping = "yes"> &lt; vxml: prompt &gt; </ xsl: text>

    <xsl: value-of select = "TotalArea / ReportAnnotation" />

    <xsl: value-of select = "// WeatherMessage" />

    <xsl: call-template name = "forRegionVoiceStream" />

   <xsl: text disable-output-escaping = "yes"> &lt; / vxml: prompt &gt; </ xsl: text>

  </ xsl: for-each>

 </ xsl: template>

 <xsl: template name = "forRegion">

 <xsl: for-each select = "// CurrentWeather / TotalArea / WideAreas / WideArea">

  <xsl: if test = "@ wideAreaCode = 01">

   <xsl: variable name = "CodeName" select = "'Seoul'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 02">

   <xsl: variable name = "CodeName" select = "'Youngseo'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 03">

   <xsl: variable name = "CodeName" select = "'Youngdong'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 04">

   <xsl: variable name = "CodeName" select = "'Chungbuk'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 05">

   <xsl: variable name = "CodeName" select = "'Chunnam'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 06">

   <xsl: variable name = "CodeName" select = "'Kyoungbuk'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 07">

   <xsl: variable name = "CodeName" select = "'Kyoungnam'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 08">

   <xsl: variable name = "CodeName" select = "'Jeonnam'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 09">

   <xsl: variable name = "CodeName" select = "'Jeonbuk'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 10">

   <xsl: variable name = "CodeName" select = "'Jejudo'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 11">

   <xsl: variable name = "CodeName" select = "'West ocean'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 12">

   <xsl: variable name = "CodeName" select = "'East ocean'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 13">

   <xsl: variable name = "CodeName" select = "'South ocean'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: if test = "@ wideAreaCode = 14">

   <xsl: variable name = "CodeName" select = "'Ulleungdo'" /> <xsl: value-of select = "$ CodeName" />-</ xsl: if>

  <xsl: value-of select = "./ Information / @ temperature" />

  <xsl: text disable-output-escaping = "yes"> &amp; </ xsl: text>

  <! [CDATA [deg;]]>, <xsl: value-of select = "./ Information" />

  <xsl: if test = "not (position () = $ totalNumber)">, </ xsl: if>

  <xsl: text disable-output-escaping = "no"> </ xsl: text>

 </ xsl: for-each>

</ xsl: template>

<xsl: template name = "forRegionVoiceStream">

 <xsl: for-each select = "// CurrentWeather / TotalArea / WideAreas / WideArea">

 <xsl: if test = "@ wideAreaCode = 01">

   <xsl: variable name = "CodeName" select = "'Seoul'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 02">

   <xsl: variable name = "CodeName" select = "'Youngseo'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 03">

   <xsl: variable name = "CodeName" select = "'Youngdong'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 04">

   <xsl: variable name = "CodeName" select = "'Chungbuk'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 05">

   <xsl: variable name = "CodeName" select = "'Chunnam'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 06">

   <xsl: variable name = "CodeName" select = "'Kyoungbuk'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 07">

   <xsl: variable name = "CodeName" select = "'Kyoungnam'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 08">

   <xsl: variable name = "CodeName" select = "'Jeonnam'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 09">

   <xsl: variable name = "CodeName" select = "'Jeonbuk'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 10">

   <xsl: variable name = "CodeName" select = "'Jejudo'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 11">

   <xsl: variable name = "CodeName" select = "'West ocean'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl : text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 12">

   <xsl: variable name = "CodeName" select = "'East ocean'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl : text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 13">

   <xsl: variable name = "CodeName" select = "'South ocean'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl : text> </ xsl: if>

  <xsl: if test = "@ wideAreaCode = 14">

   <xsl: variable name = "CodeName" select = "'Ulleungdo'" /> <xsl: value-of select = "$ CodeName" /> <xsl: text disable-output-escaping = "no"> </ xsl: text> </ xsl: if>

  <xsl: text disable-output-escaping = "no"> </ xsl: text> <xsl: value-of select = "./ Information / @ temperature" />

  <! [CDATA [degrees]]>, <xsl: text disable-output-escaping = "no"> </ xsl: text> <xsl: value-of select = "./ Information" />

  <xsl: if test = "not (position () = $ totalNumber)">, </ xsl: if>

  <xsl: text disable-output-escaping = "no"> </ xsl: text>

 </ xsl: for-each>

</ xsl: template>

</ xsl: stylesheet>

Functions or methods implemented in the present invention as described above may be implemented in 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 has an effect of providing content description data and a content providing device using the same so that a broadcast receiver of a mobile environment can easily use a voice and a graphic user interface at the same time.

In addition, the present invention has an effect that can be utilized as a standard language for producing content to be provided in a digital broadcasting system of a mobile environment.

In addition, the present invention has an effect that can be applied to the information service using a variety of mobile terminals, such as a vehicle, PDA, smart phone, and the like user interface and content description data supporting voice and graphics services.

Claims (11)

A content providing device using content description data for content description in a data broadcasting service, Content description data generating means for generating the content description data; Content authoring means for authoring content to be broadcasted using the content description data; User interface providing means for providing a voice and graphical user interface of a broadcast service; And Content conversion means for converting the authored content into a form suitable for broadcasting to various receiving terminals Including, The content description data, A metadata element for describing meta information of a document commonly required for data broadcasting; And Service content element for describing data of each service suitable for broadcasting environment Content providing apparatus using a content description data comprising a. The method of claim 1, The content providing device, Transmission means for transmitting the content converted by the content conversion means to the broadcast receiver via the user interface provided from the user interface providing means Content providing apparatus using the content description data further comprising. The method of claim 1, The content conversion means, An apparatus for providing contents using contents description data, wherein the contents are converted into a file having any one or more formats of VoiceXML, X + V, HTML, VoiceEPGXML, and SALT. The method of claim 1, The content description data, Advertising content element for describing advertising content data Content providing apparatus using the content description data further comprising. The method according to any one of claims 1 to 4, The metadata element is Content providing apparatus using the content description data, characterized in that for supporting the user's free metadata field expansion. The method according to any one of claims 1 to 4, The service content element, It is to provide any user interface among the voice user interface and the graphic user interface according to the user's preference and terminal specification for the service of news, weather, traffic, local information, education, quiz, securities and EPG. Content providing apparatus using the content description data. The method according to any one of claims 1 to 4, The service content element, An apparatus for providing contents using content description data, comprising a text stream for graphic output and a voicestream element for outputting audio for simultaneously supporting a voice and a graphic user interface. The method according to any one of claims 1 to 4, The service content element, Content providing apparatus using the content description data, characterized in that for supporting the reference for advertising and interactive channels. The method of claim 6, The service content element, About the news service, Content providing apparatus using the content description data, characterized in that to support the keyword search through the graphic and voice input, and to describe the data to support the priority to display from the emergency news. The method of claim 6, The service content element, About the weather service, Content providing apparatus using the content description data, characterized in that for describing the content of each area using a local postal code for classification. delete

Images