The baseline MMBP Player profile is aligned with TS 26.140. The container format is based on RFC 2045 as the format for the MMBPs. Offering of alternative content is the container is permitted. In addition, the profile permits to encapsulate encapsulation of real-time video into the 3GP file format using the baseline profile. The container does not support external bodies, i.e. the MMBP is expected to be delivered as a single message. For details on the container format requirements, refer to clause 6.2.2. The media types address basic text, audio/speech, images, video, text/subtitle, 3D scenes including AR as well as simple HTML-5 presentations. Content conforming to the baseline MMBP player may include media types that are not explicitly supported by the media capabilities as defined in clause 6.2.3. Receivers shall ignore non-recognized media types. However, based on the container requirements, ignoring media types may results in specific processing requirements, for example pick an alternative, or ignore the entire MMBP. Content generated to be compatible for playback on players for this profile as well as players expose their capabilities should use the URN identifier "urn:3GPP:26143:19:baseline-mmbp-player".

The following capabilities for the container format as defined in clause 5.2.1 shall be supported:

• 26143_CONTAINER_RFC2046_SINGLE
• 26143_CONTAINER_RFC2046_MIXED
• 26143_CONTAINER_RFC2046_ALTERNATIVE
• 26143_CONTAINER_RFC2387_RELATED
• 26143_CONTAINER_MP4_3GP9
• 26143_CONTAINER_MP4_MP42

The following capabilities for the container format as defined in clause 5.2 should be supported:

• 26143_CONTAINER_RFC2046_PARALLEL

In addition, multipart/parallel shall not be present in an MMBP on the same level if a 3GP file Rel-9 basic profile as defined in TS 26.244 identified by the brand '3gp9'is present and contains more than on track.

The capability 26143_TEXT_PLAIN as defined in clause 5.3 shall be supported. If still images are supported,

• the 26143_IMG_JPEG capability as defined in clause 5.4.1 shall be supported,
• the 26143_IMG_HEIC capability as defined in clause 5.4.1 should be supported.

If bitmap graphics are supported,

• the 26143_IMG_GIF capability as defined in clause 5.4.1 should be supported.
• the 26143_IMG_PNG capability as defined in clause 5.4.1 should be supported.

If the reception of audio or speech is supported, then the following applies:

• the 26143_AUDIO_IVAS capability as defined in clause 5.5.1 should be supported.
• the 26143_AUDIO_EVS capability as defined in clause 5.5.1 shall be supported.
• the 26143_AUDIO_AMR-WB capability as defined in clause 5.5.1 shall be supported.
• the 26143_AUDIO_XHE-AAC capability as defined in clause 5.5.1 should be supported.
• the 26143_AUDIO_AMR capability as defined in clause 5.5.1 shall be supported.
• the 26143_AUDIO_EAAC+ capability as defined in clause 5.5.1 shall be supported.

If the reception of video is supported, then the following applies:

• the 26143_VIDEO_AVC-HD capability as defined in clause 5.6.1 shall be supported.
• the 26143_VIDEO_HEVC-HD capability as defined in clause 5.6.1 should be supported.

If the reception of HD-HDR video is supported, then the following applies:

• the 26143_VIDEO_AVC-FullHD capability as defined in clause 5.6.1 shall be supported.
• the 26143_VIDEO_HEVC-FullHD capability as defined in clause 5.6.1 shall be supported.
• the 26143_VIDEO_HEVC-UHD capability as defined in clause 5.6.1 should be supported.

If timed text is supported,

• the 26143_TT_3GPP capability as defined in clause 5.7.1 shall be supported.
• the 26143_TT_IMSC11 capability as defined in clause 5.7.1 should be supported.

If a processor for media type 'model' as defined in RFC 2077 is supported (i.e. a processor for 3D scenes and objects), then a processor for the media subtype 'model/gltf' should be supported. If a processor for the media subtype 'model/gltf' is supported,

