EP1338147A2 - Norme mpeg dans un environnement de commutation de labels - Google Patents

Norme mpeg dans un environnement de commutation de labels

Info

Publication number
EP1338147A2
EP1338147A2 EP01994094A EP01994094A EP1338147A2 EP 1338147 A2 EP1338147 A2 EP 1338147A2 EP 01994094 A EP01994094 A EP 01994094A EP 01994094 A EP01994094 A EP 01994094A EP 1338147 A2 EP1338147 A2 EP 1338147A2
Authority
EP
European Patent Office
Prior art keywords
protocol
label
mpeg
layer
label switching
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP01994094A
Other languages
German (de)
English (en)
Inventor
Luis A. Rovira
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Scientific Atlanta LLC
Original Assignee
Scientific Atlanta LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Scientific Atlanta LLC filed Critical Scientific Atlanta LLC
Publication of EP1338147A2 publication Critical patent/EP1338147A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/70—Media network packetisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H04N21/23614—Multiplexing of additional data and video streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H04N21/4348—Demultiplexing of additional data and video streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64307—ATM
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/6433—Digital Storage Media - Command and Control Protocol [DSM-CC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast

Definitions

  • the present invention relates generally to the arts of communication networks and multimedia, and more particularly, to a multimedia program delivery system (and associated methodology) for delivering information flows to network subscribers or users.
  • IP networks were primarily designed to carry unicast information between two hosts. Though IP has the capability for multicast, IP routers and switches have not been very efficient at forwarding broadcast or multicast information. In fact, the IP network layer is designed to control traffic and prevent many broadcasts from transversing the routers of a network. When IP was developed, the bandwidth of switching devices and routers far exceeded the bandwidth of transport and transmission technologies. Thus, the IP network layer was designed to make routing decisions to keep information from being broadcast across the slow modem and X.25 links of the original Internet.
  • IP Internet Protocol
  • WDM Wave Division Multiplexing
  • connection-oriented technologies allow for network resource allocation to implement quality of service (QoS) for real-time information flows such as multimedia audio or video programs.
  • QoS quality of service
  • these connection-oriented technologies become unreasonable as the number of subscribers needing connections increases.
  • these connection-oriented technologies do not scale very well.
  • CATV Common Antenna Television
  • cable TV network where content is generally broadcast or narrowcast to a large number of subscribers on a distribution network.
  • CATV network has included many frequency-division multiplexed channels that are distributed to a large number of subscribers.
  • the CATV network has had a large amount of bandwidth to deliver information or data to many subscribers, but the CATV network's capabilities were limited for delivering customized programming for specific subscribers. This made it difficult to deliver subscriber-controllable and network-controllable features through existing CATV networks.
  • Digital signals may be communicated on a communications medium using various methods.
  • One simple method is to use a square wave to communicate the signals.
  • Networks using such square waves are often referred to as baseband or unmodulated (i.e., non-frequency-shifted) transmission systems.
  • These networks may allow multiple signals to share a communications medium through time-division multiplexing. This is in contrast to modulated signals that are frequency shifted outside of the base bandwidth (i.e., the baseband) of a square wave representation of the data.
  • Modulation may also be used to share a communications medium with multiple signals, each signal being placed within its own frequency band. This technique is known as frequency-division multiplexing.
  • baseband and broadband were used to indicate unmodulated, baseband transmission and modulated transmission, respectively.
  • lOBaseT means 10 MBPS (mega-bits per second), baseband, twisted-pair while 10Broad36 described a frequency-shifting, 10 MBPS, broadband system.
  • broadband also has been used to describe communication systems with relatively higher capacity bandwidth as opposed to systems with relatively lower capacity bandwidth that are often known as narrowband systems.
  • time-division multiplexing The two primary types of time-division multiplexing are 1) static or fixed TDM and 2) dynamic or statistical TDM.
  • Static or fixed TDM is used in circuit-switching technologies such as the PSTN (Public Switched Telephone Network) as built in the 1960s to 1990s.
  • PSTN Public Switched Telephone Network
  • Dynamic or statistical TDM is used in packet-switching to more efficiently allocate bandwidth based on an as-needed or on- demand basis.
  • Common packet-switching technologies include Ethernet switching, Internet Protocol (IP) routing, X.25, frame relay, and ATM (Asynchronous Transfer Mode).
  • Packet-switching technologies can be categorized into two types: 1) connectionless or datagram packet-switching and 2) connection-oriented or virtual-circuit packet-switching.
  • connectionless or datagram packet-switching no connections or paths are established prior to the source being able to communicate with the destination. Instead, the packet switch or router forwards each packet based on a path or route determined at the time that the packet switch or router receives the packet.
  • datagram packet-switching networks each packet transmitted from the source to the destination may follow a different path through the network. Due to different delays from following different paths, the packets in a datagram packet-switching network may arrive at the destination in a completely different order than they were transmitted by the source.
  • IP is a common example of a connectionless, datagram packet-switched protocol.
  • connection-oriented or virtual-circuit packet-switching a connection or virtual circuit is setup between the source and destination that want to communicate.
  • the connection allocates resources in the network between the source and destination, and the connection establishes the network path to be used by packets communicated from the source to the destination.
  • virtual-circuit packet-switching the packets transmitted from the source to the destination all generally follow the originally allocated path and arrive at the destination in the same order as they were transmitted by the source.
  • Common examples of packet-switching technologies that use connection-oriented, virtual-circuits are X.25, frame relay, and ATM.
  • SVCs switched virtual circuits
  • IP Internet Protocol
  • MPEG Motion Pictures Experts Group
  • IP datagrams IP datagrams.
  • MPLS Multi-Protocol Label Switching
  • MPLS was primarily designed to carry network protocols with a special emphasis on the Internet Protocol (IP) due to the ubiquitous nature of IP based networks. Also, the common method of delivering MPEG packets is to encapsulate them inside IP datagrams. However, a simple straight-forward combination of label switching technologies to encapsulate network level packets such as IP datagrams that then encapsulate MPEG packets leads to inefficiencies and makes it more difficult to deliver broadcast and multicast services to subscribers. This problem in providing digital services that are similar to the services provided by CATV broadcast networks is at least partially due to the addressing limitations of the IP protocol.
  • IP Internet Protocol
  • IP Internet Protocol
  • the preferred embodiments of the present invention provide a method (and associated devices) of using MPEG packets encapsulated in a label switched protocol such as MPLS (Multiple Protocol Label Switching) to overcome limitations of previous networks.
  • An embodiment of the present invention includes implementing label switching functionality, implementing MPEG functionality, and encapsulating MPEG packets within label switching functionality.
  • MPEG would not be considered a network protocol, which is what label switching protocols are generally designed to encapsulate.
  • the use of the preferred embodiments of the present invention in a network advantageously improves the delivery of customized services to network subscribers. Encapsulating MPEG within MPLS simplifies network deployment by converging the previously distinct environments of data communications and broadcast television service over cable TV networks.
  • the encapsulation of MPEG within MPLS allows merging MPEG program content streams with IP streams at the MPLS multiplexing level. This allows for applications such as merging MPEG video programs with IP advertising, as one non-limiting example.
  • the MPEG Digital Storage Medium Command and Control (DSM-CC) protocol may be used for label distribution for the label switching network.
  • DSM-CC MPEG Digital Storage Medium Command and Control
  • Other common protocols may be used to distribute labels to non-MPEG-aware label switching equipment. Thus, all the label switching equipment in the network does not have to be MPEG-aware.
  • the preferred embodiments of the present invention advantageously simplify the delivery of multimedia information flows to network subscribers and promote the convergence of previously distinct historical perspectives on network technologies. These historical perspectives primarily developed from the data networks for computers that predominately use unicast and multicast packets and from the CATV networks for video and other multimedia content delivery that generally use broadcast and narrowcast.
  • the preferred embodiments of the present invention resolve some of the previous problems with the delivery of digital multimedia services to subscribers as well as allow simplified deployment of new services such as personal television.
  • the preferred embodiments of the present invention advantageously use MPEG packets in a label switching environment to allow the convergence of many of the previously described network technologies.
  • the preferred embodiments of the present invention overcome many of the limitations of the previously described network technologies to deliver multimedia content to subscribers.
  • the network is designed based on the understanding that the restrictions of an IP network layer are not well suited to the deployment of a multimedia network where much of the traffic is broadcast or multicast to many subscribers.
  • the increased transport bandwidth of fiber optic cables has made an IP network layer less of a necessity.
  • the preferred embodiments of the present invention allow for service flow or information flow resource allocation in the network to provide for quality of service (QoS) in multimedia delivery without all the complexity of end-to-end, connection-oriented technologies such as ATM.
  • QoS quality of service
  • the preferred embodiments of the present invention more easily allow the multiplexing of subscriber-customized information within the network than was previously possible in other existing CATV networks. This subscriber-customized information could be used to implement new services.
  • the preferred embodiments of the present invention are oriented to time-division multiplexing techniques, they may be used within one or more frequency channels on a frequency-division multiplexed medium such as current CATV networks. Alternatively, the preferred embodiments of the present invention could be used on networks without frequency-division multiplexing. Though the current cable TV network has a broadband structure that uses frequency-division multiplexing for broadcast channels, the preferred embodiments of the present invention could be used to carry these broadcast channels in addition to subscriber-customized information in a time- division multiplexed format.
  • the preferred embodiments of the present invention may allow a migration away from the broadband, frequency-division multiplexed architecture of current cable TV networks towards a newer baseband, time-division multiplexed architecture for cable TV networks.
  • This migration may occur in stages, as the preferred embodiments of the present invention will likely first be used to provide additional and new services in a time-division-multiplexed format.
  • These example uses of the preferred embodiments of the present invention are not intended to be limiting, and those skilled in the art will be aware of unlimited variations for combining the preferred embodiments of the present invention with various time-division and frequency-division multiplexing techniques.
  • This disclosure is generally not meant to imply any limitations as to combining the preferred embodiments of the present invention, which is generally related to time-division multiplexing and baseband communications, with other multiplexing or transmission techniques.
  • FIG. 1 is a diagram of the Open Systems Interconnection (OSI) protocol model
  • FIG. 2 is a diagram showing a first location where label switching information may be placed in the OSI model
  • FIG. 3 is a diagram showing a second location where label switching information may be placed in the OSI model
  • FIG. 4 is a diagram showing label switching information between some example data link protocols and network protocols
  • FIG. 5 is a first diagram showing a protocol layer example with the PPP protocol used in a virtual private networking tunnel
  • FIG. 6 is a second diagram showing a protocol layer example with the PPP protocol used in a virtual private networking tunnel
  • FIG. 7 is a diagram showing MPEG transport inside an IP datagram in a label switched frame where the label is included in a shim label header;
  • FIG. 8 is a diagram showing MPEG transport inside an IP datagram in a label switched frame where the label is included in the layer 2 address fields;
  • FIG. 9 is a diagram showing MPEG transport inside an ATM cell or a frame relay packet as used on the PVCs and SVCs of ATM and frame relay;
  • FIG. 10 is a diagram showing MPEG transport directly inside a label switched frame where the label is included in a shim label header;
  • FIG. 11 is a diagram showing MPEG transport directly inside a label switched frame where the label is included in the layer 2 address fields;
  • FIG. 12 is a diagram showing the functions of a standard, layer 3 router
  • FIG. 13 is a diagram showing the functions of a label switching router (LSR);
  • LSR label switching router
  • FIG. 14 is a diagram showing the functions of the MPEG Systems Specification
  • FIG. 15 is a diagram showing how MPEG elementary streams are encapsulated in Packetized Elementary Streams (PES) and further encapsulated in MPEG transport packets;
  • PES Packetized Elementary Streams
  • FIG. 16 is a diagram showing an example of how MPEG transport uses Packet IDs (PIDs) to multiplex many programs including many Packetized Elementary Streams (PES); and
  • FIG. 17 is a diagram showing the use of Label Switching Routers (LSRs) in a label switching network for delivering MPEG to subscriber devices.
  • LSRs Label Switching Routers
  • FIG. 1 is a block diagram illustrating the seven-layer OSI (Open Systems Interconnection) reference architecture or protocol model for communication systems.
  • the seven layers of the OSI reference architecture are: 1) the physical layer 101, 2) the data link layer 102, 3) the network layer 103, 4) the transport layer 104, 5) the session layer 105, 6) the presentation layer 106, and 7) the application layer 107.
  • OSI Open Systems Interconnection
  • the OSI model was developed for an OSI protocol that was not widely accepted by the communications industry.
  • the seven-layer OSI protocol model is a useful abstraction for evaluating and discussing communication protocols and has become well known in the art for such purposes. Thus, a brief description of the model will be helpful before describing various embodiments of the present invention. Because the OSI model is well known in the art, a detailed discussion of all the features and functionality of each level in the OSI model will not be covered. Thus, the following descriptions of each layer are necessarily just a high-level overview of the some the functions generally found in various levels of protocol stacks or suites.
  • the first layer of the OSI protocol model is the physical layer 101, which is usually concerned with the communication of raw bits over a transmission channel. This usually involves the electrical or optical signal levels used to represent zeros and ones on the communications medium. Also, the physical layer 101 includes repeaters that regenerate and propagate digital signals.
  • the next level of the OSI model is the data link layer 102, which generally operates to ensure that bits are delivered on the medium without error.
  • the IEEE Institute for Electrical and Electronic Engineers
  • the MAC sublayer 102a comprises functions for grouping the bits of information into frames.
  • the frames usually contain headers and trailers (or tails) as well as some form of error checking such as error detection or error correction codes.
  • MAC frame headers often contain layer 2 addresses or MAC addresses. Layer 2 addresses are usually included in MAC frame headers when multiple streams of information are multiplexed onto a communication channel and the identification of the various streams for demultiplexing will be based on information in the stream. For instance, in many LAN technologies multiple transmitting and multiple receiving devices can use MAC addresses to uniquely identify which devices transmitted frames and which devices are to receive frames on a communications medium that is shared by the multiple devices.
  • the Media Access Control 102a sublayer often contains rules for specifying which device of multiple devices can transmit or receive at a specific time and/or frequency on the shared medium.
  • a communications medium shared by a number of devices contending for access is often called a contention medium, a broadcast medium, or a multi-point medium. It is often called a broadcast medium because even though only one device can transmit on the medium at a specific time and frequency, many devices could potentially receive a broadcast frame on the medium at a specific time and frequency.
  • Algorithms for arbitrating or controlling access to a shared medium can be distributed among the devices sharing the medium as is the case in Ethernet or the IEEE 802.3 CSMA CD (Carrier Sense-Multiple Access with Collision Detection) algorithm. Alternatively a controller can execute a centralized algorithm to allocate transmission rights to resolve contention in broadcast or shared media.
  • a point-to- point medium is a medium connected between only two devices.
  • a transmitter in a first device communicates in a forward direction with a receiver in a second device.
  • a transmitter in the second device communicates in a reverse direction with a receiver in the first device.
  • the LLC sublayer 102b of FIG. 1 provides support for a selection between a datagram service, a connection-oriented service, and an acknowledged datagram service.
  • the common IEEE protocol for LLC sublayer 102b is 802.2.
  • the network layer 103 generally provides transparent transfer of data from the transport layer 104.
  • the network layer 103 handles many of the details of the underlying data transmission, switching, and routing functions. To handle these functions, the network layer 103 often contains addressing information that determines how data is switched or routed through the network.
  • the abstractions of the OSI model do not exactly match every working protocol including the TCP/IP protocol suite.
  • the IP protocol is generally considered to be a level 3, network layer protocol 103.
  • a primary function of the transport layer 104 is to accept data from the session layer 105 and break the data into smaller pieces before passing it to the network layer 103.
  • the transport layer 104 often verifies that the data arrives properly at the destination.
  • TCP Transport Control Protocol
  • UDP User Datagram Protocol
  • TCP is a connection-oriented protocol that ensures in order delivery of the data that the TCP layer presents to higher level protocols.
  • UDP is a connectionless, datagram protocol that does not guarantee delivery of information, but UDP is useful for many simple communications that do not need the overhead of TCP.
  • the next layer of the OSI model is the session layer 105, which among other things provides two-way simultaneous, two-way alternating, or one-way transfer between two devices.
  • the presentation layer 106 handles data translation, formatting, and syntax selection.
  • the application layer 107 contains many commonly used functions for distributed applications. Examples of application layer protocols from the TCP/IP protocol suite include Telnet, the File Transfer Protocol (FTP), and the Hypertext Transfer Protocol (HTTP) that is used for retrieving web pages.
  • Telnet Telnet
  • FTP File Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • MPLS is a label switching protocol that was designed to work over multiple protocols and to carry multiple protocols within MPLS label switched frames. Generally, MPLS was designed to work over an OSI layer 2, data link protocol and to carry an OSI layer 3, network layer protocol. Though MPLS is designed for multiple protocols, the main proposed use for MPLS by those skilled in the art is to carry IP datagrams (t.e. , an IP network layer). In the embodiments of the present invention, MPLS or other label switching technology may be used to carry MPEG transport packets. MPEG transport is not normally considered to be a network layer protocol by those skilled in the art.
  • label switching works by assigning relatively short, fixed-length labels to packets.
  • the network equipment used to implement label switching is called a Label Switching Router (LSR).
  • LSR Label Switching Router
  • All packets that are to be forwarded in an equivalent method by an LSR are said to be part of a Forwarding Equivalence Class (FEC).
  • FEC Forwarding Equivalence Class
  • One example of an FEC includes a set of packets destined for the same destination address prefix.
  • Another example may be a flow of packets with a common quality of service (QoS) between two end-points.
  • Packets forwarded in an equivalent manner by an LSR are assigned the same label and placed in the same output queue of an LSR for transmission through one of the LSR's output ports.
  • QoS quality of service
  • LSRs generally perform the following simplified forwarding algorithm for label switched packets or frames: read the label on incoming packets, determine the FEC by looking up the incoming label in a forwarding table, swap or replace the incoming label in the packet with an outgoing label as determined by the FEC, and place the packet with the outgoing label into an output queue and/or interface for transmission as determined by the FEC.
  • an LSR may add or push a new label onto a label stack, or an LSR may delete or pop a label from a label stack.
  • the use of a label stack allows a label switched frame or packet to carry one or more labels. This capability of using label stacks allows more flexibility for label switching than the use of just a single label.
  • a label stack may be used to carry two labels when a packet is forwarded through a transit routing domain.
  • the use of label stacks as opposed to single labels is well known to those skilled in the art and has been specified in protocol descriptions of tag switching and MPLS.
  • LSP Label Switched Path
  • LSPs label switched paths
  • FEC forwarding equivalence class
  • LSR label switched path
  • the LSP is usually setup from ingress LSR to egress LSR in an ordered fashion.
  • a decision to create an LSP generally is not made by each LSR.
  • the decision to create an LSP in ordered control is usually made by a more centralized algorithm. This might be done at ingress and or egress LSRs.
  • the decision in ordered control might involve an algorithm executing on at least one centralized controller.
  • LSRs label switching routers
  • Some label switching routers have the capability of selectively forwarding packets received with label switching headers using the forwarding algorithms of label switching technologies, while selectively forwarding packets received without label switching headers using forwarding algorithms not associated with label switching technologies.
  • An LSR with such functionality may revert to slower IP routing decisions when it receives an IP datagram without a label header.
  • Some LSRs allocate labels dynamically to flows such that an initial number of IP datagrams below a threshold count from a source to a destination may be forwarded by an LSR using standard IP routing functions. Then a label will be dynamically allocated to the flow for all IP datagrams from the source to the destination over the threshold count within a certain amount of time. Further IP datagram traffic between the source and destination will be labeled and will be processed using the faster performance forwarding algorithm of label switching as opposed to the slower performance algorithm of IP routing.
  • the LSR will expend the processing overhead to create a label for the flow of information between the source and destination so that future transfers of data will utilize the faster forwarding algorithm of label switching instead of the slower forwarding algorithms of routing protocols such as IP.
  • This improved performance of label switching is similar to the improved performance from cache memory architectures because data that has been cached will be handled more quickly than uncached data much as information flows with assigned labels will be handled more quickly than information flows without assigned labels.
  • the binding is known as a data-driven label binding.
  • the binding is known as control- driven label binding.
  • An LSR does not have to use data-driven label binding or control- driven label binding to the mutual exclusion of the other type of binding.
  • the label switching information may be carried in a label header "shim" that is placed between layers 2 and 3 of the OSI model.
  • the shim contains the label switching information and is encapsulated between a layer 2 header and a layer 3 header.
  • the label switching information may be included in the layer 2 header of some protocols such as ATM and frame relay.
  • FIG. 2 shows how label switching information 211 can be placed between the data link layer 102 and the network layer 103.
  • the label switching information 211 usually includes short, fixed length labels to allow simplified and fast forwarding of packets.
  • some protocols such as ATM and frame relay, it is possible to incorporate the label switching information into the layer 2, data link layer addresses as show in FIG.
  • the label switching information could be included in the Virtual Channel Identifier (VCI) field and/or in the Virtual Path Identifier (VPI) field in the ATM header.
  • VCI Virtual Channel Identifier
  • VPI Virtual Path Identifier
  • DLCI Data Link Connection Identifier
  • some protocols can incorporate label switching information within the layer 2, data link addresses, it is not required that these protocols incorporate the label switching information within the layer 2 header. Instead, these protocols can also use the shim label header. Thus, the shim label header may be used with protocols such as ATM or frame relay.
  • some of the label switching information could be included in the layer 2 header and some could be included in a shim label header.
  • protocols such as ATM and frame relay will use the layer 2 headers to incorporate label switching information.
  • ATM and frame relay are only examples of two protocols that currently exist that are capable of incorporating label information within the layer 2 header of the protocol.
  • Other layer 2 protocols may exist that allow label switching information to be incorporated in the layer 2 headers.
  • FIG. 4 shows how multiple layer 2, data link protocols such as Ethernet 402a, token ring 402b, ATM 402c, frame relay 402d, and PPP (Point-to-Point Protocol) 402e as well as multiple layer 3, network protocols such as IPv6 (Internet Protocol version 6) 403 a, IPv4 (Internet Protocol version 4) 403b, IPX (Internetwork Packet eXchange protocol) 403c, and AppleTalk 403d can be used with a label switching layer 411.
  • IPv4 403b is the common IP protocol used in the Internet, while IPv6 403a is a newer revision of the IP protocol.
  • IPX 403c is a protocol often used on Novell networks, while AppleTalk 403d was developed for Macintosh networks.
  • the data link layer protocols and the network layer protocols of FIG. 4 are only examples. Those skilled in the art will be aware that many more data link and network protocols exist and may be used with label switching technologies such as MPLS.
  • MPLS Multi-Protocol Label Switching
  • MPLS was designed to be used with both multiple network layer protocols as well as multiple data link layer protocols. Thus, MPLS has been described as being multi-protocol both above and below.
  • Label switching and MPLS in particular do not fit nicely in the 7-layer OSI model.
  • Label switching is not a layer 2, data link level protocol because it can operate over many layer 2 protocols.
  • it is not a layer 3, network level protocol because it does not have the common addressing and routing functions of a layer 3 protocol.
  • label switching and MPLS violates the abstractions of the 7-layer OSI model, it still provides useful functionality to networks.
  • PPP 402e Point-to-Point Protocol 402e shown as a layer 2, data link protocol in FIG. 4.
  • PPP 402e was designed to provide multiple-protocol encapsulation over point-to-point media
  • the robust features of PPP 402e have been used and expanded to allow its use in many additional environments.
  • PPP 402e provides the capability to encapsulate many protocols and has control mechanisms to allow for the negotiation of settings for various other protocols.
  • PPP 402e has been used in many tunneling protocols for virtual-private networks (VPN) and other uses.
  • VPN virtual-private networks
  • FIG. 5 shows a possible protocol stack where PPP 402e is used in a VPN.
  • VPNs are designed to run over a public network layer 503a such as the IP network of the Internet.
  • VPNs carry a private network layer 503b inside of a protocol such as PPP 402e.
  • the private network layer 503b could be any network layer protocol.
  • PPP 402e frames are carried in an encapsulation protocol layer 511.
  • the Point-to-Point Tunneling Protocol (PPTP) is an example of an encapsulation protocol layer 511.
  • PPTP is based on the Generic Routing Encapsulation (GRE) Protocol.
  • GRE Generic Routing Encapsulation
  • FIG. 6 shows another possible protocol stack where PPP 402e is used in a VPN.
  • the protocol stack in FIG. 6 includes a public network protocol 603a, a private network protocol 603b, a public transport protocol 604a, and a private transport protocol 604b.
  • a public network protocol 603 a such as IP in the Internet and a public transport protocol 604a such as UDP may be used to carry an encapsulation protocol layer 61 1.
  • Example encapsulation protocol layers 611 that would use the protocol stack of FIG. 6 include the Layer 2 Tunneling Protocol (L2TP) and the Layer 2 Forwarding (L2F) protocol.
  • L2TP Layer 2 Tunneling Protocol
  • L2F Layer 2 Forwarding
  • FIG. 5 and FIG. 6 are only a small portion of the possible ways of combining protocols stacks for VPNs and other purposes. They are presented in this present application to show that there are at least two places where MPLS or other label switching information can be placed in the protocol stacks.
  • MPLS or other label switching information can be included between data link layer 102 and public network layer 503a to implement label switching in a public network.
  • label switching information could be used between PPP 402e and private network layer 503b to implement label switching in a private network that has been tunneled through the public network in a VPN.
  • MPLS or other label switching information can be included between data link layer 102 and public network layer 603 a to implement label switching in a public network.
  • label switching information could be used between PPP 402e and private network layer 603 b to implement label switching in a private network that has been tunneled through the public network in a VPN.
  • private label switching information that might exist between PPP 402e and private network layer 503b or 603b
  • label switching information normally carried between data link layer 2 and network layer 3 may occur not only above or in a data link layer 102 directly above a physical layer 101, but also above or in a layer such as PPP 402e that has many of the functions of a data link layer 102 but may be used in a way that is not directly above a physical layer 101.
  • the prior use of MPLS by those skilled in the art would likely be limited to carrying IP datagrams or other network level traffic. This would not include MPEG because those skilled in the art generally would not consider MPEG transport to be a layer 3, network level protocol.
  • each higher level protocol passes information down to a lower level protocol.
  • the information is encapsulated by the lower level and further passed down to an even lower level protocol for further encapsulation. This process is repeated until the frame or packet is completely created for transmission.
  • An inverse process of passing information up to higher level protocols is performed in decoding received frames or packets.
  • most protocol layers build frames or packets using a header, a payload, and an optional trailer or tail.
  • Some protocols use fixed length frames or packets while other protocols use variable length frames or packets.
  • 10 MBPS Ethernet is a variable length data link level protocol with frames varying in size from 64 octets to 1518 octets.
  • ATM has a 53 octet fixed length cell.
  • ways of handling protocols capable of carrying variable length payloads with the two most common being the inclusion of a length field in the header for that protocol and the use of some special flag pattern to indicate the end of a variable length frame or packet.
  • Properly mapping information from higher level protocols into lower level protocols sometimes creates problems when the amount of information from a higher level protocol does not fit the size limitations of the lower level protocol.
  • Various methods are commonly known in the art for breaking large blocks of information into smaller blocks of information for transmission by multiple lower level protocol transmissions.
  • various methods are commonly known in the art for adding stuffing or filling to small blocks of information to fill up the required minimum sizes of frames or packets.
  • packets transverse a network with different maximum transfer unit (MTU) sizes the packets created for a network with a large MTU may have to be fragmented into smaller packets for transmission over networks with a smaller MTU.
  • MTU maximum transfer unit
  • FIGs. 7 - 11 are only intended to be example packets or frames.
  • FIGs. 7 - 11 do not show tails or trailers to the frames or packets is not an indication that the embodiments of the present invention cannot work in environments where the frames or packets have tails or trailers.
  • any references to a label or a label header do not mean to limit a label header to only include a label.
  • the predominate information in a label header is often a label, other information is generally also contained in a label.
  • an MPLS shim header contains a 3 bit experimental field, a 1 bit stack field, an 8 bit Time-to-Live (TTL) field, and one or more 20 bit labels in a label stack.
  • TTL Time-to-Live
  • multiple label shim headers might be used within a single label switched frame for additional flexibility.
  • FIG. 7 shows an example of how MPEG may be encapsulated in IP in a label switched frame.
  • the label switched frame would include a header with layer 2 addressing 702, an IP network layer 703, and an MPEG transport packet in the payload of an IP datagram 704.
  • the label 711 for label switching would be carried between the header with layer 2 addressing 702 and the header for the IP network layer 703.
  • additional protocols such as the user datagram protocol (UDP) may be used between IP network layer 703 and the MPEG transport packet.
  • UDP user datagram protocol
  • the MPEG transport packet may be encapsulated within other protocols, such as UDP, which are then encapsulated inside the payload of an IP datagram 704.
  • FIG. 8 shows how MPEG is commonly encapsulated in IP in a label switched frame.
  • the label switched frame would include an ATM or frame relay header incorporating a label within the layer 2 addressing fields 802, an IP network layer 803, and an MPEG transport packet in the payload of an IP datagram 804.
  • FIG. 9 shows how an ATM or frame relay header 902 might encapsulate an MPEG transport packet in the payload of ATM cells of frame relay frames.
  • this configuration for MPEG has been used for PVCs or SVCs using a Q.2931 as a layer 3 protocol to establish SVCs.
  • the layer 2 ATM header encapsulates an MPEG transport packet while Q.2931 is used as a layer 3 protocol with layer 3 addresses to set up the ATM virtual circuits to carry the ATM cells.
  • the multi-protocol below capability of MPLS means that in the preferred embodiments of the present invention MPEG may be carried in MPLS over other layer 2 protocols besides ATM and frame relay.
  • the label switched paths are not necessarily end-to-end connections between MPEG devices as in the case of the PVCs and SVCs of ATM and frame relay.
  • the labels in general label switching may be distributed by various protocols described below, while the header addresses (t.e., VCI and VPI) of ATM are fixed for PVCs and setup using Q.2931 for SVCs.
  • the LSPs of the preferred embodiments of the present invention may terminate into shared or contention-based media with multiple attached MPEG devices as opposed to the point-to-point link termination of ATM PVCs or SVCs into a single MPEG device.
  • the LSPs may terminate at broadcast or multi-point media capable of being connected to many MPEG-capable subscriber devices.
  • FIG. 10 shows an embodiment of the present invention.
  • an MPEG transport packet 1000 is encapsulated directly inside a label switched payload.
  • the packet in FIG. 10 further comprises a header with layer 2 addressing 1002 and a label header 1011.
  • FIG. 11 shows another embodiment wherein an MPEG transport packet 1100 is encapsulated directly inside a label switched payload found inside an ATM or frame relay header that incorporates a label within the layer 2 header 1102.
  • the LSPs of the preferred embodiments of the present invention may be established by other protocols than the ATM layer 3 connection signaling protocol of Q.2931 that sets up ATM switched virtual circuits to carry ATM cells with MPEG payloads.
  • FIGs. 10 and 11 are not meant to suggest that one and only one MPEG transport packet may be encapsulated into one label switched frame.
  • the embodiments of the present invention could also work, for example, and without limitation, if multiple MPEG transport packets and/or fractions of one MPEG transport packet are encapsulated into a single label switched frame.
  • FIG. 12 shows the common functions of standard routers. These functions can be broken down into a forwarding component 1201 and a control component 1202.
  • the forwarding component 1201 generally contains rules for deciding how to forward packets 1211. In general, these rules specify what information in an incoming packet should be evaluated and compared to a forwarding table to decide how to forward an incoming packet. Unfortunately, in routers these rules became more and more complex to handle different types of packets and forwarding models.
  • Some examples of forwarding models and rules for IP routers include: forwarding rules for unicast 1215, forwarding rules for multicast 1216, and forwarding rules for unicast with type of service (TOS) flags 1217.
  • the common forwarding rule for unicast IP packets generally involves a longest match algorithm that matches the destination address of incoming packets with the entry in the forwarding table that has the longest bit length match of the destination address.
  • the control component 1202 of routers normally maintains the forwarding table used by the forwarding component 1201.
  • the maintenance of this table often requires a protocol to distribute consistent information about the network among multiple routers.
  • the control component normally includes procedures for maintaining and updating the forwarding table 1222.
  • Examples of some common routing protocols that distribute information on routing or forwarding tables include RIP (Routing Information Protocol) 1225, OSPF (Open Shortest Path First) 1226, BGP (Border Gateway Protocol) 1227, and PIM (Protocol Independent Multicast) 1228.
  • RIP Rastered Protocol
  • OSPF Open Shortest Path First
  • BGP Border Gateway Protocol
  • PIM Protocol Independent Multicast
  • FIG. 13 shows the functions of a label switching router (LSR), which is used in label switching networks instead of or in addition to standard routers.
  • LSR label switching router
  • the forwarding component 1301 and the control component 1302 have been separated into two distinct functions. This separation of functions allows simplification of the forwarding component 1301 so that it may more easily be implemented in a fast, all- hardware solution.
  • the rules for deciding how to forward packets 1311 have been reduced to one simple rule, exactly match an incoming label to a label switching forwarding table 1315. This rule can often be implemented in a simple, indexed lookup table. Thus, the forwarding table is simplified.
  • the control component 1302 must still have procedures for maintaining and updating the forwarding table 1322. These procedures can be broken down into three major tasks: path determination 1325, label assignment 1335, and label distribution.
  • Path determination normally involves performing a mapping from a forwarding equivalence class (FEC) to a next hop (t.e. , a next router or LSR where the packet is forwarded to).
  • FEC forwarding equivalence class
  • a next hop t.e. , a next router or LSR where the packet is forwarded to.
  • a network layer routing protocol such as RIP, OSPF, BGP, or PIM usually determines the next hop.
  • RIPv2 RIP version 2
  • RIPv2 is well known in the art and is used for routing in simple for IPv4 networks.
  • RIPv2 covers the usual function of RIPv2 in routed IP networks that may not be using label switching even though the description of the function of RIPv2 is explained by terminology such as forwarding equivalence class (FEC) that is used in label switching networks.
  • FEC forwarding equivalence class
  • RIPv2 packets carry a list of IP network addresses identified by a 32-bit address and a 32-bit mask.
  • each IP network address in the list is associated with a next hop IP address and a hop count.
  • the IP network addresses identified by a 32-bit address and a 32-bit mask are basically a forwarding equivalence class (FEC) such that all IP packets whose destination address field falls within the range specified by an IP network address are forwarded equivalently.
  • FEC forwarding equivalence class
  • An IP packet that matches a forwarding equivalence class is forwarded to a next hop router associated with that FEC.
  • the IP address of the next hop router is specified as the next hop IP address in the RIPv2 packet.
  • the hop count specifies the number of routers that must be transversed before a packet forwarded to the next hop router will reach the IP network specified by the FEC.
  • This type of network is similar to broadcast environments on satellite or cable networks, where a signal is sent to all or most users, but access to the signal is conditional.
  • This type of network is much more deterministic than IP networks.
  • centralized entities determine what content is put on the network and who may have access to the content. For a system where most of the content is transported across the network to the destination and access to the content is conditional, path determination is unlike the path discovery process used in routing protocols such as for IP. Instead the centralized entity must know the topology of the network and enable the proper paths.
  • a centralized system might determine paths during the label assignment process.
  • LSPs label switched paths
  • the preferred embodiments of the present invention propose to further use LSPs to set up broadcast and personal television paths for MPEG transport.
  • at least one centralized controller can accomplish the function of creating paths and assigning labels.
  • DNCS Digital Network Control System's
  • SRM Session and Resource Manager
  • DBDS Scientific-Atlanta's Digital Broadcast Delivery System
  • DSM-CC SRM MPEG Digital Storage Media-Command and Control Session and Resource Manager
  • the at least one centralized controller could base label assignments on information associated with MPEG transport packets whose format is described below. For instance, an entire MPEG transport stream might need to transverse the same label switched path (LSP), be bound for the same destination, and have identical quality of service (QoS) requirements. In such a situation all the MPEG programs in the transport stream are part of the same forwarding equivalence class (FEC). This FEC would be given an MPLS label that would designate the entire transport stream including more than one MPEG program and the associated program specific information (PSI). This method of label assignment would be useful for transporting MPEG streams over a channel that may contain more than one MPEG transport stream because the MPEG packet IDs (PIDs) in MPEG transport packets are only unique over one MPEG transport stream.
  • PIDs MPEG packet IDs
  • MPLS or other label switching technologies could be used to allow MPEG transport packets with identical PIDs but belonging to different MPEG transport streams to be time-division multiplexed into the same channel or medium.
  • PAT Program Association Table
  • PAT Program Association Table
  • the Program Association Table is only one example of two MPLS or other label switching forwarding equivalence classes (FECs) carrying two different MPEG transport packets that might have the same PID number.
  • the advantage of using MPLS or other label switching technology to carry two or more MPEG transport streams will work to differentiate MPEG transport packets belonging to different MPEG transport streams even though the MPEG transport packets have the same PID values.
  • MPLS labeled transport streams could group the same programs that are normally provided in a frequency-division multiplexed (FDM) channel in cable TV systems. This in effect enables an evolution from the current broadband, FDM cable TV system to a full baseband, transport cable TV system.
  • an MPLS preselector or switch might replace the RF tuner found in current subscriber devices for FDM cable TV systems. This would allow existing MPEG transport engines to operate with baseband streams capable of much higher data rates than individual FDM channels.
  • an MPLS label could be applied to one MPEG program that is part of an MPEG transport stream. This in effect creates a one-program MPEG transport stream and requires program specific information (PSI) for each program. This type of assignment might be useful for unicast cases where individual subscribers desire stream control so that only one program falls in a forwarding equivalence class (FEC).
  • PSI program specific information
  • MPEG transport packet IDs identify particular flows of information such as a video program stream. These PIDs could be used by and/or assigned by at least one centralized controller as part of the label assignment function.
  • the stream ID found in the header of an MPEG packetized elementary stream (PES) also might be used by at least one central controller as part of the label assignment process.
  • PID and the stream ID are more closely related to the source or content of a stream of MPEG data.
  • MPEG transport already allows merging two MPEG streams to create a new MPEG stream. This type of merge might be done to merge an MPEG stream of normal program content with an MPEG stream of advertising content.
  • MPEG transport also allows merging MPEG streams with private data streams that might contain IP datagrams.
  • MPLS or other similarly capable label switching technology additional multiplexing and merging techniques are possible. For example, multiple MPEG program streams with different PIDs could be merged into one MPLS forwarding equivalence class (FEC) that contains two MPEG programs, which share the same MPLS label.
  • FEC MPLS forwarding equivalence class
  • Label distribution involves informing label switching routers (LSRs) of label assignments by distributing the label binding information over communication paths.
  • MPLS does not specify a required protocol for distributing labels so there are various proposals for label distribution.
  • One proposed method is to distribute label assignment information with the routing protocols by including the information in the packets of RIP, OSPF, BGP, etc.
  • Another proposed method is to use the Resource ReSerVation Protocol (RSVP) to distribute labels.
  • RSVP was primarily designed for informing network equipment about information flows in an IP network. Once informed about information flows by RSVP, the network equipment may allocate resources to information flows in order to implement various quality of service (QoS) criteria for an information flow.
  • QoS quality of service
  • RSVP label switched paths
  • RSVP is basically a signaling protocol for establishing QoS for integrated services over IP- oriented networks.
  • the IETF has developed a new protocol for label distribution called the Label Distribution Protocol (LDP) that is more generalized and less IP-centric than RSVP.
  • LDP Label Distribution Protocol
  • Constraint-based routing is one way to provide quality of service in a label switched network by determining suitable routes with the network resources to meet a variety of constraints such as a minimum bandwidth.
  • the Constraint-based Routing Label Distribution Protocol (CR-LDP) is an extended version of LDP that enables constraint-based routing and QoS reservation in label switching networks such as an MPLS network.
  • the preferred embodiments of the present invention propose to use the MPEG Digital Storage Media-Command and Control (DSM-CC) protocol for label distribution to MPEG-aware devices such as MPEG-aware LSRs. Label distribution using DSM-CC may occur as part of the process of setting up DSM-CC sessions.
  • DSM-CC is an MPEG protocol specification for signaling MPEG sessions.
  • DSM-CC consists of two main protocols: 1) a DSM-CC user-network signaling protocol and 2) a DSM-CC user-user signaling protocol.
  • the DSM-CC user-network protocol is designed to signal the network to setup MPEG sessions for MPEG user devices.
  • MPEG user devices include subscriber terminal equipment, which might initiate the download of an MPEG movie.
  • MPEG user equipment includes MPEG video or audio servers, which may initiate the download of MPEG information to subscriber devices.
  • the MPEG DSM-CC user- network protocol is somewhat similar to common layer 3 signaling protocols such as Q.931 used for circuit-switched connection establishment in narrowband ISDN or Q.2931 used for switched virtual-circuit establishment in ATM.
  • Q.2931 is basically an extended version of Q.931 to provide for more sophisticated quality-of-service requirements than are possible in Q.931.
  • DSM-CC was not really designed to initiate network setups. Instead, if MPEG devices are connected to a circuit switched network, then Q.931 might be used to establish circuit-switched connections between MPEG devices. Next, DSM-CC user- network signaling would establish the MPEG video or audio sessions between MPEG user devices over the circuit-switched paths. Alternatively, if MPEG devices are connected to an ATM packet-switched, virtual-circuit network, then Q.2931 might be used to establish SVCs between MPEG devices. Next, DSM-CC user-network signaling would establish the MPEG video or audio sessions between MPEG user devices over the SVCs. The DSM-CC user-user protocol is designed to send control information between MPEG user devices.
  • the DSM-CC user-user protocol may be used by an MPEG subscriber device to control a video flow from an MPEG video source.
  • the subscriber device may be able to use VCR-like functional control to pause, rewind, or fast-forward video from an MPEG video source using the DSM-CC user-user protocol.
  • the DSM-CC standard covers various types of sessions such as Continuous Feed Sessions (CFS) and Exclusive Sessions (ES).
  • CFS Continuous Feed Sessions
  • ES Exclusive Sessions
  • UN user to network
  • UU user to user
  • the DSM-CC standard does not define network to network messages. If an external server wants to set up a continuous feed session (CFS), then it uses one or more user to network (UN) messages. Similarly, if an external client wants to create an exclusive session (ES), then it also uses one or more user to network (UN) messages. If a client wants to control a server, then one or more user to user (UU) messages are communicated.
  • allocation of resources in the network may be accomplished through the communication of other protocols besides DSM-CC.
  • DSM-CC continuous feed session
  • various non-DSM-CC messages may be used to establish the CFS.
  • the protocols carrying these messages might include remote procedure call (RPC) and or simple network management protocol (SNMP) as examples of protocols that may be used to communicate resource allocations in a CATV network between equipment such as a controller and a modulator.
  • RPC remote procedure call
  • SNMP simple network management protocol
  • These additional protocol messages might also be used to distribute labels during the process of setting up and managing DSM-CC sessions.
  • the labels may be distributed in DSM-CC messages or other non-DSM-CC protocols as part of the process of establishing DSM-CC sessions.
  • label distribution protocols such as LDP, CR-LDP, and/or RSVP could be used to distribute labels to non-MPEG-aware network equipment (e.g., LSRs) in a label switching network.
  • LSRs non-MPEG-aware network equipment
  • the preferred embodiments of the present invention propose that the label distribution messages for MPEG DSM-CC and other protocols for label distribution may be carried in IP datagrams because of the generally ubiquitous nature of basic IP functionality in network devices. Basic IP functionality is often included in network devices to allow such common capabilities as network management. Still, the embodiments of the present invention are in no way limited to only distributing label information in IP datagrams.
  • standard IP messages may be used to implement the MPLS control component functions of path or route determination, label assignment, and label distribution.
  • the devices and methods of the embodiments of the present invention may be used in a network that carries IP network level traffic.
  • the embodiments of the present invention make it possible to carry MPEG transport packets directly within MPLS or other label switched technology without the necessity of placing the MPEG transport packets inside IP datagrams or other network level protocol messages.
  • MPEG Motion Pictures Expert Group
  • MPEG-2 includes a Systems Specification 1401 that defines some of the interfaces for MPEG packets as shown in FIG. 14.
  • FIG. 14
  • FIG. 14 shows one interface of the MPEG Systems Specification 1401 as the dashed line 1405.
  • Video data 1415 goes through video encoder 1417 into the MPEG systems specification 1401.
  • This MPEG encoded video from video encoder 1417 is output on connection 1419 and is input into packetizer 1421 to create a video packetized elementary stream (PES) 1425.
  • FIG. 14 shows audio data 1435 going through audio encoder 1437 into MPEG systems specification 1401.
  • This MPEG encoded audio from audio encoder 1437 is output on connection 1439 and is input into packetizer 1441 to create audio packetized elementary stream (PES) 1445.
  • Video PES 1425 is combined with audio PES 1445 in MPEG program stream mux (or multiplexer) 1455 to create MPEG program stream 1465.
  • video PES 1425 is combined with audio PES 1445 in MPEG transport stream mux (or multiplexer) 1475 to create MPEG transport stream 1485.
  • An MPEG elementary stream is an output from an audio or video encoder. Before communicating this MPEG elementary stream, it must be packetized into a packetized elementary stream (PES).
  • MPEG systems specification 1401 comprises rules for creating MPEG program streams 1465 and MPEG transport streams 1485.
  • MPEG program streams 1465 include information to carry a single MPEG program.
  • An MPEG program comprises different PES streams that share a common time base.
  • an MPEG movie may include a video PES, an English audio track, and a Spanish audio track all as one program.
  • the MPEG program stream 1465 from MPEG program stream multiplexer 1455 is designed to allow local delivery of MPEG programs to players such as a VCR- like unit playing a movie on a locally connected TV.
  • the MPEG transport stream 1485 from MPEG transport stream multiplexer 1475 is designed to allow delivery of MPEG programs across communication networks in MPEG transport packets.
  • the MPEG transport protocol is designed to carry one or more MPEG programs and to communicate the programs in MPEG transport packets.
  • the MPEG program and the MPEG transport specifications are designed to carry additional information such as private data, time synchronization information, and service and control information.
  • An example of private data might be closed captioning for an MPEG movie.
  • the private data portion of MPEG transport may even carry IP datagrams.
  • FIG. 15 shows how elementary streams of video are placed in packetized elementary streams (PES) and MPEG transport packets.
  • Elementary stream 1505 is an I- Picture, which is an encoded "intra” frame of video that is part of the algorithm used in MPEG video compression.
  • Elementary stream 1506 is a P-Picture, which is an encoded "predictive" frame of video that is part of the algorithm used in MPEG video compression.
  • the I- Picture elementary stream 1505 is packetized into a packetized elementary stream (PES) comprising PES Header 1515 and PES Data 1516, which includes the data from the I- picture frame 1505.
  • PES packetized elementary stream
  • the P-Picture elementary stream 1506 is packetized into a packetized elementary stream (PES) comprising PES Header 1525 and PES Data 1526, which includes the data from the P-picture frame 1506.
  • the packets of a PES include a stream ID in the header of PES packets. These stream IDs allow determination of the type of information contained in a PES packet.
  • FIG. 15 further shows how one variable length PES packet comprising PES header 1515 and PES packet payload 1516 and containing data from an I-picture elementary stream is encapsulated into several fixed length MPEG transport stream packets.
  • MPEG transport stream packet with transport stream header 1535 contains an MPEG transport stream packet payload 1536 encapsulating PES header 1515 and the first part of the packetized data from the I-Picture 1516.
  • MPEG transport stream packet with transport stream header 1545 contains an MPEG transport stream packet payload 1546 encapsulating the second part of the packetized data from the I-Picture 1516.
  • MPEG transport stream packet with transport stream header 1555 contains an MPEG transport stream packet payload 1556 encapsulating the final part of the packetized data from the I-Picture 1516 as well as stuffing bits to fill out the MPEG transport packet to its fixed length size.
  • the MPEG transport stream packet header includes a 13 bit field known as a packet ID or PID that is used to identify information in the MPEG transport multiplexing hierarchy.
  • This PID field can include values from 0 to 2 13 - 1 or 8191 (decimal). Some of the PID values such as 0 and 1 are assigned to specific tables. PID values 2 to 15 (decimal) are reserved for future use. PID value 8191 (decimal) designates a null packet, while PID values 16 to 8190 (decimal) are available for PES streams, map tables, and network tables.
  • FIG. 16 shows an example of how the multiplexing architecture of MPEG transport works.
  • the first entry in the Program Association Table 1605 associates program 0 with PID 20.
  • the Network Information Table (NIT) 1625 contains information about the network properties of the network carrying the MPEG transport packets.
  • the Network Information Table (NIT) 1625 is generally associated with program 0 in the Program Association Table (PAT) 1605.
  • Program Association Table (PAT) 1605 further shows an example of three MPEG programs: program 1, program 22, and program 35.
  • Program Map Table 1635 for program 1 contains a table listing the Packetized Elementary Streams (PES) included in program 1.
  • PES Packetized Elementary Streams
  • Program Map Table 1645 for program 22 contains a table listing the Packetized Elementary Streams (PES) included in program 22.
  • PES Packetized Elementary Streams
  • Program Map Table 1655 for program 35 contains a table listing the Packetized Elementary Streams (PES) included in program 35.
  • PES Packetized Elementary Streams
  • FIG. 17 shows an example of how a CATV network might utilize MPEG transport packets in a label switching header.
  • the network of FIG. 17 is only meant to be one example of the many possible networks. Those skilled in the art will be aware of additional implementations, which are intended to be included in the present invention.
  • Some of the equipment in the network of FIG. 17 would be MPEG-aware (i.e., capable of interpreting MPEG transport packets within the label switching header) while other equipment may not be able to directly decode MPEG transport packets (i.e. , be non- MPEG-aware).
  • LSR Label Switching Router
  • CO central office
  • LSR 1705 would be MPEG-aware and take input from co-located MPEG source 1707 or co-located storage 1709 that may have stored or cached MPEG programs.
  • other MPEG sources such as MPEG source 1711 may be connected to LSR 1705 through various networks such as long distance delivery network 1715.
  • the long distance network 1715 may or may not be MPEG-aware.
  • the long distance delivery network 1715 may be made up of other label switching routers, SONET rings, or a virtual private network with a guaranteed quality of service that is tunneled through the public Internet. These are just some examples of delivery networks that may be used to implement long distance delivery network 1715, and none of these examples is intended to limit the present invention in any way.
  • Label Switching Router (LSR) 1705 would be further connected to a local delivery network 1725.
  • a delivery network is described in U.S. Patent Application entitled “A System Architecture For Customized CATV Services," by Luis A. Rovira, Lorenzo Bombelli, Paul Connolly, Donald L. Sipes, Jr., and Douglas Woodhead, filed on the same day as the present application with Attorney Docket No. A-6551, and is hereby incorporated by reference in its entirety.
  • This network would connect LSR 1705 to other MPEG-aware LSRs such as LSR 1735.
  • the network would work with non-MPEG-aware LSRs such as LSR 1745, which is also connected to local delivery network 1725.
  • MPEG-aware LSR 1735 could be connected in a first distribution hub to distribution interface 1755, which may be MPEG-aware and which is further connected to subscriber distribution network 1757.
  • Subscriber device 1765 is an example of an MPEG-aware device connected to subscriber distribution network 1757.
  • Non-MPEG-aware LSR 1745 could be connected in a second distribution hub to distribution interface 1775, which may be MPEG-aware and which is further connected to subscriber distribution network 1777.
  • Subscriber device 1785 is an example of an MPEG-aware device connected to subscriber distribution network 1777.
  • MPEG-aware LSR 1705 would be connected to an MPEG Digital Storage Medium-Command and Control (DSM-CC) Session and Resource Management (SRM) server 1795, which would also likely be co-located at a headend or central office (CO).
  • DSM-CC MPEG Digital Storage Medium-Command and Control
  • SRM Session and Resource Management
  • the DSM-CC SRM server 1795 can be used for managing MPEG session establishment and session release.
  • the DSM-CC protocol can be used to distribute labels to MPEG-aware LSRs 1705 and 1735.
  • Other label distribution protocols such as LDP (Label Distribution Protocol), CR-LDP (Constraint-based Routing-LDP), and/or RSVP (Resource ReSerVation Protocol) can be used to distribute labels to non-MPEG-aware LSRs such as LSR 1745.
  • a new set of services known generally as personal TV is a non-limiting example of how subscriber-customized information might use the enhanced network capabilities resulting from the preferred embodiments of the present invention.
  • Personal TV encompasses at least five basic functions or abilities.
  • a first function of personal TV might be broadcast-on-demand or MPEG multicast, which involves the ability to deliver, simultaneously to multiple subscribers who request it, content that is not broadcast to all subscribers or does not occupy the broadcast portion of the CATV spectrum.
  • Another function of personal TV might be the ability to deliver stored content on demand from a number of storage locations.
  • a third function of personal TV might be the ability to retrieve broadcast content whose simultaneous broadcast time has already passed. Although this time shifting function could be implemented by a subscriber's customer premise equipment (CPE) such as a video cassette recorder (VCR) or other form of personal video recorder (PVR), providing this capability with equipment in the network allows a subscriber to watch a previously broadcast program even though the subscriber did not previously anticipate the need to record the content.
  • CPE customer premise equipment
  • VCR video cassette recorder
  • PVR personal video recorder
  • a fourth function of personal TV might be the ability of subscribers to exercise control over broadcast streams, which may include VCR-like features of pause and replay. These features could be implemented by creating a unicast stream for a subscriber or user that has initiated a pause or replay request.
  • a fifth function of personal TV might be the ability to insert targeted or customized advertising into streams.
  • Such customized advertising screens may be carried in IP datagrams or in other existing or yet to be developed protocols.
  • the ability to layer communication protocols means that the IP datagrams may be delivered to user devices through many methods.
  • One example includes delivering the IP datagrams in packets without label switching headers.
  • Another example may be delivering IP datagrams in packets with label switching headers.
  • some LSRs dynamically allocate labels to IP datagram flows based upon the number of IP datagrams reaching a threshold count in a specified amount of time.
  • the IP datagrams may or may not be carried in label switched frames.
  • the IP datagrams may or may not be carried in label switched frames.
  • the IP datagrams may or may not be carried in label switched frames.
  • IP datagrams might be carried in the private data streams of MPEG transport packets. None of these examples of carrying IP datagrams are intended to be limiting in any way. They are only meant as examples of how IP datagrams may be multiplexed with MPEG transport in at least one embodiment of the present invention, which involves natively or directly carrying MPEG transport packets inside of label switched frames such as the frames of MPLS.
  • FIG. 17 will be referenced in the explanation of the following examples.
  • MPLS will be assumed to be the label switching protocol used by local delivery network 1725.
  • the techniques of the present invention are not necessarily limited to MPLS.
  • other label switching protocols capable of carrying MPEG might also be used.
  • the headend or CO system operator has identified content from MPEG source 1707 or MPEG source 1711 that should be delivered to subscriber device 1765 on subscriber distribution network 1757. If the content is to be placed on the broadcast or narrowcast portion of distribution network 1757, then label switching of MPEG transport as described in the preferred embodiments of the present invention is not required.
  • MPEG would be broadcast as normally done for carrying multiple channels to subscriber locations such as through current FDM and TDM techniques in the cable network.
  • the content from MPEG source 1707 or MPEG source 171 1 is to implement a personal TV service such as broadcast-on-demand, then the content will be switched by and or pass through at least some of the LSRs of local delivery network 1725.
  • LSR 1735 is an MPEG-aware label switching router that is specifically designed for interpreting and acting on MPEG transport in MPLS.
  • LSR 1745 is an MPLS compliant label switching router that is neither aware of nor capable of acting on the MPEG content within the MPLS frames.
  • the MPEG packets may only be addressed to subscribers who request the content, but many subscribers may want to view this content in real-time, simultaneously with the subscribers that requested the broadcast-on-demand.
  • the operator may use the DSM-CC Session and Resource Manager (SRM) 1795 to preconfigure sessions; thus establishing a path and the required resources to deliver this content to the subscribers on subscriber distribution network 1757.
  • SRM DSM-CC Session and Resource Manager
  • Such a preconfiguration would be done by establishing a DSM-CC Continuous Feed (CF) session.
  • Subscribers on subscriber distribution network 1757 may use a DSM-CC Client Session Setup Request to connect to this service and to be bound to the existing CF session.
  • conditional access (CA) process from the MPEG transport Conditional Access Table (CAT) may be activated to ensure proper authorization to decrypt the broadcast-on-demand content.
  • Use of the conditional access table in a network is optional and does not have to be implemented to obtain the benefits of the embodiments of the present invention.
  • a second headend or CO were connected to long distance delivery network 1715.
  • the equipment co-located in this second headend might be similar to the equipment co-located at the headend shown in FIG. 17 (i.e., the first headend).
  • This equipment in the first headend possibly includes LSR 1705, MPEG source 1707, storage 1709, and DSM-CC SRM 1795.
  • the second headend (not shown in FIG. 17) would have similar equipment.
  • the LSRs would be connected by another local delivery network similar to local delivery network 1725 connected to LSR 1705 as shown in FIG. 17.
  • MPEG source 1711 could provide the DSM-CC SRM in the second headend (not shown) with the same MPLS label already used for the content from MPEG source 1711 by the first headend.
  • the DSM-CC SRM in the second headend could use the provided MPLS label or select a new label.
  • Label conflicts between the two headends can be resolved because MPLS labels have only local significance to a particular network link.
  • Label switching routers may change the labels of a packet as it comes into the LSR from one link and leaves the LSR through another link.
  • DSM-CC SRM 1795 may assign the MPLS label to the stream during the DSM-CC session setup process. The DSM-CC SRM 1795 may then use MPEG DSM-CC signaling to distribute the label to MPEG- aware, DSM-CC compliant equipment in the signal path. Distribution interfaces 1755 and 1775 may terminate the label switched paths (LSPs) of the label switching network or the LSPs may extend all the way to subscriber devices such as 1765 and 1785.
  • LSPs label switched paths
  • the DSM-CC signaling messages could be carried in IP datagrams that are directly addressed to specific equipment involved in a continuous feed (CF) session.
  • the DSM- CC SRM 1795 could be used to initiate standard signaling such as CR-LDP and to provide the information for a constrained path.
  • a constrained path is a path for a flow of information packets that is constrained to those path segments that meet the quality of service requirements of the information flow.
  • the headend operator has identified the content for a broadcast-on-demand continuous feed session to be a candidate for stream control by subscribers.
  • Such stream control may include VCR-like functions of pausing, rewinding, and fast-forward searching.
  • the content of the program must be cached in a device such as storage 1709 before a subscriber chooses to rewind the program.
  • CF continuous feed
  • DSM-CC SRM 1795 would receive the request and setup a DSM-CC Exclusive Session (ES) between storage 1709 and the requesting subscriber device 1785 including any MPEG-aware components in the signal path such as distribution interface 1775.
  • MPLS labels associated with the exclusive session (ES) could be distributed in session setup messages to MPEG-aware devices such as storage 1709, LSR 1705, and distribution interface 1775.
  • MPLS labels associated with this exclusive session could be distributed to non-MPEG-aware devices such as LSR 1745 using the Label Distribution Protocol (LDP) or by other means.
  • Stream control commands such as pause or rewind between subscriber device 1785 and storage 1709 may use the command set of the DSM-CC user-user signaling protocol, or they may be implemented with other commands that have been designed into the client and server applications.
  • embodiments of the present invention may be implemented using at least one dedicated logical circuit, at least one processor and software, or at least one combination circuit that includes at least one processor circuit with software and at least one specific dedicated circuit.
  • Those, skilled in the art of implementing protocol specifications will be familiar with the design tradeoffs of implementing hardware and software functions. It is understood that all such permutations of various implementations are included herein.
  • the software which comprises an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
  • a "computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
  • the computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
  • the computer- readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical).
  • an electrical connection having one or more wires
  • a portable computer diskette magnetic
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CDROM portable compact disc read-only memory
  • the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'encapsulation de la norme MPEG (Groupe d'experts pour le codage d'images animées) dans un protocole de commutation de labels tels que le MPLS (commutation de labels multiples) est utilisée pour mettre en oeuvre un réseau de communication multimédia. Le réseau améliore de manière avantageuse la distribution de services personnalisés aux abonnés du réseau. L'encapsulation de la norme MPEG dans le protocole MPLS simplifie le déploiement du réseau du fait de la convergence d'environnements auparavant distincts de communication de données et de service de télédiffusion sur des réseaux télévisuels câblés. En outre, l'encapsulation de la norme MPEG dans le protocole MPLS permet de fusionner des flux de contenu de programme MPEG et des flux IP au niveau du multiplexage MPLS. Ceci permet des applications telles que la fusion de programmes vidéo MPEG et de publicité IP. De plus, le protocole de commande et de contrôle du stockage numérique MPEG (DSM-CC) peut être utilisé pour la distribution de labels dans un réseau de commutation de labels.
