Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [[RFC2119]].

All sections and appendixes, except "Introduction", are normative, unless they are explicitly indicated to be informative.

Terminology

MPEG-2 Transport Stream

The carriage of A/V content and related information (e.g. subtitles) in an MPEG-2 transport stream SHALL be in compliance with [[!TS101154]] clause 4, with the following additional constraints:

• Only a single program SHALL be contained in the transport stream. The transport stream SHALL contain only one Program Map Table (PMT).
• The "TS Optional-SI" profile of PSI/SI carriage, as defined in [[!TS102034]] SHALL be applied, i.e. the Program Association Table (PAT) and Program Map Table (PMT) are REQUIRED, and DVB-SI [[!DVBSI]] is OPTIONAL. However, the carriage of EIT for the associated content is RECOMMENDED, as specified in section 4.1.3 of Volume 3 [[.OIPF_META2]].
• The transport stream MAY contain EIT as specified in section 4.1.3 of Volume 3 [[.OIPF_META2]].
• The transport stream MAY contain MPEG-2 encoded AIT as defined in section 5.3 of [[!TS102809]]. This SHALL be supported as defined in [[.OIPF_DAE2]] and below:
  • The application type used for DAE applications in section 5.2.2 of [[!TS102809]] SHALL be 0x0011 (to signal "OIPF DAE").
  • If the optional data_broadcast_id_descriptor is used for carousels carrying DAE applications then the value to be used for the data_broadcast_id field of SHALL be 0x0150 (to signal "OIPF Object Carousel").
  • A maximum of one sub-table (i.e. using only one PID) signalling DAE applications shall be transmitted per service.
  • All sections of the AIT sub-table for DAE applications shall be transmitted at least once every second.
• The transport stream MAY contain DAE applications transmitted using the DSM-CC object carousel as defined in section 7.1 of [[!TS102809]].
• The transport stream MAY contain "do-it-now" DSM-CC stream events as defined by section 8.1 of [[!TS102809]].
• The maximum streaming bitrate for a transport stream carrying SD content SHALL NOT exceed 8.0 Mbit/s.
• The maximum streaming bitrate for a transport stream carrying HD content SHALL NOT exceed 24.0 Mbit/s.
• Transport streams MAY contain media zone information (zone map), possibly including navigation constraints, using the signalling mechanisms specified in [[!MRL-DMZ]]. Rules about the handling of Marlin media zone information by the OITF, for both unprotected and protected content, are contained in section 6 of [[.OIPF_CSP2]]. Note: this means an MPEG-2 transport stream may contain a DMZ descriptor in the PMT and one or more private_sections in the stream, with PID as signalled in DMZ descriptor, and containing zone map information (i.e., navigation constraints), all according to [[!MRL-DMZ]] section 7.2.
• Transport streams containing 3D content SHALL comply with the following requirements:
  • The PMT SHALL include the AVC_video_descriptor according to [[!DVB3D]] section 6.1.
  • If SDT and/or EIT are present, it SHALL meet the requirements of [[!DVB3D]] section 6.2.

The preceding specification of the MPEG-2 transport stream format is referred to as the TS systems layer format.

An additional variant of the TS format is defined, namely the time stamped MPEG-2 transport stream, as defined in [[!DLNAMEDIA]] section 9.3.4.4, applied to the TS systems layer format.

The time stamped MPEG-2 transport stream format is referred to as the TTS systems layer format.

The methods to protect (encrypt) MPEG-2 transport streams are specified in Volume 7 [[.OIPF_CSP2]]. Volume 7 specifies two approaches for content and service protection, namely the terminal-centric approach and the gateway-centric approach.

For the terminal-centric approach and for the output of the CSP gateway in the gateway-centric approach, the protected MPEG-2 transport stream SHALL comply with protection system signalling as specified in [[!MPEG2TS]] and MAY use the Conditional Access Table (CAT) as defined therein. This protected format is referred to generically as PF.

For the gateway-centric approach, the input stream to the CSP gateway is not specified, except in the case of the CI+ gateway-centric approach, where the input stream SHALL comply with the PF format. PF applies to both the TS and TTS systems layer formats.

The protected MPEG-2 transport stream format for the terminal-centric approach is further defined in [[!MRL-BBTS]] and is referred to as BBTS. BBTS applies to both the TS and TTS systems layer formats.

The OITF SHALL support the application signaling and in-band delivery of DAE applications via the IP channel, as defined above. In environments where the broadcast channel is based on DVB network technologies and uses DVB-SI as specified in [[!DVBSI]], the OITF SHALL also support the application signaling and in-band delivery of DAE applications via the broadcast channel.

MP4 File Format

The carriage of A/V content and related information (e.g. subtitles) in file-based formats (systems layer format: MP4) SHALL use the MP4 File Format [[!MP4FF]] and ISO Base Media File Format [[!ISOFF]] standards with the constraints defined in section 9.4.4.3 of [[!DLNAMEDIA]], except for 9.4.4.3.3 and 9.4.4.3.10. This is the preferred format for MP4 based unprotected content.

For services that allow the real-time playback of downloaded content before the download has been completed (e.g. Progressive Download), the following additional constraints apply:

• The moof box SHALL be used according to section 9.4.3.3.8 of [[!DLNAMEDIA]].
• The size of the moov box SHALL be equal to or less than 2Mbytes.
• Use of the pdin box, defined in 8.43 of [[!ISOFF]], is RECOMMENDED.

A service MAY apply the additional constraint on moov box size according to section 9.4.4.3.11 of [[!DLNAMEDIA]], in order to provide content compliant to the DLNA specification.

In addition, carriage of H.264/AVC content in the MP4 systems layer SHALL be conformant to the AVC File Format standard [[!AVCFF]].

In addition, carriage of MPEG-4 AAC/HE-AAC content in the MP4 systems layer SHALL be conformant to the MP4 File Format standard [[!MP4FF]].

The storage of AC-3 and Enhanced AC-3 content in the MP4 file format shall be conformant to Annex F of [[!AC3]].

MP4 files MAY contain media zone information (zone map), possibly including navigation constraints, using the signalling mechanisms specified in [[!MRL-DMZ]]. Rules about the handling of Marlin media zone information by the OITF, for both unprotected and protected content, are contained in section 6 of [[.OIPF_CSP2]]. Note: this means an MP4 file may contain one or more mDMZ boxes containing zone parameters and zone properties (i.e., navigation constraints) according to [[!MRL-DMZ]] section 7.1,

The methods to protect (encrypt) MP4-based file formats are specified in [[.OIPF_CSP2]]. Four protection methods are specified and they are allocated the protection format labels as follows:

• OMA PDCF [[!OMARLIN]] is referred to as PDCF,
• OMA DCF [[!OMARLIN]] is referred to as DCF,
• Marlin IP MP [[!MRL-FF]] format is referred to as MIPMP.
• Common encryption in ISO base media file format files [[!CENC]] is referred to as CENC.

MP4 files containing 3D content SHALL comply with section 8.15 of [[!ISOFF]], i.e. the 3D video sample SHALL be signalled as restricted video ('resv') with stereoscopic video scheme type ('stvi').

Service Usage

Multicast IPTV services (Scheduled Content) SHALL use either the TS or the TTS systems layer format.

Unicast streamed IPTV services (Scheduled Content, CoD) using the Direct UDP or RTP/UDP transport protocols SHALL use either the TS or the TTS systems layer format.

Unicast streamed IPTV services (Scheduled Content, CoD) using the HTTP transport protocol (including adaptive streaming) SHALL use either the TS, the TTS, or the MP4 systems layer format.

Download IPTV services (CoD) SHALL use either the TS, the TTS, or the MP4 systems layer format.

Voice and video telephony services using the RTP/UDP transport protocol do not require any specific systems layer format.

Mobile A/V services do not require any specific systems layer format.

The systems layer formats used for content services are summarised in the following table.

Formats

Five profiles of video content are defined and described in the following sub-sections:

• High Definition (HD),
• Standard Definition (SD),
• 3D,
• Video Telephony,
• Sub-Picture.

Additionally, Video formats for Mobile A/V Services are defined.

Service Usage

The video formats specified in the Standard Definition Profile and in the High Definition Profile are applicable to A/V content provided within any of the Release 2 IPTV services. The video formats for Mobile A/V Services are applicable to any of the Release 2 IPTV services. The video formats specified in the Video Telephony Profile are applicable to content provided within Video Telephony services. The video formats specified in the Sub Picture Profile are applicable for use with Picture-in-Picture function.

Formats

For an IPTV service delivered using the TS or TTS system formats, any of the following subtitle formats SHALL be used:

• Based on DVB subtitles [[!DVBSUBT]] using format label DVB-SUBT. This format includes support for subtitles in 3D video content.
• Based on EBU Teletext [[!DVBTTXT]] using format label EBU-SUBT.
• Based on CEA-708-C [[!CEACC]] using format label CEA-SUBT.

If other subtitle formats are used, e.g. for market specific or regulatory reasons, their usage is outside the scope of the present specification.

For Mobile A/V Services, the Timed Text [[!3GPPTS26245]] format SHALL be used. This format corresponds to video format label 3GPP-TT.

Service Usage

Subtitle streams within an IPTV service MAY be used for the provision of:

• Subtitles for foreign-language content,
• Closed captions for enhanced accessibility,
• Any other purpose where such streams form part of a service offering.

Formats

For an IPTV scheduled content service delivered using the TS or TTS system formats, the Teletext information SHALL be based on EBU Teletext [[!DVBTTXT]]. This format corresponds to the format label EBU-TTXT.

Service Usage

The Scheduled Content service MAY include teletext information.

Teletext information SHALL NOT be provided with content delivered by the Content on Demand services.

Formats

Platform Usage

Formats

Still pictures and graphics content are used within both the Declarative (DAE) and the Procedural Application Environments (PAE).

The usage of still pictures and graphics formats within declarative applications is specified in [[.OIPF_DAE2]]. The formats adopted in the DAE are defined in [[!CEA-2014-A]].

The usage of still pictures and graphics formats within procedural applications is specified in [[.OIPF_PAE2]]. The formats adopted in the PAE are defined in [[!GEM]].

The present volume just notes the labels applied to the used formats — JPEG [[!JFIF]], GIF [[!GIF]] and PNG [[!PNG]].