31.3.1m 33087
Agreed. A study will be issued. Still unclear if this will be part of a corrigendum or of AMD1. If more corrections are needed, we will do a corrigendum, otherwise we will go for AMD1.
31.3.2m33126
Agreed to move forward with the packet-based solution. Offline discussion to harmonize the signaling and support for SSBG mode 2.
Harmonization is done and a contribution with the merged will be proposed to be integrated in AMD2.
31.3.3m33127
Agreed. NB support is required to be included in the AMD1.
31.3.4m33129
Agreed. NB support is required to be included in the AMD1.
31.3.5m33237
Agreed operation points. subADC signaling needs to be harmonized with
31.3.6m33238
This will need to be first included as part of the QoE metrics documents discussed in FF. Once done, some guidelines can be added to the IG document to describe how the values are set.
31.3.7m33295
See document for comments. The agreed issues will be provided in the issues for corrigendum. More aspects need to be considered for assigning different TOIs to chunks of a transport object. For instance updates to the template mechanism need to be made.
31.3.8m33296
Noted. MMT has made a decision to only specify a packet-based FEC framework. This work might be considered as part of an LCT-based profile.
31.3.9m33317
We first need to understand the reasons why SI table was removed from the specification.
31.3.10m33318
Agreed. NB support is required to be included in AMD1.
31.3.11m33319
Agree to add the multiple packet_id. We need to provide a way to carry the ADC in XML format inside the ADC_message.
The MPU referencing will be discussed within the sub-ADC discussion.
NB support is required to be included in AMD1.
We need to check the usage of flow_lable and whether it fits into the ADC. Then we need to harmonize the binary, xml description and xml schema definitions for ADC.
31.3.12m33458
Agreed to add the binary changes. XML signaling of ADC needs to be harmonized with 237.
NB support is required to be included in AMD1.
31.3.13m33468
Clarify that ADC provides bigger picture and can be used by MANE to allocate resources for a longer period of time. Packet header QoS information applies to that particular packet or may be determined out of the ADC information (e.g. after resource allocation, flow label can be put to the packet header).
Agreed after these changes.
31.4Action Points
ISO/IEC 23008-1/DAM 1
(SC 29 N 13784)
|
Part 1: MPEG media transport (MMT), AMENDMENT 1
|
DAM
(2014-
04-13)
|
ISO/IEC 23008-1/DAM 2
(SC 29 N 13743)
|
Part 1: MPEG media transport (MMT), AMENDMENT 2: Header Compression and Cross Layer Interface
|
DAM
(2014-
07-14)
|
32.MMT FEC (23008-10) 32.1Topics 32.1.1ISO/IEC 23008-10 1st edition
MMT defines several tools for error correction Such as Forward Error Correction (FEC) and retransmissions. A set of FEC codes is defined in 23008-10 that is shares a Common FEC framework. Additional codes may also be added . Some of the Currently defined FEC codes have enhanced support for Layered media
32.2Contributions
number
|
Session
|
Title
|
Source
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Dostları ilə paylaş: |