EP01994094A 2000-11-28 2001-11-27 Norme mpeg dans un environnement de commutation de labels Withdrawn EP1338147A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US724015 1985-04-17
US72401500A 2000-11-28 2000-11-28
PCT/US2001/044264 WO2002052864A2 (fr) 2000-11-28 2001-11-27 Norme mpeg dans un environnement de commutation de labels

Publications (1)

Publication Number Publication Date
EP1338147A2 true EP1338147A2 (fr) 2003-08-27

Family

ID=24908608

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01994094A Withdrawn EP1338147A2 (fr) 2000-11-28 2001-11-27 Norme mpeg dans un environnement de commutation de labels

Country Status (3)

Country Link
EP (1) EP1338147A2 (fr)
CA (1) CA2430164A1 (fr)
WO (1) WO2002052864A2 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
PL355743A1 (en) * 2002-08-28 2004-03-08 Advanced Digital Broadcast Polska Spółka z o.o. Method of data flow control in a system with packet data transmission and system for data flow control in a system with packet data tranmission
US7735111B2 (en) 2005-04-29 2010-06-08 The Directv Group, Inc. Merging of multiple encoded audio-video streams into one program with source clock frequency locked and encoder clock synchronized
KR100724886B1 (ko) * 2005-07-18 2007-06-04 삼성전자주식회사 Ｄｍｂ 서비스에 대한 패킷 방식의 재전송 시스템 및 그장치

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5666487A (en) * 1995-06-28 1997-09-09 Bell Atlantic Network Services, Inc. Network providing signals of different formats to a user by multplexing compressed broadband data with data of a different format into MPEG encoded data stream
US5787089A (en) * 1996-07-25 1998-07-28 Northern Telecom Limited Digital signal broadcasting
US6882643B1 (en) * 1999-07-16 2005-04-19 Nortel Networks Limited Supporting multiple services in label switched networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO02052864A3 *

