hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6 ULE Paging Procedures (phase 2) | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.0 General | Clause 10.6 refers to ULE specific paging capability using B-Field channels over the ULE dummy bearer. Refer to ETSI TS 102 939-1 [12], clause 10.4 for LCE paging using A-field tail. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.1 PU Paging Message Formats | The provisions of ETSI TS 102 939-1 [12], clause 10.6.1 shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2 Paging Descriptors for ULE Paging | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.1 Basic concepts of the ULE paging system | The concepts defined in ETSI TS 102 939-1 [12], clause 10.6.2.1 shall apply plus the following: Paging ID: A numeric value that combined with a sequence defines a paging signal. Paging IDs are 9-bit numeric values (between 0 and 511). All values may be transmitted using the index format. Values between 0 and 87 may als... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.2 Basic operation of the descriptors | The provisions of ETSI TS 102 939-1 [12], clause 10.6.2.2 shall apply with the following differences. The maximum number of master type descriptors that shall be supported by all FT and PT implementations is TWO. Support of higher number of descriptors is optional. In addition to the master type descriptors, the follow... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.3 Allocation of descriptors | The provisions of ETSI TS 102 939-1 [12], clause 10.6.2.3 shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4 Format for descriptors in ULE phase 1 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.0 General | Clause 10.6.2.4 describes the formats for the descriptors used in the present document. The following formats are used in the present document: • "Format A" that is the same format defined in ETSI TS 102 939-1 [12]. • "Format B" is a new format for slave type descriptors used to carry additional commands such as "setup... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.1 Master/slave types | In order to simplify the design of the descriptors and the handling of sequences the concept of master and slave descriptors is introduced as follows: • A "master type" descriptor is a descriptor which defines a sequence, i.e. it contains information about repetition rate and offset. • Several "master type" descriptors... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.2 CA subscription capability | Refer to ETSI TS 102 939-1 [12], clause 10.6.3 for a description of the CA mechanism. Since a single descriptor has the capability to subscribe a PT to any combination of CA groups (to one, to several or to none), it is not necessary to include the CA subscription capability in all descriptors. Only the "ULE resume" ma... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.3 Format A | "Format A" is the same format used in ULE phase 1 but with some of the spare bits used for signalling. The structure and the description of fields for the "format A", as used in the present document, are as shown in Figure 4. Bit: 8 7 6 5 4 3 2 1 Octet: << ULE-MAC-CONFIGURATION-INFO >> 1 Length of Contents (L) 2 1 Codi... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.4 Format B | "Format B" is used for slave type descriptors carrying the commands "setup voice call full slot", "setup voice call long slot" and "setup SUOTA call". This format uses two octets per descriptor and does not carry CA subscription information. The structure and the description of fields for the "format B", as used in the... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.5 Format C | "Format C" is used for slave type descriptors related to the C/L downlink multicast service. This format uses four octets per descriptor and does not carry CA subscription information. The structure and the description of fields for the "format C", as used in the present document, are as shown in Figure 6. ETSI ETSI TS... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.6 Format D | "Format D" is used for info type descriptors carrying additional information about the paging configuration. This format uses two octets per descriptor. The structure and the description of fields for the "format D", as used in the present document, are as shown in Figure 7. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 59 B... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.4.7 Format E | "Format E" is used for slave type descriptors carrying application specific information. This format has variable length. The structure and the description of fields for the "format E", as used in the present document, are as shown in Figure 8. Bit: 8 7 6 5 4 3 2 1 Octet: << ULE-MAC-CONFIGURATION-INFO >> 1 Length of Co... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.5 Descriptors in ULE phase 2 | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.5.1 Descriptor codes | The following descriptors shall be supported: Channel Descriptor Type and command (octet k): Bits 8 7 6 5 4 3 2 1 Meaning Format type 0 0 1 0 x x x x ULE resume paging "format A" master 1 0 0 0 0 0 0 x Setup voice call full slot "format B" slave 1 0 0 0 0 0 1 x Setup voice call long slot "format B" slave 1 0 0 0 0 1 0 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.5.2 Descriptor detailed descriptions | 10.6.2.5.2.0 General See conventions and definitions in clause 10.6.2.1 of the present document and in clause 10.6.2.1 of ETSI TS 102 939-1 [12]. 10.6.2.5.2.1 ULE resume paging descriptor The same detailed description given in ETSI TS 102 939-1 [12], clause 10.6.2.5.2.1 shall apply. This descriptor is "master type" and... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.5.3 Additional conventions for ULE phase 2 descriptors | 10.6.2.5.3.1 Coding of bit 8 in octet k+4 of format A descriptors The following rule only applies to type A descriptors (master type descriptors): • The bit 8 of last octet (k+4) shall be set to '0' for all type A descriptors present in an IE except for the last one. The bit shall be set to '1' for the last type A desc... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.5.4 Coding of additional C/L bearer position | 10.6.2.5.4.0 General When the signal for "announcement of multicast over additional C/L bearer, unacknowledged" is transmitted, the position of the additional C/L bearer shall be sent in the same bearer of the channel PU that carries the signal, coded in either index 4 or index 10. The coding will also use the first sp... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.2.5.6 Time references for multicast transmissions | 10.6.2.5.6.1 Time reference for transmissions over the dummy The time reference for transmissions over the dummy is the next possible occurrence according to the multiplexing cycle (see clause 10.5.2.1). ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 64 10.6.2.5.6.2 Time reference for the additional C/L bearer position The ti... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.3 CA mask mechanism | The provisions of ETSI TS 102 939-1 [12], clause 10.6.3 shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.4 Paging burst mechanism | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.4.1 General | The paging burst mechanism is used to increase robustness of paging information transmission by repeating the paging information on the ULE dummy bearer in several consecutive frames, so allowing the PT multiple opportunities to receive the same information. The mechanism is enabled by the FT by setting the 'Paging bur... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.4.2 Paging burst and U-plane C/L downlink | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.4.2.1 General | If a paging burst is used to perform a U-plane C/L downlink announcement, then the rules as defined in clauses 10.5.2.4 and 10.5.3.4 shall still apply. However, because the paging information is sent in multiple frames, this has some impact on the corresponding multicast transmission. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.4.2.2 U-plane C/L downlink over the dummy bearer | As defined in clause 10.5.2.4, the U-plane C/L downlink data transmission shall follow in the next possible frame after the announcement. If a paging burst is used for the announcement, this can result in more than one transmission of the U-plane data being performed. For example, for a burst length Nburst of 4 frames,... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.6.4.2.3 U-plane C/L downlink over additional C/L bearers | As defined in clause 10.5.3.4, the U-plane C/L downlink data transmission shall follow in the next frame after the announcement. This results in the U-plane C/L downlink being repeated in the same number of frames as the paging burst. An example for a burst length Nburst of 4 frames is shown in Figure 10. t Frame 1 Pag... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7 Repeater compatibility procedures | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.1 General | The range of DECT is very good compared to most other low power wireless systems. However, there are occasions when the range needs to be extended. This is normally achieved by the use of a repeater (more correctly referred to as a Wireless Relay Station). The existing DECT Wireless Relay Station standard (ETSI EN 300 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.2 Identification of a WRS | The WRS Hop Number (HN) field of the ULE dummy bearer's Subfield 1 indicates the hop distance of a WRS from the "real base" (see ETSI EN 300 175-3 [3], clause 9.5.1.2). ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 66 An RFP that is not a WRS (i.e. the "real base") shall always indicate a hop distance of 0. A WRS will indica... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.3 ULE page delay mechanism | In general, a repeater is not always able to re-transmit information in the same frame that it was received. For example, suppose the repeater's dummy bearer is on slot 2, and the "real base" has its dummy bearer on slot 6 (i.e. after the repeater's), then this repeater could only re-transmit the information in the nex... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.4 Roaming | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.4.1 General | Regular DECT PPs can roam between cells of a multi-cell system. The positions of these RFPs (i.e. the slot and carrier of their dummy bearer or other bearers) are normally found by scanning, either as part of regular background scanning or by a dedicated RFP scan. Roaming is achieved simply by switching the position us... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.4.2 Regular DECT roaming | There are some scenarios where a ULE PP may require regular DECT roaming. For example, when a "circuit mode" connection is active or is required (e.g. for voice calls, ULE service calls, registration procedures, SUOTA, etc.). Details of the RFP scanning algorithm, deciding when to move, deciding where to move to, etc. ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.4.3 ULE roaming | A ULE PP can spend a lot of its time in sleep mode, during which time it is not scanning for RFPs. Usually, it is oblivious to the fact that it has been moved, until it wakes up some time later, e.g. the device went to sleep located near RFP1, and when it awakes it is located near RFP2. In general, assuming that the de... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.7.4.4 ULE bearer replacement (inter-cell) | The PP shall be able to perform inter-cell bearer replacement, by setting up new TBCs within the same logical connection. The following rules apply: • The bearer replacement shall be always implemented by dropping the existing bearer before establishing the new one. • There should not be more than one ULE bearer over t... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.8 Additional requirements for I channel services | 10.8.1 Lifetime management with TWO separate maximum MAC packet lifetimes |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.8.1.0 General | The FT and PT shall operate with TWO separate maximum MAC packet lifetimes, differentiating the maximum lifetime at the bearer (at TBC level) and the maximum lifetime at the MAC layer, as described in ETSI EN 300 175-3 [3], clause 10.8.2.2.1.2 and clause 10.8.2.2.1.3. The detailed provisions given in ETSI EN 300 175-3 ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.8.1.1 Operation of the counters | The overall MAC packet lifetime counter shall be started for the packet with the defined maximum value when it is delivered to the MAC layer for transmission and shall be decreased with absolute TDMA frames (every 10 ms), irrespective of if there is an active TBC or not. In other words, it shall count during suspension... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.1 General | U-NEMo mode allows ULE and No-Emission Mode (NEMo) to operate together. It allows the dummy bearer transmissions to be suspended for NEMo operation without a major impact on ULE operation. U-NEMo mode can be used when all handsets support NEMo and when all ULE devices support U-NEMo. U-NEMo is only possible if all the ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.2 Entering U-NEMo mode | The FT shall control entry to U-NEMo mode. Before entering U-NEMo mode the FP shall have communicated the preferred carrier to the ULE devices. The U-NEMo preferred carrier is the same carrier as the NEMo preferred carrier; however, since ULE devices do not normally follow the NEMo countdown another method of communica... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.3 Behaviour during U-NEMo mode | The behaviour of the FT and the PTs attached to it (not the ULE devices) shall be as described in ETSI EN 300 175-3 [3], clause 9.4.2 with additions as described in ETSI EN 300 175-3 [3], clause 9.6.3. There are no additional requirements for the ULE devices beyond those described in ETSI EN 300 175-3 [3], clause 9.5. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.4 ULE device initiated interaction | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.4.1 ULE device requests that the base raise a ULE dummy bearer | Figure 11 and the subsequent text illustrates how this shall occur. Figure 11 1) The ULE device shall scan for a quiet slot pair and then shall send a wake up request to the FT. The wake up request shall be as described in ETSI EN 300 175-3 [3], clause 9.6.4. 2) The FT shall perform an RSSI scan and a Last Minute scan ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.4.2 ULE device initiated interaction when a dummy exists | If a dummy bearer is already present when a ULE device wakes and sends a request to raise a dummy bearer the FT shall ignore the request, in fact it will not actually see the requests since it shall no longer be scanning for setup messages. However, the setup will proceed as described in clause 10.9.4.1 starting at ste... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.5 FT initiated interaction | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.5.1 Interaction with ULE devices only | If the FP wishes to interact with ULE devices without waking handsets from NEMo mode it shall raise an ID free ULE dummy bearer. The procedure to raise the dummy shall be as described in ETSI EN 300 175-3 [3], clause 9.6.6.1 with the additional requirement that the FP shall use the NEMo preferred carrier for this dummy... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.5.2 Interaction with ULE devices which also wakes NEMo handsets | If the FP wishes to interact with ULE devices and also wake handsets from NEMo mode it shall raise a NEMo++ dummy bearer. The procedure to raise the dummy shall be as described in ETSI EN 300 175-3 [3], clause 9.6.6.2. The FT begins scanning in order to generate a blind slot map. The scanning will take x frames where x... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.6 NEMo handset initiated interaction | When a NEMo handset initiates an interaction the base shall raise the NEMo++ dummy bearer. This allows for ULE interactions in the period during which the system is waking from U-NEMo mode. The procedure to raise the bearer shall be as described in ETSI EN 300 175-3 [3], clause 9.6.5.4. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.7 Leaving U-NEMo mode | The FP can leave U-NEMo mode but remain in NEMo mode, this would allow the base to page ULE devices without interacting with the NEMo handsets. To do this the FP shall raise an ID free ULE dummy bearer as described in ETSI EN 300 175-3 [3], clause 9.6.5.3. The FP can leave U-NEMo mode and NEMo mode. To do this the FP s... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.8 U-NEMo and ULE paging | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.8.1 General | ULE paging procedures are not affected by U-NEMo except in the case where no devices are to be paged on a paging cycle (see clause 10.9.8.3). When it is required to page a device, the FT shall raise the ID free ULE dummy bearer and the ULE device will be able to lock onto it and follow normal ULE paging procedures. Onc... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.8.2 Multicast paging | If multicast paging is required when a NEMo++ dummy bearer is being broadcast operation shall be as per clause 10.5.2 with the paging data replacing the ULE B-field in the second part of the long slot B-field. If multicast paging data is due to be sent in a frame that would be the first full slot ULE dummy broadcast af... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 10.9.8.3 Relaxed paging | When an ULE device has been programmed with one or more paging descriptors it expects to be able to see paging information whether or not it is actually being paged. 'Relaxed paging' will allow U-NEMo operation to be maintained when no devices are being actively paged. The Format A paging descriptor (see clause 10.6.2.... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11 DLC layer procedures | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1 Specific procedures for C/L downlink multicast channels | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.1 Procedures for C/L downlink multicast channels | 11.1.1.1 LU14 Enhanced Frame RELay service with CCM (EFREL-CCM) for C/L downlink multicast channels The provisions given in ETSI EN 300 175-4 [4], clause 11.16.3.2 "Use over C/L downlink channels: multicast mode" shall apply. Unacknowledged transmission shall be used. A single uni-directional link shall be used for eac... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.1.2.0 General | The provisions given in ETSI EN 300 175-4 [4], clause 11.15.3.2 "Use over C/L downlink channels: multicast mode" shall apply. Unacknowledged transmission shall be used. A single uni-directional link shall be used for each instance of the service. There may be multiple instances of the service in a system (in general re... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.1.2.1 Use of LU13 in multicast links | Since LU13 is not the primary LU in ULE (that is LU14) and is an optional DLC service, LU13 can only be used in a multicast link if all the PT subscribed to such multicast group supports and are using LU13 for the C/O service. NOTE: This is expected to happen only in special markets. ETSI ETSI TS 102 939-2 V1.4.1 (2024... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.1.4 FU10a frame operation for C/L downlink multicast channels | The following provisions shall apply: As single uni-directional link using frame type FU10a shall be used for each instance of the service. Segment size shall be as given in ETSI EN 300 175-4 [4], Table 12.11.1.1, taken into account the subfield format of the MAC service (see clause 10.5.1.4). |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.1.5 Transmission Class 1 over C/L downlink multicast channels | The provisions of ETSI EN 300 175-4 [4], clause 14.2.3.2.1.1 "Class 1 over C/L downlink channels: unacknowledged mode" shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.2 Security procedures for C/L downlink multicast channels | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.2.1 CCM Authenticated Encryption of C/L downlink multicast channels | The provisions of ETSI EN 300 175-7 [7], clause 6.6.2.7 shall apply with the following specific provisions: • Support of multiple instances of multicast channels for a given PT is optional. Only number "Y" = '0' needs to be supported (see ETSI EN 300 175-7 [7], clause 6.6.2.7.1). Support of other values of number "Y" i... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.2.2 Initialization Vector for multicast channels | The Initialization Vector described in ETSI EN 300 175-7 [7], clause 6.6.2.7.6 shall be used. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 11.1.2.3 Security provisions regarding the key for multicast channels | The following requirements shall apply: • The FT shall change the key at least one time for a complete round of the CCM sequence numbers. NOTE 1: It should be noted that for many applications this timer may be irrelevant (it may take years). • The key shall not be reused for different multicast channels. • When the PT ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12 NWK layer procedures | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1 Specific procedures for C/L downlink multicast channels | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1 Security procedures for C/L downlink multicast channels | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.1 Cipher keys for CCM encryption of C/L multicast channels | The provisions of ETSI EN 300 175-7 [7], clause 6.2.3.2 and clause 6.6.2.7.7 shall apply. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.2 Multicast encryption parameter assignation procedure, FT initiated | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.2.0 General | This will be the normal assignation procedure when the FT subscribes a PT to a multicast channel. This procedure will typically be executed immediately following the subscription of a PT to a multicast channel. It will be part of a Service Call and shall be executed immediately after the CC Service change that allocate... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.2.1 Procedure description | The provisions of ETSI EN 300 175-7 [7], clause 6.3.8.2 shall apply. Only multicast instance #0 is mandatory. Support of additional multicast instances other than #0 is optional. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.2.2 Security provision | In order to preserve the security of the process, the procedure shall be always executed over encrypted links. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.2.3 Coding of the operation messages | This operation is coded as follows: • Initiating message {MM-INFO-SUGGEST} • Possible replies: - Normal case: {MM-INFO-ACCEPT} - Error case {MM-INFO-REJECT} The message {MM-INFO-SUGGEST} shall be coded as shown in Table 32. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 76 Table 32: Coding of the message {MM-INFO-SUGGEST} Inf... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.3 Multicast encryption parameter retrieval procedure, PT initiated | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.3.0 General | This is the exceptional procedure used by the PT when it "misses" either the Key or the CCM sequence. It allows the PT to request either, the <<KEY>> or the CCM sequence number or both. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.3.1 Procedure description | The provisions of ETSI EN 300 175-7 [7], clause 6.3.8.3 shall apply. Only multicast instance #0 is mandatory. Support of additional multicast instances other than #0 is optional. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.3.2 Security provisions | In order to preserve the security of the process, the procedure shall be always executed over encrypted links. If the PT requests the ciphering key, then the FT shall execute a PT authentication procedure between request and response. If the PT requests only the CCM sequence number, then the FT may (at its choice) exec... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.1.3.3 Coding of the operation messages | This operation is coded as follows: • Initiating message {MM-INFO-REQUEST} • Possible replies: - Normal case: {MM-INFO-SUGGEST} - Error case {MM-INFO-REJECT} The message {MM-INFO-REQUEST} shall be coded as shown in Table 35. Table 35: Coding of the message {MM-INFO-REQUEST} Information element Field within the informat... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.2 Control procedures for C/L downlink multicast channels | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.2.1 Subscription to C/L downlink multicast channels | The subscription to C/L downlink multicast channels is under control of the FT who should know at any time the list of available C/L downlink multicast channel instances, the destination PTs of each, and the identities allocated to each instance and PT. Refer to ETSI EN 300 175-3 [3], clause 9.1.4.7 for the description... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.2.2 Activation of security procedures | If the multicast transmission is CCM encrypted (service LU14), then the security procedure "Multicast encryption parameter assignation procedure, FT initiated" (clause 12.1.1.2) shall follow the subscription process. U–plane packets can only be successfully received by the subscribed PT after the completion of the secu... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.2.3 Un-subscription to C/L downlink multicast channels | The un-subscription to C/L downlink multicast channels can only be performed by means of {CC-SERVICE-CHANGE} operations sending the << ULE-MAC-CONFIGURATION-INFO >> IE with the command "replace all descriptors", and a new descriptor content not including the undesired subscription. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.1.2.4 Parameters for the C/L downlink multicast service | There is no specific parameter negotiation for the C/L downlink multicast service. The C/L service shall inherit the parameters used by the C/O service when applicable: • The case of having subscribed to the same multicast group PTs that may have different incompatible settings in the C/O service is not covered by the ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2 Terminal capabilities and FP broadcasts | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.1 Terminal capability indication | The PP shall be able to send the <<Terminal capability>> information element and the FP shall be able to receive it at least in {ACCESS-RIGHTS-REQUEST} and when location registration is supported in the {LOCATE-REQUEST}. The following text together with the associated clauses define the mandatory requirements with rega... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.2 FP broadcasts | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.2.1 Higher layer information FP broadcast | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.2.1.0 General | The FP and PT shall support the broadcast of Higher Layer capabilities as part of QT MAC broadcast messages (see clause 10.2.2.2). The broadcast attributes are a small set of NWK layer and DLC layer capabilities (jointly known as "higher layer capabilities") that shall be broadcast regularly as part of the MAC layer br... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.2.1.1 Higher layer information in standard FP broadcast (Qh = 3) | The Higher Layer capabilities Fixed Part Information field shall be used to indicate the support of the indicated features, as shown in Table 40. Most bits are not specific of ULE phase 2, but will be set in most RFPs due to the coexistence with voice services. Table 40: Higher layer information attributes in standard ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.2.1.2 Higher layer information in Extended FP broadcast (Qh = 4) | No Extended higher layer capabilities bits are used by the present document. |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.2.2.1.3 Extended Higher Layer capabilities part 2 (Qh = 11) | The Extended Higher Layer capabilities, part 2, Fixed Part Information field shall be used indicating the support of ULE part 1 (bit < a39 >) as well as other services and optional features that may be supported by the RFP, as shown in Table 41. Table 41: Extended Higher Layer Capabilities part 2 interpretation by the ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.3 Specific procedures for "hybrid" devices | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.3.1 Incoming calls for "hybrid voice" devices | |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.3.1.1 General requirements | ULE PPs that support regular calls are referred to as "hybrid voice" devices. However, not all hybrid voice devices will need to use incoming calls, for example some may only use outgoing calls. Furthermore, these hybrid voice devices are usually for special applications (e.g. door entry-phone intercoms, medical alarm ... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.3.1.2 Paging descriptors for incoming calls | ULE Phase 2 paging descriptors for hybrid incoming calls are defined in clause 10.6.2.5 of the present document. There are two types defined for hybrid incoming calls: "Setup voice call full slot" and "Setup voice call long slot" (see clause 10.6.2.5.2.2 and clause 10.6.2.5.2.3). As with all ULE B-field paging, a "mast... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.3.1.3 Incoming call procedure | The procedure for incoming call to a hybrid device is different to the normal LCE indirect FT initiated link establishment mechanism. ETSI ETSI TS 102 939-2 V1.4.1 (2024-05) 85 The general approach is to page the PP using ULE B-field paging, on receiving the page the PP then starts an outgoing call, finally the FP maps... |
852a56a1ce48f14ae4bbbda373f8ce93 | 102 939-2 | 12.3.2 Interactions of ULE and "circuit mode" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.