• the 26143_SCENE_GLTF20 capability and the 26143_SCENE_GLTF20_GLB capability as defined in clause 5.8 shall be supported assuming either a single body part or a multipart/related body part as defined in clause 5.2.
• and if the device is a device type as defined in clause 10 of TS 26.119, the 26143_SCENE_GLTF20_AR and the 26143_SCENE_GLTF20_GLB_AR capability as defined in clause 5.8 shall be supported assuming either a single body part or a multipart/related body part as defined in clause 5.2.

If a processor for the media type text/html is supported, the 26143_PRESENTATION_HTML5 capability as defined in clause 5.9 should be supported assuming either a single body part or a multipart/related body part as defined in clause 5.2. The media formats shall be restricted to the capabilities defined in this clause.

The baseline MMBP Generator profile is aligned with TS 26.140. It primarily addresses the ability for users to generate content, for example on a mobile device. The container format is based on RFC 2045 as the format for the MMBPs. Offering of alternative content is the container is permitted. In addition, the profile permits to encapsulate encapsulation of real-time video into the 3GP file format using the baseline profile. The container does not support external bodies, i.e. the MMBP is expected to be delivered as a single message. For details on the container format requirements, refer to clause 6.3.2. The media types supported by this profile are basic text, audio/speech, images, video, and text. Content conforming to the baseline MMBP generator profile may include media types that are not explicitly supported by the media capabilities as defined in clause 6.3.3. Receivers are expected to ignore non-recognized media types. However, based on the container requirements, ignoring media types may results in specific processing requirements, for example pick an alternative, or ignore the entire MMBP. Additional packaging requirements and recommendations are provided in clause 6.3.4. Content generated to be compatible for this profile as well as generators expose their capabilities should use the URN identifier "urn:3GPP:26143:19:baseline-mmbp-generator".

The following capabilities for the container format as defined in clause 5.2.2 shall be supported:

• 26143_CONTAINER_RFC2046_SINGLE_GEN
• 26143_CONTAINER_RFC2046_MIXED_GEN

In addition, at least one of the the following two capabilities for the container format as defined in clause 5.2.2 shall be supported:

• 26143_CONTAINER_MP4_3GP9_GEN
• 26143_CONTAINER_MP4_MP42_GEN

The following capabilities for the container format as defined in clause 5.2 should be supported:

• 26143_CONTAINER_RFC2046_PARALLEL_GEN
• 26143_CONTAINER_RFC2046_ALTERNATIVE_GEN

If the transmission of images is supported, then the following applies:

• the 26143_IMAGE_ENC_JPEG capability as defined in clause 5.4.2 shall be supported.
• the 26143_IMAGE_ENC_HEIC capability as defined in clause 5.4.2 should be supported.

If the transmission of speech is supported, then the following applies:

• the 26143_AUDIO_ENC_IVAS capability as defined in clause 5.5.2 should be supported.
• the 26143_AUDIO_ENC_EVS capability as defined in clause 5.5.2 shall be supported.
• the 26143_AUDIO_ENC_AMR-WB capability as defined in clause 5.5.2 should be supported.
• the 26143_AUDIO_ENC_AMR capability as defined in clause 5.5.2 may be supported.

If the transmission of audio is supported, then the following applies:

• the 26143_AUDIO_ENC_IVAS capability as defined in clause 5.5.2 should be supported.
• the 26143_AUDIO_ENC_EAAC+ capability as defined in clause 5.5.2 shall be supported.
• the 26143_AUDIO_ENC_XHE-AAC capability as defined in clause 5.5.2 should be supported.

If the transmission of video is supported, then the following applies:

• the 26143_VIDEO_ENC_HEVC-FullHD capability as defined in clause 5.6.2 shall be supported.

If the transmission of timed text is supported, then the following applies:

• the 26143_TT_ENC_3GPP capability as defined in clause 5.7.2 shall be supported.

For content generated by this baseline generator, multipart/parallel shall not be present in an MMBP on the same level if a 3GP file Rel-9 basic profile as defined in TS 26.244 identified by the brand '3gp9'is present and contains more than on track. When generating a speech message, the MMBP Generator shall at least include an EVS Content together with potential alternatives. When generating an Audio message, the MMBP Generator shall at least include an eAAC+ stereo Content together with potential alternatives.