Also Published As

Publication number Publication date
CA2430164A1 (fr) 2002-07-04
WO2002052864A2 (fr) 2002-07-04
WO2002052864A3 (fr) 2002-12-27

Similar Documents

Publication Publication Date Title
US7149210B2 (en) Wide area multi-service communications network based on dynamic channel switching
US7031301B1 (en) Communication management system and method
US7136356B2 (en) Packet data transfer method and packet data transfer apparatus
US7181759B2 (en) System and method for providing interactivity for end-users over digital broadcast channels
EP1709808B1 (fr) Systeme et procede de transport et de lecture de signaux
CA2463097C (fr) Mecanisme de mise en oeuvre de la decouverte reseau dans un reseau cable
US7395346B2 (en) Information frame modifier
US7451475B1 (en) Method for delivery of narrow-cast data over digital broadcast channels
US20050175085A1 (en) Method and apparatus for providing dentable encoding and encapsulation
WO2009108763A1 (fr) Réseaux de paquets sans perte
KR20110061505A (ko) 상호 계층 최적화를 이용한 멀티미디어 데이터 패킷을 송신하는 방법 및 장치
KR100565942B1 (ko) 이더넷 기반의 방송 및 통신 융합 시스템 및 그 방법
KR101744355B1 (ko) 상호 계층 최적화를 이용한 멀티미디어 데이터 패킷을 송신하는 방법 및 장치
US6999477B1 (en) Method and system for providing multiple services to end-users
US20030097663A1 (en) Method and apparatus for dynamic provisioning of IP-based services in a DVB network
US8315255B1 (en) Psuedo wire merge for IPTV
US20070033477A1 (en) Packet based retransmission system for DMB service and apparatus therefor
EP1338147A2 (fr) Norme mpeg dans un environnement de commutation de labels
Negru et al. Dynamic bandwidth allocation for efficient support of concurrent digital TV and IP multicast services in DVB-T networks
US20060087970A1 (en) Method for encoding a multimedia content
KR102060410B1 (ko) 멀티미디어 데이터 패킷을 수신하는 방법 및 장치
Dubois et al. Television Services over an IP/MPLS Convergent Satellite System
Schonfeld Video communication networks
Jian-Cun et al. Delivery Digital Television Services over Ethernet.
Vehkapera et al. Cross-layer Architecture for Scalable Video

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030617

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB NL

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20040609