hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
856850865c40cb04931b6c475756c133 | 103 744 | 7.5.1 ECDH description | One of the key-establishment schemes shall be Elliptic Curve Diffie-Hellman defined in clause 5.7.1.2 of NIST SP800-56Ar3 [1]. A shared secret k is computed between two entities over the same elliptic curve domain parameters. The key-establishment scheme, for a given set of elliptic curve domain parameters, consists of... |
856850865c40cb04931b6c475756c133 | 103 744 | 7.5.2 Elliptic curve domain parameters | The elliptic curve parameters used shall be one of the following: • NIST P-384/secp384r1 defined in clause G.1.3 of NIST SP 800-186 [6]. • NIST P-256/secp256r1 defined in clause G.1.2 of NIST SP 800-186 [6]. • brainpoolP384r1 defined in clause 3.6 of IETF RFC 5639 [7]. • brainpoolP256r1 defined in clause 3.4 of IETF RF... |
856850865c40cb04931b6c475756c133 | 103 744 | 7.6 Key Encapsulation Mechanisms (KEMs) | |
856850865c40cb04931b6c475756c133 | 103 744 | 7.6.1 KEM description | The present clause specifies the basic properties of a Key Encapsulation Mechanism (KEM) as a tuple of algorithms (KEMKeyGen, Encaps, Decaps) associated with a key space K: • KEMKeyGen( ), a probabilistic algorithm that returns a private and public key pair (sk, P), or ⊥ an error indicator. • Encaps(P), a probabilistic... |
856850865c40cb04931b6c475756c133 | 103 744 | 7.6.2 Post-quantum KEMs | The present clause specifies the basic properties of post-quantum KEMs as a tuple of algorithms. All post-quantum KEMs shall expose a tuple of algorithms matching the KEM properties defined in clause 7.6.1. The current list of approved post-quantum KEMs consists of the FIPS-approved ML-KEM [11]. |
856850865c40cb04931b6c475756c133 | 103 744 | 7.7 Primitive parameter sets | |
856850865c40cb04931b6c475756c133 | 103 744 | 7.7.1 Parameter set description | The present clause specifies a parameter set. Parameter sets consist of tuples of specific choices for a key derivation function, elliptic curve Diffie-Hellman and quantum-safe key encapsulation mechanism instances. Parameters sets of are denoted KDF_CURVE_KEM. Clause 7.7.2 restricts the parameter sets to enable greate... |
856850865c40cb04931b6c475756c133 | 103 744 | 7.7.2 Parameter sets | The present clause specifies sets of primitives. The parameter sets are defined by a triple, a key derivation mechanism, a first key establishment scheme, and a second key establishment scheme. An implementation shall use one of the following parameter sets. HKDFwSHA256_P256_ML-KEM-512, HKDFwSHA256_ X25519_ML-KEM-512, ... |
856850865c40cb04931b6c475756c133 | 103 744 | 8 Hybrid key establishment schemes | |
856850865c40cb04931b6c475756c133 | 103 744 | 8.1 General | |
856850865c40cb04931b6c475756c133 | 103 744 | 8.1.1 Key establishment abstraction | The present clause specifies how to combine two or more key establishment schemes into a hybrid key establishment scheme, under the assumption that all KEM schemes provide at least OW-CPA security. NOTE: A KEM that provides IND-CPA or IND-CCA also provides OW-CPA. (See annex B for additional details.) A key establishme... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.1.2 Key establishment abstraction to ECDHE | This clause specifies the mapping of the key establishment abstraction interface to ECDHE: (sk, P) = KeyGen( ) = ECKeyGen( ). The ResponseFunc shall be a combination of the ECKeyGen( ) function and the ECDH( ) function as follows. ResponseFunc(P): 1) (sk', R) = ECKeyGen( ). 2) k or ⊥ = ECDH(sk', P). 3) Return (k, R) or... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.1.3 Key establishment abstraction to KEM | This clause specifies the mapping of the key establishment abstraction to a KEM: (sk, P) = KeyGen( ) = KEMKeyGen( ). The ResponseFunc shall be the Encaps( ) function, (k, C) or ⊥ = ResponseFunc(P) = Encaps(P). The ReceiveFunc shall be the Decaps( ) function, k or ⊥ = ReceiveFunc(sk, C) = Decaps(sk, C), where C is the c... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.2 Concatenate hybrid key establishment scheme | |
856850865c40cb04931b6c475756c133 | 103 744 | 8.2.1 Concatenate hybrid key establishment scheme - ephemeral | This clause specifies the concatenate hybrid key establishment scheme using ephemeral keys. The key establishment description of Figure 3 is extended to exchange a pair of public keys in a single message and multiple response values in a single message. The concatenate hybrid key establishment scheme is constructed as ... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.2.2 Concatenate hybrid key establishment scheme - static | This clause specifies the concatenate hybrid key establishment scheme using static keys. The key establishment description of Figure 3 is modified to obtain a pair of static public keys in a trusted manner in a single message and a pair of response values in a single message. The roles of Initiator and Responder are re... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.3 Cascade hybrid key establishment scheme | |
856850865c40cb04931b6c475756c133 | 103 744 | 8.3.1 Cascade hybrid key establishment scheme - ephemeral | This clause specifies the cascade hybrid key establishment scheme using ephemeral keys. The key establishment description of Figure 3 is extended to exchange multiple public keys in different messages and multiple response values in different messages. The cascade hybrid key establishment scheme is constructed as depic... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.3.2 Cascade hybrid key establishment scheme - static | This clause specifies the cascade hybrid key establishment scheme using static keys. A hybrid key establishment scheme using static keys is constructed as depicted in Figure 7. ETSI ETSI TS 103 744 V1.2.2 (2026-02) 26 A (Initiator) B (Responder) (sk1, P1), (sk2, P2), … MA1 = (P1, …), MA2 = (P2, …) (k1, R1) or ⊥ Respo... |
856850865c40cb04931b6c475756c133 | 103 744 | 8.3.3 Cascade hybrid key combiner - CasKDF | This clause specifies the cascade hybrid key combiner using the cascade KDF CasKDF(), as denoted in Figure 6 and Figure 7. The CasKDF() mode shall be defined as follows: Fixed values: KDF - the key derivation function being used from clause 7.4. PRF - the PRF function being used from clause 7.3. When KDF is instantiate... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 1 Scope | The present document has the objective to provide guidelines for the usage of SAREF over oneM2M (also including the SDT interoperability) for vertical industry sectors. The present document also provides a simple use case for guiding application developers to model physical devices in oneM2M and adding semantic annotat... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 2 References | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 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... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 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... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 3 Definition of terms, symbols and abbreviations | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 3.1 Terms | Void. |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 3.2 Symbols | Void. |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AE Application Entity API Application Programming Interface CSE Common Service Entity HTTP Hypertext Transfer Protocol IoT Internet Of Things IPE Interworking Proxy Element JSON JavaScript Object Notation M2M Machine to Machine NoDN Non-oneM2M... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 4 Motivation | The assumption of many existing oneM2M applications is that they interact with other oneM2M applications through known resource structures. They either create the resources themselves or are configured to use specific resources. Information is typically stored in containers, sometimes as base64-encoded content instance... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 5 System Description | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 5.1 Use case | The example scenario describes a clothes-washing machine and an application to monitor and control the IoT enabled product. This clause will show three different oneM2M resource tree models of the clothes washing machine and the call flows to create those models. The logic and call flows necessary for a client applicat... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 5.2 Custom Model | Using oneM2M to represent devices allows for unlimited flexibility. A device model can be customized to support the needs of the manufacturer or system architecture. The resource tree structure shown here represents a custom model that has a single container for reading the status of the washing machine and a separate ... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 5.3 Semantic Modelling | A SAREF description of the washing machine is mapped to the resource structure shown in Figure 7 using the rules described in ETSI TS 118 130 [i.2] and ETSI TS 118 112 [i.1]. A complete derivation of this example is shown in ETSI TS 118 112 [i.1], clause B.1.3.3. The description of our (simplified) washing machine usin... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 5.4 Smart Device Modelling | ETSI TS 118 123 [i.5] defines a framework for developing common standardized models of devices. There are multiple device specific domains defined and new models and domains are added in each release of oneM2M. The Home Domain contains a deviceClothesWasher model that aligns with the device that has been modeled. The r... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6 Semantic Annotation in oneM2M | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6.1 Semantic description of services using SAREF Ontology | The Smart Applications REFerence ontology (SAREF) is intended to enable interoperability between solutions from different providers and among various activity sectors in the Internet of Things (IoT), thus contributing to the development of the global digital market. SAREF explicitly specifies the recurring core concept... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6.2 Describing oneM2M APIs with the oneM2M Base Ontology | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6.2.1 Clothes Washing Machine APIs using oneM2M | Because the resource tree structure for each of the models is different the oneM2M primitives needed to access the services of the clothes washing machine will also be different. However, the goal for interworking device models is to allow a user to issue the same command to perform an operation regardless of which mod... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6.2.2 Custom Model API semantic description | The specific primitive requests defined in clause 6.2.1 are described in RDF triples using the oneM2M base ontology. The properties of interest in the oneM2M base ontology are: • m2m:oneM2MTargetURI • m2m:hasDataRestriction • m2m:oneM2Mmethod • m2m:oneM2Mattribute @prefix saref: <https://saref.etsi.org/core/>. @prefix ... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6.2.3 Semantic Model annotation | The specific primitive requests described in clause 6.2.1 are described in RDF triples using the oneM2M base ontology. The classes of interest in the oneM2M base ontology are: • m2m:oneM2MTargetURI • m2m:hasDataRestriction • m2m:oneM2MMethod • m2m:oneM2Mattribute ETSI ETSI TS 103 780 V1.1.1 (2022-08) 21 @prefix saref: ... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 6.2.4 SDT model annotation | The specific primitive requests described in clause 6.2.1 are described in RDF triples using the oneM2M base ontology. The classes of interest in the oneM2M base ontology are: • m2m:oneM2MTargetURI • m2m:hasDataRestriction • m2m:oneM2MMethod • m2m:oneM2Mattribute @prefix saref: <https://saref.etsi.org/core/>. @prefix s... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 7 Semantic Queries | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 7.1 Foreword | This clause describes the semantic queries and how the responses can be used to achieve interoperability. Generally, these queries are executed by an application that is designed to use the IoT devices. |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 7.2 Discovery Queries | By using the oneM2M Base Ontology in the <semanticDescriptor> resources it is possible to send queries to the oneM2M CSE to find the services offered by a device and further query those services to discover the oneM2M primitives to access those services. Here is a list of queries that usable for all three of the models... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 7.3 Interoperability Queries | The following queries demonstrate how interoperability is achieved using semantics in oneM2M. Using the results of the queries above it is possible to issue the following types of queries to determine exactly how to use the services of the washing machines, without regard the way it was modelled. This query shows how t... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8 Procedures | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.1 Introduction | Previous clauses describe the use case, the call flows, the semantic description of our device and the SPARQL queries that can be used based on the created semantic descriptions. As it is possible to see in this clause, the values returned from a query are fully dependent on the query issued. The oneM2M CSE will pass t... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.2 Implementation | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.2.1 Semantics Description Utilities | The requirements for the creation of a <semanticDescription> resource include base64 encoding the 'dsp' attribute. There are many libraries that do this operation and for this example a python library was used. import base64 def smdEncode(description): msgAscii = description.encode('ascii') b64 = base64.b64encode(msgAs... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.2.2 Semantic Query Utilities | When sending a SPARQL query as a request parameter for a oneM2M primitive, the query shall be "url" encoded. There are many libraries that do this operation and for this example a python library was used. import urllib.parse def encodedSparqlQuery(query): return (urllib.parse.quote(query,safe='')) #safe is by default '... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.3 Semantics representations and primitives | |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.3.1 Introduction | In oneM2M the <semanticDescriptor> resource is used to provide semantic annotations, such as the ones in clause 7. Semantic annotations can use the oneM2M base ontology as well as external ontologies, such as SAREF. The oneM2M base ontology is primarily used to discover how to use the APIs for devices that are modelled... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.3.2 Create <semanticDescriptor> | The <semanticDescriptor> resource can be created by the entity that is creating the model or by a separate client entity, depending on the <accessControlPolicies> of the parent resource. This example shows the create <semanticDescriptor> for the Custom Model. The RDF triples used to semantically describe the washing ma... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 8.3.3 Semantic Query | When a SPARQL query is created, it can be passed in the "semanticFilter" request parameter, shown below with the shortname form of the request parameter of "smf". The query shall first be ascii encoded. Using python, the following code will execute query 4 from above to dynamically determine all four primitives needed ... |
5b2835aa77f8a73f4758d7b54b7045ef | 103 780 | 9 Conclusion | The Internet of Things has led to the requirement to model physical devices. In oneM2M there are three methods available to build a model of a device: • Create a custom model using the variety of data sharing resources available in oneM2M to represent the information and services that are exposed by a real-world device... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 1 Scope | The present document provides speech transmission performance requirements for wireless terminals; it addresses several types of mobile wireless terminals, including softphones. The present document addresses handset and headset functionality of wideband wireless terminals. Test methods and performance requirements app... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 2 References | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 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... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 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... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 3 Definition of terms, symbols and abbreviations | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 3.1 Terms | For the purposes of the present document, the following terms apply: artificial ear: device for the calibration of earphones incorporating an acoustic coupler and a calibrated microphone for the measurement of the sound pressure and having an overall acoustic impedance similar to that of the median adult human ear over... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 3.2 Symbols | Void. |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: a.c. alternating current AM-FM Amplitude Modulation - Frequency Modulation AMR-WB Adaptive Mode Rate - Wide Band CS Composite Source CSS Composite Source Signal DECT Digital Enhanced Cordless Telecommunications ETSI ETSI TS 103 739 V1.4.1 (202... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 4 Void | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5 Test Configurations | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.1 Set-up interface | The generic schematic as defined in figure 5.1-1 is applicable to any wireless link. ETSI ETSI TS 103 739 V1.4.1 (2021-10) 11 NOTE: The "whole" terminal includes all the components from "RF interface" to the transducers and may include an additional (radio) link. The air interface considered in the figure is not the ad... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.2 Set-up for terminals | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.2.0 General | The acoustical access to terminals is the most realistic simulation of the average subscriber. This can be made by using HATS (Head And Torso Simulator) with appropriate ear simulation and appropriate means to fix handset and headset terminals in a realistic and reproducible way to the HATS. HATS is described in Recomm... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.2.1 Setup for handsets and headsets | When using a handset telephone the handset is placed in the HATS position as described in Recommendation ITU-T P.64 [6]. The artificial mouth shall conform with Recommendation ITU-T P.58 [5]. The spectrum of acoustic signal produced by the artificial mouth is calibrated under free field conditions at the MRP. ETSI ETSI... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.2.2 Setup of variable echo path | The handset is positioned d = 3 cm above a horizontal hard surface, facing the surface with speaker and microphone. The surface shall be at least 35 × 35 cm. The handset is fixed like a pendulum with a non-elastic cord 3 cm above the centre of the horizontal surface, see figure 5.2.2-1. The pivot is 55 ± 1 cm above the... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.2.3 Setup for testing positionial robustness of handsets | In order to investigate the robustness of certain measurements against non-default positions as described in clause 5.2.1, three modified positions are defined for the send and receive side. Tables 5.2.3-1 and 5.2.3-2 provide a description of these positions, which are derived from typical user behaviour. Figure 5.2.3-... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.3 Acoustical environment | In general different acoustical environments have to be taken into account: either room noise and background noise are an inherent part of the test environment or room noise and background noise shall be eliminated to such an extent that their influence on the test results can be neglected. Unless stated otherwise, mea... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.4 Test signals | Modern wireless terminals often deploy nonlinear and time-varying processing. As such terminals are designed for speech transmission, the most appropriate test signal is real speech. Appropriate test signals (general description) are defined in Recommendation ITU-T P.501 [10]. For testing the wideband telephony service... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.5 Calibration | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.5.1 Position and calibration of HATS | All the send and receive characteristics shall be tested with the HATS, it shall be indicated what type of ear was used at what application force. ETSI ETSI TS 103 739 V1.4.1 (2021-10) 15 The various steps for calibration of the artificial mouth are described in Recommendation ITU-T P.581 [12]. The spectrum of acoustic... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.5.2 Setup of background noise simulation | A setup for simulating realistic background noises in a lab-type environment is described in ETSI TS 103 224 [23]. ETSI TS 103 224 [23] contains a description of the recording arrangement for realistic background noises, a description of the setup for a loudspeaker arrangement suitable to simulate a background noise fi... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.6 Environmental conditions for tests | The following conditions shall apply for the testing environment: a) Ambient temperature: 15 °C to 35 °C (inclusive); b) Relative humidity: 5 % to 85 %; c) Air pressure: 86 kPa to 106 kPa (860 mbar to 1 060 mbar). |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.7 Accuracy of test equipment | Unless specified otherwise, the accuracy of measurements made by test equipment shall be better than: Table 5.7-1: Accuracy of measurements Item Accuracy Electrical Signal Level Electrical Signal Level Sound pressure Time Frequency Application force Measured maximum frequency Clock Accuracy ±0,2 dB for levels ≥ -50 dBV... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.8 Power feeding conditions | For terminal equipment, which is directly powered from the mains supply, all tests shall be carried out within ±5 % of the rated voltage of that supply. If the equipment is powered by other means and those means are not supplied as part of the apparatus, all tests shall be carried out within the power supply limit decl... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 5.9 Influence of terminal delay on measurements | As delay is introduced by the terminal, care shall be taken for all measurements where exact position of the analysis window is required. It shall be checked that the test is performed on the test signal and not any other signal. 6 Codec independent requirements and associated Measurement Methodologies |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.1 Send and receive frequency response | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.1.1 Send frequency response | Due to diffuse field equalization applied in the receive direction a flat frequency response is preferable in send path. Requirement The send frequency response of the handset or the headset shall be within a mask as defined in table 6.1.1-1 and shown in figure 6.1.1-1. This mask shall be applicable for all types of ha... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.1.2 Receive frequency response | Requirement The receive frequency response of the handset or the headset shall be within a mask as defined in table 6.1.2-1 and shown in figures 6.1.2-1, 6.1.2-2 and 6.1.2-3. The application force for handsets is 2N, 8N and 13N. The mask defined for 8N application force shall be applicable for all types of headsets. Ta... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.1.3 Positional Robustness of Frequency Response | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.1.3.1 Send | Requirement For each of the modified handset positions, the send frequency response shall be within a given mask. The mask values per frequency are identical to table 6.1.1-1, except that an additional tolerance is provided for certain positions. Table 6.1.3-1 provides the requirements on the lower limits per position.... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.1.3.2 Receive | Requirement For each of the modified handset positions, the send frequency response shall be within a given mask. The mask values per frequency are identical to table 6.1.2-1, except that an additional tolerance is provided for certain positions. Table 6.1.3-2 provides the requirements on the lower limits per position.... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2 Send and receive loudness ratings | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.1 Send Loudness Rating (SLR) | Requirement The nominal value of Send Loudness Rating (SLR) shall be: SLR = +8 dB ± 3 dB (2) Measurement method The test signal to be used for the measurements shall be the British-English single talk sequence described in clause 7.3.2 of Recommendation ITU-T P.501 [10]. The handset or headset terminal is set up as des... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.2 Microphone (mic) mute | Requirement The Send Loudness Rating (SLR) with mic mute on shall be 50 dB higher than with mic mute off. Measurement method The handset terminal or the headset terminal is set up as described in clause 6.2.1, but its microphone shall be configured to be muted. Measurement and calculation method are the same as in clau... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.3 Receive Loudness Rating (RLR) | Requirement The nominal value of Receive Loudness Rating (RLR) for handset and monaural headset shall be: RLR = +2 dB ± 3 dB (3) Where a user controlled receive volume control is provided, the RLR shall meet the selected nominal value for at least one setting of the control. When the control is set to maximum, the RLR ... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.4 Positional Robustness of LR | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.4.1 SLR | Requirement The difference (in dB) between the SLR measured in each of the three modified handset positions and the one in standard position (STD) shall be in the range -3 to +3 dB. ETSI ETSI TS 103 739 V1.4.1 (2021-10) 24 Measurement method In addition to the test setup and measurement of clause 6.2.1, each of the thr... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.4.2 RLR | Requirement The difference (in dB) between the RLR measured in each of the three modified handset positions and the one in standard position (STD) shall be in the range -3 to +3 dB. Measurement method In addition to the test setup and measurement of clause 6.2.3, each of the three modified handset positions for receive... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.5 Send Loudness Level | Requirements The nominal value of Send Loudness Level (SLL) shall be: SLL = 75 phon ± 4 phon Measurement method The test signal to be used for the measurements shall be the British-English single talk sequence described in clause 7.3.2 of Recommendation ITU-T P.501 [10]. The handset or headset terminal is set up as des... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.2.6 Receive Loudness Level | Requirements The nominal value of Receive Loudness Level (RLL) for handsets, monaural and binaural/stereo headsets shall be: RLL = 75 phon ± 4 phon In case a user controlled receive volume control is provided, for at least one setting of the control the RLL shall meet the nominal value. When the control is set to maxim... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.3 Sidetone parameters | |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.3.1 Overview | The present document covers different types of terminals and different use cases (including noisy environments). STMR requirements are basically defined when using terminals in low noise environments. |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.3.2 Side Tone Masking Rating (STMR) | Requirement The Side Tone Masking Rating (STMR) shall be 16 dB ± 4 dB for nominal setting of the volume control. For all other positions of the volume control, the STMR shall not be below 8 dB. NOTE: It is preferable to have a constant STMR independent of the volume control setting. Measurement method The test signal t... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.3.3 Sidetone delay | Requirement The maximum sidetone-round-trip delay shall be ≤ 5 ms, measured in an echo-free setup. Measurement method The handset or headset terminal is set up as described in clause 5.2. The handset is mounted in the standard position of the HATS. The test signal is a CS-signal complying with Recommendation ITU-T P.50... |
0f069814918a51ab5d585b1046fd3616 | 103 739 | 6.4 Send and receive noise |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.