hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.3.5 Body element | This parameter provides the body of the message. When the receiver population targeted by the service provider has a range of display screen sizes, it is recommended to use filters to provide different text lengths according to the screen capability. ETSI ETSI TS 103 689 V1.1.1 (2019-11) 13 EXAMPLE: A company has 3 typ... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.4 Picture element | The inclusion of a picture element is optional. The image formats are identical to SlideShow, see ETSI TS 101 499 [i.1]. The aspect ratio of the image is 4:3. Its attributes are detailed below: Attribute Description Type Status url MOT Content Name xs:string Required mimeValue PNG or JPG (see IETF RFC 2045 [6]) MIME ty... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.5 Validity element | The validity element describes the time period in which the message may be displayed, expressed as the calendar date based on the ISO 8601 [4] extended format: YYYY-MM-DD where "YYYY" is the year, "MM" the month and "DD" the day. EXAMPLE: 2019-05-27. Its attributes are detailed below: Attribute Description Type Status ... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.6 Geolocation | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.6.1 Introduction | 5. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.1 Introduction | The geolocation element allows messages to be localized and only displayed if the receiver is located within the specified localization. The geolocation element shall contain one or more of the following child elements: • country • poi ETSI ETSI TS 103 689 V1.1.1 (2019-11) 14 • polygon Its attributes are detailed below... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.6.2 Country element | The country element specifies the country using the ISO 3166-1 alpha-2 country codes [7]. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.6.3 Point of Interest (poi) element | The localization zone is determined from the point specified and the distance set in the receiver configuration (either by default or by the user). The poi element shall contain one point element and may contain one or more address, opening and uri elements: Element Description Type Status point Based on the georss:poi... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.6.4 Polygon element | The polygon element, based on the georss:polygon [8] type, specifies a space-separated series of points by latitude and longitude in the WGS84 coordinate reference system, forming an enclosed area, in the format: <[<latitude> <longitude>]...> ETSI ETSI TS 103 689 V1.1.1 (2019-11) 15 The first pair and last pair shall b... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.7 Filters element | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.7.1 Introduction | 5. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 7.1 Introduction | Language, geolocation and validity filters are integral to the operation of the FIS, but company defined filters are also provided to give virtually unlimited scope for directing messages to specific groups or even individual receivers. The filters are defined using a filter definition file (see clause 7) and evaluated... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.7.2 filterEnum element | A filter of type filterEnum can have either one values child element or one ignores child element. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter which has been defined in the filter definition file xs:token Required A values child element conatins one or more value c... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.7.3 filterInt element | A filter of type filterInt can have either one values child element or one ignores child element or one comparisons child element. Its attributes are detailed below: ETSI ETSI TS 103 689 V1.1.1 (2019-11) 16 Attribute Description Type Status filterName Name of the filter which has been defined in the filter definition f... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.7.4 filterFloat element | A filter of type filterFloat can have either one values child element or one ignores child element or one comparisons child element. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter which has been defined in the filter definition file xs:token Required A values child el... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 5.7.5 filterDate element | A filter of type filterDate can have either one values child element or one ignores child element or one comparisons child element. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter which has been defined in the filter definition file xs:token Required A values child ele... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6 Transport mechanism | 6.1 Introduction The FIS is transported using the MOT protocol (see ETSI EN 301 234 [2]) in a packet mode sub-channel with FEC applied. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.2 MOT Carousel | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.2.1 Basics | MOT in Directory Mode shall be used. The files may be compressed, if so the CompressionType parameter shall be used. The files may be encrypted, if so the CAInfo parameter shall be used. All MOT parameters shall be used as specified in ETSI EN 301 234 [2]. ETSI ETSI TS 103 689 V1.1.1 (2019-11) 18 |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.2.2 ContentTypes and ContentSubTypes | Only the ContentType/ContentSubType pairs (see ETSI TS 101 756 [3]) shown in table 3 are permitted: Table 3: Permitted content type and content subtypes Content type Content subtype text HTML image JFIF (JPEG) PNG |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.2.3 ContentName | The character set for the ContentName shall be ISO Latin Alphabet No 1, see ETSI TS 101 756 [3]. Permitted characters are further restricted to a subset of this character set as follows: the lowercase Latin letters, the digits, the hyphen, the forward slash and the underscore ("a".."z", "0".."9", "-", "/", "_"). The fi... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.2.4 Directory extension | The company identifier (key) shall be encoded as a 32-bit unsigned integer in the MOT directory with the extension parameter Id = 10 0000. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.3 Signalling | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.3.1 Application type, FIG 0/13 | The use of the FIS application within a DAB data channel shall be indicated by the use of FIG 0/13 with a UserApplicationType value of FIS as defined in ETSI TS 101 756 [3]. No user application specific data is defined. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 6.3.2 Date and time, FIG 0/9 and FIG 0/10 | The provision of a correctly broadcast reference time using FIG 0/10 and local time offset using FIG 0/9 is a mandatory requirement of this User Application. For further details on these parameters, see ETSI EN 300 401 [1]. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 7 Filter definition file | 7.1 Introduction To provide a greater level of message selection in the receiver, company specific filters can be defined. These filters are defined using a filter definition file and this file is used for the creation of the broadcast FIS (see clause 5) and the creation of the receiver configuration file (see clause 8... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 7.2 FisFilter element | This is the root element of the filter definition document and can contain one or more of the following elements: • filterEnumDef • filterIntDef • filterFloatDef • filterDateDef Its attributes are detailed below: Attribute Description Type Status key Identifier for entity (company) providing the information xs:unsigned... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 7.3 filterEnumDef element | A filter definition of type filterEnumDef contains the list of enumerated values, minimum 2, for the filter using the enumDef element. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter xs:token Required Each enumDef element provides one enumerated value of type xs:token.... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 7.4 filterIntDef, filterFloatDef, filterDateDef elements | A filter definition of type filterIntDef, filterFloatDef or filerDateDef has no child elements. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter xs:token Required For each filter type, additional company defined attributes may also be added without disturbing the generi... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8 Receiver configuration file | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.1 Introduction | Different receivers have different capabilities and are fitted into different environments, for example, different makes and models of cars. To provide the specific data needed to evaluate the company defined filters, a receiver configuration file is used. ETSI ETSI TS 103 689 V1.1.1 (2019-11) 20 Each defined filter fr... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.2 FisConf element | This is the root element of the receiver configuration document and can contain one or more of the following elements: • filterEnumConf • filterIntConf • filterFloatConf • filterDateConf Its attributes are detailed below: Attribute Description Type Status key Identifier for entity (company) providing the information xs... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.3 filterEnumConf element | A filter definition of type filterEnumConf contains the enumerated value for this instance of the filter. The enumerated value is of type xs:token. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter xs:token Required expiration Validity of the configuration value xs:date ... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.4 filterIntConf element | A filter definition of type filterIntConf contains the enumerated value for this instance of the filter. The enumerated value is of type xs:Int. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter xs:token Required expiration Validity of the configuration value xs:date Opt... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.5 filterFloatConf element | A filter definition of type filterFloatConf contains the enumerated value for this instance of the filter. The enumerated value is of type xs:float. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter xs:token Required expiration Validity of the configuration value xs:date... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.6 filterDateConf element | A filter definition of type filterDateConf contains the enumerated value for this instance of the filter. The enumerated value is of type xs:date. Its attributes are detailed below: Attribute Description Type Status filterName Name of the filter xs:token Required expiration Validity of the configuration value xs:date O... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 8.7 Updating the receiver configuration file | The receiver configuration file can be updated to allow receiver makers or third-party companies to add or remove filters. The update protocol implementation is chosen by the receiver maker. In the case of a third-party company, formal agreement should be found between the third-party and the receiver maker. |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9 Receiver behaviour | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.1 Introduction | A receiver equipped with the FIS application shall only decode the FIS corresponding to its authorized company identifier (key). The FIS is identified in several ways: from the MOT directory extension parameter 10 0000; from the ContentName of the files in the MOT Carousel; from the key attribute of the fis element. By... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.2 Minumum functional requirements | The receiver shall be able to store one or more receiver configuration files. Without a configuration file, the receiver will not be able to display any FIS. The FIS decoder shall only use files with a company identifier (key) corresponding to the key of the receiver configuration file(s). ETSI ETSI TS 103 689 V1.1.1 (... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.3 User controls | It is recommended that the Carsion application sets its display language from the receiver HMI. The user could also be provided with the option to display messages in the default language. It is recommended to permit the user to activate or deactivate messages with priority from 3 (normal) to 5 (low). The user could be... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4 Message display rules | |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4.1 Introduction | The minimum content of a message is a validity element and a text element. Typically, a message will contain multiple filters elements and multiple text elements in different languages. They may also contain a picture element and multiple geolocation elements. Each element of each message (except the picture element, i... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4.2 Validity element evaluation | Messages shall be valid to be displayed. To be valid, the current date shall be within the period of validity which is defined as starting on the begin date and ending on the end date; both the begin date and the end date are inclusive. The current date shall be obtained from the MJD in the FIG 0/10, taking into accoun... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4.3 Filters element evaluation | If filters elements are present in the message element, then they shall be evaluated. If any of the filters element evaluations produces a true result, then the message is a valid candidate for display. When multiple filters are present within the filters element, the result of each filter shall be evaluated and combin... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4.4 Geolocation evaluation | If no geolocation elements are present in the message element, or if no location data is available, then the result of the geolocation evaluation is true. If geolocation elements are present in the message element, and the receiver has access to location data (either static information entered by the user, or dynamic i... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4.5 Text element evaluation | A message may contain several text elements in different langauges. The text element with the language attribute that matches the display language shall be marked as a candidate for display. If no text element with the language attribute that matches the display language exists and the priority of the message is critic... |
75ab8d543d8a899a67bd2e8f4f627f5c | 103 689 | 9.4.6 Message display | If the validity evaluation is true AND the filters evaluation is true AND the geolocation evaluation is true then the text element marked as a candidate for display shall be presented. If a picture element exists for this message and the receiver is able to display it, then the picture element shall be presented. If a ... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 1 Scope | The present document defines a process of receiving, transforming and outputting material that can be assured digitally. The process is called the "Digital Evidence Bag" (DEB). The present document identifies the ways that a DEB can be used to provide assurance of material used in legal proceedings. Specifically, the a... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 2 References | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 3 Definition of terms, symbols and abbreviations | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 3.1 Terms | For the purposes of the present document, the following terms apply: case-specific input material: input material for a Digital Evidence Bag that is specific to the particular investigation or case ETSI ETSI TS 103 643 V1.2.1 (2022-01) 7 Digital Evidence Bag (DEB): process of storing digital evidence which can be assur... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 3.2 Symbols | Void. |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADT Assured Digital Transformation B-DEB Basic Digital Evidence Bag DEB Digital Evidence Bag DEB+H Digital Evidence Bag with Hashing DEB+HIA Digital Evidence Bag with Hashing and Input Assurance DEB+IA Digital Evidence Bag with Input Assurance... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 4 Basic principles | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 4.1 Summary | The present document gives a definition for a "Digital Evidence Bag", which is a process for storing and transforming digital material. Annex A provides an informative description of when this process is intended to be used. The present document defines and specifies requirements for the following types of Digital Evid... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5 Definition of a Basic Digital Evidence Bag | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.1 Reference model | The model for a Basic Digital Evidence Bag is as shown in Figure 1. ETSI ETSI TS 103 643 V1.2.1 (2022-01) 8 Figure 1: Model for Basic Digital Evidence Bag |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2 Inputs of digital data | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2.1 Nature of inputs | There are two types of input material: case-specific input material and reference input material (as defined in clause 3). EXAMPLE: Examples of reference input material are maps or publicly available reference data. Basic DEBs shall follow the specifications for input material as listed in clauses 5.2.2 to 5.2.4. |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2.2 A unique identifier for each input | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2.2.1 Identifiers for case-specific input material | For a Basic DEB, each input of case-specific input material (see clause 3) shall have a unique identifier attached to it. One of the two following approaches shall be used: 1) The identifier shall consist of: a) an identifier supplied by the originating organization; and b) a unique identifier for the originating organ... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2.2.2 Identifiers for reference input material | For a Basic DEB, the reference input material (see clause 3) should also have an identifier to make it clear where it came from, and should also identify the time it was collected if that is significantly different from the time the material is being submitted to the DEB. |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2.3 Time and location information for input material | The time information in a Basic DEB shall consist of the following: • All time information as supplied by the originating organization. The input material should contain time and date information, including indication of the time zone, for the point at which the data was generated or created (or for the period over whi... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.2.4 Format of input material | The format for each input file to a Basic DEB should be known or clear (i.e. known via a communication in advance of sending the data, or clear from the evidence file itself). Each input file should be checked syntactically for data formats where there are suitable automated checks. EXAMPLE: If data is submitted in XML... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.3.1 Definition of a Purely Digital Transformation | A Purely Digital Transformation (PDT) is one in which a repeatable, deterministic, pre-specified, fail-safe, well-defined digital function is performed on entirely digital data. Specifically: • It is repeatable in that if the step is performed again by a different computer or operator, in a different environment, in a ... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.3.2 Use of PDT in a Digital Evidence Bag | Within the Digital Evidence Bag, one or more PDTs (as defined in clause 5.3.1) may be applied. For each transformation, the DEB shall check: • That the formatting and definition of input files is clear. • That any standards referred to have a correct version number and are designed for the purpose in question. • That t... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.3.3 Definition of an Assured Digital Transformation | An Assured Digital Transformation (ADT) is one in which a documented, fail-safe task is performed on entirely digital data by a suitably qualified person. Specifically: • The task is documented, in that there is a document listing how the task is to be performed, which was available to the person performing the task an... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.3.4 Use of ADT in a Digital Evidence Bag | Within the Digital Evidence Bag, one or more ADTs (as defined in clause 5.3.3) may be applied. For each transformation, the DEB shall: • Check formatting of input files is clear (in line with the documentation). • Check that the input(s) each has an identifier. The DEB shall record: • The time and date that the transfo... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 5.4 Details for creating the output | The Basic DEB output file shall contain the following information: • List of all input files, including identifiers (as defined in clause 5.2.2) and the DEB entry time (clause 5.2.3). • For each transformation that was applied, a list of the details for that transformation from clause 5.3.2 (for PDTs) or 5.3.4 (for ADT... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6 Definition of other Digital Evidence Bags | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6.1 Introduction | Clause 6 specifies the following types of Digital Evidence Bag: • DEB+H (with Hashing). • DEB+IA (with Input Assurance). • DEB+HIA (with Hashing and Input Assurance). NOTE: A Digital Evidence Bag with Digital Signature would also meet many of the same goals as the Digital Evidence Bag with Hashing and Input Assurance a... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6.2 Definition of a DEB+H | |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6.2.1 General | A Digital Evidence Bag with Hashing (DEB+H) shall meet the specification of a Basic DEB (clause 5). In addition, it shall use hashing as specified in clause 6.2.2. NOTE: A Digital Evidence Bag with Hashing would typically be used in situations where assurance was required that material had not been changed from the poi... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6.2.2 Use of hashing in a DEB+H | A DEB+H shall create a single input file with all input material. The input material shall include all identifiers as defined in clause 5.2.2 and the DEB entry time as defined in clause 5.2.3. EXAMPLE: A number of pieces of input material could be turned into a single file through use of zip. ETSI ETSI TS 103 643 V1.2.... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6.3 Definition of a DEB+IA | A DEB+IA shall follow the specification in clause 5 for the definition of a Basic DEB. Additionally, the DEB+IA shall identify the delivery protocol or technique which was used to input the material to the DEB. The DEB+IA shall log any credentials that were provided or were necessary in order to use the specified deliv... |
fb91f821b21c13b4650e86b759564d22 | 103 643 | 6.4 Definition of a DEB+HIA | A DEB+HIA shall follow the specifications in both clauses 6.2 and 6.3 in addition to the specification of a Basic DEB in clause 5. Clause A.3 explains when it can be appropriate to each of the different types of DEB. ETSI ETSI TS 103 643 V1.2.1 (2022-01) 13 Annex A (informative): Context A.1 Purpose of the present docu... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 1 Scope | The present document specifies the subjective and objective methodologies developed in cooperation between TC STQ and TC DECT for the characterization of the Low Complexity Communication Codec Plus (LC3plus) speech codec. It describes experimental tests and conditions used for subjective and objective testing. Based on... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 2 References | |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 3 Definition of terms, symbols and abbreviations | |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 3.1 Terms | For the purposes of the present document, the following terms apply: EPFsize: size of each packet loss in milliseconds |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 3.2 Symbols | Void. |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACR Absolute Category Rating AMR Adaptive MultiRate speech codec AMR-NB Adaptive Multirate speech codec Narrow Band AMR-WB Adaptive Multirate speech codec Wide Band ASL Active Speech Level BER Bit Error Rate BT Better Than CBR Constant Bitrate... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 4 Introduction | The present document defines characterization methodologies as well as the performance requirements to be evaluated for the ETSI Low Complexity Communication Codec Plus (LC3plus) [5]. The performance of the codec was initially studied by the TC DECT group in ETSI TR 103 590 [i.1] which is considered as qualification of... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 5 Characterization methodologies | |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 5.1 Overview | The present clause describes the experiment design and the subjective and objective methodologies. The aim of the characterization test is to assess the clean channel performance, self-tandeming capabilities, cross-tandeming, as well as rate switching conditions and variation of the input speech level. The characteriza... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 5.2 Experiments | All test conditions shall be separated according to the category audio bandwidth and channel conditions. This results in six experiments, i.e. 3x audio bandwidth times 2x channel conditions. Additionally, one multi-bandwidth experiment shall be conducted in order to provide a quality overview. Such experiment is subdiv... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 5.3 Item processing | The test items shall be processed according to the EVS processing plan [i.3]. For transcoding, no frame synchronization between the codecs shall be applied. The frequency masks used by 3GPP EVS characterization tests shall be applied to the input signals. The items shall be processed and prepared for the experiments us... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 5.4 Subjective methodologies | All subjective experiments shall be conducted using the Recommendation ITU-T P.800 [1] procedure using speech material. Subjects shall be naïve listeners and native speakers. Experiments should be conducted in different languages and labs. Table 2 shows the Recommendation ITU-T P.800 [1] experiment configurations. ETSI... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 5.5 Objective methodologies | All experiments listed in Table 1 shall be assessed by the objective quality evaluation using the perceptual objective listening quality prediction tool standardized by ITU-T also known as Recommendation ITU-T P.863 [2]. Tests shall be run in the full band mode with full band reference files and appropriate degraded fi... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 6 Characterization test plan | |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 6.1 Testing Conventions | |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 6.1.1 Introduction | The following clauses specify performance requirements and conditions to be evaluated for the following use cases: • DECT with clean channel conditions. • DECT with error prone channel conditions. • VoIP without packet loss conditions. • VoIP including packet loss conditions. Besides performance requirements, performan... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 6.1.2 Software versions | The following software versions for the different codecs shall be used: • G.711 A-law: Recommendations ITU-T G.711 [12] and G.711 Appendix I (PLC) [10]. • IETF RFC 8251 [11] OPUS: V1.3.0 (latest), fix-point. NOTE: OPUS is a codec in accordance with IETF RFC 6716 [i.2] and IETF RFC 8251 [11]. • EVS: EVS Codec ETSI TS 12... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 6.1.3 Test condition numbering | The test conditions are numbered according to the scheme given in Table 3. Table 3: Test condition numbering NB WB SWB DECT with clean channel conditions 1xx 2xx 3xx DECT with error prone channel conditions 4xx 5xx 6xx VoIP without packet loss conditions 7xx 8xx 9xx VoIP including packet loss conditions 10xx 11xx 12xx ... |
e55ce9ff77129606caa5fa81ba099536 | 103 624 | 6.2.1 Overview | CuT in DECT shall provide the same or better voice quality than the VoIP network provides and guarantees higher efficiency than DECT audio codecs used today, meaning same quality at lower bit rates to allow better DECT slot exploitation in conjunction with channel coding to provide better protection for bit errors and ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.