KR100590029B1 - Method of providing table field elements by get_data operation in tv-anytime metadata service - Google Patents

Abstract

The present invention relates to a method for providing a table field element using a get_Data operation in a TV-Anytime metadata service. (A) In a get_Data operation, a request field type for specifying a field of a metadata table in a query result value type. Adding (RequestedFieldsType), (b) receiving a request message of a get_Data operation, and (c) if the request message includes a request field type specifying a query result value, requesting the request message. Extracting a query result value corresponding to a specified table field in a field type element, and transmitting the query result value by a response message of a get_Data operation.

Metadata, Anytime, TV-Anytime, metadata, SOAP, XML, get_Data, FileID, Xpath

Description

METHOD OF PROVIDING TABLE FIELD ELEMENTS BY GET_DATA OPERATION IN TV-ANYTIME METADATA SERVICE} How to Provide Table Field Elements with Metadata Services

1 is a block diagram of TV-Anytime metadata.

2 is an operation conceptual diagram of a get_Date operation.

The present invention relates to a TV-Anytime service, and more particularly, to a method of providing a table field element using a get_Data operation in a TV-Anytime metadata service.

Recently, as the digital broadcasting service becomes full-fledged, research on a technology for providing a customized broadcasting service in a multi-channel multimedia environment has been actively conducted. As an example, the private international standard TV-Anytime (hereinafter referred to as "TV-Anytime") is a user's preference information based on metadata representing the description information of the content. And the above-described metadata to match the above-mentioned metadata to provide an Anytime (Anytime) service to store the desired content for free viewing.

