KR100696949B1 - Method of providing requestedfieldstype by get_data operation in tv-anytime service - Google Patents

Abstract

The present invention provides a method for field-based retrieval of a table using a get_Data operation in a TV-Anytime service, and (a) specifying a field of the table in a Requested Table element that specifies a table as a query result value of a get_Data operation. Adding Requested Fields (RequestedFields) as subelements; (b) receiving a request message of the get_Data operation; (c) in response to receiving the request message, extracting a field specified in the request field element from the table specified in the request table element as a query result value; (d) transmitting the extracted query result value by a response message of a get_Data operation. According to the present invention, the client has an advantage of requesting a return result value in units of fields of the request table and selectively returning desired metadata.

TV-Anytime, metadata, SOAP, XML, request_Data, FileID, Xpath, submit_Data, service agent, customized service

Description

How to search for field-level units using the ｅ Ａ Ａ ａ ａ ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ Ａ

1 is a block diagram of TV-Anytime metadata.

2 is a general conceptual diagram of a get_Data operation.

3 is a request format of a conventional get_Data operation.

4 is an exemplary diagram in which a RequestedTables type is returned in which a query result is returned in a conventional get_Data operation.

5 is a response format of a conventional get_Data operation.

FIG. 6 is a diagram defining a RequestedFieldsType for specifying a specific element and attribute value according to a preferred embodiment of the present invention. FIG.

FIG. 7 illustrates a request table type (RequestedTablesType) by adding elements of the request field type (RequsetedFieldsType) of FIG.

FIG. 8 is an example of a get_Data operation requesting the RequestedTablesType element of FIG. 7 as a return value. FIG.

The present invention relates to a TV-Anytime service, and more particularly, to a method of providing a field-by-field search using a get_Data operation.

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, TV-Anytime, a private international standard, allows users to store desired content by matching their preference information with the aforementioned metadata based on metadata representing the description information of the content. This is a standard specification for providing Anytime services that can be viewed on the web.

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 XML (eXtensible Markup Language), the above-described remote procedure is a simple object access protocol (SOAP). It is defined in the form of "SOAP" operation, and there is "get_Data" operation for metadata retrieval and "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 the namespace provider is defined as "tns:" in the Schema fragment. The complete XML schema file is tva_transport_types_v10.xsd.

The aforementioned get_Data operation provides a function for a client to retrieve TV-Anytime data from a 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, the operation of the get_Data operation will be described. In the TV-Anytime service, the client may transmit a SOAP request message [get_Data Request] by the get_Data operation through an IP network or the like. Metadata Service). 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 FIG. 3, 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.

4 is an example in which the type of RequestedTables returned from the query is designated as ClassificationSchemeTable, ProgramInformationTable, GroupInformationTable, CreditsInformationTable, ProgramLocationTable, ServiceInformationTable, ProgramReviewTable, SegmentInformationTable, and the like.

I. Response Format

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

As described above, the get_Data operation currently defined in TV-Anytime SP006 returns a result of a desired table or TVAMain through a search. That is, the search result of the get_Data operation is transmitted in table units 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 the metadata service agent function in the home, and in the terminal using limited resources such as a portable media player, the meta data in the existing table unit is used. Providing data 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, request ProgramInformationTable, ProgramLocationTable, and ProgramReviewTable with the values of RequestedTables. Parse the value of the element or the value of an attribute and display it in the 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.

In addition, the conventional table unit search 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, the present invention specifies a specific element and attribute value of the RequestedTables in the conventional get_Data operation so that the client can request a return result value in units of fields of the Requested Table. The goal is to allow the selective return of metadata.

According to a first aspect of the present invention, there is provided a method for field-by-field retrieval of a table using a get_Data operation in a TV-Anytime metadata service, and (a) a request table element specifying a table as a query result value of a get_Data operation. Adding (RequestedFields) as a subelement to (RequestedTables) specifying fields of the table; (b) receiving a request message of the get_Data operation; (c) in response to receiving the request message, extracting a field specified in the request field element from the table specified in the request table element as a query result value; (d) transmitting the extracted query result value by a response message of a get_Data operation.

In this case, the requested field elements (RequestedFields) added in the step (a) may include a united request field element (RequestedField) specifying a field ID (fieldID) of the field to be searched as a sub-element, the (a In step), it is preferable to assign a field ID (fieldID) of a field to be searched as an attribute of the unit request field element. In addition, the request field element added in step (a) may include a request path element (RequestedXPath) that designates a path of a field to be searched as a subelement.

