hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
2.2M
|
|---|---|---|---|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.0 General
|
This clause defines the specifications for cab radio user equipment, which fulfil the power class 1 category as specified in ETSI TS 138 101-1 [1], clause 6.2. If an external antenna is present the PEIRP shall not exceed 33 dBm.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.1 Output power
|
The specifications defined in ETSI TS 138 101-1 [1], clause 6.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.2 Out-of-band and spurious emissions
|
The specifications defined in ETSI TS 138 101-1 [1], clauses 6.1, 6.5.2 and 6.5.3 shall apply to European frequency bands listed in Annex A.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.3 NR ACLR
|
The specifications defined in ETSI TS 138 101-1 [1], clause 6.5.2.4.1 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.4 Reference sensitivity
|
The specifications defined in ETSI TS 138 101-1 [1], clause 7.3.2 for frequency band n100 and n101 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.5 Blocking requirements
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.5.0 General
|
The following Tables define the tolerable interfering signals that need to be taken into account for the cab radio user equipment. The frequency ranges for the interfering signals shall be considered edge-to-edge, including any guard band within the carrier as defined in the respective standard of the interfering signal as shown in Tables 6.5.1-1 and 6.5.2-1. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 11
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.5.1 n100
|
For n100, the blocking signals identified in Table 6.5.1-1 shall be considered. Table 6.5.1-1: n100 cab radio blocking characteristics Frequency range (edge to edge) Interfering signal type Power level for interfering signal Level of wanted signal Corresponding test case in clause 9.2.2 880 - 915 MHz 5 MHz LTE, according to ETSI TS 136 101 [7], clause 5.6 -26 dBm REFSENS + 3 dB Test method #1 915 - 918,9 MHz 400 kHz SRD / RFID, according to ETSI EN 302 208 [6], clause 4.2 -26 dBm Test method #1 925,6 - 927 MHz CW -13 dBm Test method #2 927 - 960 MHz CW -10 dBm Test method #2 925,1 - 930,1 MHz 5 MHz LTE, according to ETSI TS 136 101 [7], clause 5.6 -13 dBm Test method #1
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6.5.2 n101
|
For n101, the blocking signals identified in Table 6.5.2-1 shall be considered. Table 6.5.2-1: n101 cab radio blocking characteristics Frequency range (edge to edge) Interfering signal type Power level for interfering signal Level of wanted signal Corresponding test case in clause 9.2.2 1 805 - 1 880 MHz 5 MHz LTE, according to ETSI TS 136 101 [7], clause 5.6 -13 dBm REFSENS + 3 dB Test method #1 1 920 - 1 980 MHz 5 MHz LTE, according to ETSI TS 136 101 [7], clause 5.6 -39 dBm Test method #1
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
7 Specifications for terminals other than cab radios
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
7.0 General
|
This clause defines the specifications for terminals other than cab radios, which fulfil the power class 3 category as specified in ETSI TS 138 101-1 [1], clause 6.2.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
7.1 Output power
|
The specifications defined in ETSI TS 138 101-1 [1], clause 6.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
7.2 Out-of-band and spurious emissions
|
The specifications defined in ETSI TS 138 101-1 [1], clauses 6.1, 6.5.2 and 6.5.3 shall apply to European frequency bands listed in Annex A.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
7.3 NR ACLR
|
The specifications defined in ETSI TS 138 101-1 [1], clause 6.5.2.4.1 shall apply. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 12
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
7.4 Reference sensitivity
|
The specifications defined in ETSI TS 138 101-1 [1], clause 7.3.2 for frequency bands n100 and n101 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
7.5 Blocking requirements
|
The specifications defined in ETSI TS 138 101-1 [1], clause 7.6 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
8 Test cases for base stations
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.1 Transmitter
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.1.1 Output power
|
The test case defined in ETSI TS 138 141-1 [3], clause 6.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.1.2 Spurious emissions
|
The test cases defined in ETSI TS 138 141-1 [3], clause 6.6 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.2 Receiver
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.2.1 Reference sensitivity
|
The test case defined in ETSI TS 138 141-1 [3], clause 7.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.2.2 In-band selectivity and blocking
|
The test cases defined in ETSI TS 138 141-1 [3], clause 7.4 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.2.3 Out-of-band blocking
|
The test case defined in ETSI TS 138 141-1 [3], clause 7.5 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
8.2.4 Receiver intermodulation
|
The test case defined in ETSI TS 138 141-1 [3], clause 7.7 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9 Test cases for cab radio user equipment
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.0 General
|
This clause defines the test cases for cab radio user equipment, which fulfil the power class 1 category as specified in ETSI TS 138 101-1 [1], clause 6.2.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.1 Transmitter
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.1.1 Output power
|
The test cases defined in ETSI TS 138 521-1 [5], clause 6.2 shall apply. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 13
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.1.2 NR ACLR
|
The test case defined in ETSI TS 138 521-1 [5], clause 6.5.2.4.1 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.1.3 Out-of-band and spurious emissions
|
The test cases defined in ETSI TS 138 521-1 [5], clauses 6.5.2 and 6.5.3 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2 Receiver
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.1 Reference sensitivity power level
|
The test case defined in ETSI TS 138 521-1 [5], clause 7.3 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2 Blocking
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.0 General Requirements
|
The test procedures specified in the present clause shall be carried out using the defined characteristics (in Tables 6.5.1-1 and 6.5.2-1) for testing RF blocking with FRMCS cab radio user equipment.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.1 Test purpose
|
The blocking characteristic is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels, without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.2 Test method #1
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.2.1 Test applicability
|
This test method applies to all FRMCS cab radio user equipment. It is used for testing RF blocking with interfering signals of type other than CW (see Tables 6.5.1-1 and 6.5.2-1).
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.2.2 Minimum conformance requirements
|
The throughput of the wanted signal shall be ≥ 95 % of the maximum throughput of the reference measurement channels as specified in ETSI TS 138 521-1 [5], clauses A.2.2, A.2.3, A.3.2 and A.3.3 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL signal as described in ETSI TS 138 521-1 [5], clause A.5) with parameters specified in Tables 9.2.2.2.2-1 and 9.2.2.2.3.1-1. Table 9.2.2.2.2-1: Test parameter table Rx parameter Units Channel bandwidth (MHz) 5, 10 Power in transmission bandwidth configuration dBm REFSENS + 3 dB BWinterferer MHz As defined in Tables 6.5.1-1 and 6.5.2-1 NOTE: The transmitter shall be set to 4 dB below PCMAX_L,f,c at the minimum UL configuration specified in ETSI TS 138 521-1 [5], Table 7.3.2.3-3 with PCMAX_L,f,c defined in ETSI TS 138 521-1 [5], clause 6.2.4. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 14
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.2.3 Test description
|
9.2.2.2.3.1 Initial conditions Initial conditions are a set of test configurations in which the cab radio UE needs to be tested in and the steps for the SS to take with the cab radio UE to reach the correct measurement state. The initial test configurations consist of environmental conditions based on NR operating bands specified in ETSI TS 138 521-1 [5], Table 5.3.5-1. The details of the uplink and downlink Reference Measurement Channels (RMC) are specified in ETSI TS 138 521-1 [5], clauses A.2 and A.3. Configuration of PDSCH and PDCCH before measurement are specified in ETSI TS 138 521-1 [5], clause C.2. Table 9.2.2.2.3.1-1: Test configuration table Default Conditions Test Environment as specified in ETSI TS 138 508-1 [4], clause 4.1 Normal Test Frequencies for wanted and unwanted signals Low, Mid, High Test Channel Bandwidths 5 MHz for band n100, 10 MHz for band n101 Test SCS for the wanted signal 15 kHz for band n100, 30 kHz for band n101 Test Parameters Downlink Configuration Uplink Configuration Test ID Modulation RB allocation Modulation RB allocation 1 CP-OFDM QPSK Note 1 DFT-s-OFDM QPSK Note 1 NOTE 1: The specific configuration of uplink and downlink are defined in ETSI TS 138 521-1 [5], Table 7.3.2.4.1-1. NOTE 2: In a band where cab radio UE supports 4Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (ETSI TS 138 521-1 [5], Table 7.3.2.5-2) is used in the test requirements. NOTE 3: The test frequencies shall be the lowest, the middle and the highest frequency available within the given frequency band with the specified configuration, for both wanted and unwanted signals. In specific cases, there are either one or two possible test frequencies. All combinations of possible wanted and unwanted frequencies shall be tested. 1) Connect the SS to the cab radio UE antenna connectors as shown in ETSI TS 138 508-1 [4], Annex A, in Figure A.3.1.4.1 for TE diagram and clause A.3.2 for UE diagram. 2) The parameter settings for the cell are set up according to ETSI TS 138 508-1 [4], clause 4.4.3. 3) Downlink signals are initially set up according to ETSI TS 138 521-1 [5], clauses C.0, C.1, C.2 and C.3.1, and uplink signals according to ETSI TS 138 521-1 [5], clauses G.0, G.1, G.2 and G.3.1. 4) The DL and UL Reference Measurement channels are set according to Table 9.2.2.2.3.1-1. 5) Propagation conditions are set according to ETSI TS 138 521-1 [5], clause B.0. 6) Ensure the cab radio UE is in state RRC_CONNECTED with generic procedure parameters Connectivity NR, Connected without release On, Test Mode On and Test Loop Function On according to ETSI TS 138 508-1 [4], clause 4.5. Message contents are defined in clause 9.2.2.2.3.3. 9.2.2.2.3.2 Test procedure 1) SS transmits PDSCH via PDCCH DCI format 1_1 for C_RNTI to transmit the DL RMC according to Table 9.2.2.2.3.1-1. The SS sends downlink MAC padding bits on the DL RMC. 2) SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0_1 for C_RNTI to schedule the UL RMC according to Table 9.2.2.2.3.1-1. Since the UL has no payload and no loopback data to send the cab radio UE sends uplink MAC padding bits on the UL RMC. 3) Set the parameters of the signal generator for an interfering signal according to Table 9.2.2.2.2-1. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 15 4) Set the downlink signal level according to Table 6.5.1-1 or 6.5.2-1. Send uplink power control commands to the cab radio UE using 1 dB power step size to ensure that the cab radio UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 9.2.2.2.2-1 for at least the duration of the Throughput measurement, where: - MU is the test system uplink power measurement uncertainty and is specified in ETSI TS 138 521-1 [5], Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. - Uplink power control window size = 1 dB (cab radio UE power step size) + 0,7 dB (cab radio UE power step tolerance) + (Test system relative power measurement uncertainty), where, the cab radio UE power step tolerance is specified in ETSI TS 138 101-1 [1], Table 6.3.4.3-1 and is 0,7 dB for 1 dB power step size, and the Test system relative power measurement uncertainty is specified for test case 6.3.4.3 in ETSI TS 138 521-1 [5], Table F.1.2-1. - For cab radio UEs supporting Tx diversity, the transmit power is measured as the sum of the output power from both cab radio UE antenna connectors. 5) Measure the average throughput for a duration sufficient to achieve statistical significance according to ETSI TS 138 521-1 [5], Annex H. NOTE: The purpose of the Uplink power control window is to ensure that the actual cab radio UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual cab radio UE Uplink power window is illustrated in ETSI TS 138 521-1 [5], clause F.4.3. 9.2.2.2.3.3 Message contents Message contents are according to ETSI TS 138 508-1 [4], clause 4.6 with TRANSFORM_PRECODER_ENABLED condition in Table 4.6.3-118 PUSCH-Config.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.2.4 Test requirement
|
The throughput measurement derived in test procedure shall be ≥ 95 % of the maximum throughput of the reference measurement channels as specified in ETSI TS 138 521-1 [5], clauses A.2.2, A.2.3 and A.3.2 with parameters specified in Tables 9.2.2.2.2-1 and 9.2.2.2.3.1-1.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.3 Test method #2
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.3.1 Test applicability
|
This test method applies to all FRMCS cab radio user equipment. It is used for testing RF blocking with interfering signals of type CW (see Table 6.5.1-1).
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.3.2 Minimum conformance requirements
|
The throughput of the wanted signal shall be ≥ 95 % of the maximum throughput of the reference measurement channels as specified in ETSI TS 138 521-1 [5], clauses A.2.2, A.2.3, A.3.2 and A.3.3 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in ETSI TS 138 521-1 [5], clauses A.5.1.1 and A.5.2.1) with parameters specified in Tables 9.2.2.3.2-1 and 9.2.2.3.3.1-1. Table 9.2.2.3.2-1: Test parameter table Channel bandwidth Power in transmission bandwidth configuration [dBm] 5, 10 MHz REFSENS + 3 dB NOTE: The transmitter shall be set to 4 dB below PCMAX_L,f,c at the minimum UL configuration specified in ETSI TS 138 521-1 [5], Table 7.3.2.3-3 with PCMAX_L,f,c defined in ETSI TS 138 521-1 [5], clause 6.2.4. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 16 For interferer frequencies in Table 6.5.1-1, a maximum of: ⌊24,6 ⋅⌈ ⋅ /6⌉ ⌊ ⋅ /10⌋, 5 ⁄ ⌋ exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a step size of ( ⌊ℎ/2⌋, 5) MHz with the number of resource blocks in the downlink transmission bandwidth configuration, BWChannel is the bandwidth of the frequency channel in MHz and n = 1,2 for SCS = 15,30 kHz, respectively. For these exceptions, the requirements in ETSI TS 138 521-1 [5], clause 7.7 apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.3.3 Test Description
|
9.2.2.3.3.1 Initial Conditions Initial conditions are a set of test configurations in which the cab radio UE needs to be tested in and the steps for the SS to take with the cab radio UE to reach the correct measurement state. The initial test configurations consist of environmental conditions based on NR operating bands specified in ETSI TS 138 521-1 [5], Table 5.3.5-1. All of these configurations for wanted and unwanted frequencies shall be tested with applicable test parameters for each combination of channel bandwidth and sub-carrier spacing, and are shown in Table 9.2.2.3.3.1-1. The details of the uplink and downlink Reference Measurement Channels (RMCs) are specified in ETSI TS 138 521-1 [5], clauses A.2 and A.3 respectively. The details of the OCNG patterns used are specified in ETSI TS 138 521-1 [5], clause A.5. Configurations of PDSCH and PDCCH before measurement are specified in ETSI TS 138 521-1 [5], clause C.3. Table 9.2.2.3.3.1-1: Test configuration table Default Conditions Test Environment as specified in ETSI TS 138 508-1 [4], clause 4.1 Normal Test Frequencies for wanted and unwanted signals Low, Mid, High Test Channel Bandwidths 5 MHz for band n100, 10 MHz for band n101 Test SCS for the wanted signal 15 kHz for band n100, 30 kHz for band n101 Test Parameters Downlink Configuration Uplink Configuration Test ID Modulation RB allocation Modulation RB allocation 1 CP-OFDM QPSK Note 1 DFT-s-OFDM QPSK Note 1 NOTE 1: The specific configuration of uplink and downlink are defined in ETSI TS 138 521-1 [5], Table 7.3.2.4.1-1. NOTE 2: In a band where cab radio UE supports 4Rx but does not support 8Rx, the test shall be performed only with 4Rx antennas ports connected and 4Rx REFSENS requirement (ETSI TS 138 521-1 [5], Tables 7.3.2.5-2a and 7.3.2.5-2b) is used in the test requirements. In a band where cab radio UE supports 8Rx, the test shall be performed only with 8Rx antennas ports connected and 8Rx REFSENS requirement (ETSI TS 138 521-1 [5], Tables 7.3.2.5-2e and 7.3.2.5-2f) is used in the test requirements. Otherwise, the UE shall be verified with two Rx antenna ports. NOTE 3: The test frequencies shall be the lowest, the middle and the highest frequency available within the given frequency band with the specified configuration, for both wanted and unwanted signals. In specific cases, there are either one or two possible test frequencies. All combinations of possible wanted and unwanted frequencies shall be tested. 1) Connect the SS to the cab radio UE antenna connectors as shown in ETSI TS 138 508-1 [4], Annex A, in Figure A.3.1.4.2 for TE diagram and clause A.3.2 for UE diagram. 2) The parameter settings for the cell are set up according to ETSI TS 138 508-1 [4], clause 4.4.3. 3) Downlink signals are initially set up according to ETSI TS 138 521-1 [5], clauses C.0, C.1, C.2 and C.3.1, and uplink signals according to ETSI TS 138 521-1 [5], clauses G.0, G.1, G.2 and G.3.1. 4) The UL and DL Reference Measurement channels are set according to Table 9.2.2.3.3.1-1. 5) Propagation conditions are set according to ETSI TS 138 521-1 [5], clause B.0. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 17 6) Ensure the cab radio UE is in State RRC_CONNECTED with generic procedure parameters Connectivity NR, Connected without release On, Test Mode On and Test Loop Function On according to ETSI TS 138 508-1 [4], clause 4.5. Message contents are defined in clause 9.2.2.3.3.3. 9.2.2.3.3.2 Test Procedure 1) SS transmits PDSCH via PDCCH DCI format 1_1 for C_RNTI to transmit the DL RMC according to Table 9.2.2.3.3.1-1. The SS sends downlink MAC padding bits on the DL RMC. 2) SS sends uplink scheduling information for each UL HARQ process via PDCCH DCI format 0_1 for C_RNTI to schedule the UL RMC according to Table 9.2.2.3.3.1-1. Since the cab radio UE has no payload data to send, the cab radio UE transmits uplink MAC padding bits on the UL RMC. 3) Set the parameters of the CW signal generator for an interfering signal below the wanted signal according to Table 6.5.1-1. The frequency step size is ( ⌊ℎ/2⌋, 5) MHz. 4) Set the downlink signal level according to the Table 6.5.1-1. Send uplink power control commands to the cab radio UE using 1 dB power step size to ensure that the cab radio UE output power measured by the test system is within the Uplink power control window, defined as -MU to -(MU + Uplink power control window size) dB of the target power level in Table 9.2.2.3.2-1 for at least the duration of the Throughput measurement, where: - MU is the test system uplink power measurement uncertainty and is specified in ETSI TS 138 521-1 [5], Table F.1.3-1 for the carrier frequency f and the channel bandwidth BW. - Uplink power control window size = 1 dB (cab radio UE power step size) + 0,7 dB (cab radio UE power step tolerance) + (Test system relative power measurement uncertainty), where, the cab radio UE power step tolerance is specified in ETSI TS 138 101-1 [1], Table 6.3.4.3-1 and is 0,7 dB for 1 dB power step size, and the Test system relative power measurement uncertainty is specified for test case 6.3.4.3 in ETSI TS 138 521-1 [5], Table F.1.2-1. - For cab radio UEs supporting Tx diversity, the transmit power is measured as the sum of the output power from both cab radio UE antenna connectors. 5) Measure the average throughput for a duration sufficient to achieve statistical significance according to ETSI TS 138 521-1 [5], Annex H. 6) Record the frequencies for which the throughput does not meet the requirements. 7) Repeat steps from 3 to 6, using an interfering signal above the wanted signal at step 3. NOTE: The purpose of the Uplink power control window is to ensure that the actual cab radio UE output power is no greater than the target power level, and as close as possible to the target power level. The relationship between the Uplink power control window, the target power level and the corresponding possible actual cab radio UE Uplink power window is illustrated in ETSI TS 138 521-1 [5], clause F.4.3. 9.2.2.3.3.3 Message Contents Message contents are according to ETSI TS 138 508-1 [4], clause 4.6 ensuring Table 4.6.3-118 with condition TRANSFORM_PRECODER_ENABLED.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
9.2.2.3.4 Test Requirement
|
The throughput measurement derived in test procedure shall be ≥ 95 % of the maximum throughput of the reference measurement channels as specified in ETSI TS 138 521-1 [5], clauses A.3.2 and A.3.3 with parameters specified in Tables 9.2.2.3.2-1 and 9.2.2.3.3.1-1. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 18
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
10 Test cases for terminals other than cab radios
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.0 General
|
This clause defines the test cases for terminals other than cab radios, which fulfil the power class 3 category as specified in ETSI TS 138 101-1 [1], clause 6.2.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.1 Transmitter
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.1.1 Output power
|
The test cases defined in ETSI TS 138 521-1 [5], clause 6.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.1.2 NR ACLR
|
The test case defined in ETSI TS 138 521-1 [5], clause 6.5.2.4.1 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.1.3 Out-of-band and spurious emissions
|
The test cases defined in ETSI TS 138 521-1 [5], clauses 6.5.2 and 6.5.3 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.2 Receiver
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.2.1 Reference sensitivity power level
|
The test case defined in ETSI TS 138 521-1 [5], clause 7.3 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
10.2.2 Blocking
|
The test cases defined in ETSI TS 138 521-1 [5], clause 7.6 shall apply. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 19 Annex A (normative): European mobile bands, excluding n100 and n101 Table A-1: List of European mobile bands, excluding n100 and n101 Protected system Frequency range for co-existence requirement GSM900 921 MHz to 960 MHz 876 MHz to 915 MHz DCS1800 1 805 MHz to 1 880 MHz 1 710 MHz to 1 785 MHz UTRA FDD Band I or 2 110 MHz to 2 170 MHz E-UTRA Band 1 or NR Band n1 1 920 MHz to 1 980 MHz UTRA FDD Band III or 1 805 MHz to 1 880 MHz E-UTRA Band 3 or NR Band n3 1 710 MHz to 1 785 MHz UTRA FDD Band VII or 2 620 MHz to 2 690 MHz E-UTRA Band 7 or NR Band n7 2 500 MHz to 2 570 MHz UTRA FDD Band VIII or 925 MHz to 960 MHz E-UTRA Band 8 or NR Band n8 880 MHz to 915 MHz UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 791 MHz to 821 MHz 832 MHz to 862 MHz E-UTRA Band 28 or NR Band n28 758 MHz to 803 MHz 703 MHz to 748 MHz UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 2 570 MHz to 2 620 MHz UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 2 300 MHz to 2 400 MHz E-UTRA Band 41 or NR Band n41 2 496 MHz to 2 690 MHz E-UTRA Band 50 or NR band n50 1 432 MHz to 1 517 MHz E-UTRA Band 51 or NR Band n51 1 427 MHz to 1 432 MHz E-UTRA Band 65 or NR Band n65 2 110 MHz to 2 200 MHz 1 920 MHz to 2 010 MHz E-UTRA Band 75 or NR Band n75 1 432 MHz to 1 517 MHz E-UTRA Band 76 or NR Band n76 1 427 MHz to 1 432 MHz NR Band n77 3 300 MHz to 4 200 MHz NR Band n78 3 300 MHz to 3 800 MHz NR band 80 1 710 MHz to 1 785 MHz NR band 81 880 MHz to 915 MHz NR band 82 832 MHz to 862 MHz NR band 83 703 MHz to 748 MHz NR band 84 1 920 MHz to 1 980 MHz E-UTRA Band 87 420 MHz to 425 MHz 410 MHz to 415 MHz E-UTRA Band 88 422 MHz to 427 MHz 412 MHz to 417 MHz NR Band n91 1 427 MHz to 1 432 MHz 832 MHz to 862 MHz NR Band n92 1 432 MHz to 1 517 MHz 832 MHz to 862 MHz NR Band n93 1 427 MHz to 1 432 MHz 880 MHz to 915 MHz NR Band n94 1 432 MHz to 1 517 MHz 880 MHz to 915 MHz ETSI ETSI TS 103 793 V1.1.1 (2025-11) 20 History Document history V1.0.0 July 2025 SRdAP process EV 20251008: 2025-07-10 to 2025-10-08 V1.1.1 November 2025 Publication
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
1 Scope
|
The present document defines standardization issues for Smart Contracts, as defined in Data Act [i.1], and based on Electronic Ledgers as defined by eIDAS2 [i.2]. It builds on existing and planned standardization and publicly available specifications. It presents a novel and as yet unpublished Chain of Trust, by addressing the role of all involved entities in building, deploying, and executing a Smart Contract computer program on an Electronic Ledger. All the relevant actors, artifacts, hardware, networks and tools, are identified by emphasizing the critical points where governance, safety, security, and identity issues are required. The Chain of Trust will be extensively translated in suitable recommendations in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. The security of Smart Contracts will be significantly compromised by an incomplete validation chain, which exposes users to various risks, including fraud and attacks. NOTE 1: The present document summarizes the results of a scoping study that examines the issues for the application of Smart Contracts, particularly in relation to the European frameworks outlined in the Data Act [i.1] and eIDAS2 [i.2] regulations. The goal is to pinpoint standardization issues for Smart Contracts and Electronic Ledgers in data-sharing computer applications. Additionally, the study considers reports and standards from ETSI ISG PDL (at the time of the publication of the present document conveyed into ETSI TC DATA), ETSI TC ESI, and checks consistency with ISO and CEN documents. NOTE 2: Unless otherwise specified in the present document, the definition of Smart Contracts refers to Regulation (EU) 2023/2854 [i.1] and the definition of Electronic Ledgers, and Qualified Electronic Ledger refer to Regulation (EU) 2022/2065 [i.2]. See Annex C for further details. The present document is structured as follows: • Clause 4 enumerates the regulations, applied standards, EU initiatives and other activities involved for the use of Smart Contracts in Data Sharing Computer Applications. • Clause 5 is the core of the present document. It identifies the entities and their inter-relations for the creation, validation, deployment and use of Smart Contracts in Electronic Ledgers. A Chain of Trust listing the main entities and their relations will be presented and discussed; the Chain of Trust allows to highlight issues that will be focused in the next clause. • Clause 6 lists in a concise way the issues that are translated into formal requirements in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. • Clause 7 concludes. • Annex A presents four figures showing a particular, fine-grained, implementation of the Chain of Trust as presented in Table 1: entities, their relations participating in the design of SC Language, the deployment, and execution of Smart Contracts on a Qualified Electronic Ledger. Other implementations are also possible. • Annex B graphically and informally depicts, the Chain of Trust, as formally described in Table 2. • Annex C gives a comparative overview of definitions in normative and standard documents. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 8
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
2 References
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
2.1 Normative references
|
Normative references are not applicable in the present document.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
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 included in the present clause were valid at the time of publication ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonized rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act). [i.2] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework (eIDAS2). [i.3] ISO 22739:2024: "Blockchain and distributed ledger technologies — Vocabulary". [i.4] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.5] ISO/IEC 15408: "Information security, cybersecurity and privacy protection — Evaluation criteria for IT security". [i.6] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC (eIDAS). [i.7] Regulation (EU) No 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). [i.8] ISO 9001:2015: "Quality management systems — Requirements". [i.9] ISO/IEC 27001:2022: "Information security, cybersecurity and privacy protection — Information security management systems — Requirements". [i.10] ETSI TR 119 476: "Electronic Signatures and Trust Infrastructures (ESI); Analysis of selective disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes". [i.11] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive). [i.12] ETSI TS 119 541: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Smart Contracts using Electronic Ledgers". [i.13] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy Requirements for Trust Service Providers". ETSI ETSI TR 119 540 V1.1.1 (2025-10) 9 [i.14] ETSI EN 319 403-1: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 1: Requirements for conformity assessment bodies assessing Trust Service Providers". [i.15] ISO/TS 23635:2022: "Blockchain and distributed ledger technologies — Guidelines for governance". [i.16] ETSI TS 119 542: "Electronic Signatures and Trust Infrastructures (ESI); Use of EU Digital Identity Wallets and electronic signatures for identification with Smart Contracts". [i.17] Architecture and Reference Framework (ARF) for the European Digital Identity (EUDI) Wallet. [i.18] ENISA: "Digital Identity Standards publications". [i.19] ISO 23257:2022: "Blockchain and distributed ledger technologies — Reference architecture". [i.20] UNCITRAL Model Law on Automated Contracting finalized by the UN Commission on International Trade Law. [i.21] ISO 24332:2025: "Information and Documentation - Blockchain and distributed ledger technology (DLT) in relation to authoritative records, records systems and records management". Forthcoming. [i.22] ETSI TR 104 173: "Data Solutions (DATA); Oracles for Smart Contracts executed in Electronic Ledgers". Forthcoming. [i.23] ETSI TS 104 172: "Data Solutions (DATA); ETSI Specification of the Requirements on Ledgers and Smart Contracts". Forthcoming. [i.24] The ROCQ theorem prover. [i.25] The Isabelle theorem prover. [i.26] The Lean theorem prover. [i.27] X. Leroy: "Formal verification of a realistic compiler". Communication of the ACM. Vol 52, pp.107-115, 2009. [i.28] CEN-CENELEC White paper: "Blockchain and Distributed Ledger Technologies. Recommendations for Successful Adoption in Europe of Emerging Technical Standards on Distributed Ledger/Blockchain Technologies". 2018. [i.29] Recommendation ITU-T F.751.0: "Requirements for Distributed Ledger Systems". [i.30] Recommendation ITU-T F.751.8: "Technical framework for distributed ledger technology (DLT) to cope with regulation". [i.31] Recommendation ITU-T X.1401: "Security threats to distributed ledger technology". [i.32] Recommendation ITU-T X.1402: "Security framework for distributed ledger technology". [i.33] Recommendation ITU-T X.1403: "Security guidelines for using distributed ledger technology for decentralized identity management". [i.34] Recommendation ITU-T X.1412: "Security requirements for smart contract management based on the distributed ledger technology". [i.35] ETSI GR PDL 001: "Permissioned Distributed Ledger (PDL); Landscape of Standards and Technologies". [i.36] ETSI GR PDL 002: "Permissioned Distributed Ledger (PDL); Applicability and compliance to data processing requirements". [i.37] ETSI GR PDL 003: "Permissioned Distributed Ledger (PDL); Application Scenarios". [i.38] ETSI GR PDL 004: "Permissioned Distributed Ledgers (PDL); Smart Contracts; System Architecture and Functional Specification". ETSI ETSI TR 119 540 V1.1.1 (2025-10) 10 [i.39] ETSI GS PDL 005: "Permissioned Distributed Ledger (PDL); Proof of Concepts Framework". [i.40] ETSI GR PDL 006: "Permissioned Distributed Ledger (PDL); Inter-Ledger interoperability". [i.41] ETSI GR PDL 008: "Permissioned Distributed Ledger (PDL); Research and Innovation Landscape". [i.42] ETSI GR PDL 009: "Permissioned Distributed Ledger (PDL); Federated Data Management". [i.43] ETSI GR PDL 010: "PDL Operations in Offline Mode". [i.44] ETSI GS PDL 011: "Permissioned Distributed Ledger (PDL); Specification of Requirements for Smart Contracts' architecture and security". [i.45] ETSI GS PDL 012: "Permissioned Distributed Ledger (PDL); Reference Architecture". [i.46] ETSI GS PDL 013: "Permissioned Distributed Ledger (PDL); Supporting Distributed Data Management". [i.47] ETSI GR PDL 014: "Permissioned Distributed Ledger (PDL); Study on non-repudiation techniques". [i.48] ETSI GS PDL 015: "Permissioned Distributed Ledger (PDL); Reputation management". [i.49] ETSI GR PDL 017: "Permissioned Distributed Ledger (PDL); Application of PDL to Amended Regulation 910/2014 (eIDAS2) Qualified Trust Services". [i.50] ETSI GR PDL 018: "Permissioned Distributed Ledger (PDL); Redactable Distributed Ledgers". [i.51] ETSI GR PDL 019: "PDL Services for Decentralized Identity and Trust Management". [i.52] ETSI GR PDL 020: "Permissioned Distributed Ledger (PDL); Wireless Consensus Network". [i.53] ETSI GR PDL 021: "Permissioned Distributed Ledgers (PDL); Overview of use cases in 3GPP network and impact analysis on architecture integration". [i.54] ETSI GS PDL 022: "Permissioned Distributed Ledgers (PDL); PDL in Wholesale Supply Chain Management". [i.55] ETSI GS PDL 023: "PDL service enablers for Decentralized Identification and Trust Management". [i.56] ETSI GS PDL 024: "Permissioned Distributed Ledgers (PDL); Architecture enhancements for PDL service provisioning in telecom networks". [i.57] ETSI GS PDL 025: "Permissioned Distributed Ledger (PDL); Wireless Consensus Network Composition and Organization". [i.58] ETSI GS PDL 026: "Permissioned Distributed Ledgers (PDL); PDL in Settlement of Usage-Based Services". [i.59] ETSI GS PDL 027: "Permissioned Distributed Ledger (PDL); Self-Sovereign Identity (SSI) in telecom networks". [i.60] ETSI GS PDL 028: "Permissioned Distributed Ledger (PDL); Specification utilizing PDL to Standardized IoT Service Layer Platform oneM2M". [i.61] ETSI GS PDL 029: "Permissioned Distributed Ledger (PDL); Distributed Autonomous Organization (DAO)". [i.62] ETSI GS PDL 030: "Permissioned Distributed Ledger (PDL); Trust in Telecom System". [i.63] ETSI GS PDL 031: "Permissioned Distributed Ledger (PDL); Energy Consumption Data Sharing based on PDL Service". [i.64] ETSI GS PDL 032: "Permissioned Distributed Ledger (PDL); Artificial Intelligence for Permissioned Distributed Ledger". ETSI ETSI TR 119 540 V1.1.1 (2025-10) 11 [i.65] ETSI GS PDL 033: "Permissioned Distributed Ledger (PDL); Smart Contracts; System Architecture and Functional Specification". [i.66] ISO/IEC 22123-2:2023: "Cloud computing - Part 1: Vocabulary". [i.67] IEEE 1934™-2018: "Standard for Adoption of OpenFog Reference Architecture for Fog Computing". [i.68] Regulation (EU) 2019/881 of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing Regulation (EU) No 526/2013 (Cybersecurity Act). [i.69] Commission Implementing Regulation (EU) 2024/482 of 31 January 2024 laying down rules for the application of Regulation (EU) 2019/881 of the European Parliament and of the Council as regards the adoption of the European Common Criteria-based cybersecurity certification scheme (EUCC). [i.70] ISO/IEC 24760-1:2025: "Information security, cybersecurity and privacy protection — A framework for identity management. Part 1: Core concepts and terminology". [i.71] ISO/IEC 29115:2013: "Information technology — Security techniques — Entity authentication assurance framework". [i.72] Ethereum®: "ERC-721 Non-Fungible Token Standard". [i.73] ISO 20022: "Universal financial industry message scheme".
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
3 Definition of terms, symbols and abbreviations
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
3.1 Terms
|
For the purposes of the present document, the following terms apply: algorithm: set of rules and non-ambiguous procedures to solve a class of problems Chain of Trust: trust needs of legal or natural persons, as used in Regulation (EU) 2024/1183 [i.2], and of the relationships existing among them Deontic Logic: philosophical logic that is concerned with obligation, permission, optional, non-optional, obligatory, must, the least one can do, better than, ought, blame, responsibility, indifferent, and related concepts distributed ledger: ledger that is shared across a set of Distributed Ledger Technology (DLT) nodes and synchronized between the DLT nodes using a consensus mechanism NOTE 1: According to ISO 22739 [i.3]. NOTE 2: A distributed ledger as defined in ISO 22739 [i.3] is a special kind of an Electronic Ledger: the vice- versa is not true. Electronic Ledger: sequence of electronic data records, ensuring the integrity of those records and the accuracy of the chronological ordering of those records NOTE 1: According to Article 3(52) in Regulation (EU) 2024/1183 [i.2]. NOTE 2: From Regulation (EU) 2024/1183 [i.2], Recital (68): "This Regulation should ensure technological neutrality, namely neither favoring, nor discriminating against, any technology used to implement the new trust service for electronic ledgers". "The process of creating and updating an electronic ledger depends on the type of ledger used, namely whether it is centralized or distributed.". ETSI ETSI TR 119 540 V1.1.1 (2025-10) 12 NOTE 3: The definition of Electronic Ledger in Regulation (EU) 2024/1183 [i.2] is more general than the definition of distributed ledger in ISO 22739 [i.3]. Qualified Electronic Ledger: Electronic Ledger provided by a qualified trust service provider and which meets the requirements laid down in Article 45l NOTE: According to Article 3/53 in Regulation (EU) 2024/1183 [i.2]. SC Byte Code: computer program, written in SC Byte Code Language, that is executed on the top of a SC Virtual Machine and that is produced by a compilation of a SC Source Code NOTE: It should correspond to the definition of Smart Contract in [i.1]. SC Byte Code Language: domain specific language for executing Smart Contracts SC Compiler: computer program, written in any programming language, translating every SC Source Code, eventually annotated with SC Legal Text, into a semantically equivalent, machine-readable SC Byte Code, and some auxiliary files NOTE 1: A compilation of a SC Source Code by a SC Compiler should produce a number of files that can be packaged in a suitable SC Package. NOTE 2: As an explanatory example, see the number of parameters of the Solidity SC Compiler. NOTE 3: It should be open source. SC Compiler Policy: set of rules to be respected by a SC Compiler SC Compiler Publisher: legal or natural persons responsible to sign the SC Compiler and the SC Compiler Policy, produced by the SC Compiler Team SC Compiler Team: legal or natural persons that produce a SC Compiler SC Deployer: legal or natural persons identified by the Electronic Ledger, in charge of putting a SC Byte Code into the Electronic Ledger SC Deployer Policy: set of rules and non-ambiguous procedures to be respected by a SC Deployer SC Development Policy: set of rules and non-ambiguous procedures to be respected in order to produce a SC Package SC Development Team: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible to produce a SC Package SC Documentation: documentary information in support of the Smart Contract NOTE: Elements of the documentation can/may be produced by a compilation of a SC Source Code and can/may also include the policy documentation and the identity documentation. SC Execution Report: signed evidence of an execution of a Smart Contract in an Electronic Ledger SC Language: domain specific language for defining Smart Contracts SC Language Publisher: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], signing the SC Language Specifications and the SC Language Specification Policy produced by the SC Language Specification Team, and also responsible to sign the SC Compiler and the SC Virtual Machine, produced by the SC Compiler Team and SC Virtual Machine Team, respectively SC Language Specification: syntax, semantic, and run-time execution model of a domain specific language for defining Smart Contracts NOTE 1: The SC Language Specification consist of: ETSI ETSI TR 119 540 V1.1.1 (2025-10) 13 1) a SC Source Code Language syntax, written in Backus-Naur Form grammar format; 2) a SC Source Code Language semantic, written in English prose or in formal system (lambda- calculus, term rewriting systems) for expressing computations, and usually referred as the semantic of the SC Language; 3) a SC Byte Code Language syntax; 4) a SC Byte Code Language semantic, written in English prose or in formal system (stack and store reduction semantics) for expressing computations, and usually referred as the execution or run-time environment of the SC Language; this is usually referred as SC Virtual Machine specification; 5) an algorithmic transaction of a computer program, written in a SC Source Code Language into a semantically equivalent computer program, written in a SC Byte Code Language; this is usually referred as SC Compiler specification. NOTE 2: It should be open access. SC Language Specification Policy: set of rules to be respected by a SC Language Specification NOTE: It should be open access. SC Language Specification Team: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible to produce a SC Language Specification and a SC Language Specification Policy SC Legal Team: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible to audit the SC Source Code and or the SC Byte Code using a fixed SC Compiler and SC Virtual Machine, and to produce a SC Legal Text that meets the SC Development Policy SC Legal Text: legal text attached or annotated into either a SC Source Code and a SC Byte Code assessing legal basis, legal requirements, legal obligations, legal use, legal rights, legal certainty, legal status and legal value to a Smart Contract NOTE: It should refer a SC Compiler and SC Virtual Machine. SC Oracle: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], that produces external data to a Smart Contract stored in an identified Electronic Ledger so triggering Electronic Transactions SC Package: set of files, such as SC Source Code, SC Byte Code, SC Legal Text, and any other SC Documentation in support of the Smart Contract, signed by the SC Publisher SC Provider: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible for providing and the execution of a Smart Contract to a SC User NOTE 1: The SC Provider may offer or trade a Smart Contract with a SC User. NOTE 2: A SC Provider can take input from external sources other than SC User. NOTE 3: The SC Provider can be a "Vendor of applications using Smart Contracts", as defined in Article 36 Regulation (EU) 2023/2854 [i.1]. SC Provider Policy: policy (or policies) governing the behaviour or the SC Provider SC Publisher: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible to sign the SC Legal Text, the SC Source Code, the SC Byte Code, and the SC Documentation, produced by the SC Development Team, using the SC Compiler SC Publisher Policy: policy (or policies) governing the behavior or the SC Provider SC Source Code: computer program, written in SC Source Code Language, defining the behavior of a Smart Contract NOTE: A SC Source Code is translated using a SC Compiler into a semantically equivalent SC Byte Code, written in a SC Byte Code Language. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 14 SC User: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], that uses services produced by Smart Contracts, provided by an identified SC Provider by accepting SC Legal Text agreements and SC Provider agreements and uses Smart Contracts to put Electronic Records into an Electronic Ledger NOTE 1: A SC User can be a user of a "connected product or related service", as defined in Regulation (EU) 2023/2854 [i.1]. NOTE 2: A SC User can be a DLT User, as defined in ISO 22739 [i.3]. SC Virtual Machine: computer program, written in any programming language, executing as input a SC Byte Code and producing as output records that will be stored into the Electronic Ledger NOTE: It should be open source. SC Virtual Machine Policy: set of rules and non-ambiguous procedures to be respected by a SC Byte Code NOTE: It should be open source. SC Virtual Machine Team: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible to produce a SC Virtual Machine SC Virtual Machine Publisher: legal or natural person as used in Regulation (EU) 2024/1183 [i.2], responsible to sign the SC Virtual Machine and the SC Virtual Machine Policy, produced by the SC Virtual Machine Team Smart Contract: computer program used for the automated execution of an agreement or part thereof, using a sequence of electronic data records and ensuring their integrity and the accuracy of their chronological ordering NOTE 1: According to Article 2/39, 104 in Regulation (EU) 2023/2854 [i.1]. NOTE 2: As per ISO 22739 [i.3]: A "smart contract is a computer program stored in a distributed ledger technology (DLT) system wherein the outcome of any execution of the program is recorded on the distributed ledger". NOTE 3: The definition of Smart Contract in Regulation (EU) 2023/2854 [i.1] is more general than the definition of Smart Contract in ISO 22739 [i.3]. Smart Legal Contract: Smart Contract with legal relevance obtained by embedding or by pointing a SC Legal Text
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
3.2 Symbols
|
Void.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence API Application Public Interface ARF Architecture and Reference Framework CA Certificate Authority DAG Directed Acyclic Graph dAPP distributed Application DID Decentralized Identity DLT Distributed Ledger Technology DPoS Delegated Proof-of-Stake EAA Electronic Attestations of Attributes EAA-Pub Electronic Attestations of Attributes Public EAL Evaluation Assurance Level EBSI European Blockchain Services Infrastructure EDIC European Digital Infrastructure Consortium eID electronic Identification ENISA European Union Agency for Cybersecurity eSIM electronic Subscriber Identity Module ETSI ETSI TR 119 540 V1.1.1 (2025-10) 15 EU European Union EUDI European Digital Identity EUDIW European Digital Identity Wallet EVM Ethereum Virtual Machine GDPR General Data Protection Regulation HSM Hardware Security Module INATBA International Association for Trusted Blockchain Applications IoT Internet of Things IPFS InterPlanetary File System ISO International Organization for Standardization KYC Know your Customer mobile-ID Mobile Digital Signature NFC Near Field Communication NFT Non-Fungible Token NIST National Institute of Standards and Technology PID Person Identification Data PIN Personal Identification Number PKI Public Key Infrastructure PoS Proof of Stake PoW Proof of Work QEAA Qualified Electronic Attestations of Attributes QES Qualified Electronic Signature QTSP Qualified Trust Service Provider SC Smart Contract SIM Subscriber Identity Module SPV Simplified Payment Verification TSP Trust Service Provider UTXO Unspent Transaction Output VM Virtual Machine 4 Smart Contracts related regulation, standardization and initiatives
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.1 Essential Overview
|
The present clause presents an overview of all relevant European Union Regulations, Standards, Projects, and other activities involving Smart Contracts and Electronic Ledgers in a neutral and agnostic manner. For each of these activities, the present document proceeds as follows: • Essential Overview: Provide an extended abstract of the activities, tailored specifically to Smart Contract and Electronic Ledgers. • Terminology: Identify main entities and relationships among them, as defined in Clause 3.1. • Chain of Trust: As defined in Clause 3.1, tailored specifically to Smart Contract and Electronic Ledgers. NOTE: The reviewed material does not claim to be comprehensive but has been selected to give as complete an overview as possible. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 16
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2 Regulations
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.1 Data Act
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.1.1 Essential Overview
|
In addressing the definition of a Smart Contract, the following objectives can be derived directly from the definition in Regulation (EU) 2023/2854 [i.1] "a computer program used for the automated execution of an agreement or part thereof, using a sequence of electronic data records and ensuring their integrity and the accuracy of their chronological ordering" and the wider application of that definition to that of a contract "an agreement that is intended to be enforceable by law and to the execution of a contract "the process of finalizing a legally binding contractual agreement between two or more parties and committing to the terms contained within that contract". 1) The automated execution of an agreement, or part thereof, represents the intended agreement of the parties. 2) The parties of the agreement can be correctly identified in case of legal dispute. 3) The recording of the sequence electronic records representing the agreement is maintained in a way which ensures their integrity and the accuracy of their chronological ordering. 4) A party of an agreement cannot later deny the agreement. 5) Privacy of sensitive information is maintained. This can include information in the data records and identities the parties of the agreement. The elements defined in the Data Act can be bound to a governance framework for identity (see Regulation (EU) 2024/1183 [i.2] to enable strict conformance to item 2). In addition, it is recognized that Smart Contracts are, implicitly, required to be transparent and explicable, arising from both items 1 and 2 above wherein the parties are able to agree that the Smart Contract is the intended agreement of the parties. It is noted that the identities of the parties to the agreement are only required to be identified by 3rd parties in the case of legal dispute and in accordance with item 5 it is reasonable to treat the identity of parties to the agreement as private.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.1.2 Terminology
|
Smart Contracts, Electronic Ledgers.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.1.3 Chain of Trust
|
Regulation (EU) 2023/2854 [i.1] is agnostic with respect to the Chain of Trust, and in particular with the production of Smart Contracts.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.2 eIDAS2
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.2.1 Essential Overview
|
The Electronic Identification, Authentication, and Trust Services Regulation (eIDAS) was first published in 2014 to provide a standardized framework across the European Union for electronic identification (eID), electronic signatures, and trust services. The aim was to enable secure and seamless digital transactions across EU member states. The eIDAS2 Regulation [i.2], published in 2024, amends the original regulation, addressing some of its limitations and introducing significant new features to adapt to the evolving digital landscape. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 17 While eIDAS laid the foundation for cross-border digital identification and trust services in the EU, Regulation (EU) 2024/1183 [i.2] significantly expands and modernizes the framework. The key innovation is the European Digital Identity Wallet (EUDIW), which gives citizens more control over their personal data, enhances security, and ensures that both the public and private sectors embrace digital identities. This evolution reflects the increasing need for secure, user-controlled, and interoperable digital solutions across Europe. eIDAS2 does not address Smart Contracts in solo, but a Smart Contract as defined by the Data Act [i.1] may use elements of eIDAS2 [i.2] such as Electronic Ledgers that are cited in the Data Act. eIDAS2 regulation defines Electronic Ledgers as given below. The definition of Electronic Ledgers in Article 3: "(52) "electronic ledger" means a sequence of electronic data records, ensuring the integrity of those records and the accuracy of the chronological ordering of those records;" This definition matches the definition of Smart Contracts in Regulation (EU) 2023/2854 [i.1] for the use of: "a sequence of electronic data records and ensuring their integrity and the accuracy of their chronological ordering"; Section 11, Article (45k) defines the legal effects of Electronic Ledgers: "1. An electronic ledger shall not be denied legal effect or admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements for qualified electronic ledgers. 2. Data records contained in a qualified electronic ledger shall enjoy the presumption of their unique and accurate sequential chronological ordering and of their integrity." and Article (45l) defines following specific requirements for Qualified Electronic Ledgers: "(a) they are created and managed by one or more qualified trust service providers; (b) they establish the origin of data records in the ledger; (c) they ensure the unique sequential chronological ordering of data records in the ledger; (d) they record data in such a way that any subsequent change to the data is immediately detectable, ensuring their integrity over time."
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.2.2 Terminology
|
Electronic Ledgers.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.2.3 Chain of Trust
|
Regulation (EU) 2024/1183 [i.2], as per the publication date of the present document, is agnostic with respect to the Smart Contracts and the Chain of Trust. This can change in the forthcoming eIDAS2 Implementing Acts.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.3 GDPR
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.3.1 Essential Overview
|
The General Data Protection Regulation (GDPR) [i.7] is a comprehensive legal framework established by the European Union to safeguard the personal data of individuals within the EU. It sets stringent rules for data privacy, ensuring that personal data is collected, processed, and stored with a high degree of transparency, security, and accountability. Regulation (EU) No 2016/679 [i.7] applies to all organizations that handle the personal data of EU residents, regardless of the organization's location, and imposes significant penalties for non-compliance. Smart Contracts can potentially support Regulation (EU) No 2016/679 [i.7] compliance by providing automated, transparent, and secure mechanisms for handling personal data, aligning with the regulation's requirements. One of the key ways Smart Contracts can assist is by automating consent management. They can store and track user consent in a tamper-proof manner on a ledger ensuring transparency and that personal data is only processed in accordance with the ETSI ETSI TR 119 540 V1.1.1 (2025-10) 18 agreed-upon terms. This automation can include limiting data usage to specific purposes and ensuring consent is periodically updated or revoked, when necessary, all of which enhances compliance with Regulation (EU) No 2016/679 [i.7] focus on individual control over personal data.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.3.2 Terminology
|
Not applicable.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.3.3 Chain of Trust
|
Regulation (EU) No 2016/679 [i.7] is agnostic with respect to Smart Contracts, Electronic Ledgers and the Chain of Trust.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.4 UNCITRAL model law on automated contracting
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.4.1 Essential Overview
|
The UNCITRAL Model Law [i.20] provides a legal framework to enable the use of automation in international contracts, including through the deployment of artificial intelligence techniques and Smart Contracts, as well as in machine-to-machine transactions. It is intended to complement and supplement existing laws on electronic transactions, in particular those based on other UNCITRAL electronic commerce texts, which have been enacted in over one hundred jurisdictions worldwide. The Model Law is the first legislative text to result from exploratory work conducted by UNCITRAL on legal issues related to the digital economy and digital trade, with work on data contracts and distributed ledger technology as described in ISO 22739 [i.3].
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.4.2 Terminology
|
Smart Contracts.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.2.4.3 Chain of Trust
|
The UNCITRAL Model Law [i.20] is agnostic with respect to the Chain of Trust.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3 Standardization
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.1 ISO/TC 307
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.1.1 Essential Overview
|
The scope of ISO/TC 307 reads: "standardisation of blockchain technologies and distributed ledger technologies". Blockchain technology holds immense promise to revolutionize not only the financial domain, but a whole host of things from societal inclusion to efficiencies in government, health and all areas of business. ISO/TC 307, blockchain and distributed ledger technologies, has been set up to meet the growing need for standardization in this area by providing internationally agreed ways of working with it to improve security, privacy and facilitate worldwide use of the technology through better interoperability. This is especially relevant due to the number of enterprises, across various sectors, that are developing blockchain and distributed ledger technologies as a product. The standardization work of ISO/TC 307 has been divided into six groups, namely Foundations (WG1), Security, privacy and identity (WG2), Smart Contracts and their applications (WG3), Use cases (WG4); Governance (WG5), and Interoperability (WG6). The need for collaboration and cooperation has been identified and ISO/TC 307 is liaising with other organizations like ETSI (namely ETSI TC ESI, TC DATA), ISO and IEC committees, as well as external organizations, to minimize any overlap. ISO/TC 307 produced (among many) the following standard specifications and technical reports: ISO 22739 [i.3], ISO/TS 23635 [i.15], ISO 23257 [i.19], and ISO 24332 [i.21]. ISO 22739 [i.3] defines a vocabulary for Blockchain and distributed ledger technologies; ISO/TS 23635 [i.15] defines guidelines for governance defined blockchain and distributed ledger technologies. ISO 23257 [i.19] defines a reference architecture for distributed ledger technology systems including blockchain systems. The reference architecture addresses concepts, cross-cutting aspects, architectural considerations, and architecture views, including functional components, roles, activities, and their relationships for blockchain and distributed ledgers. ISO 24332 [i.21] analyses ETSI ETSI TR 119 540 V1.1.1 (2025-10) 19 challenges, considerations, and potential benefits of blockchain and distributed ledger technology in relation to records management standards and related standards for systems that create records that are required to be authoritative records; can be used as records systems; or can be used for records management, including records controls.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.1.2 Terminology
|
Smart Contracts and distributed ledgers as defined in ISO 22739 [i.3].
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.1.3 Chain of Trust
|
ISO 22739 [i.3], ISO/TS 23635 [i.15], and ISO 23257 [i.19] are agnostic with respect to the Chain of Trust. However, ISO/TC 307 in ISO/TS 23635 [i.15] discuss some trust requirements on (qualified) DLT systems.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.2 CEN/CENELEC/JTC 19
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.2.1 Essential Overview
|
CEN/CLC/JTC 19 "Blockchain and distributed ledger technologies" was established based on the recommendations presented in the CEN-CENELEC White Paper [i.28] in 2018 on distributed and ledger technologies. It works in close contact with ISO/TC 307 "Blockchain and distributed ledger technologies". It established the following WGs with the given scope and work items: WG1 (development of standard for policy and security requirements for trust services providing Electronic Ledger services; standardization on functional and interoperability requirements for decentralized identifier and decentralized identity management where distributed ledger is only one possible infrastructure), WG2 (environmental and sustainability classification methodology of consensus mechanisms of blockchain and distributed ledger technologies); WG3 (development of standards for privacy in distributed ledger technologies to ensure compliance to GDPR [i.7] requirements). CEN/CLC/JTC 19 adopted ISO TC 307 vocabulary [i.3] directly into European Framework. CEN/CLC/JTC 19 considers ISO TC 307 documents [i.15], [i.19], and [i.21] as relevant basements for the CEN Project on Policy and security requirements for trust services providing ledger services and are so participating to a European standard framework for Electronic Ledgers.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.2.2 Terminology
|
Distributed ledgers and Smart Contracts as defined in ISO 22739 [i.3].
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.2.3 Chain of Trust
|
The technical body CEN/CENELEC/JTC 19 "Blockchain and Distributed Ledger Technologies" is agnostic with respect to the Chain of Trust.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.3 ETSI ISG PDL
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.3.1 Essential Overview
|
The ETSI Industry Specification Group on Permissioned Distributed Ledger (ETSI ISG PDL), at the time of the publication of the present document, conveyed into the new ETSI TC DATA, analyses and provides the foundations for the operation of permissioned distributed ledgers, with the ultimate purpose of creating an open ecosystem of industrial solutions to be deployed by different sectors, fostering the application of these technologies, and therefore contributing to consolidate the trust and dependability on information technologies supported by global, open telecommunications networks. The group puts its focus on addressing infrastructure and operational aspects that are not currently covered by previous or parallel standardization activities. In addition to that, ETSI ISG PDL fosters industry convergence towards shared standards with the intent of avoiding duplication and contradicting publications. The ETSI ISG PDL started from already available experiences in the field of permissioned distributed ledgers, seeking for the definition of open and well-known operational mechanisms to validate participant nodes, support the automation of the lifecycles of the ledger and individual nodes, publish and execute operations regarding the recorded transactions ETSI ETSI TR 119 540 V1.1.1 (2025-10) 20 through Smart Contracts, improve security of distributed ledgers during both their design and operation and establish trusted links among different distributed ledgers using these mechanisms. ETSI ISG PDL has been active since 2019 and has produced the following completed deliverables Group Report (GR) and Group Specifications (GS) to date ETSI TR 104 173 [i.22], ETSI TS 104 172 [i.23], ETSI GR PDL 001 [i.35], ETSI GR PDL 002 [i.36], ETSI GR PDL 003 [i.37], ETSI GR PDL 004 [i.38], ETSI GS PDL 005 [i.39], ETSI GR PDL 006 [i.40], ETSI GR PDL 008 [i.41], ETSI GR PDL 009 [i.42], ETSI GR PDL 010 [i.43], ETSI GS PDL 011 [i.44], ETSI GS PDL 012 [i.45], ETSI GS PDL 013 [i.46], ETSI GR PDL 014 [i.47], ETSI GS PDL 015 [i.48], ETSI GR PDL 017 [i.49], ETSI GR PDL 018 [i.50], ETSI GR PDL 019 [i.51], ETSI GR PDL 020 [i.52], ETSI GR PDL 021 [i.53], ETSI GS PDL 022 [i.54], ETSI GS PDL 023 [i.55], ETSI GS PDL 024 [i.56], ETSI GS PDL 025 [i.57], ETSI GS PDL 026 [i.58], ETSI GS PDL 027 [i.59], ETSI GS PDL 028 [i.60], ETSI GS PDL 029 [i.61], ETSI GS PDL 030 [i.62], ETSI GS PDL 031 [i.63], ETSI GS PDL 032 [i.64], ETSI GS PDL 033 [i.65]. Amongst the published documents, Smart Contracts were presented in ETSI GR PDL 004 [i.38], ETSI GS PDL 011 [i.44], ETSI GS PDL 033 [i.65], distributed ledgers and interoperability and all data issues in ETSI TR 104 173 [i.22], ETSI GR PDL 006 [i.40], ETSI GR PDL 009 [i.42], ETSI GR PDL 010 [i.43], ETSI GS PDL 012 [i.45], ETSI GS PDL 013 [i.46], ETSI GR PDL 018 [i.50]; trust, identity, and repudiation issues in ETSI GR PDL 014 [i.47], ETSI GR PDL 019 [i.51], ETSI GS PDL 023 [i.55], ETSI GS PDL 027 [i.59], ETSI GS PDL 030 [i.62], network issues in ETSI GR PDL 020 [i.52], ETSI GS PDL 022 [i.54] ETSI GS PDL 024 [i.56], ETSI GS PDL 025 [i.57], ETSI GS PDL 027 [i.59]; IoT, AI, and energy issues in ETSI GS PDL 028 [i.60], ETSI GS PDL 031 [i.63], ETSI GS PDL 032 [i.64]; reputation, settlement and Digital Autonomous Organizations in ETSI GS PDL 015 [i.48], ETSI GS PDL 026 [i.58], ETSI GS PDL 029 [i.61]. The guidelines for governance of Smart Contracts executed on a blockchain and distributed ledgers and in support for eIDAS2 [i.1] trust services were discussed in ETSI GR PDL 017 [i.49]. These publications provide a roadmap for how Smart Contracts can be used to automate and secure transactions, ensure compliance with European regulations and facilitate cross-border interoperability. The emphasis is on creating secure, scalable, and compliant Smart Contracts that can be used in a variety of industries, ranging from finance to healthcare, all within the highly controlled environments of permissioned ledgers. As per ETSI ISG rules, ISG PDL cannot produce normative recommendations, only surveys, reference architectures, proof of concepts, and can suggests guidance. The heritage of the produced documents will convey into normative recommendations within the new ETSI TC DATA (e.g. ETSI TR 104 173 [i.22] and ETSI TS 104 172 [i.23]).
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.3.2 Terminology
|
Electronic Ledgers, distributed ledgers and Smart Contracts as defined in ISO 22739 [i.3].
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.3.3 Chain of Trust
|
ETSI ISG PDL (at the time of the publication of the present document) is agnostic with respect to the Chain of Trust. This will change in the future within the new ETSI TC DATA.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.4 ITU-T X-Series Recommendations Study Group 17
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.4.1 Essential Overview
|
ITU-T X is a series of standards from the Standardization Sector the International Telecommunication Union (ITU-T), written by ITU-T Study Group 17. The description of the X series is: "Data networks, open system communications and security". The group produced a number of documents. In a nutshell: • Recommendation ITU-T F.751.0 [i.29] Requirements for Distributed Ledger Systems. • Recommendation ITU-T F.751.8 [i.30] Technical framework for distributed ledger technology (DLT) to cope with regulation. • Recommendation ITU-T X.1401 [i.31] Security threats to distributed ledger technology. • Recommendation ITU-T X.1402 [i.32] Security framework for distributed ledger technology. • Recommendation ITU-T X.1403 [i.33] Security guidelines for using distributed ledger technology for decentralized identity management. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 21 • Recommendation ITU-T X.1412 [i.34] Security requirements for smart contract management based on the distributed ledger technology.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.4.2 Terminology
|
distributed ledgers as defined in Recommendation ITU-T F.751.0 [i.29], Smart Contracts as defined in Recommendation ITU-T X.1412 [i.34].
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.4.3 Chain of Trust
|
ITU-T X Study Group 17 is agnostic with respect to the Chain of Trust. However, Recommendation ITU-T X.1412 [i.34] contains some interesting intuitions on security requirements for Smart Contracts management based on the distributed ledger technology.
|
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.5 IEEE SA P2418
| |
142241be1ea90643e055df0a41f4debe
|
119 540
|
4.3.5.1 Essential Overview
|
4.3.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.