Tech-invite   3GPPspecs   Glossaries   IETFRFCs   Groups   SIP   ABNFs   Ti+   Search in Tech-invite

Top   in Index   Prev   Next

TR 26.843 (SA4)
Study on non Bit-exact Conformance Criteria and Tools
for Floating-Point EVS Codec

3GPP‑Page   full‑ToC    
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V16.0.0 (Wzip)  2018/09  49 p.

Rapporteur:  Mr. Plante, Fabrice
See also:

The EVS coder (TS 26.441) provides enhanced quality for speech and audio communications relative to AMR-WB and 3GPP has standardized both a fixed-point version (TS 26.442) and a floating-point version (TS 26.443). Currently in TS 26.444 (Codec for Enhanced Voice Services (EVS); Test sequences) the conformance of the EVS coder implementation is achieved by checking the bit-exactness of output test vectors with the reference test vectors for both encoder and decoder, for both the fixed-point and floating-point implementations.
The bit-exact criteria defined in TS 26.444 are of very limited use for the floating-point implementation in TS 26.443 as the output values will be similar but not bit-exact for different compilers, compile options, OS and platform used and therefore failing the bit-exactness test.
This technical report aims at documenting possible methods for non bit-exact conformance process for floating-point implementation that would allow conforming implementations to be used in all scenarios acceptable for bit-exact implementations of fixed-point version (TS 26.442) and floating-point version (TS 26.443).
The scope of the study item is to assess the use of various floating-point processing cores and compilers with various levels of optimization, and establish potential conformance criteria and a tool(s) that could be used for confirming conformance under those variations. The scope of the intended conformance tool(s) is to assess the conformance of implementations to the developed criteria. The conformance criteria to be developed will aim at accepting proper floating-point processing compute core and compiler optimizations, while rejecting all bad implementations, for example coming from functional or code changes, too aggressive optimization of the compiler or insufficient arithmetic precision.

full Table of Contents for  TR 26.843  Word version:   16.0.0


Here   Top


1  ScopeWord-p. 6
2  References
3  Definitions and abbreviationsWord-p. 7
4  Overview
5  Methods DescriptionWord-p. 8
6  ResultsWord-p. 19
7  Conformance ProcessWord-p. 42
8  InteroperabilityWord-p. 43
9  Coverage AssessmentWord-p. 46
10  Conclusions
A  POLQA Considerations for Conformance TestWord-p. 47
B  Change historyWord-p. 49

Up   Top