CN100444635C - Method for providing requested fields by get-data operation in TV-Anytime metadata service - Google Patents
Method for providing requested fields by get-data operation in TV-Anytime metadata service Download PDFInfo
- Publication number
- CN100444635C CN100444635C CNB2005101034330A CN200510103433A CN100444635C CN 100444635 C CN100444635 C CN 100444635C CN B2005101034330 A CNB2005101034330 A CN B2005101034330A CN 200510103433 A CN200510103433 A CN 200510103433A CN 100444635 C CN100444635 C CN 100444635C
- Authority
- CN
- China
- Prior art keywords
- request
- territory
- type
- metadata
- name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
- H04N21/2353—Processing of additional data, e.g. scrambling of additional data or processing content descriptors specifically adapted to content descriptors, e.g. coding, compressing or processing of metadata
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04H—BROADCAST COMMUNICATION
- H04H60/00—Arrangements for broadcast applications with a direct linking to broadcast information or broadcast space-time; Broadcast-related systems
- H04H60/68—Systems specially adapted for using specific information, e.g. geographical or meteorological information
- H04H60/73—Systems specially adapted for using specific information, e.g. geographical or meteorological information using meta-information
- H04H60/74—Systems specially adapted for using specific information, e.g. geographical or meteorological information using meta-information using programme related information, e.g. title, composer or interpreter
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/643—Communication protocols
- H04N21/64322—IP
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Library & Information Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
The invention provides a method capable of requesting a field unit to return end values and selectively returning metadata required by a client during the process of modified get_Data operation in order to provide personalized services. The method of the invention utilizes the get_Data operation to provide list area elements during the process of TV-Anytime metadata service and comprises the following steps that: (a) request filed types which can determine fields of a metadata sheet are added in types of inquest end values of the get_Data operation; (b) request information of the get_Data operation is received; (c) an inquest end value corresponding to a determined list area in an element of a request field type of the request information is extracted and then transmitted through response information of the get_Data operation under the condition that the request information comprises the element of the request field type of the determined inquest end value.
Description
Technical field
The present invention relates to the TV-Anytime service, relate in particular in the service of TV-Anytime metadata and utilized get_Data request of operating territory that method is provided.
Background technology
Recently, along with Digital Television is play the formalized of service, in multichannel, multimedia environment, more and more active about the Study on Technology that provides the program request type to play service.As an example,, be to be used to provide the Anytime standard specification of service as the TV-Anytime of international standard among the people.This Anytime service is a metadata of describing (description) information according to performing content, and the user stores desirable content by hobby (preference) information and described meta data match with self, watches in the time freely.
Metadata is as aforesaid descriptor about content, in TV-Anytime, be included in the description and EPG (electronic program guiding) information of the substance (content-based) that defines among the MPEG-7, make the user can easily retrieve and select desirable content.Metadata standard is made of two parts, part A has defined the form that is used for descriptive metadata, be pattern (Schema), applied flexibly (eXtensible Markup Language: (the Description Definition Language: Description Definition Language) (ISO/IEC 15938-2) of MPEG-7 DDL extending mark language) based on XML.In addition, part B relates to the transmission of metadata, comprises Binary Cell formula [MPEG-7BiM (Binary Format for MPEG-7)] (ISO/IEC 15938-1), fragmentation (fragment) model, encapsulationization (encapsulation) and index (indexing) skill and technique.
Fig. 1 is the figure of the structure of expression TV-Anytime metadata, comprise program description metadata (Program Description Metadata) and user description metadata (User DescriptionMetadata), the program description metadata is made of content description metadata and example (instance) descriptive metadata.Metadata at a program is interrelated by the identifier that is known as CRID (Content ReferenceIdentifier is hereinafter referred to as " CRID ").
The content description metadata is generated by content generation person (Content Creator), comprises program header, kind, summary, reviewer's comment etc.The case description metadata is generated by content provider (ContentProvider), comprises position (Location) (reproduction time, channel, URL etc.), service regeulations (usage rule), pass a parameter (delivery parameter) etc.At last, user description metadata comprises user preferences (user preference), uses historical (usagehistory), individual bookmark (personal bookmark) etc., is generated by the user.
In order to provide via the twocouese metadata data, services of trip path, the TV-Anytime standard definition 2 types metadata web services, they are to well-definedbehavior with to the teleprogram (remote procedure) of input and output set.At WSDL (Web Service Description Language based on XML (extending mark language), the web services descriptive language) in the standard, above-mentioned teleprogram is with Simple Object Access Protocol (SOAP:Simple Object Access Protocol, being called " SOAP " below) form of operation defines, and ' get_Data ' that is useful on metadata retrieval operates and is used for ' submit_Data ' operation that the user describes proposition.And above-mentioned soap protocol is can be in the XML communication protocol of access object under the decentralized environment (Object).
Request (Request)/response (Response) type of using in the service of TV-Anytime metadata defines in the name space of " urn:tva:transport:2002 ", and described name space is provided as being used for the instrument that various information are verified.According to metadata specification and the content reference defined type of (Content referencing) standard (type), be referenced at transmission (transport) name space.Schema fragment (Schemafragment) is defined within above-mentioned name space, and the supplier of name space is defined as ' tns: ' in schema fragment.The XML schema file is tva_transport_types_v10.xsd completely.
1.get_Data operation
Get_Data operation provides a kind of client of allowing at program or the program groups function from server retrieves TV-Anytime data.If illustration TV-Anytime metadata supplier utilize get_Data operation the function that can provide, then as follows.
-utilize CRID tabulation to return content comparable data at CRID.
-utilize CRID tabulation to return TV-Anytime metadata at CRID.
(corresponding program is returned in for example, kind, performer etc.) inquiry at specific metadata attributes (Attribute) in-acceptance.
-response is returned corresponding program at the inquiry of specific time or specific channel.
If with the action of get_Data operation explicitly with reference to Fig. 2, can find out that then the client (Client) of TV-Anytime service will send metadata service server (Metadata Service Server) to based on the SOAP solicited message [get_Data () Request] that get_Data operates by internet (IP Network).At this moment, support all query types on the get_Data operating principle, provide inquiry widely at the metadata restrictive condition.Then, the metadata service server is by the Query Result value of SOAP response message [get_Data () Request] return to described SOAP solicited message.
First. request form (Request Format)
As shown in Figure 3, in the get_Data operation, the request form is specified the parameter of 3 types in client, will be appointed as required list (Request Tables) type as the element type that inquiry (retrieval) end value is returned.
Fig. 4 is that the required list type of return is appointed as: the example of ClassificationSchemeTable, ProgramInformationTable, GroupInformationTable, CreditsInformationTable, ProgramLocationTable, ServiceInformationTable, ProgramReviewTable, SegmentInformationTable etc. with the result of inquiry.
Second. response format (Response Format)
The response format of get_Data operation as shown in Figure 5, at element (TVAMain, ContentReferencingTable, InvalidFragments), comprise 0 or, return the Query Result value according to the required list type of being asked in the request form more than or equal to 1 XML instance document.
2.submit_Data operation
The data that can transmit by submit_Data in the technical standard of the PhaseI of TV-Anytime, are limited to and are concentrating the data that define based on the configuration data of intelligent agent that uses (usage) service and content or the anonymity by manually writing generation.Respect and comprise all users and supplier's fundamental right in TV-Anytime forum, it comprises all participants' such as the privacy fundamental right of content user and content generation person, supplier, ISP legal right.
3. utilized the get_Data operation of user profile
Now, at TV-Anytime, according to the user metadata that transmits by submit_Data, the service broker carries out the get_Data operation at each agency by special algorithm, and sends accordingly result to user.
As mentioned above, now, results such as desirable table or TVAMain are returned in the get_Data operation that defines in TV-AnytimeSP006 by retrieval.The result for retrieval that is the get_Data operation is transmitted with list positions such as ' TVAMain ' or ' ProgramInformationTable ', ' GroupInformationTable ', ' ProgramLocationTable ', ' ServiceInformationTable ', ' CreditsInformationTable ', ' ProgramReviewTable ', ' SegmentInformationTable '.
On the one hand, set-top box (SetTop Box) by get_Data operation retrieval of content, provides corresponding metadata in two-way environment.But along with set-top box develops into home server, set-top box can be brought into play metadata service broker's function within the family.Use resembling portable media player in the terminal of Limited resources, the providing of metadata of accepting existing list position may cause the suitable wasting of resources.
For example, when supposing that the metadata that provides as user environment is title, kind, positional information, browsing information in portable media player, under the situation of inquiring about by existing get_Data operation, request ProgramInformationTable, ProgramLocationTable, ProgramReviewTable are as the request tabular value, and parsing (parsing) elements corresponding value or property value also is presented on the user interface (UI).Therefore, because the unnecessary metadata of each table causes transmitting its waste of network resources and the wasting of resources that is caused by the parsing operation of portable media player.
And the retrieval of the list position of existing get_Data operation does not need to show under the situation of whole metadata in client, exists because the problem of resolving the wasting of resources that causes again of the transmission of unnecessary metadata and client.
Summary of the invention
Problem of the present invention is to address these problems, and provides personalized service, and makes in the get_Data that was corrected operation, and return end value that can request domain unit can be returned the desirable metadata of client selectively.
According to first side of the present invention, a kind of TV-Anytime metadata method of servicing of the SOAP of utilization query manipulation is provided, comprising following step: (a) in described SOAP query manipulation, in the type of Query Result value, append the step of element of the request domain type (RequestedFieldsType) in the territory that can specify metadata table; (b) step of the solicited message of the described SOAP query manipulation of reception; (c) comprise under the situation of the described request field type element of being appointed as the Query Result value in described request information, the pairing Query Result value in territory of extraction metadata table of appointment in the request domain types of elements that described request information is comprised, and transmit the step of this Query Result value by the response message of described SOAP query manipulation.
At this moment, described SOAP operation also can be the get_Data operation, and the request domain types of elements of appending in described step (a) can comprise the request domain daughter element of the territory ID that specifies metadata table and the appointment request path daughter element at the path (Xpath) of described territory ID.
In addition, described step (c) exists in described Query Result value under the situation of the repeating data with identical territory ID, also can get rid of repeating data from described Query Result value.Described metadata also can be the program description metadata.
According to second side of the present invention, provide a kind of in the service of TV-Anytime metadata, the method that the territory unit that utilizes the get_Data operation to show is retrieved, comprising following step: (d) in the required list element (RequestedTables) of named list as the Query Result value of get_Data operation, the step that request domain (RequestedFields) element in the territory of the described table of appointment is appended as daughter element; (e) step of the described get_Data request of operating information of reception; (f) reception of response described request information is from by the specified table of described request table element, the step of territory specified in the described request field element as the extraction of Query Result value; (g) response message of operating by get_Data transmits the step of the described Query Result value that is drawn out of.
According to first side of the present invention, can ask the return end value of the territory unit of get_Data operation, can optionally return the desirable metadata of client.Promptly, the client of metadata service can receive the metadata query result with the territory unit of list position and/or table, can optionally only receive the desirable metadata of user thus, so can reduce the transmission of metadata and the load of resolving again of client significantly.In addition, the present invention also can bring into play above-mentioned advantage in common set-top box environment, can bring into play bigger effect in the resource-constrained client environment resemble the portable media player.
On the one hand, in first side of the present invention, for the territory unit with client-requested processes metadata, sometimes the processing that need append at server side, consider that it is big capacity environment that the service broker compares with client environment, so can reduce the processing time of client more significantly according to the present invention.
In addition,, appended the element of request domain type, thereby, also can specify to have the unit request domain element of specific territory ID as attribute even do not change the get_Data operation as the daughter element of required list according to the 2nd side of the present invention.Thus, have client and can ask to return end value with the territory unit of required list, optionally return the advantage of self desirable metadata.
Description of drawings
Fig. 1 is the structure chart of TV-Anytime metadata.
Fig. 2 is the general movement concept figure of get_Data operation.
Fig. 3 is the figure of the existing get_Data request of operating form of expression.
In the existing get_Data operation of Fig. 4, specified the illustration figure of the required list type that can be returned Query Result.
Fig. 5 is the figure of the response format of the existing get_Data operation of expression.
Fig. 6 is in the get_Data of first embodiment of the invention operation, is used to ask the illustration figure of the request domain type of Query Result.
Fig. 7 is the figure of the get_Data request of operating form of expression first embodiment of the invention.
Fig. 8 is the query case illustration figure of the get_Data operation of expression first execution mode of the present invention.
Fig. 9 is the response example illustration figure of the get_Data operation of expression first execution mode of the present invention.
Figure 10 is the movement concept figure of the get_Data operation of expression first embodiment of the invention.
Figure 11 is the illustration figure of the request domain type of second embodiment of the invention.
Figure 12 is in the second embodiment of the invention, the illustration figure of the required list type that the request domain types of elements of Figure 11 is added as daughter element.
Figure 13 is request by the required list element of the required list type of Figure 12 definition example illustration figure as the get_Data operation of return value.
Figure 14 is the illustration figure that the request domain type has been carried out the territory row type of distortion.
Figure 15 is to use the illustration figure of required list type of the territory row type of Figure 14.
The illustration figure that Figure 16 is to use the get_Data of the territory row type of Figure 14 to operate.
Embodiment
Below, the preferred implementation that present invention will be described in detail with reference to the accompanying.
Defined in the get_Data that the was corrected operation of first execution mode of the present invention at Fig. 6, be used to ask the request domain type of the Query Result of specific element or attribute unit.
In Fig. 6, the request domain type can be appended request domain element and 2 elements of request path element (RequestedXpath) as daughter element, described each element is designated as minOccurs=' 0 ', maxOccurs=' unbounded ', can carry out the inquiry to infinitely-great request domain element and request path element more than 0.
The request domain element has classification benchmark (Sort Criteria) as daughter element.The classification benchmark is represented the classification benchmark to Query Result, according to existing sorting technique, has territory ID as attribute.The value of territory ID becomes and will now, use the filed ID Type that defines in TV-Anytime as the territory ID of Query Result reception.
When utilizing the request domain element to inquire about, though also problem may take place, this be since a territory ID to a plurality of paths should be arranged.Under above-mentioned situation, the service broker of meta data server can transmit the data of whole repetitions or get rid of and repeat, and under the situation of identical TVAMian example, can transmit according to the Policy Choice ground of self.ISP's policy is followed in the transmission of the territory ID of this repetition.
For the policy that prevents described ISP cause ambiguous, the user can utilize request path unit usually ask the inquiry.Be that the request path element can utilize the grammer in path to specify the clean path in the territory that will ask.Request path element and above-mentioned request domain element similarly have the classification benchmark as daughter element, and have the path as attribute, so can set the value that is used to the inquire about property value (type) as the path.
Fig. 7 represents to have carried out in order to utilize above-mentioned request domain type the get_Data request of operating form of correction.
With reference to Fig. 7, below the required list element, appended the request field element.The request domain element uses the request domain type of Fig. 6, can utilize above-mentioned request domain element and request path element.
Below the example that utilizes described get_Data operation to inquire about is described.As shown in Figure 8, territory ID is ' tvaf:ServiceURL ' in user's (or client) request (inquiry) request domain element, and its value is ' tv: // 7 ' or ' tv: // 9 ' part.In addition, type as the Query Result value, the required list element is appointed as ' ProgramLocationTable ', the territory ID of request domain element is appointed as: ' tvaf:CRID ', ' tvaf:Genre ', ' tvaf:Title ', ' tvaf:ProgramURL ', ' tvaf:PublishedStart ', ' tvaf:PublishedDuration ', be appointed as the request path element: '/TVAMain/ProgramDescription/ProgramReviewTable/Review/Fre eText Review/FreeText Review/text () '.
Fig. 9 illustration to the response example of the query case of Fig. 8, search condition according to Fig. 8, territory ID is ' tvaf:CRID ', ' tvaf:Genre ', ' tvaf:Title ', ' tvaf:ProgramURL ', ' tvaf:PublishedStart ', ' tvaf:PublishedDuration ' among extraction and the return Program Information Table, and the request path element is the result for retrieval value of '/TVAMain/ProgramDescription/ProgramReviewTable/Review/Fre eText Review/FreeText Review/text () '.
If with the action of get_Data operation explicitly with reference to Figure 10, then in the TV-Anytime service, client will send the metadata service server to based on the SOAP solicited message [get_Data () Request] of get_Data operation by internet etc.Then, the metadata service server is by the Query Result value of SOAP response message [get_Data () Request] return to described SOAP solicited message.
Figure 11 shows the definition of the request domain type that is used to specify specific element and property value of the present invention's the 2nd execution mode.
As shown in the figure, the request domain type comprises 2 elements that are made of unit request domain and request path, and such request domain type also can be used as the daughter element of required list type and is added.
Described unit request domain and request path element are set at minOccurs=' 0 ', maxOccurs=' unbounded ' respectively, so can carry out the inquiry to infinitely-great unit request domain and request path more than 0.
The unit request domain has the classification benchmark as daughter element.The classification benchmark is represented the classification benchmark to Query Result, according to existing sorting technique.In addition, the request domain specified domain ID of unit is as attribute, and the value of this territory ID becomes will be as the territory ID of Query Result reception.Such territory ID uses the current territory ID type that defines in TV-Anytime.
When the unit's of utilization request domain is inquired about, owing to might have a plurality of paths by a territory ID, so problem takes place sometimes.Under above-mentioned situation, the service broker of meta data server can transmit whole repeating datas or get rid of and repeat, and under the situation of identical TVAMian example, can transmit according to the Policy Choice ground of self.ISP's policy is deferred in the transmission of the territory ID of this repetition.
At this moment, if utilize above-mentioned request path to inquire about, it is ambiguous to prevent that ISP's policy from causing.Be that the request path element can utilize the grammer in path to specify the clean path in the territory that will ask.Request path element and above-mentioned request domain element similarly have the classification benchmark as daughter element, and have the path as attribute.So can set the value that the property value (type) that is used for according to the path is inquired about.
Figure 12 illustrates the element of above-mentioned request domain type, i.e. the definition of the required list type that is added as daughter element of request domain element, and thus, can ask territory with the required list of expectation is that the return value of unit is as get_Data request of operating result.
As shown in the figure, the request domain element is the daughter element of required list type, can carry out inquiry at the infinitely-great request domain element more than 0 to 1 required list.
Figure 13 is request by the required list element of the required list type of Figure 12 definition example illustration figure as the get_Data operation of return value.
As shown in the figure, the required list element comprises respectively the request domain element at ' ProgramInformationTable ' and ' ProgramLocationTable '.Comprise at the request domain element of ' ProgramInformationTable ' in addition and be endowed 2 the unit request domain of territory ID as attribute, request ' tvaf:CRID ' and ' tvaf:Genre ' is as return value.In addition, the request domain element of ' ProgramLocationTable ' comprises and is endowed ' tvaf:ProgramURL ' unit request domain as attribute, the return of request corresponding field.Thus, the service broker who has accepted the inquiry of Figure 12 can only retrieve the territory of client-requested and return its result in ' ProgramInformationTable ' and ' ProgramLocationTable ' selectively.
Figure 14 to Figure 16 shows respectively and the request domain type has been carried out the territory row type (FieldList Type) of distortion and utilized its required list type and the variation of get_Data operation.As shown in the figure, the request domain type can only change the title of respective element and use on the row type of territory, at this moment, request domain, request path element can be that IdentificationByFieledId, IdentificationByXPath use with Name Change.In addition, under situation about using, do not need the classification benchmark element of request domain type as territory row type.
More than, preferred implementation of the present invention is illustrated, but these are in order to carry out illustration, so long as have the people of common knowledge in the technical field of the invention, can in the scope that does not break away from thought of the present invention, make various modifications or amendments.Therefore, protection scope of the present invention is not limited to above-mentioned execution mode, and is determined by the scope of claim.
Be applicable to the operation at the get_Data that was corrected that is used for providing personalized service, return end value that can request domain unit can be returned in the method for the desirable metadata of client selectively.
Claims (14)
1. a TV-Anytime metadata provides method, and it utilizes Simple Object Access Protocol is that SOAP comes query manipulation that TV-Anytime is provided metadata, it is characterized in that, comprising:
(a) in the type of the Query Result value of described SOAP query manipulation, append the step of element of the request domain type in the territory that can specify metadata table;
(b) step of the solicited message of the described SOAP query manipulation of reception;
(c) comprise under the situation of element of the described request field type of being appointed as the Query Result value in described request information, the pairing Query Result value in territory of extraction metadata table of appointment in the element of the request domain type that described request information is comprised, and transmit the step of this Query Result value by the response message of described SOAP query manipulation.
2. TV-Anytime metadata according to claim 1 provides method, it is characterized in that, described SOAP query manipulation is the get_Data operation.
3. TV-Anytime metadata according to claim 1 provides method, it is characterized in that, the element of the request domain type of appending in described step (a) comprise the territory of specifying metadata table territory ID the request domain daughter element and specify request path daughter element at the path of described territory ID.
4. TV-Anytime metadata according to claim 1 provides method, it is characterized in that, described step (c) exists under the situation of the repeating data with identical territory ID in described Query Result value, gets rid of repeating data from described Query Result value.
5. TV-Anytime metadata according to claim 1 provides method, it is characterized in that, described metadata is the program description metadata.
6. TV-Anytime metadata according to claim 5 provides method, it is characterized in that, described step (c) exists under the situation of the repeating data with identical territory ID in described Query Result value, gets rid of repeating data from described Query Result value.
7. TV-Anytime metadata according to claim 5 provides method, it is characterized in that, the element of the request domain type of appending in described step (a), comprise the territory of specifying metadata table territory ID the request domain daughter element and specify request path daughter element at the path of described territory ID.
8. TV-Anytime metadata according to claim 7 provides method, it is characterized in that, described step (c) exists under the situation of the repeating data with identical territory ID in described Query Result value, gets rid of repeating data from described Query Result value.
9. TV-Anytime metadata according to claim 7 provides method, it is characterized in that, described request field type element definition is 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>
10. a TV-Anytime metadata provides method, in the service of TV-Anytime metadata, utilizes the get_Data operation that territory unit's retrieval of table is provided, and it is characterized in that, comprising:
(d) in the required list element of named list as the Query Result value of get_Data operation, the step that the request domain element in the territory of the described table of appointment is appended as daughter element;
(e) step of the described get_Data request of operating information of reception;
(f) according to the reception of described request information, from the specified table of described request table element, the step that appointed territory in the described request field element is extracted out as the Query Result value;
(g) response message of operating by get_Data transmits the step of the described Query Result value that is drawn out of.
11. TV-Anytime metadata according to claim 10 provides method, it is characterized in that the request domain element that is added in described step (d) comprises the unit request domain element of the territory ID in the territory that will retrieve as the appointment of daughter element.
12. TV-Anytime metadata according to claim 11 provides method, it is characterized in that, in described step (d), the territory ID that specifies the territory that will retrieve is given as described unit request domain attribute of an element.
13. TV-Anytime metadata according to claim 12 provides method, it is characterized in that, at the request domain element that described step (d) is appended, comprises the request path element in the path in the territory that will retrieve as the appointment of daughter element.
14. TV-Anytime metadata according to claim 13 provides method, it is characterized in that, the type definition of described request field element is 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>。
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020040074548 | 2004-09-17 | ||
| KR1020040074548A KR100590029B1 (en) | 2004-09-17 | 2004-09-17 | Method of providing table field elements by get_data operation in tv-anytime metadata service |
| KR1020050025885 | 2005-03-29 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1750640A CN1750640A (en) | 2006-03-22 |
| CN100444635C true CN100444635C (en) | 2008-12-17 |
Family
ID=36605867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101034330A Expired - Fee Related CN100444635C (en) | 2004-09-17 | 2005-09-15 | Method for providing requested fields by get-data operation in TV-Anytime metadata service |
Country Status (2)
| Country | Link |
|---|---|
| KR (1) | KR100590029B1 (en) |
| CN (1) | CN100444635C (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100590030B1 (en) * | 2004-09-17 | 2006-06-19 | 전자부품연구원 | Method using an soap operation for leaving out user metadata managed by tv-anytime metadata server |
| KR100737801B1 (en) | 2004-12-30 | 2007-07-10 | 전자부품연구원 | Method for delivering non-anonymous user metadata using an soap operation |
| KR100697536B1 (en) * | 2005-11-08 | 2007-03-20 | 전자부품연구원 | Method of providing personal information based search by get_data operation in tv-anytime service |
| KR100889744B1 (en) * | 2006-12-08 | 2009-03-24 | 한국전자통신연구원 | IPTV supplementary service control system and method |
| KR100936241B1 (en) * | 2007-09-03 | 2010-01-12 | 전자부품연구원 | Method for searching content by a soap operation |
| KR100936240B1 (en) * | 2007-09-03 | 2010-01-12 | 전자부품연구원 | Method for searching content by a soap operation |
| WO2009069923A2 (en) | 2007-11-30 | 2009-06-04 | Samsung Electronics Co., Ltd. | Method and apparatus for searching for iptv service relay devices and method and apparatus for interacting with devices |
| CN101939985B (en) * | 2008-02-05 | 2013-04-03 | 三星电子株式会社 | A method and device for sending and receiving metadata for an application providing an IPTV service |
| WO2009120030A2 (en) | 2008-03-28 | 2009-10-01 | 삼성전자 주식회사 | Data receiving method and device for applications providing an iptv communications service |
| KR101661210B1 (en) | 2008-07-24 | 2016-09-29 | 삼성전자주식회사 | Method and apparatus for performing IPTV communication service |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003077558A2 (en) * | 2002-03-14 | 2003-09-18 | Koninklijke Philips Electronics N.V. | Improved finding of tv anytime web services |
| WO2004010334A1 (en) * | 2002-07-23 | 2004-01-29 | Samsung Electronics Co., Ltd. | Index structure of metadata, method for providing indices of metadata, and metadata searching method and apparatus using the indices of metadata |
| US20040208480A1 (en) * | 2003-04-18 | 2004-10-21 | Samsung Electronics Co., Ltd. | Method and apparatus for converting digital content metadata and network system using the same |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6085186A (en) | 1996-09-20 | 2000-07-04 | Netbot, Inc. | Method and system using information written in a wrapper description language to execute query on a network |
| US7567953B2 (en) * | 2002-03-01 | 2009-07-28 | Business Objects Americas | System and method for retrieving and organizing information from disparate computer network information sources |
-
2004
- 2004-09-17 KR KR1020040074548A patent/KR100590029B1/en not_active IP Right Cessation
-
2005
- 2005-09-15 CN CNB2005101034330A patent/CN100444635C/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003077558A2 (en) * | 2002-03-14 | 2003-09-18 | Koninklijke Philips Electronics N.V. | Improved finding of tv anytime web services |
| WO2004010334A1 (en) * | 2002-07-23 | 2004-01-29 | Samsung Electronics Co., Ltd. | Index structure of metadata, method for providing indices of metadata, and metadata searching method and apparatus using the indices of metadata |
| US20040208480A1 (en) * | 2003-04-18 | 2004-10-21 | Samsung Electronics Co., Ltd. | Method and apparatus for converting digital content metadata and network system using the same |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1750640A (en) | 2006-03-22 |
| KR20060025748A (en) | 2006-03-22 |
| KR100590029B1 (en) | 2006-06-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100444635C (en) | Method for providing requested fields by get-data operation in TV-Anytime metadata service | |
| JP4280737B2 (en) | Request field providing method using get_Data operation in TV-Anytime metadata service | |
| CN102123145B (en) | Method for delivering non-anonymous user metadata using a SOAP operation | |
| US20050131906A1 (en) | Method and apparatus for managing data written in markup language and computer-readable recording medium for recording a program | |
| JP4704157B2 (en) | Method of deleting user metadata managed in TV-Anytime metadata server by SOAP operation | |
| CN101217649B (en) | Method, server and terminal to determine correlating programs in different networks | |
| CN1963817B (en) | Method of providing user information-based search using get_data operation | |
| KR100679314B1 (en) | Method of publishing tv-anytime metadata by a soap operation | |
| KR100696949B1 (en) | Method of providing requestedfieldstype by get_data operation in tv-anytime service | |
| CN1798150A (en) | Method for delivering non-anonymous user metadata using a SOAP operation in tv-anytime metadata service | |
| WO2006010107A1 (en) | Metadata service | |
| JP5114547B2 (en) | Inquiry content service method using SOAP operation | |
| CN1767534B (en) | Method for deleting user metadata managed by a TV-Anytime metadata server | |
| KR100590028B1 (en) | Method of creating and managing content lists for portable media players | |
| US20100287181A1 (en) | Method for Searching Content by a Soap Operation | |
| Davis et al. | On-demand partial schema delivery for multimedia metadata | |
| EP2069978A2 (en) | Method for searching content by a soap operation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: INTELLIGENCE DISCOVER CORP. Free format text: FORMER OWNER: ELECTRO-COMPONENTS INST. Effective date: 20150626 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20150626 Address after: Seoul, South Korea Patentee after: INDITECH KOREA CO., LTD. Address before: Gyeonggi Do, South Korea Patentee before: Electro-Components Institute |
|
| C56 | Change in the name or address of the patentee | ||
| CP01 | Change in the name or title of a patent holder |
Address after: Seoul, South Korea Patentee after: Neo Lab Convergence Inc. Address before: Seoul, South Korea Patentee before: INDITECH KOREA CO., LTD. |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20081217 Termination date: 20180915 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |