CN1767534A - Method for deleting user metadata in TV-Anytime metadata server - Google Patents

Abstract

The present invention relates to a method or an operation for providing a personalized TV-Anytime metadata service. According to an embodiment of the present invention, there is provided a method of deleting user metadata managed by a TV-Anytime metadata server using a SOAP operation, comprising the steps of a) providing an element type of a SOAP delete operation, the element of the SOAP delete operation including at least a first sub-element for designating user identifier information, b) receiving the element of the SOAP delete operation, in which the user identifier information is designated, from a client of a user, and c) identifying the user on the basis of the user identifier information in the received element of the SOAP delete operation and deleting user metadata about the identified user.

Description

Method for deleting user metadata in TV-Anytime metadata server

technical field

The invention relates to TV-Anytime service, in particular to a method for providing personalized TV-Anytime metadata service through SOAP operation.

Background technique

Recently, with the formalization of digital broadcast services, research on technologies for providing on-demand broadcast services in a multi-channel and multimedia environment has become more and more active. As an example, TV-Anytime, which is a private international standard, is a standard specification for providing Anytime services. This Anytime service is based on metadata representing content description information, and users can store desired content by matching their own preference information with the metadata, and watch it at their free time.

Metadata is content-based description information defined in MPEG-7 and EPG (Electronic Program Guide) information in TV-Anytime, as described above, so that users can easily easily search and select the desired content. The metadata standard consists of two parts. Part A defines the format for describing metadata, that is, the schema (Schema), using MPEG-7DDL (Description Definition Language: Description Definition) based on XML (eXtensible Markup Language: Extended Markup Language) language) (ISO/IEC 15938-2). In addition, Part B involves the transmission of metadata, including the binary format [MPEG-7BiM (Binary Format for MPEG-7)] (ISO/IEC 15938-1), fragmentation (fragment) model, encapsulation (encapsulation) and indexing (indexing) technology.

Figure 1 is a diagram showing the structure of TV-Anytime metadata, including program description metadata (Program Description Metadata) and user description metadata (User Description Metadata), program description metadata consists of content description metadata and instance (instance) description metadata data composition. Metadata for one program are associated with each other by an identifier called CRID (ContentReference Identifier, hereinafter referred to as "CRID").

Content description metadata is generated by the content creator (Content Creator), including program title, category, summary, critics' comments, etc. The instance description metadata is generated by the content provider (ContentProvider), including location (Location) (playing time, channel, URL, etc.), usage rule (usage rule), delivery parameter (delivery parameter), etc. Finally, user description data includes user preferences, usage history, personal bookmarks, etc., which are generated by users.

In order to provide bidirectional metadata data services via a round-trip path, the TV-Anytime standard defines two types of metadata web services, remote procedures for well-defined behavior and for input-output collections. In the XML (Extensible Markup Language)-based WSDL (Web Service Description Language, World Wide Web Service Description Language) standard, the above-mentioned remote program operates with the Simple Object Access Protocol (SOAP: Simple Object Access Protocol, hereinafter referred to as "SOAP") To define the shape, there is a 'get_Data' operation for metadata retrieval and a 'submit_Data' operation for user description presentation. Furthermore, the above-mentioned SOAP protocol is an XML communication protocol capable of accessing objects (Object) in a distributed environment.

The request (Request)/response (Response) type used in the TV-Anytime metadata service is defined in the namespace of "urn:tva:transport:2002", and the namespace is used as a Verification tools are provided. Types defined in metadata specifications and content referencing standards are referenced in the transport namespace. The schema fragment (Schema fragment) is defined in the above namespace, and the provider of the namespace is defined as 'tns:' in the schema fragment. The complete XML schema file is tva_transport_types_v10.xsd.

1. get_Data operation

The get_Data operation provides functionality for a client to retrieve TV-Anytime data from a server for a program or group of programs. An example of the functions that the TV-Anytime metadata provider can provide by using the get_Data operation is as follows.

- Using the CRID list to return the content reference data for the CRID.

- Returns the TV-Anytime metadata for the CRID using the CRID list.

-Accept queries for specific metadata attributes (Attribute) (for example, genre, actor, etc.), and return the corresponding program.

—Respond to the query for a specific time or a specific channel, and return the corresponding program.

Referring to Figure 2 in relation to the action of the get_Data operation, the client (Client) of the TV-Anytime service transmits the SOAP request information [get_Data() Request] based on the get_Data operation to the metadata service server through the Internet (IP Network) (Metadata Service Server). At this time, the get_Data operation supports all query types in principle, and provides a wide range of queries for metadata constraints. Then, the metadata service server returns the query result value of the SOAP request information through the SOAP response information [get_Data() Request].

