Abstract:
In one embodiment, there is presented a method for processing data. The method comprises receiving a plurality of packets, wherein each packet comprises a payload, and wherein the plurality of packets carry video data encoded in accordance with an encoding standard from a plurality of encoding standards; identifying encoding standards encoding the video data carried in the payloads of the plurality of packets; and inserting identifiers that identify the encoding standard encoding the video data carried in the payloads of the plurality of packets into the plurality of packets.

Description:
RELATED APPLICATIONS  
       [0001]     [Not Applicable] 
       FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT  
       [0002]     [Not Applicable] 
       MICROFICHE/COPYRIGHT REFERENCE  
       [0003]     [Not Applicable] 
       BACKGROUND OF THE INVENTION  
       [0004]     A transport stream can comprise multiplexed data from a variety of channels, and a variety of transponders. The data can then be provided to decoders for decoding and eventual presentation. The increasing number of channels and potential destinations in modern media and multimedia systems place considerable demultiplexing demands on such media and multimedia systems.  
         [0005]     In order to process multiple data types from multiple sources simultaneously, reliance may not be had on the fact that simultaneous data belongs to the same format. There may be a large number of different formats to be processed simultaneously.  
         [0006]     Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.  
       BRIEF SUMMARY OF THE INVENTION  
       [0007]     System(s) and/or method(s) are provided for demultiplexing different stream types in a programmable demultiplexer, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.  
         [0008]     These and other features and advantages of the present invention may be appreciated from a review of the following detailed description of the present invention, along with the accompanying figures in which like reference numerals refer to like parts throughout.  
     
    
     BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS  
       [0009]      FIG. 1  is a block diagram of an exemplary circuit for processing data in accordance with an embodiment of the present invention;  
         [0010]      FIG. 2  is a block diagram of an exemplary packet in accordance with an embodiment of the present invention;  
         [0011]      FIG. 3  is a flow diagram for processing data in accordance with an embodiment of the present invention;  
         [0012]      FIG. 4A  is a block diagram of an exemplary circuit for processing data in accordance with an embodiment of the present invention;  
         [0013]      FIG. 4B  is a block diagram of an alternative circuit for processing data in accordance with an embodiment of the present invention; and  
         [0014]      FIG. 5  is a flow diagram for processing data in accordance with an embodiment of the present invention.  
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0015]     Certain embodiments of the present invention relate to processing video and audio signals. More specifically, certain embodiments of the invention relate to a method and system for demultiplexing different stream types when they have been merged together into a single multiplexed stream.  
         [0016]     In general, transport demultiplexers may be required to process data of different formats. In the case of processing incoming data a single input format at a time, processing of incoming data follows a given set of rules in order to provide parsing which is native to the format. Processing may be a single input at a time, due to the fact that only one data source is supported, only one destination is supported, or if multiple data sources are supported, because all the input sources were in the same format (usually the set top box may be configured only a certain way for a certain configuration setting). A single state machine per format that needs to be parsed can be used. When data from the particular format arrives, that state machine associated with the format can the parse data appropriately. A single configuration parameter can be set at the beginning which indicates the type of data to be parsed, and then the state machine holds onto its states in between data arrival. However, with the preponderance of different input formats, as well as the requirements to process data from different sources and different formats simultaneously, the foregoing may not provide acceptable performance.  
         [0017]     When processing multiple streams, the formats can change at every packet boundary. Accordingly, one set of rules may not be sufficient to process the aggregate stream. Additionally, the multiple formats may have multiple initialization states. When processing multiple formats simultaneously, information about a packet, such as its input format, packet length, and other parameters may not be ascertainable in time to process the packet.  
         [0018]     Referring now to  FIG. 1 , there is illustrated block diagram of an exemplary circuit for processing data in accordance with an embodiment of the present invention. The circuit comprises an input  105 , a register  110 , and a transport demultiplexing engine  115 , now referred to as a Record Audio Video Engine (RAVE).  
         [0019]     The input  105  can receive packets  120  from a communication medium, such as a cable network or the Internet. The packets  120  include a payload  120 ′ carrying encoded data. The encoded data can come from a number of different sources. The encoded data is packetized for transmission and multiplexed with other data. Packetizing breaks up an associated set of encoded data into smaller portions and places the smaller portions into the payload  120 ′ of a packet  120 .  
         [0020]     An associated set of data can include, for example, a data file, a video program, an audio program, to name a few. The packets  120  carrying the smaller portions of the associated set of encoded data are multiplexed over a communication channel with other packets  120  carrying smaller portions of other associated sets of encoded data.  
         [0021]     The packets  120 , including the data carried in the payload can be encoded in accordance with a variety of encoding standards. The encoding standards can include, for example, MPEG, DirecTV, DVD Input, PES input, ES input, or DirecTV with MPEG-1, to name a few.  
         [0022]     Generally, the associated set of encoded data is encoded using the same encoding standard. However, other associated sets of encoded data that are multiplexed onto the same communication channel may be encoded with a different encoding standard.  
         [0023]     The register  110  identifies the encoding standards for each of the packets  120 . The register  110  can comprise hardware components, such as logic, or may be a programmed circuit. The register  110  inserts an identifier into each packet  120  that identifies the encoding for the packet.  
         [0024]     In certain embodiments of the present invention, the packets  120  include headers  120 ″, and the register  110  identifies the encoding standard for the packet by examining a field in the header  120 ″.  
         [0025]     Additionally, the register  110  can also determine and insert other information about the packet  120  into the packet  120 . For example, in certain embodiments of the present invention, the register  110  can determine the length of the packet and insert another identifier that identifies the length of the packet.  
         [0026]     The identifier(s) can be inserted into the packet in a variety of ways. In certain embodiments of the present invention, the identifier(s) can be appended to the packet header  120 ″. In other embodiments, the register  110  can attach another header to the packet  120 . The header can include the identifier(s).  
         [0027]     The transport demultiplexing engine  115  receives and processes the packets  120 . The transport demultiplexing engine  115  processes each of the packets based on rules that are associated with the encoding standard for the packet. Accordingly, the transport demultiplexing engine  115  examines the identifier identifying the encoding standard for the packet  120 . Based on the identifier, the transport demultiplexing engine  115  selects a set of rules that are associated with the encoding standard.  
         [0028]     Referring now to  FIG. 2 , there is illustrated a block diagram of exemplary packets  120  in accordance with an embodiment of the present invention. The packets  120  include a payload  120 ′ and a header  120 ″.  
         [0029]     In certain embodiments, the identifier(s) can be appended to the header  120 ″, e.g., identifier  205   a . Alternatively, in certain embodiments, the identifier(s) can be written into the header  120 ″, e.g., identifier  205   b , overwriting another field in the header  120 ″. In other embodiments, another header  120 ′″ can be placed onto the packet that includes the identifier(s), e.g., identifier  205   c.    
         [0030]     Referring now to  FIG. 3 , there is illustrated a flow diagram for processing data in accordance with an embodiment of the present invention. At  305 , a packet  120  is received at input  105 .  
         [0031]     At  310 , the register  110  determines the encoding standard for the packet  120 . At  315 , the register  110  inserts identifier(s) that identify the encoding standard for the packet, and other information regarding the packet.  
         [0032]     At  320 , the transport demultiplexing engine  115  examines the identifier that identifies the encoding standard for the packet  120 . Based on the identifier identifying the encoding standard for the packet  120 , the transport demultiplexing engine  115  selects a set of rules associated with the encoding standard at  325 , and processes the packet  120  in accordance with the set of rules at  330 .  
         [0033]     The foregoing can be used in a variety of applications. For example, video data transmitted over a network, such as the internet or a cable network, is often multiplexed with other data. Encoded video data that is associated with a particular program, known as an elementary stream, is transmitted in transport packets. The video data associated with a particular program, as well as audio data stream(s) associated with the same program, and audio and video data associated with other programs are multiplexed onto a communication channel.  
         [0034]     The transport packets can be encoded with varying encoding standards, and can have different lengths. The encoding standards can include, for example, MPEG (188 bytes), DirecTV™ (130 bytes), DVD Input (128 bytes), PES input (188 bytes), ES input (188 bytes), or DirecTV with MPEG-1, to name a few. The transport packets form what is known as a transport stream.  
         [0035]     Referring now to  FIG. 4A , there is illustrated a system for processing video or audio data in accordance with an embodiment of the present invention. The system  400  comprises an input  405 , a register  410 , a transport demux engine, or RAVE  415 , a plurality of decoders  417 , a playback engine  418  and memory  419 .  
         [0036]     The input  405  receives a transport stream comprising transport packets  420 . The transport packets  420  include a payload  420 ′ carrying encoded video or audio data. The encoded video or audio data can come from a number of different sources, for example, a video or audio associated with a program, known as an elementary stream.  
         [0037]     The elementary stream is packetized for transmission and multiplexed with other elementary streams. Packetizing breaks up the elementary stream into smaller portions and places the smaller portions into the payload  420 ′ of a transport packet  420 .  
         [0038]     The playback engine  418  provides packets  120  from local storage  421 . The local storage  421  can comprise, for example, a DVD, CD, or a hard disc. The local storage  421  can store data in streams, such as a video elementary stream or audio elementary stream. When the playback engine  421  provides data from the local storage  421 , the playback engine packetizes the data into packets  120 .  
         [0039]     It is noted that the elementary stream can be packetized several times. For example, the elementary stream can be packetized and carried in the payload of what is known as the packetized elementary stream. The packetized elementary stream can then be packetized and carried in the payload  420 ′ of transport packets  420 .  
         [0040]     The transport packets  420 , including the data carried in the payload  420 ′ can be encoded in accordance with a variety of encoding standards. The encoding standards can include, for example, MPEG, DirecTV, DVD Input, PES input, ES input, or DirecTV with MPEG-1, to name a few.  
         [0041]     Generally, the elementary stream is encoded using the same encoding standard. However, other elementary streams that are multiplexed onto the same communication channel may be encoded with a different encoding standard.  
         [0042]     The register  410  identifies the encoding standards for each of the transport packets  420 . The register  410  can comprise hardware components, such as logic, or may be a programmed circuit. The register  410  inserts an identifier into each transport packet  420  that identifies the encoding for the packet.  
         [0043]     In certain embodiments of the present invention, the same register  410  can identify the encoding standards for each of the transport packets  120  from the playback engine  418  and the input  405 , while in other embodiments, separate registers  410  may be used. Thus in  FIG. 4B , there is illustrated another embodiment of the present invention wherein separate registers  410  identify the encoding standards for each of the transport packets  120 .  
         [0044]     In certain embodiments of the present invention, the register  110  identifies the encoding standard for the packet by examining a field in the transport packet header  420 ″. For example, when the playback engine  418  provides packets  120  to the register  110 , the playback engine  418  may insert the field in the transport packet header  420 ″.  
         [0045]     Additionally, the register  410  can also determine and insert other information about the packet  420  into the packet  420 . For example, in certain embodiments of the present invention, the register  410  can determine the length of the packet and insert another identifier that identifies the length of the packet.  
         [0046]     The identifier(s) can be inserted into the transport packet  420  in a variety of ways. In certain embodiments of the present invention, the identifier(s) can be appended to the packet header  420 ″. In other embodiments, the register  410  can attach another header to the packet  420 . The header can include the identifier(s).  
         [0047]     The RAVE  415  uses this information to decide how to process a given packet on a dynamic basis. The processing states of the various streams, as well as the processing rules, can be stored in memory  419 . A new set of states and rules may then be loaded at each packet time.  
         [0048]     The RAVE  415  receives and processes the packets  420 . The RAVE  415  processes each of the packets based on rules that are associated with the encoding standard for the packet. Accordingly, the RAVE  415  examines the identifier identifying the encoding standard for the packet  420 . Based on the identifier, the RAVE  420  selects a set of rules that are associated with the encoding standard.  
         [0049]     The RAVE  415  provides each elementary stream to a particular one of the decoders  417  associated with the elementary stream.  
         [0050]     In order to accurately demultiplex transport packets  420  with different encoding standards, the RAVE  420  treats each transport packet  420  independently, without influence from previous transport packets  420 . Thus, state machine states of the RAVE  415  are stored into memory  419  at the end of processing each transport packet  420 . The memory  419  associates the state machines states of the RAVE  415  with contexts. Each type of encoding standard is associated with a particular context.  
         [0051]     When the RAVE  415  receives a transport packet  420  with a particular encoding standard, the RAVE  415  retrieves and loads the state machine state in the context associated with the encoding standard. Upon completing processing of the transport packet  420 , the RAVE  415  writes the state machine state to the context in memory  419  that is associated with the encoding standard for the processed transport packet  420 .  
         [0052]     The RAVE  415  can comprise the system(s) and apparatus, and employ the method(s) of the following applications which are incorporated herein by reference for all purposes:  
                                       Attorney Docket   Filed   Serial Number                   16778US01               16779US01       16780US01       16897US01       16902US01       16908US01       16912US01       16917US01                  
 
         [0053]     Referring now to  FIG. 5 , there is illustrated a flow diagram for processing data in accordance with an embodiment of the present invention. At  505 , the playback engine  418  retrieves data from the local storage  421  and packetizes the data at  510 . The playback engine  418  inserts at  515 , a field in the header  420 ″ of the packet indicating the encoding standard for the packet  420 . The field can also indicate that the packet  420 ″ is sent by the playback engine  418  from the local storage  421 .  
         [0054]     At  520 , the register  410  receives the packet  420 ″ and inserts an identifier identifying the encoding standard associated with the packet  420 . At  525 , the RAVE  415  examines the identifier identifying the encoding standard. At  530 , the RAVE  415  selects a set of rules based on the identifier identifying the encoding standard and applies them to the packet  420 .  
         [0055]     At  535 , the RAVE  415  retrieves portions of an elementary stream from the transport packet and adds the portion to other portions of the elementary stream that are retrieved. RAVE provides the ES data to the decoder  417  associated with the elementary stream at  545 .  
         [0056]     The embodiments described herein may be implemented as a board level product, as a single chip, application specific integrated circuit (ASIC), or with varying levels of the system integrated with other portions of the system as separate components. Alternatively, if the processor is available as an ASIC core or logic block, then the commercially available processor can be implemented as part of an ASIC device wherein certain aspects of the present invention are implemented as firmware.  
         [0057]     The degree of integration may primarily be determined by the speed and cost considerations. Because of the sophisticated nature of modern processors, it is possible to utilized a commercially available processor, which may be implemented external to an ASIC implementation.  
         [0058]     While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.