8 RTP Payload Format Conformance for EVS
26.1303GPPRelease 18Speech/Audio Codec RTP Payload Format Conformance for UE TestingTS
8.1 Applicability
[The requirements and test methods in this clause shall apply when UE is used to provide narrowband, wideband, super-wideband or fullband telephony, either as a stand-alone service, or as part of a multimedia service.]
8.2 [Test cases in sending]
8.2.1 [SDP answer conformance]
8.2.2.1 [Requirement]
[To be defined
The DUT shall accept the first dynamic EVS payload type offer without modifying it (same paramaters, no value modification).
Examples of offers / expected answers (to be completed with table?):
– offer : br=9.6-24.4;mode-set=0,1,2,8;mode-change-capability=2; evs-mode-switch=1, answer]
8.2.2.2 [Test method]
[Editor’s note: test setup to be fully defined first, the principle of the test method could be to setup MT call(s) with EVS at predefined configurations and analyse captured PCAP files at the IP level. ]
8.2.2 [Q-bit verification]
8.2.2.1 [Requirement]
[The Q-bit shall always bit set to 1 in the RTP payload when EVS-IO and header-full modes are negotiated.
NOTE: The Q-bit is the frame quality indicator [RFC 4867]. If set to 0, it indicates that the corresponding frame is severely damaged, and the receiver should set the RX_TYPE to either SPEECH_BAD or SID_BAD depending on the frame type (FT).]
8.2.2.2 [Test method]
[Editor’s note: test setup to be fully defined first, the principle of the test method could be to setup MT call(s) with AMR-WB at predefined modes and analyse captured PCAP files at the IP level. ]
8.2.3 [Handling of CMR]
8.2.3.1 [Requirement]
[The EVS Primary bit rate (mode) in sending shall be according to the EVS Primary CMR inserted in receiving after [X] ms.
The EVS-IO bit rate (mode) in sending shall be according to the EVS-IO CMR inserted in receiving after [X] ms when the call is initiated with AMR-WB IO.
Editor’s note: the list of tests can be extended and conformance tests may be formulated in a table ]
8.2.3.2 [Test method]
[Editor’s note: test setup to be fully defined first, the principle of the test method could be to setup MT call(s) with EVS at predefined modes and analyse captured PCAP files at the IP level. ]
8.2.4 [RTCP bandwidth verification]
[Editor’s note: one option could be to refer to TS 26.139 and require that UE comply with this specification. ]
8.2.4.1 [Requirement]
[RTCP conformance is defined in 3GPP TS 26.139.
Requirement to be defined]
8.2.4.2 [Test method]
[Editor’s note: test setup to be fully defined first, the principle of the test method could be to setup MT call(s) with AMR-WB at predefined modes and analyse captured PCAP files at the IP level. ]
8.3 [Test cases in receiving]
tbd
Annex <A> (normative):
[RTP payload tools]
Editor’s note: Additional tools such as direct decoding of RTP payload or RTP payload dissectors may also be specified (see eUET WID).
Annex <B> (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2022-08 |
SA4#120-e |
S4-221028 |
Initial version |
0.0.1 |
|||
|
2022-08 |
SA4#120-e |
S4-221189 |
Inclusion of pCR in S4-221029 in brackets |
0.1.0 |
|||