KR100590030B1 - Method using an soap operation for leaving out user metadata managed by tv-anytime metadata server - Google Patents

Abstract

The present invention provides a method for deleting user metadata managed by a TV-Anytime metadata server by a SOAP operation, and (a) providing an element type of a SOAP delete operation, wherein An element comprising a first subelement for specifying user identification information; (b) receiving an element of a SOAP deletion operation for which user identification information is specified from a user's client; and (c ) Identifying a user from the user identification information of the received SOAP delete operation element and deleting the user metadata of the identified user.

Metadata, Anytime, TV-Anytime, metadata, SOAP

Description

METHOD USING AN SOAP OPERATION FOR LEAVING OUT USER METADATA MANAGED BY TV-ANYTIME METADATA SERVER} How to Delete User Metadata Managed by a Metadata Server

1 is a block diagram of TV-Anytime metadata.

2 is a conceptual diagram of a clear_submitted_data () operation according to a preferred embodiment of the present invention.

The present invention relates to a TV-Anytime service, and more particularly, to a method of deleting user metadata managed by a TV-Anytime metadata server by a SOAP 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, 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 standard metadata for providing an Anytime service that allows the user to store the desired content and watch it at a free time by matching the aforementioned metadata.

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 the configuration of TV-Anytime metadata, which includes program description metadata and user description metadata, and the program description metadata includes content description metadata and instance description 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, 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 "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 a namespace of "urn: tva: transport: 2002", which is provided as a tool for validating various messages. do. 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 namespace, and the namespace provider is 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 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.

The get_Data operation in principle supports all query types and provides a wide range of queries for metadata constraints.

end. Request Format

In the get_Data operation, the request format specifies three types of parameters to the client, and the description of each parameter is shown in Table 1.

<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>

I. Response Format

The get_Data response format includes zero or one or more XML instance documents for the elements (TVAMain, ContentReferencingTable, InvalidFragments), as shown in Table 2.

<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" />

2. submit_Data operation

TV-Anytime's Phase I technical standard restricts to data defined as a set of intelligent agent based on usage services and content, or a set of anonymous profile data generated by manual entry. The TV-Anytime Forum respects and includes the basic rights of all users and providers, which includes the basic rights of the privacy of content users and the legal rights of all participants, such as content creators, providers and service providers.

3. get_Data operation with user information

Currently, in the TV-Anytime, based on the user metadata transmitted through submit_Data, the service agent performs the get_Data operation through a special algorithm for each agent and transmits the result to the user.

As such, the user information provided to the service agent is used according to the service provider's policy. For example, the user information collected for a specific period of time may be used or the entire user information may be used. As described above, the use of the user information according to the service agent's policy provides the user with more convenience. However, when the user does not need the service agent's service, that is, the service agent's information is based on the accumulated personal information If the service result is not suitable, there is no method for deleting the user information of the user so far.

Moreover, since the method of processing user metadata is entirely dependent on the algorithm of the service provider, the user can not be concerned at all about how his information is used, etc., and thus the user can hesitate to use the interactive metadata service have.

In order to solve the above problem, the present invention provides a method for deleting user information transmitted to the metadata server or service agent through submit_Data (), so that the user has a minimum control over his or her information. There is a purpose.

According to an aspect of the present invention, there is provided a method for deleting user metadata managed by a TV-Anytime metadata server by a SOAP operation, and (a) providing an element type of a SOAP delete operation, Providing a SOAP delete operation, wherein the element of the SOAP delete operation includes a first subelement for specifying user identification information; and (b) receiving an element of a SOAP delete operation for which user identification information is specified from a user's client. And (c) identifying the user from the user identification of the received SOAP delete operation element and deleting the user metadata of the identified user.

In this case, the method may further include transmitting the deletion result of step (c) to the client. In addition, the element of the SOAP delete operation defined in step (a) further includes a second subelement for specifying a delete condition, and step (c) includes a second subelement of the received SOAP delete operation element. It may be configured to delete user information that meets a specified deletion condition.

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

2 illustrates the concept of the clear_submitted_Data () operation provided for deleting user information according to a preferred embodiment of the present invention.

