hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.4.3 PHL service to procedure mapping | The following Physical layer (PHL) service to procedure mapping shall apply. Table 7: PHL service to procedure mapping Service Procedure Reference Status PT FT ULE1-P.1 GFSK modulation 5.1.1 M M GFSK modulation 8.1.1 M M Modulation scheme 1a 8.1.2 M M ULE1-P.2 Physical Packet P32 5.5.1 M M Physical Packet P32 8.2.1 M M... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.5 MAC layer requirements | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.5.1 MAC layer services | DECT Ultra Low Energy, phase 1 devices shall support the following MAC layer services. Table 8: MAC service support Item Name of service Reference Support status PT FT ULE1-M.1 General 5.1.2 M M ULE1-M.2 A-field Continuous broadcast 5.1.2 M M ULE1-M.3 A-field Paging broadcast 5.1.2 M M ULE1-M.4 B-field Continuous ULE b... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.5.2 MAC service to procedure mapping | The following MAC layer service to procedure mapping shall apply. Table 9: MAC service to procedure mapping Service Procedure Reference Status PT FT ULE1-M.1 General 5.1.2 M M Frame and Multiframe structure 10.1.1 M M Bit mappings 10.1.2 M M E/U mux modes and B-field identification (BA) bits 10.1.3 M M Scrambling 10.1.... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.6 DLC layer | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.6.1 DLC layer services | DECT Ultra Low Energy, phase 1 devices shall support the following DLC services. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 44 Table 10: DLC service status Status Item no. Name of service Reference PT FT ULE1-D.1 LU14 Enhanced Frame RELay service with CCM (EFREL-CCM) 5.1.3 M M ULE1-D.2 LU13 Enhanced Frame RELay service wi... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.6.2 DLC service to procedure mapping | The following DLC layer service to procedure mapping shall apply. Table 11: DLC service to procedure mapping Service Procedure Reference Status PT FT ULE1-D.1 LU14 Enhanced Frame RELay service with CCM (EFREL- CCM) 5.1.3 M M LU14 Enhanced Frame RELay service with CCM (EFREL-CCM) 11.1 M M ULE1-D.2 LU13 Enhanced Frame RE... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.7 NWK layer | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.7.1 General | The NWK layer provisions shall include the following entities: • Call Control (CC). • Mobility Management (MM). • Link Control Entity (LCE). • ConnectionLess Message Service (CLMS). DECT ULE phase 1 requires a NWK layer. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.7.2 NWK features | DECT Ultra Low Energy, phase 1 devices shall support the following NWK layer features. Table 12: NWK features status Feature supported Features Status Item no. Name of feature Reference PT FT ULE1-N.1 ULE phase 1 NWK control 5.1.4 M M ULE1-N.2 ULE Service Call 5.1.4 M M ULE1-N.3 Authentication of PP 5.1.4 M M ULE1-N.4 ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.7.3 NWK features to procedures mapping | The following NWK layer feature to procedure mapping shall apply. Table 13: NWK feature to procedure mapping Feature/Procedure mapping Status Feature Procedure Reference PT FT R/B ULE1-N.1 ULE phase 1 NWK control 5.1.4 M M General pre-requisites 12.1.1 M M Creation of the ULE PVC and states 12.1.2 M M Allowed CC Operat... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.8 Application Layer | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.8.1 Application features | DECT Ultra Low Energy, phase 1 devices shall support the following application features. Table 14: Application features status Feature supported Status Item no. Name of feature Reference PT FT ULE1.A.1 AC to bitstring mapping 5.1.5 M M ULE1.A.2 Multiple subscription registration 5.1.5 O N/A ULE1.A.3 Easy PIN code regis... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.8.2 Application features to procedures mapping | The following Application layer feature to procedure mapping shall apply. Table 15: Application feature to procedure mapping Feature/Procedure mapping Status Feature Procedure Ref. PT FT AC to bitstring mapping [ULE1.A.1] M M AC to bitstring mapping 14.2 [9] M M Multiple subscription registration [ULE1.A.2] O N/A Subsc... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.9 Distributed communications | The distributed communication mode (PP-PP communication) is not part of the present document. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.10 Management Entity (ME) | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.10.1 Management Entity (ME) services | In regard to ULE phase 1 equipment, the following ME services shall apply. Table 16: Management Entity Requirements Feature supported Status Feature Name of feature Ref. PT FT ULE1-ME.1 ULE phase 1 Management 5.1.6 M M ULE1-ME.2 ULE Physical Channel Selection 5.1.6 M M NOTE: The reference column refers to the relevant ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.10.2 Management Entity (ME) mode to procedures mapping | In regard to ULE phase 1 equipment, the following ME service to procedure mapping shall apply. Table 17: Management Entity mode to procedures mapping Feature/Procedure mapping Status Service Procedure Reference PT FT ULE phase 1 Management [ULE1-ME.1] 5.1.6 M M ULE phase 1 connection and resources management 9.1.1 M M ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.11 U-plane services and interworking requirements | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.11.1 U-plane and interworking services | DECT Ultra Low Energy, phase 1 devices shall support the following U-plane and interworking services. Table 18: U-plane services and interworking Item Name of service Reference Support status PT FT ULE1-I.1 Transparent U-plane Interworking 5.1.7 M M NOTE: The reference column refers to the relevant clause in the presen... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 6.11.2 U-plane and interworking service to procedure mapping | The following U-plane and interworking service to procedure mapping shall apply. Table 19: U-plane and interworking service to procedure mapping Service Procedure Reference Status PT FT ULE1-I.1 Transparent U-plane Interworking 5.1.2 M M U-plane procedures B.2.1 M M C-plane procedures B.2.2 M M Transport of IWU-to-IWU ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 7 Profile specific procedures description | All profile specific procedures are described in clauses 8 to 13 of the present document, organized by layers. This clause may be used for the definition of general profile specific procedures or general requirements in further releases of the present document. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8 Physical Layer (PHL) procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.1 Supported Modulation types and schemes | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.1.1 GFSK modulation | All equipment compliant with the present document shall support GFSK modulation, as defined by EN 300 175-2 [2], clause 5.4. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.1.2 Modulation scheme 1a | All equipment compliant with the present document shall support the modulation scheme configuration 1a, as defined by EN 300 175-2 [2], clause 5.4 and table D.1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.2 Supported Physical Packets | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.2.1 Physical Packet P32 | All equipment compliant with the present document shall support the Physical Packet P32, as defined by EN 300 175-2 [2], clause 4.4.2. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.2.2 Use of Physical Packet P32 | All equipment compliant with the present document shall use the Physical Packet P32 for all ULE connection oriented services transmissions, except within the exceptions listed in clause 8.2.4, where Packet P00 may be also used. NOTE 1: Equipment compliant with the present document may also implement other DECT applicat... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.2.3 Physical Packet P00 | All equipment compliant with the present document shall support the reception and may support the transmission of Physical Packet P00, as defined by EN 300 175-2 [2], clause 4.4.1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.2.4 Transmission and use of Physical Packet P00 | All equipment compliant with the present document may optionally use the Physical Packet P00 for transmission of connection oriented service packets with empty B fields in the specific cases described in clause 10.11.2.2 of the present document "Use of short slots for packets containing "no B-field". All equipment comp... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.2.5 Reception of Physical Packet P00 | All equipment compliant with the present document shall support the reception of Physical Packet P00 for connection oriented service packets with empty B fields in the specific cases described in clause 10.11.2.2 of the present document "Use of short slots in C/O bearers". |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3 General PHL procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.1 General radio requirements | As specified in EN 300 175-2 [2] and EN 301 406 [11] (replacing TBR 006 [i.2]). |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.2 Radio receiver sensitivity | The radio receiver sensitivity shall be -86 dBm, or better. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.3 Z-field | The Z-field shall be transmitted by RFPs and PTs. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.4 Sliding collision detection | PT and FT shall be able to detect sliding collision on received packets. Minimum criteria for sliding collision are defined as S- or Z-field failure. Early sliding collision detection may be supported by other means e.g. signal strength measurements in the guard band. The Z-field is defined to have failed if the receiv... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.5 Physical channel availability | A FP shall be able to receive and transmit on all DECT frequencies f0 to f9 and at least half of the slot pairs 0 to 11. A PP shall be able to receive and transmit on all DECT frequencies f0 to f9, and shall be able to lock on any slot number 0 to 11, and receive and transmit at least on every slot pair that is not dir... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.6 Synchronization window | Related to its reference timer, the PP synchronization window shall be at least ±4 bits for bearers to the RFP to which the reference timer is synchronized, and at least ±10 bits for other bearers. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.7 Minimum Normal Transmit Power (NTP) | The nominal NTP shall be greater than 80 mW per simultaneously active transmitter as shown by the test verdict criteria and declaration of EN 300 176-1 [10], clause 10.2.3. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.8 Power management | To fight mutual interference between data terminals operating in different local DECT networks when using for the transmission most of the slots from a frame, control of the transmission power is recommended. If transmission power control procedure is implemented, the requirements in EN 300 175-2 [2], annex E shall ful... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 8.3.9 Fast hopping radio | The radio transceiver shall be able to perform any frequency change during the interval between two consecutive Physical Packets P32 (full slot). |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9 Management Entity (ME) procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.1 ULE phase 1 Management | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.1.1 ULE phase 1 connection and resources management | The management entity rules for the present document are based on the following elements: • Simplified Network Layer CC model based on PVC (Permanent Virtual Circuit) controllable by means of Service Change operations, as described in feature [ULE1-N.1] ULE phase 1 NWK control. • Use of two mechanisms of Suspend and Re... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.1.2 Stay alive procedure | ULE phase 1 may use a stay alive procedure, to control the integrity of the connection and the existence of the other peer. No specific stay alive procedure is defined in the present document. Therefore, the design of the stay alive procedure is left to the implementer. The expected response after a failure, or a multi... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2 Channel selection and collision avoidance procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2.1 Overall architecture of ULE channel selection processes | DECT ULE devices shall implement the Physical channel selection procedures as described in EN 300 175-3 [3], clause 11.12. The processes and mechanisms described in EN 300 175-3 [3], clause 11.12.2 shall be implemented. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2.2 Process M0 (RFP side pre-selection process) | DECT ULE RFPs shall implement the process M0 (RFP side pre-selection process) as described in EN 300 175-3 [3], clause 11.12.3. Implementation at PP side shall consist in the understanding of the RFP algorithm. The guidelines given in EN 300 175-3 [3], clause 11.12.3 shall be followed. The following additional provisio... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2.3 Broadcast mechanism | DECT ULE RFPs shall implement and DECT ULE PPs shall understand the broadcast mechanism described in EN 300 175-3 [3], clause 11.12.4. The following additional provisions shall apply: • The value of m, the time difference between frame that carries the broadcast and the access frame for which the channel selection info... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2.4 Process M1 (PP side channel selection process) | DECT ULE PPs shall implement the process M1 (PP side channel selection process) as described in EN 300 175-3 [3], clause 11.12.5. Implementation at RFP side shall consist in the understanding of the PP setup process. The following additional provisions and notes shall apply: • For PPs without power consumption limitati... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2.5 Setup attempt and evaluation of responses | PPs shall perform the access request and evaluation or responses as defined in EN 300 175-3 [3], clause 11.12.6. Implementation at RFP side shall consist in the understanding of the PP response. The following additional provisions shall apply: • The differentiation of error responses compatible and not compatible with ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 9.2.6 Process M2 (collision handling/collision avoidance process) | DECT ULE PPs shall implement the process M2 (PP side collision handling/collision avoidance process) as described in EN 300 175-3 [3], clause 11.12.7. Implementation at RFP side shall consist in the understanding of the PP response under potential collision conditions. The following additional provisions and notes shal... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10 MAC layer procedures | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1 General | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.1 Frame and multiframe structure | The FT and PT shall support frame and multiframe structures as defined in EN 300 175-3 [3], clause 4.2. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.2 Bit mappings | The FT and PT shall support the D-field mappings as defined in EN 300 175-3 [3], clause 6.2.1.1 for full slot, Physical Packet P32, GFSK modulation and modulation schema 1a (clause 6.4.1, table 5 and clause 6.4.2 table 6). The FT and PT shall support the D-field mappings as defined in EN 300 175-3 [3], clause 6.2.1.1 f... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.3 E/U mux modes and B-field identification (BA) bits | NOTE: See also clause 10.2.2 for detailed provisions regarding the E/U multiplexer modes. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.3.1 E/U mux modes and B-field identification (BA) bits for C/O bearers | The FT and PT shall support the following E/U mux modes and associated B-field identifications (BA bits a4, a5 and a6) as defined in EN 300 175-3 [3], clause 7.1.4 for traffic C/O bearers: • BA = "000"B: U-type, IP packet number 0; • BA = "001"B: U-type, IP packet number 1; • BA = "111"B: no B-field, (shall only be use... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.3.2 E/U mux modes and B-field identification (BA) bits for C/L (dummy) bearers | The FT and PT shall support the following E/U mux modes and associated B-field identifications (BA bits a4, a5 and a6) as defined in EN 300 175-3 [3], clause 7.1.4 for dummy C/L bearers: • BA = "110"B: E-type, all MAC control. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.4 Scrambling | The FT and PT shall support scrambling as defined in EN 300 175-3 [3], clause 6.2.4. The dummy C/L bearer containing the special B-field ULE dummy structure shall not be scrambled. The previous provision applies even if there are several ULE dummy bearers. Other C/L bearers not containing the special B-field ULE dummy ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.5 Error control | The FT and PT shall support R-CRC and X-CRC generation as defined in EN 300 175-3 [3], clause 6.2.5. FT and PT shall support 16-Bit R-CRC as defined in EN 300 175-3 [3], clause 6.2.5.2. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.6 RFP idle receiver scan sequence | The FT shall support primary scan as defined in EN 300 175-3 [3], clause 11.8. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.1.7 Identities | The provisions of EN 300 175-3 [3], clause 11.7 and EN 300 175-6 [6] shall be implemented with respect to the structure and use of identities. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2 Time multiplexers | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.1 A-field Multiplexer | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.1.1 Tail Multiplexer (T-MUX) | The FT and PT shall support T-MUX as defined in EN 300 175-3 [3], clause 6.2.2.1. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 57 |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.1.2 A-tail identifications | The FT and PT shall understand all A-field tail identifications (bits a0 to a2) as defined in EN 300 175-3 [3], clause 7.1.2. The value 101 - "escape" need not be understood. To distinguish a connectionless bearer from a non-connectionless bearer the NT message send on a connectionless bearer shall carry the value "Ide... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2 B-field control Multiplexer (E/U-MUX) | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1 B-field control Multiplexer (E/U-MUX), basic modes | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1.1 U-type Multiplexer for C/O bearers | The FT and PT shall support the following U-type multiplexer modes as defined in EN 300 175-3 [3], clause 6.2.2.2 for traffic C/O bearers: • BA = "000"B: U-type, IP packet number 0; • BA = "001"B: U-type, IP packet number 1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1.2 E-type Multiplexer "all MAC control" for C/O bearers | The FT and PT shall support the following E-type multiplexer mode as defined in EN 300 175-3 [3], clauses 6.2.2.2 and 6.2.2.3: • BA = "110"B: E-type, all MAC control. The following restrictions apply: • Channel GF does not need to be supported. • MAC control messages for controlling channel IPF do not need to be suppor... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1.3 E-type Multiplexer "no-B field" for C/O bearers | The FT and PT shall support the following E-type multiplexer mode as defined in EN 300 175-3 [3], clauses 6.2.2.2 and 6.2.2.3: • BA = "111"B: no B-field NOTE: This BA code and mux mode should only be used over C/O bearers. In general, the BA coding and multiplexer mode "no-B field" shall be understood as transmission o... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1.4 E-type Multiplexer "all MAC control" for C/L (dummy) bearers | The FT and PT shall support the following E-type multiplexer mode as defined in EN 300 175-3 [3], clauses 6.2.2.2 and 6.2.2.3, over dummy C/L bearers: • BA = "110"B: E-type, all MAC control. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 58 The following restrictions apply: • The repertory of possible MAC control messages is ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1.5 E/U-Mux priority schema | The FT and PT shall support the priority schema as defined in EN 300 175-3 [3], clause 6.2.2.4 with the following restrictions: • IPF channel modes and IPF segmentation control are not applicable. • CF channel modes are not applicable. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.1.6 B-field identifications (basic) | The FT and PT shall use and understand all B-field identifications (bits a4 to a6) as defined in EN 300 175-3 [3], clause 7.1.4 with the following restrictions: • Codes for E-mux with CF channel ("010", "011", 100" and "101") are not applicable. • Code "110" is only understood as "E-type all MAC control". • Code "111" ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.2 B-field control Multiplexer (E/U-MUX), CF modes | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.2.1 E-type Multiplexer, all modes (over C/O bearers) | The FT and PT shall support E-type mode multiplexer as defined in EN 300 175-3 [3], clauses 6.2.2.2 and 6.2.2.3, including the modes "E-type all CF", and "E-type not all CF" over traffic C/O bearers. The FT and PT shall support all E-type modes as defined in EN 300 175-3 [3], clause 6.2.2.3 (tables 6.24 to 6.33) for th... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.2.2 E/U-Mux priority schema | The FT and PT shall support the priority schema as defined in EN 300 175-3 [3], clause 6.2.2.4 with the following restriction: • IPF channel modes and IPF segmentation control are not applicable. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.2.2.2.3 B-field identifications (CF) | The FT and PT shall use and understand all B-field identifications (bits a4 to a6) as defined in EN 300 175-3 [3], clause 7.1.4 with the following restrictions: • Code "110" is only understood as "E-type all MAC control". • Code "111" is only understood as "no B-field". |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3 Downlink broadcast (A-field) | The procedure shall be performed as defined in EN 300 444 (GAP) [9], clause 10.2 and EN 300 175-3 [3], clause 9.1.1. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.1 NT messages | The same message defined in EN 300 444 (GAP) [9], clause 10.2.1 shall be used. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2 QT messages | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.1 QT - static system information | The FT shall be capable of sending and the PT shall be capable of receiving and processing the QT static system information message as defined in EN 300 175-3 [3], clause 7.2.3.2, with the following contents as defined below. The same contents defined in EN 300 444 (GAP) [9], clause 10.2.3 shall be supported. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.2 QT - FP capabilities | |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.2.1 Standard FP Capabilities | The FP shall indicate its standard capabilities using the fixed part capabilities QT message as described in EN 300 175-3 [3], clause 7.2.3.4, with contents as defined below. The PT shall be able to receive and understand this message. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 60 Table 20: Values used within Standard FP ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.2.2 Extended FP Capabilities | The FP shall indicate its extended capabilities using the Extended fixed part capabilities QT message as described in EN 300 175-3 [3], clause 7.2.3.5, with contents as defined below. The PT shall be able to receive and understand this message. Table 21: Values used within Extended FP capabilities MAC message Field wit... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.2.3 Extended FP Capabilities part 2 | The use of Extended FP Capabilities part 2 is needed in all cases due to the position of the bit <a39> in the Extended higher layer capabilities broadcast, which defines the support of ULE phase 1 (see clause 12.3.2.1.3). All bits in the MAC layer part of the broadcast are optional and will be set to describe the suppo... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.3 QT - SARI list contents | The FT may send and the PT shall be capable of receiving and processing (if broadcast by the FT) the QT SARI message as defined in EN 300 175-3 [3], clause 7.2.3.6, with same contents as defined by EN 300 444 (GAP) [9], clause 10.2.4. This is relevant if the NT message indicates SARI support. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.2.4 Multiframe number (A-field) | QT message carries the multiframe number which is used in the encryption algorithm. Both, FT and PT, shall be able to transmit and respectively retrieve the information carried in this message. Table 23: Values used within QT multiframe number message MAC message Field within the message Standard values within the MAC ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.3.3 Reception of downlink broadcast (A-field) | DECT ULE PPs are not required to listen to downlink broadcast channels (over A-field) in all states. They will listen to these channels only in specific situations. The following channels are considered downlink broadcasts for this description: • NT : Identities Information ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 62 • ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4 Paging broadcast | This clause refers to the LCE paging capability using A-field messages. Refer to clause 10.6 for ULE paging using B- field channels. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.1 Paging message formats | The FT and PT shall support full, short and zero length paging message formats as defined in EN 300 175-3 [3], clause 7.2.4. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.1.1 Full page message format | Table 24: Values used within full-page message format MAC message Field within the message Standard values within the MAC message Normative action/comment << PT full page format >> < PT-header extend flag > (a8) 0,1 a8 = 1 means another page message shall start in the next frame in this multiframe that is permitted to ... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.1.2 Short page message format | The same values defined in EN 300 444 GAP) [9], clause 10.3.1 shall be supported. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.1.3 Zero length page message format | The same values defined in EN 300 444 GAP) [9], clause 10.3.2 shall be supported. ETSI ETSI TS 102 939-1 V1.1.1 (2013-04) 63 |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.1.4 MAC layer information in zero and short length paging messages | The following MAC layer information types defined by EN 300 175-3 [3], clause 7.2.4.3 shall be supported (understood) by a PT. Table 25: Types of MAC layer paging information to be supported by a PT a32 a33 a34 a35 MAC information type 0 0 0 1 Blind slot information for circuit mode service. 0 0 1 0 Other bearer. 0 0 1... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.1.4.1 RFP status | RFP Modulation Types status A-field (B + Z)-fields a36 a39 a40 a43 a44 a47 Figure 5: RFP status Table 26: RFP status RFP status Meaning 0xxx RFP clear for data. 1xxx RFP busy for data (see note). NOTE: "RFP busy for data" means that the RFP recommends PTs not to send access request messages for ULE service towards this... |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2 MAC layer information messages procedures | The following MAC layer information message procedures are defined as described below. Each supported message shall be broadcasted at least once every 10 s. In regard to the support status of the different codes, the provisions of EN 300 444 [9], clause 10.3.1 shall apply. |
01d4cead4603302c51d644c860b8516f | 102 939-1 | 10.4.2.1 Blind slot information for circuit mode service | The provisions of EN 300 444 (GAP) [9], clause 10.3.3 shall apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.