1 / 8

IETF#66 – 10-14 July 2006 FECFRAME Overview of 3GPP FEC Framework

IETF#66 – 10-14 July 2006 FECFRAME Overview of 3GPP FEC Framework. Mark Watson. Architecture. Content Delivery Protocol. Definition of flows to be protected and flow to carry protection data Rules/indications for source data partitioning/timing. Application. Application/Transport protocols

elisabethj
Download Presentation

IETF#66 – 10-14 July 2006 FECFRAME Overview of 3GPP FEC Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF#66 – 10-14 July 2006FECFRAMEOverview of 3GPP FEC Framework Mark Watson

  2. Architecture Content Delivery Protocol Definition of flows to be protected and flow to carry protection data Rules/indications for source data partitioning/timing Application Application/Transport protocols (RTP, RTCP, MIKEY etc.) Construction of source block from source data Mapping of source and repair symbols into FEC source and FEC repair packets FEC Streaming Framework FEC Scheme UDP Provides encoding and decoding of FEC data. Defines signaling requirements (Object Transmission Information, FEC Payload IDs) IP

  3. FEC Streaming Configuration Information • “One-off” information provided by application to FEC Streaming Framework at encoder and decoder • Defines: • The set of source UDP flows to be protected • The UDP flow that will carry the repair data • FEC Encoding ID to identify the FEC code in use • 3GPP defines SDP attributes for applications to signal this information

  4. Source Block construction • FEC codes calculated over a logical ‘source block’ • Source Block consists of concatenated ‘source packet information’ (SPI) for each packet in the block • Arrangement of packets into blocks is out of scope • Common example is based on time – source blocks all have approximately the same playout duration (“protection period”) • Source Packet Information consists of • UDP flow identifier (1 byte) • UDP Packet Length (2 bytes) • UDP Payload • Padding bytes • SPI always starts on an FEC Symbol Boundary within the source block (symbols can be any size, but within a source block they are all the same size) • FEC framework adds/removes padding to symbol boundaries at encoder and decoder

  5. Source Packet Tagging • Source Packets are tagged with an FEC Payload ID, indicating • The source block number for the packet • The source symbol the SPI for the packet starts at • FEC Payload ID field defined by FEC Scheme and appended to the packet by the FEC Streaming Framework • Note that FECFRAME may support other ways of identifying source packets in specific contexts e.g. RTP Sequence Number – FEC Schemes can specify different ways

  6. Source packet format IP header UDP header UDP payload FEC Payload ID FEC Payload ID placed at end of packet so that ROHC will still compress RTP headers in the case of RTP packets.

  7. Repair packets • Repair packets contain FEC repair symbols • FEC Payload ID in repair packets identifies the repair symbols • Format of this field defined by FEC Schemes

  8. Repair packet format IP header UDP header FEC Payload ID FEC Symbols

More Related