Referring to FIG. 2, clear_submitted_Data () is an operation for deleting user information transmitted to the bidirectional server, and the client (Client) identifies a SOAP message including a period and user identification information (UserIdentifier) to be deleted by clear_submitted_Data (). It transmits to the service agent of the metadata server and can use the IP network. In this case, as a policy for deleting user information, i) delete user information (user metadata) transmitted before the corresponding date on the basis of a specific date, or ii) delete all user information transmitted. Subsequently, the service agent transmits a result (clear_submitted_Data_Result) resulting from the deletion of the user information to the client.

Hereinafter, with reference to Table 3, the structure of the above-described clear_submitted_Data () operation will be described in detail.

<element name = "clear_submitted_Data" type = "tns: clear_submitted_DataType" />                                                  <complexType name = "clear_submitted_DataType">                                                       <sequence>                                                            <element name = "DateFrom" type = "tva: TVATimeType" minOccurs = "0" />                                                            <element name = "DateTo" type = "tva: TVATimeType" minOccurs = "0" />                                                            <element name = "UserIdentifier" type = "mpeg7: UserIdentifierType" maxOccurs = "unbounded" />                                                       </ sequence>                                                  </ complexType>                                                                                                    <element name = "clear_submitted_Data_Result" type = "tns: clear_submitted_Data_ResultType" />                                                                                                    <simpleType name = "clear_submitted_Data_ResultType">                                                     <restriction base = "string">                                                       <enumeration value = "success" />                                                       <enumeration value = "system error" />                                                       <enumeration value = "no data" />                                                       </ restriction>                                                       </ simpleType>                                                      </ restriction>                                                  </ simpleType>                                             

Referring to Table 3, clear_submitted_Data largely has dateFrom, dateTo, and UserIdentifier elements. The dateFrom and dateTo elements indicate the date of user information to be deleted, and the UserIdentifier element is used to identify the user.

More specifically, the dateFrom element is the start date of the user data to be deleted and the dateTo element is the end date of the user data to be deleted. For example, if you delete user data from March 6, 2003 to July 8, 2004, you can apply 20030306 to dateFrom and 20040708 to dateTo. Since the dateFrom and dateTo elements are set to minOccurs = "0" maxOccurs = "1", respectively, either one value or both may not be set. If only the value of dateTo is set, all user data before dateTo is deleted. If only the value of dateFrom is set, all user data after dateFrom can be deleted. If neither dateFrom nor dateTo are set, all user data is deleted regardless of the time period.

The result of performing the delete operation by the clear_submitted_Data request is transmitted through clear_submitted_Data_ResultType. In this case, the result value may be selected from success, system error, and no data. success indicates that the process has been completed, and system error indicates that the delete operation was not performed due to the current system. And no data indicates that there is no result to process.

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, the clear_submitted_data () operation provided by the present invention provides a method for deleting user information sent to a server or agent, so that the user can have a minimum control over his or her information. There is this.

Claims (8)

As a method of deleting user metadata managed by a TV-Anytime metadata server by a SOAP operation, (a) providing an element type of a SOAP delete operation, wherein the element of the SOAP delete operation includes a first subelement for specifying user identification information; (b) receiving an element of a SOAP delete operation for which user identification information is specified from a client of the user, (c) identifying a user from the user identification of the received SOAP delete operation element and deleting the user metadata of the identified user Method for deleting user metadata by a SOAP operation including a. The method of claim 1, and (d) transmitting the deletion result of step (c) to the client. The method of claim 2, Deletion result sent to the client in the step (d) is one of the value indicating the success, error, no deletion target user metadata deletion method by the SOAP operation. The method according to any one of claims 1 to 3, The element of the SOAP delete operation defined in step (a) further includes a second subelement for specifying a delete condition, And (c) deleting the user information that satisfies the deletion condition specified in the second sub-element of the received SOAP deletion operation element. The method according to any one of claims 1 to 3, The element of the SOAP delete operation defined in step (a) further includes a third subelement for specifying a dateFrom, And (c) deleting the user information transmitted after the date specified in the third sub-element of the received SOAP delete operation element. The method according to any one of claims 1 to 3, The element of the SOAP delete operation defined in step (a) further includes a fourth subelement for specifying a dateTo, And (c) deleting the user information transmitted before the date specified in the fourth sub-element of the received SOAP delete operation element. A computer-readable recording medium comprising instructions for performing each step of the method according to any one of claims 1 to 3. A computer-readable recording medium comprising instructions for performing each step of the method according to claim 4.

Images