hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.1.6.3 A"-Interface (Relay Operation) timing | An EP which cannot successfully receive a base station is called an Orphan EP (OEP). An OEP may communicate with a BS via a Relay EP (RP) if the radio path permits; EP to RP communication uses the A"-interface. In normal circumstances OEP are avoided by careful deployment planning, however relay operation provides an o... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.1.6.4 Frequency and Time Synchronization | An EP typically has a low-stability frequency reference. It establishes and maintains frequency and time synchronization by receiving and decoding transmissions from a BS. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.2 Network Layer | The DD-UNB Layer 3 is implementation-dependent. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3 Data Link Layer | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.1 DLL introduction | The DD-UNB DLL is implementation-dependent and a range of DLL implementations can be used to take advantage of the features supported by the DD-UNB PHY, in particular the logical channels provided. However MAC sub-layer functionality is closely related to the PHY constraints of UNB (and DD-UNB specifics) and shall be i... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2 MAC sub-layer | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.1 MAC on A-interface UL - Data Subframe | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.1.1 General | The A-interface UL protocol MAC procedure is based on the "Aloha" approach randomized in both time (slotted Aloha) and frequency. The MAC procedure randomizes the timing of the transmission of data-bursts subject to avoiding unnecessary delays in sending data and subject to constraints arising from selected frame forma... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.1.2 UL throttle | The BS shall transmit (as part of its broadcast channel, see Table 6-7) a number between 0 and 7 related to the degree of overall uplink congestion it is experiencing. This number is called "uplink throttle value". If the uplink throttle value is not zero, then independently for each current or attempted connection (i.... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.1.3 Time domain | The random selection of timing of UL transmissions is strongly influenced by current physical layer configuration (including frame format) and constraints on the handling of data-bursts to be transmitted. A number of UL transmission time windows are available to an EP in the UL Data subframe, each is of 8 timeslots dur... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.1.4 Frequency domain | If an EP has one or more data-bursts to send during the UL subframe, MAC shall select, at random and independently for each data-burst, a UL sub-channel on which to transmit the data-burst (a value FMAC is provided to PHY, see clause 6.3.2.2.3); an exception is described in clause 6.4.3.3.3 for strongly-coded PDUs. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.2 MAC on A-interface UL - Ack Subframe | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.2.1 General | The A-interface UL protocol MAC procedure is based on the "Aloha" approach randomized in both time (slotted Aloha) and frequency. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.2.2 Time domain | The random selection of timing of UL transmissions is strongly influenced by current physical layer configuration (including frame format) and constraints on the handling of data-bursts to be transmitted. ETSI ETSI TS 103 357-1 V2.1.1 (2024-06) 39 A number of UL transmission time windows are available to an EP in the U... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.2.3 Frequency domain | If an EP has one or more data-bursts to send during the UL Ack subframe, MAC shall select, at random and independently for each data-burst, a UL sub-channel on which to transmit the data-burst (a value FMAC is provided to PHY, see clause 6.3.2). |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.3 MAC on A"-interface UL | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.3.1 General | The DD-UNB A" UL supports randomization in the time domain but not the frequency domain. In the A"-interface DL for each frame, an RP shall indicate to attached OEP (see clause 6.4.2.3) that the current A"-interface subframe is either "open" or "closed": • In an open A"-interface subframe any attached OEP may transmit.... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.2.3.2 Time domain | The MAC in an open A" UL subframe is based on slotted Aloha principles in the time domain. A number of timeslots are available to an OEP in the UL A" subframe (Table 6-3). Transmission of an A" UL data- burst shall start at the beginning of a timeslot, the timeslot shall be chosen randomly from those which permit compl... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.3.3 Encryption and Authentication | DD-UNB supports UL and DL encryption of application messages on the A and A"-interfaces. Encryption is applied between SC and EP (or OEP). Each EP shall be pre-provisioned with a pair of randomly-selected secret 256-bit keys (one for each of UL and DL), the mechanism for this is implementation-dependent; the keys shall... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4 Physical Layer | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1 PHY Format | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.1 Timing and Frame Formats | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.1.1 Introduction | The A-interface and A"-interface PHY use Time Domain Duplex (TDD). The basic element in the time structure of the DD-UNB system is the timeslot, which has a fixed length of 0,4 seconds. A frame comprises 60 timeslots numbered from timeslot number 0. A superframe comprises 64 frames numbered from frame 0. Each DD-UNB da... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.1.2 A-interface Frame Formats | There are 8 frame formats defined for the A-interface of a DD-UNB system, the number of timeslots in each subframe are shown in Table 6-2; the timeslots are allocated to subframes within the frame in the order shown. The choice of A-interface frame format shall be made by the BS on a per-frame basis and should take int... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.1.3 A"-interface Subframe Formats | There are 5 frame formats defined for the A"-interface of a DD-UNB system, the number of timeslots in each subframe is shown in Table 6-3; timeslots are allocated to subframes within the A"-interface subframe in the order shown. The choice of A"-interface format shall be made by the RP on a per-frame basis and should t... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.1.4 Synchronization and Frame Offset | BS in a DD-UNB system may be synchronized to a common timing of timeslot 0 of frame 0 (i.e. start of a superframe) with a maximum error of ±8 ms; such synchronization allows management of inter-BS interference. The method of maintaining synchronization is implementation-dependent. As described in Table 6-2, the DD-UNB ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.1.5 Battery saving | 6.4.1.1.5.1 Battery saving in DD-UNB DD-UNB supports three classes of EP operation. Class(es) supported by a specific EP are implementation-dependent as below. In battery-save mode an EP/RP does not support air-interface activity; it shall exit battery-save mode in time to operate as described below. Further battery-sa... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.1.2 Physical Channels | For the Downlink and A" downlink, each logical channel transferring data from higher layers corresponds to a physical channel, with three additional physical channels: the Sync Physical Channel, the Broadcast Physical Channel and the Wakeup Physical Channel. For the Uplink, two of the logical channels (the Uplink DLL C... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2 L1 PDUs and SDUs | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.1 Overview | Figure 6-10 shows how information is passed to/from Physical layer (downlink example), using L1 PDUs and SDUs. Figure 6-10: PHY PDUs and SDUs (Downlink) L1 PDUs and SDUs shall be constructed as described below. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.2 Sync PDU | Sync PDU is created at L1 and is formed by combining an uncoded Sync Header with a Sync Codeword (i.e. SC codeword, see Table 6-26 and Table 6-28) which is the result of BCH coding of Sync pre-coding block. Sync Header is defined as follows: Table 6-4: Sync Header Type Preamble Sequence Sync Word Downlink/ A" Downlink ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.3 Broadcast PDU | Broadcast PDU contains information describing the structure of the DL data-burst. The Broadcast PDU has different formats for the downlink and A" downlink. The Broadcast PDU is a broadcast codeword of length 175 bits. For the A-interface downlink, the Broadcast pre-coding block has length 51 bits, see Table 6-7. ETSI E... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.4 Wakeup PDU | Each Wakeup PDU contains 2 wakeup messages. Each wakeup message is 18 bits long which is evaluated and filled at physical layer, according to what is going to be transmitted on the data channel so that relevant EP stay up and anticipate, whereas others go to sleep and save power. Each wakeup message contains 14 bits Co... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.5 Multicast L1 SDU and PDU | Multicast L1 SDU can have two different lengths (51 bits and 139 bits). The Multicast Short L1 pre-coding block is identical to the Multicast Short L1 SDU and therefore is 51 bits. The Multicast Long L1 pre-coding block is described in Table 6-10. Table 6-10: Multicast Long L1 pre-coding block Field Length (bits) Notes... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.6 Control L1 SDU and PDU | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.6.1 Overview | The Control L1 SDU is always 135 bits long with the format shown in Table 6-11. ETSI ETSI TS 103 357-1 V2.1.1 (2024-06) 48 Table 6-11: Control L1 SDU Field Length (bits) Notes SSID 10 Short System ID. Direction 1 0 = towards Service Centre. 1 = away from Service Centre. L2 BSID 13 If Direction = 1: L2 BSID identifies t... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.6.2 A-interface Downlink and A"-interface | On A-interface DL and A"-interface the pre-coding block is shown in Table 6-12. Table 6-12: Downlink/A" Control L1 pre-coding block Field Length (bits) Notes Reserved 1 Reserved field (set to 0) Content 135 Control L1 SDU In this case Control L1 PDU is 168 bits if normal coding (i.e. CC codeword, see Table 6-26 and Tab... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.6.3 A-interface Uplink | In UL there is only one physical channel (UDPCH) to carry both control and connection data, the corresponding PDU is called Data L1 PDU. For normal coding strength see Table 6-13. Table 6-13: Uplink Data L1 pre-coding block - normal strength coding Field Length (bits) Notes Content Type 1 = 0 for Control Content 135 Co... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.7 Connection L1 SDU and PDU | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.7.1 Connection L1 SDU | Connection L1 SDU is 131 bits long as described in Table 6-16. Table 6-16: Connection L1 SDU Field Length (bits) Notes ConID 14 Connection ID BlkNum 5 PDU block number allocated by layer 3 Content 112 payload (14 bytes) |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.7.2 A-interface Downlink and A"-interface | PHY extracts Connection ID (14 bits) from the Connection L1 SDU and puts it in Wakeup PDU as explained in clause 6.4.2.4. The Connection L1 pre-coding block is shown in Table 6-17. Table 6-17: A-interface Downlink/A" Connection L1 pre-coding block Field Length (bits) Notes Reserved 7 Reserved field (set to 0) Content 1... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.7.3 A-interface Uplink | In this case, the pre-coding block contains Connection L1 SDU (including its ConID field) plus 5 bits header added by PHY, so the pre-coding block is 136 bits. ETSI ETSI TS 103 357-1 V2.1.1 (2024-06) 50 Table 6-18: Uplink Data L1 pre-coding block - normal strength coding Field Length (bits) Notes Content Type 1 =1 for ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.8 Acknowledge L1 SDU | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.8.1 Ack Message Format | Acknowledge L1 SDU comprises a number of Ack messages declaring Connection PDUs that are successfully received on the opposite (Up/Down)link, plus some L1-specific control parameters. The format of an Ack message is described in Table 6-19. Table 6-19: Ack Message Format Field Length (bits) Notes ConID 14 Connection ID... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.8.2 Acknowledge on A"-interface and A-interface DL | For downlink, A" downlink and A" uplink, Acknowledge L1 SDU can have two different lengths, see Table 6-21 and Table 6-22. PHY adds some L1 control fields and creates long Ack L1 pre-coding block (143 bits) or short Ack L1 pre-coding block (51 bits), which are then coded using the WAC or AC codeword respectively. The r... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.2.8.3 Acknowledge on A-interface UL | For A-interface uplink, Acknowledge L1 SDU is always 21 bits long. PHY creates Uplink Ack L1 pre-coding block which is 31 bits long as Table 6-25. Table 6-25: Uplink Ack L1 pre-coding block Field Length (bits) Notes Reserved 1 Reserved field (set to (0)) AC BSGP 4 BSGP used for UL Ack Reserved 4 Reserved field (set to ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3 PHY Functions | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.1 Channel Processing | Figure 6-11 illustrates the channel processing applied in the physical layer for the A-interface Downlink transmission. L2 PDUs are passed to the PHY through logical channels (which is then called L1 SDU). L1 SDUs are passed as described in clause 6.4.2 as pre-coding blocks to PHY channel coding function which performs... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.2 Channel Coding | All data transmitted by either Base Station or End-point shall be encoded using shortened BCH cyclic codes as described in Table 6-26, Table 6-27 and Table 6-28. ETSI ETSI TS 103 357-1 V2.1.1 (2024-06) 55 Table 6-26: Downlink Codewords Code Type Base Code Shortened Form Properties DL BCH Codewords n k n' k' rate t (use... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3 Data-Burst Building | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.1 Introduction | In the DD-UNB system, a data-burst typically occupies multiple timeslots. Data-bursts of different types are used for A- interface (Downlink, Uplink and Uplink Ack) and A"-interface (Downlink and Uplink). The transmission of data-bursts is generally determined by application requirements and those of other protocol lay... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.2 A-interface DL | Each A-interface DL data-burst shall comprise, in the order shown, a concatenation of: • A Sync PDU (a Sync header of 80 bits followed by 112 bits SC codeword and then a guard period) which fits exactly into one timeslot (0,4 second). • A single BC which carries the details of the sequence of codewords that follows it.... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.3 A-interface UL Data | Each A-interface UL Data data-burst shall comprise a Sync header of 16 bits (see Table 6-4) followed by a CC/XC codeword (176 bits) or a double SCC/XCC codeword (352 bits), occupying 8 or 16 timeslots. A resulting 16-slot data- burst shall be divided into a first and second sequential (but not necessarily contiguous) 8... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.4 A-interface UL Ack | Each A-interface Uplink Ack data-burst shall comprise a Sync header of 16 bits (see Table 6-4) followed by a single AC codeword (80 bits), occupying 4 timeslots. Zero or more UL Ack data-bursts may be transmitted by an EP/RP in each UL subframe, see Figure 6-12, subject to frame and subframe format constraints. Timing ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.5 A"-interface DL | Each A"-interface DL data-burst shall comprise, in the order shown, a concatenation of: • A Sync PDU (a Sync header of 80 bits followed by 112 bits SC codeword and then a guard period) which fits exactly into one timeslot (0,4 second). • A single BC which carries the details of the sequence of codewords that follows it... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.6 A"-interface UL Data data-burst | Each A"-interface UL data-burst shall comprise, in the order shown, a concatenation of: • A Sync PDU (a Sync header of 80 bits followed by 112 bits DC codeword and then a guard period) which fits exactly into one timeslot (0,4 second). ETSI ETSI TS 103 357-1 V2.1.1 (2024-06) 57 • Zero or more CC/SCC codewords. • Zero o... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.7 A"-interface UL Ack data-burst | A"-interface Uplink Ack data-burst shall always start with a specific Sync header of 16 bits (as in Table 6-4). The remainder of the data-burst consists of a single AC codeword (80 bits). A RP shall transmit no more than one such data-burst in each A"-interface UL subframe, subject to frame and subframe format constrai... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.3.8 Bit order | Each pre-coding block shall be packed with the last entry in its pre-coding block table in the least significant location of the PDU (without changing bit order) and then each preceding entry shall be added in more significant locations (in the same bit order). The packed and coded PDU is transmitted least significant ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.4 Power Control | Power control is used in A-interface Uplink transmission by EP. Provision is made in PHY to control transmit power level using "Too Loud" flag. When the received RSSI at the BS is higher than an implementation-dependent defined threshold, BS may indicate "Too Loud" (see Table 6-23) in which case the EP shall reduce its... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.3.5 High Interference Mode | As described in the present document, strong and weak coding is available for a range of PDUs. The choice of coding scheme shall be made by the related entity and shall be signalled as described (e.g. Table 6-9). Choice of algorithm by which to determine whether to use High Interference Mode is implementation dependent... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4 PHY Procedures | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.1 Synchronization and Frequency Scanning | Layer 1 supports frequency scanning and synchronization processes to detect available BS and RP. This process is implementation-dependent. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.2 Base Selection | The process by which an EP selects a BS / RP with which to attempt connection is implementation-dependent. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.3 Transmit Duty-Cycle Control | DD-UNB implementations are typically subject to regulatory limits on transmitter duty cycle. It is an implementation issue to ensure such limits are not exceeded. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.4 A-interface Downlink Transmission Control - Frame Structure | Before the start of each frame, BS shall determine the frame format to use for that frame as described in clause 6.4.1.1. This process is implementation-dependent. Transmission of DL data-bursts shall commence in the first timeslot allocated to the related subframe, see Table 6-1. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.5 A"-interface Downlink Transmission Control - Subframe Structure | Before the start of each A"-interface subframe, RP shall determine the format to use for that subframe as described in clause 6.4.1.1. This process is implementation-dependent. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.6 Uplink Transmission Control | BS transmissions are the reference for both the time and the frequency of EP and RP transmissions. No allowance for propagation delays is required in the timing of uplink transmissions. |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.7 PHY Measurements | PHY measurements are implementation-dependent and may include: • the average power (RSSI) of the Sync Word in a data-burst; • the number of corrected bits in each received codeword; or • other measurements. Such measurements may be used to support "too loud" indication (clause 6.4.3.4). |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.8 Noise Measurement | Some A-interface frame formats allocate "noise measurement" timeslots during which no system elements transmit. These may be used to measure noise and/or interference levels; such measurements, and the use of the results, are implementation-dependent. ETSI ETSI TS 103 357-1 V2.1.1 (2024-06) 59 |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.4.4.9 Base-System Group (BSGP) | To enable the BS to distinguish reception of a local EP's (intended) transmissions from distant EP's (unintended) transmissions (in the case that block numbers coincide), "Uplink Connection Base-System Group" (XC BSGP) is included in each Data L1 PDU on the A-interface UL, see Table 6-18. XC BSGP (see Table 6-18) has t... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5 Radio characteristics | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5.1 Frequency Structure - Radio Mode 0 | Clause 6.5.1 and any subclauses describe DD-UNB operation in Radio Mode 0; other modes are for further study. Table 6-29: Radio Mode definition Radio Mode Downlink / A" Uplink Bit-rate (bps) Symbol-rate (Hz) Deviation Δf (Hz) Bit-rate (bps) Symbol-rate (Hz) Deviation Δf (Hz) 0 500 500 ±250 62,5 62,5 ±250 Other Reserved... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5.2 Modulation - Radio Mode 0 | |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5.2.1 General | Clause 6.5.2 and subclauses describe DD-UNB operation in Radio Mode 0; other modes are for further study and may, for example, include the generation of more than one modulated carrier within the identified channel on one or more interfaces or alternative modulation schemes. The DD-UNB modulation uses Binary Frequency ... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5.2.2 A-interface DL and A"-interface (UL and DL) modulation | Within the selected 25 kHz channel a number of nominal carrier frequencies spaced at 500 Hz intervals are identified (as FDM_fc(n)) as depicted in Figure 6-17. For Radio Mode 0 A-interface DL a modulated carrier is generated at FDM_fc(10) or FDM_fc(40); the choice between these values of FDM_fc is made in network plann... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5.2.3 A-interface UL modulation | Uplink modulation is implemented based on a combination of BFSK and Random Frequency Selection (RFS). In Radio Mode 0 the UL operating channel width is 15 kHz. Each EP/RP shall perform RFS independently for each data-burst (except as described in clause 6.4.3.3.3 for strongly-coded PDUs where each pair of data-bursts s... |
8b6d4106d11993cc2e728ec36f5b938d | 103 357-1 | 6.5.3 Radio-Burst Power Ramping | A guard period of 16 ms is provided for power-ramping and optional frequency hopping between radio-bursts; when transmitting, transmit power shall be reduced during the guard period in all entities (whether or not frequency-hopping). Transmit power shall rise or fall by ≥60 dB within 500 µs of the start or end (respect... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 1 Scope | The present document specifies security processes and techniques for LI and RD systems. The present document is limited to: 1) The provision of evidential assurance of RD material. 2) Security issues around the role for global, third-party or virtualized components for RD systems. Future versions of the present documen... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 2 References | |
46fe10ab777a208d85d6085043905f1c | 103 307 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 3 Definition of terms, symbols and abbreviations | |
46fe10ab777a208d85d6085043905f1c | 103 307 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 657 [i.1] and the following apply: third party: organization other than the CSP or LEA who is engaged to assist in providing RD or LI services NOTE: Often the phrase "Trusted Third Party" is used. Clearly the CSP or LEA are expected to engage Thir... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 3.2 Symbols | Void. |
46fe10ab777a208d85d6085043905f1c | 103 307 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CESG Communications Electronic Security Group CSP Communications Service Provider LEA Law Enforcement Agency LI Lawful Interception RD Retained Data SHA Secure Hash Algorithm XML eXtensible Markup Language |
46fe10ab777a208d85d6085043905f1c | 103 307 | 4 Structure of document and list of relevant interfaces | |
46fe10ab777a208d85d6085043905f1c | 103 307 | 4.1 Introduction | The present document considers the list of particular information flows and interfaces for RD and LI specified in clause 4.2. It examines them from a security (confidentiality, integrity and authenticity) perspective and specifies implementation details (technologies, algorithms, options, minimum requirements on keys, ... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 4.2 List of LI and RD items covered in the present document | The present document addresses the following LI and RD items: 1) Providing evidential assurance of LI or RD material (annex A). 2) Security issues around the role for global, third-party or virtualized components of Retained Data facilities (annex B). The following topics will be covered in future versions of the prese... |
46fe10ab777a208d85d6085043905f1c | 103 307 | 5 Common techniques | |
46fe10ab777a208d85d6085043905f1c | 103 307 | 5.1 Introduction | The following techniques are used in a number of the annexes of the present document: • Algorithms for hashing data. The following techniques will be included in future versions of the present document: • Digital signature algorithms. • Procedures for Trusted timestamp. • Transport-layer security. |
46fe10ab777a208d85d6085043905f1c | 103 307 | 5.2 Hash algorithms | The SHA-256 algorithm shall be as defined in FIPS Publication 180-4 [1]. The SHA-512 algorithm shall be as defined in FIPS Publication 180-4 [1]. ETSI ETSI TS 103 307 V1.5.1 (2023-10) 9 Annex A (normative): Providing assurance for LI or RD material as evidence A.1 Statement of problem The requirement is to provide assu... |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 1 Scope | The present document describes the test scenarios performed at the RFID Interoperability event in Brazil. The interoperability event, also called Plugtests event is being organized by ETSI, CPqD and FP7 Probe-IT Project. The event took place from 20 - 24 May 2013 at the CPqD Head Quarters, in Campinas, Brazil. The prim... |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 2 References | |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 3 Definitions, symbols and abbreviations | |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: interrogator: device that can read and write to RFID tags tag: transponder that holds data and responds to an interrogation signal Tari: reference time interval for a data-0 in interrogator-to-tag signalling ETSI ETSI TS 103 302 V1.1.1... |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: dB decibel dBm power level relative to 1 mW kHz kilo Hertz m metres MHz Mega Hertz us micro second |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BER Bit Error Rate DAA Detect And Avoid EIRP Effective Isotropic Radiated Power EPC Electronic Product Code FDM Frequency-Division Multiplexing FHSS Frequency Hopping Spread Spectrum FM Frequency Modulation GSM Global System for Mobile communi... |
be9fab393e60b5be9c779b9b4969cd5b | 103 302 | 4 Test preparation |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.