According to a second aspect of the invention, there is provided a computer readable recording medium comprising instructions for performing each step of the method described above.

Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings.

FIG. 6 illustrates the definition of a RequestedFieldsType for specifying a specific element and attribute value, in accordance with a preferred embodiment of the present invention.

As shown, the Requested Fields Type (RequsetedFieldsType) contains two elements: RequestedField (RequestedField) and Requested Path (RequestedXPath), and these RequestedFieldsTypes are subelements of the RequestedTablesType. Can be added.

Since the above-mentioned unit request field (RequestedField) and request path (RequestedXPath) elements are respectively set to minOccurs = "0" maxOccurs = "unbounded", zero or more infinite unit request fields (RequestedField) and RequestedXPath (RequestedXPath) Inquiry is possible.

The RequestedField has a sort criterion (SortCriteria) as a sub element. SortCriteria represents a sorting criterion for the query result, which follows a conventional sorting method. In addition, the united request field (RequestedField) specifies a field ID (fieldID) as an attribute (Attribute), the value of this fieldID is the ID of the field to receive as a query result. This fieldID uses the field ID type (fieldIDType) defined by the current TV-Anytime.

On the other hand, when querying using a united request field (RequestedField), a problem may occur because multiple Xpaths may exist in one fieldID. In this 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 this case, querying using the above-described RequestedXPath may prevent ambiguity according to the policy of the service provider. In other words, RequestedXPath can specify an explicit path (XPath) of a field to request according to the syntax of XPath. RequestedXPath has a SortCriteria as a sub element like the RequestedField described above, and has an XPath as an attribute. Therefore, you can set a value for querying with an XPath attribute value (type).

FIG. 7 illustrates a definition of an element of the above-mentioned RequestedFieldsType, that is, a RequestedTablesType in which Requested Fields (RequestedFields) have been added as a subelement, and thus desired as a query result of a get_Data operation. The return value can be requested in units of fields in the request table.

As shown, the request field elements (RequestedFields) is a subelement of the Request Tables Type (RequestedTablesType), it is possible to query for zero or more Requested Fields (RequestedFields) for one request table.

FIG. 8 illustrates an example of a get_Data operation for requesting a request table element (RequestedTables) of a request table type (RequestedTablesType) defined according to FIG. 7 as a return value.

As shown, the RequestedTables element includes RequestedFields for the "ProgramInformation Table" and the "ProgramLocation Table", respectively. The request field element for the "ProgramInformation Table" includes two unit request fields having a field ID (FieldID) as an attribute and requests "tvaf: CRID" and "tvaf: Genre" as return values. In addition, the request field element of the "ProgramLocation Table" includes a unit request field in which "tvaf: ProgramURL" is provided as an attribute and requests the return of this field. Accordingly, the service agent receiving the query of FIG. 7 may selectively search only the fields requested by the clients in the "ProgramInformation Table" and "ProgramLocation Table" and return the result.

Although the preferred embodiment of the present invention has been described above, this is for illustrative purposes, and those skilled in the art to which the present invention pertains may variously modify or modify it 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, as a subelement of RequestedTables, an element of RequestedFieldsType is added, thereby requesting a unit request having an ID (FieldID) of a specific field as an attribute without changing the get_Data operation. You can specify field elements. Accordingly, the client may request a return result value in units of fields of the request table, and selectively return desired metadata.

Claims (6)

delete In the TV-Anytime metadata service, a method of providing a field-based search of a table using a get_Data operation, (a) adding a request field element (RequestedFields) designating a field of the table as a subelement to a request table element (RequestedTables) designating a table as a query result value of a get_Data operation; (b) receiving a request message of the get_Data operation; (c) in response to receiving the request message, extracting a field specified in the request field element from the table specified in the request table element as a query result value; (d) transmitting the extracted query result value by a response message of a get_Data operation; Including, The request field elements (RequestedFields) added in the step (a) includes a unit-requested field element (RequestedField) specifying a field ID (fieldID) of the field to be searched as a sub-element TV-Anytime metadata providing method . The method of claim 2, wherein step (a) And providing a field ID (fieldID) of a field to be searched as an attribute of the unit request field element. The method according to claim 2 or 3, wherein the request field element added in step (a) is And a request path element (RequestedXPath) specifying a path of a field to be searched as a sub element. delete A computer-readable recording medium comprising instructions for performing each step of the method for providing TV-Anytime metadata according to any one of claims 2 and 3.

Images