A. Request Format (Request Format)

As shown in Figure 3, in the get_Data operation, the request format specifies three types of parameters in the client, and the element type returned as the query (retrieval) result value is specified as the request table (Request Tables) type.

Figure 4 is an example of specifying the returned request table type as ClassificationSchemeTable, ProgramInformationTable, GroupInformationTable, CreditsInformationTable, ProgramLocationTable, ServiceInformationTable, ProgramReviewTable, SegmentInformationTable, etc. as a query result.

B. Response Format

The response format of the get_Data operation is shown in Figure 5. For elements (TVAMain, ContentReferencingTable, InvalidFragments), which contain 0 or more than 1 XML instance document, the query result value is returned according to the requested table type in the request format.

2. submit_Data operation

Transmittable data based on the submit_Data operation is limited to data defined in an anonymous configuration data set generated by an intelligent agent based on usage (usage) service and content or by manual writing in the technical standard of Phase I of TV-Anytime. The TV-Anytime forum respects and embraces the basic rights of all users and providers, including the basic rights of privacy of content users, and the legal rights of all participants such as content producers, providers, and service providers.

3. The get_Data operation using user information

Now, in TV-Anytime, according to 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 corresponding result to the user.

The user information provided to the service agent in this way can be used according to the policy of the service provider, for example, the user information collected in a specific period can be used, or the overall user information can be used. In the case where user information is used according to the policy of the service agent, there is an advantage of providing greater convenience to the user. However, if the user does not need the service of the service agency, that is, when the service result of the service agency based on the existing accumulated personal information is not suitable, there is no method for the user to delete his own user information. .

Furthermore, since the processing method of user metadata completely depends on the algorithm of the service provider, the user cannot interfere with the method of using his/her own information at all, and thus may be hesitant to use the two-way metadata service.

Contents of the invention

The object of the present invention is to solve these problems by providing a method for deleting user information transmitted to a metadata server or service agent through a submit_Data operation, enabling users to have minimal control over their own information.

According to one aspect of the present invention, there is provided a method for deleting user metadata managed in a TV-Anytime metadata server through a SOAP operation, comprising: (a) a step of providing a SOAP delete operation, providing elements of a SOAP delete operation type, the element of the SOAP delete operation includes at least the first sub-element for specifying the user identification information; (b) the step of receiving the element of the SOAP delete operation specifying the user identification information from the user's client; (c) according to The received user identification information of the SOAP delete operation element identifies the user, and deletes the user metadata of the identified user.

At this time, the step of transmitting the deletion result of the step (c) to the client may also be included. In addition, the element of the SOAP delete operation defined in the step (a) also includes a second sub-element for specifying the delete condition, and in the step (c), delete the element corresponding to the received element of the SOAP delete operation 2 The user information corresponding to the deletion condition specified by the sub-element.

According to other aspects of the present invention, there is provided a method for deleting non-anonymous user metadata managed in a TV-Anytime metadata server through a SOAP operation, comprising: (e) a step of providing a SOAP delete operation, the request element of which SOAP delete operation Contains elements for inputting the start point and end point of the non-anonymous user metadata to be deleted, and the object table element for inputting the table to be deleted, and the response element contains the version information (ServiceVersion) of the metadata function description and the reception result; (f) the client The terminal inputs the starting point, end point and deletion object table of the non-anonymous user metadata to be deleted into the request element, and transmits it to the server; (g) the server responds to the reception of the request element, Steps of deleting the non-anonymous user metadata between the start point and the end point from the delete object table, inputting the result and version information into the response element, and sending it to the client.

According to the present invention, by limiting the table including user information to the uppermost layer and the second upper layer of the above-mentioned extended user description type, the delete operation can be easily realized.

Description of drawings

Fig. 1 is a structure diagram of TV-Anytime metadata.

FIG. 2 is a general action concept diagram of the get_Data operation.

Fig. 3 is a diagram showing a request format of a conventional get_Data operation.

FIG. 4 is an illustration diagram of specifying the request table type that can be returned as a query result in the existing get_Data operation.

FIG. 5 is a diagram showing a response format of a conventional get_Data operation.

Fig. 6 is a conceptual diagram showing the operation of the clear_personal_Data operation of the present invention.

Fig. 7 is a diagram showing a request format and a response format of the clear_personal_Data operation according to the first embodiment of the present invention.

FIG. 8 is an illustration showing a request format of a SOAP operation (clear_personal_Data) for deleting non-anonymous user metadata according to the second embodiment of the present invention.

