Abstract:
A method of decoding a content bitstream including at least one of an audio bitstream and a video bitstream is disclosed. This invention comprises: (a) receiving said content bitstream; (b) receiving a respective watermark associated with different portions of said content bitstream; (c) decoding meta-data encoded within each of said respective watermark associated with said different portions of said content bitstream; (d) wherein a first said meta-data encoded within a first one of said watermarks includes content and signal server communication information.

Description:
TECHNICAL FIELD 
       [0001]    The present invention relates generally to a system with audio-visual content watermarking. 
       BACKGROUND ART 
       [0002]    In many digital broadcasting systems, a broadcasting station transmits both streams of audio-visual (AV) content and one or more enhanced service data. The enhanced service data may be provided with the AV content to provide information and services or may be provided separately from the AV content to provide information and services. 
         [0003]    In many broadcasting environments, the audio-visual content and the one or more enhanced service data is not received directly by an AV presentation device from the broadcasting station. Rather the AV presentation device, such as a television, is typically connected to a broadcast receiving device that receives the audio-visual content and the one or more enhanced service data in a compressed form and provides uncompressed audio-visual content to the AV presentation device. 
       SUMMARY OF INVENTION 
     Technical Problem 
       [0004]    In some broadcasting environments, the broadcast receiving device receives audio-visual content from a server (sometimes referred to as a Multichannel Video Programming Distributor (MVPD)). The MVPD receives an audio-visual broadcast signal from the broadcasting station, extracts content from the received audio-visual broadcast signal, converts the extracted content into audio-visual signals having a suitable format for transmission, and provides the converted audio-visual signals to the broadcast receiving device. During the conversion process, the MVPD often removes the enhanced service data provided from the broadcasting station or may incorporate a different enhanced service data that is provided to the broadcast receiving device. In this manner, the broadcasting station may provide the audio-visual content with enhanced service data, but the enhanced service data, if any, that is ultimately provided to the AV presentation device and/or the broadcast receiving device may not be the same as that provided by the broadcasting station. 
         [0005]    Since the broadcast receiving device extracts audio-visual content from the signal received from the MVPD and provides only uncompressed audio-visual data to the AV presentation device, only enhanced service data provided to the broadcast receiving device is available. Furthermore, the same enhanced service data provided by the broadcasting station may not be provided to the broadcast receiving device and/or AV presentation device. 
       Solution to Problem 
       [0006]    According to the present invention, there is provided a method of decoding a content bitstream including at least one of an audio bitstream and a video bitstream, comprising: 
         [0007]    (a) receiving said content bitstream; 
         [0008]    (b) receiving a respective watermark associated with different portions of said content bitstream; 
         [0009]    (c) decoding meta-data encoded within each of said respective watermark associated with said different portions of said content bitstream; 
         [0010]    (d) wherein a first said meta-data encoded within a first one of said watermarks includes content and signal server communication information. 
         [0011]    According to the present invention, there is provided a method of decoding a content bitstream including at least one of an audio bitstream and a video bitstream, comprising: 
         [0012]    (a) receiving said content bitstream; 
         [0013]    (b) receiving a respective watermark associated with different portions of said content bitstream; 
         [0014]    (c) decoding meta-data encoded within each of said respective watermark associated with said different portions of said content bitstream; 
         [0015]    (d) wherein a first said meta-data encoded within a first one of said watermarks includes at least one of: 
         [0016]    (i) a location of a content server; 
         [0017]    (ii) a folder on said content server. 
       Advantageous Effects of Invention 
       [0018]    The foregoing and other objectives, features, and advantages of the invention will be more readily understood upon consideration of the following detailed description of the invention, taken in conjunction with the accompanying drawings. 
     
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0019]      FIG. 1  illustrates a system with enhanced service information. 
           [0020]      FIG. 2  illustrates another system with enhanced information. 
           [0021]      FIG. 3  illustrates a data flow for a system with enhanced information. 
           [0022]      FIG. 4  illustrates another system with enhanced information. 
           [0023]      FIG. 5  illustrates a watermark payload. 
           [0024]      FIG. 6  illustrates another watermark payload. 
           [0025]      FIG. 7  illustrates relationships between watermark payloads. 
           [0026]      FIG. 8  illustrates relationships between watermark payloads. 
           [0027]      FIG. 9  illustrates relationships between watermark payloads. 
           [0028]      FIG. 10  illustrates another system with enhanced information. 
           [0029]      FIG. 11  illustrates obtaining synchronization and maintaining synchronization. 
           [0030]      FIG. 12  illustrates another watermark payload. 
           [0031]      FIG. 13  illustrates SDO Private Data. 
           [0032]      FIG. 14  illustrates metadata encapsulated within SDO Private data as SDO Payload using cmdID&#39;s. 
       
    
    
     DESCRIPTION OF EMBODIMENTS 
       [0033]    Referring to  FIG. 1 , the system may include a content source  100 , a content recognizing service providing server  120 , a multi-channel video program distributor  130 , an enhanced service information providing server  140 , a broadcast receiving device  160 , a network  170 , and an AV presentation device  180 . 
         [0034]    The content source  100  may correspond to a broadcasting station that broadcasts a broadcast signal including one or more streams of audio-visual content (e.g., audio and/or video). The broadcast signal may further include enhanced services data and/or signaling information. The enhanced services data preferably relates to one or more of the audio-visual broadcast streams. The enhanced data services may have any suitable format, such as for example, service information, metadata, additional data, compiled execution files, web applications, Hypertext Markup Language (HTML) documents, XML documents, Cascading Style Sheet (CSS) documents, audio files, video files, ATSC 2.0 or future versions contents, and addresses such as Uniform Resource Locator (URL). 
         [0035]    The content recognizing service providing server  120  provides a content recognizing service that allows the AV presentation device  180  to recognize content on the basis of audio-visual content from the content source  100 . The content recognizing service providing server  120  may optionally modify the audio-visual broadcast content, such as by including a watermark. 
         [0036]    The content recognizing service providing server  120  may include a watermark inserter. The watermark inserter may insert watermarks which are designed to carry enhanced services data and/or signaling information, while being imperceptible or at least minimally intrusive to viewers. In other cases a readily observable watermark may be inserted (e.g., readily observable may be readily visible in the image and/or readily observable may be readily audible in the audio). For example, the readily observable watermark may be a logo, such as a logo of a content provider at the upper-left or upper-right of each frame. 
         [0037]    The content recognizing service providing server  120  may include a watermark inserter that modifies the audio-visual content to include a non-readily observable watermark (e.g., non-readily observable may be readily non-visible in the image and/or non-readily observable may be non-readily audible in the audio). For example, the non-readily observable watermark may include security information, tracking information, data, or otherwise. Another example includes the channel, content, timing, triggers, and/or URL information. 
         [0038]    The multi-channel video program distributor  130  receives broadcast signals from one or more broadcasting stations and typically provides multiplexed broadcast signals to the broadcast receiving device  160 . The multi-channel video program distributor  130  may perform demodulation and channel decoding on the received broadcast signals to extract the audio-visual content and enhanced service data. The multi-channel video program distributor  130  may also perform channel encoding on the extracted audio-visual content and enhanced service data to generate a multiplexed signal for further distribution. The multi-channel video program distributor  130  may exclude the extracted enhanced service data and/or may include a different enhanced service data. 
         [0039]    The broadcast receiving device  160  may tune to a channel selected by a user and receive an audio-visual signal of the tuned channel. The broadcast receiving device  160  typically performs demodulation and channel decoding on the received signal to extract desired audio-visual content. The broadcast receiving device  160  decodes the extracted audio-visual content using any suitable technique, such as for example, H.264/Moving Picture Experts Group-4 advanced video coding (MPEG-4 AVC), H.265/High efficiency video coding (HEVC), Dolby AC-3, and Moving Picture Experts Group-2 Advanced Audio Coding (MPEG-2 AAC). The broadcast receiving device  160  typically provides uncompressed audio-visual content to the AV presentation device  180 . 
         [0040]    The enhanced service information providing server  140  provides enhanced service information to audio-visual content in response to a request from the AV presentation device  180 . 
         [0041]    The AV presentation device  180  may include a display, such as for example, a television, a notebook computer, a mobile phone, and a smart phone. The AV presentation device  180  may receive uncompressed (or compressed) audio-visual or video or audio content from the broadcast receiving device  160 , a broadcast signal including encoded audio-visual or video or audio content from the content source  100 , and/or encoded or decoded audio-visual or video or audio content from the multi-channel video program distributor  130 . In some cases the uncompressed video and audio, may be received via an HDMI cable. The AV presentation device  180  may receive from the content recognizing service providing server  120  through the network  170 , an address of an enhanced service relating to the audio-visual content from the enhanced service information providing server  140 . 
         [0042]    It is to be understood that the content source  100 , the content recognizing service providing server  120 , the multi-channel video program distributor  130 , and the enhanced service information providing server  140  may be combined, or omitted, as desired. It is to be understood that these are logical roles. In some case some of these entities may be separate physical devices. In other cases some of these logical entities may be embodied in same physical device. For example, the broadcast receiving device  160  and AV presentation device  180  may be combined, if desired. 
         [0043]    Referring to  FIG. 2 , a modified system may include a watermark inserter  190 . The watermark inserter  190  may modify the audio-visual (e.g., the audio and/or video) content to include additional information in the audio-visual content. The multi-channel video program distribution  130  may receive and distribute a broadcast signal including the modified audio-visual content with the watermark. 
         [0044]    The watermark inserter  190  preferably modifies the signal in a manner that includes additional information which is non-readily observable (e.g., visually and/or audibly) in the form of digital information. In non-readily observable watermarking, the inserted information may be readily identifiable in the audio and/or video. In non-readily observable watermarking, although information is included in the audio-visual content (e.g., the audio and/or video), a user is not readily aware of the information. 
         [0045]    One use for the watermarking is copyright protection for inhibiting illegal copying of digital media. Another use for the watermarking is source tracking of digital media. A further use for the watermarking is descriptive information for the digital media. Yet another use for the watermarking is providing location information for where additional content may be received associated with the digital media. Yet another use is to identify content and content source that is being viewed and the current time point in the content, and then allowing the device to access the desired additional functionality via an Internet connection. The watermark information is included within the audio-visual content itself, as distinguished from, meta-data that is delivered along with the audio-visual content. By way of example, the watermark information may be included by using a spread spectrum technique, a quantization technique, and/or an amplitude modulation technique. 
         [0046]    Referring to  FIG. 3 , an exemplary data flow is illustrated. The content source  100  transmits a broadcast signal including at least one audio-visual content and an enhanced service data  201  to the watermark inserter  190 . 
         [0047]    The watermark inserter  190  receives the broadcast signal that the content source  100  provides and includes a readily observable and/or a non-readily observable watermark in the audio-visual content. The modified audio-visual content with the watermark is provided together with enhanced service data  203  to the MVPD  130 . 
         [0048]    The content information associated with the watermark may include, for example, identification information of a content provider that provides audio-visual content, audio-visual content identification information, time information of a content section used in content information acquisition, names of channels through which audio-visual content is broadcasted, logos of channels through which audio-visual content is broadcasted, descriptions of channels through which the audio-visual content is broadcasted, a usage information reporting period, the minimum usage time for usage information acquisition, statistics for sporting events, display of useful information, widgets, applications, executables, and/or available enhanced service information relating to audio-visual content. 
         [0049]    The acquisition path of available enhanced service data may be represented in any manner, such an Internet Protocol based path or Advanced Television Systems Committee—Mobile/Handheld (ATSC M/H). 
         [0050]    The MVPD  130  receives broadcast signals including watermarked audio-visual content and enhanced data service and may generate a multiplexed signal to provide it  205  to the broadcast receiving device  160 . At this point, the multiplexed signal may exclude the received enhanced service data and/or may include a different enhanced service data. 
         [0051]    The broadcast receiving device  160  may tune to a channel that a user selects and receives signals of the tuned channel, demodulates the received signals, performs channel decoding and audio-video decoding on the demodulated signals to generate an uncompressed audio-video content, and then, provide  206  the uncompressed audio-visual content to the AV presentation device  180 . The content source  100  may also broadcast  207  the audio-visual content through a channel to the AV presentation device  180 . The MVPD  130  may directly transmit  208  a broadcast signal including audio-visual content to the AV presentation device  180  without going through the broadcast receiving device  160 . In yet another case some of the AV information may be sent to the AV presentation device  180  over a broadband connection. In some cases this may be managed broadband connection. In another case it may be unmanaged broadband connection. 
         [0052]    The AV presentation device  180  may receive uncompressed (or compressed) audio-visual content from the broadcast receiving device  160 . Additionally, the AV presentation device  180  may receive a broadcast signal through a channel from the content source  100 , and then, may demodulate and decode the received broadcast signal to obtain audio-visual content. Additionally, the AV presentation device  180  may receive a broadcast signal from the MVPD  130 , and then, may demodulate and decode the received broadcast signal to obtain audio-visual content. The AV presentation device  180  (or broadcast receiving device  160 ) extracts watermark information from one or more video frames or a selection of audio samples of the received audio-visual content. The AV presentation device  180  may use the information obtained from the watermark(s) to make a request  209  to the enhanced service information providing server  140  (or any other device) for additional information. The enhanced service information providing server  140  may provide, in response thereto a reply  211 . 
         [0053]    Referring to  FIG. 4 , a further embodiment includes the content source  100  that provides audio-visual content together with enhanced service data (if desired) to the watermark inserter  190 . In addition, the content source  100  may provide a code  300  to the watermark inserter  190  together with the audio-visual content. The code  300  may be any suitable code to identify which, among a plurality of audio-visual streams, should be modified with the watermark. For example code=1 may identify the first audio-visual stream, code=2 may identify the second audio-visual stream, code=3 may identify ABC, code=4 may identify NBC, etc. The code may include temporal location information within the audio-visual content. The code may include other metadata, if desired. 
         [0054]    The watermarked audio-visual content and associated data, signaling is provided by the watermark inserter  190  to the MVPD, which in turn may provide the watermarked compressed audio-visual content to the broadcast receiving device  160  (e.g., a set top box). The broadcast receiving device  160  may provide watermarked audio-visual content (e.g., typically uncompressed) to the AV presentation device  180 . The AV presentation device  180  may include a watermark capable receiver  310  together with a watermark client  320 . The watermark capable receiver  310  is suitable to detect the existence of the watermark within the audio-visual content, and to extract the watermark data from within the audio-visual content. The watermark client  320  is suitable to use the data extracted from the watermark to request additional data based thereon, and subsequently use this additional data in a suitable manner. 
         [0055]    The AV presentation device  180  may use the code  300  from the extracted watermark to make a request to a metadata server  350 . A code database  370  receives the data from the content source  100  that includes the code  300  and associated metadata  360 . The code  300  and associated metadata  360  is stored in the code database  370  for subsequent use. In this manner, the code  300  that is provided to the watermark inserter  190  which is encoded within the audio-visual content is also stored in the code database  370  together with its associated metadata  360 . In the event that the MVPD  130 , or otherwise, removes the associated metadata or otherwise changes the associated metadata, it is recoverable by the AV presentation device  180  from the metadata server  350  which uses the provided code  351  to query the code database  370  and provide an associated response with the metadata  353  to the AV presentation device  180 . The reply metadata provided by the metadata server  350  is used by the AV presentation device  180  to form a request  355  that is provided to the content and signaling server  380 . The content and signaling server  380 , in response to the request, provides selected content and signaling  357  to the AV presentation device  180 . In general, the content and signaling server  380  may be different from the metadata server  350 . 
         [0056]    However, making a first request to the metadata server to obtain a response to the code provided, then subsequently using the metadata to provide a request to the content and signaling server  380  is burdensome, and prone to failure, due to the two different servers and/or requests that are utilized. Additionally it may increase the latency. 
         [0057]    By way of example, the metadata may consist of one or more of the following syntax elements: 
         [0058]    (1) location of content and signaling server (e.g., where is the server, such as its network address. Examples of network addresses are domain names, IPv4 address etc.); 
         [0059]    (2) protocol to be used for communication with the content and signaling server (e.g., Hypertext Transfer Protocol—http, Hypertext Transfer Protocol Secure—https etc.); 
         [0060]    (3) time code identifying a temporal location in the audio-visual content (e.g., where the metadata should be associated with in the audio-visual content); 
         [0061]    (4) time sensitive event trigger (e.g., an advertisement or an event for a particular location in the audio-visual content); 
         [0062]    (5) channel identification (e.g., channel specific information; local channel content); 
         [0063]    (6) duration over which the content and signaling server requests are randomly carried out by client (e.g., for load balancing). For brevity, this syntax element may also be referred to as duration for content server requests; 
         [0064]    (7) etc. 
         [0065]    The watermark(s) embedded in the audio-video content typically have a capacity to carry only a few bits of payload information when the watermarked audio-video broadcast has non-readily observable information. For relatively small payload sizes, the time code (element 3 above) and/or the location of the content and signaling server (element 1 above) tends to take on a significant percentage of the available payload leaving limited additional payload for the remaining data, which tends to be problematic. 
         [0066]    To include sufficient metadata within the watermark, so that both the time code and the location information may be provided together with additional information, it may be desirable to partition the metadata across multiple watermark payloads. Each of the watermark payloads is likewise preferably included within different portions of the audio-visual content. The data extracted from the multiple watermark payloads are combined together to form a set of desirable information to be used to make a request. In the description below the term payload may be used to indicate watermark payload. Each of the syntax elements may be included within a single payload, spanned across multiple payloads, and/or fragmented across multiple payloads. Each payload may be assigned a payload type for purposes of identification. Further, an association may be established between multiple payloads belonging to the same or approximately the same timeline location. Also, the association may be uni-directional or bi-directional, as desired. 
         [0067]    The desired time code data may be obtained from payload(s) that span across several temporal locations of the audio-visual content. Therefore some systems may establish rules to associate the determined time code with a particular temporal location of the audio-visual content. In an example embodiment the chosen temporal location may correspond to the temporal location at the end of a pre-determined watermark payload. 
         [0068]    For example, the payload size may be  50  bits while the desirable metadata may be  70  bits, thus exceeding the payload size of a single watermark. An example of the desirable metadata may be as follows: 
         [0000]    
       
         
               
               
             
           
               
                   
               
             
             
               
                 Location of content and  
                 32 bits (Internet Protocol “IP” 
               
               
                 server (I) 
                 address) 
               
               
                 Application layer protocol (A) 
                 1 bit (http/https) 
               
               
                 Time code (T) 
                 25 bits (for 1 year of uniqueness 
               
               
                   
                 with a granularity of 1 second) 
               
               
                 Time sensitive trigger (D) 
                 1 bit (A value of 1 indicates the 
               
               
                   
                 AV presentation device should query  
               
               
                   
                 for interactive content. A value of 0 
               
               
                   
                 indicates the AV presentation device  
               
               
                   
                 should not query for interactive  
               
               
                   
                 content (e.g. as in time base trigger)). 
               
               
                 Channel identification (L) 
                 9 bits 
               
               
                 Duration for content server  
                 2 bits 
               
               
                 requests (R) 
               
               
                   
               
             
          
         
       
     
         [0069]    Another example of the desirable metadata may be as follows: 
         [0000]    
       
         
               
               
             
           
               
                   
               
             
             
               
                 Location of content and server (I) 
                 32 bits (IP address) 
               
               
                 Application layer protocol (A) 
                 2 bit (00 = http/01 = https, 10 = 
               
               
                   
                 reserved, 11 = reserved) 
               
               
                 Time code (T) 
                 25 bits (for 1 year of uniqueness 
               
               
                   
                 with a granularity of 1 second) 
               
               
                 Time sensitive trigger (D) 
                 1 bit 
               
               
                 Channel identification (L) 
                 9 bits 
               
               
                 Duration for content server requests (R) 
                 2 bits 
               
               
                   
               
             
          
         
       
     
         [0070]    One manner of partitioning the metadata is to include the content and signal server communication information (CSSCI) in one payload and timeline information in another payload. The CSSCI payload may include, for example, where information (e.g., location of content and signaling server), association information (e.g., an identifier to associate the CSSCI payload with one or more other payloads), and how information (e.g., application layer protocol, duration for content server requests). The timeline information may include, for example, association information (e.g., an identifier to associate the timeline with one or more other payloads), when information (e.g., time code information), and which information (e.g., channel identification). 
         [0071]    Referring to  FIG. 5 , an exemplary CSSCI payload is illustrated. 
         [0072]    Referring to  FIG. 6 , an exemplary time location payload is illustrated. The term time location may be alternatively used in place of the term temporal location. 
         [0073]    The payload type may be identified by the first bit, “Y”. When Y is set to 0 the payload corresponds to CSSCI payload and the 14 bit payload identifier (P) is used to label the CSSCI. When Y is set to 1 the payload corresponds to the temporal location payload and the 14 bit payload identifier (P) signals the corresponding CSSCI. As a result, different payload types with same payload identifier (P) value are associated with each other. The identifier R indicates a time duration over which to spread the content and signaling server requests. In yet another example embodiment “Y” may correspond to a 2-bit field where the value 00 indicates a CSSCI payload, the value 01 indicates a temporal location payload and the values 10, 11 are reserved for future use. 
         [0074]    Referring to  FIG. 7 , an exemplary time line is illustrated. A first CSSCI type payload (e.g., CSSCI- 0 ) has a first set of association information P while a second CSSCI type payload (e.g., CSSCI- 1 ) has a second different set of association information P. Having two different association information P for CSSCI- 0  and CSSCI- 1  distinguish between and identify the two CSSCI payloads. A first time location payload (e.g., Timeline- 0 ) has the first set of association information P that matches the association information P for CSSCI- 0 , a second time location payload (e.g., Timeline- 1 ) has the same first set of association information P that matches the association information P for CSSCI- 0 , a third time location payload (e.g., Timeline- 2 ) has the same second set of association information P that matches the association information P for CSSCI- 1 . In this manner, CSSCI- 0 , Timeline- 0 ; CSSCI- 0 , Timeline- 1 ; and CSSCI- 1 , Timeline- 2  are associated together as pairs having spanned watermarked information. This permits the same CSSCI type payload to be used for multiple different time location payloads. 
         [0075]    As illustrated, each temporal location payload is associated with a previously received CSSCI type payload, and thus unidirectional in its association. In the event that a previous CSSCI type payload matching a temporal location payload is not available, then the system may be able to determine that a packet has been lost or otherwise the watermarking was not effective. The loss of watermarking data occurs with some frequency because the audio-video content tends to be modified by audio-video transcoding, such as to reduce the bitrate of the audio-video content. 
         [0076]    Referring to  FIG. 8 , an exemplary time line is illustrated. A first CSSCI type payload (e.g., CSSCI- 0 ) has a first set of association information P while a second CSSCI type payload (e.g., CSSCI- 1 ) has a second different set of association information P. Having two different association information P for CSSCI- 0  and CSSCI- 1  distinguish between and identify the two CSSCI payloads. A first time location payload (e.g., Timeline- 0 ) has the first set of association information P that matches the association information P for CSSCI- 0 , a second time location payload (e.g., Timeline- 1 ) has the same first set of association information P that matches the association information P for CSSCI- 0 , a third time location payload (e.g., Timeline- 2 ) has the same second set of association information P that matches the association information P for CSSCI- 1 . In this manner, CSSCI- 0 , Timeline- 0 ; CSSCI- 0 , Timeline- 1 ; and CSSCI- 1 , Timeline- 2  are associated together as pairs having spanned watermarked information. This permits the same CSSCI type payload to be used for multiple different time location payloads. As illustrated, two of the temporal location payloads are associated with a previously received CSSCI type payload, and one of the CSSCI type payloads are associated with a subsequently received Temporal location payload, and thus bidirectional in its association. In the event that a corresponding CSSCI type payload matching a temporal location payload is not available, then the system may be able to determine that a packet has been lost or otherwise the watermarking was not effective. Similarly, in the event that a corresponding timeline type payload matching a CSSCI payload is not available, then the system may be able to determine that a packet has been lost or otherwise the watermarking was not effective. The loss of watermarking data occurs with some frequency because the audio-video content tends to be modified by audio-video transcoding, such as to reduce the bitrate of the audio-video content. 
         [0077]    In an example, a CSSCI type payload (e.g. CSSCI- 0 ) has two sets of association information P 0  and P 1 . A time location payload, e.g. Timeline- 0 , has two sets of association information P 0  and P 1  that matches the association information P 0  and P 1  for CSSCI- 0 . In this example a bidirectional association exists for the pair CSSCI- 0 , Timeline- 0  where P 0  points to CSSCI- 0  and P 1  points to Timeline- 0 . 
         [0078]    The number of bits assigned to the payload identifier (P) may be modified, as desired (e.g., for a desired robustness). Similarly, the number of bits assigned to I, A, T, D, L, and R may be modified, as desired. 
         [0079]    In an example embodiment, the AV presentation device  180  may maintain a list denoted by a variable listC of “c” most recently received CSSCI payload(s). “c” may be provided in the watermark, if desired, or otherwise set by the system. In this manner, the AV presentation device  180  may only have to maintain a limited number of CSSCI payloads in memory. In the case that c=1, then once a CSSCI payload is received it remains in effect until another CSSCI payload is received, as illustrated in  FIG. 9 . A loss of a CSSCI payload may be detected using the payload identifier (P), for example, the temporal location payload contains a P that does not correspond to any of the CSSCI payloads in listC. In this manner, the same user experience may be achieved across different AV presentation devices  180 . 
         [0080]    In an example embodiment, the AV presentation device  180  may maintain more than one list of received CSSCI payload(s). Each list may differ in size and may be maintained (i.e. addition/removal of entries within the list) using a differing set of rules. It is to be understood, that this does not preclude the possibility that a subset of lists may have same size and/or same maintenance rules. As an example, there may be two lists maintained by  180  where one list contains “c1” most recently received CSSCI payload(s) where each payload is received at an interval of “0” CSSCI payload(s); while the other list contains “c2” most recently received CSSCI payload(s), where each payload is received at an interval of “d” CSSCI payload(s). 
         [0081]    Referring to  FIG. 10 , a modified system may include the content source  100 , the watermark inserter  190 , the MVPD  130 , the broadcast receiving device  160 , and the AV presentation device  180  together with its watermark capable receiver  310  and watermark client  320 . The content server  400  may be modified to include the code database  370 , the metadata server  350 , and the content and signaling server(s)  380 . The code  300  and metadata  360  is provided to the content server  400  by the content source  100 . The content and signaling data is provided to the content and signaling server(s)  390 . 
         [0082]    The AV presentation device  180  may provide a code in a request based upon the decoded one or more watermarks from the audio-video broadcast. The content server  400  receives the request with the code from the AV presentation device  180 . The metadata server  380  then parses the received code request and based upon information from the code database  370 , makes a request to the content and signaling server(s)  390  to determine the content and signaling information which is then provided to the AV presentation device  180 . In this manner, the AV presentation device  180  only needs to make a single request to a single content server  400 , which in turn provides the response to the AV presentation device  180 . It is to be understood that the different functions of the content server  400  may be achieved by combining the existing functions together, separating the existing functions into more components, omitting components, and/or any other technique. 
         [0083]    A http/https request URL (that will be sent to the content server  400 ) corresponding to payload(s) in  FIG. 5  and  FIG. 6 , when time sentive trigger D equals to 1, may be defined as:
   If A is equal to 0 then the http request URL is:   http://IIIIIIII.IIIIIIII.IIIIIIII.IIIIIIII/LLLLLLLLL?time=TTTTTTTTTTTTTTTTTTTT TTTTT   Otherwise, the https request URL is:   https://IIIIIIII.IIIIIIII.IIIIIIII.IIIIIIII/LLLLLLLLL?time=TTTTTTTTTTTTTTTTTTTT TTTTT   where IIIIIIII.IIIIIIII.IIIIIIII.IIIIIIII above corresponds to the 32-bit IP address signaled in CSSCI payload.   
 
         [0089]    In an example embodiment, the subset of URL that specifies information such as: the content server location, the communication protocol, communication port, the login information, the folder on the content server are carried in a designated payload type. 
         [0090]    In some implementations a syntax element&#39;s value may be derived using a decoding process which may access information spanning multiple payloads. For example, the time code may be fragmented into multiple watermark payloads and then reassembled to construct a complete time code. In an example, the time code may correspond to a temporal location within the audio-visual content. In an example, the time code may correspond to timeline data of the audio-visual content. 
         [0091]    For example, the payload size may be 50-bits while the desirable metadata may be 66 bits, thus exceeding the payload size of a single watermark. An example of the desirable metadata may be as follows: 
         [0000]    
       
         
               
               
             
           
               
                   
               
             
             
               
                 Location of content and server (I) 
                 32 bits (IP address) 
               
               
                 Application layer protocol (A) 
                 1 bit (http/https) 
               
               
                 Time code (T) 
                 25 bits (for 1 year of uniqueness 
               
               
                   
                 with a granularity of 1 second) 
               
               
                 Time sensitive trigger (D) 
                 1 bit 
               
               
                 Channel identification (L) 
                 5 bits 
               
               
                 Duration for content server requests (R)  
                 2 bits 
               
               
                   
               
             
          
         
       
     
         [0092]    Another example of the desirable metadata may be as follows: 
         [0000]    
       
         
               
               
             
           
               
                   
               
             
             
               
                 Location of content and server (I) 
                 32 bits (IP address) 
               
               
                 Application layer protocol (A) 
                 2 bit (00 = http/01 = https, 10 = 
               
               
                   
                 reserved, 11 = reserved) 
               
               
                 Time code (T) 
                 25 bits (for 1 year of uniqueness 
               
               
                   
                 with a granularity of 1 second) 
               
               
                 Time sensitive trigger (D) 
                 1 bit 
               
               
                 Channel identification (L) 
                 5 bits 
               
               
                 Duration for content server requests (R) 
                 2 bits 
               
               
                   
               
             
          
         
       
     
         [0093]    Referring to  FIG. 11 , a state transition diagram illustrates one technique to calculate the time code. To obtain a time code synchronization a number of consecutive payloads starting with a payload type “start sync”, is followed by payloads of type “not start sync”, with a total being equal to “r”. By using the total of “r” consecutive payloads, each having some time information contained therein, the time synchronization may be determined by calculating an anchor time. After calculating the anchor time code, the time code may be updated by receiving additional payloads that include partial time code information therein in such a manner that does not require receiving another total of “r” consecutive payloads to determine the next time code. One technique to achieve this time synchronization is to partition the time code in consecutive payloads and an incremental time code in each of the consecutive payloads. When the synchronization is lost, such as by changing the channel, the obtain synchronization process is performed. A video display device when first turned ON enters the initial “obtaining synchronization” state. 
         [0094]    Referring to  FIG. 12 , an exemplary structure of a watermark payload is illustrated. Z indicates the payload type, where Z equal to 1 indicates the start of the time sync and Z equal to 0 indicates not start of time sync. S indicates the time sync payload bits used in determining absolute time code. M indicates the time sync payloads bits used in maintaining the time code. 
         [0095]    By way of example, the AV presentation device  180  may receive n=7 consecutive watermark payloads where the first payload has Z=1 while the rest have Z=0. The bits corresponding to “SSSS” are extracted from (t−n+1) th  to t th  watermark payload and concatenated together to obtain a 28 bit representation of the time code “T t ” of a temporal location. The anchor time code “C t ” is also set to “T t ”. “T t ” may be represented as SSSS z−1,t−n+1 . . .  SSSS z=0,t−1 SSSS z=0,t ; “C t ”=“T t ”. In another embodiment, constants may be added (to select a future time) and/or multiplied (to change the granularity) to the derived values. In yet another alternative embodiment, the derived values are mapped to another value by use of a maping function. 
         [0096]    Once the initialization synchronization is obtained, the anchor time and payload time are updated using each payload. This may be performed, for example, as follows: 
         [0000]        T   t   =f ( C   t−1   , MMMM   t ) 
         [0000]        C   t   =g ( T   t ) 
         [0097]    Where, f represents a mapping function that takes as input 2 values and outputs 1 value; g represents a mapping function that takes as input 1 value and outputs 1 value;/represents integer division with truncation of the result toward zero, For example, 7/4 and −7/−4 are truncated to 1 and −7/4 and 7/−4 are truncated to −1. In an example embodiment: 
         [0000]    
       
      
       T 
       t 
       =C 
       t−1 
       +MMMM 
       t  
      
     
         [0000]      C t =T t    
         [0098]    As described above, every “n” payloads the anchor time may also be determined using the bits corresponding to “SSSS”. The anchor time determined using “SSSS” must match the anchor time derivation above and can be used to verify the correctness of the maintained time code. 
         [0099]    Since the watermark may span a non-zero time, the temporal location of the time code T t  may be determined by a set of rules, such as for example, T t  may correspond to a time instant at the end of the t-th watermark payload. 
         [0100]    It is to be understood that multiple syntax elements may be combined to form the code. The code may then be mapped either by the AV presentation device  180  or using another server to different syntax element values. For example, the server information (e.g., location of the content and signaling server(s) and/or application layer protocol, etc.) and time code is combined into a single code. The single code is then mapped to a temporal location in the uncompressed audio-video stream, and location of the content and signaling server(s). In this manner, a single request may be made to the server for additional information. 
         [0101]    A limited number of bits may be used for the time code, in such a manner to permits collisions in the time code. For example, using 20 bits for the timcode allows for at most 12 days of uniqueness at a granularity of 1 second. After 12 days the codespace corresponding to the timecode will be reused tending to result in collisions. 
         [0102]    In one embodiment the watermark payload may be encapsulated within a Standards Developing Organization (SDO) Private data command as SDO Payload using cmdID&#39;s. As an example the watermark payload of  FIG. 5  or  FIG. 6  maybe encapsulated as SDO payload. A cmdID value 0×05 may refer to a watermark based interactive services trigger (triggered declarative object—TDO Model). A cmdID value 0×06 may refer to a watermark based interactive services trigger (direct execution model). This facilitates the re-use of existing segmentation and reassembly modules built for trigger transportation. The segmented command may be embedded in watermarks, if desired. The SDO Private data may be desired, such as illustrated in  FIG. 13 , where the packet is included as part of SDO_payload( ). In some embodiments the watermark payload received in this manner maybe passed to an entity/module in the receiver which handles these defined cmdID types. Then segmentation and reassembly functionality of that module could be reused if watermark payload packet needs to be split into multiple packets—depending upon the selected watermark scheme&#39;s capacity in terms of number of bits. 
         [0103]    Parameter type T is a 2-bit field that indicates whether the instance of the SDOPrivatedata command is part of a segmented variable length command, as defined in Section 7.1.11.2 of CEA-708 (“CEA: “Digital Television (DTV) Closed Captioning, CEA-708-E, Consumer Electronics Association, June 2013”), and if so, whether the instance is the first, middle, or last segment. The Type field in the SDOPrivateData command is encoded as specified in Section 7.1.11.2 of CEA-708. pr is a flag that indicates, when set to ‘1’, that the content of the command is asserted to be Program Related. When the flag is set to ‘0’, the content of the command is not so asserted. Length (L) is an unsigned integer that indicates the number of bytes following the header, in the range 2 to 27, and is represented in the SDOPrivateData command as the set of bits L 4  through L 0  where L 4  is the most signficiant and L 0  is the least significant. cid (cmdID) is an 8-bit field that identifies the SDO that has defined the syntax and semanditcs of the SDO_payload( ) data structure to follow. The metadata may be encapsulated within SDO Private data as SDO Payload using cmdID&#39;s as shown in  FIG. 14 . 
         [0104]    The payload defined in  FIG. 5  and  FIG. 6  may be encapsulated within a Standards Developing Organization (SDO) Private data (SDOPrivateData) command as SDO Payload using cmdID&#39;s. A cmdID value 0×05 and 0×06 may refer to encapsulation of payloads defined in  FIG. 5  and  FIG. 6  respecively. This facilitates the re-use of existing segmentation and reassembly modules built for trigger transportation. The segmented command may be embedded in watermarks, if desired. The SDO Private data may be desired, such as illustrated in  FIG. 13 , where the payload packet is included as part of SDO_payload( ). 
         [0105]    The payload defined in  FIG. 12  may be encapsulated within a Standards Developing Organization (SDO) Private data command as SDO Payload using cmdID&#39;s. A cmdID value 0×05 may refer to encapsulation of payload defined in  FIG. 12 . This facilitates the re-use of existing segmentation and reassembly modules built for trigger transportation. The segmented command may be embedded in watermarks, if desired. The SDO Private data may be desired, such as illustrated in  FIG. 13 , where the packet is included as part of SDO_payload( ). 
         [0106]    It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.