hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
548bdcc0533dcbd4ed60848bf1c006d9 | 102 925 | 6.3.8.1 Note | NOTE: Additional requirements may be needed in order to further investigate the effect of NLP implementations on the users' perception of speech quality. |
548bdcc0533dcbd4ed60848bf1c006d9 | 102 925 | 6.3.8.2 Activation in send direction | The activation in send direction is mainly determined by the built-up time Tr,S,min and the minimum activation level (LS,min). The minimum activation level is the level required to remove the inserted attenuation in send direction during idle mode. The built-up time is determined for the test signal burst which is appl... |
548bdcc0533dcbd4ed60848bf1c006d9 | 102 925 | 6.3.8.3 Silence suppression and comfort noise generation | For further study. ETSI ETSI TS 102 925 V1.2.1 (2018-10) 55 Annex A (normative): Room acoustics and electro acoustic equipment positioning The positioning of transducers in the acoustic environment can strongly influence their effective performances and suitable installation criteria should be followed in order to maxi... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 1 Scope | The scope of the present document is to define the system requirements for reconfiguring the radios in mobile devices. The work will be based on the Use Cases defined in TR 103 062 [i.1], TR 102 839 [i.2] and TR 102 944 [i.3]. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS); Use Cases and Scenarios for Software Defined Radio (SDR) Reference Architecture for Mobile Devic... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 3 Definitions and abbreviations | |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: resource: resource that radio application needs in active state, which includes processor and accelerator loads, memory usage, interconnect bandwidth occupation, Radio Frequency (RF) circuitry, etc. NOTE: Resources are provided by the ... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASIC Application Specific Integrated Circuit BBI BaseBand Interface BER Bit Error Rate BPA Baseband Parameter Aggregation CAT Category CII Context Information Interface CR Cognitive Radio DoA Direction of Arrival FEC Forward Error Correction F... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 4 Requirement Organization and Methodology | This clause is containing the description of how the requirements are organised and the format of the requirement. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 4.1 Requirement Organization | The present document is structured such that a level 1 section is dedicated to the requirements associated with a single category. The requirements should be partitioned into groups of related category to assist understanding. The overall structure is shown in figure 4.1.1. ETSI ETSI TS 102 969 V1.1.1 (2012-03) 8 Figur... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 4.2 Requirement Format | A letter code system is defined which makes a unique identification of each requirement R-<CAT>-<GROUP>-<XX>. It should be constructed as follows: • R-: Standard requirement prefix • <CAT> Code Category FUNC Functional aspects • <GROUP>: Requirement group identifier. A letter code will be used for this identifier. The ... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 4.3 Requirement Formulation | A requirement formulation is defined which makes a unique way to formulate it. It will be built as follows: Title: <Title Description> • Description: <The description of the requirement shall be formulated using one of the following terms. As described into the ETSI Terms & Definitions database (TEDDI), the terms are e... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 5 Working assumptions | |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 5.1 Assumptions | |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 5.1.1 Mobile Device Reconfiguration Classes | As introduced in [i.2], clause 5.4: Radio computer deployment scenarios, it is expected that the reconfiguration capabilities of MD will evolve over time. The requirements defined in the present document will thus be introduced for the concerned Mobile Device Reconfiguration Classes (MDRC) as shown in figure 5.1.1.1. F... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6 Functional Requirements | |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.1 Requirements on RAT Link Support and Management | 6.1.1 R-FUNC-RAT–01 Function for MDRC-1 to MDRC-7 A MD may offer support for multiple links to heterogeneous RATs being maintained simultaneously. 6.1.2 R-FUNC-RAT–02 Function for MDRC-1 to MDRC-7 In case that a MD offers support for multiple links to heterogeneous RATs being maintained simultaneously (in alignment to ... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.2 Base Band Interface Requirements | |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.2.1 R-FUNC-BBI-01 Composition for MDRC-1 to MDRC-7 | Base Band Interface (BBI) shall support Radio Application Interface (RAI) for baseband signal processing (including real-time Media Access Control (MAC) data processing). Explanation: Note that MDRC-1 is included in this categorization because of only one possible case that entire radio application is implemented with ... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.2.2 R-FUNC-BBI-02 Data for MDRC-1 to MDRC-7 | BBI shall support the function of transferring receive (Rx) data from baseband processor to networking stack, the function of transferring transmit (Tx) data from networking stack to baseband processor. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.2.3 R-FUNC-BBI-03 Context Information for MDRC-1 to MDRC-7 | BBI shall support the function of transferring context information to monitor. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.2.4 R-FUNC-BBI-04 Interface Type for MDRC-2 to MDRC-7 | Each BBI shall support both synchronous and asynchronous interface. Explanation: A called function block suspends the current execution until the called block execution is completed in case of synchronous interfaces and vise versa for asynchronous interfaces. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.2.5 R-FUNC-BBI-05 Pipelining for MDRC-2 to MDRC-7 | BBI shall be applicable to fixed pipeline, programmable pipeline, and hybrid pipeline. Explanation: Pipeline of function blocks is determined by the contents of metadata included in the radio application package. Modem chip manufacturer selects one of the 3 pipeline structures for their baseband processor. When the bas... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3 Base Band Function Block requirements | |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.1 R-FUNC-FB-01 Implementation for MDRC-2 to MDRC-7 | Each BBI shall be implemented with a corresponding function block which provides implementation code for each of the function block properties. Explanation: For example, a BBI corresponding to the function block shown in figure 6.3.1.1 is represented as "Name(Input, Output, Property 1, Property 2, …, Property N)" and i... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.2 R-FUNC-FB-02 Function Block for MDRC-2 to MDRC-7 | Each function block shall be defined as functionality required for implementing a radio application, including baseband signal processing, MAC data processing, etc. Explanation: Functionalities of each function block include Fast Fourier Transform (FFT), Forward Error Correction (FEC), MIMO encoding, MIMO decoding, Bea... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.3 R-FUNC-FB-03 Normative Library for MDRC-2 to MDRC-7 | The normative library shall consist of function block(s). ETSI ETSI TS 102 969 V1.1.1 (2012-03) 15 |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.4 R-FUNC-FB-04 Execution for MDRC-2 to MDRC-7 | Each function block shall be executed only by calling corresponding BBI. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.5 R-FUNC-FB-05 Side Effects for MDRC-2 to MDRC-7 | Internal state of each function block shall not be shared with any other function blocks. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.6 R-FUNC-FB-06 Shared Data for MDRC-2 to MDRC-7 | A few function blocks shall be capable to share the same input data. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.7 R-FUNC-FB-07 Concurrency for MDRC-2 to MDRC-7 | A few function blocks shall be capable to be executed in parallel. 6.3.8 R-FUNC-FB-08 User Defined Function Block for MDRC-2 to MDRC- 7 BBI shall support user defined function block for specific radio application or specific algorithm in addition to the function block specified in clause 6.3.2. Explanation: User define... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.3.9 R-FUNC-FB-09 Extendability for MDRC-2 to MDRC-7 | The normative procedure for the normative library extension by adding user defined function blocks shall be established. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4 Mobile Device Reconfiguration Requirements | 6.4.1 R-FUNC-MDR-01 Platform-specific Executable Code for MDRC-2, MDRC-3 or MDRC-4 The configuration of MD compliant to MDRC-2, MDRC-3 or MDRC-4 shall be realized with radio application package of which the user defined function block, specified in 6.3.8, is provided in platform-specific executable code. Explanation: R... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4.5 R-FUNC-MDR-05 Concurrent Execution for MDRC-1 to MDRC-7 | RPI shall provide means for explicit expression of functional blocks or operators concurrent execution. 6.4.6 R-FUNC-MDR-06 Dynamic Execution for MDRC-3, MDRC-4, MDRC-6 and MDRC-7 RPI shall provide means for explicit expression of functional blocks or operators dynamic execution. ETSI ETSI TS 102 969 V1.1.1 (2012-03) 1... |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4.7 R-FUNC-MDR-07 Formal Verification for MDRC-1 to MDRC-7 | RPI shall provide means for formal verification of URAs. 6.4.8 R-FUNC-MDR-08 Independency on Memory Model for MDRC-1 to MDRC-7 RPI shall support different radio platform memory models including the shared memory and the message passing models. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4.9 R-FUNC-MDR-09 IR Format for MDRC-5 to MDRC-7 | IR shall be expressed in a format suitable for human reading or writing and automated processing. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4.10 R-FUNC-MDR-10 Timing Constraints for MDRC-1 to MDRC-7 | RPI shall provide means for explicit expression of timing constraints in baseband processing. 6.4.11 R-FUNC-MDR-11 Intermediate Representation for MDRC-5 to MDRC-7 URAs should be kept in radio application packages as IR. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4.12 R-FUNC-MDR-12 Unified Radio Application for MDRC-1 to MDRC-7 | URA for MD compliant to MDRC-1 - MDRC-7 should be described in terms of the unified RPI independent on hardware platforms. This description is a part of the radio application package. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 6.4.13 R-FUNC-MDR-13 Function Granularity for MDRC-1 to MDRC-7 | Functional blocks described in terms of the RPI may have different granularity. Explanation: The functional blocks might be for example arithmetic operations or functions like FFT or even whole radio applications like Wi-Fi. |
a2f45fe609f3faff880995f9ca847a6a | 102 969 | 7 Conclusions | The present document introduces the system requirements to be met by the system architecture and protocol definitions work related to Base Band Interfaces. ETSI ETSI TS 102 969 V1.1.1 (2012-03) 20 History Document history V1.1.1 March 2012 Publication |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 1 Scope | The present document covers the following DECT ULE services and features: • Back-compatibility with ULE Phase 1 [12]. • Regional variants of ULE for US and Japan. • Support for hybrid devices which utilize ULE and non-ULE services (such as voice). • Software Update Over The Air (SUOTA), compatible with the same feature... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 2 References | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 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... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 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... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 3 Definition of terms, symbols and abbreviations | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 939-1 [12], ETSI TS 102 527-1 [11], ETSI TS 102 527-4 [13] and the following apply: circuit mode: DECT connections involving setup of the MAC connection using Basic Connection control or Advanced Connection control, but not the "expedited" setup m... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: BA (bits) B-field identification bits, the bits from the A-field header that provide indication for the content of the B-field of one MAC layer packet BCK bit used for IP channel flow control in MAC IP error correction services BS slow Broadcast cha... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC-LD Advanced Audio Coding - Low Delay profile AC Authentication Code ADPCM Adaptive Differential Pulse Code Modulation AES Advanced Encryption Standard AP Application Profile ARIB Association of Radio Industries and Business ARQ Automatic R... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4 Description of services and features | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1 DECT Ultra Low Energy | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.0 General | DECT ULE provides bi-directional radio communication with medium range, data protection, and Ultra Low Power consumption features between different types of Portable Devices and Radio Fixed Parts. The present document is part 2 of a multi-part deliverable intended to cover the Machine to Machine communications based on... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.1 Back-compatibility with ULE Phase 1 | ULE Phase 2 devices are back-compatible with ULE Phase 1 devices. This means, with regards to the Phase 1 functionality, a Phase 1 PT will be able to function correctly with a Phase 2 FT. Similarly, with regards to the Phase 1 functionality, a Phase 2 PT will be able to function correctly with a Phase 1 FT. Obviously, ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.2 Coexistence with other DECT services | DECT ULE has been designed to be coexistent with other DECT systems (including GAP or NG-DECT). Different types of DECT devices may be used over the same spectrum, and mixed devices supporting DECT ULE and other DECT applications may be built. It is foreseen that the majority of DECT ULE RFPs and some DECT ULE PPs will... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.3 Example applications covered by ULE Phase 2 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.3.0 General | Examples of the applications that can be built with ULE Phase 2 are the following: • Simple medical pendant alarms These devices may have some sensing ability (for instance to monitor heart rate or movement), as well as possessing an alarm button in case the wearer is in distress. They may also have additional voice ca... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.3.1 Simple medical pendant alarms | Figure 1 shows a typical use-case scenario for a medical pendant system. The user will often wear the device, so that if they require assistance then can easily activate the alarm button and get connected to a carer or medical professional. The diagram shows the ULE base station connected to the Internet, but this coul... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.3.2 Software Upgrade Over The Air | SUOTA allows a ULE device to download and upgrade its software from a remote server over the air using the DECT services. An instance of the DPRS LU10 is used for the transport layer. C-plane interactions are used to control the process, e.g. to specify the software version number and URL of the download server. The SU... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.1.3.3 M2M devices with audio capability | ULE phase 2 adds audio transmission to ULE devices. This allows the design of devices with integrated speaker and/or microphone and the capability to establish an audio communication (in addition to ULE data transport). The audio communication may be established to either: • Regular DECT handsets (GAP or NG-DECT) in th... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2 Requirements for ULE Phase 2 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1 Device types | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.0 General | In addition to the device types defined by ULE Phase 1, ULE Phase 2 also supports the following types of devices: • RFP with support of ULE Phase 2 • PP type IV: "hybrid device with voice/data support" |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.1 ULE Phase 2 RFP | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.1.1 General description | A ULE Phase 2 RFP supports the services and features described in the present document. The RFP will typically support other DECT services such as GAP or New Generation DECT; however, this is not mandatory. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.1.2 Requirements | A ULE Phase 2 RFP has the following requirements. General coexistence requirement: • The RFP can support at the same time, ULE Phase 1, ULE Phase 2 and DECT voice services (e.g. GAP or New Generation DECT). Specific ULE Phase 2 requirements: • All RFPs compliant with the present document shall be able to support all th... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.2 PP type IV: hybrid device with voice/data support | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.2.1 General description | ULE PP type IV devices are generally battery powered, with strong power saving requirements, and the occasional requirement to be used in voice/data-mode. In general, ULE PP device types can be combined, and so for example, a hybrid device may be combined with a ULE sensor type, or a ULE actuator type. Typical examples... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.1.2.2 Requirements | ULE type IV PPs shall have some or all of the following specific requirements: • The ability to transfer ULE data during a voice call • The ability to carry voice during a ULE data transfer • The ability to switch between voice and ULE data modes • The ability to use ULE paging to initiate a voice call |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.2 U-plane interworking and protocol architecture | U-plane interworking and protocol architecture is defined in ETSI TS 102 939-1 [12]. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 20 |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.2.3 Performance Objectives | Performance objectives are defined in ETSI TS 102 939-1 [12]. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3 Services and features implemented by ULE phase 2 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.0 General | In addition to the core services and features defined by DECT Ultra Low Energy (ULE) Part 1 (ETSI TS 102 939-1 [12]), the present document also provides the enhanced services and features described in clause 4.3.1 to clause 4.3.7. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.1 MAC/PHY layer | • Enhanced ULE paging support, including index-based paging identifiers, optimized paging descriptors and specific descriptors for advanced features (e.g. connectionless downlink, hybrid voice, etc.) • Connectionless downlink multi-cast paging support • Support for US and Japan regions • Long-slot (j = 640), which can ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.2 DLC layer | • LU1 Transparent Unprotected service for "hybrid voice" systems • LU10 Enhanced Frame Relay service for SUOTA/LDS • Connectionless downlink multi-cast channel • Inter-cell connection handover for "circuit mode" connections |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.3 NWK layer | • Incoming calls for "hybrid voice" devices • Handling interactions of "packet mode" and "circuit mode" operation • General Purpose Service Channel (i.e. ULE data transport over C-plane) • Various basic telephony features (e.g. on-hook/off-hook, dialled digits, alerting, etc.) • Codec negotiation/codec switching for "h... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.4 Interworking and Application layer | • Support for "hybrid voice" devices • Support for "hybrid data" devices • Support for SUOTA/LDS • General Purpose Service Channel (i.e. ULE data transport over C-plane) |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.5 Security | • Management of cipher keys for connectionless downlink multi-cast channels • Ciphering of connectionless downlink multi-cast channels • Ciphering of General Purpose Service Channel (i.e. ULE data transport over C-plane) |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.6 Management Entity | • Physical channel selection for US • Physical channel selection for Japan • DPRS management (class 4 mandatory) |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 4.3.7 Speech services and codecs | • Narrowband and wideband codecs and speech services for "hybrid voice" devices |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5 Service and feature definitions | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1 ULE Phase 2 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.1 PHL service definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.1, ETSI TS 102 527-1 [11], clause 5.5 and ETSI TS 102 527-4 [13], clause 5.1.1 apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.2 MAC service definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.2, ETSI TS 102 527-1 [11], clause 5.4, ETSI TS 102 527-4 [13], clause 5.1.2 and the following apply: U-plane C/L downlink multicast service [ULE1-M.28]: Simplex service from FT to PT that provides U-plane transmission using ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.3 DLC service definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.3, ETSI ETSI TS 102 527-1 [11], clause 5.3, ETSI TS 102 527-4 [13], clause 5.1.3 and the following apply: Intra-cell voluntary connection handover [ULE1-D.13]: internal handover process provided and initiated by the DLC laye... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.4 NWK feature definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.4, ETSI TS 102 527-1 [11], clause 5.2, ETSI TS 102 527-4 [13], clause 5.1.4 and the following apply: Security procedures for C/L downlink multicast [ULE1-N.19]: CCM encryption control and synchronization procedures for U-pla... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.5 Application feature definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.5, ETSI TS 102 527-1 [11], clause 5.7, ETSI TS 102 527-4 [13], clause 5.1.5 and the following apply: Hybrid device voice service [ULE1-A.4]: Voice support may be narrow band or wideband. Hybrid device data service [ULE1-A.5]... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.6 Management Entity (ME) definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.6, ETSI TS 102 527-4 [13], clause 5.1.6 and the following apply: ULE Physical Channel Selection for US region [ULE1-ME.3]: This service provides additional or modified channel selection procedures to meet the regulatory requ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.7 U-plane service and interworking definitions | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.7, ETSI TS 102 527-4 [13], clause 5.1.8 and the following apply: Configuration and control service channel [ULE1-I.2]: a channel transported over DECT C-plane that provides a pair of end-points accessible to the higher layer... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.8 ULE device types | For the purposes of the present document, all definitions of ETSI TS 102 939-1 [12], clause 5.1.8 and the following apply: RFP with support for ULE phase 2 [ULE1-TYP.6]: A DECT RFP with support of ULE phase 2 specification. Other DECT services, such as GAP or NG-DECT, may also be supported in the same RFP. PP type IV "... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.9 Speech services and speech coding definitions | For the purposes of the present document, all definitions of ETSI TS 102 527-1 [11], clause 5.6, apply. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 24 |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 5.1.10 Call Control (CC) and mobility management service definitions | For the purposes of the present document, all definitions of ETSI TS 102 527-4 [13], clause 5.1.7, apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6 Profile specific requirements | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.1 General | Table 1 to Table 21 define the status of all protocol elements (i.e. features, services, and procedures), which can be: mandatory, optional, conditional under the provision of another protocol element, outside the scope of the present document, or not applicable. Protocol elements defined as mandatory, optional or cond... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.2 Specific conventions | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.2.1 Use of symbols in support status tables | The symbols defined in this clause are applied for procedures, features, and services in the present document if not explicitly otherwise stated. The interpretation of status columns in Table 1 to Table 21 is as follows: C conditional to support I out-of-scope M mandatory to support N/A not applicable O optional to sup... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.3 DECT ULE phase 1 device types | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.3.1 Types of devices supported by the present document | The following types of DECT ULE devices, described by Table 1, are supported by the present document. Additional device types may be added to further releases of the present document. Table 1: Types of DECT ULE phase 2 devices Item Name of service Reference Support status in a ULE system PT FT ULE1-TYP.6 RFP with suppo... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.3.2 Specific procedures for specific device types | All services, features and procedures described in the present document are applicable to all kinds of device types, except when otherwise stated. The present document defines only one type of RFP [ULE1-TYP.6]. Therefore, the support status of all services, features and procedures for FP is as given in Table 2 to Table... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.4 Physical layer (PHL) requirements |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.