FIG. 9 is an illustration showing a response format of a SOAP operation (clear_personal_Data) for deleting non-anonymous user metadata according to the second embodiment of the present invention.

FIG. 10 is an illustration showing a request format of a SOAP operation (clear_personal_Data) for deleting non-anonymous user metadata according to the third embodiment of the present invention.

Detailed ways

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

FIG. 6 is a diagram showing the concept of the clear_personal_Data operation provided for deleting user information in the present invention.

Referring to Fig. 6, clear_personal_Data () is the operation of deleting the user information transmitted to the two-way server, and the client sends the SOAP information including the period to be deleted and the user identification information (UserIdentifier) to the service agent of the metadata server through clear_personal_Data (), Internet is available. At this time, as a policy for deleting user information, it is possible to i) delete user information (user metadata) transmitted before a specific date on the basis of a specific date, or ii) delete all user information transmitted. Then, the service agent transmits the deletion result (clear_personal_Result) of the user information to the client.

FIG. 7 defines the request format and response format of the clear_personal_Data operation in the first embodiment of the present invention.

Referring to FIG. 7 , if roughly distinguished, clear_personal_Data() has elements of dateFrom, dateTo, and UserIdentifier. The dateFrom element and the dateTo element indicate the date of the user information to be deleted, and the UserIdentifier element is used to identify the corresponding 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, when deleting user data from March 6, 2003 to July 8, 2004, the value of dateFrom is 20030306, and the value of dateTo is 20040708. The dateFrom and dateTo elements are respectively set to minOccurs='0' and maxOccurs='unbounded', so only one of the values may be set, or neither value may be set. When only the value of dateTo is set, all user data before dateTo is deleted, and when only the value of dateFrom is set, all user data after dateFrom is deleted. When the values of dateFrom and dateTo are not set, all user data is deleted regardless of the period.

As shown in Figure 6, in association with the action of clear_personal_Data(), the result of the delete operation performed by the request of clear_personal_Data() is transmitted by clear_personal_Data_Result Type. At this time, the result value is selected from success (success), system error (system error), and no data (no data). Success indicates that the corresponding processing has been completed, and system error indicates that the deletion operation cannot be completed due to system problems. Furthermore, the absence of data indicates that there are no results that should be addressed.

FIG. 8 and FIG. 9 respectively show the request format and response format of the SOAP operation (clear_personal_Data) for deleting non-anonymous user metadata according to the second embodiment of the present invention.

Referring first to FIG. 8 , the clear_personal_Data operation in the second embodiment of the present invention is an operation for the user to delete the user information transmitted to the server through the above upload_personal_Data operation, and provides the following functions.

1. Delete the user information of a specific user transmitted during a specific period.

2. Only the selected table of the specific user transmitted during the specific period is deleted.

3. Delete all the information of the selected table for the specific user transferred.

4. Delete all information of a specific user.

Therefore, the input of the clear_personal_Data operation uses elements specifying a specific period of user information to be deleted, such as "TimeFrom" and "TimeTo". The TimeFrom element indicates the starting point of the user data to be deleted, and the TimeTo element indicates the end point of the user data to be deleted. In addition, these elements are respectively set to minOccurs='0', so only one of them may be set, or neither of them may be set. When only the value of TimeTo is set, all non-anonymous user data before TimeTo is deleted, and when only the value of TimeFrom is set, all user data after TimeFrom is deleted. When the values of TimeFrom and TimeTo are not set, all user data is deleted regardless of the period.

In addition, the clear_personal_Data operation contains another target table element ("TargetTable") for specifying the table to be deleted. The type of the above-mentioned target table element ("TargetTable") is defined as "clear_TableType" as shown in the figure, and as enumerated, the table containing user information is limited to the highest level and the second highest level of the above-mentioned extended user description type , the operation can be easily realized.

Then, referring to Figure 9, the response result of the clear_personal_Data operation, as explained in the upload_personal_Data operation, must contain the information for the current service version, and the result (status) of the delete operation selects a notification from among success, failure, and no data to the user.

Finally, referring to FIG. 10 showing a modified example of the clear_personal_Data operation in the third embodiment of the present invention, the TargetTable of clear_personal_Data can be expressed as tns:personalInformationTableType, and the TargetTable can include the TerminalInformationTable as user profile information additionally defined on the TV-Anytime Forum , NetworkInformationTable, NaturalEnvironmentInformationTable and other device association tables can be deleted through the clear_personal_Data operation. In addition, UsageHistory and UserPreference which are lower tables of UserInformationTable may be deleted.

