hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.4.1 Physical layer (PHL) services | ULE Phase 2 devices shall support the PHL layer services described by Table 3. Table 3: Physical layer service support Item Name of service Reference Support status PT FT ULE1-P.1 GFSK modulation 5.1.1 [12] M M ULE1-P.2 Physical Packet P32 5.1.1 [12] M M ULE1-P.3 Physical Packet P00 5.1.1 [12] M M ULE1-P.4 General PHL ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.4.2 Modulation schemes | The modulation schemes described by Table 4 and defined by ETSI EN 300 175-2 [2], annex D shall be supported. Table 4: Allowed combinations of modulation schemes Modulation scheme S-field A-field B + Z-field Support status 1a GFSK GFSK GFSK M ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 26 |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.4.3 PHL service to procedure mapping | Those PHL layer services that are defined in clause 6.4.1 shall have identical procedure mapping to that defined in their referenced documents. Table 5: PHL service to procedure mapping Service Procedure Reference Status PT FT This table is intentionally left blank in order to facilitate future modification. NOTE: The ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.5 MAC layer requirements | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.5.1 MAC layer services | ULE Phase 2 devices shall support the MAC layer services described by Table 6. Table 6: MAC service support Item Name of service Reference Support status PT FT ULE1-M.1 General 5.1.2 [12] M M ULE1-M.2 A-field Continuous broadcast 5.1.2 [12] M M ULE1-M.3 A-field Paging broadcast 5.1.2 [12] M M ULE1-M.4 B-field Continuou... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.5.2 MAC service to procedure mapping | The MAC layer service to procedure mapping described by Table 7 shall apply. In addition, those MAC layer services that are defined in clause 6.5.1 that do not have explicit procedure mapping described by Table 7, shall have identical procedure mapping to that defined in their referenced documents. ETSI ETSI TS 102 939... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.6 DLC layer | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.6.1 DLC layer services | ULE Phase 2 devices shall support the DLC services described by Table 8. Table 8: DLC service status Item no. Name of service Reference Status PT FT ULE1-D.1 LU14 Enhanced Frame RELay service with CCM (EFREL-CCM) 5.1.3 [12] M M ULE1-D.2 LU13 Enhanced Frame RELay service with CRC (EFREL-CRC) 5.1.3 [12] O O ULE1-D.3 LU10... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.6.2 DLC service to procedure mapping | The DLC layer service to procedure mapping described by Table 9 shall apply. In addition, those DLC layer services that are defined in clause 6.6.1 that do not have explicit procedure mapping described by Table 9, shall have identical procedure mapping to that defined in their referenced documents. Table 9: DLC service... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.7 NWK layer | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 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). |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.7.2 NWK features | ULE Phase 2 devices shall support the NWK layer features described by Table 10. Table 10: NWK features status Feature supported Features Status Item no. Name of feature Reference PT FT ULE1-N.1 ULE NWK control 5.1.4 [12] M M ULE1-N.2 ULE Service Call 5.1.4 [12] M M ULE1-N.3 Authentication of PP 5.1.4 [12] M M ULE1-N.4 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.7.3 NWK features to procedures mapping | The NWK layer feature to procedure mapping described by Table 11 shall apply. In addition, those NWK layer features that are defined in clause 6.7.2 that do not have explicit procedure mapping described by Table 11, shall have identical procedure mapping to that defined in their referenced documents. ETSI ETSI TS 102 9... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.8 Application Layer | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.8.1 Application features | ULE Phase 2 devices shall support the application features described by Table 12. Table 12: Application features status Feature supported Status Item no. Name of feature Reference PT FT ULE1.A.1 AC to bitstring mapping 5.1.5 [12] M M ULE1.A.2 Multiple subscription registration 5.1.5 [12] O N/A ULE1.A.3 Easy pairing reg... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.8.2 Application features to procedures mapping | The Application layer feature to procedure mapping described by Table 13 shall apply. In addition, those Application layer features that are defined in clause 6.8.1 that do not have explicit procedure mapping described by Table 13, shall have identical procedure mapping to that defined in their referenced documents. ET... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.9 Distributed communications | This is not applicable. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.10 Management Entity (ME) | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.10.1 Management Entity (ME) services | ULE Phase 2 devices shall support the ME services described by Table 14. Table 14: Management Entity Requirements Feature supported Status Feature Name of feature Reference PT FT ULE1-ME.1 ULE phase 1 Management 5.1.6 [12] M M ULE1-ME.2 ULE Physical Channel Selection 5.1.6 [12] C1401 C1401 ULE1-ME.3 ULE Physical Channe... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.10.2 Management Entity (ME) mode to procedures mapping | The ME service to procedure mapping described by Table 15 shall apply. In addition, those Management Entity services that are defined in clause 6.10.1 that do not have explicit procedure mapping described by Table 15, shall have identical procedure mapping to that defined in their referenced documents. ETSI ETSI TS 102... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.11 U-plane services and interworking requirements | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.11.1 U-plane and interworking services | ULE Phase 2 devices shall support the U-plane and interworking services described by Table 16. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 38 Table 16: U-plane services and interworking Item Name of service Reference Support status PT FT ULE1-I.1 Transparent U-plane Interworking 5.1.7 [12] M M ULE1-I.2 Configuration and co... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.11.2 U-plane and interworking service to procedure mapping | The U-plane and interworking service to procedure mapping described by Table 17 shall apply. In addition, those U-plane and interworking services that are defined in clause 6.11.1 that do not have explicit procedure mapping described by Table 17, shall have identical procedure mapping to that defined in their reference... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.12 Speech Services | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.12.1 Speech Services features | ULE Phase 2 devices shall support the speech service features described by Table 18. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 39 Table 18: Speech services features Feature supported Status Feature Name of feature Reference PT FT NG1.1 Narrow band ADPCM G.726 [i.2] 32 kbit/s voice service 5.1 [11] C1801 M NG1.2 Narrow ba... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.12.2 Speech Services to procedures mapping | Those U-plane and interworking services that are defined in clause 6.12.1 shall have identical procedure mapping to that defined in their referenced documents. Table 19: Speech service feature to procedure mapping Feature/Procedure mapping Status Feature Procedure Reference PT FT This table is intentionally left blank ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.13 General class/service/interworking support | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.13.1 Class/service support | The service classes and end-user services described by Table 20 shall apply. Table 20: General class and service support Item Name of service Reference Support status PT FT DPRS-G.1 DPRS Class 1 4.3.8 [16] I I DPRS-G.2 DPRS Class 2 4.3.8 [16] C1802 O DPRS-G.3 Frame Relay (FREL) 4.3.9 [16] and annex B [16] C1801 M DPRS-... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 6.13.2 Protocol interworking support | The protocol interworking modes described by Table 21 shall apply. Table 21: General service/interworking support Service Interworking Reference Status PT FT DPRS-G.3, Frame Relay (FREL) 4.3.9 [16] and annex B [16] C1901 M DPRS-I.1, Ethernet 4.3.9 [16] and B.4 [16] I I DPRS-I.2, Token Ring 4.3.9 [16] and B.5 [16] I I D... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 7 Profile specific procedures description | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 7.0 General | In addition to the general requirements and procedures defined in clause 7, further profile specific procedures are described in clause 8 to clause 14 of the present document (organized by protocol layers). |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 7.1 Back compatibility with ULE Phase 1 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 7.1.0 General | A ULE Phase 2 PP may determine what type of FP it is attached to by the use the Extended Fixed Part Capabilities (Part 2) message (see clause 10.2.2.2.3). A ULE Phase 2 FP may determine what type(s) of PP(s) are registered to it by the use of the Terminal Capabilities (see clause 12.2.1). NOTE: ULE Phase 1 FPs and PPs ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 7.1.1 Back compatibility with a ULE Phase 1 Fixed Part (FP) | In the absence of any specific back-compatibility rules defined in the present document, the PP shall inter-operate with a ULE Phase 1 FP using those procedures defined in ETSI TS 102 939-1 [12]. The PP shall not attempt to use procedures or features that are not supported by the ULE Phase 1 FP. ETSI ETSI TS 102 939-2 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 7.1.2 Back compatibility with a ULE Phase 1 Portable Part (PP) | In the absence of any specific back-compatibility rules defined in the present document, the FP shall inter-operate with a ULE Phase 1 PP using those procedures defined in ETSI TS 102 939-1 [12]. The FP shall not attempt to use procedures or features that are not supported by the ULE Phase 1 PP. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 8 Physical Layer (PHL) procedures | There are currently no new PHL layer procedures specifically defined for ULE Phase 2. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9 Management Entity (ME) procedures | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.1 ULE phase 1 Management | The provisions of ETSI TS 102 939-1 [12], clause 9.1 shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.2 Channel selection and collision avoidance procedures | The provisions of ETSI TS 102 939-1 [12], clause 9.2 shall apply. 9.3 Channel selection and collision avoidance procedures for US region |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.0 General | In addition to the clause 9.3, the provisions of ETSI TS 102 497 [14] shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.1 Overall architecture of ULE channel selection processes | DECT ULE devices shall implement the Physical channel selection procedures as described in ETSI EN 300 175-3 [3], clause 11.12. The processes and mechanisms described in ETSI EN 300 175-3 [3], clause 11.12.2 shall be implemented. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.2 Process M0 (RFP side pre-selection process) | DECT ULE RFPs shall implement the process M0 (RFP side pre-selection process) as described in ETSI EN 300 175-3 [3], clause 11.12.3. Implementation at PP side shall consist in the understanding of the RFP algorithm. The provisions given in ETSI EN 300 175-3 [3], clause 11.12.3 shall be followed. The following additiona... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.3 Broadcast mechanism | DECT ULE RFPs shall implement and DECT ULE PPs shall understand the broadcast mechanism described in ETSI 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... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.4 Process M1 (PP side channel selection process) | If the FP does not indicate any channels with RSSI of -84 dBm or less, then the PP shall perform its own Least Interfered Channel (LIC) scan, in accordance with the requirements for the US (ETSI TS 102 497 [14]). If, during the process of the performing the LIC scan, the PP detects channel(s) with RSSI of -84 dBm or le... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.5 Setup attempt and evaluation of responses | PPs shall perform the access request and evaluation or responses as defined in ETSI 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 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.3.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 ETSI EN 300 175-3 [3], clause 11.12.7. The input to process M2 shall be either the output of the PP's LIC scan, or the list of quiet channels (i.e. those less than -84 dBm) as indicated by the FP or disc... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.0 General | In addition to clause 9.4, the provisions of ARIB standard STD-T101 [15] shall also apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.1 Overall architecture of ULE channel selection processes | DECT ULE devices shall implement the Physical channel selection procedures as described in ETSI EN 300 175-3 [3], clause 11.12. The processes and mechanisms described in ETSI EN 300 175-3 [3], clause 11.12.2 shall be implemented. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 44 |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.2 Process M0 (RFP side pre-selection process) | DECT ULE RFPs shall implement the process M0 (RFP side pre-selection process) as described in ETSI 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 ETSI EN 300 175-3 [3], clause 11.12.3 shall be followed. The following additiona... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.3 Broadcast mechanism | DECT ULE RFPs shall implement and DECT ULE PPs shall understand the broadcast mechanism described in ETSI 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... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.4 Process M1 (PP side channel selection process) | DECT ULE PPs shall implement the process M1 (PP side channel selection process) as described in ETSI EN 300 175-3 [3], clause 11.12.5. Implementation at RFP side shall consist in the understanding of the PP setup process. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 45 The following additional provisions shall apply: • For ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.5 Setup attempt and evaluation of responses | PPs shall perform the access request and evaluation or responses as defined in ETSI 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 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 9.4.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 ETSI 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 shall app... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10 MAC layer procedures | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.1 Radio Control Bits | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.1.1 Quiet Channel Indication | If the FP's M0 process detects that there are channels with RSSI of less than -84 dBm, then it may do the following: • set the "RFC1" bit (bit 172) of the dummy bearer's subfield 2 (see ETSI EN 300 175-3 [3], clause 9.5.1.3); and • use the MU broadcast to indicate those channels that have RSSI of less than -84 dBm. ETS... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.1.2 PHS Detection Indication | Systems operating in Japan have specific requirements for detecting and avoiding PHS systems. The procedure for detecting PHS systems is outside the scope of the present document. The specific requirements are described in ARIB standard STD-T101 [15]. In addition to the provisions of STD-T101 [15], the following shall ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2 Downlink broadcast (A-field) | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.0 General | The procedure shall be performed as defined in ETSI EN 300 444 (GAP) [9], clause 10.2 and ETSI EN 300 175-3 [3], clause 9.1.1. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.1 NT messages | The same message defined in ETSI EN 300 444 (GAP) [9], clause 10.2.1 shall be used. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.2 QT messages | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.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 ETSI EN 300 175-3 [3], clause 7.2.3.2. The same contents defined in ETSI EN 300 444 (GAP) [9], clause 10.2.3 shall be supported. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 47 |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.2.2 QT - FP capabilities | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.2.2.1 Standard FP Capabilities | The FP shall indicate its standard capabilities using the fixed part capabilities QT message as described in ETSI EN 300 175-3 [3], clause 7.2.3.4, with contents as defined in Table 22. The PT shall be able to receive and understand this message. Table 22: Values used within Standard FP capabilities MAC message Field w... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.2.2.2 Extended FP Capabilities | The FP shall indicate its extended capabilities using the Extended fixed part capabilities QT message as described in ETSI EN 300 175-3 [3], clause 7.2.3.5, with contents as defined in Table 23. The PT shall be able to receive and understand this message. Table 23: Values used within Extended FP capabilities MAC messag... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.2.2.2.3 Extended FP Capabilities part 2 | The FP shall indicate its extended capabilities using the Extended fixed part capabilities part 2 QT message as described in ETSI EN 300 175-3 [3], clause 7.2.3.11, with contents as defined in Table 24. The PT shall be able to receive and understand this message. Table 24: Values used within Extended FP capabilities pa... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3 Slot types and slot use | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.1 Full Slot | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.1.1 General | The D-field mapping for the full slot structure (physical packet P32), as defined by ETSI EN 300 175-3 [3], clause 6.2.1.1.2 shall be supported. The B-field mapping for the full slot structure (physical packet P32), as defined by ETSI EN 300 175-3 [3], clause 6.2.1.3.1.2 shall be supported. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.1.2 Use of full slot in C/O bearers | Full slot shall be used for C/O bearers, unless another slot type is explicitly requested (e.g. using Advanced Connection control procedures). Additionally, a short slot may also be used in some cases, see clause 10.3.2.2. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.1.3 Use of full slot in C/L dummy bearers | Full slot shall be used in the dummy C/L bearers in all cases. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 49 |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.2 Short Slot | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.2.1 General | The D-field mapping for the short slot structure (physical packet P00), as defined by ETSI EN 300 175-3 [3], clause 6.2.1.1.3 shall be supported in both PT and FT, at least in receiving mode. Use (transmission) of the slot is optional at both sides. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.2.2 Use of short slot in C/O bearers | In order to further save energy, it is allowed to transmit as short slots frames that do not carry any B-field (BA code = no B-field) in certain cases. The use of short slots is optional at sending side (transmitter choice). However, its understanding by the receiving side is mandatory. For expedited connections the ru... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.3 Long Slot | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.3.1 General | The D-field mapping for the long slot structure (physical packet P64), as defined by ETSI EN 300 175-3 [3], clause 6.2.1.1.4 shall be supported. The B-field mapping for the long slot structure (physical packet P64), as defined by ETSI EN 300 175-3 [3], clause 6.2.1.3.1.3 shall be supported. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.3.3.2 Use of long slot in C/O bearers | The use of long slot for C/O bearers is required for some services (e.g. wideband voice). It requires the Advanced Connection control procedures, as defined by ETSI EN 300 175-3 [3], clause 10. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.4 No-emission legacy mode procedures | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.4.1 General | "No-emissions" mode is not directly compatible with ULE Phase 2. This is for a number of reasons, for example: • The high power consumption required for "NEMo scanning". • The additional latency required for "NEMo wakeup". • Features such as "ULE paging", including ConnectionLess Downlink broadcast will not work effect... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5 U-plane C/L downlink services | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.0 General | DECT ULE phase 2 supports C/L U-plane downlink transmission by means of the logical channel SIP and the procedures described in ETSI EN 300 175-3 [3], clause 9.1.4. Only multicast unacknowledged service is supported. Transmission may be done over the ULE dummy bearer or over additional C/L bearers. Multiple instances o... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.1 U-plane C/L downlink multicast unacknowledged service | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.1.0 General | This service allows the transmission in unacknowledged mode of U-plane packets addressed to previously configured groups of PT (multicast groups). The service allows the simultaneous sending of messages to multiple devices and is intended for applications that require synchronized actions in multiple PTs. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.1.1 Logical channels and instance separation | Multiple instances of the service may exist. Each instance corresponds to a separate SIP channel accessible by the DLC by separate SAPs. Separate DLC LU and IWU instances shall also be used towards the application, which may access the service by means of separate SAPs. The application decides which messages are routed... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.1.2 Addressing and management of multicast groups | The addressing system is based on the "X" and "Y" identities described in ETSI EN 300 175-3 [3], clause 9.1.4.7 and is entirely managed by the RFP ME. The RFP ME shall decide the composition of the multicast groups, shall keep the list of subscribed PTs, shall allocate the unique global identity of the group (identity ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.1.3 Procedure | The provisions given in ETSI EN 300 175-3 [3], clause 9.1.4.3 (Announcement via the BU paging channel), clause 9.1.4.4 (Routing and instance separation), clause 9.1.4.5 (Additional attributes), clause 9.1.4.6 (Encryption), clause 9.1.4.7.2 (C/L downlink multicast service) and clause 9.1.4.7.3 (Identities in C/L downlin... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.1.4 SIP subfield format | The U-plane packet (SIP channel) shall use single subfield (SIPQ) format. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.2 U-plane C/L downlink over the dummy bearer | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.2.0 General | Downlink multicast U-plane transmission may happen over the same dummy bearer used to carry the ULE B-field dummy channels. In such a case the transmission interrupts the normal transmission of the dummy and causes a waiting cycle impacting most ULE services. In order to restrict the disturbance to normal ULE operation... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.2.1 Multiplexing cycle | As given by ETSI EN 300 175-3 [3], frames 1, 5, 9 and 13 may be used for C/L downlink traffic insertion over the dummy bearer. This is the maximum multiplexing cycle possible for the insertions. Within this range, the FT ME shall decide the real multiplexing cycle in the system, taken into account the expected multicas... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.2.2 Single-burst transmission | Only single burst transmission is supported (see ETSI EN 300 175-3 [3], clause 9.1.4.3). Each segment of C/L downlink transmission shall have an individual announcement via the BU channel. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.2.3 Identification of C/L downlink insertion | Dummy bearer frames carrying an insertion of C/L downlink traffic are identified by means of the BA bits in the A-field hearer. Such frames shall use the "SIP"coding as indicated in ETSI EN 300 175-3 [3], clause 9.1.4.1. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.2.4 Announcement via the BU paging channel and identification of instances | All transmissions of the C/L downlink service over dummy bearers shall be announced by the paging channel BU as indicated by ETSI EN 300 175-3 [3], clause 9.1.4.3. The following additional provisions shall apply: The announcement shall be done by means of the paging signal coded by the descriptor "announcement of multi... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.3 U-plane C/L downlink over additional C/L bearers | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.3.0 General | The Downlink multicast U-plane transmission may happen over additional C/L bearers different from the dummy(ies). In such a case, there is no interruption in the normal transmission of the dummy and no impact in ULE operation. If this procedure is supported by both peers, the RFP may decide to setup at any time an addi... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.3.1 Channel selection and transmission start | The RFP shall follow the channel selection rules for the additional C/L bearer as given in ETSI EN 300 175-3 [3], clause 11.4.3 and clause 9.1.1.2. The RFP may insert the C/L U-plane data directly in the initial setup bearer or wait until a subsequent one (see clause 10.5.3.2). |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.3.2 MAC signalling in the additional C/L downlink bearer | The signalling of the additional C/L downlink bearer shall be as described in ETSI EN 300 175-3 [3], clause 9.1.4.2.1 with the following specific provisions: • Only single-burst transmissions are supported (see clause 10.5.3.3). However, it is allowed to setup the bearer and not send the C/L data in the very first fram... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.3.3 Single-burst transmission | From multicast channel perspective, only single burst transmission is supported (see ETSI EN 300 175-3 [3], clause 9.1.4.3). Each segment of C/L downlink transmission shall have an individual announcement via the BU channel. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 53 However, it is allowed to chain several segments (ea... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.3.4 Announcement via the BU paging channel and identification of instances | All transmissions of the C/L downlink service over additional C/L bearers shall be announced by the paging channel BU as indicated by ETSI EN 300 175-3 [3], clause 9.1.4.3. The following additional provisions shall apply: • The announcement shall be done by means of the paging signal coded by the descriptor "announceme... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.5.4 Repetition of U-plane C/L downlink | This procedure describes a mechanism for repeating C/L downlink U-plane data for the C/L multicast unacknowledged service, which can provide additional robustness to the system, for example in case a PP misses the initial broadcast due to unforeseen circumstances or interference. When submitting an SDU for transmission... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.