Abstract:
The device disclosed is capable of accepting and transmitting multiplexed compressed digital video, (Digital TV DTV/HDTV), in a MPEG2 Transport Stream (TS) form, from various devices and sources. It is intended to be used by broadcasting companies to leverage high-speed networks, for point to point and point to multipoint transmissions. The disclosure includes methods for Supporting DHCP and DNS. The processing of the received signals provides a Constant Delay for synchronization. This is obtained by providing at the receiving node provides buffering for accommodating network jitter and lost packages and for controlling the output bit rate. The buffering includes a buffer for retaining a predetermined quantity of data the effective size of which before the data is released is changed depending upon bit rate and the output bit rate is controlled by varying the amount of data retained. Remote Management and Monitoring function is provided based on the SNMP protocol and a remote management and monitoring function via the WWW and HTTP protocol. A design is provided for Point to Multipoint multicast Transmissions.

Description:
[0001]    This application claims priority under 35 U.S.C.119 from Provisional Application Ser. No. 60/331,489 filed Nov. 19 th  2001. 
     
    
     
       FIELD OF THE INVENTION  
         [0002]    This invention relates to a method for transmitting digital video signals over an IP network.  
           [0003]    The digital video broadcasting industry requires high-speed, low-latency communication links for transmission of production components and for distribution. Today, the video production process includes digital editing and integration of components from sometimes geographically distributed locations. Satellite transmission is the main communication link. Both digital and analog components are utilized.  
           [0004]    Other typical transmission uses:  
           [0005]    Delivery of live video program streams to the head-end or production studio  
           [0006]    Transmission of movie or video rushes  
           [0007]    Remote Broadcast  
           [0008]    Delivery of live video to cable head-ends  
           [0009]    Video Backhaul  
           [0010]    Broadcasting companies are currently in the process of assessing the use of high-speed data networks. This will enhance the production, storage, and distribution process. Several major telecommunications carriers are involved in this type of study. Digital Video Broadcasting (DVB) is a standard that has emerged for digital video transmission. The standard is managed by the European Telecommunications Standards Institute (ETSI). It is a market-led initiative to standardize digital broadcasting and includes over 220 organizations in more than 30 countries. DVB equipment is widely available. DVB is based on the MPEG-2 standard. DVB interfaces are available for satellite, cable, terrestrial broadcast and studio equipment. It offers a lot of flexibility in terms of the type of data that can be carried.  
           [0011]    Other digital video interface technologies are also used, such as the North American standards (ATSC), SMPTE 310M and 259M, also know as SDI, for example. From a network point of view, DVB is a transport technology that defines its own physical, media access, and network protocols. It is not compatible with mainstream data networking technologies.  
           [0012]    The Internet protocol (IP) is the dominant protocol for implementation of multimedia network applications. At least one major telecommunications carrier has announced that the data business is larger than the voice business and for this reason is focusing on further development of IP-based offerings. In addition, network equipment providers continue to increase bandwidth to support high-quality multimedia applications.  
           [0013]    Current video transport technology allows digital video signals to be modulated over analog channels to be transmitted via satellite, cable distribution systems and antenna systems, over the air. There are also products that can transmit digital video over existing telephone networks at speeds approaching 50 Mbps. Most of these products were designed to transport analog video, or low bit rate digital video in a point to point fashion.  
           [0014]    There is a need for interfaces that will allow HDTV and DTV data to be transmitted over the new high speed IP based networks as we transition to digital television. Broadcasting companies will be using storage area network (SAN) technologies to archive contents and technology for back-haul of video from the studios to distribution points that may include cable head ends or affiliates. Broadcast networks could also use new technology to send their program stream to member stations.  
           [0015]    This new transmission technology offers a much shorter time delay between points because the satellite delay is eliminated. This technology could also be used for interview applications were a response delay is annoying.  
           [0016]    This technology can also be used for broadcasting sporting events. In a case where an event such as baseball or football is to be broadcast from a metropolitan area were high speed network bandwidth is available, a network interface could easily be established for point to point transmission between a stadium and the broadcasters&#39; studio. It could be established for the duration of the sporting event and then disassembled.  
           [0017]    The interface also has the potential of being applied at the home environment as a video acquisition board. Direct to theatre distribution of movies would be feasible using this technology.  
           [0018]    DVB has a provision to transport user data as well as MPEG-2 program material. This capability can make use of the high bandwidth network connection to send very high-resolution medical images between hospitals and to central databases for storage and to specialists for diagnostic analysis. With the advances in IP network infrastructure towards high bandwidth connections, there is now a market for a device that transports digital video over an IP network. This device competes well with current methods such as using satellites and private networks, which are high cost, require a lengthy install time, and have issues of lower bandwidth and larger latencies.  
         BACKGROUND PRIOR ART  
         [0019]    There has been little work in this field because digital video is a relatively new thing, especially with broadcasters. In addition, it has not been technically or economically feasible to transmit digital video over long distances. Most of the work has been aimed to provide digital video over very low bandwidth connections. Thus most of the focus has been on encoding methods to reduce the bandwidth, rather than the transport techniques used to deliver the content. There is however, research into transporting MPEG digital video over ATM based networks. Almost all software that transmits digital video over IP networks utilizes the Real-Time Protocol.  
           [0020]    A product has previously been available which is the Optibase MGW 3100, an Israeli company, which is identified hereinafter and provides a device which transmits digital video signals over IP networks. However this is presently no longer available and has a number of disadvantages.  
           [0021]    The following documents are also of some interest in this field:  
           [0022]    U.S. Patents:  
           [0023]    U.S. Pat. No. 6,434,562 Computer system and method for providing digital video and data over a communication channel  
           [0024]    U.S. Pat. No. 6,208,666 System and method for maintaining timing synchronization in a digital video network  
           [0025]    U.S. Pat. No. 5,883,924 Method and apparatus for PCR jitter measurement in an MPEG-2 transport stream using sliding window  
           [0026]    U.S. Pat. No. 5,640,388 Method and apparatus for removing jitter and correcting timestamps in a packet stream  
           [0027]    U.S. Pat. No. 6,434,606 System for real time communication buffer management  
           [0028]    U.S. Pat. No. 6,377,588 Method and apparatus for reducing jitter of a program clock reference in a transport stream of MPEG over ATM, and MPEG decoder  
           [0029]    U.S. Pat. No. 5,534,937 Minimum-delay jitter smoothing device and method for packet video communications  
           [0030]    U.S. Pat. No. 6,233,256 Method and apparatus for analyzing and monitoring packet streams  
           [0031]    U.S. Pat. No. 6,208,643 Apparatus and method for analyzing bit streams  
           [0032]    U.S. Pat. No. 6,429,902 Method and apparatus for audio and video end-to-end synchronization  
           [0033]    U.S. Pat. No. 6,266,384 Method and apparatus for time base recovery and processing  
           [0034]    U.S. Pat. No. 5,966,387 Apparatus and method for correcting jitter in data packets  
           [0035]    U.S. Pat. No. 5,790,543 Apparatus and method for correcting jitter in data packets  
           [0036]    U.S. Pat. No. 5,596,581 Recording and reproducing an MPEG information signal using tagged timing information  
           [0037]    Application 20020024970 Transmitting MPEG data packets received from a non-constant delay network  
           [0038]    Application 20020154640 Method of clock mismatch and drift compensation for packet networks  
           [0039]    Related Articles and Standards:  
           [0040]    Optimal Multicast Smoothing of Streaming Video over an Internetwork, IEEE Journal, S. Sen, D. Towsley, Z. Zhang and J. Dey, 1999  
           [0041]    DVB Interfaces to SDH Networks, ETS 300 814 Standard  
           [0042]    Synchronization of MPEG-2 based digital TV services over IP networks, Master Thesis at Telia Research AB, B. Kaxe, 2000  
           [0043]    MPEG-2 Transport over ATM Networks, Masters Thesis at University of California, Santa Cruz, Christos Tryfonas, September 1996  
           [0044]    RTP: A Transport Protocol for Real-Time Applications, RFC1889, H. Schulzrinne, S. Casner, R. Frederick and V. Jacobson, January 1996  
           [0045]    RTP Profile for Audio and Video Conferences with Minimal Control, RFC1890, H. Schulzrinne, January 1996  
           [0046]    RTP Payload Format for MPEG1/MPEG2 Video, RFC2250, D. Hoffman, G. Fernando, V. Goyal and M. Civanlar, January 1998  
           [0047]    Extension of RTP Payload Type for Multiple Program MPEG Transport Streams, draft-ietf-avt-rtp-mp2t-00, H. Liu, March 2000  
           [0048]    Information Technology—Generic coding of moving pictures and associated audio information: Systems, ISO/IEC Standard 13818-1 (The MPEG2 Standard), 1996  
           [0049]    MPEG Video Compression Standard, J. Mitchell, W. Pennebaker, C. Fogg and D. LeGall, 1997  
           [0050]    Real-Time Transport Protocol Management Information Base, draft-ietf-avt-rtp-mib-13, M. Baugher, I. Suconick and B. Strahm, May 2000  
           [0051]    Transport of MPEG-2 Constant Bit Rate Television Signals in B-ISDN (ATM), ITU-T Rec.J.82, July 1996  
           [0052]    Transport of MPEG-2 signals in SDH Networks, ITU-T Rec.J.132, March 1998  
           [0053]    Transport of MPEG-2 signals in PDH Networks, ITU-T Rec.G.703  
           [0054]    Monitoring of Audio, Video and Data in a Multi-Channel Facility: SMPTE 35 th  Advanced Motion Imaging Conference Capital Hilton, Washington D.C., David Strachan, Evertz Microsystems, Ltd. Feb. 8-11 th , 2001.  
           [0055]    An SNMP Agent for a DTV Data Server, SMPTE 35 th  Advanced Motion Imaging Conference Capital Hilton, Washington D.C., Dinkar Bhat, David Catapano, James Kenealy, Gomer Thomas, Feb. 8-11 th , 2001.  
           [0056]    ETS 300 813 Digital Video Broadcasting (DVB); DVB interfaces to Plesiochronous Digital Hierarchy (PDH) networks  
           [0057]    ETS 300 814 Digital Video Broadcasting (DVB); DVB interfaces to Synchronous Digital Hierarchy (SDH) networks  
           [0058]    ETS 300 818 Broadband Integrated Services Digital Network (B-ISDN); Asynchronous Transfer Mode (ATM); Retainability performance for B-ISDN switched connections  
           [0059]    Optibase MGW 3100 (http://www.optibase.com/html/products/Media 13 Gateways/MGW 13  3100.html)  
           [0060]    Notation:  
           [0061]    SDH: Synchronous Digital Hierarchy (a superset of SONET, used to carry most modern high-speed backbone links)  
           [0062]    PDH: Plesiochronous Digital Hierarchy (Old-world style Telco network, with voice channels and TDM, the Tx/Ex style links)  
           [0063]    MPEG: Motion Pictures Experts Group (http://www.cselt.it/mpeq/ and also www.mpeg.org)  
           [0064]    SMPTE: Society of Motion Pictures Technical Engineers (www.smpte.org)  
           [0065]    DVB: Digital Video Broadcasting (www.dvb.org, DVB Standards are under www.etsi.org and http://server.cenelec.be)  
           [0066]    ATSC: Advanced Television Standards Committee (www.atsc.orq, the US equivalent to the European DVB Project)  
           [0067]    ASI: Asynchronous Serial Interface  
           [0068]    SDI: Serial Digital Interface  
           [0069]    RFC: Request For Comment (De facto standard for internet protocols)  
           [0070]    IP: Internet Protocol (RFC 791)  
           [0071]    TCP: Transmission Control Protocol (RFC 793)  
           [0072]    UDP: User Datagram Protocol (RFC 768)  
           [0073]    RTP: Real-Time Protocol (RFC 1889, 1890, 2250)  
           [0074]    SSRC: Synchronization Source (from RTP)  
           [0075]    MTU: Maximum Transmission Unit (TCP/IP)  
           [0076]    GbE: Gigabit Ethernet (IEEE 802)  
           [0077]    MP2TS: MPEG 2 Transport Stream (ISO/IEC 13818-1)  
           [0078]    TS: Transport Stream (referring to an MPEG 2 Transport Stream)  
           [0079]    QoS: Quality of Service  
           [0080]    Diffserv: Differentiated Services (RFC 2998)  
           [0081]    DHCP: Dynamic Host Configuration Protocol (RFC 2131)  
           [0082]    DNS: Domain Name Service (RFC 1034,1035)  
           [0083]    SNMP: Simple Network Management Protocol (RFC 1157)  
           [0084]    IGMP: Internet Group Multicast/Management Protocol (RFC 2236)  
           [0085]    WWW: World Wide Web (http://www.w3c.org)  
           [0086]    PHP: PHP Hypertext Preprocessor (server-side scripting language, http://www.php.net)  
           [0087]    HTTP: Hyper Text Transfer Protocol (RFC 1855, world wide web protocol)  
           [0088]    CGI: Common Gateway Interface (web scripting facility)  
           [0089]    HTML: Hyper Text Markup Language (http://www.w3c.org)  
           [0090]    MIB: Management Information Base  
           [0091]    GUI: Graphical User Interface  
         SUMMARY OF THE INVENTION  
         [0092]    The object of the invention is to be a competitive technology to current Satellite broadcast methods for most point-to-point digital television back-haul applications. In the future when fiber is installed everywhere, then it will also be a competitive technology to satellite (lower cost) for point to multi-point applications. High-speed fiber IP networks are now being installed worldwide. These networks provide a high-speed backbone for voice, data and video applications. The invention enables transport of DVB or ATSC digital video over wide-area IP networks, see FIG. 1. This provides an alternative to satellite links for video backhauling, remote broadcasts, or distribution to cable head-ends. The invention is designed to decrease the latency of transmission as opposed to satellite links. It is designed to significantly reduced equipment cost and operation cost for broadcast transmission. In addition the invention affords a much greater geographic and location portability of the device, due to its ease of configuration and widespread availability of network access. The invention affords much versatility of location of the devices as there are no limitations due to satellite footprints, nor the requirement for retransmission from remote locations. The invention is also designed to be adaptable and versatile to be easily extensible to other functions.  
           [0093]    According to a first aspect of the invention there is provided a method for transmitting digital video signals comprising:  
           [0094]    providing a transmitter node and a receiver node each connected to an IP network;  
           [0095]    providing at the transmitter node an input for receiving multiplexed compressed digital video in a MPEG2 Transport Stream form containing MPEG2 Transport Stream packets from a source;  
           [0096]    providing at the receiver node an output for transmitting multiplexed compressed digital video in a MPEG2 Transport Stream form to a receiver;  
           [0097]    at the transmitter node, extracting the data from the MPEG2 Transport Stream, encapsulating that data in IP network packets each containing the data from a plurality of MPEG2 Transport Stream packets and transmitting the IP network packets addressed to the receiver node over the IP network from the transmitter node to the receiver node;  
           [0098]    at the receiver node, receiving the IP network packets, extracting the data therein, encapsulating the data into a MPEG2 Transport Stream and transmitting the MPEG2 Transport Stream to the receiver;  
           [0099]    wherein the receiving node transmits the MPEG2 Transport Stream at a predetermined required output bit rate equal to the bit rate of the stream from the source;  
           [0100]    and wherein the IP network packets are jumbo Ethernet frames.  
           [0101]    Preferably the jumbo Ethernet frame size is at least 1501 bytes.  
           [0102]    Preferably the transmitting node selects a jumbo Ethernet frame format from a plurality of different available formats depending upon the frame format which can be accepted by the IP network.  
           [0103]    Preferably the transmitting node selects a format in response to an automatic detection of the available format on the network.  
           [0104]    According to a second aspect of the invention there is provided a method for transmitting digital video signals comprising:  
           [0105]    providing a transmitter node and a plurality of receiver nodes each connected to an IP network;  
           [0106]    providing at the transmitter node an input for receiving multiplexed compressed digital video in a MPEG2 Transport Stream form containing MPEG2 Transport Stream packets from a source;  
           [0107]    providing at each of the receiver nodes an output for transmitting multiplexed compressed digital video in a MPEG2 Transport Stream form to a respective receiver;  
           [0108]    at the transmitter node, extracting the data from the MPEG2 Transport Stream, encapsulating that data in IP network packets each containing the data from a plurality of MPEG2 Transport Stream packets and transmitting the IP network packets over the IP network from the transmitter node to the receiver node;  
           [0109]    at the receiver nodes, receiving the IP network packets, extracting the data therein, encapsulating the data into a MPEG2 Transport Stream and transmitting the MPEG2 Transport Stream to the respective receiver;  
           [0110]    wherein the receiving node transmits the MPEG2 Transport Stream at a predetermined required output bit rate equal to the bit rate of the stream from the source;  
           [0111]    and wherein the transmitter node is arranged to address the IP network packages such that each transmitted packet is directed by the network to each of the receiver nodes in a multicast arrangement.  
           [0112]    Preferably the receiver node requests participation in the multicast arrangement.  
           [0113]    According to a third aspect of the invention there is provided a method for transmitting digital video signals comprising:  
           [0114]    providing a transmitter node and a receiver node each connected to an IP network;  
           [0115]    providing at the transmitter node an input for receiving multiplexed compressed digital video in a MPEG2 Transport Stream form containing MPEG2 Transport Stream packets from a source;  
           [0116]    providing at the receiver node an output for transmitting multiplexed compressed digital video in a MPEG2 Transport Stream form to a receiver;  
           [0117]    at the transmitter node, extracting the data from the MPEG2 Transport Stream, encapsulating that data in IP network packets each containing the data from a plurality of MPEG2 Transport Stream packets and transmitting the IP network packets addressed to the receiver node over the IP network from the transmitter node to the receiver node;  
           [0118]    at the receiver node, receiving the IP network packets, extracting the data therein, encapsulating the data into a MPEG2 Transport Stream and transmitting the MPEG2 Transport Stream to the receiver;  
           [0119]    wherein the receiving node transmits the MPEG2 Transport Stream at a predetermined required output bit rate equal to the bit rate of the stream from the source;  
           [0120]    wherein the receiver node and the transmitter node are arranged to support DHCP configuration of its network interfaces to improve the manageability and to support DNS name resolution to improve the configurability of the operation.  
           [0121]    According to a fourth aspect of the invention there is provided a method for transmitting digital video signals comprising:  
           [0122]    providing a transmitter node and a receiver node each connected to an IP network;  
           [0123]    providing at the transmitter node an input for receiving multiplexed compressed digital video in an input MPEG2 Transport Stream form containing MPEG2 Transport Stream packets from a source;  
           [0124]    providing at the receiver node an output for transmitting multiplexed compressed digital video in an output MPEG2 Transport Stream form to a receiver;  
           [0125]    at the transmitter node, extracting the data from the MPEG2 Transport Stream, encapsulating that data in IP network packets each containing the data from a plurality of MPEG2 Transport Stream packets and transmitting the IP network packets addressed to the receiver node over the IP network from the transmitter node to the receiver node;  
           [0126]    at the receiver node, receiving the IP network packets, extracting the data therein, encapsulating the data into a MPEG2 Transport Stream and transmitting the MPEG2 Transport Stream to the receiver;  
           [0127]    wherein the receiving node transmits the MPEG2 Transport Stream at a predetermined required output bit rate equal to the bit rate of the stream from the source;  
           [0128]    wherein the receiving node provides buffering for accommodating network jitter and lost packages and for controlling the output bit rate;  
           [0129]    and wherein the buffering is controlled to provide a predetermined constant time delay between the input stream and the output stream.  
           [0130]    Preferably the delay is of the order of 0.5 seconds.  
           [0131]    Preferably the transmitter node is arranged for receiving different input streams at different bit rates and the buffering is arranged to maintain the same delay for different bit rates.  
           [0132]    Preferably the buffering includes a buffer for retaining a predetermined quantity of data the effective size of which before the data is released is changed depending upon bit rate.  
           [0133]    Preferably the output bit rate is controlled by varying the amount of data retained.  
           [0134]    Preferably at the transmitter node there is applied to each transmitted packet an accurate time stamp and wherein the input rate is determined at the receiver node by detecting the time stamp of a plurality of sequential packets and the quantity of data therein.  
           [0135]    Preferably the input rate is determined taking into account lost and erroneous packets.  
           [0136]    Preferably the buffering includes a buffer for retaining a predetermined quantity of data the effective size of which before the data is released is changed depending upon bit rate and wherein the lost and erroneous packets are replaced by null packets prior to inputting the packets into the buffer.  
           [0137]    Preferably the buffer size is maintained at substantially a minimum so as to minimize the delay.  
           [0138]    Preferably each time a network packet is received, the software checks the RTP timestamp to see if its sampling interval has elapsed where the interval should be much longer than the difference between consecutive RTP timestamps, such that the actual sampling intervals are almost uniform; the variation in the RTP packet arrival times is ignored; if the sampling interval has passed, the software compares the actual circular buffer level to the desired half-full level and uses this difference as the error signal for a digital feedback control system; this error signal is applied to a proportional-integral (PI) compensator whose output is the bit rate; the gains of the proportional and integral blocks are set such that the control loop is stable and highly damped, to reject variations in the RTP packet arrival times; the bit rate is applied to the circular buffer, which acts as a second integrator and produces the actual buffer level used in the error signal calculation; each time the sampling interval elapses, the bit rate of the DVB ASI interface is updated; since the actual output bit rate is controlled by the hardware interface, it is very stable; and the control loop makes minor changes to the bit rate over long periods of time, resulting in an overall bit rate within tolerances of transport stream standards for jitter and drift.  
           [0139]    According to a fifth aspect of the invention there is provided a method for transmitting digital video signals comprising:  
           [0140]    providing a transmitter node and a receiver node each connected to an IP network;  
           [0141]    providing at the transmitter node an input for receiving multiplexed compressed digital video in an input MPEG2 Transport Stream form containing MPEG2 Transport Stream packets from a source;  
           [0142]    providing at the receiver node an output for transmitting multiplexed compressed digital video in an output MPEG2 Transport Stream form to a receiver;  
           [0143]    at the transmitter node, extracting the data from the MPEG2 Transport Stream, encapsulating that data in IP network packets each containing the data from a plurality of MPEG2 Transport Stream packets and transmitting the IP network packets addressed to the receiver node over the IP network from the transmitter node to the receiver node;  
           [0144]    at the receiver node, receiving the IP network packets, extracting the data therein, encapsulating the data into a MPEG2 Transport Stream and transmitting the MPEG2 Transport Stream to the receiver;  
           [0145]    wherein the receiving node transmits the MPEG2 Transport Stream at a predetermined required output bit rate equal to the bit rate of the stream from the source;  
           [0146]    wherein the receiving node provides buffering for accommodating network jitter and lost packages and for controlling the output bit rate;  
           [0147]    wherein the buffering includes a buffer for retaining a predetermined quantity of data the effective size of which before the data is released is changed depending upon bit rate;  
           [0148]    and wherein the output bit rate is controlled by varying the amount of data retained.  
           [0149]    Preferably at the transmitter node there is applied to each transmitted packet an accurate time stamp and wherein the input rate is determined at the receiver node by detecting the time stamp of a plurality of sequential packets and the quantity of data therein.  
           [0150]    Preferably the input rate is determined taking into account lost and erroneous packets.  
           [0151]    Preferably the lost and erroneous packets are replaced by null packets prior to inputting the packets into the buffer.  
           [0152]    Preferably the buffer size is maintained at substantially a minimum so as to minimize the delay.  
           [0153]    According to a sixth aspect of the invention there is provided a method for transmitting digital video signals comprising:  
           [0154]    providing a transmitter node and a receiver node each connected to an IP network;  
           [0155]    providing at the transmitter node an input for receiving multiplexed compressed digital video in an input MPEG2 Transport Stream form containing MPEG2 Transport Stream packets from a source;  
           [0156]    providing at the receiver node an output for transmitting multiplexed compressed digital video in an output MPEG2 Transport Stream form to a receiver;  
           [0157]    at the transmitter node, extracting the data from the MPEG2 Transport Stream, encapsulating that data in IP network packets each containing the data from a plurality of MPEG2 Transport Stream packets and transmitting the IP network packets addressed to the receiver node over the IP network from the transmitter node to the receiver node;  
           [0158]    at the receiver node, receiving the IP network packets, extracting the data therein, encapsulating the data into a MPEG2 Transport Stream and transmitting the MPEG2 Transport Stream to the receiver;  
           [0159]    wherein the receiving node transmits the MPEG2 Transport Stream at a predetermined required output bit rate equal to the bit rate of the stream from the source;  
           [0160]    wherein the receiver and transmitter nodes include a remote monitoring function based on the SNMP protocol and a remote management and monitoring function via the WWW and HTTP protocol.  
           [0161]    Preferably both the SNMP and WWW interfaces obtain the monitoring information from several variables recorded by the software of the node and stored in a shared memory location of the node.  
           [0162]    Preferably access control is implemented on the shared memory location to maintain accuracy of information.  
           [0163]    Preferably the SNMP protocol utilizes a MIB specification to implement the function.  
           [0164]    Preferably the WWW interface also links directly to the configuration and log files and system software for management functions.  
           [0165]    Preferably the WWW interface is implemented in industry standard HTML and PHP software.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0166]    One embodiment will now be described in conjunction with the accompanying figure and Appendices in which:  
         [0167]    Figures  
         [0168]    [0168]FIG. 1 depicts an overview of the invention&#39;s overall usage.  
         [0169]    [0169]FIG. 2 describes the modular hardware interface configuration.  
         [0170]    [0170]FIG. 3 shows a typical network connection for the invention.  
         [0171]    [0171]FIG. 4 illustrates the logical software configuration of the invention.  
         [0172]    [0172]FIG. 5 illustrates the network packet encapsulation and packet overhead considerations.  
         [0173]    [0173]FIG. 6 shows the buffer control algorithm. 
     
    
     APPENDICES  
       [0174]    Appendix 1 displays the SNMP MIB specification for the device.  
         [0175]    Appendix 2 illustrates the shared memory structure used for remote management.  
         [0176]    Appendix 3 shows example pseudo code for transmit and receive functions of the invention.  
       DETAILED DESCRIPTION  
       [0177]    The device is capable of accepting and transmitting multiplexed compressed digital video, (Digital TV DTV/HDTV), in a MPEG2 Transport Stream (TS) form, from various devices and sources. It includes DVB ASI and SMPTE 310M and state-of-the-art IP interfaces. It is intended to be used by broadcasting companies to leverage high-speed networks, for point to point and point to multipoint transmissions.  
         [0178]    The invention includes methods for Supporting DHCP and DNS, Constant Delay, Frame Optimization, Remote Management and Monitoring, Utilizing Network QoS Protocols, Transmitting at High Bit Rates and Operating with Lower Costs and designs for Point to Multipoint Transmissions, Extensible Modular System and Lower Cost System.  
         [0179]    Design for Point to Multipoint Transmissions  
         [0180]    The device is capable of transmitting data in a point to multipoint fashion utilizing multicast protocols. A transmitter node sets the multicast TTL also known as the scope for the outgoing packets. In addition, a transmitter node allows selection from a plurality of network interfaces within the invention for the multicast arrangement. A receiver node requests participation in the multicast arrangement through the use of the IGMP protocol.  
         [0181]    Method for Supporting DHCP and DNS  
         [0182]    The invention is capable of utilizing DHCP client software for the configuration of its network interfaces and parameters. The invention is capable of communicating with name servers for translation of network names to addresses used for operation. The invention is capable of using network names as configuration parameters for operation. Supporting these protocols improves configurability and ease of use of the device. Other existing technology does not support these protocols.  
         [0183]    Method for Constant Delay  
         [0184]    From a simplified point of view, the invention bridges a synchronous connection, an MPEG 2 Transport Stream, over an unreliable asynchronous connection, an IP network. An important element of the invention is therefore the method for recreating the precise timing required by an MPEG 2 Transport Stream while managing errors introduced by unreliable IP networks. The invention utilizes a two stage approach.  
         [0185]    The first stage originates in a transmitter node. A transmitter node uses an accurate hardware clock described elsewhere, to timestamp network packets which contain transport stream packets obtained from a source at an arbitrary bit rate. A receiver node estimates the transport stream bit rate from the timestamps contained in network packets it receives and the quantity of transport stream packets received. This estimation takes place over arbitrary period, for example, 0.2 seconds. It takes into account lost and erroneous network packets in its estimation. Lost packets are detected through the use of a sequence number in the network packet and are replaced with MPEG 2 Transport Stream null packets. Replacing lost transport stream packets with null packets does not recover missing data elements, but is used to maintain the precise timing of the transport stream. Numerous potential errors in the packet structure and headers are detected and discarded; any discarded packets are replaced with null packets. During the period when the estimation is taking place, measurements of network jitter can be taken using the network packet timestamps, since the MPEG 2 Transport Stream can be assumed to be constant bit rate.  
         [0186]    MPEG 2 Transport Stream data arrives periodically from the source at a transmitter node. This data is transmitted to the network periodically as well. However, the affects of jitter in the network mean that the packets arrive in a non-periodic fashion at a receiver node. In order for a receiver node to output the transport stream packets periodically it must maintain a buffer of transport stream packets, such that there is always a packet available to output at the required time. For optimal resiliency, the buffer level has to be kept at fifty percent capacity. To increase resiliency you create a larger buffer, however as the size of the buffer increases so too does the latency of data through the device. End users of the device, namely broadcasters, desire a minimal latency. Thusly, the buffer size is minimized while maintaining a sufficient size for jitter and error resiliency. The bit rate and network jitter estimates can be used to optimize the buffer size. The calculation would take the following form, where M and N are constants:  
         [0187]    Buffer Size=2*((M*Jitter Estimate)+N)*Bit Rate Estimate  
         [0188]    Alternatively, the invention uses the bit rate estimate and a fixed delay specification for sizing the buffer. The calculation would take the following form, with a fixed delay of 0.5 seconds:  
         [0189]    Buffer Size=2*(0.5 seconds*Bit Rate Estimate)  
         [0190]    End users of the device desire a constant low delay to maintain synchronization of schedules and for ease of use. In order to achieve this result, the average buffer level in a receiver node must be held constant. The second stage implements a bit rate control function in order to maintain the average buffer level.  
         [0191]    A receiver node can be modeled as shown in FIG. 6. The data flowing into the system is a ramp disturbance. To track a ramp with zero steady-state error, the open-loop transfer function  
         G   C     s                         
 
         [0192]    Needs Two Integrations. Suppose we use proportional-integral-derivative (PID) compensation;  
         G   c     =           K   D          s   2       +       K   P        s     +     K   I       s                           
 
         [0193]    where K D , K p , and K I  are the derivative, proportional, and integral gains respectively.  
         [0194]    The closed-loop transfer function is then  
           G   C       s   +     G   C         =           K   D          s   2       +       K   P        s     +     K   I           s   2     +       K   D          s   2       +       K   P        s     +     K   I                               
 
         [0195]    It is common knowledge that the optimum closed loop transfer function based on the integral of time multiplied by the absolute error (ITAE) for a ramp input in this case is  
           3.2        ω   n        s     +     ω   n   2           s   2     +     3.2        ω   n        s     +     ω   n   2                             
 
         [0196]    where ω n  controls the response of the system. Therefore, K D =0, K p =3.2ω n  and K I =ω n   2 .  
         [0197]    Using the bilinear transformation  
       s   =       2        (     1   -     z     -   1         )         T        (     1   +     z     +   1         )                               
 
         [0198]    where T is the sampling interval, we can find a digital filter equivalent to the analog compensator;  
         G   C     =       outputrate   error     =         2          K   P          (     1   -     z     -   1         )         +       K   I          T        (     1   +     z     -   1         )             2        (     1   -     z     -   1         )                                 
 
         [0199]    This may be implemented as  
         outputrate   n     =       outputrate     n   -   1       +           2        K   P       +       K   I        T       2          error   n       +             K   I        T     -     2        K   P         2          error     n   -   1                                 
 
         [0200]    The value of ω n  must be chosen such that the compensator break frequency is less than the sampling rate and the system is stable.  
         [0201]    Each time a network packet is received by a receiver node, it checks the RTP timestamp to see if its sampling interval has elapsed. This interval should be much longer than the difference between consecutive RTP timestamps, such that the actual sampling intervals are almost uniform. The variation in the RTP packet arrival times is ignored here. If the sampling interval has passed, the device compares the actual buffer level to the desired half-full level. It then uses this difference as the error signal for a digital feedback control system as described previously. This error signal is applied to the compensator, whose output is the bit rate. The control loop is highly damped to reject variations in the RTP packet arrival times. The bit rate is applied to the buffer, which acts as a second integrator and produces the actual buffer level used in the error signal calculation. Each time the sampling interval elapses, the bit rate of the video interface is updated. Since the actual output bit rate is controlled by the hardware interface, it is very stable. The control loop makes minor changes to the bit rate over long periods of time, resulting in an overall bit rate within tolerances of MPEG 2 Transport Stream standards for jitter and drift. In addition, the specific interface utilized within the preferred embodiment, which is described elsewhere, has configurations to minimize jitter which are fully utilized by the invention. Similar methods are used in this stage as the first stage for error management.  
         [0202]    As a result of synchronizing the output bit rate to the input rate of the system the average buffer level is held constant. This achieves the desired result of constant low delay.  
         [0203]    Method for Frame Optimization  
         [0204]    A node of the invention must expend resources and processing time for each network packet transmitted or received. Since the invention operates at high bit rates the packet rate is also high. This becomes a significant bottleneck to the device&#39;s operation. In order to minimize the required resources one can simply reduce the number of packets. The device accomplishes this by encapsulating the maximum number of TS packets per network packet. Typically the maximum network packet size is limited by the hardware&#39;s maximum frame size. Fragmentation allows this limitation to be overcome, however it is not practical. The device also utilizes jumbo Ethernet frames to increase the packet capacity beyond the 1500 byte limitation of Ethernet.  
         [0205]    A transmitter node is capable of automatically detecting the maximum packet size, also called the MTU, supported by the network connection. The invention implements a well known protocol called Path MTU Discovery. Path MTU discovery has the downside of periodically losing packets which is detrimental to video transmission. The invention additionally implements a modified version of Path MTU discovery wherein the Path MTU is only discovered once at the initiation of the session. This avoids the periodic packet loss problem. This can be implemented in two ways. The first maintains the Don&#39;t Fragment setting which allows for the possibility of a session timeout if network conditions change. On the other hand, removing the Don&#39;t Fragment setting allows the session to continue but introduces the possibility of incurring the additional overhead of packet fragmentation. Alternatively the device is capable of allowing a user to specify the frame size.  
         [0206]    A receiver node implements functions to automatically detect the network packet size as well as the transport stream packet size it is receiving. A receiver node calculates the network packet size from length information in the packet header inserted by a transmitter node. The transport stream packet size is determined by checking if the data size present in the network packet is an integer multiple of a 188 or 204 byte TS packet. The data is further scanned for the unique TS sync byte present in integer multiples of the TS packet size.  
         [0207]    Method for Remote Management and Monitoring  
         [0208]    The device is designed with remote management and monitoring functions. Each device stores information in a shared memory location. To maintain accuracy of the information stored in shared memory, access is controlled using a semaphore. The shared memory location contains information used to monitor the operation of the device. Examples of the information include bit rate, buffer levels and system state. The complete memory structure is shown in FIG. 8.  
         [0209]    The device implements the SNMP protocol by accessing information contained within the shared memory location in response to queries from SNMP clients. A network management station would use the MIB specification displayed in FIG. 7 in order to monitor and manage devices.  
         [0210]    The device implements a GUI interface for remote management and monitoring. The interface is created with industry standard HTML, PHP, Javascript and CGI code. This interface is accessible to any network connected host using standard WWW browsers and the HTTP protocol. The GUI interface manipulates configuration and log files used by the device and calls system functions in order to manage the device.  
         [0211]    Method for Utilizing Network QoS Protocols  
         [0212]    The device implements Diffserv QoS tagging of IP packets. In addition, it is fully compatible with most other QoS standards as they are controlled via upstream routers or edge devices, see FIG. 3. Since Diffserv is already integrated, extending support for other protocols is straightforward.  
         [0213]    Method for Transmitting at High Bit Rates  
         [0214]    The device is designed to operate with high MP2TS bit rates. The preferred embodiment operates in excess of 150 Mbps (Megabits per second). Existing technology can only operate with lesser bit rates.  
         [0215]    Design of Extensible Modular System  
         [0216]    The invention is designed for the flexibility to incorporate a wide variety of video and network interfaces, see FIGS. 2 &amp; 4. This was accomplished with abstraction of the devices and extended ranges in device configurations. The core software of the invention is divided into three modular components: A program file which performs the task of mapping the video and network, interfaces and protocols, and transporting and encapsulating the data. The two additional components provide SNMP and WWW GUI monitoring and management functions. The software was designed to be extensible.  
         [0217]    Design of Lower Cost System  
         [0218]    The invention has been designed with off the shelf components and simple devices in order to minimize the cost of the system. External development and manufacturing costs are also minimized for a lower cost design.  
         [0219]    Method of Operating with Lower Costs  
         [0220]    The device is design to utilize IP networks for transmission of broadcast video material. These networks provide a lower operating cost as compared to existing technology, such as satellite systems.  
         [0221]    General Description  
         [0222]    The device is a hardware/software product which transports a constant bit rate MPEG-2 transport stream (ISO/IEC 13818-1) over an IP network. It is composed of a fairly standard personal computer (PC) with a few special components, running Linux and some custom software. In addition to standard components, the PC is outfitted with digital video and network interfaces, most commonly a DVB ASI (EN 50083-9) and gigabit Ethernet interface respectively.  
         [0223]    The device is available with a combination DVB input and output or a combination SMPTE 310M input and output. The device is suitable for use with private dark fiber networks, which can provide better access control and security.  
         [0224]    2RU rack configuration (3.5″×18.9″×24.1″ with bezel)  
         [0225]    275-watt PFC power supply  
         [0226]    Conforms to FCC Class A, CE and UL  
         [0227]    DVB ASI Interface  
         [0228]    SMPTE 310M Interface  
         [0229]    1000Base-SX Interface (SC multimode fiber)  
         [0230]    10/100/1000Base-T Interface (RJ-45 copper)  
         [0231]    UDP Unicast or Multicast  
         [0232]    RTP as per RFC 1889, 1890, 2250  
         [0233]    Ethernet or Jumbo packet sizes  
         [0234]    10/100 Base-T control network interface  
         [0235]    SNMP Monitor  
         [0236]    Web based Manager  
         [0237]    The device is configured to enable an inexperienced operator to set-up a session and start the transmission of the video. It provides a simple to use interface that uses as little technical jargon as possible to allow video technicians or anyone who is not used to wide area networking technology, to start the system working.  
         [0238]    The setup is very easy and secure, allowing the possibility to use this technology for temporary remote broadcasts, such as soccer, football, or track and field events.  
         [0239]    The units are designed for remote monitoring and control. A web-based GUI is provided for this and is selected by browsing to the machine&#39;s URL (for example, http://192.168.3.15). The GUI is intended for Microsoft Internet Explorer 5.0 or higher or Netscape Navigator 4.0 or higher. The home page of the GUI presents a menu of available channels and a download of the SNMP MIB. Each unit normally provides one transmit channel and one receive channel. Selecting one of the channels will display the status of the connection on that channel. From the status page, you can return to the initial selection screen by clicking on the graphic at the top center of the page.  
         [0240]    The status page displays important operating parameters as well as the current status of the connection. When the connection is disabled, the status page will display the message “Process not running”. When the connection is enabled, the start time of the connection, as well as some status indicators are displayed. The status page updates automatically every second to provide current status information. Finally, the status page provides two control buttons to start and stop the connection. Also accessible from the status page are the two other major parts of the GUI, the configuration and log pages. These can be selected by clicking on the appropriate graphics at the top of the screen. You can return to the status page at any time by clicking on the status graphic at the top of the page.  
         [0241]    The configuration page allows you to setup the stream transmission, the ASI input or output port is displayed at the top of the box. For a transmit channel the configurable parameters are listed below:  
         [0242]    Destination parameter (required)—Destination is the IP address or network name of the unit at the other end of the bridge. This is the destination of the stream, where the MPEG-2 transport stream will be recovered.  
         [0243]    Port parameter (optional)—The network port used by the destination unit to receive the data transmission (port  5004  by default).  
         [0244]    Local address parameter (optional)—The IP address or network name of one of this unit&#39;s network interfaces. The default wildcard address is usually adequate, but if necessary this allows you to bypass normal system routing policies and use a specific interface for data transmission.  
         [0245]    Multicast TTL parameter (required for multicast)—The multicast TTL (time-to-live) parameter. This parameter is ignored unless you are transmitting to a multicast IP address. The TTL parameter is used to limit the scope of the multicast transmission. There is no strict definition of multicast TTL; often it means the maximum number of hops or routers in the path. The minimum value for the TTL is 1, which will transmit to the local network only; the maximum is 255, which will probably attempt to circle the global network.  
         [0246]    Type of Service parameter (optional)—The value of the Type-of-Service field in the IP packets. This is used to enable Quality of Service (QoS) protocols that may be available in your network. Please consult your network provider or administrator for details on this, as changing it to an unsupported value may decrease performance. The ToS value ranges from 0 to 254 and must be even.  
         [0247]    Frame size parameter (optional)—The maximum Ethernet frame size available on the network. The units support jumbo Ethernet frames of up to 16114 bytes on the gigabit Ethernet interface, but many network devices do not support these large frames. The larger the frame size the better. The default value is 1500 bytes.  
         [0248]    Transport stream packet size parameter—The MPEG-2 transport stream packet size. If you know the packet size, choose either 188- or 204-byte packets. Otherwise, choose Auto-detect.  
         [0249]    For a receive channel, the ASI output port is given at the top of the configuration page. The configuration parameters are also somewhat different and are described following:  
         [0250]    Local address parameter (optional)—The IP address or network name of one of this unit&#39;s network interfaces. You can use this to limit data connections to a specific interface if required. The default wildcard address will accept connections from all interfaces.  
         [0251]    Port parameter (optional)—The network port used to receive the data transmission. This must match the destination port specified on the transmitting unit. The default is port  5004 .  
         [0252]    Multicast group parameter (required for multicast)—The multicast IP address or group to be used to receive data. If you are multicasting, use the destination address specified on the transmitter unit. Otherwise, leave this field blank.  
         [0253]    Source parameter (optional)—The IP address or network name of the transmitting unit. Data from other addresses will be rejected.  
         [0254]    ASI burst mode parameter—The burst mode setting of the ASI output port. When burst mode is enabled, no stuffing is inserted within the MPEG-2 transport stream packets. When burst mode is disabled, the maximum amount of stuffing for the stream bit rate is inserted.  
         [0255]    The log page of the GUI provides a record of events that have occurred on this channel. The GUI will jump to the most recently logged events, which are at the bottom of the page. If many events have been logged, the page may be very long. You can use the Top link return to the top of the page. There may also be a Later or Earlier link at the bottom of the page, which provides access to logs from successive or previous days.  
         [0256]    The device also features SNMPv1-based remote monitoring. Information similar to that provided by the web-based GUI is available to SNMP clients, but no parameters may be changed. The information is in the “public” community under the iso.org.dod.internet.private.enterprises.linearSystems.ipCasterTable.ipCasterEntry tree (1.3.6.1.4.1.10582.1.1.1). There is a separate table for each channel, represented by an index number. Transmit channels are numbered from 100 to 199, and receive channels are numbered from 200 to 299. The MIB is available from the system&#39;s GUI on the main page.  
         [0257]    While running the software periodically updates several variables which are used to drive a SNMP monitoring facility as well as provide monitoring data to the GUI.  
         [0258]    Parameters available in the shared memory include data to describe the system, software, operating status, packet sizes, internet addresses, errors and video stream parameters. These allow fairly detailed monitoring of the video stream and system.  
         [0259]    Reference is made to the Appendices 1 to 3 as follows for further detail describing the detailed operation of the device.