As described above, the metadata is descriptive information about the content. In TV-Anytime, the metadata includes content-based description and EPG (electronic program guide) information defined in MPEG-7. Make it easy to navigate and select. The metadata standard consists of two parts. Part A defines a format for describing metadata, that is, a schema. The metadata standard is MPEG-7 Description Definition Language (DDL) based on XML (eXtensible Markup Language). ISO / IEC 15938-2). Part B relates to metadata transfer, which is binary format [MPEG-7 BiM (Binary Format for MPEG-7) (ISO / IEC 15938-1), fragmentation model, encapsulation and indexing. It includes techniques.

FIG. 1 illustrates a configuration of TV-Anytime metadata, and includes program description metadata and user description metadata. The program description metadata may include content description metadata and an instance ( instance) consists of descriptive metadata. The metadata for one program is correlated with a content identifier called a CRID (Content Reference Identifier).

Content description metadata is generated by a content creator and includes program titles, genres, summaries, critic reviews, and the like. The instance description metadata is generated by a content provider and includes a location (broadcast time, channel, URL, etc.), a usage rule, a delivery parameter, and the like. Finally, user description metadata includes user preferences, usage history, personal bookmarks, and the like, and is generated by the user.

The TV-Anytime standard defines two types of metadata web services for bi-directional metadata services via return paths, which are well-defined behaviors and remote procedures for input and output sets. In the Web Service Description Language (WSDL) standard based on the XML (eXtensible Markup Languge), the above-described remote procedure is a simple object access protocol (SOAP). It is defined in the form of "SOAP" operation, and there is a "get_Data ()" operation for metadata retrieval and a "submit_Data" operation for user description submission. For reference, the aforementioned SOAP protocol is an XML communication protocol that allows access to an object in a distributed environment.

The request / response type used in the TV-Anytime metadata service is defined in the namespace of "urn: tva: transport: 2002", which is provided as a tool for validating various messages. do. The types defined in the metadata specification and the content referencing standard are referenced in the transport namespace. Schema fragments (hereinafter referred to as "Schema fragments") are defined in the aforementioned namespaces, and namespace providers are defined as "tns:" in the Schma fragment. The complete XML schema file is tva_transport_types_v10.xsd.

1. get_Data () operation

The get_Data () operation provides the client with the ability to retrieve TV-Anytime data from the server for a program or program group. An example of a function that a TV-Anytime metadata provider can provide using the get_Data () operation is as follows.

Return the content reference data for the CRID using the CRID list

-Return TV-Anytime metadata for CRID using CRID list

Receive a query for a specific metadata attribute (eg genre, actor, etc.) and return the corresponding program

In response to a query for a specific time or channel, the program is returned.

Referring to FIG. 2 with respect to the operation of the get_Data () operation, in the TV-Anytime service, the client (Client) is a SOAP request message by the get_Data () operation via the IP network [get_Data () Request] To the metadata service server. In this case, the get_Data () operation supports all query types in principle, and provides a wide range of queries for metadata constraints. Subsequently, the metadata service server returns a query result value for the SOAP request message by a SOAP response message [get_Data () Request].

end. Request Format

As shown in Table 1, in the get_Data () operation, the request format specifies three types of parameters to the client, and the element type returned as a query (search) result value to the RequestedTables type.

<element name = "get_Data" type = "tns: get_Data" /> <complexType name = "get_Data"> <sequence> <element name = "QueryConstraints"> <complexType> <choice> <element name = "PredicateBag" type = "tns: PredicateBagType" /> <element name = "BinaryPredicate" type = "tns: BinaryPredicateType" /> <element name = "UnaryPredicate" type = "tns: UnaryPredicateType" /> </ choice> </ complexType> </ element > <element name = "RequestedTables" type = "tns: RequestedTablesType" /> </ sequence> <attribute name = "maxPrograms" type = "unsignedInt" /> </ complexType>

Table 2 shows an example of specifying the RequestedTables returned as a query result as ClassificationSchemeTable, ProgramInformationTable, GroupInformationTable, CreditsInformationTable, ProgramLocationTable, ServiceInformationTable, ProgramReviewTable, SegmentInformationTable, and so on.

<element name = "get_Data" type = "tns: get_Data" /> <complexType name = "get_Data"> <sequence> <element name = "QueryConstraints"> <complexType> <choice> <element name = "PredicateBag" type = "tns: PredicateBagType" /> <element name = "BinaryPredicate" type = "tns: BinaryPredicateType" /> <element name = "UnaryPredicate" type = "tns: UnaryPredicateType" /> </ choice> </ complexType> </ element > <element name = "RequestedTables" type = "tns: RequestedTablesType" /> </ sequence> <attribute name = "maxPrograms" type = "unsignedInt" /> </ complexType>                                                        <complexType name = "RequestedTablesType"> <sequence> <element name = "Table" maxOccurs = "unbounded"> <complexType> <sequence> <element name = "SortCriteria" type = "tns: SortCriteriaType" minOccurs = "0" maxOccurs = "unbounded" /> </ sequence> <attribute name = "type" use = "required"> <simpleType> <restriction base = "string"> <enumeration value = "ContentReferencingTable" /> <enumeration value = "ClassificationSchemeTable" /> <enumeration value = "ProgramInformationTable" /> <enumeration value = "GroupInformationTable" /> <enumeration value = "CreditsInformationTable" /> <enumeration value = "ProgramLocationTable" /> <enumeration value = "ServiceInformationTable" /> <enumeration value = "ProgramReviewTable" /> <enumeration value = "SegmentInformationTable" /> </ restriction> </ simpleType> </ attribute> </ complexType> </ element> </ sequence> </ complexType>

I. Response Format

The response format of the get_Data () operation contains zero or one or more XML instance documents for the elements (TVAMain, ContentReferencingTable, InvalidFragments), as shown in Table 3, and returns the query result according to the requested RequtstedTables type in the request format. do.

<element name = "get_Data_Result" type = "tns: get_Data_ResultType" /> <complexType name = "get_Data_ResultType"> <sequence> <element name = "TableSortingInformation" type = "tns: RequestedTablesType" minOccurs = "0" /> <element ref = "tva: TVAMain" minOccurs = "0" /> <element ref = "cr: ContentReferencingTable" minOccurs = "0" /> <element name = "InvalidFragments" type = "tns: InvalidFragmentsType" minOccurs = "0" / > </ sequence> <attribute name = "serviceVersion" type = "unsignedInt" use = "required" /> <attribute name = "truncated" type = "boolean" />

As described above, the get_Data () operation currently defined in TV-Anytime SP006 returns a desired table or TVAMain through a search. That is, the search result of the get_Data () operation is transmitted in a table unit such as "TVAMain" or "ProgramInformationTable", "GroupInformationTable", "programLocationTable", "ServiceInformationTable", "CreditsInformationTable", "ProgramReviwTable", "SegmentInformatinTable", and the like.

Meanwhile, the settop box may retrieve content and receive corresponding metadata through a get_Data () operation in an interactive environment. However, as the set-top box is developed as a home server, the set-top box can perform a metadata service agent function in the home, and in a terminal using limited resources such as a portable media player, the existing table unit Being provided with metadata can cause significant resource waste.

For example, assuming that the metadata provided by the portable media player to the user environment is title, genre, location information, and review information, when querying through the existing get_Data () operation, programInformationTable, ProgramLocationTable, and ProgramReviewTable are used as the values of RequestedTables. Request and parse the value of the element or attribute and display it in the user interface (UI). Therefore, the unnecessary metadata of each table causes a waste of network resources for transmitting them and a waste of resources due to parsing of the portable media player.

Therefore, the conventional table-by-table retrieval of the get_Data () operation has a problem that resource waste occurs due to unnecessary metadata transmission and reparsing of the client when the client does not need the metadata of the entire table.

In order to solve the above-described problem, an object of the present invention is to enable a client to selectively return desired metadata by requesting a return result value in units of fields in a get_Data () operation.

According to an aspect of the present invention, there is provided a TV-Anytime metadata service method using a SOAP query operation, and (a) in the SOAP query operation, a request field type that can specify a field of a metadata table in a query result value type Adding (RequestedFieldsType), (b) receiving a request message of the SOAP query operation, and (c) the request message includes an element of the requested field type specifying a query result value, Extracting a query result value corresponding to a table field specified in a request field type element of the request message, and transmitting the query result value by a response message of the SOAP operation.

In this case, the SOAP operation may be a get_Data () operation, and the request field type element added in the step (a) includes a request field subelement that specifies a field ID (fieldID) of a metadata table, and the field ID. It may include a request path subelement that specifies a path (Xpath) for (fieldID).

Also, in the step (c), when duplicate data having the same field ID (fieldID) exists in the query result value, the duplicate data may be excluded from the query result value, and the metadata may include program description metadata ( Program Description Metadata).

According to a second aspect of the present invention, there is provided a computer-readable recording medium comprising instructions for performing each step of the TV-Anytime metadata service method according to the first aspect of the present invention described above.

Hereinafter, preferred embodiments of the present invention will be described.

Table 4 defines a request field type (referred to as "RequestedFieldsType") for requesting a query result of a specific element or attribute unit in a modified get_Data () operation according to a preferred embodiment of the present invention. .

<complexType name = "RequestedFieldsType"> <sequence> <element name = "RequestedField" minOccurs = "0" maxOccurs = "unbounded"> <complexType> <sequence> <element name = "SortCriteria" type = "tns: SortCriteriaType" minOccurs = "0" maxOccurs = "unbounded" /> </ sequence> <attribute name = "fieldID" type = "tns: fieldIDType" use = "required" /> </ complexType> </ element>                                                      <element name = "RequestedXPath" minOccurs = "0" maxOccurs = "unbounded"> <complexType> <sequence> <element name = "SortCriteria" type = "tns: SortCriteriaType" minOccurs = "0" maxOccurs = "unbounded" /> </ sequence> <attribute name = "XPath" type = "string" use = "required" /> </ complexType> </ element> </ sequence> </ complexType>

In Table 4, two elements of RequestedField and RequestedXPath can be added as sub-elements, and each element is designated as minOccurs = "0" maxOccurs = "unbounded", so that for zero or more infinite RequestedField and RequestedXPath Inquiry is possible.

RequetstedField has a SortCriteria as a sub element. SortCriteria represents the sorting criteria for the query results, follows the existing sorting method, and has fieldID as an attribute. The fieldID value is the ID of the field to receive as a query result and uses the fieldIDType defined by the current TV-Anytime.

Problems can occur when querying using RequestedField, because there can be multiple Xpaths in one fieldID. In the above-described case, the service agent of the metadata server may transmit all duplicate data or exclude duplicates, and may selectively transmit the same TVAMain instance according to its own policy. Such transmission of duplicate fieldID follows the policy of the service provider.

In order to prevent ambiguity according to the service provider's policy, the user can request a query using RequestedXPath. In other words, RequestedXPath can specify an explicit path (XPath) of a field to request according to the syntax of XPath. Like RequestedField described above, RequestedXPath has a SortCriteria as a sub element and has an XPath as an attribute, so that a value for querying the value (type) of the XPath attribute can be set.

Table 5 below shows the request format of the get_Data () operation modified to use the aforementioned RequsetedFieldsType.

<element name = "get_Data" type = "tns: get_Data" /> <complexType name = "get_Data"> <sequence> <element name = "QueryConstraints"> <complexType> <choice> <element name = "PredicateBag" type = "tns: PredicateBagType" /> <element name = "BinaryPredicate" type = "tns: BinaryPredicateType" /> <element name = "UnaryPredicate" type = "tns: UnaryPredicateType" /> </ choice> </ complexType> </ element >                                                      <element name = "RequestedTables" type = "tns: RequestedTablesType" minOccurs = "0" maxOccurs = "unbounded" /> <element name = "RequestedFields" type = "tns: RequestedFieldsType" minOccurs = "0" maxOccurs = "unbounded" />                                                      </ sequence> <attribute name = "maxPrograms" type = "unsignedInt" /> </ complexType>

Referring to Table 5, RequestedFields is added after RquestedTables. RequestedFields uses RequestedFieldstype of Table 4 and can use the above-described RequestedField and RequestedXPath elements.

Next, an example of an instance performing a query using the modified get_Data () operation described above will be described. As shown in Table 6, the user (or client) requests (query) the field in the RequestedField whose fieldID is "tvaf: ServiceURL" and its value is "tv: // 7" or "tv: // 9". . As the type of the query result value, RequestedTables is designated as "ProgramLocation Table", and the fieldID of RequestedFields is "tvaf: CRID", "tvaf: Genre", "tvaf: Title", "tvaf: ProgramURL", "tvaf: PublishedStart "," tvaf: PublishedDuration ", and RequestedXPath

It is specified in "/ TVAMain / ProgramDescription / ProgramReviewTable / Review / FreeTextReview / text ()".

<? xml version = "1.0" encoding = "UTF-8"?> <tns: get_Data xmlns: tns = "urn: tva: transport: 2002" xmlns: cr = "http://www.tv-anytime.org / 2002/06 / ContentReferencing "xmlns: mpeg7 =" urn: mpeg: mpeg7: schema: 2001 "xmlns: p3p =" http://www.w3.org/2002/01/P3Pv1 "xmlns: rar =" http: //www.tv-anytime.org/2002/06/ResolvingAuthority "xmlns: tva =" urn: tva: metadata: 2002 "xmlns: xsi =" http://www.w3.org/2001/XMLSchema-instance " xsi: schemaLocation = "urn: tva: transport: 2002 tva_transport_types_v10.xsd">                                                  <tns: QueryConstraints> <tns: PredicateBag type = "OR"> <tns: BinaryPredicate fieldID = "tvaf: ServiceURL" fieldValue = "tv: // 7" /> <tns: BinaryPredicate fieldID = "tvaf: ServiceURL" fieldValue = "tv: // 9" /> </ tns: PredicateBag> </ tns: QueryConstraints> <tns: RequestedTables> <tns: Table type = "ProgramLocationTable" /> </ tns: RequestedTables> <tns: RequestedFields> <tns : RequestedField fieldID = "tvaf: CRID" /> <tns: RequestedField fieldID = "tvaf: Genre" /> <tns: RequestedField fieldID = "tvaf: Title" /> <tns: RequestedField fieldID = "tvaf: ProgramURL" /> <tns: RequestedField fieldID = "tvaf: PublishedStart" /> <tns: RequestedField fieldID = "tvaf: PublishedDuration" /> <tns: RequestedXPath XPath = "/ TVAMain / ProgramDescription / ProgramReviewTable / Review / FreeTextReview / text ()" /> </ tns: RequestedFields> </ tns: get_Data>

Table 7 illustrates the response instances for the query instances in Table 6, with fieldIDs of "tvaf: CRID", "tvaf: Genre", "tvaf: Title", and "tvaf: ProgramURL" in the ProgramInformationTable according to the search conditions in Table 6. "," tvaf: PublishedStart "," tvaf: PublishedDuration ", and RequestedXPath is

The search result value "/ TVAMain / ProgramDescription / ProgramReviewTable / Review / FreeTextReview / text ()" is extracted and returned.

<? xml version = "1.0" encoding = "UTF-8"?> <tns: get_Data_Result xmlns: tns = "urn: tva: transport: 2002" xmlns: cr = http: //www.tv-anytime.org/ 2002/06 / ContentReferencing xmlns: mpeg7 = "urn: mpeg: mpeg7: schema: 2001" xmlns: p3p = http: //www.w3.org/2002/01/P3Pv1 xmlns: rar = "http: // www. tv-anytime.org/2002/06/ResolvingAuthority "xmlns: tva =" urn: tva: metadata: 2002 "xmlns: xsi =" http://www.w3.org/2001/XMLSchema-instance "xsi: schemaLocation = "urn: tva: transport: 2002 F: \ Doc \ WORKINDOC \ Project \ Part Materials \ Creation Documents \ Metadata Definition \ sp006test \ tva_transport_types_v10.xsd" serviceVersion = "1" truncated = "false">                                                  <tns: TableSortingInformation> <tns: Table type = "ProgramLocationTable"> <tns: SortCriteria fieldID = "tvaf: CRID" /> </ tns: Table> <tns: Table type = "ProgramInformationTable"> <tns: SortCriteria fieldID = "tvaf: CRID" /> </ tns: Table> </ tns: TableSortingInformation> <tva: TVAMain> <tva: ProgramDescription> <tva: ProgramInformationTable> <tva: ProgramInformation programId = "CRID: //www.kbs.co .kr: cultural / specialreport_7 "> <tva: BasicDescription> <tva: Title> Iranian 25th Anniversary of the Shiite Choice Revolution </ tva: Title> <tva: Genre href =" urn: tva: metadata: cs: ContentCS: 2002 "type =" main "> <tva: Name> Cultural </ tva: Name> </ tva: Genre> <tva: Genre href =" urn: tva: metadata: cs: ContentCS: 2002 "type =" secondary "> <tva: Name> Local / regional </ tva: Name> </ tva: Genre> </ tva: BasicDescription> </ tva: ProgramInformation>

          <tva: ProgramInformation programId = "CRID: //www.keti.re.kr: drama / wanggun"> <tva: BasicDescription> <tva: Title> Tempered Wang Gun </ tva: Title> <tva: Genre href = "urn : tva: metadata: cs: ContentCS: 2002 "type =" main "> <tva: Name> FICTION </ tva: Name> </ tva: Genre> <tva: Genre href =" urn: tva: metadata: cs: ContentCS: 2002 "type =" secondary "> <tva: Name> HISTORICAL / EPIC </ tva: Name> </ tva: Genre> </ tva: BasicDescription> </ tva: ProgramInformation> </ tva: ProgramInformationTable> <tva : ProgramLocationTable> <tva: BroadcastEvent serviceIDRef = "9"> <tva: Program crid = "CRID: //www.kbs.com: cultural / specialreport_7" /> <tva: ProgramURL> ftp: //203.253. 130.21 / images / 230x158 / news9.tar </ tva: ProgramURL> <tva: PublishedStartTime> 2004-09-07T11: 00: 00.00 + 09: 00 </ tva: PublishedStartTime> <tva: PublishedDuration> PT55M </ tva: PublishedDuration > </ tva: BroadcastEvent> <tva: BroadcastEvent serviceIDRef = "9"> <tva: Program crid = "CRID: //www.keti.re.kr: drama / wanggun" /> <tva: ProgramURL> ftp: / /203.253.130.21/images/230x158/wanggun.tar </ tva: ProgramURL> <tva: PublishedStartTime> 2003-10-20T21: 00: 00.00 + 09: 00 </ tva: PublishedStartTime> <tva: PublishedDuration> PT9M23S </ tva: PublishedDuration> </ tva: BroadcastEvent> </ tva: ProgramLocationTable> <tva: ProgramReviewTable> <tva: Review programId = "CRID: //www.keti.re.kr: drama / wanggun"> <tva: FreeTextReview> Disruption of the Three Kingdoms and New History of Koryo Great drama shows vividly </ tva: FreeTextReview> </ tva: Review> </ tva: ProgramReviewTable>                                              </ tva: ProgramDescription> </ tva: TVAMain> <tns: InvalidFragments /> </ tns: get_Data_Result>

Although the preferred embodiment of the present invention has been described above, this is for the purpose of illustration, and those skilled in the art to which the present invention pertains may make various changes or modifications without departing from the spirit of the present invention. Therefore, the protection scope of the present invention is not limited to the above-described embodiment, but is determined by the following claims.

As described above, according to the present invention, the get_Data () operation of the TV-Anytime standard enables requesting a return result value in units of fields, thereby selectively returning metadata desired by the client. That is, the client of the metadata service may receive the metadata query result in table units and / or field units of the table, and thus may selectively receive only metadata desired by the user. The reparsing load on the client can be significantly reduced. Meanwhile, the present invention can implement the above-mentioned advantages even in a typical set-top box environment, and can be more advantageously used in a client environment where processing resources are limited, such as a portable media player.

On the other hand, in the present invention, in order to process the metadata in units of fields requested by the client, additional processing may be required at the server side, but considering that the server of the service agent is a large environment compared to the client environment, The processing time of the client can be reduced more significantly.

Claims (11)

A method of providing TV-Anytime metadata using a SOAP query operation, (a) adding, in the SOAP query operation, a RequestedFieldsType that can specify a field of a metadata table to a query result value type; (b) receiving a request message of the SOAP query operation; (c) if the request message includes an element of the request field type specifying a query result value, extract a query result value corresponding to a table field specified in the request field type element of the request message, and query result Sending a value by a response message of the SOAP operation TV-Anytime metadata providing method comprising a. The method of claim 1, wherein the SOAP query operation is a get_Data () operation. According to claim 1 or 2, wherein the element of the request field type added in step (a), A request field subelement that specifies a field ID (fieldID) of the metadata table; TV-Anytime metadata providing method comprising a request path sub-element specifying a path (Xpath) for the field ID (fieldID). The method of claim 1 or 2, wherein step (c) And if duplicate data having the same field ID (fieldID) exists in the query result value, excludes duplicate data from the query result value. The method of claim 1 or 2, wherein the metadata is program description metadata. The method of claim 5, wherein step (c) And if duplicate data having the same field ID (fieldID) exists in the query result value, excludes duplicate data from the query result value. The method of claim 5, wherein the request field type element added in step (a) is A request field subelement that specifies a field ID (fieldID) of the metadata table; And a request path sub-element specifying a path (Xpath) for the field ID (fieldID). The method of claim 7, wherein step (c) And if duplicate data having the same field ID (fieldID) exists in the query result value, excludes duplicate data from the query result value. 8. The method of claim 7, wherein the RequestFiedlsType element is defined as follows. <complexType name = "RequestedFieldsType"> <sequence> <element name = "RequestedField" minOccurs = "0" maxOccurs = "unbounded"> <complexType> <sequence> <element name = "SortCriteria" type = "tns: SortCriteriaType" minOccurs = "0" maxOccurs = "unbounded" /> </ sequence> <attribute name = "fieldID" type = "tns: fieldIDType" use = "required" /> </ complexType> </ element> <element name = "RequestedXPath" minOccurs = "0" maxOccurs = "unbounded"> <complexType> <sequence> <element name = "SortCriteria" type = "tns: SortCriteriaType" minOccurs = "0" maxOccurs = "unbounded" /> </ sequence> <attribute name = "XPath" type = "string" use = "required" /> </ complexType> </ element> </ sequence> </ complexType> A computer-readable recording medium comprising instructions for performing each step of the method for providing TV-Anytime metadata according to claim 1. A computer-readable recording medium comprising instructions for performing each step of the method for providing TV-Anytime metadata according to claim 3.

Images