As above, preferred embodiments of the present invention have been described, but these are for illustration, and those who have ordinary knowledge in the technical field to which the present invention pertains can make various modifications without departing from the spirit of the present invention. deformation or correction. Therefore, the protection scope of the present invention is not limited to the above-mentioned embodiments, but is determined by the scope of the claims.

By providing a method for deleting user information transmitted to a metadata server or service agent through submit_Data( ), it is applicable to a method enabling a user to have minimal control over his own information.

Claims (9)

1. A method for deleting user metadata based on SOAP operation, which deletes user metadata managed in a TV-Anytime metadata server through a Simple Object Access Protocol (hereinafter referred to as "SOAP") operation, characterized in that it includes: (a) providing a step of a SOAP delete operation, providing an element type of a SOAP delete operation, wherein the element of the SOAP delete operation includes at least a first sub-element for specifying user identification information; (b) receiving, from the client of the user, an element of a SOAP delete operation specifying user identification information; (c) A step of identifying a user according to the user identification information of the received SOAP delete operation element, and deleting user metadata of the identified user. 2. The method for deleting user metadata based on SOAP operation according to claim 1, further comprising the step of (d) transmitting the deletion result of step (c) to the client. 3. The method for deleting user metadata based on SOAP operation according to claim 2 is characterized in that the deletion result transmitted to the client in step (d) is selected from values indicating success, error, and no deleted object. 4. The method for deleting user metadata based on SOAP operation according to claim 1, characterized in that: The SOAP delete operation element defined in step (a) further includes a second sub-element for specifying a delete condition. In the step (b), user information corresponding to the deletion condition specified by the second sub-element of the received SOAP delete operation element is deleted. 5. The method for deleting user metadata based on SOAP operation according to claim 1, characterized in that: The SOAP delete operation element defined in step (a) further includes a third child element for specifying a date (dateFrom). In the step (c), user information transmitted after the date specified by the third child element of the received SOAP delete operation element is deleted. 6. The method for deleting user metadata based on SOAP operation according to claim 5, characterized in that: The SOAP delete operation element defined in step (a) further includes a fourth sub-element for specifying a date (dateTo). In the step (c), user information transmitted before the date specified by the fourth child element of the received SOAP delete operation element is deleted. 7. A method for deleting non-anonymous user metadata based on SOAP operation, which deletes non-anonymous user metadata managed in a TV-Anytime metadata server through SOAP operation, characterized in that it includes: (e) providing a step of a SOAP delete operation, wherein a request element of the SOAP delete operation includes elements for inputting a start point and an end point of non-anonymous user metadata to be deleted, and an object list element for inputting a list of deletion objects, and a response element includes version information (ServiceVersion) of the metadata function description and a receiving result; (f) The client inputs the starting point, end point and deletion object list of the non-anonymous user metadata to be deleted into the request element and transmits it to the server; (g) The server deletes the non-anonymous user metadata between the start point and the end point from the deletion object table in response to receiving the request element, inputs the result and version information into the response element, and transmits it to the client. 8. The method for deleting non-anonymous user metadata based on SOAP operation according to claim 7, characterized in that: The step (e) limits the deletion object table to the topmost layer and the second topmost layer of the extended user description type (ExtendedUser Description Type). 9. The method for deleting non-anonymous user metadata based on SOAP operation according to claim 7, characterized in that: The request element and response element of the SOAP delete operation provided in step (d) are defined as follows: <element name="clear_Personal_Data" type=" "tns:clear_Personal_DataType"/> <complexType name="clear_Personal_DataType"> <sequence>        <element name="TimeFrom" type="tva:TVATimeType" minOccurs="0" /> <element name="TimeTo" type="tva:TVATimeType" minOccurs="0"/> <element name="TargetTable" type="tns:clear_TableType" minOccurs="0" maxOccurs="unbounded"/> </sequence> </complexType> <simpleType name="clear_TableType"> <restriction base="string">       <enumeration value="All"/> <enumeration value="UserInformationTable"/> <enumeration value="UsageEnvironment"/> <enumeration value="BioGraphicInformation"/> <enumeration value="AccessibilityInformation"/><enumeration value="TerminalInformationTable"/><enumeration value="NetworkInformationTable"/><enumeration value="NaturalEnvironmentInformationTable"/></restriction></simpleType><element name="clear_Personal_Data_Result "type="tns:clear_Personal_Data_Result"/><complexType name="clear_Personal_Data_Result"><attribute name="serviceVersion" type="unsignedInt" use="required" <attribute name="status" use="required"> <simpleType>        <restriction base="string">                                    <enumeration value="success"/>                   <enumeration value="failed"/> ​<enumeration value="no data"/> </restriction> </simpleType> </attribute></complexType>.

Images