hash
stringlengths
32
32
doc_id
stringlengths
7
13
section
stringlengths
3
121
content
stringlengths
0
2.2M
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.3.2.1 General requirements
In general, ULE data transfers ("packet mode") and regular calls ("circuit mode") should run independently using separate MAC bearers, channel selection procedures and higher layers (DLC and NWK). This simplifies the design and implementation. Another reason for keeping the "packet mode" and "circuit mode" separate is ...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.3.2.2 ULE request whilst "circuit mode" active
If a ULE PP has an active "circuit mode" call (e.g. voice call) and a request for ULE data transfer occurs, then the following shall apply: • If there are no resources for the ULE data transfer, then according to the requirements of the application, one of the following shall apply: - The ULE data transfer request is d...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.3.2.3 "Circuit mode" request whilst ULE active
If the ULE PP has an active ULE data transfer ("packet mode") and a request for a "circuit mode" call (e.g. voice call) occurs, then the following shall apply: • If there are no resources for the "circuit mode" call, then according to the requirements of the application then one of the following shall apply: - The "cir...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.3.2.4 Suspend/resume ULE service
Some applications might want to disable ULE data transfer whilst performing extended "circuit mode" operations. For example, when performing Software Download Over The Air, or when the nature of the hybrid device is modal (e.g. operating as either ULE or regular device, but not both at the same time). These application...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.4.2 Paging descriptors for SUOTA push mode
ULE Phase 2 paging descriptor for SUOTA is defined in clause 10.6.2.5 and specifically in clause 10.6.2.5.2.4 of the present document. As with all ULE B-field paging, a "master" descriptor shall be assigned which defines the paging periodicity, and one or more "slave" descriptors shall be assigned which determine the t...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.5 Additional requirements for ULE NWK Control
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.5.1 Default ULE PVC transaction parameters
The default parameters for ULE PVC transactions are as described in ETSI TS 102 939-1 [12], clause 12.1.3.5, with the exception of the value(s) given in Table 42. Table 42: Specific default ULE PVC transaction parameters Information element Field within the information element Default values Normative action/comment <<...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.6 U-NEMo procedures
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
12.6.1 Communication of U-NEMo preferred carrier
The U-NEMo preferred carrier shall be passed from the base to the ULE device using a <<ULE-MAC- CONFIGURATION-INFO>> Information Element (see ETSI TS 102 939-1 [12], clause A.2.1). This operation may be performed by any {CC SERVICE CHANGE} operation with the capability to transport the << ULE-MAC- CONFIGURATION-INFO >>...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13 Services and Interworking procedures
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1 Specific procedures for ULE phase 2
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1 Service channels transported via <<IWU-to-IWU>> IE
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.1 General concepts
In the context of the present document a "service channel" is defined as any point to point channel able to carry higher layer data different from regular U-plane transmission. All service channels defined by the present document are bidirectional and transported via C-plane procedures using the IE <<IWU-to-IWU>> as co...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.2 Configuration and control service channel
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.2.0 General
This service channel is identical to the one defined in ETSI TS 102 939-1 [12], clause 13.2.1. It is intended to be used to exchange configuration and control information. The configuration and control information is transported in an <<IWU to IWU>> Information Element, contained inside an IWU-INFO message, as describe...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.2.1 ULE Common Control Protocol procedures
One of the protocols that can be transported by the Configuration and Control Service Channel is the ULE Common Control Protocol. This may be used to send configuration and control information. The message is coded in to an <<IWU to IWU>> Information Element contained in an IWU-INFO message. It is sent using the config...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3 CCM encrypted general purpose service channel
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3.0 General
This service channel provides a pair of end-points accessible to the higher layers where application protocol messages may be exchanged. This channel is intended for use when it is not possible nor convenient to utilize regular ULE bearers for sending data via U-plane service. An example of such situation is when a cir...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3.1 Services provided by the DECT sub-system
The DECT system provides the following features and services regarding the general purpose service channel. • A pair of SAPs, accessible directly by the application, separated from regular U-plane service SAPs. • CCM encryption of the messages using the same key used by regular U-plane service, but a different Initiali...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3.2 Transport of the general purpose service channel
Data shall be sent using <<IWU-to-IWU>> Information Element contained within one or more {IWU-INFO} Call Control (CC) message. The general format of the message is shown in Table 43. These IWU-INFO messages shall use the special Transaction Value of 5, as described in ETSI TS 102 939-1 [12], clause 12.1.2.2. The IWU-IN...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3.3 Security procedures
13.1.1.3.3.1 CCM encryption If DLC service is LU14 [ULE1-D.1] then, the service channel shall also be CCM encrypted. To encrypt the channel, each message before segmentation shall be CCM encrypted according to the provisions given in ETSI EN 300 175-7 [7], clause 6.6.2.8. The following specific provisions shall apply: ...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3.4 Segmentation and reassembling
13.1.1.3.4.0 General The external message will be CCM encrypted and the MIC of 4 octets shall be added at the end of the message, as described in clause 13.1.1.3.3. If needed, the resulting structure shall be segmented into pieces of "N" bytes or less, where the value of "N" is chosen as the maximum value that allows t...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.1.3.5 MAC Release Reason Emulation
The regular ULE U-plane data service has a "back-channel" by virtue of the "release reason" mechanism. This provides "reason" and "info" fields. These fields can be used to feed-back information regarding the link and/or requested next action, for example requesting the PP to "set-up again". However, when ULE data is s...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.2 IWU procedures for C/L downlink multicast service
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.2.1 General
IWU instances for the C/L downlink multicast service are independent from the instance used by the C/O service and are acceded by the application towards independent SAPs. The application decides which messages are routed toward C/L downlink multicast SAP, and which are routed towards the C/O SAP, taking into account t...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.2.2 U-plane procedures
The service is uni-directional. Otherwise, there is no difference compared to C/O service. Transparent IWU does not add any header to the U-plane format and is not used for identification of instances. Separation of instances (usually allocated to multicast groups) is done by the different SAP towards the application l...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
13.1.2.3 C-plane procedures
There are no specific C-plane procedures for the C/L downlink multicast service. The service inherits all attributes negotiated by means of C-plane procedures for the C/O service, such as the maximum MTU/SDU size, and the identification parameters of the transported protocol. See ETSI TS 102 939-1 [12], clause B.2.2. •...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14 Application procedures
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.1 Hybrid device voice service
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.1.0 Introduction
ULE devices that also support a voice service are known as "hybrid" devices. Devices such as medical alarm pendants and door entry-phone intercoms fall under this category. Many hybrid devices will not have keypad and display, or only have very limited keypad and display, (e.g. 1 button and 1 LED). Additionally, some d...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.1.1 General requirements
The specific requirements for hybrid voice devices are defined by the feature/service support tables in clause 6.4, clause 6.5, clause 6.6, clause 6.7, clause 6.8, clause 6.10, clause 6.11 and clause 6.12.
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.2 Hybrid device data service
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.2.0 Introduction
ULE devices that also support an additional (non-ULE) data service are "hybrid" devices. The particular data service is non-specific, and could for example be DPRS, Light Data Service, or other connection-orientated data service. The key distinction is that this data services uses traditional DECT procedures (referred ...
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.2.1 General requirements
The specific requirements for hybrid data devices are defined by the feature/service support tables in clause 6.4, clause 6.5, clause 6.6, clause 6.7, clause 6.8, clause 6.10, clause 6.11 and clause 6.13.
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.3 Software Upgrade Over The Air (SUOTA) for ULE devices
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.3.0 Introduction
The Software Upgrade Over The Air (SUOTA) is a specific use-case of hybrid device with data service. It is such a significant feature that it has its own application layer feature definition. However, a device supporting SUOTA is still classed as a hybrid data device.
852a56a1ce48f14ae4bbbda373f8ce93
102 939-2
14.3.1 General requirements
The specific requirements for SUOTA are defined by the feature/service support tables in clause 6.4, clause 6.5, clause 6.6, clause 6.7, clause 6.8, clause 6.10, clause 6.11 and clause 6.13. The SUOTA process can be initiated from the PP or the FP. For example, the PP may periodically check for the availability of new ...
01d4cead4603302c51d644c860b8516f
102 939-1
1 Scope
The present document specifies the first set of functionalities of the ETSI radio technology named DECT Ultra Low Energy (ULE). DECT ULE provides bi-directional radio communication with medium range, data protection, and Ultra Low Power consumption between different types of Portable Devices and Radio Fixed Parts. DECT...
01d4cead4603302c51d644c860b8516f
102 939-1
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 referenced document (including any amendments) applies. Referenced documents which a...
01d4cead4603302c51d644c860b8516f
102 939-1
2.1 Normative references
The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 1: Overview". [2] ETSI EN 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 2:...
01d4cead4603302c51d644c860b8516f
102 939-1
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 101 178: "Digital Enhanced Cordless Telecommunications (DECT); A high Level Guide to the DECT Standardization". [i.2] ETSI TBR 006: "Digital E...
01d4cead4603302c51d644c860b8516f
102 939-1
3 Definitions, symbols and abbreviations
01d4cead4603302c51d644c860b8516f
102 939-1
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply: Access Rights Identity (ARI): globally unique identity that shows the access rights related to a service provider NOTE: See EN 300 175-6 [6]. attach: process whereby a PP within the coverage area of a FP to which it has access rights, ...
01d4cead4603302c51d644c860b8516f
102 939-1
3.2 Symbols and abbreviations
For the purposes of the present document, the following symbols, terms and definitions apply: AC Authentication Code ACK ACKnowledgement AES Advanced Encryption Standard AP Application Profile ARI Access Rights Identity ARQ Automatic Retransmission reQuest BA (bits) B-field identification bits, the bits from the A-fiel...
01d4cead4603302c51d644c860b8516f
102 939-1
4 Description of services
01d4cead4603302c51d644c860b8516f
102 939-1
4.1 DECT Ultra Low Energy
01d4cead4603302c51d644c860b8516f
102 939-1
4.1.1 Introduction
Digital Enhanced Cordless Telecommunications (DECT) technology was launched in 1987 and has since then developed into one of the most reliable and flexible digital radio access standard for cordless communication. DECT has been a continuously evolving technology and new versions of the core technology such as New Gener...
01d4cead4603302c51d644c860b8516f
102 939-1
4.2 ULE phase 1
01d4cead4603302c51d644c860b8516f
102 939-1
4.2.1 Definition of ULE phase 1
DECT ULE phase 1 is defined as a specific DECT ULE capability set that provides solutions intended primarily, but not necessarily, for Home Automation scenarios. DECT ULE phase 1 consists on three types of PP devices (or device functionalities) named type 1: "sensor", type 2: "fast actuator" and type 3: "slow actuator"...
01d4cead4603302c51d644c860b8516f
102 939-1
4.2.2 Example of applications covered by ULE phase 1
Examples of the applications that can be built with DECT ULE phase 1 (the present document) are the following: • Actuator devices Devices with fast response time requirements and traffic usually FT initiated, such as electricity plugs, electric control elements, alarm centrals and other control elements. • Slow Actuato...
01d4cead4603302c51d644c860b8516f
102 939-1
4.2.3 Physical layer, radio properties and spectrum use
The maximum radio coverage range of DECT ULE will be as wide as standard DECT technology. Smaller coverage may be defined for specific applications due to power consumption and spectrum use considerations. Due to the nature of DECT ULE applications, it is foreseen that most of them would operate, however not necessaril...
01d4cead4603302c51d644c860b8516f
102 939-1
4.2.4 Coexistence with other DECT services
DECT ULE has been designed to be coexistent with other DECT applications (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...
01d4cead4603302c51d644c860b8516f
102 939-1
4.3 Reference scenarios for DECT ULE phase 1
The following figures show examples of the applications scenarios that can be covered by DECT ULE phase 1.
01d4cead4603302c51d644c860b8516f
102 939-1
4.3.1 Security applications (fire and burglary alarms)
Figure 1 shows a typical security application scenario. External communications (via PSTN or internet) may be part of the scenario and easily implemented due to the usual PSTN or internet connectivity of most DECT RFPs. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 24 Figure 1: Security application scenario (fire and burglar...
01d4cead4603302c51d644c860b8516f
102 939-1
4.3.2 Global Home control and domotic scenario
Figure 2 shows a Home control and domotic scenario. Sensor type and actuator type ULE devices are combined with specific application logic to perform a potentially large number of functions in a home scenario. DECT advanced voice terminals such as New Generation DECT parts 3 or 5, and external connectivity via internet...
01d4cead4603302c51d644c860b8516f
102 939-1
4.3.3 Energy and appliances management scenario
Energy control is a target application of DECT ULE phase 1. Figure 3 shows an energy and appliances management scenario in a domestic environment. Sensor type and actuator type ULE devices are used to perform multiple energy control related functions. Interconnection to utility companies via internet may be part of the...
01d4cead4603302c51d644c860b8516f
102 939-1
4.4 Requirement specification for ULE phase 1
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1 ULE phase 1 device types
ULE phase 1 supports the following types of devices: • RFP with support of ULE phase 1 • PP type I: "sensor" • PP type II: "fast actuator" • PP type III: "slow actuator"
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.1 PP type I: "sensor"
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.1.1 General description
ULE PP devices, generally battery powered, with long sleep times and strong power saving requirements. Typical examples are sensors (all types), Smoke Detectors, Motion Detectors, temperature sensor, switches and press buttons, command modules, etc.
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.1.2 Requirements and functionalities for type I devices
ULE type I "sensor" PPs has the following requirements and specific functionalities: • Ultra low power consumption ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 26 • Unlocked "deep sleep" operation • Ultra low paging cycles (type Ia) or no paging cycle at all (type Ib) • Fast response times when activated due to an event at ...
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.2 PP type II: "fast actuator"
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.2.1 General description
ULE PP devices, generally line powered, with not so strong power saving requirements, but requiring fast response times as response to FP side orders. Typical examples are electric control modules (actuators) driving powers circuits, air conditioning equipment, alarm bells and control modules, etc.
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.2.2 Requirements and functionalities for type II devices
ULE type II "fast actuator" PPs have the following requirements and specific functionalities: • Locked operation • Normal or fast paging cycles • High paging capacity • Fast response times as response to paging commands from the FP side
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.3 PP type III: "slow actuator"
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.3.1 General description
ULE PP devices, battery or powered, with power saving requirements, but with traffic dominated by order from the FP and requiring medium response times as response to FP side orders, Typical examples are control modules (actuators) for heating (hot water circuit radiator) and air conditioning equipment.
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.3.2 Requirements and functionalities for type III devices
ULE type III "slow actuator" PPs have the following requirements and specific functionalities: • Locked or un-locked operation • Normal to slow paging cycles • Medium paging capacity • Medium response times as response to paging commands from the FP side
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.4 ULE phase 1 compliant RFP
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.4.1 General description
A DECT RFP supporting the functionalities described in the present document. The RFP will typically support other DECT services such as GAP or New Generation DECT (any phase), however this is not mandatory. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 27
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.1.4.2 Requirements and functionalities for ULE phase 1 RFP
ULE phase 1 RFP has the following requirements and specific functionalities: General coexistence requirement: • It should be possible the implementation of RFP supporting at the same time, ULE phase 1 and a DECT voice service (GAP or New Generation DECT). Specific ULE phase 1 requirements: • All RFPs compliant with the...
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.2 U-plane interworking and protocol architecture
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.2.1 ULE phase 1 protocol architecture
Figure 4 shows the protocol architecture of DECT ULE phase 1. An external protocol (application layer) is transported over LU14 by means of an Interworking layer. The DECT C-plane may be activated as response to external application protocol when needed. In ULE phase 1, the only Interworking defined provides the transp...
01d4cead4603302c51d644c860b8516f
102 939-1
4.4.3 Performance Objectives
Table 1 shows the performance objectives of DECT ULE phase 1. Table 1: Performance objectives Performance Value Notes Maximum data rate for full-slot devices 24 kbit/s Maximum data rate for double-slot devices 64 kbit/s Response time for a PP => FP transmission when the PP was in locked state 20 ms Response time for a ...
01d4cead4603302c51d644c860b8516f
102 939-1
4.5 Technical features implemented by ULE phase 1
DECT Ultra Low Energy (ULE) Part 1 (the present document) provides the following basic functionalities.
01d4cead4603302c51d644c860b8516f
102 939-1
4.5.1 MAC/PHY layer
C/O MAC service with capability of suspend/resume via expedited operations: • Advanced connection setup • Advanced connection release • Full slot • Short slot • MAC format IPQ Expedited ULE C/O operations: • Ultra-fast "expedited" procedures optimized for ULE and allowing combined transmission of signalling and data pa...
01d4cead4603302c51d644c860b8516f
102 939-1
4.5.2 DLC layer
DLC C-plane • C-plane DLC (LAPC) as in existing DECT DLC U-plane • New DLC service LU14 adding a CCM authenticated encryption layer based on existing service LU10 - Provides sequence numbering and control, flow control, Tx/Rx window handling, and segmentation and re-assembling, of higher layer packets - See also securi...
01d4cead4603302c51d644c860b8516f
102 939-1
4.5.3 NWK layer
• Connection Oriented model including CC (Call Control) and MM (Mobility Management) entities - Configurable Virtual Circuits (= PDP Context) created at the beginning and kept for long time - No NWK layer operations required during regular packet handling • DECT CC message and operations support - Simplified NWK CC pro...
01d4cead4603302c51d644c860b8516f
102 939-1
4.5.4 Interworking and Application layer
Transparent interworking allowing the use of external protocols with packet size of up to 500 octets.
01d4cead4603302c51d644c860b8516f
102 939-1
4.5.5 Security
NWK layer authentication algorithm DSAA2 based on AES [i.8] with key length 128 bits (see EN 300 175-7 [7]): • Provides both PT and FT mutual authentication and Cipher Key generation. • Split into two security processes in NWK side allowing geographic distribution in home/visited domains. New authenticated encryption b...
01d4cead4603302c51d644c860b8516f
102 939-1
4.5.6 Management entity
Management entity processes for: • Channel selection • Handling of collisions • Handling of other errors • Rules for resume • Rules for suspend, sending Ready for Release, Release, etc.
01d4cead4603302c51d644c860b8516f
102 939-1
5 Relevant requirements
In any case, the requirements of EN 300 176-1 [10] and any of the harmonized standard EN 301 406 [11] shall apply as well.
01d4cead4603302c51d644c860b8516f
102 939-1
5.1 Service and feature definitions
For the purposes of the present document the following service and feature definitions apply.
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.1 PHL service definitions
For the purpose of the present document, the following definitions shall apply. GFSK modulation [ULE1-P.1]: 2 level Gaussian frequency Shift Key (GFSK) modulation as defined by EN 300 175-2 [2], clause 5. Physical Packet P32 [ULE1-P.2]: Physical packet P32 (full slot) as defined by EN 300 175-2 [2], clause 4.4.2. Physi...
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.2 MAC service definitions
For the purpose of the present document, the following definitions shall apply. General [ULE1-M.1]: set of basic requirements regarding data formats, multiplexing, CRC usage, scanning and locking, which are prerequisites to communication between peer MAC entities. A-field continuous broadcast [ULE1-M.2]: simplex servic...
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.3 DLC service definitions
For the purpose of the present document, the following definitions shall apply. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 33 LU14 Enhanced Frame RELay service with CCM encryption (EFREL-CCM) [ULE1-D.1]: an enhanced frame relay service accessed through the LU14 SAP. LU14 adds CCM encryption on top of LU10. LU14 encrypts t...
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.4 NWK feature definitions
For the purpose of the present document, the following definitions shall apply. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 34 ULE phase 1 NWK control [ULE1-N.1]: simplified NWK layer control procedures for ULE phase 1. ULE Service Call [ULE1-N.2]: call with only C-plane initiated by a DECT PT for entering of FT related se...
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.5 Application service definitions
For the purpose of the present document, the following definitions shall apply. AC to bitstring mapping [ULE1.A.1]: mapping of the AC into a bitstring. Multiple subscription registration [ULE1.A.2]: ability of PP to store more than one subscription. Easy PIN code registration [ULE1.A.3]: ability to invite the user to r...
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.6 Management Entity (ME) definitions
For the purpose of the present document, the following definitions shall apply. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 35 ULE phase 1 Management [ULE1-ME.1]: inter and intra DECT protocol layers management of the phase 1 of the ULE protocol requirements that does incorporate a C-plane providing some MM and CC capabili...
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.7 U-plane service and interworking definitions
For the purpose of the present document, the following definitions shall apply: Transparent U-plane Interworking [ULE1-I.1]: provides the transparent transport of external protocol packets. C- plane configuration of the external protocol and MTU size are provided.
01d4cead4603302c51d644c860b8516f
102 939-1
5.1.8 ULE 1 device types
For the purpose of the present document, the following definitions shall apply. RFP with support of ULE phase 1 [ULE1-TYP.1]: A DECT RFP with support of ULE phase 1 specification. Other DECT services, such as GAP or NG-DECT, may also be supported in the same RFP. PP type I "sensor" with paging support [ULE1-TYP.2]: ULE...
01d4cead4603302c51d644c860b8516f
102 939-1
6 Profile specific requirements
01d4cead4603302c51d644c860b8516f
102 939-1
6.1 General
The tables listed in this clause 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. The status is identified by the status colu...
01d4cead4603302c51d644c860b8516f
102 939-1
6.2 Specific conventions
01d4cead4603302c51d644c860b8516f
102 939-1
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 all tables is as follows: • "M" (provision mandatory, process mandatory) means that the indicated feature service or procedure shall b...
01d4cead4603302c51d644c860b8516f
102 939-1
6.3 DECT ULE phase 1 device types
01d4cead4603302c51d644c860b8516f
102 939-1
6.3.1 Types of devices supported by the present document
The following types of DECT ULE phase 1 devices are supported by the present document. Additional device types may be added to further releases of the present document. Table 3: Types of DECT ULE phase 1 devices Item Name of service Reference Support status in a ULE system PT FT ULE1-TYP.1 RFP with support of ULE phase...
01d4cead4603302c51d644c860b8516f
102 939-1
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.1]. Therefore, the support status of all services, features and procedures for FP is as given in tables 5 to 19. ...
01d4cead4603302c51d644c860b8516f
102 939-1
6.4 Physical layer (PHL) requirements
01d4cead4603302c51d644c860b8516f
102 939-1
6.4.1 Physical layer (PHL) services
DECT Ultra Low Energy, phase 1 devices shall support the following Physical layer (PHL) services. Table 5: Physical layer service support Item Name of service Reference Support status PT FT ULE1-P.1 GFSK modulation 5.1.1 M M ULE1-P.2 Physical Packet P32 5.1.1 M M ULE1-P.3 Physical Packet P00 5.1.1 M M ULE1-P.4 General ...
01d4cead4603302c51d644c860b8516f
102 939-1
6.4.2 Modulation schemes
The following modulation schemes defined by EN 300 175-2 [2], annex D shall be supported. Table 6: Allowed combinations of modulation schemes Modulation scheme S-field A-field B + Z-field Support status 1a GFSK GFSK GFSK M